SAVEGROUP(8) Legato NetWorker 3.0 SAVEGROUP(8)
NAME
savegroup - start a group of NetWorker clients saving their filesys
tems
SYNOPSIS
savegroup [ options ] [ -R ] [ groupname ]
savegroup [ options ] -c client [ -c client ... ]
options: [ -EImnpv ] [ -l level | -C schedule ] [ -W width ]
DESCRIPTION
Savegroup runs a group of NetWorker clients though the process of
saving their filesystems (see savefs(8)). The group of clients can
be selected by naming a NetWorker group (see nsrgroup(5)), or by
explicitly listing each client's name with -c. If no group or client
names are specified, the NetWorker group default is used. If a Net
Worker group is named, all clients who's nsrclient(5) resources
specifies the named group in their group attribute, will be saved.
If an explicit client list is specified, savegroup will name this
pseudo group "ad hoc" for reporting purposes.
Savegroup is normally run automatically by nsrd(8), as specified by
each group's nsrgroup(5) resource.
Savegroup will use rcmd(3) to run savefs on each client for each
filesystem listed in the nsrclient resource save set attribute. If
a save set of All is specified for a client, savegroup will request
from the client a list of filesystems to be saved. The savefs com
mand generates this list by looking for filesystems that are local to
that client machine. The determination of which filesystems to save
will vary between different operating systems. To see which filesys
tems a client will save run savefs -p on that client. Each filesystem
saved is called a save set.
savegroup attempts to keep multiple clients busy by scheduling the
client save sets. As save sets complete, the output is collected and
another save set will be started by savegroup.
The parallelism attribute in the nsrservice(5) resource is the maxi
mum 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 running drops below the new value.
When all 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, and the bootstrap save set
information (see saveindex(8)) will be printed to the default
printer.
Savegroup will detect other active invocations of the same group, and
will exit with an error message. If two different NetWorker groups
are running simultaneously, they each will run up to parallelism save
Licensed material--property of copyright holder(s) 1
SAVEGROUP(8) Legato NetWorker 3.0 SAVEGROUP(8)
sessions simultaneously.
The progress of the actively saving clients can be monitored using
the Xm based networker(8)) program or the curses(3X) based nsr
watch(8) program. The nsradmin(8) browser may also be used to exam
ine the completion status work list of each NSR group resource,
though the hidden attribute display option will need to be selected
(see nsradmin(8)). These two attributes allows you to track the
progress of each savegroup. See NSR group for more details.
When all the save sets have finished, an NSR notification (see
nsrnotification(5)) with an event of savegroup and priority of
notice is sent to the NSR notification system. This is generally set
up to cause mail to be sent to the root user specifying the list of
clients who failed (if any), and all the output collected from all
clients.
OPTIONS
-E Cause savefs 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 generate 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.
-I Disable the saving of each client's index.
-m Disable monitor status reporting, including all NSR notifica
tion actions.
-n No save. Cause savefs to perform an estimate as described for
-E, but not to perform any actual saves. This option also
sets -m.
-p Run the savefs on each client with the -p flag, so you can see
which filesystem would be saved and at what level, but do not
actually save any data. This option also sets -m.
-R Restart. Use the information stored with the NetWorker server
to restart a group which previously was terminated, generally
due to a crash of the NetWorker server machine.
-v Verbose. Print extra information about what savegroup is
doing, and do not pass the -q flag along to savefs, so it too
will be chatty.
-l level
The level of save (see nsrschedule(5)) to perform on each
client. This overrides the save level which savegroup would
normally automaticly determine.
Licensed material--property of copyright holder(s) 2
SAVEGROUP(8) Legato NetWorker 3.0 SAVEGROUP(8)
-C schedule
The name of the NSR schedule (see nsrschedule(5)) to be used
in the automatic save level selection process which savegroup
normally performs. This overrides the save schedule which
savegroup would normally use for a given client.
-W width
The width used when formatting output or notification mes
sages. By default, this is 80.
group Specifies the NetWorker group of clients that should be
started, rather than the default NSR group (which has the name
attribute of default). See nsrgroup(5) for more details.
-c client
The name of a client to save filesystems on. There can be
multiple -c client specifications. The networker(8) monitor
will refer to this group of clients as the ad hoc group.
RESOURCE TYPES
NSR Use the parallelism attribute for the maximum number of
saves to start simultaneously.
NSR group The attribute work list 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 completion contains values in groups of 4,
specifying the client name, path saved, status, and the
output, for each save set completed.
NSR schedule Used by the savegroup command with each client's
nsrclient(5) resource to determine which level of save
to perform for each specified save set.
NSR client Each client resource names the groups it should be saved
by, the save sets which should be saved (see savefs(8)),
the name of the schedule to use (see, nsrschedule(5)).
and the name of the directives to use (see.
nsrdirective(5)).
NSR notification
Three kinds of notices are sent to the NSR notification
system, both with the event attribute of savegroup.
While a savegroup is in progress, status notices are
sent with the priority of info. At completion of a
savegroup, a notice is sent containing the collected
output of all saves, and the name of clients which had a
save which failed (if any). This notice will have an
event type of savegroup, and a priority of notice. If
savegroup is interrupted, a notice stating the group was
terminated, with an event type of savegroup, and a pri
ority of alert will be sent. These last two typically
will result in the notice being encapsulated in a mail
message to root.
SEE ALSO
rsh(1), curses(3X), fstab(5), nsrnotification(5), nsrservice(5),
nsrgroup(5), nsrschedule(5), nsrresource(5), networker(8), nsr(8),
nsradmin(8), nsrwatch(8), savegroup(8), savefs(8)
Licensed material--property of copyright holder(s) 3