|
|
|
|
|
Cloning is a process of reproducing complete save sets from a storage volume to a
clone volume. You can clone save set data from backups, archives, or migration. You
can clone save sets automatically (as part of a backup, archive, or migration
operation) or manually at another time.
Use cloning for higher reliability or convenience. For example, you can store clones
offsite, send your data to another location, or verify backed-up data.
The cloning operation happens in two steps: first, Backup recovers data from the
source volume. Then, Backup writes the data to a clone volume (a volume from a
pool of type "clone"). Cloning requires at least two active devices, because one is
required for reading the source volume and one is required for writing the new,
cloned data. During cloning, the reproduction of data is from source volume to clone
volume. Cloning does not involve data stored on the clients or server. Backup allows
only one clone of a save set per volume. Therefore, if you specify three clones of a
save set, each is written to a separate volume.
Automatic cloning (that is, cloning associated with a scheduled group backup
operation) is performed after all backup operations are complete. The savegroup
completion report that is issued after a scheduled backup also includes a report of
the success or failure of the cloning operation for each save set.
The location of the devices where the clone data is written is determined by the list
in the Storage Nodes attribute in the Clients resource for the Backup server. You can
add or remove the names of storage nodes and the Backup server at any time, but
you cannot have a different list of storage nodes to receive clone data than to receive
backup data.
If you want to perform cloning long after a group has finished, you must do the
cloning manually, volume by volume, or from the command line using a script in
combination with a batch file. If you execute cloning manually, no report is
generated.
When you clone data, different capacities of storage media may mean that more or
fewer clone volumes are required. The cloning operation leaves traceable
information entries in both the client file index and the media database. The
capability to track cloned data distinguishes cloning from an operating system or
hardware device copy operation.
To initiate cloning for a complete scheduled backup operation, enable cloning as part
of the Group configuration. To clone individual save sets or clone single storage
volumes, use the Save Set Clone or Volume Clone windows in the nwadminGUI, or
the nsrcloneprogram from the command line.
|
|
