NSRCLONE(8)

NAME
nsrclone - NetWorker save set cloning command

SYNOPSIS

nsrclone
    [ -v ] [ -s server ] [ -b pool ] { -f file | volname... }

nsrclone
    [ -v ] [ -s server ] [ -b pool ] -S { -f file | ssid... }

nsrclone
    [ -v ] [ -s server ] [ -b pool ] -V { -f file | volid... }

and on HSM enabled server:

nsrclone
    [ -v ] [ -s server ] [ -b pool ] -c client -N saveset

DESCRIPTION
The nsrclone program makes new copies of existing save sets. These copies are indistinguishable from the original, except for the volume(s) storing the copies. The copies are placed on different media volumes, allowing for higher reliability than a single copy provides. The copies may be made onto any kind of media (for example, save sets on an 8mm tape may be copied to a set of optical disks). However, all media used as the destination of an nsrclone operation must be in a clone pool. See nsr_pool(8) for a description of the various pool types.

Although the command line parameters allow you to specify volume names or volume identifiers, nsrclone always copies complete save sets. Save sets that are only partially contained on a specified volume will be completely copied, so volumes may be requested during the cloning operation in addition to those specified on the command line. Note that nsrclone does not perform simple volume duplication, but rather, copies full save sets to a set of destination volumes in a given pool. If the first destination volume chosen cannot hold all of the save sets to be copied, another volume will be chosen. This allows you to use different kinds of media for each copy, allowing for variable sized volumes, such as tapes.

If you use the -c and -N options together, nsrclone will create a super-full clone for the given client save set. A super-full clone is a feature that is supported only with HSM (most useful on HSM enabled servers). It automatically creates a clone of the most recent complete full backup of the named client and save set, along with any HSM migration save sets referenced to by the backup. Super-full clones should be cloned to a volume from a pool of type Migration Clone. If no migration save sets are referenced by the most recent backup, only the full save set is cloned.

The nsrclone program, in conjunction with nsrmmd(8), guarantees that each save set will have at most one clone on a given volume. When you specify a volume name or identifier, the copy of the save sets on that volume are used as the source. When save sets are specified explicitly, those with existing multiple copies are automatically chosen (copies of save sets that exist on volumes in a jukebox are chosen over those that require operator intervention). You can also specify which copy (clone) of a save set to use as the source, (see the -S option,in the options section).

Cloning between storage nodes is accomplished by an nsrmmd(8) on the source node reading from a volume, and another nsrmmd(8) on the target node writing to a volume. The source node is determined by the location of a source volume, which is given by where the volume is currently mounted or by its "location" field if unmounted (see mmlocate(8)). The target node of a clone is determined by the "clone storage nodes" attribute of the storage node's client resource, the "clone storage nodes", or the "storage nodes" attribute of the server's client resource in decending priority. See nsr_storage_node(5) and nsr_client(5) for additional detail on how these attributes are used and on other storage node information.

OPTIONS

-b pool
    Specifies the media pool to which the destination clones should be sent. The pool may be any pool currently registered with nsrd(8) that has its status set to clone. The possible values can be viewed by selecting the Pools menu item from the Administration menu of nwadmin(8). If you omit this option, the cloned save sets are automatically sent to the Default Clone pool.

-c client
    Specifies a client whose save sets should be considered in the creation of a super-full clone. This option must always be specified in conjunction with the -N option.

-f file
    Instructs nsrclone to read the volume names, volume identifiers or save set identifiers from the file specified, instead of listing them on the command line. The values must be listed one per line in the input file. The file may be "-", in which case the values are read from standard input.

-N saveset
    Specifies which save set name is used to create a super-full clone. This option must always be specified in conjunction with the -c option.

-s server
    Specifes a NetWorker server to migrate save sets from. See nsr(8) for a description of server selection. The default is the current system.

-v  Enable verbose operation. In this mode, additional messages are displayed about the operation of nsrclone, such as save sets that cross volumes, or save set series expansions.

-S  Causes nsrclone to treat subsequent command line parameters as save set identifiers, not volume names. Save set identifiers are unsigned numbers. You can find out the save set identifier of a save set using the mminfo -v command (see mminfo(8)). The -S option is useful when you want to copy individual save sets from a volume or all save sets matching an mminfo query (see the examples below). The save set identifiers may also specify exactly which copy of a save set with multiple copies to use as the source. To specify exact copies, use the ssid/cloneid format for each save set identifier. In this case, the ssid and the cloneid are unsigned numbers, separated by a single slash (/). You can find out the cloneid for a particular copy by using the mminfo -S report, or a custom report.

