SAVEFS(8) Legato NetWorker 3.0 SAVEFS(8)
NAME
savefs - save filesystems to a NetWorker server
SYNOPSIS
savefs [ -BEFnpqRv ] [ -s server ] [ -l level | -C schedule ] [ -W
width ] [ -N name ] [ -e expiration ] [ -f filename ] [ -T seconds ]
[ -g groupname ] [ filesystem... ]
DESCRIPTION
Savefs will save filesystems (using save(8)) to a NetWorker server.
Mount points are not crossed, and symbolic links are not followed.
Filesystems on different disks will be saved in parallel, up to a
maximum of 4 simultaneously.
A level based system (similar to dump(8)) is used to save only those
files which have been modified since some previous save (a partial
save).
The local NetWorker client's nsrclient(5) resources will be exam
ined, and the filesystems listed in the save set attribute will be
saved. If the save set list consists of the keyword All, then
/etc/fstab will be examined to determine which filesystems should be
saved, and only local filesystems will be saved,
Care should be taken when the NSR client resource explicitly lists
the save sets, for two primary reasons. First, this list must be
manually updated when new filesystems are added which need saving.
Second, since savefs only stops at the end of a path or a mount
point, if you list two save sets in the same filesystem, and one is a
subdirectory of the other, the subdirectory will be saved twice.
Filesystem arguments can be specified to limit the filesystem saves
to only those specified, but the specified filesystems must appear on
some Save Set list for this client (see the -F option).
The nsrschedule(5) for the local NetWorker client will be examined
to determine the proper level of save for the current date.
The set of files that actually get saved will depend on when, and at
what level, previous saves have been performed, in addition to the
effects of the default directives (see nsrdirective(5)), and the
various directive files (see nsr(5)) which are encountered while pro
cessing the filesystem.
OPTIONS
-E estimate. Before saving any data, walk the filesystem trees
to be saved and accurately estimate the amount of data which
will be generated. Without this flag, the estimate size zero.
Note that this flag will consume an amount of time propor
tional to the number of files in each filesystem. This is
because the entire directory is walked before any saving
begins and walked again when actually saving the directory,
but the file data is only read from the disk the last time.
In many cases, the overhead for using this flag is not onerous
Licensed material--property of copyright holder(s) 1
SAVEFS(8) Legato NetWorker 3.0 SAVEFS(8)
and is well-justified.
-F Force. Save each argument with a level like a filesystem,
even if they are not listed in fstab (8) nor nsrclient (5).
-g groupname
Restrict the scope of the client to a particular group. If
this option is not specified, savesets from all instances of
the client will be used, regardless of the group.
-n No save. Accurately estimate the amount of data which would
be generated (as described for -E, but don't actually save any
data.
-p List the name of the filesystems, the level of save that would
be performed, and the time in which files must have been modi
fied since to be saved, but don't actually do the save. This
information is gleaned from /etc/fstab and the
nsrschedule(5).
-q Quiet. Display only summary information and error messages.
-qq Really quiet. Display only error messages.
-R Cause saveindex to report on its success or failure, by echo
ing a simple "succeeded" or "failed" message as its last act.
This is used by savegroup when it is running savefs.
-v Verbose. Cause lots of debugging style output.
-s server
Specify which machine to use as the NetWorker server. The
default is to try the local machine if it is a server, then
the logical name ``nsrhost'' if it exists.
-T seconds
This specifies the ``inactivity timeout'' in seconds. If
savefs detects that the (local) server has made no progress in
the specified time, then it concludes that the save command is
hung. A message is printed to stderr and savefs exits nor
mally. This option should only be used on NetWorker server
machines.
-l level
The level of save to perform. There are 12 levels: full, lev
els 1 though 9, incr, and skip. Full specifies that all files
are to be saved. It is analogous to a level 0 dump in
dump(8). Incr specifies incremental saves in which only those
files that have been modified since the most recent save, at
any level, are saved. This level has no exact analogue in
dump since the last save at any level, including previous
incremental saves, are considered when determining what to
save. Skip causes no files to be saved. The levels 1 though
9 cause all files to be saved which have been modified since
Licensed material--property of copyright holder(s) 2
SAVEFS(8) Legato NetWorker 3.0 SAVEFS(8)
any lower level save was performed. As an example, if you did
a full on Monday, followed by a level 3 save on Tuesday, a
subsequent level 3 save on Wednesday would contain all files
modified or added since the Monday full save. By default, the
save level is determined automatically from the NetWorker
client's schedule (see nsrschedule(5)). By using the history
of previous saves maintained by nsrmmd(8) on the NetWorker
server, the needed time for the given level can correctly be
computed. By using media information on the server, times
computed for saves which are based on previous save levels
will automatically be adjusted as required when tapes are
deleted.
-C schedule
The name of the schedule (see nsrschedule(5)) to use when
automatically determining the save level. If this option is
not specified, savefs will use the schedule named by the NSR
client resource for the specified filesystems.
-W width
The width used when formatting output or notification mes
sages. By default, this is 80.
-N name
The symbolic name this set of saves is to be known by. By
default, the first path argument is used as the name.
-e expiration
Sets the date (in getdate(3) format) when the saved data will
expire. By default, no explicit expiration date is used.
-f filename
The file from which application specific modules (or ASMs)
should take their directives (see nsr(5)). By default, these
are taken from the NSR directive resource named by the direc
tive attribute in the NSR client resource for each client (see
nsrdirective(5)).
-B Force save of all connecting directory information from root
(``/'') down to the point of invocation.
RESOURCE TYPES
NSR client
These specify the client's save sets, and the default schedule
and directives to use when saving them.
NSR directive
A resource of this type is named by the directive attribute in
each NSR client resource. These are the directives used for
the save sets specified in the associated NSR client resource.
NSR schedule
A resource of this type is named by the schedule attribute in
each NSR client resource. This is the schedule used for the
save sets specified in the associated NSR client resource.
Licensed material--property of copyright holder(s) 3
SAVEFS(8) Legato NetWorker 3.0 SAVEFS(8)
FILES
/etc/fstab
If All is specified in the save set attribute for a NSR client
resource, then the list of local filesystems is taken from
this file.
SEE ALSO
getdate(3), fstab(5), nsr(5), nsrservice(5), nsrschedule(5),
dump(8), nsr(8), nsrd(8), nsrindexd(8), nsrmmd(8), recover(8),
save(8), savegroup(8).
DIAGNOSTICS
Exit Codes
0 Normal exit.
255 Abnormal exit.
Licensed material--property of copyright holder(s) 4