


SAVEGRP(8)                                             SAVEGRP(8)


NNAAMMEE
       savegrp  - start a group of NetWorker clients saving their
       filesystems

SSYYNNOOPPSSIISS
       ssaavveeggrrpp [ _o_p_t_i_o_n_s ] [ --RR | --GG ] [ ggrroouuppnnaammee ]

       _o_p_t_i_o_n_s:  [ --EEIIOOFFXXmmnnppvv ] [ --ll _l_e_v_e_l | --CC _s_c_h_e_d_u_l_e ]  [  --ee
                 _e_x_p_i_r_a_t_i_o_n  ]  [  --tt  _d_a_t_e ] [ --rr _r_e_t_r_i_e_s ] [ --PP
                 _p_r_i_n_t_e_r ] [ --WW _w_i_d_t_h ] [ --cc _c_l_i_e_n_t [  --cc  _c_l_i_e_n_t
                 ... ] ]


       DDEESSCCRRIIPPTTIIOONN
              The  ssaavveeggrrpp  command  runs  a  group  of NetWorker
              clients  through  the  process  of   saving   their
              filesystems  (using ssaavvee(8)).  The group of clients
              is  selected  by  naming  a  NetWorker  group  (see
              nnssrr__ggrroouupp(5)), from which individual clients can be
              selected by using one or more --cc  options.   If  no
              group   name  is  specified,  the  NetWorker  group
              DDeeffaauulltt is used.  If a NetWorker  group  is  named,
              clients  whose  nnssrr__cclliieenntt(5) resources specify the
              named group in their _g_r_o_u_p attribute will be saved.
              If an explicit client list is also specified, ssaavvee--
              ggrrpp will only back up those clients,  with  respect
              to the named group.  The ssaavveeggrrpp command will auto-
              matically make a clone of the newly saved data when
              the appropriate attributes are set on the NNSSRR ggrroouupp
              resource (see below).

       The ssaavveeggrrpp  command  is  normally  run  automatically  by
       nnssrrdd(8),   as   specified  by  each  group's  nnssrr__ggrroouupp(5)
       resource.

       The ssaavveeggrrpp command will  set  up  an  RPC  connection  to
       nnssrreexxeeccdd(8)  to  run ssaavvee(8) on each client (and will fall
       back on using the rrccmmdd(3)  protocol  and  the  client-side
       rrsshhdd(8) if nnssrreexxeeccdd is unavailable on the client) for each
       filesystem listed in the nnssrr__cclliieenntt(5) resource  _s_a_v_e  _s_e_t
       attribute.   If  a  save  set  of  _A_l_l  is specified for a
       client, ssaavveeggrrpp will request from the  client  a  list  of
       filesystems  to  be saved (this is called the _p_r_o_b_e opera-
       tion).  The probe expands _A_l_l into a list by  looking  for
       filesystems  that are both local and automatically mounted
       on that client machine (e.g. NFS mount points and filesys-
       tems  mounted  manually are generally ignored).  The exact
       determination of  which  filesystems  to  save  will  vary
       between  different  operating  systems.  See ssaavveeffss(8) for
       additional details on the probe operation.  To  see  which
       filesystems  a  client  will  save  run a savegrp preview,
       _s_a_v_e_g_r_p _-_c _c_l_i_e_n_t  _-_p  (assuming  the  client  is  in  the
       Default  group).   Each  filesystem saved is called a _s_a_v_e
       _s_e_t.



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        1





SAVEGRP(8)                                             SAVEGRP(8)


       The ssaavveeggrrpp command attempts to keep multiple clients busy
       by  individually scheduling the client save sets.  As save
       sets complete, the output is collected  and  another  save
       set will be started by ssaavveeggrrpp.

       The  ppaarraalllleelliissmm  attribute in the nnssrr__sseerrvviiccee(5) resource
       is the maximum number of save sets to run  simultaneously.
       Modifications  to  this parameter will take effect as save
       sets complete - if the value is reduced, no new  save  set
       will  be started until the number of active save sets run-
       ning drops below the new value.

       When all of the save sets are completed on a  client,  the
       client's  index on the NetWorker server will be saved.  If
       the NetWorker server is one of the machines  being  saved,
       its  index  will  be saved after all the other clients are
       completely done.  When the server's index  is  saved,  the
       bootstrap  save  set  information  will  be printed to the
       default printer (or another specified printer).  If  ssaavvee--
       ggrrpp detects that the NetWorker server is not listed in any
       active group (a group with its autostart  attribute  set),
       then  the  server's index and bootstrap will be saved with
       every group.

       The ssaavveeggrrpp command will detect other  active  invocations
       of  the  same  group, and will exit with an error message.
       If two different NetWorker groups are  running  simultane-
       ously,  they each will run up to _p_a_r_a_l_l_e_l_i_s_m save sessions
       simultaneously, however, the NetWorker  server  will  only
       allow _p_a_r_a_l_l_e_l_i_s_m of these sessions to write to the backup
       devices at a time.  Note  that  running  multiple  ssaavveeggrrpp
       commands  simultaneously  can  use  up  significant server
       resources, due to the number of pending saves.

       The progress of the actively saving clients can  be  moni-
       tored  using  the  X11  based  nnwwaaddmmiinn(8)  program  or the
       ccuurrsseess(3X) based  nnssrrwwaattcchh(8)  program.   The  nnssrraaddmmiinn(8)
       browser  may also be used to examine the _c_o_m_p_l_e_t_i_o_n status
       and _w_o_r_k _l_i_s_t of each _N_S_R  _g_r_o_u_p  resource,  although  the
       _h_i_d_d_e_n  attribute  display option will need to be selected
       (see nnssrraaddmmiinn(8)).  These two  attributes  allows  you  to
       track  the progress of each savegrp.  See nnssrr__ggrroouupp(5) for
       more details.

       When ssaavveeggrrpp starts, it sends  an  NNSSRR  nnoottiiffiiccaattiioonn  (see
       nnssrr__nnoottiiffiiccaattiioonn(5)) with an event of ssaavveeggrrpp and priority
       of iinnffoo to the NSR notification  system.   This  event  is
       normally  logged in the _m_e_s_s_a_g_e_s attribute of the nnssrr__sseerr--
       vviiccee(5) resource, and also logged in the log  file  speci-
       fied in the _L_o_g _d_e_f_a_u_l_t NSR notification resource.

       When  all  the  save sets have finished, the save sets are
       automatically cloned, if the NNSSRR ggrroouupp  resource  has  the
       cclloonneess  attribute enabled.  The client save sets and their



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        2





