ron
Member
Production: Sun V480, Solaris 8, Progress 9.1D06
Warm Spare: Sun E3500, Solaris 8, progress 9.1D06
We're testing a Warm Spare set-up using AI files to update the Warm Spare. There are 8 databases involved.
No problem on Production ... the AI files get swapped when they should ... and despatched to the Warm Spare server.
No problem in the Warm Spare applying the AI files -- works just fine.
No problem taking tape backups using probkup (with -norecover) on the Warm Spare server. And after taking a backup there is no problem continuing to apply the AI files.
HOWEVER ... if a backup from tape is restored to the Warm Spare it expects AI file #1 to be the next to be applied to it. That is not what was expected ... we thought we could continue to apply AI files in the same sequence as previously.
Is there any way to coerce Progress to NOT start back at #1?
If we have to have it the way it is -- it wrecks a substantial slice of our plans. (Where's the melting pot?)
Has anyone else found this to be a problem?
Warm Spare: Sun E3500, Solaris 8, progress 9.1D06
We're testing a Warm Spare set-up using AI files to update the Warm Spare. There are 8 databases involved.
No problem on Production ... the AI files get swapped when they should ... and despatched to the Warm Spare server.
No problem in the Warm Spare applying the AI files -- works just fine.
No problem taking tape backups using probkup (with -norecover) on the Warm Spare server. And after taking a backup there is no problem continuing to apply the AI files.
HOWEVER ... if a backup from tape is restored to the Warm Spare it expects AI file #1 to be the next to be applied to it. That is not what was expected ... we thought we could continue to apply AI files in the same sequence as previously.
Is there any way to coerce Progress to NOT start back at #1?
If we have to have it the way it is -- it wrecks a substantial slice of our plans. (Where's the melting pot?)
Has anyone else found this to be a problem?