If a backup of a raw device needs to be performed, then the Path must be the raw device path that is accessible to nsrscsi_save.
If a backup of a SYMMETRIX device needs to be performed, then the Path must contain SYMMETRIX id and SYMMETRIX device id (See options section below for syntax of the Path). The nsrscsi_save program directly interacts with the SYMMETRIX device via the SYMAPI library and discovers the host accessible raw device path for the corresponding SYMMETRIX device id. It then performs a SCSI backup of the raw device path. (Refer to SYMMETRIX documentation for more details on SYMMETRIX and SYMAPI.)
The status of a backup can be monitored using the Java based NetWorker Management Console or the curses(3X) based nsrwatch(1m) program for other terminal types.
The user can also specify a device set to be backed up where the device set is a set of device entries. If the Path specified is a device-set-name (See Options section below), then for each device entry in the device set a backup thread is forked to dedicate the backup operation for each device for optimized performance and better utilization of system and NetWorker resources. The total number of threads run are directly proportional to number of device entries in the device set. However, server, client and device parallelism attributes are enforced on the NetWorker server.
Details about handling media are discussed in nsrmm(1m) and nsr_device(5).
In order to save data for another system, make sure the user performing the nsrscsi_save operation is on the remote access attribute list of the client resource. See nsr_client(5).
Since it is a raw device backup, the save sets are not browsable. These save sets are recoverable via nsrscsi_recover command only (See nsrscsi_recover (1m)). Also, if the number of devices to be backed up is more than one, then nsrscsi_save will start and end a save session to create a container set(deduced from cover set). This container set would encompass all the save sets backed up by threads. The mminfo tool would display the container sets as any other regular save sets (See mminfo (1m)).
Note:- This client name is not necessarily the host where device is accessible. For instance, a SYMMETRIX BCV device is accessible on a different host for backup but the user wants to register the backup against the client where standard device is attached.
Inputfile can be an absolute path to the file that needs to be read, or inputfile can be "-" which means read device entries from stdin.
If device-set-name is specified in the Path and -I is not specified, the default location for input file is /nsr/res/device-set-name.res
Notes:
The
input-filename
should contain only the device entries that need to be backed up,
and multiple device entries should be separated by newline.
When -I is specified,
device-set-name
should also be specified.
"Raw device path" E.g. "/dev/rdsk/c1t2d0s2"
"{device-set-name}" E.g. "{OracleDevices}"
Note that the braces are mandatory
to distinguish device-set-name from
single device path.
In this case, device entries are read
from /nsr/res/device-set-name.res file
i.e., the resource file name should be
same as the device-set-name.
Also note that the device entries in
this file must be raw device paths.
"<<vendor>>{device-set-name}"
Same syntax as above. However, the
difference is that the device entries
must be in vendor specific format.
E.g. "<<emc_symm>>{OracleDevices}"
Currently, emc_symm is the only suppored
vendor.
SYMMETRIX format of a device entry or
a device path is SymID/DevId where
SymId is 00343456567 and DevId is 0366.
"<<vendor>>vendordevice" E.g. "<<emc_symm>>00343456567/0366"
In this case, only one vendor device is
backed up. Here, vendor is "emc_symm"
and device to be backed up is
"SymID/DevId".
Note:- Path must be given in double quotes.