SAVEGRP(8)                                             SAVEGRP(8)


       indexes are cloned before the bootstrap save set is gener-
       ated so the bootstrap information can track both the orig-
       inal set of save sets and  their  clones.   The  bootstrap
       save  set is also cloned.  Clones will be sent to the pool
       named in the cclloonnee ppooooll attribute.  Changing the values of
       these  attributes  while ssaavveeggrrpp is running has no effect;
       they must be set before ssaavveeggrrpp starts.   The  nnssrrcclloonnee(8)
       command  is  used  to  clone the save sets.  Since ssaavveeggrrpp
       uses a heuristic to determine which save sets were  gener-
       ated  as part of the group, it may occasionally clone more
       save sets than expected, if a client has  its  filesystems
       separated  into multiple groups that run at the same time.
       Note that at least two enabled  devices  are  required  to
       clone save sets.

       When the save sets are all complete and cloned (if cloning
       is enabled), an NNSSRR nnoottiiffiiccaattiioonn with an event of  ssaavveeggrrpp
       and  priority  of  nnoottiiccee  is sent to the NSR notification
       system.  This is generally set up to cause  e-mail  to  be
       sent  to  the rroooott user specifying the list of clients who
       failed (if any), and all the  output  collected  from  all
       clients.  The format and common error messages included in
       the savegrp notification are explained in the SSAAVVEEGGRRPP CCOOMM--
       PPLLEETTIIOONN NNOOTTIIFFIICCAATTIIOONN MMEESSSSAAGGEE section, below.


OOPPTTIIOONNSS
       --EE     Cause ssaavvee(8) on each client to estimate the amount
              of data which will be generated by  each  save  set
              before  performing  it.   This  will  result in the
              filesystem trees being walked twice - once to  gen-
              erate  a  estimate of how much data would be gener-
              ated, and again to generate a save  stream  to  the
              NetWorker  server.  Note that the data is only read
              from the disk on the final filesystem walk, as  the
              estimate is performed by using inode information.

       --II     Disable the saving of each client's index.

       --OO     Only  save each client's index (for the server, the
              bootstrap is also saved).

       --mm     Disable monitor status reporting, including all NNSSRR
              nnoottiiffiiccaattiioonn actions.

       --nn     No  save.   Cause  ssaavvee  to  perform an estimate as
              described for --EE, but not  to  perform  any  actual
              saves.  This option also sets --mm..

       --pp     Run  the  probe step on each client, so you can see
              which filesystem would be saved and at what  level,
              but  do  not  actually  save any data.  This option
              also sets --mm..   The  output  generated  by  the  --pp
              option  may  show several save levels for each save



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        3





SAVEGRP(8)                                             SAVEGRP(8)


              set at different points in the output,  as  ssaavveeggrrpp
              learns  the  correct  level.   This is the expected
              behavior, and can be  useful  for  debugging.   The
              actual level the savegrp will use will be shown the
              last time each save set is  shown  in  the  output.
              The media pool the save set would be directed to is
              also listed in the preview output.

       --vv     Verbose.  Print extra information about what  ssaavvee--
              ggrrpp  is doing, and do not pass the --qq flag along to
              ssaavvee so it too will be chatty.

       --GG     Just run the group;  apply  no  restart  semantics.
              This  is  the default mode of operation; the option
              is provided for compatibility with  other  versions
              of ssaavveeggrrpp.

       --RR     Restart.   Use the information stored with the Net-
              Worker server to restart a group  which  previously
              was  terminated,  generally  due  to a crash of the
              NetWorker server machine.

       --ll _l_e_v_e_l
              The level of save (see nnssrr__sscchheedduullee(5)) to  perform
              on  each  client.   This  overrides  the save level
              which ssaavveeggrrpp would normally automaticly determine.
              --ll and --CC cannot be specified together.

       --CC _s_c_h_e_d_u_l_e
              The  name of the NNSSRR sscchheedduullee (see nnssrr__sscchheedduullee(5))
              to be used in the automatic  save  level  selection
              process  which  ssaavveeggrrpp  normally  performs.   This
              overrides the save  schedule  which  ssaavveeggrrpp  would
              normally  use for a given client.  --ll and --CC cannot
              be specified together.

       --ee _e_x_p_i_r_a_t_i_o_n
              Set the date (in nnssrr__ggeettddaattee(3)  format)  when  the
              saved  data will expire.  The special value ffoorreevveerr
              is used  to  indicate  that  a  volume  that  never
              expires  (i.e.  an  archive  or a migration volume)
              must be used.  By default, no  explicit  expiration
              date is used.

       --tt _d_a_t_e
              The  time  to  use  instead of the current time for
              determining which level to use for this savegrp (in
              nnssrr__ggeettddaattee(3)  format).   By  default, the current
              time is used.

       --FF     Automatically perform a full level backup  if  save
              set  consolidation fails. This option is ignored if
              the backup level is not "c".




NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        4





SAVEGRP(8)                                             SAVEGRP(8)


       --XX     Automatically remove the level  1  save  set  after
              save  set  consolidation  builds  a full level save
              set.  This option is ignored if the backup level is
              not  "c". It is also ignored if the backup level is
              "c" but the save set consolidation process fails.

       --rr _r_e_t_r_i_e_s
              The  number  of  times  failed  clients  should  be
              retried  before  ssaavveeggrrpp gives up and declares them
              failed.   The  default  is  taken  from  the  group
              resource.  Abandoned saves are not retried, because
              they may  eventually  complete.   Retries  are  not
              attempted if --pp is specified.

       --PP _p_r_i_n_t_e_r
              The  printer  which ssaavveeggrrpp should use for printing
              bootstrap information.

       --WW _w_i_d_t_h
              The width used when formatting output or  notifica-
              tion messages.  By default, this is 80.

       _g_r_o_u_p  Specifies  the  NetWorker  group  of  clients  that
              should be started,  rather  than  the  default  NSR
              group  (which  has  the nnaammee attribute of ddeeffaauulltt).
              See nnssrr__ggrroouupp(5) for more details.

       --cc _c_l_i_e_n_t
              The name of a client on which to save  filesystems.
              There  can  be  multiple  --cc _c_l_i_e_n_t specifications.
              When --cc  options  are  specified,  only  the  named
              clients   from   the   specified  group  (which  is
              "Default" if no group is specified) will be run.

