nsr_directive(5)
nsr_directive(5)
NAME
nsr_directive - NetWorker resource type 'NSR directive'
SYNOPSIS
type: NSR directive
DESCRIPTION
Each NSR directive is described by a single resource of type NSR direc-
tive (see nsr_resource(5)). To edit the NSR directive resources for a
NetWorker server, use nsradmin(8) or NetWorker Management Console. See
the corresponding manual page for more information on the use of these
NetWorker administration programs.
These resources are used by the NetWorker ASM (Application Specific
Module) family of commands when processing files; see uasm(8) and
nsr(5). Directives can be used to improve the efficiency of backups by
controlling which files get saved and specifying special handling on
certain types of files.
Names of the currently defined 'NSR directive' resources are listed in
the directive attribute of the 'NSR client' resource for selection
which will be used to backup the client (see nsr_client(5)).
ATTRIBUTES
The following attributes are defined for resource type NSR directive.
The information in parentheses describes how the attribute values are
accessed. Create-only indicates that the value cannot be changed after
the resource has been created. Read/write means the value can be
updated by authorized administrators. Hidden means it is an attribute
of interest only to programs or experts, and these attributes can only
be seen when the hidden option is turned on in nsradmin(8). Dynamic
attributes have values which change rapidly. Several additional
attributes such as, administrator, are common to all resources, and are
described in nsr_resource(5).
name (create-only)
The names of directive resources are displayed as choices when
creating or updating NetWorker client resources, see
nsr_client(8). The name can generally be chosen at the adminis-
trator's convenience, but it must be unique for this NetWorker
server. The directive resource named 'Unix standard directives'
may be modified, but it may not be deleted. Other directives can
only be deleted if no clients or archive lists are using them.
Example: name: Unix standard directives;
comment (read/write)
This attribute is provided for the administrator to keep any
explanatory remarks or supplementary information about the
directive.
directive (read/write)
This attribute contains the rules defining the directive. The
value of this attribute is similar to the contents of a .nsr
file except that absolute path names must be specified for each
<< path >> directive. See nsr(5) for more information on the
format of NetWorker directives.
Example: directive: "<< / >> skip : core";
NetWorker comes with several directive resources already defined.
Examples include "UNIX standard directives", "UNIX with compression
directives", "NT standard directives" and "Encryption directive". The
first two are meant for use with clients running on UNIX platforms.
The next directive is intended for use with clients running on Windows
platforms. The last directive is for clients requiring encryption with
Advanced Encryption Standard (AES). There may also be two other direc-
tives "Default" and "Default with compression". These are old
names for "Unix standard directives" and "Unix with compression direc-
tives", respectively. NetWorker will remove the directive resources
using the old names when they are no longer being used.
EXAMPLE
An example NSR directive resource, named 'Unix directive', follows:
type: NSR directive;
name: Unix directive;
directive: "
<< / >>
+skip : core
skip : tmp
<< /usr/spool/mail >>
mailasm : *
<< /nsr >>
allow
";
SEE ALSO
nsr(5), nsr_resource(5), nsr_client(8), savegroup(8), savefs(1), uasm(1),
nsradmin(8).
NetWorker 7.6.2 Jul 14, 11 nsr_directive(5)