Backup and Restore 2 Manual
BRCOM BACKUP Command
Backup and Restore 2 Manual—522696-019
6-5
Summary of Backing Up OSS or SQL/MX Files
SG_TABLE, if the table contains an IDENTITY column.
Backing up an index includes:
All index partitions.
Backing up individual index partitions includes the partition data only when you
specify the PARTONLY job option.
You cannot directly specify a constraint in a BACKUP command. To back up a
constraint, you must back up the table that contains the constraint. The constraints
that are backed up varies depending on whether you specify CONSTRAINTS
INCLUDED or CONSTRAINTS EXCLUDED.
Backing Up the Restricted-Access Fileset
To back up a restricted-access fileset, ensure that:
The user is the file owner or a member of the SECURITY-OSS-ADMINISTRATOR
security group.
The PRIVSOARFOPEN file privilege is set on the BR2DS, BR2ODS, BR2DMA,
and BR2ODMA executable files. For information on how to set the file privileges on
executable files, see Configuring Backup and Restore 2 on page 3-1.
Backing Up the Unrestricted Fileset
An unrestricted fileset can be backed up by the super ID, file owner, or any user who
has sufficient permissions on the file.
Members of the SECURITY-OSS-ADMINISTRATOR security group can back up files in
an unrestricted fileset only if the files have the required permissions set.
Note. IDENTITY column feature is supported only in SQL/MX 3.1 versions and above.
Note. The super ID cannot back up files or directories from the restricted-access fileset if
the super ID:
Is not the owner of the file, or
Does not have sufficient file permissions on the file or the group to which the file
belongs
Note.
Only members of the SECURITY-PRV-ADMINISTRATOR security group can set or
remove restrictions on the restricted-access fileset. For more information, see the
Security Management Guide
.
The restricted-access fileset attribute and the SECURITY-PRV-ADMINISTRATOR
security group are supported only on systems running J06.11 and later J-series RVUs
and H06.22 and later H-series RVUs.