RREESSOOUURRCCEE TTYYPPEESS
       NNSSRR          Use the ppaarraalllleelliissmm attribute for the maximum
                    number of saves to start simultaneously.
       NNSSRR ggrroouupp    The  attribute  _w_o_r_k  _l_i_s_t contains values in
                    groups of  3,  specifying  the  client  name,
                    level  of  save,  and  path to save, for each
                    save set not yet  completed.   The  attribute
                    _c_o_m_p_l_e_t_i_o_n  contains  values  in groups of 4,
                    specifying the client name, path saved,  sta-
                    tus,  and  the output, for each save set com-
                    pleted.
       NNSSRR sscchheedduullee Used  by  the  ssaavveeggrrpp  command   with   each
                    client's  nnssrr__cclliieenntt(5) resource to determine
                    which level of save to perform for each spec-
                    ified save set.
       NNSSRR cclliieenntt   Each  client  resource  names  the  groups it
                    should be saved by, the  names  of  the  save
                    sets  which  should be saved, the name of the
                    schedule to use (see  nnssrr__sscchheedduullee(5)).   and
                    the  name  of  the  directives  to  use  (see



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        5





SAVEGRP(8)                                             SAVEGRP(8)


                    nnssrr__ddiirreeccttiivvee(5)).
       NNSSRR nnoottiiffiiccaattiioonn
                    Three kinds of notices are sent  to  the  NSR
                    notification  system,  both  with  the  eevveenntt
                    attribute of _s_a_v_e_g_r_p.  While a savegrp is  in
                    progress,  status  notices  are sent with the
                    pprriioorriittyy of _i_n_f_o.  At completion of  a  save-
                    grp,  a  notice  is  sent containing the col-
                    lected output of all saves, and the  name  of
                    clients  which  had  a  save which failed (if
                    any).  This notice will have an eevveenntt type of
                    _s_a_v_e_g_r_p,  and a pprriioorriittyy of _n_o_t_i_c_e.  If ssaavvee--
                    ggrrpp is  interrupted,  a  notice  stating  the
                    group  was  terminated, with an eevveenntt type of
                    _s_a_v_e_g_r_p, and a  pprriioorriittyy  of  _a_l_e_r_t  will  be
                    sent.   These  last two typically will result
                    in the notice being encapsulated  in  a  mail
                    message to rroooott.

SSAAVVEEGGRROOUUPP CCOOMMPPLLEETTIIOONN NNOOTTIIFFIICCAATTIIOONN MMEESSSSAAGGEE
       The  savegroup  completion notification message contains 5
       parts: the header, the Never Started Save Sets, the Unsuc-
       cessful  Save  Sets,  the  Successful  Save  Sets, and the
       Cloned Save Sets.  Each client in the group will be listed
       in  one  or  more of sections categories (more than one if
       some save sets are in one category, and other save sets in
       another category).  The clients are listed in alphanumeric
       sorted order, with the server listed last.

       The header shows the name of the  group  and  lists  which
       clients  failed.   If  the  group  was aborted, the header
       includes an indicator of this as well.   The  header  also
       shows the time the group was started (or restarted, if the
       --RR option was used), and the time the  savegrp  completed.
       The  failed  clients  list  in the header shows only those
       clients for which saves  were  attempted,  not  those  for
       which saves never started.

       The  Never  Started Save Sets section is optional and will
       only be included if there  are  some  save  sets  of  some
       clients in the group that were never started.  This should
       only occur when a savegrp is aborted,  either  by  killing
       the  master  savegrp daemon or by selecting the _S_t_o_p func-
       tion in the _G_r_o_u_p _C_o_n_t_r_o_l window or the _S_t_o_p _N_o_w attribute
       in  the  _G_r_o_u_p window of nnwwaaddmmiinn(8).  Each entry listed in
       this section shows the client and save set that was  never
       started  (or  _A_l_l  if  no  save  sets  were saved for that
       client).  No other error messages should  appear  in  this
       section.

       The  Unsuccessful Save Sets section shows all of the saves
       that were attempted but failed.  This section will only be
       present  if  at least one save set failed.  There are many
       reasons for a save to fail.  The most  common  are  listed



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        6





SAVEGRP(8)                                             SAVEGRP(8)


       below.   More reasons will be listed in the future.  It is
       important to differentiate between the many reasons for  a
       save to fail, so that the administrator can quickly deter-
       mine the cause and fix it, so the save  will  succeed  the
       next time.

       Each entry in the Unsuccessful Save Sets section lists the
       client and save set that failed, along with  one  or  more
       lines  of  error and information messages.  Each client is
       separated by a blank line, and all the  failed  save  sets
       for a client a listed together.  Typical error or informa-
       tion messages are listed  at  the  end  of  this  section,
       (without  the  client:saveset  prefix), with the necessary
       action(s) to take to correct the problem.

       Each entry in the Successful Save Sets section  lists  the
       client  and  save  set that succeeded, along with level of
       the save, the amount of data saved, the time  to  run  the
       save  set,  and the number of files saved.  Each entry may
       also be preceded by one or more warning  or  informational
       messages,  the  most  common  of  which  are listed below.
       These warning or informational messages are  usually  (but
       not  always)  prefixed  by ``* ''.  Note that a save set's
       output may include warnings; these do not necessarily mean
       the  save set was unsuccessful.  See ssaavvee(8) for the defi-
       nitions a successful and unsuccessful save sets.

       The  Cloned  Save  Sets  section  is  somewhat  different,
       because  it  refers  to  the save sets cloned, and not the
       clients that originated those save sets.  The output shown
       in  this  section  is  the output of the nnssrrcclloonnee command.
       See the nnssrrcclloonnee(8) man page for information on the output
       of nnssrrcclloonnee.

       The  following  is a list of common informational, warning
       and error messages found in the  completion  notification.
       This list is not complete.  Note that the messages you see
       may vary slightly from those shown here due to differences
       in  the  operating  system vendor-supplied error messages.
       Since many messages include client or server names, it  is
       most efficient to look for a keyword in the error message.
       The messages are listed below in  alphabetical  order,  by
       the  first non-variable word in the message (note: initial
       words like "save", "asm" and "savefs" may or may not vary,
       and initial pathnames are always assumed to vary).

       aabboorrtteedd
              This  informational  message  only  occurs when you
              abort a running  savegrp,  generally  by  selecting
              _S_t_o_p  from  the  Group  Control Window of the nnwwaadd--
              mmiinn(8) interface.  It means that the specified save
              set  had started saving, but had not completed when
              the savegrp was aborted.  The session (in the  Ses-
              sions  display of nnwwaaddmmiinn(8)) for this save set may



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        7





