06.11.2014 Views

HP Archive Backup System for OpenVMS Guide to Operations

HP Archive Backup System for OpenVMS Guide to Operations

HP Archive Backup System for OpenVMS Guide to Operations

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Preparing For Disaster Recovery<br />

7.1 Disaster Recovery <strong>for</strong> <strong>OpenVMS</strong> <strong>System</strong>s<br />

7.1.3 <strong>Backup</strong> of ABS$ROOT<br />

Backing up ABS$ROOT with ABS will always find the ABS log files open <strong>for</strong> write because a<br />

save request always has a catalog file open <strong>for</strong> write. Not all catalog files might be accessible<br />

through ABS$ROOT. For example if you have created a search list <strong>for</strong> ABS$CATALOG and<br />

extensions <strong>to</strong> ABS$CATALOG point <strong>to</strong> other direc<strong>to</strong>ries and/or disk devices.<br />

If ABS$ROOT is not located on your system disk or you want a separate save operation, you can<br />

use a separate SAVE object like this:<br />

Example 7–3 Save Object <strong>for</strong> Disaster Recovery of ABS$ROOT<br />

Save: DISASTER_RECOVERY<br />

Description:<br />

Access Control: BONFYR::ABS (READ, WRITE, EXECUTE, DELETE, SET,<br />

SHOW,<br />

CONTROL)<br />

Owner: BONFYR::ABS<br />

<strong>Archive</strong>: DISASTER_RECOVERY<br />

Base Date: NONE<br />

Delete Interval: NONE<br />

Environment: DISASTER_RECOVERY_ENV<br />

Epilogue: @ABS$SYSTEM:ABS$DISASTER_RECOVERY EPILOG<br />

Execution Nodes: BONFYR<br />

Explicit Interval:<br />

Frequency: DAILY<br />

Groups:<br />

Incremental: NO<br />

Job Number: 0<br />

Prologue: @ABS$SYSTEM:ABS$DISASTER_RECOVERY PROLOG<br />

Schedule: DISASTER_RECOVERY_SAVE_SCHED<br />

Sequence Option: SEQUENTIAL<br />

Skip Time: NONE<br />

Start Date: NONE<br />

Transaction Status:<br />

Selections: DISASTER_RECOVERY_SAVE_SEL_DEF<br />

Default Selection -<br />

- Data Select Type: VMS_FILES<br />

- Include: ABSS$ROOT:[000000...]*.*;*,<br />

- Exclude: [*...]COORD_CLEANUP.DAT;*,[*...]*.LOG;<br />

- Source Node:<br />

If this object does not exist on your system run the ABS database initialization program:<br />

$ RUN SYS$SYSTEM:ABS$DB_INIT<br />

This program adds all the missing default ABS objects <strong>to</strong> the MDMS database.<br />

This save request excludes all the files open <strong>for</strong> write by ABS like the current logfile and the<br />

database file used by the coordina<strong>to</strong>r cleanup process (“ABS$COORD_CLEAN”). There should<br />

not be any error message in the save log file.<br />

You have <strong>to</strong> make sure that you use the DISASTER_RECOVERY archived with an empty catalog<br />

name defined. The disaster recovery archive is the only archive which allows no catalog<br />

name. Otherwise you get open and verify errors <strong>for</strong> the catalog being used.<br />

If you have an extended ABS$CATALOG search list, then you have <strong>to</strong> include the extra entries<br />

in the include specification as well. By default the catalog subdirec<strong>to</strong>ry is included under<br />

ABS$ROOT.<br />

If you want, you can combine the save of the MDMS$ROOT and the ABS$ROOT in<strong>to</strong> one save<br />

object.<br />

7-4 Preparing For Disaster Recovery

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!