Kbase P122290: Should probkup -norecover be used for an AI-enabled database?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/12/2008 |
|
Status: Verified
GOAL:
Should probkup -norecover be used for an AI-enabled database?
GOAL:
Can probkup -norecover be used on a Source replication enabled database
GOAL:
Will AI files roll forward against a probkup taken with -norecover option
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge Replication
Progress 9.x
OpenEdge 10.x
FIX:
The only reason you would use the -norecover is to ensure that the BI file doesn't rollback before taking an offline backup.
Typically the -norecover option is used in situations where:
a.) A backup of the target database is taken so that you don't break being able to roll forward AI files
b.) You've hit BI file size limits so you restore to a structure that has more BI space somewhere
Behaviors associated with making use of the -norecover option:
Ensures that no ai switch will occur.
Does not perform crash recovery / BI roll back recovery is delayed until after the restore occurs and the database is started or accessed.
Note:
Using -norecover with probkup ONLINE is ignored, ie the AI switch still ensues as though the command option was not in use.
In terms of Fathom Replication therefore, don't use it. There really is no point. The restored database will not allow ai files to be rolled forward against it.
Simply take online or offline probkups as normal. Then restore and roll forward AI files from that point onwards (an AI switch is ensured on a probkup). The target database would have to be re-baselined once the source is restored and enabled.