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

4. Backup and Restore 2.0 preserves OSS file access information. However, if you are using the
Backup and Restore utilities (T9074), you need to record all user ID information relevant to
OSS file access. You can do this in either of the following ways:
• Using Safeguard:
SAFECOM
DISPLAY AS COMMANDS ON
LOG OSSGRPS
INFO GROUP *
LOG OSSUSRS
INFO USER *.*
LOG OSSALIAS
INFO ALIAS *
LOG
Edit these log files to create OBEY files for Safeguard so that the attributes of each
file-sharing group, user ID, and user ID alias can be recreated if necessary.
• Using the T9074 Backup and Restore utilities (if the node you are backing up uses the
same RVU of Safeguard as the node you will be restoring). The relevant user ID information
is kept in the following files:
$SYSTEM.SYSTEM.USERID
$SYSTEM.SYSTEM.USERIDAK
$SYSTEM.SAFE.LUSERID
$SYSTEM.SAFE.LUSERIDG
Use the OPEN option when doing the BACKUP operation. Ensure that no Safeguard
changes are made while BACKUP is running.
Backing Up User Files
You should back up and restore all Guardian files and SQL data tables used by OSS applications
using normal procedures for Guardian data:
• Recover audited files and tables using TMF; nonaudited files and tables
• Backup and recover unaudited files and tables using a version of Backup/Restore
Use Backup and Restore 2.0 BRCOM commands to back up SQL/MX and OSS files. Use Backup
and Restore utility (T9074) commands to backup SQL/MP and Enscribe files.
Although several OSS filesets can be simultaneously backed up—assuming that your system has
more than one storage device—each fileset backup is a separate task.
Consolidate Changing OSS Files
To make backup easier, organize your filesets so that changing data files are on filesets that are
regularly backed up while static files are on filesets that are backed up only occasionally. You can
simplify backup by copying isolated, changing files from filesets that are not periodically backed
up to those that are, just before you perform a backup. This action allows the dynamic files to be
backed up without requiring an entire file-system backup. You could write a shell script to do this.
For information about shell scripts, see the Open System Services User’s Guide.
You can use the find command to produce a list of files that must be backed up and then pipe
this list to the backup command pax. For example, to back up all user files that were modified in
the past week onto the tape using the tape device $TAPE, use a command such as:
find /user/* -mtime -7 | pax -w -f /G/TAPE
where /user contains all working directories.
186 Managing OSS Files