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...  }

DESCRIPTION

The nsrclone command is used by system administrators to make 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 that will be used as the destination of a 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 one 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 one to use different kinds of media for each copy, and allows for variable sized volumes, such as tapes.

The nsrclone command, in cooperation with nsrmmd(8), guarantees that each save set will have at most one clone on a given volume.  When a volume name or identifier is specified, the copy of the save sets on that volume are used as the source.  When save sets are specified explicitly, those with multiple copies already are automatically chosen (generally, copies of save sets on volumes in a jukebox are chosen over those that require human intervention).  You can also specify exactly which copy (clone) of a save set to use as the source; see the −S option, below. 

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 networker(8).  If this option is omitted, the cloned save sets are automatically assigned to the Default Clone pool. 

−f file Read the volume names, volume identifiers or save set identifiers from the named file 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. 

−s server
Clones save sets stored on the NetWorker system on server. 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 to copy all the save sets matching some mminfo query.  See the examples below for one possible such use.  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 number, separated by a single slash (/) character.  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 via the mminfo -mv report, for example.  This option may not be used with −S. 

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 save sets created during the previous weekend (recall that getdate(3) dates without time-of-day match midnight at the beginning of that day):

nsrclone -S ‘mminfo −r ssid \
-q ’savetime>last saturday,savetime<last monday’‘

Copy a specific clone of a specific save set:

nsrclone -S 1538800517/770700786

SEE ALSO

getdate(3), mminfo(8), networker(8), nsr(8), nsr_pool(5), nsrd(8), nsrmmd(8)

DIAGNOSTICS

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

Several messages are printed which denote a temporary unavailability if the nsrd(8) for cloning data.  These are self-explanatory.  In addition, you may see a message from the following list. 

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.

cloning requires at least 2 active devices
The server has only one active device. You must increase this to at least 2 before cloning, since cloning copies data from one volume directly to another volume.

server does not support cloning
The named server has no capability for cloning.

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 additional information.  In addition, for servers with archive capability, users listed in the NSR archive client’s user list are allowed to clone archive save sets. 

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. 

waiting 30 seconds then retrying
A well-known temporary error occurred and nsrclone will automatically retry its request until the condition is cleared.  An example of such an error is that all of the active devices may be busy saving or recovering, so nsrclone cannot use those devices and must wait for two of them to become free. 

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 clone number/cloneid does not exist
You specified a specific clone of a save set, but that save save has no clones with that clone identifier. Verify your save set identifiers using mminfo(8). 

cannot clone save set number, series is currupt
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. One way this can happen is if 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.

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 set are unsigned numbers. The save set with cloneid form is specified as two unsigned numbers separated by a single slash (/) character.

volume name-or-number does not exist
The given volume (either a volume name of a volid, if you specified the −V option) does not exist in the media database. 

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

NetWorker 4.1.2  —  Last change: May 1995