Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ savefs(8) — DG/UX 5.4R3.00

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

getdate(3)

fstab(5)

vfstab(5)

nsr(5)

dump(8)

nsr(8)

nsrd(8)

nsrindexd(8)

nsrmmd(8)

recover(8)

save(8)

savegroup(8)



SAVEFS(8)                   Legato NetWorker 4.0                   SAVEFS(8)


NAME
       savefs - save filesystems to a NetWorker server

SYNOPSIS
       savefs [ -BEFnpqRv ] [ -s server ] [ -l level | -C schedule ] [ -N
       name ] [ -g group ] [ -e expiration ] [ -f filename ] [ -W width ] [
       -t date ] [ -T seconds ] [ filesystem...  ]

DESCRIPTION
       The savefs command will save filesystems (using save(8)) to a Net­
       Worker server.  Mount points are not crossed, and symbolic links are
       not followed.  Filesystems on different disks will be saved in paral­
       lel, up to a maximum of 4 simultaneously.  NOTE: running savefs
       directly is not recommended; use savegroup(8) instead.

       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 no filesystems are listed on the command line).  If the
       save set list consists of the keyword All, then the /etc/fstab file
       (/etc/vfstab on Solaris, and /etc/mnttab on SCO) on will be examined
       to determine which filesystems should be saved, making sure to save
       only local filesystems.

       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



Licensed material--property of copyright holder(s)                         1




SAVEFS(8)                   Legato NetWorker 4.0                   SAVEFS(8)


              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
              and is well-justified.

       -F     Force.  Save every argument like a filesystem, even if they
              are not listed in fstab (5) nor nsrclient (5).

       -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 since which files must have been
              modified to be saved, but don't actually do the save.  This
              information is gleaned from then /etc/fstab file (or another
              operating system specific file, as described above) and the
              nsrschedule(5).

       -q     Quiet.  Display only summary information and error messages.

       -qq    Really quiet.  Display only error messages.

       -R     Cause savefs to report on its success or failure, by echoing a
              simple "succeeded" or "failed" message as its last act.  This
              is used by savegroup(8) when it is running savefs.

       -v     Verbose.  Cause lots of debugging style output.  This option
              is also used by savegroup(8) when it is probing for the capa­
              bilities of the client's savefs, for supporting multiple ver­
              sions.

       -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 date
              The date (in getdate(3) format) from which to base schedule
              level calculations.  If not specified, the current time is
              used.

       -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



Licensed material--property of copyright holder(s)                         2




SAVEFS(8)                   Legato NetWorker 4.0                   SAVEFS(8)


              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(8) 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
              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.

       -N name
              The symbolic name this set of saves is to be known by.  By
              default, the first filesystem argument is used as the name.

       -g group
              Restrict the scope of the client to a particular group.  If
              this option is not specified, save sets from all instances of
              the NSR client resource for this client will be used, regard­
              less of the group.  This value is also passed on to save(8),
              which uses it to select a specific media pool.

       -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)).

       -W width
              The width used when formatting output or notification mes­
              sages.  By default, this is 80.

       -B     Force save of all connecting directory information from root
              (``/'') down to the point of invocation.  This option is used



Licensed material--property of copyright holder(s)                         3




SAVEFS(8)                   Legato NetWorker 4.0                   SAVEFS(8)


              by savegroup(8), for example, when saving the server's boot­
              strap information.

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.

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.

       /etc/vfstab
              Solaris only.  The same as /etc/fstab on other operating sys­
              tems.

       /etc/mnttab
              SCO only.  The same as /etc/fstab on other operating systems.

SEE ALSO
       getdate(3), fstab(5), mnttab(F) (SCO only), vfstab(5) (Solaris only),
       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


Typewritten Software • bear@typewritten.org • Edmonds, WA 98026