- Print
- DarkLight
- PDF
Database BKP File is a Different Size Between Scheduled Task and Manual Backup
Article summary
Did you find this summary helpful?
Thank you for your feedback
When the scheduled database backup task is done the resulting bkp file is smaller than when doing a manual back up.
Steps To Duplicate:
- Set up scheduled task for database backup
- See that the task runs
- Look at the backup file generated and see the size of 375,640 KB
- Run a manual database backup
- Look at the file generated and see its much larger; 548,088 KB
Answer:
This is because the scheduled task uses a bat file which has the -com parameter for compression whereas the manual backup process does not.
\FIMS\dbbackup.bat has the -com parameter:
call "%DLC%\bin\probkup" online %1 %2\%3 -com
Manual backup instructions in the article mentioned above does not:
Probkup online found ..\dbbackup\found-backupfilename.bkp
See the following Progress article for more detail: https://knowledgebase.progress.com/articles/Article/probkup-com-red-parameters-000073371
\FIMS\dbbackup.bat has the -com parameter:
call "%DLC%\bin\probkup" online %1 %2\%3 -com
Manual backup instructions in the article mentioned above does not:
Probkup online found ..\dbbackup\found-backupfilename.bkp
See the following Progress article for more detail: https://knowledgebase.progress.com/articles/Article/probkup-com-red-parameters-000073371
Compression (-com):
The compression parameter -com will reduce the total size of database backup volumes. Database Blocks below the High Water Mark in each Storage Area are first compressed prior to writing to the backup volume when compression is used:
Using Compression may also speed up the backup process onto a "slow" media (like a tape drive), however it will slow down the backup process onto a fast media (like a disk or network storage) because of the additional processing required to compress the backup. Use the -scan parameter to get an estimate of the final size and the -verbose parameter to get an idea of how fast it's going at 10 second intervals.
The compression parameter -com will reduce the total size of database backup volumes. Database Blocks below the High Water Mark in each Storage Area are first compressed prior to writing to the backup volume when compression is used:
- The unused portion of index and record blocks are compressed to a 3-byte compression string.
- Free Blocks are compressed to the length of their header, 16 bytes.
Using Compression may also speed up the backup process onto a "slow" media (like a tape drive), however it will slow down the backup process onto a fast media (like a disk or network storage) because of the additional processing required to compress the backup. Use the -scan parameter to get an estimate of the final size and the -verbose parameter to get an idea of how fast it's going at 10 second intervals.
Was this article helpful?