When you specify that a particular volume be cloned, the specified volume as the source data.

Backup uses the save sets on

When you specify a clone of a particular save set, Backup determines whether the save set already has a clone. If multiple clones of a save set exist, clones of save sets on volumes in an autochanger are generally selected as the source data, rather than a volume that requires human intervention to mount. Command line options enable you to specify the precise save set clone to use as the source, if you want. If you execute a clone operation manually, no completion report is generated. Messages generated by the nsrcloneprogram are displayed in a message window in the administration program's GUI and are also logged to the /nsr/logs/messages Backup message file.

Clone Storage Node Affinity

The link between a client's resource of a storage node and a list of available storage nodes to receive cloned save sets from the storage node client is called "clone storage node affinity." Data is cloned from media that contains the original save sets to media on the specified clone storage node. You define clone storage node affinity in the Clone Storage Nodes attribute, which is found in the Clients resource of a storage node. When you make a change to the Clone Storage Nodes attribute in the Client resource for a storage node client, the changed value is propagated to any additional Clients resources configured for that storage node client. The Clone Storage Nodes attribute allows you to specify a different network interface for storage nodes that perform cloning operations than the network interface you specify for the storage node's remote device.
The server utilizes the exact hostname you specify in the Clone Storage Nodes attribute, instead of using the hostname prefix for the remote device name configured in the Devices resource.
When a volume is being cloned, the Backup server checks the value of the Clone Storage Nodes attribute for that storage node client. If the Clone Storage Nodes attribute has a null value, then the value listed in the server's Clone Storage Nodes attribute is used. If that list also contains a null value, then the server's Storage Nodes attribute is used.
Compatibility is maintained with the existing clone function which follows the server's Storage Node attribute.
To independently direct clones from each storage node, add the hostname of the storage node you want to receive the directed clones to the Clone Storage Nodes attribute in the Client resource configured for the storage node. The first entry made on the list that has a functional, enabled device is selected to receive the cloned data from the storage node.

Chapter 4

Device and Media Management

81