Legato 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_schedule
nsr_schedule - NetWorker resource type "NSR schedule"SYNOPSIS
type: NSR schedule
DESCRIPTION
Each NetWorker schedule is described by a single resource of type NSR schedule (see nsr_resource(5)). To edit the NSR schedule resources for a NetWorker server, type: nsradmin -c "type:NSR schedule" or use the nwadmin(1) GUI. See nsradmin(1) for more information on using the NetWorker administration program. This resource describes a sequence of levels controlling the amount of data saved by NetWorker clients (see nsr_client(5)). There is one NSR schedule resource for each NetWorker schedule.
ATTRIBUTES
The following attributes are defined for resource type NSR schedule. 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. Several additional hidden attributes (e.g., administrator) are common to all resources, and are described in nsr_resource(5). name (read/write) This attribute specifies the schedule's name. The schedule is referred to by its name in client resources. Example: name: monthly_fulls; comment (read/write) This attribute is provided for the administrator to keep any explanatory remarks or supplementary information about the schedule. period (read-only) This attribute specifies the length of the schedule's period. It may be either "Week" or "Month". "Week" schedules repeat every 7 days and start on Sunday. "Month" schedules start over at the first of each month. The default is "Week." Example: period: Month; action (read/write) This attribute specifies the sequence of save levels making up the schedule. One entry is used for each day of the schedule. The entries must be separated by whitespace, i.e., blanks or tabs. The valid levels are "consolidate," "full," "incr," "skip," and the numbers 1 through 9. The actions consolidate, full, incr, and skip may be abbreviated "c," "f," "i," and "s," respectively. When the action attribute does not contain enough entries to account for every day in the period, NetWorker will repeat the list of actions when the end of the action list is reached. is of the form "month/day/year." Month and day are 2 digit num- bers, year may be either 2 or 4 digits. If the year is 2 digits, numbers in the range 70-99 are assumed to be offsets from 1900, those in the range 00-69 are assumed to be offset from 2000. Recurring date is of the form '[ number ] weekday every [ number ] period'. number can be a number (1, 2, 3, etc.) or an ordinal (first, second, third, etc.), and it is optional. weekday must be one of "monday," "tuesday," "wednesday," "thursday," "fri- day," "saturday," "sunday." The use of "last" for number is not supported (for example, "last friday" cannot be used to refer to the last Friday of the month). period must be one of "week," "month," "quarter," or "year." Action/date pairs are separated by commas (','). Example: override: full 1/1/1994, full first friday every 2 week;
EXAMPLE
The following defines a NSR schedule resource named "Default." The Default schedule may be modified, but it may not be deleted. Each Net- Worker server must have a Default schedule. This schedule has a period of one week, does a full save on Sunday, followed by 6 incremental saves. There are no override actions specified. type: NSR schedule; name: Default; period: Week; action: f i i i i i i; override:; The following defines a schedule named "quarterly." It has a period of one month. The action attribute specifies level 5, 9, and incremental saves. In the override attribute, full saves are specified for the first day of each quarter. Note that there are only 7 entries in the action attribute. Upon reaching the end of the list, NetWorker will start over at the beginning of the list, performing a level 5 save. type: NSR schedule; name: quarterly; period: Month; action: 5 incr incr incr 9 incr incr; override: f 1/1/1994, f 3/1/1994, f 6/1/1994, f 9/1/1994, f 1/1/1995;
SEE ALSO
nsr(1), savefs(1), mminfo(1), nsradmin(1), nsr_client(5), nsr_policy(5), nsr_resource(5), nwadmin(1).
ADVERTISEMENT
Legato NetWorker 7.xMan(1) output converted with man2html, sed, awk