Online backup on Linux
- Thread starter nickjean
- Start date
TomBascom
Curmudgeon
Well you could just put that command in cron. It will work as is for any reasonably modern release of Progress and any database less than 2GB (so long as you have disk space for the .bu file).
BTW -- I'm assuming a backup to disk. Personally I always backup to disk first and then backup to tape (if necessary). It's faster and more convenient.
If the database is larger than 2GB then you need to get fancier and use multiple backup extents. Usually you construct a file of extent names and provide the -vs parameter. Something along these lines:
-- backup.list --
/backup/dbname.bu2
/backup/dbname.bu3
/backup/dbname.bu4
/backup/dbname.bu5
/backup/dbname.bu6
/backup/dbname.bu7
/backup/dbname.bu8
-- backup command --
probkup online dbname /backup/dbname.bu1 -com -vs 125000 < backup.list
(Note: The units for -vs are database blocks.)
Of course this whole process could get quite a lot fancier depending on your specific needs. But you haven't mentioned any requirements other than getting an online backup made.
BTW -- I'm assuming a backup to disk. Personally I always backup to disk first and then backup to tape (if necessary). It's faster and more convenient.
If the database is larger than 2GB then you need to get fancier and use multiple backup extents. Usually you construct a file of extent names and provide the -vs parameter. Something along these lines:
-- backup.list --
/backup/dbname.bu2
/backup/dbname.bu3
/backup/dbname.bu4
/backup/dbname.bu5
/backup/dbname.bu6
/backup/dbname.bu7
/backup/dbname.bu8
-- backup command --
probkup online dbname /backup/dbname.bu1 -com -vs 125000 < backup.list
(Note: The units for -vs are database blocks.)
Of course this whole process could get quite a lot fancier depending on your specific needs. But you haven't mentioned any requirements other than getting an online backup made.