SQL/MX 3.1 Installation and Management Guide (H06.23+, J06.12+)

Planning Database Security and Recovery
HP NonStop SQL/MX Release 3.1 Installation and Management Guide—663852-001
5-33
SQL/MX Objects That Are Backed Up Implicitly
You cannot use the PARTONLY option with the INDEXES INCLUDED option.
Backing Up Indices and Index Partitions
When you back up an index, all its subordinate objects (for example, partitions) are
also backed up unless they are specifically excluded.
To back up one or more indices, take a backup of their associated schemas or catalogs
implicitly or specify the MX INDEX or MX IND backup object explicitly:
BR> BACKUP $tape-drive, MX INDEX cat1.sch1.index1;
BR> BACKUP $tape-drive, MX INDEX
cat1.sch1.index1,cat1.sch1.index2;
To back up one or more index partitions, take a backup of their associated indices
implicitly or use the PARTITION backup object specification explicitly
BR> BACKUP $tape-drive, MX (IPART cat1.sch1.index1
PARTITION(part1)), PARTONLY ON;
BR> BACKUP $tape-drive, MX (IPART cat1.sch1.index1
PARTITION(part1, part2))
BR+>, PARTONLY ON;
SQL/MX Objects That Are Backed Up Implicitly
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).