Kbase P133408: 6774 and 6776 errors when restoring incremental backups on hot / warm standby database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
18/07/2008 |
|
Status: Unverified
SYMPTOM(s):
Restoring incremental backups against a hot / warm standby database gives error 6776 and 6774.
Last incremental restore was number <restore number> on <date>. (6776)
Incremental restore out of sequence on <database name>. WARNING: Applying this incremental backup could damage your database. (6774)
WARNING: This incremental was done for full backup dated <date>, (3747)
and last full restored to this database is dated <date>. (3748)
Restore failed. (1618)
!!! ERROR - Database restore utility FAILED !!! (8564)
FACT(s) (Environment):
Using what is referred to in the industry as "poor mans version of replication"
Using probkup command to backup source database.
probkup with -norecover option does not change the behavior
Performing incremental backups against a source database to be applied to a hot / warm standby database on another machine.
prorest command is used to restore backup of database on source machine to a hot / warm standby database on another machine.
All Supported Operating Systems
Progress/OpenEdge Versions
CHANGE:
Progress probkup command was used to take a backup of the target (hot / warm standby) database to replicate the hot / warm standby to another machine.
CAUSE:
The probkup command when performed against the hot / warm standby database changes the date of the last backup. It also resets the value associated with incremental backups.
FIX:
1. Use an Operating System (OS) copy command or other non-Progress related command to copy the hot / warm standby database to another machine instead of the probkup command. or
2. Restore original Progress backup taken from source database to the secondary hot / warm standby machine and apply incrementals to get to the same point as the current hot / warm standby database.