Hi all,
Rather strange issue which may or may not be a problem.
I’ve been bought in at a late stage to ensure that some Progress databases are backed up regularly.
I’ve little previous experience of Progress Databases in general, and this database in particular, but having set this up previously for another system I’ve used PROBKUP to perform a couple of FULL ONLINE backups outside office hours, and some incrementals (actually I use the -io switch with a value of 4 to make them differentials) during office hours.
The full backups are around 1.7GB.
However, the incremental backups are always around the same size of 1.4 GB, even if I remove the IO switch from the command and run one directly after a previous run.
The data SHOULD be fairly static I would have thought (nobody has been able to suggest otherwise)
The command I use for the FULL backup is…
PROBKUP ONLINE (db name and location) (.bak name and location) –com
Then for each of 4 Incrementals I use…
PROBKUP ONLINE (db name and location) INCREMENTAL (.bak name and location) –io 4 –com
In theory very few changes should be taking place between each backup so I’m surprised that the incrementals are so large. Especially as this is the case for the LIVE and TEST versions of the same database.
Can anyone suggest a reason for this or anything I can check out?
Progress version 9.1C IIRC
Many thanks
Graeme
Rather strange issue which may or may not be a problem.
I’ve been bought in at a late stage to ensure that some Progress databases are backed up regularly.
I’ve little previous experience of Progress Databases in general, and this database in particular, but having set this up previously for another system I’ve used PROBKUP to perform a couple of FULL ONLINE backups outside office hours, and some incrementals (actually I use the -io switch with a value of 4 to make them differentials) during office hours.
The full backups are around 1.7GB.
However, the incremental backups are always around the same size of 1.4 GB, even if I remove the IO switch from the command and run one directly after a previous run.
The data SHOULD be fairly static I would have thought (nobody has been able to suggest otherwise)
The command I use for the FULL backup is…
PROBKUP ONLINE (db name and location) (.bak name and location) –com
Then for each of 4 Incrementals I use…
PROBKUP ONLINE (db name and location) INCREMENTAL (.bak name and location) –io 4 –com
In theory very few changes should be taking place between each backup so I’m surprised that the incrementals are so large. Especially as this is the case for the LIVE and TEST versions of the same database.
Can anyone suggest a reason for this or anything I can check out?
Progress version 9.1C IIRC
Many thanks
Graeme