Sources
Official Documentation
NetWorker
Release 7.2 Microsoft Windows Version Administrator’s Guide (822 pages)
NetWorker
Legato Command Line Reference (includes all man pages "NW 7.2" build
172 (443 pages)
NetWorker Support Landing Page - http://support.emc.com/products/networker
Networking
Powerlink Case Support : https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/kmlogin/login.jsp?forgot=true
System Components
autochanger synonym
of autoloader, carousel, datawheel, jukebox, librairy
volumes physical volume, K7
devices logical device, partition
storage node computer that
contains NetWorker client
file index index of backed-up data items
media database volumes index
directive defines file processing activities
that are performed during a backup
Server components
Location of
Components
%SystemDrive%\Program
Files\nsr
Important Files
and Directories
mm NetWorker
media database
res NetWorker
resource files:
- nsrla.res
- rservers
- servers
- \nsrdb NetWorker
resource database
index\client_name\db
Client
file index database + E:\Legato_Index
logs
NetWorker
log files
Services
nsrd The Master NetWorker Server Process : service can start several
nsrmmd services, one for each enabled device. An additional nsrmmd service
is started during pending mount requests. This is the media multiplexor
service. The nsrd process
• Starting
other services.
•
Allocating media services on server and storage node computers.
•
Authorizing backup and recover services for the client.
•
Contacting clients for scheduled backups.
•
Maintaining NetWorker configuration information.
•
Monitoring backup and recover sessions.
•
Maintaining server statistics and message logs.
The nsrd
NetWorker server service calls on the nsrexecd NetWorker client
service and several client-side programs when it receives a scheduled or manual
backup request. The ansrd agent starts on the NetWorker server computer
to monitor the progress of the backup session.
nsrd Provides an RPC-based save and
recover service to NetWorker clients. For details regarding this
service, see "The Master NetWorker Server
Process" on page 61.
ansrd
Monitors an active recover session. This agent process is
spawned by nsrd in response to a recover session.
nsrck
Checks consistency of client file index. It is invoked by nsrd when
consistency of client file index needs to be confirmed.
nsrexec
Monitors the progress of individual save sets; agent process
invoked by the savegrp program.
nsrim
Manages the server’s client file index; invoked at the end of an instance
of the savegrp program. Note that nsrim is invoked only once
within a twenty-four hour period, regardless of how many times savegrp is
run in that same period.
nsrindexd
Provides a method for inserting entries in the client file index
based on information passed by the save program.
nsrmmd Provides
device support, generates mount requests, and multiplexes save set data
during a multiclient backup.
nsrmmdbd Provides
media and save set database management services to the local nsrd and nsrmmd
service, and records entries in the media database. This is the media
management database service.
savegrp
Runs
a group of NetWorker clients through the save process.
ADMINISTRATION
NetWorker
is administered via resources and attributes. Every resource has
one or more attributes associated with it.
Resource
files are not normally edited by hand. Rather, a NetWorker tool (usually nwadmin(1m)
or nsradmin(1m)) is used to modify resource files dynamically so that
values can be checked and changes can be propagated automatically to the
interested programs.
The
following are tools that are used to administer various aspects of NetWorker.
nwadmin(1m)
Monitors
the activity of and administers NetWorker servers. The nwadmin command
is an X Window System application, using a Motif look and feel. The nwadmin command
is most users’ primary interface to NetWorker.
nsradmin(1m)
A curses(3)
based tool for the administration of NetWorker servers.
nsrwatch(1m)
A curses(3)
based tool to monitor the activity of NetWorker servers.
nsrmm(1m) Media
manager command. The nsrmm command is used to label, mount, unmount,
delete and purge volumes. Mount requests are generated by nsrmmd, and
displayed by nwadmin or nsrwatch. The size of the on-line user
file indexes may be controlled by deleting and purging volumes.
nsrjb(1m) The
NetWorker jukebox-controlling command. When dealing with a jukebox, nsrjb,
rather than nsrmm, should be used to label, load, and unload the volumes
contained within a jukebox.
nsrim(1m)
Automatically manages the on-line index. It is usually run periodically by savegrp.
mminfo(1m)
Provides information about volumes and save sets.
nsrck(1m) Checks
and repairs the NetWorker on-line index. It is run automatically when nsrd starts
up if the databases were not closed cleanly due to a system crash.
nsr_shutdown(1m)
A
shell script used to safely shut down the NetWorker-specific remote execution
service which runs on NetWorker clients. Used by savegrp to start save
and savefs on client machines.
savefs(1m) Used
by savegrp to determine characteristics of a client, and to map the save
set All to the current list of all save sets on a client.
SAVING
FILES
NetWorker
supports both scheduled and manual saving of files and filesystems. Each client
may be scheduled to save all or part of its filesystems. Different clients may
be scheduled to begin saving at different times.
save(1m) A
command-line-based tool used to back up a specified file or group of files. The
save command may be run manually by users and administrators, or
automatically by savegrp.
nwbackup(1m)
A
Motif-based tool for backing up files. The nwbackup command is the
graphical equivalent of save.
savegrp(1m) Used
to initiate the backup of a group of client machines. Usually started
automatically by
the
NetWorker server. The savegrp command also backs up the clients’ on-line
file indexes,
which are
stored on the server. When backing up the server itself, a bootstrap save
set is
also created.
nsrexec(1m) The agent
savegrp process, spawned by savegrp. The nsrexec command
monitors the
progress of
NetWorker commands.
nsrclone(1m) The
NetWorker save set/volume cloning command. Using nsrclone, clones,
or exact replicas,
of save
sets or entire volumes can be made. Clone data is indistinguishable from the
original
data, except for the NetWorker media volumes upon which the data reside.
nsrexecd(1m)
RECOVERING
FILES
NetWorker
maintains an on-line index of user files that have been saved. Users may browse
the index and
select
files for recovery. This information is used to build a representation of the
file heirarchy as of any
time in the
past. NetWorker then locates the correct volume and recovers the requested
files.
recover(1m)
Browses the on-line user file index and selects files and filesystems to
recover.
nwrecover(1m) A
Motif-based tool for recovering files. The nwrecover command is the
graphical equivalent
of recover.
mmrecov(1m) Used
only for disaster recovery. Recovers the special bootstrap index and the
server’s online
file index.
The recover or nwrecover commands are used to recover other
on-line
file
indexes.
scanner(1m)
Verifies correctness and integrity of NetWorker volumes. Can also recover
complete save
sets and
rebuild the on-line file and media indexes.
nsr_crash(1m) A man
page describing crash recovery techniques.
nsrinfo(1m) Used
to generate reports about the contents of a client’s file index.
APPLICATION
SPECIFIC MODULES
In order to
process user files in an optimal manner, NetWorker provides the ASM mechanism.
Pattern
matching is
used to select files for processing by the different ASMs. The patterns and
associated ASMs are
described
in nsr(5). The save command keeps track of which ASMs were used
to process a file so that
recover may use the
same ASMs to recover the file.
uasm(1m) UNIX
filesystem specific save/recover module. The uasm man page documents the
general
rules for
all ASMs. The uasm command and its man page actually comprise several
additional
ASMs, including compressasm, mailasm, and xlateasm, to
name a few.
nsrindexasm(1m)
Processes
the on-line user file indexes.
nsrmmdbasm(1m)
Processes
the on on-line media database.
NAME
nsr_layout
- NetWorker file layout
The format
of this directory is as follows:
/nsr/logs
Contains
server logging messages. The files in this directory are in ASCII format.
/nsr/res Contains
the configuration files for various components of the NetWorker server. For
example, the
server
stores configuration files in /nsr/res/nsrdb.
/nsr/mm
Contains the
media index. Information about the contents of this index file can be printed
with the
nsrls(1m)
command. See the nsrmm(1m) and mminfo(1m) manual pages on how to
view and
manipulate
the media index information.
/nsr/index
This
directory contains subdirectories with names that correspond to the NetWorker
clients that
have sav ed
files. Each index directory contains files that allow the NetWorker server to
provide an
on-line
database of the client’s saved files. The most important element is the db6 directory
which
contains
the NetWorker save records and access indexes to those records. The disk space
utilized
by the
index grows with the number of files saved by the NetWorker service.
Administrators
should plan
to use about 200 bytes per saved file instance placed in this index. There are
no practical
limits
RESOURCE
TYPES
This
release of NetWorker defines the following types of resources:
NSR This
resource describes a NetWorker server. It contains attributes that control
administrator authorization,
information
about operations in progress, and statistics and error information about past
operations.
For more information see the nsr_service(5) manual page.
NSR client
This
resource describes a NetWorker client. It includes attributes that specify the
files to save,
which
schedule to use, and which group this client belongs to. There may be more than
one client
resource
for a NetWorker client. This allows a client to save files on different
schedules. For more
information
see the nsr_client(5) manual page.
NSR device
This
resource type describes a storage device. It includes attributes that specify a
particular device
name (for
example, /dev/nrst1), media type (for example, 8mm), and the name of the
currently
mounted
volume. It also provides status and statistics on current and past operations.
For more
information
see the nsr_device(5) manual page.
NSR
directive
This
resource describes a directive. Directives control how a client’s files are
processed as they are
being
saved. For more information see the nsr_directive(5), nsr(5) and uasm(1m)
manual pages.
NSR group
This
resource specifies a logical grouping of NetWorker clients and a starting time.
Each day, at
NetWorker
7.2 Last change: Oct 25, 04 2
Headers,
Environments, and Macros NSR_RESOURCE ( 5 )
the
specified time, all members of the group will start their saves. For more
information see the
nsr_group(5) manual
page.
NSR jukebox
This
resource type describes a jukebox. It includes attributes such as the jukebox
model, the first
and last
slot numbers in the jukebox, and the names of the devices within the jukebox.
For more
information
see the nsr_jukebox(5) manual page.
NSR label
This
resource type specifies a template describing a sequence of names to be used
when labeling
volumes.
For more information see the nsr_label(5) manual page.
NSR license
This
resource contains licensing information for each feature currently enabled in
this NetWorker
installation.
It contains various enabler and authorization codes that are used by NetWorker
to validate
licensed
capabilities. For more information see the nsr_license(5) and nsrcap(1m)
manual
pages.
NSR
notification
A
notification specifies an action to be performed when a particular type of
NetWorker event takes
place. For
more information see the nsr_notification(5) manual page.
NSR policy
Policy
resources are used as part of the index management process in NetWorker. These
policies
control how
long entries remain in a client’s on-line file index and when to mark a save
set as recyclable.
For more
information see the nsr_policy(5) manual page.
NSR pool
This
resource type is used by NetWorker to determine what volumes save sets should
reside on
based on
the characteristics of the save (for example, group or level). For more
information see
the nsr_pool(5)
manual page.
NSR
schedule
Schedule
resources define a sequence of save lev els and an override list. The override
list is made
up of pairs
of levels and dates. The level controls the amount of data saved when a client
is
backed up.
For more information see the nsr_schedule(5) manual page.
NSR stage
Each stage
resource describes a staging policy. The resource includes attributes that
define control
parameters
for the policy, and devices managed by the policy. For more information see the
nsr_stage(5) manual page.
FILES
/nsr/res/nsrdb
Holds
the NetWorker server’s resources. Files in this directory should never be
edited
directly. Use nsradmin(1m) or nwadmin(1m) instead.
Client Services
nsrexecd Authenticates
NetWorker server’s remote execution request and executes save and savefs
on the client.
recover Browses the
NetWorker server’s client file index and restores the specified file to primary
disk storage.
save Sends
specified files in a multiplexed data stream to the NetWorker server for backup
to media by nsrmmd and entry in
the client
file indexes and media database by nsrindexd.
savefs Saves a
filesystem (using the save program) to a NetWorker server; a level-based
system is used to save only those files which have been modified since some
previous save (a partial save).
Synoptic
A storage
node is controlled by a NetWorker server (or multiple NetWorker servers).
Backup and recovery occur as follows:
1. The
NetWorker server’s nsrd master service starts an instance of nsrmmd (media
management) on the storage node.
2. The
server routes data to each media
management service according to the Storage Node attribute in the Client
resource.
3. After
data is written to the storage devices connected to a storage node, the NetWorker
server tracks the location of the data.
4. On the
NetWorker server:
• The nsrindexd
service writes entries in the client file indexes to track the location of
each file in a save set.
• The nsrmmdbd
service writes entries in the media database to track the location of each
save set on the media.
Tapes Mounting order in operations
1
tape 0
2
tape 1
3
tape 2
4
tape 3
Distributed Components
Indexes
The
NetWorker server tracks the files it backs up in two databases, which are stored
on the server’s local filesystem:
• The client
file index tracks the files that belong to a save set. There is one client
file index for each client.
• The media
database tracks the following:
– Volume
name
– Backup
dates of the save sets on the volume
–
Filesystems in each save set
Each entry
in the client file index includes the following information for a backed-up
file:
• Filename
• Number of
blocks
• Access
permissions
• Number of
links
• Owner
• Group
• Size
• Last
modified time
•
Backup time
Automated
Index Activities
The
NetWorker server performs the following online index activities:
•
Inserts entries in the client file index for each file saved during a backup. For
each new backup, the NetWorker server acquires more space from the filesystem
for the new entries.
•
Removes entries and returns disk space to the operating system. The browse and
retention policies automatically determine when entries are removed from the
index. You can also remove index entries manually by clicking Remove Oldest
Cycle in the Index Save Sets dialog box.
Checking
Online Indexes
Each
time the NetWorker server starts, it uses nsrck -ML1 to perform a level
1 consistency check on the client file indexes. In some circumstances, this consistency
check will not detect corruption in the client file indexes. If you believe an
index may be corrupt, run a higher level check on the index, for example: nsrck
-L5
If
the index is still corrupt, recover the index by using the procedure outlined in
"Recovering Online Indexes" on page 459.
It
is also good maintenance practice to periodically run the nsrck -F and nsrim
-X commands to check the integrity of the client and media indexes.
How to
Cross-Check Indexes
By
cross-checking, you can verify the consistency between the client file index and
the media database. If the NetWorker server finds entries in the client file index
that do not have corresponding entries in the media database, it removes
the client
file index entries. This feature is useful, for example, if you perform an
index operation and the server crashes before the NetWorker server has completely
updated the indexes. Once the server is running again, cross-check to
accurately update the online indexes.
To
cross-check a client’s index:
1. In the
NetWorker Administrator program, select the Indexes tab in the server window.
2. Right-click
the client whose index you want to cross check and select Cross Check Index.
The
NetWorker server prompts you with the following message:
Cross-checking
may take considerable time. Would you like to cross-check client_name?
3. Click
Yes to continue.
The
NetWorker server displays a status box until the cross-checking is complete.
Location of
the Client File Index
During the
initial client setup, the NetWorker software normally designates a default
location for the client’s client file index on the NetWorker backup server.
This default location is <NetWorker_install_path>\index\client_name.
However, there may be times when you need to designate a different index location
when first configuring a Client resource, or you might need to move
the
file index of an existing client. The following sections address these needs.
Managing
the Size of the Online Indexes
Over
time, the size of the NetWorker server’s online indexes can become prohibitively
large. You can reduce the size of these indexes by using the solutions suggested in the following
sections:
•
"Reducing Client File Index Size" on page 181
•
"Reducing Media Database Size" on page 182
•
"How to Remove the Oldest Save Set Cycles" on page 182
•
"Removing Volume-Based Entries from the Online Indexes"
on page 183
• "How to Compress the Media Database" on page 185
Save Sets
To
view the status of a save set:
1.
In the NetWorker Administrator program, select the Volumes tab.
2.
Right-click the save set whose status you want to view, and select Show Save
Sets to open the Volume Save Sets dialog box as shown in Figure
18 on page 217.
The
browse policy determines how long files are maintained
in the client’s file index on the NetWorker server.
The
retention policy determines how long save sets are
maintained in the NetWorker server’s media database. For at least the period of
the retention policy, you can recover a client’s backed-up save sets from
media:
Save Set
Status Values
abort
aborted You aborted the backup for this save set manually, or a crash occurred .This
save set is considered immediately eligible for recycling.
brows
browsable You can restore all the files using an index-based recover.
inpro in
progress This save set is currently being backed up.
recov
recoverable The files in this save set do not have browsable entries in the client
file index, and have not passed the retention policy.
recyc
recyclable The save set, and all save sets dependent have exceeded their
retention policies.
scann
scanned-in The entry for this save set was restored by using the scanner program.
The policies were reset to the values that were applied when the save set was
created (or, if the save set was created on NetWorker servers from releases
prior to 6.0, when the save sets were upgraded to the 6.x format). For more
information, see "The scanner Program" on page 462.
susp
suspect An attempt to recover this save set failed. The recover command could not read all the blocks of
the save set. This can occur, for example, when there is a bad spot on the
tape.
p
purged The save set has been purged from the media database.
Retention
Policy
After the
retention period is exceeded, the save set is eligible to change its status
from recoverable to recyclable.
When
all of the save set entries on a volume change status to recyclable, the mode
of the volume itself changes from either full or appendable to recyclable.
If auto
media management is enabled, the volume may be relabeled automatically by the
NetWorker server to satisfy a volume mount request.
After the volume is relabeled, all existing data on the volume is unavailable
for recovery. For more information
on
this feature, see "Auto Media Management" on page 336.
Important:
When you relabel a volume for reuse within the same pool, the
volume identification (the volume name as it appears on the volume label) remains
unchanged. Even though the volume has the same label, information required by
the NetWorker server to locate and restore data on the volume is destroyed.
Neither the save set recover feature nor the scanner program can be used
to recover the data. At this point, the volume is ready for new data; all existing
data is inaccessible and will be overwritten.
Browse and
Retention Policies for Manual Backups
Browse and
retention policies for manual backups adopt the same policies as the instance
of a particular client name that has the longest retention time. The insertion time is the time this save set
record was most recently introduced into the save set database.
Reports on
Browse and Retention Policies for Save Sets
The mminfo
command can be used with the -p option to display a report on the
browse and retention times for save sets.
Expression
Matching of Save Sets to Pools
the Save
Set attributes in the Pool resource are matched using LEGATO’s regular
expression matching described in the nsr_regexp and nsr_pool entries.
• A save
set path of c:\SomeDir\MyFiles should be written c:\\SomeDir\\MyFiles.
• A
filename of MyFile.txt should be written MyFile\.txt.
When using
the NetWorker Administrator program, each save set in the Save Set attribute
must be on a separate line. The following is an example of properly written
save set entries:
/
/usr
c:\\Program
Files\\bin
*\.doc
Directives
Local and
Global Directives
There are
three types of directives:
• Global
directives — Administrators can create global directives by using the
NetWorker Administrator program. These directives are stored as resources on
the NetWorker server, and can be selectively applied to individual clients
using the Directive attribute of the Client resource.
• NetWorker
User local directives — On clients running Microsoft Windows, users with
local Windows Administrator or Backup Operator privileges can create local
directives using the NetWorker User program. These directives are stored on the
client in a file named Networkr.cfg, and are applied throughout the
client’s filesystems during scheduled backups (or save operations that
do not include the -i option).
• Local
directive files — Users can create local directive files named nsr.dir anywhere
on a client filesystem that they have permission to create files. The
directives these files contain apply only to the immediate data within the path
where the directive file is located.
Application
Specific Modules
Directives
use Application Specific Modules (ASMs) to process files and directories. ASMs
are programs that operate within the NetWorker environment to perform various
tasks during backup and recovery. p252 table of ASM
Client
Priority
The Client
Priority attribute in the Client resource specifies the order in which participating
clients are probed for the information needed to complete the save set worklist
for that client. The Client Priority attribute is part of the Client resource,
and is only visible when Hidden Attributes is enabled. This attribute can
contain a value between 1 and 1,000. The lower the value, the higher the priority.
The client with the lowest value for the Client Priority attribute is placed at
the top of the list to be contacted by the NetWorker server. If a value is not specified
in the Priority attribute, the contact order is random.
Backup levels
Full
Backs up all files, regardless of whether or not they have changed.
Level
[1 – 9] Backs up files that have changed since the last backup with a lower-numbered
backup level. For example:
•
A level 1 backup backs up all files that have changed since the most recent
full backup (considered a level zero).
•
A level 3 backup backs up all files that have changed since the most recent
backup of level 2, level 1, or full backup. For example, if the most recent
backup was at level full, then a level 3 backup backs up all files that changed
since the full backup. However, if the most recent backup was at level 2, then
a level 3 backup backs up only those files changed since the level 2 backup.
•
A level 9 backs up all the files that have changed since the most recent backup
of any level except level 9.
Note:
The NetWorker software ignores any incremental-level backups when
determining what files should be backed up.
Incremental
Backs up files that have changed since the last backup, regardless of level.
Consolidated
Backs up all data that has changed since last full backup and subsequently merges
these changes with the last full backup. For more information, see "Save
Set Consolidation" on page 397.
Skip
Skips the scheduled backup. For example, you may want to skip a backup on a
holiday if you know that no one will be available to change or add more media
volumes.
Managing the Data Life Cycle
Scripting
You can
customize client backups by creating additional programs (scripts) that affect
the way your NetWorker server
• Shuts
down a mail server or database before the NetWorker server performs a
backup operation.
• Restarts
the mail server or database after the backup has completed
• Prints a
message (such as, "Backup started at 3:33 a.m.") before thebackup
operation begins.
• Executes
the backup.
• Prints a
message (such as "Backup completed at 6:30 a.m.") when the
backup
has completed.
DFS Components
Backing Up
and Restoring a Distributed Filesystem
Microsoft
Distributed Filesystem (DFS) is aWindows feature that enables you to create a name space of shared directories
that are physically distributed across a network.
DFS
Components
A DFS
component is a DFS root (namespace for files and DFS links) or a DFS
child node (connection to a shared file or folder). DFS components are filesystem
objects, but they are not files or directories.
NetWorker
DFS Backups
A complete
NetWorker backup of a distributed filesystem requires:
• Backup of
the DFS topology information
• Backup of
the DFS components
• Backup of
the DFS destination directories (the shared directories
connected
to DFS child nodes)
DFS
Topology Backup
DFS
topology information is backed up as a part of the DFS host server’s registry,
a component of the SYSTEM STATE or VSS SYSTEM BOOT save set (see "SYSTEM
STATE Save Set Components" on page 199, or "VSS
SYSTEM BOOT Save Set Components" on
page 204).
How
to Save DFS Topology Information in an Excel File
Before
you perform a backup of the DFS components, save a copy of the DFS topology
information in an Excel file. To do this:
1.
Start the Microsoft DFS Administrator.
2.
Select Save from the DFS menu.
DFS
Administrator prompts you for a pathname and saves the topology information in
a Microsoft Excel file.
Restoring
a Distributed Filesystem
To
properly restore a distributed filesystem, you must perform all of the following
steps:
1.
Restore the Windows registry.
Note:
In NetWorker release 5.7 and later, the Windows registry is backed
up and restored as a component of the SYSTEM STATE or VSS SYSTEM BOOT save set
(see "SYSTEM STATE Save Set Components" on page 199,
or "VSS SYSTEM BOOT Save Set Components" on page 204).
2.
Restore the DFS components.
Note:
You cannot restore individual DFS child nodes. If your DFS root
has lost a child node, you must restore the entire DFS root in which that child
node resided.
3. If necessary, restore the destination directory save sets
(local or remote).
4.
After the recovery is complete, ensure that the Excel file containing the previously
saved topology information was restored (see "DFS
Topology Backup" on page 186).
5. Start the DFS Administrator and select Load from the DFS menu.
DDS Dynamic Drive Sharing
Dynamic
Drive Sharing (DDS) is a feature to recognize shared drives. DDS enables
NetWorker software
to skip the
shared drives that are in use and route the backups or recoveries to other
available shared drives.
EFS
windows
2000+EFS : Legato do not support key recovery : if EFS is reapplied-> new
keys AND do not support VERIFIED -V Backup of SYSTEM STATE
Device and Media Management
Media Types
Media
Types :
sdlt
sdlt300
sdlt600
…
dlt Digital
linear tape
vhs VHS
tape
optical
Optical disk
DEVICES
> CREATE NEW to see available compatible Media Types
Device Parameter Environment
Variables
A number of
environment variables can be used to adjust several NetWorker device
parameters:
• NSR_DEV_BLOCK_SIZE_MEDIA_TYPE
• NSR_DEV_TAPE_FILE_SIZE_MEDIA_TYPE
• NSR_DEV_DEFAULT_CAPACITY_MEDIA_TYPE
• NSR_DEV_LOAD_TIME_MEDIA_TYPE
• NSR_DEV_LOAD_POLL_INTERVAL_MEDIA_TYPE
•
NSR_DEV_LOAD_TRY_LIMIT_MEDIA_TYPE
Media Devices Volumes
Auto Media
Verification
If the Auto
Media Verify attribute is enabled, the NetWorker server verifies data written
to volumes from this pool.
When a
volume fails verification, it is marked full so that the server will not select
that volume for future saves. The volume remains full until it is recycled or a
user marks it not full. If a volume fails verification while the server is attempting
to switch volumes, all save sets writing to the volume are terminated.
Device
Autodetection and Configuration
Device
autodetection and configuration automatically detects SCSI tape and autochanger
devices attached to the NetWorker server and its storage nodes. The feature
also automatically configures each device, making it easier to get
devices up
and running. However, any devices that are listed in the environment variable
NSR_SKIP_SCSI_TARGETS are ignored.
Automated
Enabling of All Dedicated Devices
Setting the
Enable New Devices attribute enables any new Device resources created during
the autodetection process.
How to
Enable Individual Devices Manually
If the
NetWorker server is not set to automatically enable all detected devices, you
must manually enable each device belonging to the autochanger.To enable each
individual Device resource:
1. In the
NetWorker Administrator program, click Devices from the Configure tab.
2. In the
Devices window, right-click the device and select Edit.
3. For the
Enabled attribute, select Yes.
4.
Click OK.
How to
Enable Devices After Autodetection
If you know
in advance that you will want to enable all devices found during the
device autodetection session, you can set the NetWorker server to enable all
found devices.
NetWorker
DiskBackup
One
NetWorker data storage option is to save data to a computer’s local or network-attached
disk, rather than use a tape device to write the data to storage media. Storing
data using the NetWorker DiskBackup solution greatly reduces the time it takes
to both save and recover data compared to using tape.
Media
Handling Errors
How to
Reenable a Device
To reenable
a device:
1. In the
NetWorker Administrator program, click Devices from the Configure tab.
2. Right-click
the icon of the disabled device, and select Edit.
3. For the
Enabled attribute, click Yes.
4. For
theWrite Enabled attribute, select Yes (unless you want the volume to be
read-only).
5. Click
OK.
If the
disabled device is part of an autochanger, you might need to reset the device
as follows:
1. Open an
MS-DOS window.
2. Change
the path to the directory that contains the NetWorker binaries.
3. Enter
the following command:
nsrjb
–HE
Auto
Media Management
The
auto media management feature gives the NetWorker server automatic control over
media loaded in the storage device. If auto media management is enabled through
the Device dialog box, the server automatically:
•
Labels, mounts, and overwrites a volume it considers unlabeled.
•
Recycles volumes eligible for reuse that are loaded into the device.
For
an autochanger, however, the value of the Auto Media Management text box is
always set to No. For information on how to use the auto media management
feature with an autochanger, see "Auto Media Management with Autochangers"
on page 543.
Nb
If auto
media management is enabled and the device is a stand-alone device, the
NetWorker server exhibits the following behavior when a volume becomes full
during a backup:
1. A
notification is sent to indicate that the server is waiting for a writable
volume. At the same time, the NetWorker server waits for the full volume to be
unmounted.
2. The
NetWorker server monitors the device, waiting for another volume to be inserted
into the device.
3. After a
volume is detected, the NetWorker server checks that the volume is labeled:
– If the
volume is labeled, the server mounts the volume and checks to see if the volume
is a candidate for writing. If it is, the
write
continues. If it is not, the server waits for a writable volume to continue the
backup.
– If a
volume is unlabeled, it is labeled when the next writable volume is needed for
a save.
4. If a
volume is recyclable and is a member of the required pool, it is recycled the
next time a writable volume is needed.
Note: If a
partially full volume is unmounted, the device is put in a monitor state for 15
minutes. During this time, manually eject and load another volume into the
device. After the 15 minute timeout period has passed, the NetWorker server
automatically mounts the volume
Storage
Node Devices
Storage
nodes are host computers with attached remote storage devices. A storage node
has the physical connection and ownership of the attached devices, but the
NetWorker server maintains the client file index and media database. You can
route client data directly to attached remote storage devices without the data
first going to the NetWorker server.
Storage
Management Operations
The
following sections detail the various tasks and components involved in the
operation of storage volumes and its relationship with pools.
How the
NetWorker Server Uses Volume Labeling
A volume
label is a unique internal code applied by the NetWorker server that initializes
the volume for the server to use and identifies a storage volume as part of a
specific pool. Labeling a volume provides a unique name for tracking and
recognizing the media, as well as references to volume labels in the records
stored in the media database. The NetWorker server uses the media database
records to determine which volumes are needed for backing up or recovering
data.
When it
labels a volume, the NetWorker server performs the following:
1. Verifies
that the volume is unlabeled.
2. Labels
the volume with the name specified in the Volume Name attribute by using one of
the following:
• The next
sequential label from the label template associated with the chosen pool.
• An
override volume name you entered.
If you
relabel a recyclable volume from the same pool, the volume label name
and
sequence number remain the same, but access to the original data on the
volume is
destroyed. The volume becomes available for new data.
How the
NetWorker Server Uses Pools
Every
volume belongs to a pool. Each pool has a matching label template associated
with it. Volumes are labeled according to the rules of these label templates.
Label templates provide a method for consistently naming and labeling volumes
so there is no need to keep track of how many volumes you have used. You can
either take advantage of the preconfigured pools and
associated
label templates that come with the NetWorker product, or create your own pools,
label templates, and pool-template associations. By customizing label
templates, you can better control your data storage organization.
Important: Placing a
new label on a storable volume, or recycling a volume by relabeling it, makes
any existing stored data unavailable for recovery.
How
the NetWorker Server Selects a Volume during Backup
When
a backup takes place, the NetWorker server searches for a volume from the appropriate
pool. Available volumes can be either:
•
Volumes that are labeled for the appropriate pool and are already mounted in a
device.
•
Volumes that are available for labeling, if Auto Media Management is enabled.
For more information, see "Auto Media Management"
on page 336.
•
Volumes that are labeled for the appropriate pool and are available for mounting,
if an autochanger is being used.
If
two or more volumes from the appropriate pool are available, the server uses
the following hierarchy to select a volume:
1.
Mounted volumes from the appropriate pool with the mode appendable are selected.
This includes newly labeled volumes. If more than one mounted volume is
appendable, the server uses the following hierarchy:
a.
Device availability. The server will write to the volume from the appropriate
pool that is mounted on the device with the fewest
current
sessions.
b.
Volume label time. If multiple mounted volumes are appendable and session
availability is not an issue, the volume with the oldest label time is
selected.
2.
If no mounted volumes are appendable and Auto Media Management is enabled, a
mounted volume with the mode recyclable is selected. The server relabels
and mounts the volume.
Note:
A volume is automatically set to recyclable when all save sets on
the volume, including partial save sets that span other volumes, are marked as
recyclable.If a stand-alone device is being used and Auto Media Management is
not enabled, the server sends a mount request notification. For more information,
see "Notifications" on page 143.
3.
If an autochanger is being used and the above criteria have not been met, the
server determines if there is an unmounted appendable volume. This includes
newly labeled volumes. If multiple unmounted appendable volumes are available, the
volume with the oldest label time is selected.
4.
If an autochanger is being used and no unmounted appendable volumes exist, the
server determines if there is an unmounted recyclable volume. If Auto Media
Management is enabled, the server will relabel and mount the volume.
If
Auto Media Management is not enabled, or if there are no appendable or
recyclable volumes, the server will send a mount request notification. For more
information about appendable and recyclable volumes, see "Volume
Status" on page 344.
Data
Recovery and Volume Selection
The
NetWorker server determines the volumes that are required for recovery. If the
appropriate volume is currently mounted, the recovery begins. If the volume is
not mounted and an autochanger is being used, the server attempts to locate and
mount the volume. If a stand-alone device is used, or if the server cannot
locate and mount the volume, the server will send a mount request notification.
For more information, see "Notifications" on page
143. If you need more than one volume to recover your data, the
NetWorker server displays all the volumes in the order they are needed. During
the recovery process, the server requests the volumes it needs, one at a time.
Automatic
Volume Relabeling
If
Auto Media Management is enabled and a volume has the mode recyclable, the
server will automatically relabel the volume.Avolume is automatically set to
recyclable when all save sets on the volume, including partial save sets that
span
other volumes, are marked as recyclable. For more information about recyclable
save sets, see "How the Retention Policy Works" on page 223.
The mode of a volume can also be manually changed to recyclable. For more information
about changing the mode of a volume, see "How
to Change the Mode of a Volume" on page 350.
Volume
Status
The
NetWorker server reports on the status of volumes using values such as Volume
Name, Written, %Used, Location, and Mode. This section defines some of the most
common terms contained in reports about volumes.
•
Volume Name: Within the NetWorker Administrator program, the volume name is the
same as the name that appears on the volume label.
At
the end of the name, the following designations may appear:
–
(A) indicates an archive volume.
–
(R) indicates a volume that is considered read-only.
•
Written: Always indicates the exact number of bytes written to the volume.
•
%Used: An estimate of percentage used based on the total capacity of the volume,
based entirely on the specified value of the Media Type of the
Device
resource. When Used is equal to full, there is no more space on the volume and
the end-of-tape marker has been reached or an error with the media has
occurred. This is in contrast to a Used value of 100%, which means that the
value of Written is equal to, or exceeds, the estimate for this volume.
•
Location: Refers to an administrator-defined character field that describes a
physical location of the volume within the user’s environment, for example, 2nd
shelf, Cabinet 2, Room 42.
•
Mode: Refers to the volume’s mode. Table 56 on page 344 lists
the NetWorker volume modes and their definitions. For information on changing
volume modes, see "How to Change the Mode of a Volume"
on page 350. For information about save set status, see "Client
and Save Set Combination" on page 216.
Volumes Tab
Use the
Volumes tab to see the contents of the media database and as a starting point
for:
• Removing
volumes.
• Changing
volume modes.
•
Setting locations for your collection of volumes
How to
Label and Mount a Volume in One Operation
Note: Relabeling
a volume makes it impossible for the NetWorker server to recover original data
from that volume.
To label
and mount a volume in one operation:
1. Insert a
volume in the NetWorker server storage device.
2. In the
NetWorker Administrator program, click Devices in the Configure tab.
3.
Right-click the individual device icon for which you want to label a
volume, and
select Operations.
4. Click
Label to open the Label dialog box.
5. From the
Pools list, select a pool.
The
NetWorker server assigns the next sequential label from the label template
associated with the chosen pool if the volume is considered unlabeled.
If you are
relabeling a recyclable volume from the same pool, the volume label name and
sequence number remain the same. However, access to the original data on the
volume is destroyed and the volume becomes available.
6. If you
want to manually recycle the volume, select Manual Recycle.
When a
volume is marked for manual recycle, the NetWorker server disregards the
assigned browse and retention policies.
7. Select
Mount After Labeling.
8. Click
OK.
The
server automatically labels and mounts the volume.
How
to Label without Mounting
You
can prelabel volumes without mounting them. Follow the steps for "How
to Label and Mount a Volume in One Operation" on page 349,
but clear the Mount After Labeling check box in step 7.
How
to Find a Volume Name
If
the adhesive label on the volume is missing or illegible, you can determine its
name by using one of these methods:
•
Mount the volume in the storage device.
The
volume name appears next to the device name in the Devices pane of the Monitor
tab. For more information, see "How to Mount a Volume"
on page 348.
•
Mount the volume in the storage device and enter the nsrmm command to
determine the volume’s name:
nsrmm
-pv -f devicename
•
Load the volume in a device.
a.
In the NetWorker Administrator program, click Devices in the Configure tab.
b.
Right-click the device’s icon in the Device or Autochanger window and select
Operations.
c.
Click Label. When the Label dialog box appears, the name of the label appears
in the Volume Label text box.
d. Click Cancel.
How
to Change the Mode of a Volume
The
mode of a volume determines whether the NetWorker server can write to it during
a backup. For a listing of the volume modes, see Table 56 on
page 344.
A
volume is automatically recyclable if all of the save sets on it are
recyclable.
Recyclable
save sets are those that have passed the time period designated by the
Retention policy for the client.
You
can manually change the mode of a full or appendable volume to recyclable if
you do not need the data on the volume. The NetWorker server then overwrites
the data on the volume the next time it needs a volume for a backup.
To
change the mode of a volume:
1.
In the NetWorker Administrator program, select the Volumes tab.
2.
Right-click the volume whose mode you want to change, and select Change Mode to
open the Change Mode dialog box.
3.
Select a Mode button and click OK. Notice the mode of the volume changes in the
Volumes list box.
Marking a
Volume as Full for Off-Site Storage
When
removing a volume from your autochanger to store off-site, mark the
volume as
full so that the NetWorker software will not continue to ask for the
volume.
To do this,
enter the following command:
nsrmm -V volid -o full
Where volid
is the volume identifier of the volume. When a volume is marked
as full, it
is also marked as read-only. The mminfo command can be used to
determine
the volume identifier.
Removing
Volumes
You
remove volumes from the media database in the Remove Volume dialog box.
•
Removing Client File Index Entries
•
Removing Client File Index and Media Database Entries
Removing
Client File Index Entries
By
removing just the client file index entries, you change the status of the
browsable
save sets to recoverable. When save sets are marked recoverable,
users
may no longer browse and recover these files. You would need to use the
save
set recover procedure to recover data once the client file index entries are
removed. For information, see "Save
Set Recovery" on page 451.
Removing
Client File Index and Media Database Entries
By
removing both the client file index and media database entries, you remove
all
knowledge of the volume from the NetWorker server. Remove only a
volume
from the media database if you think the volume has been physically
damaged
and is unusable. However, even if you remove the database entries
for
a volume, as long as the volume is undamaged, the data remains
recoverable
using the scanner program. For more information on the scanner
program, see "The scanner Program" on
page 462.
Client Time
Zone Adjustment
The
NetWorker software allows you to schedule backups over long-distance
networks.
In some cases, scheduling can occur over two or more time zones.
To incorporate
time zones into your backup schedules, you must adjust each
client time
zone setting by editing the client’s AUTOEXEC.BAT file.
How to
Adjust the Client Time Zone
To adjust
the time zone for backups of a remote client:
1. Open the
AUTOEXEC.BAT file using a text editor.
2. Enter
the following in the AUTOEXEC.BAT file:
TZ = <local_standard_timezone><+/- gmt_differences>
<local_daylight_savings_timezone>
Using
Autochangers with a Volume Import/Export Capability
The
NetWorker software supports the use of the SCSI-II import/export feature
found in
many brands of autochangers. Depending on the autochanger model,
this
feature is also known as cartridge access port (CAP), mail slot, and loading
port. The
import/export feature deposits and withdraws volumes from slots
in the
autochanger. This feature enables the operator to deposit and withdraw
cartridges
without invalidating the device inventory list. Normally, if the
operator
opens the door to load or unload media, the element status of the
autoloader
is invalidated, requiring the long operation of reinitializing the
autochanger.
However, the NetWorker server does not automatically
inventory
the volume after a deposit and withdraw.
How to
Deposit a Volume by Using the Import/Export Feature
To deposit
a volume by using the import/export feature:
1. Place
the volume in the import area of the autochanger. This area and procedure vary
with the type of autochanger. For specific instructions, refer to the
autochanger documentation.
2. In the
NetWorker Administrator program, click Autochanger from the Configure tab.
3.
Right-click the icon of the appropriate autochanger and select Operations.
4. In the
Autochanger Operations dialog box, click Deposit.
The
NetWorker software deposits the volumes with no further action necessary.
Depending
on the type of autochanger and how the volume is labeled, either the volume
name or a hyphen (-) appears in the Slot list of the Autochanger Operations
dialog box. In either case, inventory the volume.
How to
Withdraw a Volume by Using the Import/Export Feature
To withdraw
a volume by using the import/export feature:
1. In the
NetWorker Administrator program, click Autochanger from the Configure tab.
2.
Right-click on the icon of the autochanger whose volumes you want to deposit, and
select Operations.
3. In the
Autochanger Operations dialog box, select the volume you want to withdraw from
the Slot list and click Withdraw.
4. Remove
the volume from the autochanger. For specific instructions, refer to the
autochanger documentation.
Recycling
Compared to Adding More Volumes
The
NetWorker server saves files on volumes marked appen (appendable) in the
Volumes tab. If the volumes inside the autochanger are marked full, they
cannot receive backups.
Change the
volume mode to recyc (recyclable) in the Volumes tab of the NetWorker
Administrator program if you do not need the data on the full volumes. The
NetWorker server overwrites the data with new backups, but maintains the
existing labels. This is the only instance in which you do not need to relabel
a volume to make it eligible to be overwritten with new data.
When all of
the save sets on the volume have passed the time period specified by the
retention policy, the mode of a volume automatically changes to recyclable.
There are
advantages to both recycling media and adding more media to a pool. By
recycling, you reuse the same volumes and do not add new volumes to the pool.
However, the media may wear out over time and have a higher failure rate.
On the
other hand, if you need to store backups for a period of time, then you may
have to add more media to the pool instead of recycling it. For example, an
autochanger may need new volumes every three months if the company policy is to
maintain the backups for a year. In this case, you need to keep adding new
media to the pool until you can recycle the volumes that contain expired or old
backups.
Device
Calibration
For
information about the frequency and method for calibrating the loading mechanism
for the device, refer to the autochanger manufacturer’s documentation.
How to
Disable the Element Status
Some
autochangers support the element status feature. The NetWorker software uses
the element status feature to determine whether a slot contains a volume. If
volumes have barcodes, the element status feature speeds up the inventory
process by eliminating the need to load and read volume labels. If the volume
has a barcode label, the NetWorker software reads it without
loading
the volume. To disable the element status option for an autochanger if the
volumes do not have barcodes:
1. In the
NetWorker Administrator program, select Customize from the Options menu.
2. Select
Display Hidden Attributes and click OK.
3. From the
Configure tab, click Autochanger.
4.
Right-click the icon of the appropriate autochanger and select Edit.
5. Select
the Preferences tab.
6. For the
Jukebox Options attribute, clear the Elements Status attribute.
7.
Click OK.
How
NetWorker Software Interacts with a Silo
The
NetWorker server communicates with the silo through the Silo Tape Library
Interface (STLI), which must be installed on the
NetWorker
server that uses the silo. The silo management software controls many of the
operations that NetWorker software controls with an autochanger. For example,
the silo management software keeps track of the slot where each silo volume
resides, and may control the deposit and withdrawal of volumes, and automated cleaning
of silo devices.
NDMP Support for the NetWorker
Server
Any
communication to and from the NetWorker server to any NDMP device (servers,
disk, storage) communicates via NDMP.
The
NetWorker server with NDMP Connection supports the following configurations:
•
Local backup using NDMP Tape Server — backup performed to a local tape device
attached to the server
•
NetWorker Storage Node — The backup is performed from an NDMP host to a
NetWorker device. NetWorker storage nodes use a data server agent (DSA). Note:
Any backup performed via DSA has a D flag.
•
Three-party using NDMP Tape Server — The backup is performed from one NDMP
server to another NDMP server.
NetWorker
NDMP Requirements
The
following requirements must be observed when running NetWorker with NDMP
support:
•
To back up the bootstrap file, a non-NDMP device must
be attached to the NetWorker server. The bootstrap includes the media database
and configuration files needed for recovering the NetWorker server after a disk
crash.
SNMP
Module
Configuring
NetWorker SNMP Notifications
NetWorker
software provides notifications to a variety of resources about NetWorker server
events. The NetWorker SNMP Module is one of those resources. The module then
forwards the notification to the SNMP management software using the nsrtrap program.
When you configure the SNMP notification, you include the IP address or
hostname of the SNMP
management
server, along with other optional nsrtrap command line switches, such as
the SNMP community and the trap type.
Additional
Attributes in the Autochanger Resource
The
Autochanger resource now contains attributes that provide a detailed view of
options that the nsrjb program uses. These are hidden attributes. For information
about displaying hidden attributes, see "Hidden Attributes" on page
103.
Standards Operations
Configure Resources
CONFIGURING
RESSOURCES
1.
configure Schedule and Policy
resources first
2.
configure Group, Client, Pool
resources after
Figure
7 on page 89 illustrates the process for configuring NetWorker resources.
SPECIFY
SERVER ON NETWORKER USER CLIENT
winworkr -s RUDMSBACK01
SPECIFY
SERVER ON NETWORKER SQL MODULE CLIENT
nwmssql.exe -s RUDMSBACK01
GROUPS > RUDMSMANUF01 : edit details, modify Backup command
nsrsqlsv -s RUDMSBACK01
Estimate Group Save Set Sizes
Select the
Estimate and No Save options in the Options attribute of the Group resource.
Note: The Options
attribute is a hidden attribute; you must configure the NetWorker Administrator
program to display hidden attributes before you can access and change the
Options value.
To estimate
group backup save set sizes prior to starting the backup:
1. In the
NetWorker Administrator program, select Manage Groups from the Configure tab.
2.
Right-click the appropriate group and select Edit.
3. Select
the Preferences tab.
4. For the
Options attribute, select the Estimate and No Save options and click OK.
To see the
estimated save set sizes, open the daemon.log file located in the <NetWorker_install_dir>\logs
directory.
Notes:
• Selecting
the Estimate, No Save, and Verbose options produces an estimate showing all
paths saved in the group .
• Selecting
the Estimate and Verbose options produces a detailed estimate and performs the
save in one operation.
• Selecting
only the Estimate option (without the No Save or Verbose option) results in a
save operation without an estimate.
Scheduling
Large Client Filesystems
At a
moderate backup rate of 400 KB per second, a full backup for a client with 10
GB of data takes about 7 hours to complete
Start/Stop a Group Immediately
To start a
group immediately:
1. In the
NetWorker Administrator program, click Manage Groups from the Configure tab.
2.
Right-click the group to start, and select Start.
3. Click
Yes to start the group.
The
NetWorker server overrides the group’s scheduled start time and immediately
backs up the clients in the group. The current group icon changes to the clock
icon until the backup is completed or interrupted.
To stop a
group immediately:
1. In the
NetWorker Administrator program, click Manage Groups from the Configure tab.
2.
Right-click the group to stop immediately, and select Stop.
3. Click
Yes to stop the group.
The group
stops immediately, any running save sessions are aborted, and the NetWorker
Administrator program displays Not Finished in the Status attribute in the
Group Control window.
Important: If you
manually stop a scheduled backup, or if the backup is interrupted for some
reason (for example, due to a power failure), the Autorestart attribute is
automatically set to Disabled. To ensure that the scheduled backup restarts automatically,
set the Autorestart attribute to Enabled.
FORCE
INCREMENTAL
For groups
that have more than one scheduled backup within a 24-hour period, you can use
the Force Incremental attribute in the Group resource to instruct the NetWorker
server to perform only one full or level backup per 24-hour period. If the
Force Incremental attribute is set to Yes, the first backup is performed at the
configured level. All subsequent scheduled backups
during the
next 24 hours after the start time of the first backup will be incremental,
meaning that only changed files will be backed up regardless of the configured
level. This may be advantageous when an environment requires frequent scheduled
backups, but you want to minimize the impact on systems being backed up. The
Force Incremental attribute applies only to
scheduled
backups that the NetWorker server runs automatically. If the savegrp program
is run by other means, such as from the command prompt or a script, this
attribute is not used. If the Force Incremental attribute is set to No,
multiple full or level backups are allowed during the 24 hours after the start
time of the first backup.
Manual Backups
Note: Manual
backups only back up filesystem data, not the client file index entries that
are made during scheduled backups. If you do not create a customized pool to
receive data from manual backups, the NetWorker server uses the Default pool
and looks for a mounted volume from the Default pool on which to write data.
HOW TO LABEL AND MOUNT A DEVICE
0. Start
NetWorker Administrator program
1. Insert a
volume into the stand-alone device drive or slot 1 of the autochanger.
2. If
Device autodetection is enabled, the device should be listed in the Devices
window. If it is not enabled, you must either perform an autodetect, or create
the device manually.
• To perform an
autodetect:
a.
Click Set Up Server in the Manage Server section to open the Server window.
b.
Click the Device Configuration tab and select Now for the Search New Device
attribute.
c.
Click OK. The NetWorker software automatically detects devices attached to the
server.
• To create the device
manually:
a.
Click Devices in the Media Management section of the Configure tab to open the
Devices window.
b.
Right-click Devices and select Create.
c.
Enter the name of the device, and select the media type.
d.
Click OK.
3. From the
Devices window, right-click the icon representing the storage device, and
select Operations to open the Device or Autochanger Operations dialog box.
4. Click
Label.
5. From the
Label dialog box, select a pool for the Pool attribute.
Selecting a
pool automatically chooses a label for the volume.
6. If you
back up to a stand-alone device, select Mount After Labeling in the Label
dialog box.
7. If you
back up to a device in an autochanger, enter 1 in both the First Slot and
Last Slot attributes in the Autochanger Label dialog box.
8. Click
OK.
The
NetWorker software labels the volume. If the storage device is a stand-alone
device, the NetWorker software also mounts the volume and displays the name and
status of the volume in the Monitor window.
For
example: wangdat00 venus.001 labeling, done
Backing
Up Data
NetWorker
software contains preconfigured resources you can start using immediately;
therefore, when the volume is successfully labeled, you are ready to perform a
backup.
There
are two types of backups in the NetWorker environment:
•
Scheduled backups — These are configured in the NetWorker Administrator program
and are assigned a specific time for the backup to run, usually when network
usage is low. For example, the preconfigured Default group is scheduled to
begin its backup at 3:33 a.m. You can override scheduled backups to perform the
backup immediately, if necessary.
•
Manual backups — These are performed by the user of the client computer in the
NetWorker User program (winworkr).
To run a scheduled backup, you need only enable the default schedule. NetWorker
software can use Volume Shadow Copy Service (VSS)
How
to Start a Manual Backup
To
start a manual backup by using the NetWorker User program:
1.
In the NetWorker User program, click the Backup button.
The
NetWorker User program provides a graphical interface through which to perform
manual backups. For general information about the NetWorker User program, see "NetWorker
User Program" on page 113.
2.
In the left pane of the Backup window, click the appropriate directory folder.
3.
Select each directory and/or file you intend for manual backup by performing
one of the following:
• Select the directory or file and click the Mark button
To
clear an item, click the Unmark button.
•
Right-click the directory or file.
To
clear an item, right-click the directory or file again.
When
you mark a directory or file for backup, a check mark appears next to that
item.
Note:
If performing a NetWorker User backup on a NetWorker server, see
"Excluding
File Type Devices from Manual Backups" on page 406.
4.
Click the Start button to begin the manual backup.
The
Backup Status dialog box displays the progress of the backup.
When
the NetWorker server has successfully finished the backup, the nwbackup program
displays the following (or a similar) message: Backup completion time: 2-15-03
3:27p
Note:
If the backup fails due to a problem with VSS or a writer, an
error message will appear. Use theWindows Event Viewer to examine the event logs
for additional information. VSS backup error messages are also written to the
NetWorker log file.
Important:
There are certain kinds of corrupt files or errors on computer
disk volumes that NetWorker software cannot detect during a backup. It backs up
the corrupt data. It is a good idea to run diagnostic programs such as CHKDSK or
SCANDISK regularly on your computers to correct disk volume errors.
Backing Up
Data Manually from the Command Prompt
You can
also perform a manual backup from the command prompt by using the save.exe command.
For example, to back up C:\myfile to the server jupiter, enter
the following:
save.exe -s
jupiter C:\myfile
Archiving
Not
read chapter 8
Autochanger Inventory Problems
Any
of the following situations can cause the autochanger inventory to become
outdated:
•
The media is manually ejected from the autochanger drive.
•
The media is removed from the autochanger.
•
The autochanger door is opened.
An
outdated inventory means that NetWorker software cannot use the autochanger. To
make the autochanger usable again:
1.
Verify that the media cartridge is correctly installed in the autochanger and
that the autochanger door is closed.
2.
Log on as a member of the Windows Administrators group on the NetWorker server.
3.
Reset the autochanger by entering the following command at the prompt:
nsrjb
-Hv
4.
Perform an inventory by entering the following command at the prompt:
nsrjb
-Iv
After
the inventory operation is finished, the NetWorker server can once again use
the autochanger.
For
complete information on the use of the nsrjb command, refer to the nsrjb(8) man
page or see "Chapter 10: Autochangers and Silos" on page 505.
Unapproved Server Error
If
an unapproved server attempts to contact a client for backup during a scheduled
backup, the following message appears in the Group Control . Details dialog box
of the NetWorker Administrator program:
client_name:server_name
cannot request command execution
After
installation, if you want the client to accept backup requests from other
NetWorker
servers, you must add the name of the additional NetWorker
servers
to the servers file.
The
preferred method of editing the servers file is to run NetWorker Setup
program
in maintenance mode and edit the Allowed Servers list. For detailed
instructions,
refer to the LEGATO NetWorker Installation Guide, Microsoft
Windows
Version.
Alternatively,
you can use the following procedure to edit the servers file:
1.
Using the Windows Control Panel Services tool, stop the NetWorker
Remote
Exec Service.
2.
Open the <NetWorker_install_path>/res/servers file in a text editor.
3.
Enter one server name per line.
4.
Save the changes and exit the text editor.
5.
Restart the NetWorker Remote Exec Service.
Cloning
Volume
Cloning Performance
In general,
a volume write occurs at the same speed whether it is part of a backup
operation or a cloning operation.
Data Tracking Information
Each save set clone shares the same save set ID
(ssid) as the source save set
-
If the source save sets are still browsable, the clone status is also browsable.
-
If the source save sets have passed their browse policies, the clone status is
recoverable.
Cloned
save sets are only tracked through the media database. Volumes that belong to a
clone pool are also tracked through volume entries in the media database.
Changing
the Mode of a Volume Clone to Recyclable
In some
cases, you might want to manually change the mode of a clone volume to recyclable,
with the intent of reusing that clone volume. However, keep in mind that the
mode of a volume only changes to recyclable when all the save sets on that
volume are recyclable. Therefore, when you change the mode of the clone volume
to recyclable, you effectively change the status of all save sets on the volume
to recyclable. Because the save sets share the same entry in the media
database, there is no distinction between original and clone save sets. The end
result is that all the save sets that reside on the now-recyclable
volume, or
on any other volume, become candidates for immediate recycling. Important: Changing
the mode of a clone volume to recyclable results in all primary save sets
related to that clone volume being marked recyclable as well. This could result
in data loss. If you want to reuse a particular clone volume and still protect
the save sets that exist on other volumes from inadvertent data loss, first
change the mode of the volumes that you want to protect to manually recycle.
This way, the NetWorker software cannot automatically recycle the volume. Then,
you can safely change the volume that you intend for reuse to recyclable mode. For more information about changing the status of a save
set, see "How to Change the Status of a
Save Set" on page 218. You can execute
the scanner program on a clone volume to rebuild entries in the client
file index, the media database, or both. After you re-create the entries,
normal recovery is available.
Purging a
Clone Volume
Similarly,
if you purge a clone volume, you effectively remove from the client file
index all the file entries associated with all the save sets that reside on the
clone volume (in whole or in part)
Deleting a
Clone Volume
If you delete
a clone volume, the nsrim index management program locates the entry
in the media database for each save set that resides on the clone volume. The nsrim
program then marks the information about the location of one of the save
set clones for deletion from the entry. This action is performed for each save
set entry. In addition, nsrim marks the entry for the particular clone volume
(identified by its volume ID number) for deletion from the database.
How to
Create a Clone Volume
1. In the
NetWorker Administrator program, click Clone Volumes from the Configure tab.
2. In the
Clone Volumes window, select the volume to clone from the Clone Volumes list,
and click the Clone button.
3. Select a
pool from the Clone Pool list.
Cloned
volumes must belong to a clone pool, either one of the preconfigured clone
pools or one you create. If you do not select a clone pool, the NetWorker
software automatically selects a pool for you.
4.
Click Clone
The
Volume Clone window appears, showing the status of the cloning operation
Save
Set Clone Status
To
determine whether a save set on a volume has been cloned, or is itself a clone, check the Volume Save Sets window,
which lists all the save sets contained on the currently selected volume. For
an example of the Volume Save Sets window and instructions for displaying it,
see "Volume Save Sets" on page 347.
Save Set
Cloning
Cloning
save sets allows you to create identical copies of backed-up data quickly and
easily. The save set cloning feature provides a high degree of flexibility for
determining which data to copy. You can clone save sets automatically or
manually. You can also clone a single save set, or configure the software to
clone only full backups for an entire group.
Verifying and Monitoring Operations
How to monitor Operations
Events Notifications
There are 2
Main Log Files in the <NetWorker_install_dir>\logs
messages.log
—generated
by nsrlog
daemon.log—generated
by nsrd, nsrexecd
rap.log
- The Monitor RAP (resource
allocation protocol) attribute in the Server resource tracks the history of
additions, deletions, or modifications to NetWorker resources and their
attributes. The rap.log file lists the user name, the source computer, and
the time of the modification sufficient to undo any changes
Create a Notification
Notifications
of events can be sent via e-mail, logged to file, SNMP message, or programs
executed when an event occurs.
1.
In the NetWorker Administrator program, click the Server Notifications icon in
the Configure tab
2.
Right-click the main Notifications icon, and select Create to open the Create
Notification dialog box.
3.
Verify that Hidden Attributes are enabled:
4.
In the Action attribute, enter the name of the command you want the NetWorker
server to use.
Ex
. to use the nsrtrap program to send a message to a network management
console about a volume that needs mounting, enter: <NetWorker_install_dir>\bin\nsrtrap
-s 1 host
How to monitor a Remote Server
1. From the
Option menu, select Remote Servers to open the Remote Servers dialog box.
2. In the
Server Name text box, enter the name of the remote NetWorker server, then click
Add.
3. Click
OK.
Reports
The
following sections describe various aspects of the NetWorker reporting function
Bootstrap
Report
When
the NetWorker server finishes a scheduled backup that includes the NetWorker
server, it creates a bootstrap save
set, which contains backups of the client
file index, media database, and NetWorker configuration files. The data
in the bootstrap save set is required to re-create the NetWorker
server in the event
of a disaster
Completion
Report
The
degree of success in the completion of scheduled backups is reported to you by
the savegrp program through a Savegroup Completion Report sent to the log file in <NetWorker_install_dir>\logs\messages.
The
report consolidates the following information:
•
Success or failure of each save set participating in the operation
•
Bootstrap save set ID
•
Bootstrap volume location (volume name, starting record number, and ending
record number)
How to
Monitor and Verify Data during a Backup
To monitor
and verify data during a backup:
1.
Right-click the Default icon in the Groups window and select Edit to open the
Edit Group Default dialog box.
2. When the
NetWorker Administrator prompts you to confirm that you want to start backing
up the group, click Yes.
3. Click
the Monitor tab.
In the
Messages window, the NetWorker server displays detailed messages about the
progress of the backup.
Note: If the
backup fails due to a problem with VSS or a writer, an error message will
appear. Use theWindows EventViewer to examine the event logs for additional
information. VSS backup error messages are also written to the NetWorker log
file
How to
Verify Data
Use the
NetWorkerVerify feature to ensure that backup data on the NetWorker
server
matches the data on the local disk. The Verify feature compares the file
types, file
modification times, file sizes, and file contents. It does not verify
other
system attributes, such as read-only, archive, hidden, system,
compressed,
and file ACL.
To verify
your data:
1. In the
NetWorker User program, click the Verify button.
2. Mark the
data items you want to verify.
3.
Click the Start toolbar button
How to View
the Group Details Dialog Box
You can
also view information about the backup in the Group Details dialog box.
To open the
Group Detail dialog box from the main window of the NetWorker Administrator
program:
1.
Right-click the Default Group icon.
2. Select
Details.
The
NetWorker Administrator program lists the successful, or unsuccessful save sets
in the Group Detail dialog box.
The Group
Status tab in the Messages window at the bottom of the NetWorker Administrator
program also displays the group icons and messages about the progress of the
backup.
Note: If you have
a stand-alone storage device, make sure that you leave the volume in the
device; otherwise, the NetWorker software will not be able to begin the
scheduled backup for the Default group at 3:33 a.m.
How to
Verify Backup Servers
You can
verify the servers that are authorized to back up a client computer by
checking
the client’s <NetWorker_install_path>\res\servers file, which
lists the
servers
that are authorized to back up the computer.
How
to Verify That the NetWorker Processes Are Running
To
verify that the NetWorker processes are running:
1.
Open the Task Manager.
2.
Click the Processes tab to display running processes.
3.
Depending on the type of installation, the processes listed in Table
6 on
page
92 should be running:
Type of
Installation Processes
NetWorker
Server
nsrd — NetWorker
server
nsrexecd — NetWorker
client
nsrmmd — NetWorker
media multiplexer (one process per device)
nsrmmdbd — NetWorker
media management database
nsrindexd — NetWorker
file index database
NetWorker
Client
nsrexecd — NetWorker
client
NetWorker
Storage Node
nsrexecd — NetWorker
client
nsrmmd — NetWorker
media multiplexer (one process per device)
How
to View a Message
Messages
appear in the NetWorker Administrator program and are also written to message
logs.
To view a
message:
• In the
NetWorker Administration program:
–
Double-click a server listed in the Pending Messages tab to see information
about a particular server’s activity and performance.
– Click the
Monitor tab to see messages relating to the NetWorker server to which you are
currently connected.
• In
message logs:
– View
current messages in <NetWorker_install_path>\logs\networkr.log for
messages created since the most recent save or recovery.
– You can
also see messages or notifications in the bootstrap notification, as well as
the following log files:
<NetWorker_install_path>\logs\messages
(Windows Event Viewer application log).
<NetWorker_install_path>\logs\savegrp.log
(savegroup completion report).
<NetWorker_install_path>\logs\media.log
(media I/O error messages)
Customizing
and Configuring the NetWorker Software
Once you
have used some of the basic features of the NetWorker software, you
can start
to customize and configure NetWorker settings for an environment.
The
NetWorker software enables you to configure some or all of its settings.
You can
also mix customized and preconfigured settings in any combination.
Preconfigured
Settings
You can
fully use and evaluate NetWorker software with the default settings
that are
automatically assigned to resources and attributes (for example, the
Default
pool). Whenever you create a new resource, or if you use the Setup
Wizard to
configure your server, clients, storage devices, and volumes, you
always have
the option of using default attributes and preconfigured
resources.
Configuration
Planning
Configuration
planning helps to clarify the interdependencies and trade-offs
in
implementing an overall backup strategy. Careful configuration planning is
the most
critical factor in ensuring that backups run smoothly and recoveries
proceed
efficiently and without error.
To plan a
configuration:
1. Draw a
diagram of the networked computers to be used as NetWorker
servers and
clients. Identify potential network trouble spots, such as
computers
on the other side of a firewall or routers that might not be able
to
successfully back up to the NetWorker server.
2. Estimate
the size of the average daily backup window for the enterprise
(the period
of time set aside for backing up data on the network). Identify
special
circumstances that might alter the size of the backup window, such
as weekend
activity, operator availability (if a stand-alone device is being
used), or
end-of-quarter requirements.
3. Identify
the amount of data that must be backed up by each computer and estimate the
total amount of backed-up data. Estimate how long backups will take, given the
characteristics of the specific environment (for example, network bottleneck
speeds, device speeds, and data availability). Organize and prioritize data into
clusters that can begin backups at the
same time
of day (so that they can be organized into NetWorker backup groups). This step
is most appropriate if backups require load balancing or staggered schedules to
accommodate the constraints of the backup’s allotted time.
5. Decide
how long different data should remain in the storage management system for
users to browse and recover. The availability of data files might need to be
weighed against the space required to maintain the file entries within the
client file index.
6. Decide
how data should be organized within the storage management system. By using
NetWorker pools, you can send specific save sets of data to designated
collections of volumes. For example, one pool may be designated for all client
backups of an organization’s accounting department.
7. Identify
the trade-offs and select optimal values for the following performance
features:
• Number of
devices to use for backups
• Number of
devices to reserve for recoveries
• Number of
data streams to be interleaved onto a single volume
• Number of
data streams to send to each NetWorker server and storage node
8. If a VSS
license is available, decide whether to perform a backup that uses VSS or the
legacy method, and disable writers if necessary.
• If VSS is
licensed and enabled, the default backup method is VSS.
• If you
use a NetWorker module to back up data associated with a specific application,
you need to disable the VSS writer associated with that application.
Volume
Shadow Copy Service
VSS acts as
a coordinator between all the components that create, archive, modify, back up,
or restore data: the operating system, storage hardware, applications such as
SQL Server, and utility or backup programs such as LEGATO NetWorker.
In
NetWorker release 7.1, if a VSS client license is present, NetWorker software takes
advantage of VSS technology to create snapshot backups of volumes and exact
copies of files, including all open files.
Processes
NetWorker
Server nsrd — NetWorker server
nsrexecd — NetWorker
client
nsrmmd — NetWorker
media multiplexer (one process per device)
nsrmmdbd — NetWorker
media management database
nsrindexd — NetWorker
file index database NetWorker Client - NetWorker Storage Node
nsrexecd — NetWorker
client
nsrmmd — NetWorker
media multiplexer (one process per device)
TCP/IP
Network Requirements
The
following are the requirements for TCP/IP network communication when using
NetWorker software:
• The
NetWorker server name must be added to the domain name system (DNS) file that
contains the names and aliases of the servers (hosts) on your network, or to
the local hosts file located in %SystemRoot%\system32\drivers\etc.
Note: If DNS is
used, reverse lookup must be correctly configured.
• If the
NetWorker server is a dynamic host configuration protocol (DHCP) client, it
must use a reserved address.
• If DHCP
with dynamic addresses is used, DHCP must be synchronized with DNS.
• Use the
same name for the NetWorker server’s TCP/IP hostname and the Windows computer
name.
Two
NetWorker Software Configurations with Service Ports
Two
common NetWorker software configurations exist:
•
Storage node on the same side of the firewall as the NetWorker client (Figure
13 on page 157).
•
Storage node on the same side of the firewall as the NetWorker server (Figure
14 on page 159).
Both
NetWorker software configurations use the following services to facilitate
communication and perform tasks:
•
nsrd
•
nsrexecd
•
nsrindexd
•
nsrmmd
•
nsrmmdbd
Each
service has one service port, except for nsrexecd, which has two fixed service
ports: 7937 and 7938. Port 7937 is the service port used for starting commands.
Port 7938 is the service port used for the LEGATO portmapper.
The
port numbers used by the services, except for nsrexecd, are assigned
from the service port range that is set in the NetWorker software. One service
port is used for each nsrmmd process.
Dynamic
Drive Sharing (DDS) is a feature that provides NetWorker software
with the
ability to recognize shared drives. Two terms central to the use of DDS are drive
and device.Within the context of
DDS, these
terms are defined as follows:
• Drive —
The physical backup object, such as a tape drive, disk, or file.
•
Device — The access path to the physical drive.
Overview
of NDMP
NDMP
is a TCP/IP-based protocol that specifies how network components
talk to each other for the purpose of moving data contained on each component
across the network for backup and recovery.
NetWorker
Administrator Interfaces
You
can administer a NetWorker server software by the following methods:
•
Using the graphical NetWorker Administrator program (nwadmin). For
more
information, see "NetWorker Administrator Program" on
page 99.
•
Using the character-based NetWorker administration interface
(nsradmin).
For more information, see "NetWorker Character-Based Interface"
on page 113.
•
Using the command line. For more information, see "Command
Line Interfaces" on page 113.
How to
Modify the Window Configuration
To modify
the way the NetWorker Administrator program displays certain resource
information:
1. Select
Customize from the Options menu to open the Customize dialog box.
2.
Select the Window Configurations tab.
How to View
the Server Window in Expanded Server Resources Mode
To view the
server window in Expanded Server Resources mode:
1. Select
Customize from the Options menu to open the Customize dialog box.
2. Select
the Go Directly to Expanded Server Resources check box, and then click OK.
Adding
Resources by Using Drag and Drop
You can use
the drag-and-drop feature in the NetWorker Administrator
program to
add clients to your NetWorker server, move clients between
backup
groups, and perform other functions by dragging one resource icon
onto
another
Optimizing performance
+ Using MULTIPLEXING
The
Parallelism and Target Sessions attributes are used.
By
definition, save sets that are multiplexed must belong to the same pool of
storage volumes. The NetWorker parallelism allows
to back up data from many clients concurrently, and multiplex the data onto the
same backup volume. The Parallelism attribute is located in the Set Up Server
dialog box . The maximum parallelism for any NetWorker server and storage node
combination can vary as described in Table 18 on page 132.
+ Using VSS
- Disable
VSS for a particular drive. For example: VSS:c:\=off . The specified
drive is backed up using the legacy method. Or Instruct NetWorker software to
back up the filesystem by using VSS only. VSS:root drive path=only
To indicate all drives, enter: VSS:*:=only
+ Using WRITERS
-
Disable an individual writer. VSS:writer=off
where writer is the name of the writer to disable.
For example: VSS:MicrosoftExchange Writer=off . When a
writer is disabled, NetWorker software still processes it so its files are
skipped during the filesystem backup.
Disaster Recovery
Disaster Recovery Procedures
In this context, a “Disaster” is a failure or
incident impacting the Legato infrastructure. We need in this case to be in the
capacity to recover the whole infrastructure or some parts, for example a
Legato server or a Legato Client, and their filesystems at the time prior to
the event or after this one, depending on the nature of the event. Disasters
are evaluated in the Risk Management Plan.
Requirements
for operating Major Disaster Recovery & Disaster Recovery
Information
Table needed as per immediately prior to the disaster
Windows
Recovery Requirements
|
•
Operating system version and any installed patches, service packs, or option
packs
|
• Path
location of the operating system installation
|
• Host
properties:
|
– Computer name
|
– Fully
qualified domain name
|
–
Administrator account password
|
• TCP/IP
properties:
|
– Adapter
type
|
– IP
address
|
– Default
gateway
|
– Subnet
mask
|
– DNS
server
|
– WINS
server (if used)
|
• Any
other protocols installed
|
•
Removable Storage enabled/disabled settings
|
• Virtual
memory settings
|
• Date
and time properties
|
•
Localization properties
|
Legato
Recovery Requirements
|
• Legato
Client Information :
|
– Client name
|
– Client
index
|
– Client
save-set
|
– Client
save-set
|
• Legato Server Information
|
–
Bootstrap
- Save
sets
-
Policies
- Groups
- Indexes
- Logs
|
Recovery Methods
NetWorker
provides 2 types of recovery methods:
Bootstrap Recovery
Run the
nsrjb -vHE command from the command prompt. This resets the autochanger, ejects
backup volumes, reinitializes the element status, and checks each slot for a
volume. If the autochanger does not support the -E option (to reinitialize the
element status), use the sjiielm command to initialize the element status.
No comments:
Post a Comment