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

Backing Up and Restoring OSS Files
This subsection describes the tasks for backing up and restoring the OSS environment and user
files on your system.
OSS files can be backed up with the OSS pax command or the BRCOM interface for Backup and
Restore 2.0. An entire OSS fileset can be backed up by using its mount point as the current directory
when running either utility.
NOTE: To back up files in a restricted-access fileset:
• The executable files of the backup software must have the PRIVSOARFOPEN file privilege.
• The backup software must be started by a member of the Safeguard
SECURITY-OSS-ADMINISTRATOR (SOA) group.
For an example of enabling the Backup and Restore 2 product to access files in restricted-access
filesets, see “Backup and Restore 2 Product and Restricted-Access Filesets” (page 192).
System administrators familiar with Guardian tools can use Backup and Restore 2.0 for almost all
archiving tasks. Administrators more familiar with UNIX can use pax; however, the pax utility has
several restrictions:
• For H06.06 and later H-series RVUs and for J-series RVUs,a pax archive has a file size limit
of 8 gigabytes. For earlier RVUs, a pax archive has the same file size limit as other OSS files
(approximately 2 gigabytes). These limits might prevent complete backup of a large fileset or
directory tree.
• The pax utility does not support labeled tapes and imposes requirements for unlabeled tapes.
• The pax utility does not support filenames longer than 100 characters in archives using its
default USTAR format.
The pax utility can be used when any of the following conditions exists:
• The system that will be restored (target system) might not have the same node name or node
number as the system being backed up (source system).
• The operating system release version update (RVU) of the target system might not be the same
as that of the source system.
• The disk volume names of the target system might not be the same as those on the source
system. (The storage-pool files and any OBEY files used on the source system will still need to
be modified to be used on the target system.)
NOTE: Beginning with the J06.14 and H06.25 RVUs, the tar, gzip, gunzip, and bzip2
Open Source tools are available; however, the file formats of various Guardian file types are not
guaranteed to be retained by these tools. For details about viewing the reference pages of these
Open Source commands, see “Viewing OSS Core Utilities Reference Pages” (page 244).
Considerations
For all backup activities described in this guide, the pax utility must be run at a time when no
updates or changes are being made to the OSS files that are being saved.
Multiple copies of pax output from a backup activity should be saved in case of media failure.
You cannot use tape libraries for an OSS backup from the OSS environment.
Use of Storage Management Foundation (SMF) logical volumes for an OSS backup from the OSS
environment is supported only on systems running either J06.15 and later J-series RVUs or H06.26
and later H-series RVUs. For details of creating an OSS backup to SMF logical volumes, see the
HP NonStop Storage Management Foundation User’s Guide.
You cannot perform remote backups of OSS files, directories, or file systems directly. For information
about remote backups, see “Backing Up OSS Files to Other Expand Nodes” (page 192).
Backing Up and Restoring OSS Files 183