[Contents] [Previous Topic] [Next Topic]
The nsradmin program is an administrative program for the NetWorker system that uses the command line. Typically, nsradmin monitors and modifies NetWorker resources over the network. Commands are entered on standard input, and output is produced on standard output.
If you enter the nsradmin command without command options, the program opens with a command prompt for you to enter additional options as needed:
The following example describes the format and command options available for the nsradmin program:
nsradmin [-i file] [-s server]
At each nsradmin input prompt, you enter a command name and optional arguments. You can shorten command names to the smallest unique string, for example, you can enter p for the print command. You specify command arguments in the form of an attribute list. Most nsradmin commands operate on a set of resources returned by a query. The query is specified as an attribute list that is used to match resources with the following rules:
If the query has only one name and no values, the nsradmin program tries to determine the query based on the name. If the name is a hostname, the query is made for all the resources on the given host. Otherwise, the name is interpreted as a type name, and all resources of that given type are selected.
Command Options for nsradmin
The following list describes the commands available and their function:
- bind query
- To bind to the service that owns the resource described by query. If a query is not specified, send the queries to the RAP Resource Directory, and update, create, and delete commands to the service that owns the resource being changed. On failure, the previous service continues to be used.
- create attribute-list
- To create a resource with the given attributes.
- delete query
- To delete the resources that match the current query. If a query is specified, it becomes the current query.
- help command-name
- ? command-name
- To print a message describing a command. If no command name is given, a synopsis of all the commands is printed.
- print query
- To print the resources that match the current query. If a query is specified, it becomes the current query. If the current show list is not empty, only the attributes named in the show list are displayed.
- server server-name
- To bind to the given NetWorker server name. If no server is specified, the RAP location service is used. On failure, the previous server continues to be used.
- show name
- To add names to the show list if a name list (really an attribute list with no values) is specified. Only these attributes are displayed in subsequent print commands. If no name list is given the show list is cleared, resulting in all attributes being shown.
- To print a list of all known types.
- update attributes
- To update the resources given by the current query to match attributes.
- To exit the nsradmin program.
- . query
- To set the current query, if a query is specified, without printing the results of the query. Otherwise, the current query, show list, server binding, and options are displayed.
Resources Available in the nsradmin Program
The nsradmin program provides a character-based interface to manage the same resources available through the nwadmin program. These include:
The NSR client resource describes the files that are saved, the backup schedule, the directive used to omit files from the save, the length of time the files' index entries should be kept in the on-line file and media indexes, the users given access to back up, browse, and recover a client's files. To edit the NSR client resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI.
The NSR client resource has the following attributes:
The following is an example of a NSR client resource used to define a client, called saturn, backing up all of its files to the server mars:
- The name attribute specifies the hostname of a client.
- The server attribute specifies the hostname of a client's server.
- The archive- services attribute specifies if a system can use archive services. To use this attribute archive support must be enabled on the server first.
- The schedule attribute specifies the name of the schedule controlling the backup levels for the save sets listed in the save set attribute.
- The browse- policy attribute specifies the name of the policy controlling the length of time entries will remain in a client's on-line file index.
- The retention -policy attribute specifies the name of the policy controlling the length of time entries will remain in the media index before they are marked as recyclable.
- The directive attribute specifies the directive used for backing up a client.
- The group attribute specifies the group a client is a member of. The group controls when scheduled backups are performed on the client.
- The save- set attribute lists the path names to be saved for a client. When a client requires different file systems to be saved on different schedules, a client resource is required for each file system and schedule.
- The priority attribute specifies the backup priority given to a client where priority 1 is the highest, 1000 is the lowest. Automated savegroup's will attempt to back up clients with higher priorities before clients with lower priorities.
- The remote -access attribute specifies a users access to back up, browse, and recover a client's files. Additional users, hosts, and netgroups may be granted permission to access a 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 a client's files to the specified users.
- The remote user attribute:
- The password attribute is used by savegrp to initiate the commands savefs and save on a client machine. The commands savefs and save use the password to gain access to files being backed up. If a password is given, then the remote user attribute for the client resource must also be defined.
- The backup -command performs a remote backup of client's data and save sets. This command can also perform pre and post backup processes. The prefix of the specified value must begin with "nsr" or "save".
- The executable -path attribute specifies the path used by the server for executing commands on the client.
- The server- network -interface attribute specifies the network interface the server uses for saves and recovers.
- The aliases attribute specifies the aliases for a client machine that queries can match.
- The owner -notification attribute sends the contents of status messages to the owner/primary user of a system.
- The statistics attribute consists of: the size of the client's on-line file index, the number of kilobytes used and the number of entries in the index.
- The index -save -set attribute specifies save set, residing in a client's file index, to purge when an index operation is set to purging oldest cycle.
- The index -message attribute is the status message resulting from the previous index operation.
- The index -operation- start attribute indicates the starting time of the current index operation. This attribute is a null string ("") when the operation is "Idle".
- The index- progress attribute indicates the progress an index has made towards finishing the current task. This attribute is blank when the operation is "Idle", and is expressed as a percentage.
- The index -operation attribute specifies the current index operation.
- The parallelism attribute indicates the maximum number of saves that should be run simultaneously on a single client.
- The archive -users attribute specifies the users given access to the archive services on a client. This attribute can only be set if archive support has been enabled on the server.
- The application -information attribute specifies a client's application information.
- The storage -nodes attribute specifies the storage nodes available to a client for saving data. A client's saves are directed to the first storage node that has an enabled device and a functional media service.
- The clone- storage- nodes attribute specifies the storage nodes available to a storage node whose data is being cloned. Cloned data originating from a storage node will be directed to the first storage node that has an enabled device and a functional media service.
type: NSR client;
archive services: Disabled;
browse policy: Month;
retention policy: Quarter;
save set: h:\, c: \usr, c:\usrsrc;
remote access: venus, sam@*, jupiter/john;
remote user: operator;
backup command: ;
archive users: ;
storage nodes: nsrserverhost;
clone storage nodes: ;
To edit the NSR device resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI
The NSR device resource has the following attributes:
The following is an example of a NSR device resource:
- The name attribute specifies the path name for a device. For systems that optionally support "Berkeley style" tape positioning on close, the BSD style tape device name should be used. For optical disks the path name is generally the "c" partition.
- To facilitate interaction with external media management services a logical device type has been defined. When interacting with such services, the device into which a volume is loaded may be determined by the media management service. A logical device is used to define a device resource.
- At the time of definition the name of a device is not related to any specific device. The default for both the media type and family are set to logical. The name, type, and family are not determined until the media management service has loaded a volume into a device in response to a request made by . The name, type, and family of the actual device are then stored in the attributes logical name, logical type, and logical family, respectively. The association between the logical device and the actual device last only as long as a volume is loaded into the device and allocated for use by .
- The media- type attribute specifies the media type used by a device. Some of the possible values for this attribute are:
- The enabled attribute indicates whether a device is available for use.
- The read -only attribute indicates whether a device is reserved for read only operations, such as recover or retrieve.
- The target -sessions attribute specifies the target number of saves for a device, and used for load-balancing. Once all the devices have reached their corresponding target number, additional sessions are allocated equally across all devices.
- The media -family attribute specifies the class of storage media, as determined from the media type:
- The message attribute specifies the last message from a server regarding a device, such as the progress or rate of an operation.
- The volume -name attribute is monitors the mounting and unmounting of volumes for a device.
- The write -enabled attribute indicates if writing to the current volume is allowed.
- The volume -operation attribute manipulates media volumes currently in the device, through several operations:
- The volume -label attribute is set by the Verify label operation and may be an input to the Label operation.
- The volume- default -capacity attribute is used by the Label operation if the volume current capacity attribute is blank. This attribute enables the override of default sizes when using devices (and/or tapes) with different capacities than the defaults.
- The volume -current -capacity attribute determines the capacity of a volume during the Label operation.
- The volume- expiration attribute specifies a volumes expiration date, which is set by the Verify label operation.
- The volume -pool attribute specifies the pool a volume belongs, or has been assigned to.
- The NSR- operation attribute specifies the current operation being performed by the device.
- The minor -mode attribute reports the current status of a device.
- The statistics attribute reports the statistics on the operation of a device. The statistics include:
- elapsed, the time of operation
- errors, the number of errors
- last rate, the last writing rate
- max clients, the maximum number of concurrent clients
- file marks, the number of file marks written
- rewinds, the number of rewinds
- files skipped, the number of files skipped
- records skipped, the number of records skipped
- current file, the current file number
- current record, the current record number
- seek files, the relative number of files being spaced over
- seek records, the relative number of records being spaced over
- estimated kb, the total estimated amount read/written on a volume
- amount kb, the total amount read/written on the volume, in kb
- file amount kb, the current amount read/written on this file, in kb
- sessions, the current number of sessions assigned to this device
- The cleaning -required attribute indicates whether a device needs to be cleaned. If the value of this attribute changes from yes to no and the value of date last cleaned is not updated then date last cleaned is set to the current time. will set this attribute to yes if the device is scheduled to be cleaned. Then the notification device cleaning required is sent, indicating that a device needs to be cleaned.
- The cleaning- interval attribute specifies the amount of time from date last cleaned until the next scheduled cleaning for a device.
- The date -last- cleaned attribute records the time and day a device was last cleaned.
- The volume -block -size attribute specifies the block size of a currently mounted volume.
- The volume-id attribute specifies the volume id for a currently mounted volume.
- The access- count attribute indicates the number of operations performed on a device since it's configuration as a device.
- The access -weight attribute indicates the weight of a single operation performed on a device. Each time a device is used its weight is increased and the less often the device will be selected for new operations.
- The consecutive -errors attribute specifies the current number of consecutive errors resident on a device.
- The max c-onsecutive -errors attribute indicates the maximum number of consecutive errors allowed before the device will be disabled.
- The operation -arg attribute specifies extra parameters about a device operation. Parameters are packed into a string and parsed.
- The volume -message attribute indicates the result of the volume's last operation.
- The volume- write -time attribute indicates the time a save set was first written onto the volume.
- The volume -flags attribute indicates new flags for the volume to operated on, during a "Label" or "Label without mount" operation.
- The jukebox- device attribute indicates if a media device is in a jukebox
- The unlabeled -volume -loaded attribute indicates whether a volume loaded into a device has a readable volume label.
- The auto- media- management attribute indicates whether automated media management for a device is enabled. If the value is set to yes then recyclable volumes loaded into the device may automatically be re-labeled by for re-use and unlabeled volumes loaded into the device may be automatically labeled. A volume is considered to be unlabeled if the volume does not contain a label that may be read by this device. Volumes are considered unlabeled:
- The logical- name attribute specifies the name for a logical device.
- The logical- type attribute specifies the type for a logical device.
- The logical -family attribute is the family associated with a logical device.
- The connection- process -id attribute specifies the process identifier that maintains the connection between external media management services and a mounted volume.
- The connection -message attribute specifies error messages reported by a process connected to an external media management service.
- The connection -status attribute specifies the exit status reported by a process connected to an external media management service.
- The save- mount- timeout attribute indicates the timeout value from an initial save mount request for a storage node, on which a device resides. If a request is not satisfied, the storage node will be locked from receiving save assignments, for "save lockout" minutes.
- The save -lockout attribute indicates the amount of time a storage node will be locked from receiving save assignments.
type: NSR device;
message: writing, done
volume name: mars.017;
media family: tape;
media type: 8mm 5GB;
write enabled: Yes;
read only: No;
target sessions: 4;
volume label: mars.017;
volume default capacity: ;
volume current capacity: 5000 MB;
volume expiration: "Thu Sep 21 17:23:37 1996";
volume pool: Default;
volume flags: ;
volume operation: ;
volume write time: ;
volume block size: 32 KB;
volume id: 32449;
access weight: 1;
consecutive errors: 0;
max consecutive errors: 20;
operation arg: ;
volume message: ;
NSR operation: ;
minor mode: idle;
jukebox device: Yes;
statistics: elapsed = 257572, errors = 0, last rate =
max clients = 3, file marks = 22, rewinds = 4,
files skipped = 1976, records skipped = 0,
current file = 2389, current record = 162,
seek files = 0, seek records = 0,
estimated kb = 0, amount kb = 6273,
file amount kb = 6273, sessions = 1;
cleaning required: No;
cleaning interval: 2 weeks;
date last cleaned: "Tue Apr 11 15:10:32 1995";
auto media management: No;
unlabeled volume loaded: No;
logical name: ;
logical type: ;
logical family: ;
connection process id: ;
connection message: ;
connection status: ;
save mount timeout: 30;
save lockout: 0;
To edit the NSR directive resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI
The NSR directive resource has the following attributes:
The following is an example of a NSR directive resource, named "NTdirective"
type: NSR directive;
name: NT directive;
<< / >>
+skip : core
skip : tmp
<< c:\usr\spool\mail >>
mailasm : *
<< c:\nsr >>
controls when a group of clients begin saving data and whether scheduled backups are started automatically each day. To edit the resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI
The resource has the following attributes:
The following is an example of a nsr_group resource:
type: NSR group;
start time: "3:33";
inactivity timeout: 30;
work list: mars, incr, /g, mars, incr, index,
completion: mars, /, succeeded,
"mars: / level=incr, 31 KB 00:01:01 72 files
To edit the NSR jukebox resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI.
The NSR jukebox resource has the following attributes:
Following is an example of a resource named Huntington:
- The name attribute specifies the name of a jukebox.
- The model attribute specifies the jukebox model.
- The physical- slots attribute specifies the first and last physical slot numbers in the jukebox. The first slot number must be less than or equal to the last slot number, and specified as two separate attribute values. For Silo Tape Libraries this attribute is equal to the number of volumes allocated to a server.
- The control- port attribute specifies the path of the control port, for the jukebox robotics. Control commands are then sent to the jukebox, from the control port. For Silo Tape Libraries this attribute specifies the hostname and type of the Silo Tape Libraries server.
- The devices attribute identifies device pathnames for each device residing within a jukebox. The entries are listed in the same order as they were physically installed in the jukebox.
- The number -devices attribute identifies the number of configured devices in the jukebox.
- The write -enabled attribute indicates if the mounted volume can be written to.
- The bar- code -reader attribute indicates if is using the bar code label from the media when a jukebox has a bar code label reader.
- The match- bar -code- labels attribute indicates if is using the bar code label, instead of a label template, when labeling media volumes.
- The volume -expiration attribute specifies the expiration time for a volume that is currently being labeled, or specifies the time a volume within a jukebox will end interaction with external media management services.
- The available- slots attribute specifies the slots containing volumes available to be written to by requests. The slots are specified by a range which may be a single slot number or a pair of slot numbers separated by a dash. The first number is less than or equal to the second. When satisfying requests to mount a particular volume or slot, all of the volumes within the physical slots can be used.
- The enabler -code attribute identifies the enabler code for a NSR license resource corresponding to a jukebox resource.
- The operation attribute identifies the current jukebox operation.
- The operation- message attribute displays error messages when an jukebox operation fails.
- The operation -device attribute passes device names to current operations.
- The operation -slots attribute passes slots to current operations.
- The operation -options attribute passes the mode of a volume to the current operation.
- The operation -barcodes attribute passes volume tags or barcodes to the current operation.
- The operation -response attribute identifies the default response to questions asked while performing an operation.
- The operation- report- mode attribute identifies the amount of output generated during operation execution.
- The operation -label -state attribute designates the operation to be performed on a labeled volume as; to be recycled or to be unlabeled.
- The operation- volume -capacity attribute specifies a volume's capacity.
- The operation- volume type attribute specifies the types of volumes that may be considered when allocating a volume.
- The operation -ineligible attribute specifies volumes ineligible for the current operation.
- The operation -task attribute designates a secondary task or operation to be performed with the current operation.
- The operation- result attribute reports error messages for multiple operations. This attribute maintains error messages for 32 simultaneous operations performed on a jukebox, that failed.
- The operation- instance attribute specifies the instance number associated with an operation.
- The operation -next -instance attribute specifies the instance number associated with the next simultaneous operation.
- The operation- instances attribute specifies the instance number for each simultaneous operation currently executing.
- The operation -hostname attribute identifies the name of the system an operation is to executed.This attribute is used for jukeboxes who support devices, attached to multiple hosts, where the host machine may be inferred from other attributes, such as operation device.
- The operation- template attribute specifies the template a label operation will use.
- The operation -volume- pool attribute specifies the default volume pool for label operations.
- The operation- source- pool attribute specifies the pool a volume will be selected for recycling.
- The operation- uses -left attribute indicates the number of times a cleaning cartridge can used.
- The volumes attribute specifies the names of resident volumes in corresponding order to the slot number.
- The volume -ids attribute specifies the volume identifiers (volid) for resident volumes.
- The volume -cartridge- ids attribute tracks the identifier for each cartridge h a volume resides.
- The loaded -volumes attribute contains the names of volumes currently loaded in jukebox devices.
- The loaded -bar- codes attribute identifies the bar codes of loaded volumes.
- The loaded -slots attribute identifies the slot numbers of loaded volumes.
- The event- tag attribute specifies the tag of the last notification event sent to the nsrd service
- The event- message attribute is the text of the last notification event sent to the nsrd service.
- The messages attribute specifies the log messages from previous operations nsrjb has completed.
- The minimum- space attribute specifies the low water mark of the remaining space on the volumes contained in the available slots.
- The jukebox- options attribute specifies the options for this jukebox.
- The auto -clean attribute specifies automatic cleaning for each device.
- The cleaning -slots attribute identifies the range of slots in a jukebox that have been set aside for cleaning cartridges. For a pair of slot numbers the first number of the pair is less than or equal to the second. When auto clean is set to yes the range of slots specified for this attribute are assumed to contain cleaning cartridges, and the range of slots specified by available slots.
- The default -cleanings attribute specifies the number of uses assigned to a new cleaning cartridge during an inventory of a jukebox by nsrjb.
- The auto- media -management attribute indicates whether automated media management for a jukebox is enabled. If the value is set to yes, unlabeled volumes in a jukebox may be automatically labeled.
- The STL -device- names attribute specifies silo device names of the devices identified in the devices attribute of a Silo Tape Library.
- The STL- interface- lib attribute indicates the path name of the dynamically linked Silo Tape interface library.
- The STL -device- sharing attribute specifies, how device sharing is handled. Device sharing is the automatic, load dependent, device switching for devices within a Silo Tape Library between different connected hosts. When this attribute is specified as "perm-max", perm and max are numbers with perm < max, and perm is the number of devices, which can be reserved permanently.
- The STL -barcodes attribute indicates the barcodes of the volumes residing within in a Silo Tape library, which are available to .
- The STL -device- reservation attribute specifies the reservation state of shared devices in a Silo Tape library.
- The allocated -devices attribute specifies jukeboxes allocated to RLM.
- The application -name attribute specifies the name used by a server to identify itself to OpenVault when submitting a request to access resources on a jukebox.
- The application -key attribute specifies the key used by a server to identify itself to OpenVault when submitting a request to access resources on jukebox.
- The jukebox- lock attribute synchronizes access to resources in a jukebox that supports multiple simultaneous operations. This attribute can be used to lock and unlock a entire jukebox.
- The device -locks attribute synchronizes access to device resources in a jukebox that supports multiple simultaneous operations. The first two numbers of this attribute identify a range of devices locked, and the third number is the instance number assigned to the lock operation.
- The volume/slot locks attribute synchronizes access to volume and slot resources in a jukebox. The first two numbers of this attribute identifies the range of volumes/slots locked and the third number is the instance number assigned to the operation holding the lock.
type: NSR jukebox;
physical slots: 1-11;
control port: email@example.com;
devices: c:\dev\rmt\0mbn, c:\dev\rmt\1mbn;
number device: 2;
write enabled: Yes;
bar code reader: Yes;
match bar code labels: Yes;
volume expiration: ;
available slots: 2-11;
enabler code: 012345-6789ab-cdef00;
operation device: h:\dev\rmt\0mbn;
operation slots: 1-10;
operation options: manual;
operation barcodes: A01B, A0/3-5/B;
operation response: Yes;
operation report mode: verbose;
operation label state: recycle;
operation volume capacity: 10G;
operation volume type: 8mm, dlt;
operation ineligible: ;
operation task: mount after label;
operation instance: 3;
operation next instance: 2;
operation hostname: host1;
operation template: default;
operation volume pool: NonFull;
operation source pool: Default;
volumes: venus.001, venus.002, venus.003;
volume ids: 24198, 24199, 24200;
STL device sharing: 2-4;
STL device reservation: ;
STL interface lib: h:\usr\lib\libstl.sol;
event tag: 6319962287;
event message: could not unload device
messages: "09/12/97 11:50:56 CREATED";
minimum space: 7g;
jukebox options: two_sided;
auto clean: Yes;
cleaning slots: 1;
default cleanings: 12;
auto media management: Yes;
reset class: initialize unload;
jukebox lock: 10;
device locks: 1-1-10;
volume/slot locks: 1-5-10;
describes the templates for generating volume labels. To edit the NSR label resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI.
The NSR label resource has the following attributes:
The following is an example of a nsr_label resource:
type: NSR label;
fields: aa-zz, 00-99;
describes the features enabled in your NetWorker installation. To inspect the NSR license resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI.
The NSR license resource has the following attributes:
IMPORTANT: If a server's host id changes, all auth codes will immediately be
invalidated, and the enablers must be re-registered with Legato to obtain new
Following is an example of a NSR license resource:
type: NSR license;
name: NetWorker Advanced/10;
enabler code: 123456-123456-123456;
host id: 7260d859;
expiration date: Authorized - no expiration date;
auth code: abcdef00;
license type: B10;
specifies the files to be saved, the schedule, directives to use to omit files from a save, the group files will be pre-migrated with, the high-water and low-water marks to use for migration, the minimum access time and file size for migration, a list of file owners and groups to include or exclude during migration, and a list of file name patterns to skip.
To edit the NSR migration resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI.
The NSR migration resource has the following attributes:
Following is an example of a NSR migration resource defining an HSM client, called elantra:
type: NSR migration;
save set: c:\test;
directive: Unix with compression directives ;
high water mark (%): 90;
low water mark (%): 80;
last access time: ;
minimum file size (KB): 5;
file owner: joe, dave;
file group: staff, developers;
preserve: *.exe *.dll;
is used for each combination of an event, priority, and action handled by the notification system. A notification consists of a single event type, a single priority, and a message. The notification system posts each message to the action of each NSR notification resource that includes an event type and priority. To edit the NSR notification resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI.
The NSR notification resource has the following attributes:
Following is an example of a NSR notification resource:
type: NSR notification;
name: savegroup completion;
action: h:\usr\ucb\mail -s savegroup completion;
priority: Info, Notice, Warning, Waiting;
controls how long entries remain in a client's on-line file index, and when to mark a save set as recyclable. Each NSR client resource uses two policies, a browse policy and a retention policy. Each policy defines an amount of time determined by the period and the number of periods.
To edit the NSR policy resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI.
The NSR policy resource has the following attributes:
Following is an example of a NSR policy resource named Quarter:
type: NSR policy;
number of periods: 3;
This resource determines where volumes save sets reside based upon their characteristics.
There are four types of pools:
There are four pre-enabled pools shipped with :
There are also a few pools shipped with that are not enabled by default:
To edit the NSR pool resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI.
The NSR pool resource has the following attributes:
Following is an example of a NSR pool resource:
type: NSR pool;
archive only: No;
label template: Default;
save sets: ;
store index entries: Yes;
auto media verify: Yes;
recycle from other pools: Yes;
recycle from other pools: Yes;
volume type preference: 4mm;
a sequence of levels controlling the amount of data saved by clients. There is one NSR schedule resource for each schedule.
To edit the NSR schedule resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI.
The NSR schedule resource has the following attributes:
Following is an example of a NSR schedule resource:
type: NSR schedule;
action: 5 incr incr incr 9 incr incr;
override: f 1/1/1997, f 3/1/1997;
To edit the NSR Stage resources for a NetWorker server use nsradmin or use the NetWorker Administrator GUI.
The NSR stage resource has the following attributes:
Following is an example of a NSR Stage resource:
type: NSR stage;
name: test stage1;
max storage period: 7;
high water mark (%): 90;
low water mark (%): 85;
save set selection: largest save set;
destination pool: Default Clone;
start now: ;
Each resource represents a component of a system that needs administration. Resources are manipulated to control a system. The file and the resources in them are accessible through the nwadmin and nsradmin programs, and can be viewed with a text editor.
Each resource is described by a list of attributes. Each attribute consists of a name and optional list of values. The attribute name is separated from an attributes options by a colon (:), attribute values are separated by commas (,), and each attribute ends in a semicolon (;). A comma, semicolon or back-slash (\) at the end of a line continues the line.
Following is an example of a resource, with eight attributes.
Each NSR resource includes the following attributes:
type: NSR client;
directive: Unix standard directives;
save set: All;
remote access: ;
defines the following types of resources:
[Contents] [Previous Topic] [Next Topic]
Legato Systems, Inc.
Copyright © 1998, Legato Systems. All rights