NSRNDMP_CLONE man page on DigitalUNIX

Man page or keyword search:  
man Server   12896 pages
apropos Keyword Search (all sections)
Output format
DigitalUNIX logo
[printable version]


NSRNDMP_CLONE(8)					      NSRNDMP_CLONE(8)

NAME
       nsrndmp_clone  -	 use  NetWorker	 and  Network  Data  Management Proto‐
       col(NDMP) to perform save set cloning

SYNOPSIS
       nsrndmp_clone [ -v ] [ -s server ] [ -b pool ] ] -y retention ] { -f
		     file | volname...	}

       nsrndmp_clone [ -v ] [ -s server ] [ -b pool ] [ -y retention ] -S { -f
		     file | ssid[/cloneid]...  }

       nsrndmp_clone [ -v ] [ -s server ] [ -b pool ] [ -y retention ] -S -t
		     start time [ -e end time ] [ -c client name ] [ -g group
		     name ]

       nsrndmp_clone [ -v ] [ -s server ] [ -b pool ] [ -y retention ] -S -e
		     end time [ -t start time ] [ -c client name ] [ -g group
		     name ]

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

       DESCRIPTION
	      The  nsrndmp_clone  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 reliabil‐
	      ity  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  an  LGTO Ultrium 2 tape). However, all media used as
	      the destination of an nsrndmp_clone 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, nsrndmp_clone 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 nsrndmp_clone 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.

       The nsrndmp_clone 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  cho‐
       sen  (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 discription, in the Options section).

       Cloning between storage nodes is accomplished by an NDMP Tape Server on
       the  source node reading from a volume, and another NDMP Tape Server on
       the target node writing to a volume.  The source node is determined  by
       the location of a source volume; 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 client resource in descending  priority.   See  nsr_storage_node(5)
       and  nsr_client(5)  for	additional  detail on how these attributes are
       used and for other storage node information.

       If the save set	to  be	cloned	was  backed  up	 by  nsrndmp_save  via
       nsrdsa_save  (i.e.  the	save  set's flags  have 'N' and 's'), then use
       nsrclone to clone these save sets; they are  cloned  to	any  NetWorker
       storage device other than an NDMP tape device.  Cloning from a non-NDMP
       tape device to an NDMP tape device, and vice-versa, is  not  supported.
       See mminfo(8) for more details on the 'N' and 's' save set flags.

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 Media Pools from  the	left  pane  of
	      NetWorker	 Management Console's Media display.  If you omit this
	      option, the cloned save  sets  are  automatically	 sent  to  the
	      Default Clone pool.

       -f file
	      Instructs nsrndmp_clone to read the volume names, volume identi‐
	      fiers 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.

       -s server
	      Specifies	 a  NetWorker 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 nsrndmp_clone, such as save
	      sets that cross volumes, or save set series expansions.

       -y retention
	      Sets the date (in nsr_getdate(3) format) when  the  cloned  data
	      will  become  recyclable.	  The special value forever is used to
	      indicate that a volume that never expires (i.e. an archive  vol‐
	      ume)  must be used.  By default, the server determines this date
	      for the save set based on	 the  retention	 policies  in  effect.
	      This option allows overriding the existing policies.

       -S     Causes nsrndmp_clone 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 for‐
	      mat 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 nsrndmp_clone 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.

       -e end time
	      Specify the end time (in nsr_getdate(3)  format)	for  selecting
	      save  set IDs for cloning.  This option can only be used with -S
	      option.  If not specified, end time  is  set  as	current	 time.
	      Please note that, -e 0 is same as -e today.

       -t start time
	      Specify  the start time (in nsr_getdate(3) format) for selecting
	      save set IDs for cloning.	 This option can only be used with  -S
	      option.	If  not	 specified, start time is set as end time - 24
	      hours.  Please note that, -t 0 is same as -t today.  When speci‐
	      fying a time range, at least -t or -e option must be specified.

       -c client name
	      If  client  name	is  specified, only the save sets belonging to
	      that client will be selected.  More than one client name can  be
	      specified	 by using multiple -c options. This option can only be
	      used with -t or -e option.

       -g group name
	      If a group name is specified, only the save  sets	 belonging  to
	      that  group  will be selected. Only one group name can be speci‐
	      fied.  It can be used with -c option.  This option can  only  be
	      used with -t or -e option.

EXAMPLES
       Copy all save sets that begin on the volume mars.001 to a volume in the
       Offsite Clone pool:
	      nsrndmp_clone -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
       nsrndmp_clone(8):
	      nsrndmp_clone -S `mminfo -r ssid \
		   -q '!incomplete,savetime>last saturday,savetime<last monday'`

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

       Copy  all save sets created between time 01/21/05 14:50:03 and 01/24/05
       14:50:03 for the group Default
	      nsrndmp_clone -S -t '01/21/05 14:50:03' -e '01/24/05 14:50:03' \
		   -g Default

       Copy all save sets created in the last 24 hours for clients "rose"  and
       "seam".
	      nsrndmp_clone -S -e now -c rose -c seam

SEE ALSO
       nsrclone(8), nsrndmp_save(8), nsrndmp_recover(8), nsr_getdate(3),
       nsr_pool(5), nsr_storage_node(5), mminfo(8), nsr(8), nsrd(8), nsr‐
       mmd(8),

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(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 parent ssid
	      If running in verbose mode, this message is printed when
	      nsrndmp_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
	      nsrndmp_clone notices that a requested save set is a continua‐
	      tion, 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 open nsrndmp_clone 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.

       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.

       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" for the
	      -b option.

       Volume name has clone; requesting
	      additional volumes
	      This message is printed in verbose mode when a specified save
	      set has already been cloned to the volume specified in the error
	      message.	Since a save set can have at most one clone per vol‐
	      ume, nsrndmp_clone automatically requests additional volumes.

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

       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 nsrndmp_clone 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 nsrndmp_clone must wait for these devices become available.

NetWorker 7.3.2			  Aug 23, 06		      NSRNDMP_CLONE(8)
[top]

List of man pages available for DigitalUNIX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net