Open System Services Management and Operations Guide (G06.25+, H06.03+)

Managing OSS Files
Open System Services Management and Operations Guide—527191-002
6-24
Restoring User Files
Restoring User Files
The following subsections describe:
•
Restoring NonStop SQL/MP Programs Using Backup/Restore Utilities (T9074) on
page 6-24
•
Restoring Security Data Used For File Access on page 6-24
•
Restoring a pax Archive of OSS Files Directly From the Guardian Environment on
page 6-25
•
Restoring a Compressed pax Archive of OSS Files From the Guardian File System
on page 6-25
•
Restoring Files From a pax Archive to the Guardian File System on page 6-25
•
Restoring a pax Archive of Guardian Files From a Tape on page 6-26
•
Verifying a Restored OSS File Backup on page 6-27
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 on page 6-14
•
Use RESTORE on all of the Guardian files described in Backing Up the OSS
Environment Using a Version of Backup/Restore on page 6-14. This approach
recovers passwords but at the risk of using files corrupted by being changed during
backup. To use RESTORE:
1. Restore the security database files using the RESTORE MAP NAMES and
OPEN options as new files in a temporary location (subvolume).