The only reason you would use the -norecover option, 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.) An offline backup of the target database is taken so that you don't break being able to continue applying AI files with RFUTIL -C roll forward
b.) You've hit BI file size limits so you restore to a new 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.
Using -norecover with probkup ONLINE is ignored. The AI switch still ensues as though the command option was not in use.
In terms of OpenEdge Replication there is no need to use the -norecover switch:
- Since OpenEdge 10.1C offline target PROBKUP no longer needs to use the -norecover switch when this target will be restarted after the offline probkup to assure synchronisation with the current source database.
- If this target database has ai enabled, an offline backup volume created with the -norecover switch, cannot be used to roll forward ai files once restored. An online or offline target probkup is needed, which assures the ai switch can be used to apply target ai files.
A rare use-case is to re-establish the source production database from online replication target backup volumes & roll forward target ai files. Then re-baseline a new target database once the source is restored and enabled as a replication source.
