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-33
SQL/MX Objects That Are Backed Up Implicitly
You can use the BACKUP job option PARTONLY only when a database has
partitioned tables and indexes. PARTONLY enables you to back up and restore
individual components of a partitioned database. (For more information about this and
other job options, see the Backup and Restore 2 Manual.)
You cannot use the PARTONLY option with the INDEXES INCLUDED option.
SQL/MX Objects That Are Backed Up Implicitly
Indexes and Index Partitions
Indexes cannot be backed up explicitly. To back up all the indexes and index partitions
in a catalog, schema, or table, specify that catalog, schema, or table:
BR> BACKUP $tape-drive, MX TABLE cat1.sch1.table1;
To exclude the indexes and index partitions from the backup, specify the INDEXES
EXCLUDED option:
BR> BACKUP $tape-drive, MX TABLE cat1.sch1.table1, INDEXES
EXCLUDED;
For more information about backing up indexes and index partitions, see the Backup
and Restore 2 Manual.
Constraints
PRIMARY KEY, NOT NULL, UNIQUE, CHECK, and REFERENTIAL INTEGRITY
constraints are automatically backed up when their associated tables are backed up.
You can choose not to have table constraints backed up by using the CONSTRAINTS
EXCLUDED backup job option. Using CONTRAINTS EXCLUDED, however, does not
prevent the backup of PRIMARY KEY constraints that are NOT DROPPABLE or the
backup of NOT NULL constraints.
For more information about backing up constraints, see the Backup and Restore 2
Manual.
Caution. Use caution when using PARTONLY in Backup and Restore 2 operations for
partitioned tables. It is possible to make the primary and secondary partitions of a table
inconsistent, both with each other and with indexes (for example, by performing DML
operations on only one of two backed up partitions before you restore both).