Multi-partition DB2 target set definition file

As a result, the contents of the target set definition file is separated into multiple sections. One section is used for each partition, as shown in this example:

>>> TARGET_SET SET_1 
            # IBM Storage Protect Snapshot determines a target for every source
>>> PARTITION NODE0000
TARGET_VOLUME 40913158
TARGET_VOLUME 40A13158
<<<
>>> PARTITION NODE0001
TARGET_VOLUME 40B13158
TARGET_VOLUME 50913158
TARGET_VOLUME 50A13158
TARGET_VOLUME 50B13158
TARGET_VOLUME 51713158
<<<
>>> PARTITION NODE0002
TARGET_VOLUME 51813158
TARGET_VOLUME 52113158
TARGET_VOLUME 52313158
<<<
<<<

A single backup server environment (for a multi-partition DB2 database) can be distributed across multiple servers. In this situation, make sure that the target volumes in the target set definition file are assigned to the correct host. For best results, assign all target volumes in the target set definition file (and that are associated with the same partition) to the same host. In environments where multiple partitions are on the same volume group (volume sharing), target set definition files need to specify certain values. For more information, see Manage target volumes files for your storage system.