|
|
|
|
|
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.
|
|
|
|
|
|
|
|
When you clone a volume, the volume is not simply duplicated. Each save set on the
volume is reproduced completely, which could mean that more or less space is used
on the clone volume than on the source volume.
You might prefer to make exact copies (duplicates) of Backup volumes to provide
additional disaster recovery protection. This approach, which in UNIX relies on the
tcopycommand, is not recommended but might serve a specific environment
adequately. If you rely on an exact copy command, you must first ensure that the
destination volume can hold the number of bytes that are contained in the source
Backup volume. In addition, be aware that Backup would have no knowledge of the
duplicated volume since the volume is not entered into the server's media database.
If you enabled automated media management and you leave the volume in an
autochanger managed by Backup, the volume may be considered eligible for
relabeling and use during a scheduled backup, because it does not have a valid
Backup label.
Similarly, it is possible to make an exact copy of an archive volume. However, the
annotation that is associated with each archive save set is information that is stored
in the Backup server's media database, not on the volume itself. Therefore, a
duplicate volume of the archived save set does not include the annotation. If the
entry of the original archive save set is removed from the media database, the
annotation that describes it is also removed.
|
|
|
|
|
|
|
The clone operation does not insert entries into the client file index. Cloned save sets
are only tracked through the media database. During a clone operation, the location
of a cloned save set is added to the existing save set entry in the media database.
That is, each save set clone shares the same ssid as the source save set. All
characteristics that are true for the source save set are also true for the clone save set.
If the source save sets are still browsable, the clone status is also browsable. If the
source save sets have passed their browse policies, the clone status is recoverable.
|
|
