EMC Legato NetWorker Commands Reference

nsrclone

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  vol-
       ume(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(1) 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  begin  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.  Conversely, save sets residing on
       the specified volumes that begin elsewhere are not cloned.

       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  vari-
       able 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 migra-
       tion 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(1), 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  explic-
       itly,  those  with  existing  multiple  copies are automatically chosen
       (copies of save sets that exist on volumes in a jukebox are chosen over
       rently  mounted  or  by  its  "location"  field if unmounted (see 
       mmlocate(1)).  The target node of a clone is determined by the "clone stor-
       age  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   descending   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(1)  that  has its status set to clone.  The possible values
              can be viewed by selecting the Pools menu item from the Adminis-
              tration menu of nwadmin(1).  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.  The cloning  operation
              begins only when all the entries in the file are correctly spec-
              ified; even if one of the entries is invalid, the operation will
              not continue and the corresponding error is reported.

       -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
              Specifies  a  NetWorker  server  to migrate save sets from.  See
              nsr(1) 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, names of cloned volumes, or save set series
              expansions.  If concurrent nsrclone operations are performed  on
              the  same  savesets,  it  is possible for the volume names to be
              inaccurate. In that case nsrclone will issue a  warning.  Please
              see DIAGNOSTICS for the exact warning message.

       -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(1)).   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
              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 that begin 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 weekend. If no time of
       day is specified with the date, nsr_getdate (3) uses  midnight  as  the
       start  time for copying all the complete save sets.  Only complete save
       sets can be copied by nsrclone(1):
              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(1), nsr(1),
       nsrd(1), nsrmmd(1), nwadmin(1).

DIAGNOSTICS

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

       Several messages are printed signaling that nsrd(1) 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 parent ssid
              If running in verbose mode, this message is printed when nsr-
              clone 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).

       adding save set series which includes descendent ssid
              If running in verbose mode, this message is printed when nsr-
              clone notices that a requested save set is a continuation,
              requiring the entire series to be cloned.

       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

       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.

       each clone host needs at least two enabled devices
              When cloning between two storage nodes that share the same phys-
              ical drive, each node must have at least two enabled devices.

       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 sepa-
              rated 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(1).

       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 resi-
              dent on the listed volumes.  Since only complete save sets can
              be cloned, nsrclone automatically requests additional volumes.
              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.

       WARNING: Multiple concurrent cloning operations on the same
              savesets have been detected. The list of volumes reported below
              may not be accurate.
              nsrclone prints this message when it detects more clone
              instances than it expected.  This happens when more than one
              nsrclone commands are run on same saveset concurrently. Verify
              the clone volumes using mminfo(1).  Please note that the result
              of the clone operation is not affected by this warning.

ADVERTISEMENT