Backing up partitioned tables using IBM® Tivoli Space Manager Hierarchical Storage Management

The Tivoli® Space Manager Hierarchical Storage Manager (HSM) client program automatically migrates eligible files to secondary storage to maintain specific levels of free space on local file systems.

With table partitioning, table data is divided across multiple storage objects called data partitions. HSM supports the backup of individual data partitions to secondary storage.

When using SMS table spaces, each data partition range is represented as a file in the corresponding directory. Therefore, it is very easy to migrate individual ranges of data (data partitions) to secondary storage.

When using DMS table spaces, each container is represented as a file. In this case, infrequently accessed ranges should be stored in their own table space. When you issue a CREATE TABLE statement using the EVERY clause, use the NO CYCLE clause to ensure that the number of table spaces listed in the table level IN clause match the number of data partitions being created. This is demonstrated in the following example:

CREATE TABLE t1 (c INT) IN tbsp1, tbsp2, tbsp3 NO CYCLE
		PARTITION BY RANGE(c)
		(STARTING FROM 2 ENDING AT 6 EVERY 2);