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.

To direct clones from all storage nodes to the same destination, leave the Clone Storage Nodes attribute blank for the Clients resources you configure for the storage nodes, and only configure the Backup server's Clone Storage Nodes attribute. This tactic provides a single source of control for clone destination.

The file index and media database entries for the save sets cloned to media on a remote device on a storage node still reside on the Backup server, which enforces the browse and retention policies in the same manner as for any cloned save sets that reside on the media in a device that is locally-attached to the server.