Legato NetWorker Commands Index:
ansrdascdcode
cdi_block_limits
cdi_bsf
cdi_bsr
cdi_eod
cdi_filemark
cdi_fsf
cdi_fsr
cdi_get_config
cdi_get_status
cdi_inq
cdi_load_unload
cdi_locate
cdi_offline
cdi_rewind
cdi_set_compression
cdi_space
cdi_ta
cdi_tapesize
cdi_tur
changers
dasadmin
ddmgr
EMASS_silo
erase
generate_test_tape
hadump
hafs
hagentd
hagetconf
haprune
hascsi
hasubmit
hasys
hpflip
IBM_silo
ielem
inquire
jbconfig
jbexercise
jbverify
ldunld
lgtolic
lgtolmd
libcdi
libscsi
libsji
libstlemass
libstlibm
libstlstk
lrescan
lreset
lus_add_fp_devs
lusbinfo
lusdebug
mini_el
mm_data
mminfo
mmlocate
mmpool
mmrecov
msense
mt
ndmpjbconf
networker
nsr (1)
nsr (5)
nsr_archive_request
nsr_client
nsr_crash
nsr_data
nsr_device
nsr_directive
nsr_getdate
nsr_group
nsr_ize
nsr_jukebox
nsr_label
nsr_layout
nsr_license
nsr_migration
nsr_notification
nsr_policy
nsr_pool
nsr_regexp
nsr_resource
nsr_schedule
nsr_service
nsr_shutdown
nsr_stage
nsr_storage_node
nsr_support
nsr_usergroup
nsradmin
nsralist
nsrarchive
nsrcap
nsrcat
nsrck
nsrclone
nsrcnct
nsrd
nsrexec
nsrexecd
nsrhsmck
nsrhsmclear
nsrhsmd
nsrhsmls
nsrhsmnfs
nsrhsmrc
nsrhsmrecall
nsrib
nsriba
nsrim
nsrindexasm
nsrindexd
nsrinfo
nsrjb
nsrlic
nsrls
nsrmig
nsrmm
nsrmmd
nsrmmdbasm
nsrmmdbd
nsrmon
nsrndmp_clone
nsrndmp_recover
nsrndmp_save
nsrpmig
nsrports
nsrretrieve
nsrssc
nsrstage
nsrtrap
nsrwatch
nwadmin
nwarchive
nwbackup
nwrecover
nwretrieve
pathownerignore
pmode
preclntsave
pstclntsave
read_a_block
recover
relem
resource
save
savefs
savegrp
savepnpc
scanner
sjiielm
sjiinq
sjimm
sjirdp
sjirdtag
sjirelem
sjirjc
sjisn
sn
ssi
stk_eject
STK_silo
stli
sym2xdm
tapeexercise
tur
uasm
writebuf
* - Windows Only
* mt
* nsrlpr
* nsrperf
nsrstage
nsrstage - NetWorker save set staging commandSYNOPSIS
nsrstage [ -v ] [ -d ] [ -s server ] [ -b pool ] -m -S { -f file | ssid[/cloneid]... } nsrstage [ -v ] [ -s server ] -C -V volume
DESCRIPTION
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 suc- cessful 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.
OPTIONS
-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(1). You can view values by selecting Pools from the Admin- istration menu of nwadmin(1). 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. -m Performs the actual migration operation. -s server Specifies a NetWorker server with save sets to migrate. See nsr(1) for a description of server selection. The default is the current system. -v 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 concur- rent 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. 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 num- bers. 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 migrate individual save sets from a vol- ume, 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. Notes: 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.
EXAMPLES
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(1):
DIAGNOSTICS
The exit status is zero if all of the requested save sets migrated suc- cessfully; otherwise status is non-zero. 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 sepa- rated 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(1). 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(1). 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(1). Please note that the result of the staging operation is not affected by this warning.
SEE ALSO
nsr_stage(5), nsrclone(1), nsr_getdate(3), mminfo(1), nsr(1), nsr_device(5), nsr_pool(5), nsrd(1), nsrmmd(1), nwadmin(1).
ADVERTISEMENT
Legato NetWorker 7.xMan(1) output converted with man2html, sed, awk