Content-type: text/html Man page of NSRSCSI_SAVE


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


nsrscsi_save - Performs binary image backup of a host accessible raw device to long term storage with NetWorker  


nsrscsi_save [ -c client-name ] [ -g group ] [ -N save-set-name ] [ -I input filename ] [ -s server ] [ -b pool ] [ -e expiration ] [ -y retention time ] Path


The nsrscsi_save program performs raw device backup using SCSI commands directly accessing the device. It retrieves the data blocks directly from the device and sends the data stream to a NetWorker storage device (See nsrmmd(1m)). Only the super-user may run this command. The user must specify a Path.

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)).  


-c client-name
Specifies the client name for starting the save session. However, the client name is optional. If client name is unspecified, then the local host will be assumed to be the client. If client-name is specified, the save session is started against this client and the resulting save set is registered against client-name.

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.

-N save-set-name
Symbolic name to the save set. By default, save-set-name is the Path name itself. However, if the Path is a device-set-name , then -N will be ignored as device-set-name will be tagged against each device entry to form a save set name for that backup session.
-I input-filename
Input file name (eg. /tmp/testdisks.res) is the absolute file path name that must have the list of devices to be backed up. If the input-filename is not specified, then default input-filename is constructed from device-set-name. For example, if the device-set-name is oracledisks, the input-filename would be /nsr/res/oracledisks.res.

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


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.

The Path can be anyone of the following formats:-

"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.

                             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

                             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

Note:- Path must be given in double quotes.

-g group
Is used by savegrp(1m) and savefs(1m) to denote the group of the save. See nsr_client(5) and nsr_group(5). It is also used by the NetWorker server to select the specific media pool.
-b pool
Specifies a particular destination pool for the save. Note that all the save sessions go the same pool.
When two -L options are specified, this option causes an extra line to be printed at the end of the form ``complete savetime=number'', where number is the savetime of the save set created by this backup. Used by savegrp(1m).
-m masquerade
Specifies the tag to precede the summary line. This option is used by savegrp(1m) and savefs(1m) to aid in savegrp summary notifications.
Indicates no save. Not supported, but provided for compatibility.
Indicates quiet.
-s server
Specifies which machine to use as the NetWorker server.
-e expiration
Set the date (in nsr_getdate(3) format) when the saved data will expire. When a save set has an explicit expiration date, the save set remains non-recyclable until it expires. If it has expired and it has passed its retention time, the save set will become recyclable. The special value forever is used to indicate that a volume that never expires (i.e. an archive or a migration volume) must be used. By default, no explicit expiration date is used.
-w browse
Indicates the browse date. Not supported, but provided for compatibility.
-y retention
Sets the date (in nsr_getdate(3) format) when the saved data will become recyclable. The special value forever is used to indicate that a volume that never expires (an archive or a migration 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 on a save-by-save basis.
-W width
The width used when formatting summary information output.


curses(3X), mminfo(1m), nsr_getdate(3), nsr_client(5), nsr_device(5), nsr_group(5), nsr_service(5), nsrd(1m), nsrim(1m), nsrindexd(1m), nsrmm(1m), nsrmmd(1m), save(1m), nsrwatch(1m), recover(1m), savefs(1m), savegrp(1m)




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