Target set definitions using the naming convention

Target set definitions can also be provided by using a naming convention on SAN Volume Controller and Storwize® family.

IBM® Storage Protect Snapshot supports using a naming convention, instead of a definition file, for target set definitions on SAN Volume Controller and Storwize family storage systems. IBM Storage Protect Snapshot determines the target volume names from the name of the target set, used for the current backup, and the name of the source volume.

Target sets are specified directly in the DEVICE_CLASS configuration section of the profile for example, TARGET_SETS 1 2 3. The names are generated from TARGET_SETS and are sequentially numbered, 1, 2, 3, 1, 2, and so on. When target sets are defined in the profile, the target set name must be unique in the entire profile. For example, you cannot have the TARGET_SETS parameter, set to t1 for more than one device class. The following example shows multiple device classes that are named in the DEVICE_CLASS configuration section of the profile:

>>> Device_Class SVC_01
.
.
TARGET_SETS t1 t2
.
.
<<<
>>> Device_Class SVC_02
.
.
TARGET_SETS t3 t4
.
.
<<<
>>> Device_Class SVC_03
.
.
TARGET_SETS t5 t6
.
.
<<<

A TARGET_NAMING rule is also specified to determine the name of the target volume from the name of the source. For example, TARGET_NAMING %SOURCE_bt%TARGETSET. If the application is stored on a volume named db_vol, the targets required by IBM Storage Protect Snapshot are db_vol_bt1, db_vol_bt2, and db_vol_bt3. These targets depend on the target set that is selected for the current backup.

>>> DEVICE_CLASS STANDARD
COPYSERVICES_HARDWARE_TYPE SVC 
COPYSERVICES_PRIMARY_SERVERNAME <hostname> 
TARGET_SETS 1 2 3
TARGET_NAMING %SOURCE_bt%TARGETSET
FLASHCOPY_TYPE NOCOPY
<<<

The given TARGET_SETS or TARGET_NAMING definition results in the following target volume names:

name of source volume_bt1
name of source volume_bt2
name of source volume_bt3