SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Planning Database Security and Recovery
HP NonStop SQL/MX Installation and Management Guide—523723-004
5-34
SQL/MX Objects That Are Not Restored by BRCOM
SQL/MX Objects That Are Not Restored by BRCOM
You cannot use Backup and Restore 2 to restore these SQL/MX objects:
•
GRANT and REVOKE privileges
•
Referential integrity constraints
•
SPJs
•
Triggers
•
Views
However, except for GRANT and REVOKE privileges, you can capture the DDL for the
CREATE statements executed for these objects and use this information to manually
re-create these objects after a Restore operation. For more information, see Using the
RESTORE SHOWDDL ON Option to Re-Create Objects on page 5-36. For information
about restoring privileges, see Example: Recovering Table Privileges on page 12-11.
Other Restrictions on Backup and Restore 2 Operations
These Backup operations are not currently supported:
•
Parallel BACKUP
•
BACKCOPY or parallel BACKCOPY
It is important to distinguish between multiple backup jobs, which are supported, and
parallel BACKUP of the type where two identical tapes are written simultaneously,
which is not supported.
To back up two copies of the data, use the BACKUP command twice rather than using
the BACKCOPY or parallel BACKUP commands. To back up three copies of the data,
use the BACKUP command three times. For more information about these restrictions,
see the Backup and Restore 2 Manual.
Other restrictions include:
•
You cannot currently BACKUP or RESTORE SQL/MX, SQL/MP, or Enscribe
objects to the same tape set. However, you can issue a single command to back
up all objects.
•
If a failure occurs, a BACKUP operation cannot be automatically restarted.
•
Currently, there is no support for media catalog.