Hi there. In this video, we'll take a look at an introduction to save set cloning in networker. These steps are for users using networker version nine and onwards, this video will help backup administrators new to networker, familiarize themselves with networker cloning terminology and design concepts in networker cloning is the term we use when making copies of backup data.
The definition of backup data is referred to as a safe set. Each safe set copies an instance including the original safe sets are backed up to volumes which must be labeled into a pool and logically mounted onto a device to be used. Cloning is used to replicate a safe set from any media or device type to any other. A safe set backup may only be performed to a volume in a backup type pool volume. A safe set may only be cloned to a clone type pool volume.
When multiple volumes may be labeled into the same pool, each individual volume may only be labeled for a single pool. A policy is a logical container of one or more workflows, workflows are executed against one or more groups applying to these a series of actions in succession. A group can be used to define a collection of several different things such as clients for backup or safe sets for cloning.
Use a client group for a workflow which backs up and then clones the successful safe sets, use a safe set queried group for a workflow, which clones existing save sets on schedule. When cloning a network or storage node must be selected for both operations which are the reading of the source safe set from its volume and the writing of the clone to the destination volume. These are each known as the source storage node and the destination storage node.
These may be the same storage nodes and either or both may be the network or server itself. The networker management console can be used to create configure start stop or edit any networker clone operation. The NSR clone command can also be used for these purposes. Although it is primarily used for ad hoc clone operations or within scripts, a safe set receives the same numeric safe set id as its media database identifier for all its instances.
A clone id is a secondary numeric identifier which helps to distinguish a specific instance of the safe set. For example, a safe set backup of the C drive must be written first to a backup pool and volume. It may then be cloned to one or more clone pools and volumes. All instances will share the same SS ID as the data is identical but each will have a unique clone ID. You can therefore refer to all instances of the safe set by querying its global SS ID. There are many ways to clone your data depending on your needs.
You can clone immediately after scheduled backup or clone one or more safe sets on demand. You can clone by volume or schedule clone operations for safe sets, matching specific criteria such as pool backup time or current number of copies you can clone from any media type to any other, which may have different implications. Cloning to tape is a tested long term storage option. Cloning between a pair of data domains is popular due to its exceptional speeds and network efficiency. Cloning to the cloud using a solution like cloud boost is also increasingly common for many customers. Any clone operation can optionally delete the source data as well effectively moving the safe set from one volume to another.
Some important information to be aware of with regards to cloning in theory and practice no more than one instance of the same save set may exist on any given volume cloning may only use a clone type pool volume as a destination clones may be tracked using the NMC gooey or the mm info command. It is important to understand your desired volume pool device and storage node for both source and destination.
Thanks for watching.