SAVEGRP(8)                                             SAVEGRP(8)


              not disappear immediately, especially if  ssaavveeggrrpp's
              attempt  to  kill the save session fails.  The save
              set will be retried if and  when  you  _R_e_s_t_a_r_t  the
              savegrp (e.g. from the Group Control Window).

       AAcccceessss vviioollaattiioonn ffrroomm _c_l_i_e_n_t -- iinnsseeccuurree ppoorrtt _N
              This  message,  generated  by  the  ssaavvee command on
              client, means that ssaavvee is not setuid  root.   Make
              sure  that  the ssaavvee command on the client is owned
              by root and has its setuid bit set.  If ssaavvee is  on
              an NFS mounted filesystem, make sure the filesystem
              was not mounted on that client using the  "-nosuid"
              option.

       AAcccceessss vviioollaattiioonn -- uunnkknnoowwnn hhoosstt:: _c_l_i_e_n_t
              This message is caused when then the client's host-
              name and IP address are not correctly listed in one
              or  more  of  /etc/hosts, NIS or DNS on the server.
              You need to  either  change  the  appropriate  host
              table (depending on which one(s) are in use on your
              server) to list the client's name as it is know  to
              NetWorker,  as  that  client's primary name, or you
              need to add the name listed at the end of the error
              message  to  the  _a_l_i_a_s_e_s attribute of the client's
              Client resource(s).

       _a_s_m:: ccaannnnoott ooppeenn _p_a_t_h:: II//OO eerrrroorr
              This message generally means  that  there  are  bad
              blocks on the disk(s) containing the specified file
              or  directory.   You  should  immediately   run   a
              filesystem check on the named client filesystem and
              check your client's system error log.  If there are
              bad  block,  repair  them  if possible, or move the
              filesystem to a different disk.

       _a_s_m:: ccaannnnoott ssttaatt _p_a_t_h:: SSttaallee NNFFSS ffiillee hhaannddllee
       _a_s_m:: ccaannnnoott ssttaatt _p_a_t_h:: MMiissssiinngg ffiillee oorr ffiilleessyysstteemm
              These informational messages (or variants  of  them
              for  other  operating  systems)  mean that the when
              ssaavvee attempted  to  test  the  named  directory  to
              determine if it was a different filesystem from the
              one currently being saved, the filesystem  was,  in
              fact  NFS  mounted,  but  the  mount point was bad.
              While this message does not affect the saved  data,
              it  does  mean  you  have  a network or NFS problem
              between the specified client and one or more of its
              fileservers.   You  may need to remount filesystems
              on the client, or perhaps reboot it, to correct the
              problem.

       _/_p_a_t_h//nnssrreexxeeccdd:: CCaann''tt mmaakkee ppiippee
       _/_p_a_t_h//nnssrreexxeeccdd:: CCaann''tt ffoorrkk
       ffoorrkk:: NNoo mmoorree pprroocceesssseess
              The   specified   client-side   resource  has  been



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        8





SAVEGRP(8)                                             SAVEGRP(8)


              exceeded.  There are too many other  services  run-
              ning  on  the  client  while  savegrp  is  running.
              Inspect the client and determine why it has run out
              of  resources.  The client may need to be rebooted.
              You should also  consider  re-scheduling  any  jobs
              automatically  started  on  the  client  (e.g.  via
              ccrroonn(8)) that run while savegrp is running.

       _a_s_m:: cchhddiirr ffaaiilleedd _p_a_t_h:: PPeerrmmiissssiioonn ddeenniieedd
              This message means that while backing up the speci-
              fied  save  set, ssaavvee was unable to enter the named
              directory.  This may mean that ssaavvee is  not  setuid
              root on the specified client, or that the directory
              is actually an NFS mount point for  which  root  is
              not  allowed access.  Check the permissions on ssaavvee
              on the specified client (using llss(1)) and make sure
              that  ssaavvee is owned by root and that the setuid bit
              is set.

       ccoonnnneecctt ttoo aaddddrreessss AAAA..BBBB..CCCC..DDDD:: _m_e_s_s_a_g_e
       TTrryyiinngg AAAA..BBBB..CCCC..DDDD......
              These informational  messages  are  displayed  only
              when  the  --vv  option  is used.  They mean that the
              connection to the  client  failed  on  the  address
              specified in the first line of the message.  If the
              client has more than one IP  address,  savegrp  has
              attempted  the  address  listed in the second line.
              Looking at subsequent lines of the completion  mail
              show  if  this  second  address succeeded.  You may
              want to  check  and  change  your  network  routing
              tables to avoid getting these messages.

       CCoonnnneeccttiioonn rreeffuusseedd
              This  means the client machine is up, but it is not
              accepting new network connections for nnssrreexxeeccdd  (or
              rrsshhdd).   This could mean the client was in the pro-
              cess of booting when the savegrp attempted to  con-
              nect, or that the client had exceeded some resource
              limit, and was not accepting any  new  connections.
              You  should attempt to log into the client and ver-
              ify that it is accepting  remote  connections.   If
              the  client  is a non-Unix machine, you may need to
              start the NetWorker client on that machine.   Refer
              to  your  ClientPak  installation for more informa-
              tion.

       CCoonnnneeccttiioonn ttiimmeedd oouutt
              This usually means the client  has  crashed  or  is
              hung.   Make sure the client has rebooted, and that
              nnssrreexxeeccdd is running on it (if you are using  nnssrreexx--
              eeccdd).  If the client is a non-Unix machine, you may
              need to  ensure  that  the  network  protocols  are
              loaded, and that the NetWorker client is running on
              that machine.  Refer to your ClientPak installation



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                        9





SAVEGRP(8)                                             SAVEGRP(8)


              for more information.

       _a_s_m:: eexxtteerrnnaall AASSMM ``_a_s_m_2'' eexxiitteedd wwiitthh ccooddee 11
              This  message generally accompanies another message
              reporting a specific problem while saving a file or
              directory  on  the named save set.  The backup will
              attempt to continue and attempt to save other data,
              and generally, the backup will not be listed in the
              failed save sets section of the completion mail  if
              any  files  on the save set are saved successfully,
              even if it only saves the top directory of the save
              set.

       ssaavvee:: _p_a_t_h ffiillee ssiizzee cchhaannggeedd!!
              This  informational message is often generated when
              NetWorker backs up log files.  It  may  also  occur
              for other files.  For files that you expect to grow
              while ssaavveeggrrpp is running, you can use  a  directive
              specifying  that  the  llooggaassmm(8)  should be used to
              back up the file.  See also nnssrr(5)  and  nnssrr__ddiirreecc--
              ttiivvee(5).

       _a_s_m:: ggeettwwdd ffaaiilleedd
              This message means that while backing up the speci-
              fied save set, an attempt to determine the  current
              directory's  name  failed.  This occurs on clients,
              generally running older versions of  the  NetWorker
              ClientPak,  on  which  the ggeettwwdd(3) library call is
              broken.  You may want to contact Legato  Tech  Sup-
              port  to find out if there is a patch available for
              your client platform to work  around  this  vendor-
              specific bug, or contact your operating system ven-
              dor to see if a more recent O.S. version  addresses
              this problem.

       ggrroouupp _g_r_o_u_p_n_a_m_e aabboorrtteedd,, ssaavveeggrrpp iiss aallrreeaaddyy rruunnnniinngg
              This  message  is  only  delivered  by  itself.  It
              occurs  when  the  named  group  has  already  been
              started  or  restarted  (eg after a reboot, or when
              requested via the Group  Control  Window  of  nnwwaadd--
              mmiinn(8)),  either  automatically by nnssrrdd(8) or manu-
              ally, from the command line.  You can use ppss(1)  to
              find  out the process id of a running savegrp.  The
              existance of a running group is determined by look-
              ing  for  a  file named //nnssrr//ttmmpp//ssgg.._g_r_o_u_p which, if
              existing and locked, means a savegrp is running.

       hhaass bbeeeenn iinnaaccttiivvee ffoorr _N mmiinnuutteess ssiinnccee _t_i_m_e..
       _c_l_i_e_n_t_:_s_a_v_e_s_e_t iiss bbeeiinngg aabbaannddoonneedd bbyy ssaavveeggrrpp..
              A backup of the specified  save  set  started,  but
              after _N minutes of no activity, and ssaavveeggrrpp gave up
              on the save set.  Generally, this  means  that  the
              client  is  hung  waiting  for  an  NFS  partition.
              Unfortunately, NetWorker (or any other program) has



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                       10





