Online backup and PROQUIET

[pinne65]

Hello,

In the online backup script we are using the probkup command is not preceded by a PROQUIET. I remember reading somewhere that it was required to keep the database consistent. (Can't find that part again, that's why I'm asking). The backup seems to be working without it though. We can roll forward against it without any problems and start.

Any 5 Cents welcome!

 

[ron]

You are quite safe. A probkup online does not require proquiet. The backup will be "as at" the moment when the backup commenced. During the backup there will be many instances where a block NOT backed-up yet gets updated. probkup "sees" that and backs-up the block prior to the update.

If you need to recover, after restoring the backup you must roll-forward starting with the AI file that commences at the moment when the backup commenced. As you may be aware, probkup will cause an AI file "switch" as at the moment when the backup starts.

The need for proquiet is if you want to backup the database by any means other than by using probkup. But, who would want to do that??

Hope that helps.
Ron.

 

[TomBascom]

If the script is using probkup with the "online" option the db can be up and running and no proquiet is needed. If "online" is not specified then the db must be shutdown but, again, no proquiet is needed.

Basically if probkup runs then all is well.

A quiet point is used to make a non-progress backup of a live database. Typically this would be done by enabling the quiet point (you must wait for the message in the .lg file -- simply issuing "proquiet" and getting a successful return doesn't mean that it is actually enabled yet...), splitting disk mirrors and disabling the proquiet. You then backup the split mirror and after the backup is finished re-sync the mirror.

 

[tamhas]

Note that it is important to choose the moment to start the backup carefully in order to have a known point to which the backup will correspond. If you have users flailing away at the time you start, there will be no clear line of what was and wasn't in the backup ... clear to Progress, but not to the users. Of course, this consideration is largely mitigated by using AI.

 

[pinne65]

Yeah,

Who would not want to use probkup?

Thanks everybody for the clarification!

 

[TomBascom]

It can take quite a while to backup a large database with probkup. Some customers with very large databases need to use the proquiet/split mirror technique in order to get it done in a reasonable amount of time.

But unless that is your situation probkup is the preferred option.