-V  Causes nsrclone to treat subsequent command line parameters as volume identifiers, not volume names. Volume identifiers can be found using the mminfo -mv report, for example. This option can not be used in conjunction with the -S option.

EXAMPLES
Copy all save sets on the volume mars.001 to a volume in the Offsite Clone pool:
    nsrclone -b 'Offsite Clone' mars.001

Copy all complete save sets created during the previous weekend (recall that nsr_getdate(3) dates without time-of-day match midnight at the beginning of that day). Only complete save sets can be copied by nsrclone(8):
    nsrclone -S `mminfo -r ssid \
     -q '!incomplete,savetime>last saturday,savetime<last monday'`

Copy a specific clone of a specific save set:
    nsrclone -S 1538800517/770700786

SEE ALSO
nsr_getdate(3), nsr_pool(5), nsr_storage_node(5), mminfo(8), nsr(8), nsrd(8), nsrmmd(8), nwadmin(8).

DIAGNOSTICS
The exit status is zero if all of the requested save sets were cloned successfully, non-zero otherwise.

Several messages are printed signalling that nsrd(8) is unavailable for cloning data; these are self-explanatory. You may also see a message from the following list.

adding save set series which includes ssid
    If running in verbose mode, this message is printed when nsrclone notices that a requested save set is continued, requiring the entire series to be cloned (even if only part of the series was specified in the command line parameters).

Cannot contact media database
    The media database (and most likely other NetWorker services as well) on the named server is not answering queries. The server may need to be started, or if it was just started, it needs to finish its startup checks before answering queries.

cannot clone save set number, series is corrupt
    The given save set is part of a save set series (used for saving very large files or filesystems), but not all of the save sets in the series were found in the media database. This can happen if, for example, you relabel a tape that contains part of a save set series.

cannot clone backup and archive data together
    Archive and backup data is fundamentally different and cannot be cloned to the same pool. You need to run nsrclone twice, once to clone the backup save sets and once more for the archive save sets.

cannot open nsrclone session with server
    This message is printed when the server does not accept clone sessions.

cloning not supported; upgrade required
    Another enabler is required to use this feature.

cloning requires at least 2 devices
    Cloning requires at least one read/write device and one read-only or read/write device, since data is copied from one volume directly to another.

server does not support cloning
    The named server is not capable of cloning.

error, no valid clones of ssid number
    The listed save set exists, but cannot be cloned because there are no complete copies of the save set. The save set was either aborted or is in progress. Only complete save sets can be copied.

error, user username needs to be on administrator list
error, user username needs to be on archive users list
    Only NetWorker administrators are allowed to make clones of backup save sets. NetWorker administrators are listed in the NSR server resource, see nsr_service(5) for more information. For servers with archive capability, users listed in the NSR archive client's user list are allowed to clone archive save sets.

no complete, full backup of client:saveset
    During an attempt to create a super-full clone, nsrclone could not find a complete, full backup of the requested save set.

no complete save sets to clone
    Only complete save sets can be copied, and no complete save sets were found matching the requested command line parameters.

number is not a valid save set
    The given save set identifier is not valid. Two forms are understood: simple save set identifiers and those with a cloneid specified. Simple save sets are unsigned numbers. The save set with the cloneid form is specified as two unsigned numbers separated by a single slash (/).

pool is not a cloning pool
    The pool specified with the -b pool option is not a clone pool. You must always use a pool with a type of "Backup Clone" or "Archive Clone" for the -b option.

save set number does not exist
    The given save set (from a -S save set list) does not exist. Verify your save set identifiers using mminfo(8).

save set number crosses volumes; requesting additional volumes
    This message is printed in verbose mode when volume names or IDs were specified, but the given save set is only partially resident on the listed volumes. Since only complete save sets can be cloned, nsrclone automatically requests additional volumes.

save set clone number/cloneid does not exist
    A specific clone of a save set was specified, but that save set has no clones with that clone identifier. Verify your save set identifiers using mminfo(8).

volume name-or-number does not exist
    The given volume (either a volume name or a volume id specified in the -V option) does not exist in the media database.

waiting 30 seconds then retrying
    A temporary error occurred and nsrclone will automatically retry the request until the condition is cleared. For example, an error will occur if all devices are busy saving or recovering and nsrclone must wait for these devices become available.

Warning: No candidate migration save sets of client:saveset
    If you are using nsrclone to create a super-full clone, and the most recent full backup of the named client and save set does not refer to any migration save sets, this warning is printed as nsrclone begins cloning the full backup.