SAVEGRP(8)                                             SAVEGRP(8)


              no way of reliably telling if an NFS partition will
              hang until after it tries to access the  partition.
              When  the  partition  comes  back on line, the save
              will complete, despite the fact that ssaavveeggrrpp  aban-
              doned  it.   You  should check the client, however,
              since you sometimes need to reboot  the  client  to
              unhang  NFS partitions.  Non-Unix clients also hang
              for other reasons, most notably, bugs in the  oper-
              ating system implementation of their network proto-
              cols.

       HHoosstt iiss uunnrreeaacchhaabbllee
              The NetWorker server cannot make TCP/IP connections
              to  the  client.   This generally means the network
              itself is not configured correctly; most  commonly,
              one  or  more  gateways or routers are down, or the
              network routes were  not  set  up  correctly.   You
              should  verify  that  the server can connect to the
              client, and if not, check and, if necessary, recon-
              figure your routers, gateways or routing tables.

       LLooggiinn iinnccoorrrreecctt
              This  message  is  generated  when  the _r_e_m_o_t_e _u_s_e_r
              attribute for the client is  not  set  to  a  valid
              login  on  the client.  Verify that the _r_e_m_o_t_e _u_s_e_r
              attribute for the client  is  set  to  the  correct
              login  name.   You  may  see this message even when
              running nnssrreexxeeccdd if nnssrreexxeeccdd has not  been  started
              (or was killed) on the client.

       _a_s_m:: mmiissssiinngg hhaarrdd lliinnkkss nnoott ffoouunndd::
              This message is generated when a backed-up file had
              one or more hard links that were  not  found.   The
              message  is  followed by a list of one or more file
              names which were backed up minus some  links.   The
              message  means  that  the files were either created
              (with multiple hard links)  while  the  backup  was
              occurring,  so some of the links were missed due to
              the order of filesystem tree walking, or  the  file
              (or  some  links) were removed while the backup was
              occurring.  Only those links that were found can be
              recovered;  additional  links  will have been lost.
              One can do an additional incremental backup of  the
              affected  filesystem  if a consistent state for the
              affected file is essential.

       lloosstt ccoonnnneeccttiioonn ttoo sseerrvveerr,, eexxiittiinngg
       ssaavvee:: nneettwwoorrkk eerrrroorr,, sseerrvveerr mmaayy bbee ddoowwnn
              The backup of the named filesystem was  begun,  but
              the  connection to the NetWorker server closed part
              way through.  This typically means that the  server
              machine rebooted, one or more NetWorker server dae-
              mon processes were killed by the system administra-
              tor   or   by   the  system  itself  (e.g.  due  to



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                       11





SAVEGRP(8)                                             SAVEGRP(8)


              overwriting the binary or  a  disk  error  in  swap
              space),  or  there  was some transport problem that
              caused the network connection  to  dropped  by  the
              operating  system.   Restart  the  save  at a later
              time.
       nnoo ccyycclleess ffoouunndd iinn mmeeddiiaa ddbb;; ddooiinngg ffuullll ssaavvee
              This informational message is added by  ssaavveeggrrpp  to
              any  save  set  that  is  saved  at  the level _f_u_l_l
              instead of the level found in the  client's  sched-
              ule.   Due to timing problems, you can occasionally
              see this message when the clocks on the client  and
              server  are  out  of  sync,  or when ssaavveeggrrpp starts
              before midnight and ends after midnight.   You  may
              also  get  spurious messages of this type from some
              versions of NetWorker client software backing up  a
              NetWare BINDERY, which ignore the schedule and per-
              form a full, no matter what.  In both these  cases,
              the  client  re-checks the level, and overrides the
              server's requested level.
       NNoo mmoorree pprroocceesssseess
              See "Can't make pipe", above.
       NNoo ''NNSSRR cclliieenntt'' rreessoouurrccee ffoorr cclliieenntt _c_l_i_e_n_t_h_o_s_t_n_a_m_e
       ssaavveeffss:: ccaannnnoott rreettrriieevvee cclliieenntt rreessoouurrcceess
              This pair of messages occurs if  the  the  client's
              hostname  changed (in /etc/hosts, NIS or DNS).  You
              may also have deleted the client's _C_l_i_e_n_t  resource
              while savegrp was running.  In the former case, you
              will need to add  the  client's  new  name  to  the
              _a_l_i_a_s_e_s  attribute  of the client (this is a hidden
              attribute) using nnssrraaddmmiinn(8) (selecting the  _H_i_d_d_e_n
              display   option)   or  nnwwaaddmmiinn(8)  (selecting  the
              _D_e_t_a_i_l_s _V_i_e_w option for the _C_l_i_e_n_t window).  In the
              latter  case,  no  additional action is required if
              this deletion was  intentional  (the  next  run  of
              ssaavveeggrrpp  will  not attempt to save the client).  If
              it was accidental, and you did not want  to  delete
              the  client,  you  should add the client back again
              and  add  the  client  back  into  the  appropriate
              group(s).  The next time ssaavveeggrrpp runs, it will back
              up the client, just as if the client had been  down
              the previous day.

       nnoo oouuttppuutt
              The save set completed, but returned no status out-
              put.  The most common reasons are that  the  client
              crashed  or  lost  its  network connection (i.e.. a
              router between the client and server crashed) while
              the  client  was  being backed up.  Another is that
              the disk on  which  the  client  status  was  being
              logged  filled  up (perform a ddff //nnssrr//ttmmpp to see if
              this was the case).  To determine if the  save  set
              was saved, you can use mmmmiinnffoo(8).  For example, run
              mmmmiinnffoo --vv --cc _c_l_i_e_n_t_n_a_m_e --tt ''11 ddaayy aaggoo'' and look  at
              the _f_l_a_g_s column for the completion status.  An 'a'



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                       12





