SGI Techpubs Library

IRIX 6.5  »  Man Pages
find in page



     save - save files to long term storage with NetWorker


     save [ -BEiLnqvx ] [ -s server ] [ -c client-name ] [ -N name ] [ -e
     expiration ] [ -f dirfile ] [ -b pool ] [ -F file ] [ -I input_file ] [
     -g group ] [ -l level ] [ -t date ] [ -m masquerade ] [ -W width ] [ path
     ... ]


     save saves files, including directories or entire filesystems, to the
     NetWorker server (see nsr(1M)).  The progress of a save can be monitored
     using the X Window System based nwadmin(1M) program or the curses(3X)
     based nsrwatch(1M) program for other terminal types.

     If no path arguments are specified on the command line or via the -I
     option, the current directory will be saved.  save will save a directory
     by saving all the files and subdirectories it contains, but it will not
     cross mount points, nor will it follow symbolic links.  If the paths to
     be saved are mounted from a network file server, save will instruct the
     user to run the save on the remote machine or use the -L option.

     The directive files (see nsr(4)) encountered in each directory will be
     read by default, and they contain special instructions directing how
     particular files are to be saved (i.e. compressed, skipped, etc.).  These
     files are named '.nsr'.

     Each file in the subdirectory structures specified by the path arguments
     will be encapsulated in a NetWorker save stream.  This stream of data is
     sent to a receiving process (see nsrd(1M)) on the NetWorker server, which
     will process the data, adding entries to the on-line index (see
     nsrindexd(1M)) for each file in the stream, with the data finally ending
     up on some long term storage media (see nsrmmd(1M)).

     Details about handling media are discussed in nsrmm(1M) and


     -E   Estimate the amount of data which will be generated by the save,
          then perform the actual save.  Note that the estimate is generated
          from the inode information, and thus the data is only actually read

     -I input_file
          In addtion to taking the paths to save from the command line, read
          paths to save from the named file.  The paths must be listed one per
          line.  If no paths are specified on the command line, then only
          those paths specified in the file will be saved.

     -i   Ignore any .nsr directive files as they are encountered in the
          subdirectory structures being saved.

     -L   Local.  Saves will be performed from the local NetWorker client,
          even when files are from a network file server.  To recover these
          files, run recover(1M) with the -c client arguments, where client is
          the name of the NetWorker client that did the save.

     -LL  In additional to treating the backup as a local backup, cause an
          extra line to be printed at the end of the completion output of the
          form ``complete savetime=number'', where number is the savetime of
          the save set created by this backup.  This option is meant to be
          used by the savegrp(1M) command in performing automatic cloning.

     -m masquerade
          Specifies the tag to precede the summary line with.  This option is
          used by savegrp(1M) and savefs(1M) to aid in savegrp summary

     -n   No save.  Estimate the amount of data which will be generated by the
          save, but do not perform the actual save.

     -v   Verbose.  Cause the save program to tell you in great detail what it
          is doing as it proceeds.

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

     -s server
          Specify which machine to use as the NetWorker server.  The default
          is the current machine if it is running a server, otherwise the
          machine with the logical name ``nsrhost'' in the host table (see
          hosts(4)) is used.

     -c client-name
          Specify the client name for starting the save session.  This is
          useful on clients with multiple network interfaces, and hence
          multiple host names.  It can be used to create multiple index
          databases for the same physical client.  Note that this does not
          specify the network interface to use.  This is specified in the
          server network interface attribute of the client resource (see

     -N name
          The symbolic name of this save set.  By default, the most common
          prefix of the path arguments is used as the save set name.

     -e expiration
          Sets the date (in nsr_getdate(3) format) when this save set will
          expire.  By default, no explicit save set expiration date is used.

     -f dirfile
          The file from which to read prototype default directives (see
          nsr(4)).  A dirfile of - causes the default directives to be read
          from standard input.

     -b pool
          Specifies a particular destination pool for the save.

     -F file
          Only save files whose change time is newer than the file
          modification date of file.

     -g group
          This option is used by savegrp(1M) and savefs(1M) to denote the
          group of the save (see nsr_client(4) and nsr_group(4)) and is used
          by the NetWorker server to select the specific media pool.

     -l level
          The level of the save.  This option is used by savegrp(1M) and
          savefs(1M) to specify a particular level for a scheduled save.

     -t date
          The date (in nsr_getdate(3) format) after which files must have been
          modified before they will be saved.  This option is used by
          savegrp(1M) and savefs(1M) to perform scheduled saves by consulting
          with the media database to determine the appropriate time value
          based on the previous saves for the save set and the level of the
          scheduled save.

     -W width
          The width used when formatting summary information output.

     -x   Cross mount points.

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


     curses(3X), nsr_getdate(3), hosts(4), nwadmin(1M), nsr(4), nsr(1M),
     nsr_client(4), nsr_device(4), nsr_group(4), nsr_service(4), nsrd(1M),
     nsrindexd(1M), nsrmm(1M), nsrmmd(1M), nsrwatch(1M), recover(1M),
     savefs(1M), savegrp(1M)


   Exit Codes
     0    Normal exit.  This means that a save set was correctly created on
          the server.  Messages about individual file backup failures are
          warnings, and do not cause abnormal exit.
     1    Abnormal exit.  A save set was not correctly created on the server.

     host: saveset   level=level,  size   time  count files.
          This message (with the appropriate client host name, saveset name,
          level, total save set size, elapsed time, and file count) is printed
          whenever save is run by savegrp(1M) and exits normally.

     host: filename: warning
          Messages of this form are warnings about difficulties backing up
          individual files.  Such messages do not normally cause the save to
          fail, and therefore may appear in the save output found in the
          ``Savegroup Completion'' message's Successful section.

home/search | what's new | help