Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

4. Stop all disk volumes used for OSS catalogs and OSS data files on the source system.
5. Use the BACKUP VOLUME mode option to backup the OSS catalog disk volume from the
source system.
6. Use the BACKUP VOLUME mode option to backup the OSS data file disk volumes from the
source system.
7. Use the RESTORE VOLUME mode option to restore the OSS catalog disk volume to the target
system.
8. Use the RESTORE VOLUME mode option to restore the OSS data file disk volumes to the target
system.
9. Restore any other files backed up earlier in this procedure.
10. Start the OSS Monitor. If necessary, use an OBEY file for the kernel subsystem SCF interface
to restore its configuration in the persistence monitor and OBEY files or RESTORE to restore
the configuration of the OSS environment.
11. Use RESTORE to restore the storage-pool files. The source and target system DEVICELABEL
values must match.
12. Restore the remainder of the OSS environment as described in “Restoring NonStop SQL/MP
Programs Using Backup/Restore Utilities (T9074)” (page 193) and “Restoring Security Data
Used For File Access” (page 193).
13. Start all filesets.
Restoring User Files
The following subsections describe:
• “Restoring NonStop SQL/MP Programs Using Backup/Restore Utilities (T9074)” (page 193)
• “Restoring Security Data Used For File Access” (page 193)
• “Restoring a pax Archive of OSS Files Directly From the Guardian Environment” (page 194)
• “Restoring a Compressed pax Archive of OSS Files From the Guardian File System” (page 194)
• “Restoring Files From a pax Archive to the Guardian File System” (page 194)
• “Restoring a pax Archive of Guardian Files From a Tape” (page 194)
• “Verifying a Restored OSS File Backup” (page 195)
To restore files using the pax utility, the fileset to be restored must first be configured and started
using the OSS Monitor.
Restoring NonStop SQL/MP Programs Using Backup/Restore Utilities (T9074)
When an OSS fileset is lost, there are orphan entries in surviving SQL/MP PROGRAMS and
USAGES tables. These entries are harmless.
If the OSS fileset is recovered using volume mode RESTORE and the original SQL catalog exists,
the orphaned entries again match existing, valid SQL programs. If the OSS fileset is not recovered
using volume mode RESTORE, then these SQL objects must be SQL-compiled to reregister them in
the PROGRAMS and USAGES table; the orphaned entries remain in the table.
Restoring Security Data Used For File Access
The security database files contain user ID aliases, file-sharing groups, and initial-directory
information. This user information can be reconstructed by one of the following methods:
• Use Safeguard OBEY files, previously created as described in “Backing Up the OSS
Environment Using a Version of Backup/Restore” (page 185)
• Use RESTORE on all of the Guardian files described in “Backing Up the OSS Environment
Using a Version of Backup/Restore” (page 185). This approach recovers passwords but at the
risk of using files corrupted by being changed during backup. To use RESTORE:
Backing Up and Restoring OSS Files 193