SAVEGRP(8)                                             SAVEGRP(8)


              flag means it aborted.  Use  a  more  distant  time
              (the --tt option) to look further back in time.

       _f_i_l_e_s_y_s_t_e_m:: NNoo ssuucchh ffiillee oorr ddiirreeccttoorryy
              An  explicit  save  set  was  named  in  the _C_l_i_e_n_t
              resource for the specified client,  and  that  save
              set does not exist (or is not currently mounted) on
              the client.  Make sure you  spelled  the  save  set
              name  correctly  (and  that  it is capitalized cor-
              rectly), and log into the client  and  verify  that
              the save set is mounted.

       _/_p_a_t_h//nnssrreexxeeccdd:: CCoouullddnn''tt llooookk uupp aaddddrreessss ffoorr yyoouurr hhoosstt
       _/_p_a_t_h//nnssrreexxeeccdd:: HHoosstt aaddddrreessss mmiissmmaattcchh ffoorr _s_e_r_v_e_r
              The  nnssrreexxeeccdd  daemon on the client managed to look
              up the server in the client's host table,  but  the
              address  listed  there did not match the address of
              the server.  Every interface  of  the  server  must
              have a unique name listed in the host table (possi-
              bly with non-unique aliases or CNAME's),  and  each
              unique  name  must  be  listed as a valid server to
              nnssrreexxeeccdd.

       _/_p_a_t_h//nnssrreexxeeccdd:: HHoosstt _s_e_r_v_e_r ccaannnnoott rreeqquueesstt ccoommmmaanndd eexxeeccuu--
       ttiioonn
       _/_p_a_t_h//nnssrreexxeeccdd:: YYoouurr hhoosstt ccaannnnoott rreeqquueesstt ccoommmmaanndd eexxeeccuuttiioonn
              The server is not  listed  in  nnssrreexxeeccdd's  list  of
              valid servers on the specified client.  The list of
              valid servers is either  on  the  nnssrreexxeeccdd  command
              line  (with one or more --ss _s_e_r_v_e_r options to nnssrreexx--
              eeccdd), or in a file (with  the  --ff  _f_i_l_e  option  to
              nnssrreexxeeccdd).   If neither is specified, some versions
              of nnssrreexxeeccdd will look for a file named  _s_e_r_v_e_r_s  in
              the  same directory that contains tha _n_s_r_._r_e_s file.
              It may also be the case  that  the  server  is  not
              listed  in  one or more of /etc/hosts, NIS, or DNS,
              on the client, in which case nnssrreexxeeccdd cannot  vali-
              date the server until the client's host naming con-
              figuration is fixed.

       _/_p_a_t_h//nnssrreexxeeccdd:: IInnvvaalliidd aauutthheennttiiccaattoorr
       _/_p_a_t_h//nnssrreexxeeccdd:: IInnvvaalliidd ccoommmmaanndd
              These two messages should never occur  in  a  save-
              group  completion  message.  They mean that ssaavveeggrrpp
              did not follow its protocol correctly.

       _/_p_a_t_h//nnssrreexxeeccdd:: PPeerrmmiissssiioonn ddeenniieedd
       PPeerrmmiissssiioonn ddeenniieedd
              These similar messages are  generated  by  nnssrreexxeeccdd
              and rrsshhdd, respectively.  In either case, the server
              does not have permission to execute commands on the
              client.   In  the  case  of the first message, make
              sure that the server is listed as a valid server on
              the client (see "Host _s_e_r_v_e_r cannot request command



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                       13





SAVEGRP(8)                                             SAVEGRP(8)


              execution", above, for details).  In  the  case  of
              the  second  message, which does not mention nnssrreexx--
              eeccdd, make sure that "_s_e_r_v_e_r_n_a_m_e" is listed  in  the
              client's  _/_._r_h_o_s_t_s  file  (or,  if you have set the
              _r_e_m_o_t_e _u_s_e_r attribute for this client, the  _._r_h_o_s_t_s
              file  in  the  home  directory for that user on the
              client).

       //_p_a_t_h//ssaavveeggrrpp:: pprriinnttiinngg bboooottssttrraapp iinnffoorrmmaattiioonn ffaaiilleedd
              See "unknown printer" below.

       rreeaaddiinngg lloogg ffiillee ffaaiilleedd
              After the specified save set completed, savegrp was
              unable  to  read  the log file of the output status
              from the save set.  This generally means that some-
              one,  or  an automated non-NetWorker administrative
              program or script, removed the log file.  This mes-
              sage  can also occur if the filesystem on which the
              client logs are stored has run out of space (use ddff
              //nnssrr//ttmmpp to determine if this is the case).  Verify
              that no scripts remove files from  _/_n_s_r_/_t_m_p  (which
              is where savegrp stores the save set log files).

       rreeqquueesstt ffrroomm mmaacchhiinnee _s_e_r_v_e_r rreejjeecctteedd
              The server is not listed in the PC (NetWare or DOS)
              client's list  of  acceptable  servers.   See  your
              ClientPak  installation  guide  for instructions on
              adding the server to the client-side list.

       _N rreettrriieess aatttteemmpptteedd
       _1 rreettrryy aatttteemmpptteedd
              One of these informational messages is prepended to
              a save set's output if ssaavveeggrrpp was unable to backup
              the data on the first try and if the _c_l_i_e_n_t _r_e_t_r_i_e_s
              attribute  for  the  group has a value greater than
              zero.   In  this  case,  the  specified  number  of
              retries was performed before the backup of the save
              set succeeded or was finally marked as failed.

       RRPPCC eerrrroorr,, _d_e_t_a_i_l_s_._._.
       CCaannnnoott ooppeenn ssaavvee sseessssiioonn wwiitthh ``_s_e_r_v_e_r''
              The ssaavvee command generates this message  if  it  is
              unable  to  back  up  data to the NetWorker server.
              There  are  several  possible  _d_e_t_a_i_l_s.   The  most
              likely  causes  are:  resources are exceeded on the
              server so nsrd cannot  accept  new  save  sessions,
              nsrd  actually died since savegrp started (however,
              this is unlikely, since you cannot normally receive
              a  savegrp  completion message after nsrd dies, but
              you can see this when using the --pp  option),  there
              are numerous network errors occurring and save can-
              not open a session to save its data (check this  by
              running  nneettssttaatt --ss and see how many network errors
              are occurring; you may  need  to  do  this  several



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                       14





SAVEGRP(8)                                             SAVEGRP(8)


              times  a  few  minutes  apart  to get the change in
              errors).  Save cannot tell  which  of  these  three
              causes are the real cause.  If you see these errors
              frequently, and it looks  like  a  server  resource
              problem, you might consider increasing the value of
              the _c_l_i_e_n_t _r_e_t_r_i_e_s attribute of the ggrroouupp  resource
              having  these  problems.   This  won't decrease the
              resource utilization, but will  make  ssaavveeggrrpp  more
              robust  so  such  problems  (the  trade-off is that
              increasing _c_l_i_e_n_t _r_e_t_r_i_e_s will increase the load on
              the server even more).

       RRPPCC eexxeecc oonn _c_l_i_e_n_t iiss uunnaavvaaiillaabbllee..  TTrryyiinngg RRSSHH..
              This  informational  message is only displayed when
              the --vv flag has been used for verbose  information.
              This  message means that nnssrreexxeeccdd is not running on
              the client, and that savegrp is attempting  to  use
              the  rrsshhdd service instead, for backward compatibil-
              ity with older versions of ssaavveeggrrpp.

       ssaavvee:: _c_l_i_e_n_t_n_a_m_e_2 iiss nnoott oonn _c_l_i_e_n_t''ss aacccceessss lliisstt
              This error occurs when the named  client  has  more
              than  one  name, for example, a short name, _c_l_i_e_n_t,
              and     a     fully-qualified     domain      name,
              _c_l_i_e_n_t_._l_e_g_a_t_o_._c_o_m.   When  the  client  attempts to
              connect back to the NetWorker  server  to  start  a
              save,  that  client  is  calling itself by the name
              _c_l_i_e_n_t, which matches the client resource name, but
              when  the  server  looks  up  the  client's network
              address, it is getting back the  name  _c_l_i_e_n_t_n_a_m_e_2.
              If  this is, in fact, correct, add the name _c_l_i_e_n_t_-
              _n_a_m_e_2 to the client's aalliiaasseess attribute, and re-run
              the save.

       ssaavvee:: ppaatthh lleennggtthh ooff _x_x_x_x ttoooo lloonngg,, ddiirreeccttoorryy nnoott ssaavveedd
              This message can occur if you have a directory tree
              that is very deep, or directory names that are very
              long.  This message can also occur if there are bad
              blocks in  the  specified  filesystem,  or  if  the
              filesystem  is  corrupt.  NetWorker limits the full
              pathname to 1024 characters  which  is  the  system
              imposed  maximum  on  most  systems.   To save such
              directories, you need to rename or move the  direc-
              tories  so  that  the full pathname is shorter than
              1024 characters.  If the filesystem appears  to  be
              corrupted  (for  example, a very long pathname that
              looks like it has a loop in the  name),  perform  a
              filesystem check on the specified client.

       _/_p_a_t_h//ssaavvee:: CCoommmmaanndd nnoott ffoouunndd
       _/_p_a_t_h//ssaavveeffss:: CCoommmmaanndd nnoott ffoouunndd
       _/_p_a_t_h//ssaavvee:: NNoott ffoouunndd
       _/_p_a_t_h//ssaavveeffss:: NNoott ffoouunndd
              The  ssaavvee  or  ssaavveeffss command could not be found in



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                       15





SAVEGRP(8)                                             SAVEGRP(8)


              the specified path.  If  you  are  using  nnssrreexxeeccdd,
              this probably means that the ssaavvee or ssaavveeffss command
              is not in the same directory in which  nnssrreexxeeccdd  is
              installed (or that ssaavvee or ssaavveeffss was removed).  If
              you are using rrsshhdd for remote execution,  then  you
              need  to  set  the _e_x_e_c_u_t_a_b_l_e _p_a_t_h attribute in the
              _C_l_i_e_n_t resource for this client to be the directory
              in which the NetWorker executables are installed on
              the client.

       ssaavveeffss:: eerrrroorr ssttaarrttiinngg ssaavvee ooff _f_i_l_e_s_y_s_t_e_m
              This  informational  message  accompanies   several
              other  ssaavvee or aassmm messages listed here.  This mes-
              sage means that savefs has detected the failed save
              and has marked the save set as failed.

       ssaavvee:: uunnkknnoowwnn hhoosstt nnaammee:: _s_e_r_v_e_r
       ssaavveeffss:: uunnkknnoowwnn hhoosstt nnaammee:: _s_e_r_v_e_r
              The  host  table  on  the  specified client (either
              /etc/hosts, NIS or DNS, depending on that  client's
              configuration)  does not include the server's name.
              You need to add the server's hostname to the speci-
              fied client's host table.  Note that if you use DNS
              but the server's Client  resource  name  (i.e.  the
              client resource for the server itself) is not fully
              qualified  (i.e.  it  looks  like   "server",   not
              "server.dom.ain",  and the server is in a different
              domain from the client, you will need  to  add  the
              name _s_e_r_v_e_r to the domain table for the domain con-
              taining the client.  If you  use  NIS,  this  error
              means  that  either the NIS hosts map does not con-
              tain the server, the _/_e_t_c_/_h_o_s_t_s file does not  list
              the  server,  or  the  NIS master for the specified
              client is otherwise mis-configured (the server is a
              secondary server and there is no yyppppuusshh(8) from the
              primary; run yyppwwhhiicchh --mm on the client to  find  out
              which  NIS server is providing master translation).
       ssaavveeggrrpp:: cclliieenntt rrccmmdd((33)) pprroobblleemm ffoorr ccoommmmaanndd ''_c_o_m_m_a_n_d''
              This error message  normally  accompanies  another,
              more specific, error message.  It is generated when
              the attempt to run the specified  command  (usually
              ssaavvee  or  ssaavveeffss  with several command line parame-
              ters) failed on the specified save set.  The previ-
              ous  line  of  error output should include the more
              specific error message (look for that message else-
              where  in this section).  Generally, the problem is
              a bad hosttable configuration, or  various  permis-
              sions  denied  errors  (server  not  specified when
              starting  nsrexecd,  or  missing   permissions   in
              .rhosts  if  not using nsrexecd).  If not, log into
              the NetWorker server as root and  run  the  command
              ssaavveeggrrpp  --pp  --vv  --cc _c_l_i_e_n_t_n_a_m_e _g_r_o_u_p_n_a_m_e giving the
              appropriate client for _c_l_i_e_n_t_n_a_m_e and  _g_r_o_u_p_n_a_m_e  _.
              This  verbose  output  should include the necessary



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                       16





SAVEGRP(8)                                             SAVEGRP(8)


              additional information needed for fixing the  prob-
              lem.
       SSaavviinngg sseerrvveerr iinnddeexx bbeeccaauussee sseerrvveerr iiss nnoott iinn aann aaccttiivvee
       ggrroouupp
              This informational message, generated  by  ssaavveeggrrpp,
              means  that  savegrp has noticed that the NetWorker
              server is not listed in any automatically  started,
              enabled group.  Since all of the indexes are stored
              on the server, ssaavveeggrrpp is saving the server's index
              and   bootstrap  information  in  case  a  disaster
              occurs.  You should add the server to a group  with
              autostart  enabled,  or enable one of the groups of
              which the server is already a member.
       ssoocckkeett:: AAllll ppoorrttss iinn uussee
              The NetWorker server has run out of socket descrip-
              tors.  This means that you have exceeded the socket
              resource limit  on  your  server.   To  avoid  such
              future  messages,  you  should determine what other
              network services are running while savegrp is  run-
              ning,  and consider re-scheduling either savegrp or
              the other service(s).  You can also reduce the par-
              allelism  in the nnssrr__sseerrvviiccee(5) resource, to reduce
              the resource utilization.
       ssoocckkeett:: pprroottooccooll ffaaiilluurree iinn cciirrccuuiitt sseettuupp..
              The client does not seem to support the TCP/IP pro-
              tocol  stack, or has not used a privileged port for
              setting up its connection.  The latter could  occur
              if you use nnssrreexxeeccdd but did not start it as root on
              the specified client.  The nnssrreexxeeccdd daemon must run
              as root on each client.
       _p_a_t_h:: TThhiiss ddaattaa sseett iiss iinn uussee aanndd ccaannnnoott bbee aacccceesssseedd aatt
       tthhiiss ttiimmee
              This  message  is  generated  by  save  sets  on PC
              clients running  DOS  or  NetWare.   The  NetWorker
              client  software  on  these  systems cannot back up
              files open for writing, due to the  interface  pro-
              vided  by the operating system.  This message actu-
              ally comes from Novell's TSA and is not changeable.
       uunnkknnoowwnn hhoosstt
              The  specified  client  is  not  listed in the host
              table on the server  (note:  a  similar  "save"  or
              "savefs"  specific  message  is  described  above).
              Depending on your host  configuration,  this  means
              the  client  is  not  listed  in  one  (or more) of
              /etc/hosts, NIS, or the Domain  Name  Service.   If
              you  use fully qualified domain names, you may need
              to make a new  client  resource  for  this  client,
              using  that  fully qualified domain name (i.e. name
              the client resource "mars.legato.com", not "mars").
       _p_r_i_n_t_e_r:: uunnkknnoowwnn pprriinntteerr
       _p_a_t_h//ssaavveeggrrpp:: pprriinnttiinngg bboooottssttrraapp iinnffoorrmmaattiioonn ffaaiilleedd
       ((rreepprroodduucceedd bbeellooww))
              This  message, or similar messages, accompanies the
              bootstrap information when ssaavveeggrrpp  was  unable  to



NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                       17





SAVEGRP(8)                                             SAVEGRP(8)


              print  the  bootstrap  on the printer.  You need to
              either specify a different printer in  the  _p_r_i_n_t_e_r
              attribute  for  the  group, or configure your print
              server to recognize the printer (by  default,  your
              system's  default  printer is used).  The bootstrap
              information is listed as part of the  savegrp  com-
              pletion  mail.   You should print out this informa-
              tion immediately, in case your server has a  disas-
              ter and loses a disk, and fix the printer name used
              by ssaavveeggrrpp.

       WWaarrnniinngg -- ffiillee ``_p_a_t_h'' cchhaannggeedd dduurriinngg ssaavvee
              This warning message is generated when ssaavvee notices
              that the file's modification time changed while the
              file was  being  backed  up.   NetWorker  does  not
              attempt  to  lock  files  before saving them, since
              this would make backups run extremely slowly.   You
              may  wish  to backup files which generate this mes-
              sage manually, to ensure that a consistent copy  is
              saved.   NetWorker  does not attempt this automati-
              cally, to avoid trying forever on the same file.

       WWaarrnniinngg:: ``_c_l_i_e_n_t'' iiss nnoott iinn tthhee hhoossttss ttaabbllee!!
              This message is generated by a ssaavvee or ssaavveeffss  com-
              mand  run  on  the  specified  client  to save that
              client's filesystems.  The client's hostname is not
              listed  in  the  host  table  on the client (either
              /etc/hosts, NIS or DNS, depending on that  client's
              configuration).   This  almost  always results in a
              failed save.  Fix the client's host table  and  re-
              run the save.

       WWaarrnniinngg:: uunnssyynncchhrroonniizzeedd cclliieenntt cclloocckk ddeetteecctteedd
              After  completing  a  save set, ssaavveeggrrpp was able to
              determine that the client and  server  clocks  were
              not synchronized (this cannot be detected for older
              clients).  Unsynchronized clocks can cause  various
              anomolous  results,  such  as  a client's save sets
              always being backed up at the level  _f_u_l_l.   Unsyn-
              chronized  clocks,  once  detected,  will not cause
              failed or incomplete backups,  but  can  cause  too
              much  data to be backed up.  Keeping the client and
              server clocks synchronized to within a minute  will
              avoid such anomolous situations.

       _a_s_m:: _p_a_t_h wwaass nnoott ssuucccceessssffuullllyy ssaavveedd
              This  message  generally  accompanies  one  or more
              other more-specific messages for the save set.  The
              specified  path within the current save set was not
              saved successfully.  The backup will continue  try-
              ing  to  back up other files and directories on the
              save set.





NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                       18





SAVEGRP(8)                                             SAVEGRP(8)


       _a_s_m:: xxddrr___o_p ffaaiilleedd ffoorr _p_a_t_h
              This error can be caused by several possible condi-
              tions  (e.g.  out of memory, buggy networking soft-
              ware in the operating system, an external ASM unex-
              pectedly  exiting,  a lost network connection).  If
              it was due to a lost network connection,  then  the
              NetWorker   server   most  likely  exited  (due  to
              nnssrr__sshhuuttddoowwnn).  After restarting the server,  rerun
              the  group.   If due to an ASM exiting unexpectedly
              (in this case, the message should be accompanied by
              a  message  describing  which  ASM exited unexpect-
              edly), you may have found a bad block on the  disk,
              or  perhaps  a bug.  Check if the client ran out of
              memory (there may be console messages), and  verify
              that  there  are  no  bad  blocks on the save set's
              disk.  If there were network errors, there may also
              have  been messages logged by other programs on the
              system console (client or server), or to system log
              files.

FFIILLEESS
       //nnssrr//ttmmpp//ssgg.._g_r_o_u_p           A  lock  file to keep multiple
                                   savegrps  of  the  same  group
                                   from running simultaneously.
       //nnssrr//ttmmpp//ssgg.._g_r_o_u_p.._c_l_i_e_n_t..**  Temporary  files  used  to log
                                   the output of individual  save
                                   sets  for  the named group and
                                   client.
       //nnssrr//ttmmpp//gg_g_r_o_u_p**            On  filesystems   with   short
                                   names  (less  than  64 charac-
                                   ters),  the  temporary   files
                                   used  to  log  the  output  of
                                   individual save sets  for  the
                                   named group.

SSEEEE AALLSSOO
       llss(1), ppss(1), nnssrr__ggeettddaattee(3), rrccmmdd(3), ffssttaabb(5), nnssrr(5),
       nnssrr__ddiirreeccttiivvee(5), nnssrr__nnoottiiffiiccaattiioonn(5), nnssrr__sseerrvviiccee(5),
       nnssrr__ggrroouupp(5), nnssrr__sscchheedduullee(5), nnssrr__rreessoouurrccee(5), mmmmiinnffoo(8),
       nnssrrsssscc(8), nneettssttaatt(8), nnssrr(8), nnssrraaddmmiinn(8), nnssrreexxeecc(8),
       nnssrreexxeeccdd(8), nnssrrwwaattcchh(8), nnwwaaddmmiinn(8), rrsshhdd(8), ssaavvee(8),
       ssaavveeffss(8), yyppppuusshh(8).















NetWorker rt_1998_4Q.Build.MMaJrFcehra0l8_,0021000                       19


