EMC Legato NetWorker Commands ReferenceLegato 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
nsr_client
nsr_client - NetWorker resource type 'NSR client'SYNOPSIS
type: NSR client
DESCRIPTION
Each NSR client is described by a single resource of type NSR client
(see nsr_resource(5)). To edit the NSR client resources for a Net-
Worker server type:
nsradmin -c "type:NSR client"
See the nsradmin(1) manual page for more information on using the Net-
Worker administration program. The client resource may also be edited
using the nwadmin(1) command.
For each NetWorker client, this resource describes which files should
be saved, the schedule used to save these files, which directive should
be used to omit files from the save, how long the files' index entries
should be kept in the on-line file index and the media index, and who
is allowed to back up, browse, and recover this client's files. A
client may have more than one resource describing it.
ATTRIBUTES
The following attributes are defined for resource type NSR client. The
information in parentheses describes how the attribute values are
accessed. Read-only indicates that the value cannot be changed by an
administrator. Read/write means the value can be set as well as read.
Hidden means it is an attribute of interest only to programs or
experts. Hidden attributes can only be seen when the hidden option is
turned on in nsradmin(1) or by selecting the details Menu Item in the
View Menu for a particular window in nwadmin(1). Dynamic attributes
have values which change rapidly. Encrypted attributes contain data
that is not displayed in its original form. The assumption is that the
data is sensitive in nature and needs to be protected from accidental
disclosure. Several additional attributes (for example, administrator)
are common to all resources, and are described in nsr_resource(5).
Certain client attributes (e.g. "Client OS type", "CPUs", "NetWorker
version" and "Enabler in use") do not get populated in the Client
Setup/Information window of the NetWorker GUI, when the NetWorker
Server is running under Eval mode or an Enterprise license. However,
when the NetWorker server has a Workgroup/NetWork/Power edition
enabler, these client attributes are refreshed appropriately in the
window after the client backup.
name (read-only, single string)
This attribute specifies the hostname of this NetWorker client.
Example: name: venus;
server (constant, single string)
This attribute specifies the hostname of this client's NetWorker
server. The server's hostname will be used as the default
value.
archive services (read/write, choice)
This attribute determines if this system can use archive ser-
vices. This attribute can only be set if archive support has
been enabled on the server. The choices are enabled or dis-
abled. Example: archive services: enabled;
schedule (read/write, choice)
This attribute specifies the name of the schedule controlling
the backup levels for the save sets listed in the 'save set'
attribute. The default value is 'Default'. Any currently
defined schedule names may be used, see nsr_schedule(5).
Example: schedule: Default;
browse policy (read/write, choice)
This attribute specifies the name of the policy controlling how
long entries will remain in this client's on-line file index.
The default value is 'Month'. Any currently defined policy name
may be used as long as the period defined by the policy is not
longer than the retention policy's period, see nsr_policy(5).
Example: browse policy: Month;
retention policy (read/write, choice)
This attribute specifies the name of the policy controlling how
long entries will remain in the media index before they are
marked as recyclable. The default value is 'Year'. Any cur-
rently defined policy name may be used as long as the period
defined by the policy is not shorter than the browse policy's
period, see nsr_policy(5).
Example: retention policy: Year;
directive (read/write, choice)
This attribute specifies the directive to use when backing up
the client. The default value is NULL. The valid choices for
the directive resource are names of the currently defined 'NSR
directive' resources, see nsr_directive(5).
Example: directive: Unix with compression directives;
group (read/write, choice list)
This attribute specifies the group this client is a member of.
The group controls the start time for automatic backups. The
value may be one of the currently defined 'NSR group' resources,
see nsr_group(5). The default value is 'Default'.
Example: group: Default;
save set (read/write, list)
This attribute lists the path names to be saved for this client.
The names should be separated by comma space (, ). The default
value is 'All'. On all NetWorker supported clients, 'All'
refers to the mounted file systems. Also, NetWorker supports
'wildcard' at the filesystem level. Eg., For a Unix NetWorker
client, '/*' refers to all mounted filesystems under '/'. And if
'/space1' and '/space2' are valid filesystems, one could use
'/space*' to get both these filesystems backed up on the partic-
ular client. Please note that 'wildcard ' matching at the subdi-
rectory level, is not supported. So, '/space1/subdir*' will not
work.
When a client needs to have different file systems saved on dif-
priority (hidden, read/write, choice)
This attribute controls the backup priority of this client.
Priority 1 is the highest, 1000 is the lowest. Automated save-
grp's will attempt to back up clients with higher priorities
before clients with lower priorities. Note that this is only
one factor used to determing the next client. The savegrp com-
mand has many parameters to consider, and may choose a lower
priority client while trying to balance the load.
Example: priority: 500;
remote access (read/write, string list)
This attribute controls who may back up, browse, and recover a
client's files. By default this attribute is an empty list,
signifying that only users on the client are allowed to back up,
browse, and recover its files. Additional users, hosts, and
netgroups may be granted permission to access this client's
files by adding their names to this attribute. Netgroup names
must be preceded by an ampersand ('&'). Input of the form
<user>@<host> or <host>/<user>, grants access to the client's
files to the specified users. The <user> and/or <host> may be a
wild card, "*". If a user name is a wild card, it means all
users at the host are granted access to the client's data. When
a host name is a wild card, that user on all hosts is granted
access to the client's data. All users on a host may also be
granted access to the client's data by just listing the host's
name, that is, <host> is equivalent to *@<host> or <host>/*.
Note that this attribute does not override file system permis-
sions, the user still needs the necessary file system permis-
sions to back up, browse, or recover a file. The following
example grants access to the client's data for all users that
satisfy at least one of the following criteria, <user name,
user's hostname, server's domain> is a member of the netgroup
"netadmins", the user is from the host mars, the user is from
the host jupiter, the user's name is sam from host pluto, or the
user's id is root from any host.
Example: remote access: &netadmins, mars, *@jupiter, sam@pluto,
*/root;
remote user (read/write, string)
This attribute has several uses. For those clients that are
accessed via the rsh(1) protocol (new clients use nsrexecd(1)
instead), this attribute specifies the user login name the Net-
Worker server will use to authenticate itself with the client.
The default value is NULL, implying that 'root' should be used.
When savegrp-p (see savegrp(1)) is run on the NetWorker server,
the server runs commands on the client to determine which files
to save. Note that when the nsrexecd(1) protocol is used to
access the client, the remote user attribute is not used for
authentication.
Certain clients, such as NetWare fileservers, use this attribute
along with the password attribute, below, to gain access to the
files being backed up. Other clients that back up application
data, such as Sybase databases, use this attribute along with
the password to gain access to the application data. There may
be a different value of this attribute for each resource that
describes the same client.
NDMP clients use this attribute along with the password
savefs and save commands on the client's machine. The savefs
and save commands use the password to gain access to the files
being backed up. If a password is given, then the "remote user"
attribute for the client resource must also be defined. There
may be a different value of this attribute for each resource
that describes the same client.
This attribute does not need to be set for existing Unix clients
that are not backing up any application specific data.
This attribute is also used in conjunction with the remote user
attribute to configure access to a NDMP server.
backup command (read/write, string)
The remote command to run to back up data for this client and
save sets. This command can be used to perform pre and post
backup processing and defaults to the save command. The value
must not include a path and must start with the prefix "save" or
"nsr".
Example: backup command: savemsg;
executable path (read/write, string, hidden)
This attribute specifies the path to use when the NetWorker
server is executing commands on the client. When no path is
specified, the "remote user's" $PATH is used.
Example: executable path: /etc/nsr;
server network interface (read/write, string, hidden)
The name of the network interface on the server to be used for
saves and recovers.
Example: server network interface: mars-2;
aliases (read/write, string list, hidden)
This attribute is a list of aliases (nicknames) for the client
machine that queries can match. If this list is empty, match on
client name alone.
Example: aliases: mars;
owner notification (read/write, hidden)
A notification action to be executed to send the contents of
status messages to the owner/primary user of a machine (for
example, savegrp completion messages).
Example: owner notification: /usr/ucb/mail -s "mars' owner noti-
fication" carl@mars;
statistics (constant, hidden, dynamic)
This attribute contains three values: the size of the client's
on-line file index in kilobytes, the number of kilobytes actu-
ally used, and the number of entries in the index.
Example:
statistics: elapsed = 1761860, index size (KB) = 776,
amount used (KB) = 680, entries = 2216;
index save set (update-only, hidden, dynamic)
This attribute specifies the client file index save set to purge
when the index operation is set to purging oldest cycle.
Example: index save set: /;
index path (read/write, hidden)
Example: index path: /disk2/index/venus;
index message (update-only, hidden, dynamic)
This attribute contains the ending status message for the previ-
ous index operation. This attribute is typically blank,
indicating that the previous operation completed successfully.
Example: index message:;
index operation start (update-only, hidden, dynamic)
This attribute contains the starting time of the current index
operation. This attribute is a null string ("") when the opera-
tion is 'Idle'. The format is weekday followed by hour and min-
utes.
Example: index operation start: Wednesday 02:45;
index progress (update-only, hidden, dynamic)
This attribute contains the progress the index has made towards
finishing the current task. This attribute is blank when the
operation is 'Idle'. The progress is expressed as a percentage.
Example: index progress: 45;
index operation (update-only, hidden, dynamic)
This attribute contains the current index operation. It is nor-
mally 'Idle'.
Example: index operation: Reclaiming space;
parallelism (read/write, hidden)
This attribute specifies the maximum number of saves that should
be run at the same time for the client.
Example: parallelism: 2;
archive users (read/write, string list)
This attribute specifies a list of users that are allowed to use
the archive services on the client. This attribute can only be
set if archive support has been enabled on the server. To
schedule an archive request for a client, root (or equivalent)
must be on that client's Archive users list, or else root@client
must be in the server's Administrator list. If no users are
listed and the client resides in same machine as the server,
only administrators and the local root user (that is,
root@server) are allowed to use the archive services on the
client. A value of '*' implies any user is allowed to archive
or retrieve data. The '/' and '@' characters are not allowed as
part of the user name.
Example: archive users: paul;
application information (read/write, hidden,
string list)
This attribute contains client application information. The use
of this attribute is client specific and should be utilized as
indicated by the documentation received with the product. NDMP
clients fill in various parameters and values in this attribute
separated by an equals sign ('=').
Example: application information: HIST=yes;
ndmp (read/write, choice)
This attribute indicates whether or not the client resource is
configured for NDMP backups. If the client is used for NDMP
tional media daemon, nsrmmd(1). The default value of
'nsrserverhost' represents the server. In addition to storage
node names the keyword 'curphyhost' could also be entered into
the list. The entry 'curphyhost' denotes the current physical
host. It is only used for virtual clients on a cluster. It
should not be used on physical clients or on the client which is
tied with the virtual server. Using the curphyhost keyword would
enable the virtual clients backup to be directed to the storage
node on which the virtual client is currently residing on. See
nsr_storage_node(5) for additional detail on storage nodes.
clone storage nodes (read/write, string list)
This attribute specifies the hostnames of the storage nodes to
receive the directed clones. Cloned data originating from the
storage node is directed to the first storage node that has an
enabled device and a functional media daemon, nsrmmd(1). There
is no default value. If this attribute has no value, the
server's 'clone storage nodes' will be consulted. If this
attribute also has no value, then the server's 'storage nodes'
attribute will be used to select a target node for the clone.
See nsr_storage_node(5) for additional detail on storage nodes.
licensed applications (read-only, string list)
This attribute contains names of the licensed applications used
by the client. By default, this field is blank.
EXAMPLES
Note: The hidden attributes are not shown in these examples.
A resource to define a client, called venus, backing up all of its
files to the NetWorker server mars:
type: NSR client;
name: venus;
server: mars;
archive services: Disabled;
schedule: Full Every Friday;
browse policy: Month;
retention policy: Quarter;
directive: Unix with compression directives;
group: Default;
save set: All;
remote access: ;
remote user: ;
password: ;
backup command: ;
aliases: venus, venus.legato.com;
archive users: ;
storage nodes: nsrserverhost;
clone storage nodes: ;
The resources for a client backing up different file systems on differ-
ent schedules:
type: NSR client;
name: saturn;
remote access: venus, sam@*, jupiter/john;
remote user: operator;
password: ;
backup command: ;
aliases: saturn.legato.com;
archive users: ;
storage nodes: nsrserverhost;
clone storage nodes: ;
type: NSR client;
name: saturn;
server: mars;
archive services: Disabled;
schedule: Full on 1st Friday of Month;
browse policy: Month;
retention policy: Quarter;
directive: Unix standard directives;
group: Default;
save set: /usr/src/archive;
remote access: sam@venus, &netadmins, root@*;
remote user: operator;
password: ;
backup command: ;
aliases: saturn.legato.com;
archive users: ;
storage nodes: nsrserverhost;
clone storage nodes: ;
SEE ALSO
rsh(1), ruserok(3), nsr(5), nsr_schedule(5), nsr_directive(5),
nsr_group(5), nsr_policy(5), nsr_storage_node(5), save(1), savegrp(1),
savefs(1), nsradmin(1), nsrexecd(1), nwadmin(1)
ADVERTISEMENT
Legato NetWorker 7.xMan(1) output converted with man2html, sed, awk