SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

You can back up one or more table partitions, either implicitly, by backing up associated tables,
or explicitly, by using the PARTITION backup object specification:
BR> BACKUP $tape-drive, MX (TPART cat1.sch1.table1 PARTITION (part1)),
PARTONLY ON;
BR> BACKUP $tape-drive, MX (TPART cat1.sch1.table1 PARTITION (part1,
part2))
BR+>, PARTONLY ON;
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, see the Backup and Restore 2 Manual.)
You cannot use the PARTONLY option with the INDEXES INCLUDED option.
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).
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 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, see the Backup and Restore 2 Manual.
Sequence Generator
A sequence generator is automatically backed up when its associated catalog or schema is backed
up.
Using Backup and Restore 2 for SQL/MX Database Recovery 65