Content-type: text/html Man page of NSRSTAGE


Section: Maintenance Commands (8)
Updated: Dec 11, 01m
Index Return to Main Contents


nsrstage - NetWorker save set staging command  


[ -v ] [ -d ] [ -s server ] [ -J storage-node ] [ -b pool ] [ -y retention ] -m -S { -f file | ssid[/cloneid]... }
[ -v ] [ -s server ] [ -J storage-node ] [ -y retention ] -C -V volume


The nsrstage program is used to migrate existing save sets on a manual basis. Migration is the process of moving one or more save sets between volumes. The process begins with a clone of the specific save sets to the new volume specified, followed by the deletion of cloned save set entries from the media database (see the -S description). Finally, the possible removal of the save sets from the original source volumes. The second and the third operations are triggered by the successful completion of the previous operation. The data is moved to new media volumes, making room for new data on the original volumes.

Migration can be onto any media type (for example, save sets on a adv_file or file volume can be migrated to an optical disk). The nsrstage program does not perform simple volume migration; it migrates full save sets.

You can specify exactly which copy (clone) of a save set to use as the source. See the -S option description.

If the nsrstage program encounters an error after successfully cloning some of the specified save sets, then it will delete only those successful save sets from the source volume before it gets aborted.  


-b pool
Specifies the name of the media pool to which the data should migrate. The pool may be any pool currently registered with nsrd(1m). You can view values 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 assigned to the Clone pool corresponding to the original pool. Eg., if staging a save set from the Default pool, it is assigned to the Default Clone pool; if staging a save set from an Archive pool, it is assigned to the Archive Clone pool.
Performs the actual migration operation.
-s server
Specifies a NetWorker server with save sets to migrate. See nsr(1m) for a description of server selection. The default is the current system.
-J storage-node
Specifies which host to use as the storage node for the recovery part of the staging process (see nsr_storage_node(5)).
Enables verbose operation. In this mode, additional messages are displayed about the operation of nsrstage, such as save sets that cross volumes, or save set series expansions. If concurrent nsrstage operations are performed on the same savesets, it is possible for the volume names to be inaccurate. In that case nsrstage will issue a warning. Please see DIAGNOSTICS for the exact warning message.
-y retention
Sets the date (in nsr_getdate(3) format) when the staged data will become recyclable. The special value forever is used to indicate that a volume that never expires (i.e. an archive volume) 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.
Deletes the input file that specifies the save set identifiers to be staged. This option must always be specified in conjunction with a -f option.
Instructs nsrstage to perform a volume cleaning operation. Scans a volume for save sets with no entries in the media data base and recovers their space. Space for recyclable and aborted save sets are also recovered from the volume with the save set entries removed from the media data base. You can perform this operation on adv_file and file type volumes.
-S ssid
Causes nsrstage to treat subsequent command line parameters as save set identifiers. 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(1m). The -S option is useful when you want to migrate individual save sets from a volume, or to migrate all save sets matching some mminfo query. The save set identifiers also specify exactly which copy of a save set 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 referring to the mminfo -S report.


If the -S ssid/cloneid format is used, then only the specific ssid instances will be removed from media database.

If the -S ssid is specified and no cloneid is specified, that all cloned instances of the ssid will be deleted from the media database, except the one being staged.

If other adv_file or file device clone instances were removed from the media database as a result of staging, then those save sets will also be removed from their respective volumes, and space will be recovered.
-f file
Instructs nsrstage to read the 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.
-V volume
Specifies the name of the volume to be cleaned. This option cannot be used with -S or -m options.


Migrate save sets 1234 and 4568 to a volume in the Offsite Clone pool:
nsrstage -b 'Offsite Clone' -m -S 1234 4567

Migrate clone instance 12345678 of save set 1234 to a volume in the Default Clone pool:

nsrstage -m -S 1234/12345678

Migrate all save sets created since last Saturday to a volume in the Default Clone pool:

nsrstage -m -S `mminfo -r ssid \
-q 'savetime>last saturday'`

Recover space from volume jupiter.013:

nsrstage -C -V jupiter.013

Only complete save sets can be migrated by nsrstage(1m):  


The exit status is zero if all of the requested save sets migrated successfully; otherwise status is non-zero.

Several messages are printed denoting a temporary unavailability of nsrd(1m) for migrating data. These are self-explanatory. In addition, you may see one of the following messages:

Adding save set series which includes ssid
If running in verbose mode, this message prints when nsrstage notices that a requested save set is continued and requires the entire series to be migrated (even if only part of the series was specified by the command line parameters).
Cannot contact media database on server
The media database (and probably 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 open nsrstage session with server
This message prints when the server is not accepting migration sessions. A more detailed reason prints on the previous line.
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. You specify the save set with the cloneid form as two unsigned numbers separated by a single slash (/).
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(1m).
save set clone number/cloneid does not exist
You specified a specific clone of a save set, but that save has no clones with that clone identifier. Verify your save set identifiers using mminfo(1m).
volume name does not exist
The given volume (if you specified the -V option) does not exist in the media database.
waiting 30 seconds then retrying
A temporary error occur. nsrstage automatically retries its request until the condition is cleared. For example, if all of the devices are busy saving or recovering, nsrstage cannot use these devices and must wait for two of them to become free.
Space can only be recovered from adv_file and file type devices.
The given volume (if you specified the -V option) is not a file or adv_file type volume. This message is also printed after a successful migration of data from volumes of type other than file and adv_file.
WARNING: Multiple concurrent cloning operations on the same
savesets have been detected. The list of volumes reported below may not be accurate.
nsrstage prints this message when it detects more clone instances than it expected. This happens when more than one nsrstage commands are run on same saveset concurrently. Verify the clone volumes using mminfo(1m). Please note that the result of the staging operation is not affected by this warning.


nsr_stage(5), nsrclone(1m), nsr_getdate(3), mminfo(1m), nsr(1m), nsr_device(5), nsr_pool(5), nsrd(1m), nsrmmd(1m),




This document was created by man2html, using the manual pages.
Time: 02:37:01 GMT, October 02, 2010