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

1. Restore the security database files using the RESTORE MAP NAMES and OPEN options
as new files in a temporary location (subvolume).
2. Use the File Utility Program (FUP) to rename the old security database files and to move
the restored copies to the correct subvolume.
3. Stop and restart Safeguard and all Expand lines to close the old security database files
and open the restored ones.
Restoring a pax Archive of OSS Files Directly From the Guardian Environment
The PINSTALL utility that runs in the Guardian environment can restore a pax archive backup made
as described in “Creating a pax Backup of OSS Files in the Guardian File System” (page 190)
directly into the OSS file system.
At a TACL prompt, use PINSTALL to restore the backup to the OSS file system. For example, to
restore the $OSS.BACKUP.PAXHOME pax archive file, you would enter the following command:
PINSTALL -pe -rvf /G/oss/backup/paxhome
Restoring a Compressed pax Archive of OSS Files From the Guardian File System
The compressed pax archive made as described in “Creating a pax Backup of OSS Files in the
Guardian File System” (page 190) can be restored directly into the OSS file system using the following
OSS shell command:
zcat < /G/oss/backup/paxhome | pax -rv -pe
The zcat command uncompresses the file and sends the result to the pax command, where the
-pe flags preserve the file permissions.
Restoring Files From a pax Archive to the Guardian File System
Because of the syntactic differences between the names of Guardian and OSS files, the following
behaviors can occur when a pax archive member is restored to a Guardian file system:
• An OSS filename might contain characters that are illegal in Guardian filenames. As a result,
the archive member cannot be created on the Guardian target and the restore operation fails.
For example, if the archived file were named ca$h/.profile, then an attempt to restore it
to /G/oss fails because of the embedded dollar sign character.
• In the name-transformation process, OSS names that are longer than eight characters are
truncated to the first valid eight characters. For example, the OSS pathname abcde.fghi is
transformed to the Guardian name ABCDEFGH. This can cause confusion and make
identification of files difficult. Filenames that are similar in one environment might be transformed
to the same filename in the other environment, which might result in the overwriting of previously
restored files.
Guardian files can be specified as pathnames in a /G directory. Files can be restored within /G
directories, but existing Guardian files are overwritten only if you use the -W clobber flag. The
Guardian file attributes are not preserved.
Guardian files are restored as unstructured Guardian files with the file code 0. Only Guardian
files with file codes that are supported by the OSS environment are processed.
Restoring a pax Archive of Guardian Files From a Tape
To restore files from the tape that is mounted on $tape to the Guardian target $vol.subvol, extracting
only files whose names end with .c and overwriting any existing Guardian files with the same
name, enter the following OSS shell commands:
cd /G/vol/subvol
pax -rv -f /G/tape -W clobber *.c
The cd command selects the Guardian subvolume that you want to restore. The pax command
has the following form:
194 Managing OSS Files