Kbase P24021: How to use -norecover parameter with probkup
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/12/2008 |
|
Status: Verified
GOAL:
How to use -norecover parameter with probkup
GOAL:
What does the -norecover parameter do when issued with a probkup?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
The -norecover parameter was intended to be used in situations where mirrored drives are split for the purpose of creating a database to serve as a Hot Spare to which AI files are to be applied.
Once the split has occurred and the .lk file is removed from the fractured database it is ready for use as a hot spare, however, there is no Progress backup of the database and there should be one for safety sake.
To do this run:
probkup -norecover <dbname> <device-name>
The -norecover parameter will prevent the BI file from going through crash recovery (BI truncation), and will not cause an AI switch. Either of these actions would break the Hot Spare prohibiting it from having AI files applied to it.
The -norecover parameter is used with an offline backup only and is not a valid parameter for an online backup.
An online backup when presented with the -norecover option will proceed without error. However, it will ignore the parameter and cause an AI switch.