nsrndmp_recover(8)
nsrndmp_recover(8)
NAME
nsrndmp_recover - use NetWorker and Network Data Management Proto-
col(NDMP) to recover data
SYNOPSIS
nsrndmp_recover [ -c client ] [ -s server ] [ -J storage-node ] [ -R
recover-target ] { -r raw device -S ssid/[clone] -m mount point [
-v { on|off } ] [ paths [ paths... ] ] | -F }
DESCRIPTION
nsrndmp_recover is used to coordinate recover operations with NetWorker
and a Network Data Management Protocol(NDMP) system. Only the super-
user may run this command. There are two ways to recover data:
destructive recovers and file-level recovers. Destructive recovers
occur when a raw partition is specifed by the -r option along with a
save set id (-S) option. Only a single save set can be specified at a
time since the target raw device pathname must be specified. Users may
opt to use the administrative user interface, NetWorker Management Con-
sole, to perform the destructive recover operation through the save set
recover window. Users can determine save set ids using the user
interfaces or the mminfo(8) command. File level recovers are specified
by the -F option in conjunction with the use of the nwrecover(8) or
recover(8) commands. Users should not specify this option.
The status of a recover can be monitored using the Java based NetWorker
Management Console or the curses(3X) based nsrwatch(8) program
for other terminal types. Only volume information is available at this
time. The amount of data that has been recovered is not provided.
nsrndmp_recover is not responsible for moving data on the NDMP system.
All such activity is handled by the NDMP system. nsrndmp_recover
receives messages from the NDMP system and processes them appropri-
ately. Such messages could request a new tape be mounted or to post a
log message. Refer to the NDMP specification and documentation avail-
able at www.ndmp.org for more details.
In order to recover data for another system, make sure the user per-
forming the nsrndmp_recover operation is on the remote access attribute
list of the client resource. See nsr_client(5).
Supports recovering data from a NetWorker storage device if the save
set was backed up by nsrndmp_save via nsrdsa_save. Nsrndmp_recover
program will spawn nsrdsa_recover locally if the save set's flags are
identified to have 'N' and 's'. See mminfo(8) for more details on 'N'
and 's' save set flags.
Notes:
It should be noted that browsers such as recover, nwrecover and win-
workr will spawn nsrndmp_recover locally. Therefore, for better perfor-
mance, try to launch browsers based on a volume location that has save
sets to be restored. For instance, if a backup was performed to a Net-
Worker storage node that is different from the NetWorker server, then
launch the browser on the NetWorker storage node for better perfor-
mance. If the browser is launched on the NetWorker server, then data
will flow from the NetWorker storage node to the NetWorker server and
from the NetWorker server to the NDMP system. All command line options
mentioned below apply for recovering from NetWorker storage node too.
OPTIONS
-c client
Client is the name of the machine that saved the files.
-F Specifies that a file-level recovery is going to be performed.
This option should only be specified by nwrecover(8) or
recover(8).
-m mount point
Specifies the destination directory to relocate recovered files.
If not specified, the data will be restored to original loca-
tion.
Notes:
If the NDMP Server is SnapImage, then the mount point of the raw
device specified by the -r option. The filesystem will be
unmounted for the recover operation and mounted after the opera-
tion is complete.
-r raw device
This option specifies the pathname of the raw device the data is
to be recovered to. You must use this option only for destruc-
tive recovers with SnapImage product.
-R recover-target
This option specifies the name of the destination host the data
will be recovered to. If not specified, the data will be
restored to the source host.
-s server
This option selects which NetWorker server to use.
-J storage-node
This option selects which NetWorker storage node to use.
-S ssid[/cloneid]
This mandatory option is used to specify save set recover mode.
This mode can be used to implement fast batch file recovery
without requiring the NetWorker file index entries. ssid speci-
fies the save set id for the save set to be recovered. When
there are multiple clone instances for a save set, the cloneid
can also be specified to select the particular clone instance to
be recovered from. The cloneid of a particular saveset can be
obtained from mminfo(8) output.
When no path arguments are specified, the entire save set
contents will be recovered. One or more path arguments can be
specified to limit which directories and files are actually
recovered. If path arguments are supplied, then the begining of
each path name as it exists in the save set must exactly match
one of the path before it will be recovered. Shell like file
name, matching using meta characters like '*', '?', and '[...]',
is not supported.
-v on|off
This option specifies the value of the verify flag. If the ver-
ify flag is turned on then, prior to sending to ndmp server for
recovery, the paths would be verified as having existance in the
index database for the given Save set id. Only those entries
that are found in the index database would be sent to the NDMP
server for recovery. On other hand if verify flag is off then
paths would be sent across to the NDMP server without verifica-
tion. The default value of this flag is on.
EXAMPLES
Sub-directory level restore to original location.
nsrndmp_recover -s server -c client -S ssid[/cloneid]
/fs/dir1 /fs/dir2 /fs/dir3 /fs/dir4/file1 ...
When indexes are not available for the specified paths
nsrndmp_recover -s server -c client -S ssid[/cloneid]
-v off /fs/dir1 /fs/dir2 /fs/dir3 ...
Restore to the original location
nsrndmp_recover -s server -c client -S ssid[/cloneid]
Relocate to a different location on the client
nsrndmp_recover -s server -c client -S ssid[/cloneid]
-m /destdir
where /destdir is the destination directory on the client
Relocate to a different location on the remote host
nsrndmp_recover -s server -c client -S ssid[/cloneid]
-m /destdir -R desthost
OR
nsrndmp_recover -s server -c client -S ssid[/cloneid]
-m desthost::/destdir
where desthost is another NDMP Client configured in the
NW server
Destructive restore with SnapImage
nsrndmp_recover -s server -c client -S ssid[/cloneid]
-m /mntpoint -r /dev/rdsk/c2t2d0s1
DIAGNOSTICS
Skipping file due to incomplete save set: /core
The user has marked a file that is associated with an incomplete
save set. The user should run nsrim -X to resynchronize the
file index and media database.
Entry /core not found in index, skipping
The user specified directory / file (/core) in path arguments,
which could not be found in the index database. The user should
run nsrndmp_recover with -v off from the command line if this
check is wished to bypass. This can be useful if the indexes are
lost and the data exists in backup media.
SEE ALSO
mminfo(8), nsr_client(5), nsrndmp_save(8), recover(8), nwrecover(8)
NetWorker 8.0.1 Dec 02, 12 nsrndmp_recover(8)