nsrndmp_save(8)
nsrndmp_save(8)
NAME
nsrndmp_save - use NetWorker and Network Data Management Protocol(NDMP)
to save data
SYNOPSIS
nsrndmp_save -T backup-type -c client-name [ -LL ] [ -M ] [ -P Proxy-
host ] [ -I Index-host ] [ -g group ] [ -l level ] [ -b pool ] [ -m
masquerade ] [ -N name ] [ -s server ] [ -J storage-node ] [ -t date ]
[ -e expiration ] [ -w browse_time ] [ -y retention_time ] [ -W width ]
[ -k checkpointid ] path
DESCRIPTION
nsrndmp_save coordinates the backup process with NetWorker and a target
Network Data Management Protocol(NDMP) system. Only the super-user may
run this command. The user must specify a backup type, client-name,
server, and path.
The behavior of the backup depends on the NDMP system being protected.
Certain environment variables may be needed depending upon the target
system. Documentation for such backups should be consulted for more
details.
The status of a backup can be monitored using the Java based NetWorker
Management Console or the curses(3X) based nsrwatch(8) program for
other terminal types.
nsrndmp_save is not responsible for moving data on the NDMP system.
All such activity is handled by the NDMP system. nsrndmp_save receives
messages from the NDMP system and processes them appropriately. Such
messages could request a new tape be mounted or a file index entry to
be created. Refer to the NDMP specification and documentation avail-
able at www.ndmp.org for more details.
Details about handling media are discussed in nsrmm(8) and
nsr_device(5).
In order to save data for another system, make sure the user performing
the nsrndmp_save operation is on the remote access attribute list of
the client resource. See nsr_client(5).
OPTIONS
-c client-name
Specifies the client name for starting the save session. This
is useful on clients with multiple network interfaces, and hence
multiple host names. It can be used to create multiple index
databases for the same physical client. Note that this does not
specify the network interface to use. This is specified in the
server network interface attribute of the client resource. See
nsr_client(5).
-M An NDMP client will be backed up to a NetWorker storage node by
the nsrdsa_save program. This option provides most of the Net-
Worker storage node features, such as backup to disk, multiplex-
ing, automedia verification, and staging. The nsrndmp_save pro-
gram spawns nsrdsa_save locally. A NetWorker storage node host-
name should be listed in the "storage nodes" attribute of
server's client-name resource.
Notes:
Save sets that are backed up by nsrndmp_save via nsrdsa_save
will be treated as regular NetWorker save set and will have save
set flags as 'N' and 's'. 'N' indicates NDMP client and 's'
indicates backed up to NetWorker storage node. See mminfo(8) for
more details.
-P proxy-host
nsrndmp_save spawns nsrdsa_save on Proxy-host. Proxy-host must
be a valid NetWorker client and should be listed in the remote
access list of client-name resource. This host will act as a
proxy to NDMP Data Server to receive the data and save it to
NetWorker storage device. This option is valid only with -M.
-I index-host
Used by savegrp to spawn nsrndmp_save on Index-host. Index-host
must be a valid NetWorker client and should be listed in the
remote access list of client-name resource. This host is desig-
nated to perform NDMP backup initiation and index processing.
This host must have 'Operate NetWorker' privileges.
-g group
Is used by savegrp(8) and savefs(8) 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.
-l level
Indicates the level of the save. This option is used by save-
grp(8) and savefs(8) to specify a particular level for a sched-
uled save. Valid values are: full, incr, and 1 through 9 inclu-
sive. The incr option is only supported when used with NDMP
servers that support token based backups using the NDMP
BASE_DATE/DUMP_DATE backup environment variables. Currently
Network Appliance and EMC Celerra filerservers are recognized as
supporting this. For other NDMP servers an incremental backup
is forced to a full backup and a message noting this is included
in nsrndmp_save's output. When the level value incr is speci-
fied the -t option must also be included and must specify the
save time of a previously produced full or incremental backup.
See the -t option for additional information. If the NDMP
server's implementation is lower than version 4, incremental
backups are forced to full backups.
When the level values 1-9 are specified nsrndmp_save will use
the NDMP server's native dump levels 1-9 if there is no token
based backup support. If the NDMP server does support token
based backups, then the -t option specifies the savetime of a
previously created saveset and the current backup will contain
files created or modified since the previous backup. If token
based backups are supported and -t is not specified the
requested level backup will be forced to a full backup.
-b pool
Specifies a particular destination pool for the save.
-L When two -L options are specified, this option causes an extra
line to be printed at the end of the form ``complete save-
time=number'', where number is the savetime of the save set cre-
ated by this backup. Used by savegrp(8).
-m masquerade
Specifies the tag to precede the summary line. This option is
used by savegrp(8) and savefs(8) to aid in savegrp summary noti-
fications.
-n Provide an estimate of the size of the backup. This option is
not supported but is accepted to be compatible with savegrp(8).
If this option is specified no estimate is produced and no
backup is performed.
-N name
Indicates the symbolic name of this save set. By default, the
most common prefix of the path arguments is used as the save set
name. The indexes get stored against the actual path name.
-q Indicates quiet. Not supported, but provided for compatibility.
-s server
Specifies which machine to use as the NetWorker server.
-J storage-node
Specifies which machine to use as the NetWorker storage node.
-t date
Indicates the date (in nsr_getdate(3) format) after which files
must have been modified before they will be saved. This option
is used by savegrp(8) and savefs(8) to perform scheduled saves
by consulting with the media database to determine the appropri-
ate time value based on the previous saves for the save set and
the level of the scheduled save. nsrndmp_save lists a valid
(but cryptic) date that may be used in future runs requestig an
incremental backup. Look for an output line like:
"nsrndmp_save: browsable savetime=1290539475". The large number
is the save time and may be used with this option.
-T backup-type
The type of backup on the NDMP server should perform, for example
dump, tar, cpio, smtape, or celestra. The backup-type value
supplied with this flag is dependent on the type of NDMP client
being backed up. Check the NDMP client's vendor documentation
to discover what values may be supplied with the NDMP backup
environment variable TYPE. Valid values for the TYPE variable
may be specified with -T.
-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 both browsable and non-recyclable until it
expires. After it expires and it has passed its browse time,
its state will become non-browsable. If it has expired and it
has passed its retention time, the save set will become recy-
clable. The special value forever is used to indicate that a
volume that never expires (i.e. an archive or a migration vol-
ume) must be used. By default, no explicit expiration date is
used.
-w browse
Sets the date (in nsr_getdate(3) format) after which the saved
data will no longer be browsable. By default, the server deter-
mines the browse date for the save set based on the browse poli-
cies in effect. This option allows overriding the existing
policies on a save by save basis.
-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 (i.e. an archive or a
migration volume) must be used. By default, the server deter-
mines 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.
-k checkpointid
Requests that a checkpointed backup be performed if the NDMP
data server being backed up supports it. A checkpointed backup
is paused periodically to remember the current state of the
backup. If the backup is interrupted, it can be resumed from
the point of the last checkpoint. The first backup of a check-
pointed backup is performed with a checkpoint id argument of
zero. As part of the backup the checkpoint id for the backup
will be printed out. If the backup is interrupted before com-
pletion it can be resumed by specifying the checkpoint id from
the output of the previous interrupted backup. The checkpoint
id remains the same until the backup completes either in failure
or success.
SEE ALSO
curses(3X), mminfo(8), nsr_getdate(3), nsr_client(5), nsr_device(5),
nsr_group(5), nsr_service(5), nsrd(8), nsrim(8), nsrindexd(8),
nsrmm(8), nsrmmd(8), nsrndmp_recover(8), nsrwatch(8), recover(8),
savefs(8), savegrp(8).
NetWorker 8.0.1 Dec 02, 12 nsrndmp_save(8)