NetWorker: nsrstage failure using -d switch

When attempting to use the nsrstage command with -d switch, receiving the error:

39096:nsrstage: Need to specify both -f and -d.
usage: nsrstage [-v] [-F] [-d] [-O] [-A action-parallelism] [-s server] [-J storage-node] [-b pool] [-y retention time] -m -S [-o]

When -d is used with nsrstage, the log shows it has been swapped for -R switch:

180169:nsrstage: Step (1 of 16): NSRCLONE_INIT_PHASE_ONE: nsrstage has been started on host 'hostname', with command 'nsrstage command_arguments -R destination_node command_arguments'.

nsrstage interprets -d as -R internally, meaning that if it is used with -d to attempt to designate the destination Storage Node, the command fails.

Although the two commands are similar, and nsrclone functionality covers all nsrstage functions, the current product has several subtle differences:

-R is not listed in nsrstage man page, although it is in nsrclone man page. 

nsrstage

-d Deletes the input file that specifies the save set identifiers to be staged. This option must always be specified with a -f option.

nsrclone

-d save storage node
              Specifies which host to use as the storage node for the saved part of the cloning process (see nsr_storage_node(5))

-R Removes the input file that specifies the volume names, save set or volume identifiers to be cloned. This option can only be specified with a -f option.

Otherwise - the two commands are identical in function. Both commands require the -m switch in order to complete the job as a stage job (clone, followed by deletion of the source):

-m  Performs the migration (or stage) operation. For Block based backup save sets, this option does not migrate save sets to the new media volumes. For volumes that have a combination of Block based backup save sets and regular NetWorker save sets, nsrclone -m skips over the Block based backup save sets with an error. For Data Domain retention-locked save sets, this option does not migrate save sets to the new media volumes. For volumes that have a combination of Data Domain retention-locked save sets and regular NetWorker save sets, nsrclone -m skips over the Data Domain retention-locked save sets with an error.  Bootstrap save sets are cloned to target media. The source save set entry is removed from the media database, but the data remains on the source media.

-m  Performs the migration operation. For Block based backup save sets, this option does not migrate save sets to the new media volumes. For volumes that have a combination of Block based backup save sets and regular NetWorker save sets, nsrstage -m skips over the Block based backup save sets with an error. If migration is attempted on a save set copy with Data Domain Retention Lock (DDRL), the operation fails if the DDRL expiry time has not passed. If migration is attempted on a save set, not a specific copy, the operation fails if the save set has a Data Domain retention lock and the expiry time has not passed. For a volume that has a combination of Data Domain retention-locked save sets and regular NetWorker save sets, nsrstage -m skips the Data Domain retention-locked save sets on the volume and attempt to migrate the rest. Bootstrap save sets are cloned to target media. The source save set entry is removed from the media database, but the data remains on the source media.

Workaround:

Using nsrclone with -m provides the same functionality as nsrstage, along with other switches which are not supported or included with nsrstage - see man page of nsrclone for details. 

Administrators are recommended to use nsrclone -m for staging operations always to enable use of nsrclone's more advanced and robust set of command arguments, while still providing staging capability.

The nsrclone and nsrstage commands are detailed in the NetWorker Command Reference Guide, available through: https://www.dell.com/support/product-details/product/networker/docs