Chapter 01 - NetWorker Overview

Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved.
Chapter 1 - EMC NetWorker Overview
Upon completion of this chapter, you will be able to:

y Explain NetWorker hosts and their functions
y Explain NetWorker control data and its use
y Explain the purpose of each NetWorker daemon/service
y Explain EMC NetWorker advantages
y Describe interprocess communication during a backup
© 2006 EMC Corporation. All rights reserved. EMC NetWorker Overview - 1
In this chapter you learn about NetWorker components including host roles, control data,
daemons (UNIX) or processes started by NetWorker services (Windows), and the role of each
component in providing backup protection for your important data. You also learn about the
advantages of using EMC NetWorker®. Lastly, a brief overview of the backup process will be
presented.
EMC NetWorker Overview, Page 1-1

NetWorker Hosts
Processes and Functions

The NetWorker Solution
App
App Oracle
SQL
SQL App
EMC
IT App
App NetWorker
Solution
Operating
Operating
System
System
Hardware
Hardware
There are many pieces in an overall solution for your business computing needs. EMC
NetWorker works within the existing framework of hardware, operating system software, and
network communication protocols to provide protection for the critical data that the framework
supports.
NetWorker protects critical business data by centralizing, automating and accelerating backup
and recovery operations across an enterprise. NetWorker provides support for the latest disk
backup and snapshot technologies.

NetWorker Hosts
The NetWorker
Server
Server supports
the backup and Node NetWorker
Node stores tracking Storage Node(s)
and configuration write data to
Client
information. and read data
Client
from devices.
NetWorker Client(s)
Client
generate the
backup data.
NetWorker Data Zone
There are three types of NetWorker hosts.

y NetWorker Server
y NetWorker Client(s)
y NetWorker Storage Node(s)
A NetWorker Data Zone consists of a single NetWorker server and its storage node(s) and
client(s). Another way to define a data zone is to say it is the set of hosts managed by a single
NetWorker server. This includes all hosts that have backup devices controlled by the
NetWorker server and all hosts who send their backup data to those devices.
NetWorker clients may be backed up by multiple NetWorker servers and therefore may belong
to multiple data zones. NetWorker servers and storage nodes may belong to only one data zone.

NetWorker Client
Server
Node Node
Client Client
y Generates backups Save Set

y Generates tracking information Client
y Performs recoveries
y Provides user interfaces for backup
and recovery
The NetWorker Client is the largest NetWorker software component and the fundamental host.
The client’s most important functions are to generate backups (also called save sets), push them
to a NetWorker storage node, and retrieve them during a recovery. NetWorker clients are
usually the data servers in an IT environment.
While performing a backup, the client also generates tracking information (including the name
of each file and directory backed up and the time of the backup) and sends it to the NetWorker
server where it is stored. This tracking information is used to facilitate point-in-time recoveries.
The client software includes graphical user interfaces (GUIs) and command-line utilities which
allow users to manually perform backup and recovery operations. NetWorker client software is
installed on all participating hosts in the data zone, including hosts that also perform the
functions of NetWorker server and NetWorker storage node.
Note: Every host in a NetWorker data zone is a NetWorker client.

NetWorker Storage Node
Server
Node
Node
Client
Client
y Organizes the backup data

y Writes data to a backup device
Client
y Sends tracking information to the
NetWorker server
y Reads data from the device during
recoveries and cloning
A NetWorker Storage Node is a host that physically controls a backup device and responds to
requests from the NetWorker server. The device may be either a direct-attached or SAN-
accessible device. If a device is controlled by a host other than the NetWorker server, it is
considered a remote device and the storage node controlling the device is referred to as a remote
storage node.
The NetWorker server is always a storage node and is the default storage node for backups.
Using remote storage nodes is optional, although they distribute the backup workload and can
reduce network traffic. Storage node hosts have both the NetWorker client and storage node
software installed.
During a backup, a NetWorker client sends backup data to a particular storage node based on the
client’s configuration. During a recovery, the client reads from the storage node that controls the
device containing the necessary volume.
Storage nodes also send tracking information, including details about save sets written to the
volume during a backup, to the NetWorker server. This information is used for future backups
as well as for recoveries.
Note: See nsr_storage_node(5) in the EMC NetWorker Command Reference Guide

(man pages) for more information.

NetWorker Server
CFI
CFI
Server CFI
Node Node
Media
Database
Resource Client
Client Directory
y Supports client backup and recovery

y Stores and manages tracking and Client
configuration information
y Backs up tracking and configuration
information
The NetWorker Server is the host that stores the configuration information, such as supported
clients and devices, when to run the backups, what data to back up, etc. The NetWorker server
also stores the online NetWorker databases that track the backups and volumes. These include
the Client File Indexes (CFI) and Media Database. The NetWorker server, as a client within the
data zone, automatically backs up the configuration information and tracking databases to
protect NetWorker data.
There is a single NetWorker server per data zone and it must be available for any NetWorker
activity to be supported in that data zone. NetWorker servers have NetWorker client, storage
node, and server software installed.
Note: See the nsr_service(5) man page for more information.

NetWorker Control Data
CFI
CFI
CFI
Server
/nsr/index/
Node
Media
Resource Database
Client Directory
/nsr/mm/
/nsr/res/
For a Microsoft Windows NetWorker Server, replace /nsr

with <drive>:\Program Files\Legato\nsr
NetWorker control data is the collection of NetWorker configuration information and the
backup tracking information stored on the NetWorker server. NetWorker control data includes
three components:
y Resource Directory: This directory (the resource database) contains the resource files.
y Media Database: This database is used to track all volumes used by NetWorker and all
save sets written to those volumes.
y Client File Indexes (CFI): These databases track each file (pathname) backed up by
clients, allowing users to browse their backups for files from a
particular point in time. The NetWorker server creates and
maintains one CFI per physical client.
The next several pages provide more details on each NetWorker control data component.
Note: See the nsr_layout(5) man page for more information.

Control Data - Resource Files

nsr
res
nsrdb jobsdb nsrladb
00 01 02 03 04 05 06 07 08 09 00 01 02 03 04 05 06 07 08 09
Sample contents of a resource file in /nsr/res/nsrdb/*/*

action: full incr incr incr incr incr incr;
comment:;
name: Default;
override:;
period: Week;
type: NSR schedule;
resource identifier: 49.0.60.9.23.70.11.67.10.8.3.73(1)
NetWorker stores and maintains configuration information as resources. Resource information is

stored in resource files located below the /nsr/res directory. Subdirectories containing
resource files include:
• nsrdb - The files below this directory contain configuration information describing clients,
devices, jukeboxes (autochanger, library, or silo), backup start times, backup
schedules, licenses, etc. This directory exists only on the NetWorker server. The
slide shows an example of a NetWorker Schedule resource, which defines the backup
level used each day of the week.
• nsrladb – The files below this directory contain resource information used to determine the
RPC port range used by this host when receiving connections from and making
connections to other NetWorker hosts. All NetWorker hosts use this directory.
• jobsdb – This directory contains statistics and information generated by operations such
as backups, and is used by NMC for reporting.
Note: See Chapter 3, NetWorker Resources and Administrative Interfaces, and the
nsr_resource(5) man page for more information.
Important: NetWorker resource files are text files and are to be managed only through
NetWorker administrative interfaces. Do not edit them directly!!

Control Data - Media Database
Media
Database
volume client date time size ssid fl lvl name

leg_win1.001 leg-win1 10/3/2005 3:33:51 AM 227 KB 3795902175 cr full bootstrap
leg_win1.001 leg-win1 10/3/2005 3:33:26 AM 59 KB 3863011014 cr 9 index:leg-win1
leg_win1.001 leg-win1 10/3/2005 3:33:23 AM 4 B 3879788227 cb incr C:\WINNT\Fonts
leg_win1.001 leg-win1 10/3/2005 3:33:16 AM 4 B 3896565436 cb incr C:\WINNT\Cursors
leg_win1.001 leg-win1 10/3/2005 3:33:15 AM 323 KB 3913342651 cr 9 index:leg-sun2
leg_win1.001 leg-sun2 10/3/2005 3:35:57 AM 4 B 3930119860 cb incr /usr/bin
leg_win1.001 leg-sun2 10/3/2005 3:35:56 AM 4 B 3946897075 cb incr /etc
leg_win1.001 leg-win1 10/2/2005 3:34:01 AM 192 KB 3963587945 cr full bootstrap
leg_win1.001 leg-win1 10/2/2005 3:33:37 AM 59 KB 4013919569 cr full index:leg-win1
leg_win1.001 leg-win1 10/2/2005 3:33:22 AM 8391 KB 4047473989 cb full C:\WINNT\Fonts
leg_win1.001 leg-win1 10/2/2005 3:33:21 AM 389 KB 4064251204 cb full C:\WINNT\Cursors
leg_win1.001 leg-win1 10/2/2005 3:33:23 AM 323 KB 4081028419 cr full index:leg-sun2
leg_win1.001 leg-sun2 10/2/2005 3:35:55 AM 31 MB 4097805621 cb full /usr/bin
leg_win1.001 leg-sun2 10/2/2005 3:35:54 AM 2742 KB 4114582834 cb full /etc
The Media Database stores tracking information describing all save sets backed up within the
data zone and all volumes labeled by NetWorker. Save set information includes:
y Save set name
y Volume storing the save set
y NetWorker client that created the save set
y Date and time the save set was backed up
y Size of the save set
y Unique save set identifier (SSID)
y Aging status
y Backup level
Volume information includes:
y Volume name
y List of save sets on the volume
y Volume status
y Name of media pool that the volume belongs to
Note: Many more pieces of information are maintained in the media database. See the
mminfo(1) man page for more information.

Control Data - Client File Indexes
CFICFI
CFI
C:\WINNT\Fonts\8514fix.fon, date=1128238402 Sun Oct 02 03:33:22 2005

C:\WINNT\Fonts\8514oem.fon, date=1128238402 Sun Oct 02 03:33:22 2005
C:\WINNT\Fonts\8514sys.fon, date=1128238402 Sun Oct 02 03:33:22 2005
C:\WINNT\Fonts\app850.fon, date=1128238402 Sun Oct 02 03:33:22 2005
C:\WINNT\Fonts\arial.ttf, date=1128238402 Sun Oct 02 03:33:22 2005
C:\WINNT\Fonts\arialbd.ttf, date=1128238402 Sun Oct 02 03:33:22 2005
C:\WINNT\Fonts\arialbi.ttf, date=1128238402 Sun Oct 02 03:33:22 2005
C:\WINNT\Fonts\ariali.ttf, date=1128238402 Sun Oct 02 03:33:22 2005
C:\WINNT\Fonts\ariblk.ttf, date=1128238402 Sun Oct 02 03:33:22 2005
C:\WINNT\Fonts\cga40850.fon, date=1128238402 Sun Oct 02 03:33:22 2005
C:\WINNT\Fonts\cga40woa.fon, date=1128238402 Sun Oct 02 03:33:22 2005
C:\WINNT\Fonts\cga80850.fon, date=1128238402 Sun Oct 02 03:33:22 2005
A Client File Index (CFI) stores client-generated information about a client’s backed up files
and directories. For each file and directory that is backed up, a CFI contains its pathname, file
attributes such as permissions and ownership, and the time stamp of when the save set
containing the file was backed up.
NetWorker clients send tracking information to their CFI, which resides on the NetWorker
server. A single CFI exists for each physical client.

NetWorker Management Console (NMC) Server

Data Zone Data Zone
Tracking Data Report Tracking Data
Server Configuration Configuration Server

Information Information
Node Node
NMC Server
Client Client Client Client Client

Client
Client
y Provides a Java interface for configuration and management of

NetWorker server(s)
y Can gather information about backups from multiple data zones
y Can generate detailed, customizable reports
Starting with NetWorker 7.3, administration of a NetWorker server is performed using the
NetWorker Management Console Server (NMC) GUI (commonly referred to as the Console
Server), a Java-based interface accessible from any supported web browser.
The Console server provides a global view of your NetWorker environment, allowing you to
centrally manage one or more NetWorker data zones. There will normally be only one Console
server in an enterprise, but multiple servers are allowed.
The Console server must have the NetWorker 7.3 (or later) client software already installed.
The Console server can generate a number of preconfigured reports using information gathered
from any or all of the NetWorker servers. Detailed customized reports can also be created.
Reporting is discussed in Chapter 12, Administering the NetWorker Management Console
Server.

Core NetWorker Daemons
nsrindexd
CFI
CFI
CFI
nsrd
Server
Resource nsrmmd
nsrmmd Directory nsrmmdbd
Node Media Node
nsrjobd DB
Client Client
nsrexecd nsrexecd
nsrexecd
Client
NetWorker daemon processes are involved in almost all NetWorker operations, including
backups and recoveries. There are one or more NetWorker daemons to support each of the three
NetWorker host functions:
y Client daemon
y Storage node daemon
y Server daemons
In a Microsoft Windows environment, the core NetWorker processes shown in the slide are
started via two NetWorker services.
The following pages provide more details about each of the core NetWorker daemons.
There are additional daemon processes associated with NetWorker Management Console.
These will be discussed shortly.

NetWorker Client Daemon: nsrexecd
y Listens for, authenticates, and supports remote

execution requests from the NetWorker server
y Determines which RPC ports to use to support
and request NetWorker services over the network
nsrexecd
Client
The NetWorker client daemon, nsrexecd (network save and recover execution daemon),
runs on NetWorker clients to support remote execution requests from NetWorker servers. For
example, nsrexecd executes a backup command at the request of the NetWorker server. The
nsrexecd process also determines which RPC ports to use to support and request NetWorker
services.
In a UNIX environment, nsrexecd is started automatically during system boot up. In a
Windows environment, nsrexecd is started via the NetWorker Remote Exec Service, which is
configured to start automatically during boot up.
Note: See the nsrexecd(1m) man page for more information.

NetWorker Storage Node Daemon: nsrmmd
y Receives backup data from nsrmmd

the client
y Reads from and writes to nsrmmd
NetWorker backup devices
Node
y Organizes backup data
y Supports simultaneous Client
backups nsrexecd
y Sends tracking information

to the media database
There is one nsrmmd per device.
The NetWorker Storage Node daemon, nsrmmd (network save and recover media
multiplexing daemon), runs on NetWorker storage nodes to support reading and writing of data
to devices. One nsrmmd is started for each device configured as a NetWorker resource.
The nsrmmd daemon:
y Receives backup data (save streams) from NetWorker clients.
y Writes the data to a volume in the backup device it is controlling.
y Can receive data from multiple backups concurrently, organizing the data into a special
NetWorker format which supports multiplexing.
y Sends tracking information to the NetWorker server to track data written to the volume.
y Reads data from the volume during operations such as recoveries and cloning.
Note: See the nsrmmd(1m) man page for more information.

NetWorker Server Daemons

y Manages the master resource database (directory)
y Starts the other server and storage node daemons
y Initiates scheduled backups Manages the Client File
y Manages all backups and recoveries Indexes
nsrindexd CFI
CFI
CFI
Server nsrd
nsrmmd Resource
Node Directory nsrmmdbd Manages the Media
Database
nsrjobd Media
DB
Client
nsrexecd
Coordinates all scheduled backups, and manages
the resulting information and statistics.
The NetWorker server daemons provide access to NetWorker services such as configuration
information, support for backup and recovery requests, and access to the media database and
client file indexes. There are four NetWorker server daemons.
y nsrd - (network save and recover daemon) is the master daemon. nsrd manages the
NetWorker resource database, which contains almost all NetWorker configuration
information. It also starts the nsrmmdbd and nsrindexd processes. nsrd is
started automatically at system startup via a run-control script. Once started, nsrd
starts the other server daemons and one nsrmmd process for each device local to the
NetWorker server.
y nsrmmdbd - (network save and recover media management database daemon) provides
the read and write service for the media database.
y nsrindexd - (network save and recover index daemon) provides the read and write
service for the client file index databases.
y nsrjobd – (network save and recover job daemon) is responsible for coordinating all
scheduled backups. It stores information about these operations and provides it
to the NetWorker server and the NMC server for reporting purposes.
Note: See the nsrd(1), nsrmmdbd(1m), nsrindexd(1m), and nsrjobd(1m) man pages
for more information.

Console Server Daemons

y Starts the other Console Server daemons
y Manages communication with Console
client after initial HTTP request
y Can generate detailed reports
Reports
Data Zone Data Zone
lgto_gstdb
NW Server NW Server
gstd
Jobs NMC Server Jobs
DB gsttclsh dbsrv9 DB
Client
y HTTP daemon that responds

to an initial HTTP request from y Manages the Generic Services
a console client Toolkit (GST) database
The three NetWorker Management Console daemons are:

gsttclsh – This process is basically a mini web server. A Console client initially
communicates with this process when connecting to the Console server. Once
communication is established between the client and the server, gsttclsh is no
longer used for that session.
gstd – This process is the master Console process and is responsible for starting the
gsttclsh and dbsrv9 processes. After a Console client has established
communication with the Console server, all further communication is performed
through gstd.
dbsrv9 – This process manages the Generic Services Toolkit (GST) database. This database is
also referred to as the Console server database and contains information concerning
all backup, recover, and cloning operations performed on NetWorker servers
managed by the Console server. This information is used by gstd to generate
reports.
In a UNIX environment, these processes are started automatically during system boot up. On a
Microsoft Windows host, these processes are started via the EMC Legato GST Service which is
configured to start automatically during boot up

NetWorker Features
and
Backup Process Flow

The NetWorker Advantage
y Ease of administration
y Network-based backup protection
y Efficient backups
y A full range of data protection

functions
EMC NetWorker is an award-winning, extremely efficient, highly configurable, distributed

storage management solution that offers the advantages listed in the slide.
These advantages are discussed in more detail on the following pages.

NetWorker Advantages
Ease of administration Network-based backup protection
y GUI (Web-based browser using NMC) y WAN and SAN
y Command-line Interface (CLI) y Open-system protocols (TCP/IP, NDMP)
y Highly configurable y Cross-platform (UNIX, Windows, Linux, etc.)
Client
UNIX NAS/NDMP Host

UNIX
NetWorker
Server
W2k3 SAN
UNIX
NetWorker
Data Zone Client Remote
Storage Node
You can easily administer NetWorker from any host having a supported web browser.
NetWorker also provides many command-line utilities. NetWorker is highly configurable,
allowing you to customize backups to meet specific needs.
NetWorker provides network-based backup protection that functions in WAN and SAN
environments on open system protocols, including TCP/IP and Network Data Management
Protocol (NDMP).
NetWorker uses the client/server model, which distributes the workload and improves
performance. It is supported on the many operating systems listed in the EMC Legato Software
Compatibility Guide. The supported platforms seamlessly co-exist within the data zone. For
example, a Microsoft NetWorker client can back up to a UNIX NetWorker storage node and
vice versa.

NetWorker Advantage – Efficient Backups
NetWorker supports:
y Multiple concurrent backups
y Backups from different operating
systems
y Backups to multiple devices
Save Set 1 Storage
Save Set 2 Node
W2k3
UNIX
Save Set 3
Save Set 4 NetWare

Server Save Set 5
Save Set 6
EMC NetWorker allows you to perform more efficient backups than most native operating
system backup software programs.
Many native solutions limit you to one backup at a time, one operating system, and only local
devices. NetWorker is not bound by these restrictions and is capable of backing up multiple save
sets from clients running different operating systems to any NetWorker-configured device.
Features that support these capabilities include:
y Multiplexing
y Open Tape Format
y Remote device support
These features are discussed on the following pages.

Backups – Without Multiplexing
Data Rate
4 MB/s
Save Sets
4 MB/s
buffer
4 MB/s
4 MB/s
4 MB/s
4 MB/s Storage
4 MB/s
node Device/Volume
Multiple Data Streams
In an environment without multiplexing, only one stream of data is written to the device at any
given time. This situation is not ideal because as more clients perform simultaneous backups,
the tape drive’s throughput is not optimized.

Backups – With Multiplexing
Collective Data Rate
24 MB/s
Save Sets
4 MB/s
buffer
4 MB/s
4 MB/s
4 MB/s
4 MB/s Storage
4 MB/s
node Device/Volume
Multiple Data Streams
Multiplexing enables the device to simultaneously write more than one save set to a volume.
This allows the device to write to the volume at the collective data rate of the save streams, up to
the maximum data rate of the device.
The amount of multiplexing allowed (the number of save sets that can back up simultaneously)
is primarily controlled by two NetWorker settings, server parallelism and device target sessions.
These settings will be discussed in detail in a later chapter.

Open Tape Format (OTF)

1. NetWorker clients send data
in boxes (save set chunks).
UNIX
SS1
W2K
SS2
SS
OTF
1
SS2
3. Pallets are placed

sequentially on shelves
2. The storage node organizes (volumes) until the
the boxes on pallets (records). shelves are filled.
Open Tape Format (OTF) is a data format that allows multiplexed, heterogeneous (UNIX,
Windows, NetWare, etc.) data to reside on the same tape.
As shown in the slide, clients wrap their backup data into packages containing platform-
independent data (save set chunks) before sending them to the storage node. The storage node
receives the packages and arranges them on a pallet (media records and media files). These
pallets are then stored in the warehouse, or tape volume.
The way the storage node organizes the pallets is also platform-independent (Open Tape
Format), allowing any NetWorker storage node to read the data. Because of Open Tape Format,
a NetWorker storage node can be migrated to a host running a different operating system.
Note: For more information on OTF, see the mm_data(5) man page or the white papers
available at software.emc.com.

Remote Device Support
The NetWorker
Server Server stores
tracking information. Storage
Node
CFI
Media
DB
The client generates

the backup.
Another feature of NetWorker that promotes efficient backups is the support of remote devices.
This means that data can be backed up to devices controlled by remote storage nodes. Recall
that a remote storage node is any storage node other than the NetWorker server. The
NetWorker server is the only local storage node. Devices controlled by the NetWorker server
are local devices. Devices controlled by remote storage nodes are remote devices.
This feature allows you to distribute the backup workload throughout the data zone.

Data Protection Functions
Backup
Staging Recovery
(optional)
Cloning Tracking and

(optional) Reporting
Aging
In addition to backup and recovery, NetWorker provides a full range of data protection functions
including tracking and reporting, staging, cloning and recovery.
Backup
A backup is a copy of data you want to protect by storing it in another location. NetWorker
provides a scalable solution to manage backups for a small network or an entire enterprise, and
enables you to automate and configure this process for speed and efficiency.
Recovery
Recovery is the process of restoring data to a given point-in-time. NetWorker makes this process
possible from anywhere within the NetWorker data zone. This feature allows users to retrieve
single files or restore an entire filesystem.

Tracking and Reporting

Tracking is the process of storing and accessing information about the backup. NetWorker saves
and tracks information such as:
y The backup’s location on the volume(s)
y The client that generated the backup
y The backup creation date and time
y The level of backup
The Console Server uses information about backed up data to generate reports.
Aging
Aging determines the length of time that the backup data is available for recovery. NetWorker
allows you to specify:
y How long to keep the tracking information viewable (browsable)
y How long to protect each volume from recycling (overwriting)
Cloning
Cloning is the optional process of copying a save set to another storage volume.
Staging
Staging is the optional process of moving a save set from one storage volume (the physical
medium where the data is stored) to another.

NetWorker Backup Example

NetWorker Server
Media
DB CFI
CFI
nsrmmdbd nsrd CFI
4 1
nsrindexd
3 3
6 2
6
nsrmmd nsrjobd
1 5
nsrexecd
5 2
4
1
5
save
NetWorker Client
The slide shows a high-level process and data flow of a typical NetWorker scheduled backup.
1. The server’s nsrd starts a scheduled backup. nsrd asks nsrjobd to send a remote
execution request to the client’s nsrexecd, requesting that it execute the NetWorker save
command to perform the backup.
2. The save command started on the client communicates with the server’s nsrd (through
nsrjobd) to request backup support.
3. nsrd matches the backup to a storage node’s nsrmmd based on configuration information
and save request attributes.
4. Once the volume has been mounted on the backup device, nsrd directs the client to push its
data to the storage node.
5. The client:
- pushes the data to the storage node’s nsrmmd
- sends tracking information to its client file index (CFI) via the server’s nsrindexd
6. nsrmmd on the storage node:
- writes the data sent by the save command to the volume
- send tracking information to the media database via the server’s nsrmmdbd
7. When the backup is finished, the connections are dropped.

Chapter 1 - Summary
Key topics covered in this chapter include:

y NetWorker hosts and their functions
y NetWorker control data and its use
y The purpose of each NetWorker daemon/service
y EMC NetWorker advantages
y Interprocess communication during a backup
These are the key points covered in this chapter. Please take a moment to review them.

9 Check Your Knowledge – Part 1

1. What are the functions of the three types of NetWorker
hosts?
2. Which NetWorker server daemon starts nsrindexd?
3. List some examples of the information stored in the
resource files.
4. What is the media database?
5. What is the function of a client file index (CFI)?
6. What is the function of nsrexecd?

9 Check Your Knowledge – Part 2

7. What is the name of the storage node daemon? What
does it do?
8. Which NetWorker feature enables the storage node to

write NetWorker data from different operating systems
to one tape?
9. Which NetWorker function enables you to make a copy

of a save set?
10. Which NetWorker function enables you to move a save
set from one volume to another?


Chapter 01 - NetWorker Overview

Uploaded by

Copyright:

Available Formats

Chapter 01 - NetWorker Overview

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter 01 - NetWorker Overview

Uploaded by

Copyright:

Available Formats

Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved.

Chapter 1 - EMC NetWorker Overview

Upon completion of this chapter, you will be able to:

y Explain NetWorker control data and its use

y Explain the purpose of each NetWorker daemon/service

y Explain EMC NetWorker advantages

y Describe interprocess communication during a backup

© 2006 EMC Corporation. All rights reserved. EMC NetWorker Overview - 1

EMC NetWorker Overview, Page 1-1

© 2006 EMC Corporation. All rights reserved. EMC NetWorker Overview - 2

EMC NetWorker Overview, Page 1-2

The NetWorker Solution

© 2006 EMC Corporation. All rights reserved. EMC NetWorker Overview - 3

EMC NetWorker Overview, Page 1-3

NetWorker Data Zone

© 2006 EMC Corporation. All rights reserved. EMC NetWorker Overview - 4

There are three types of NetWorker hosts.

EMC NetWorker Overview, Page 1-4

y Generates backups Save Set

© 2006 EMC Corporation. All rights reserved. EMC NetWorker Overview - 5

Note: Every host in a NetWorker data zone is a NetWorker client.

EMC NetWorker Overview, Page 1-5

NetWorker Storage Node

y Organizes the backup data

Note: See nsr_storage_node(5) in the EMC NetWorker Command Reference Guide

EMC NetWorker Overview, Page 1-6

y Supports client backup and recovery

© 2006 EMC Corporation. All rights reserved. EMC NetWorker Overview - 7

Note: See the nsr_service(5) man page for more information.

EMC NetWorker Overview, Page 1-7

NetWorker Control Data

For a Microsoft Windows NetWorker Server, replace /nsr

© 2006 EMC Corporation. All rights reserved. EMC NetWorker Overview - 8

Note: See the nsr_layout(5) man page for more information.

EMC NetWorker Overview, Page 1-8

Control Data - Resource Files

nsrdb jobsdb nsrladb

Sample contents of a resource file in /nsr/res/nsrdb/*/*

NetWorker stores and maintains configuration information as resources. Resource information is

EMC NetWorker Overview, Page 1-9

Control Data - Media Database

volume client date time size ssid fl lvl name

© 2006 EMC Corporation. All rights reserved. EMC NetWorker Overview - 10

EMC NetWorker Overview, Page 1-10

Control Data - Client File Indexes

C:\WINNT\Fonts\8514fix.fon, date=1128238402 Sun Oct 02 03:33:22 2005

© 2006 EMC Corporation. All rights reserved. EMC NetWorker Overview - 11

EMC NetWorker Overview, Page 1-11

NetWorker Management Console (NMC) Server

Server Configuration Configuration Server

Client Client Client Client Client

y Provides a Java interface for configuration and management of

© 2006 EMC Corporation. All rights reserved. EMC NetWorker Overview - 12

EMC NetWorker Overview, Page 1-12

Core NetWorker Daemons

© 2006 EMC Corporation. All rights reserved. EMC NetWorker Overview - 13

EMC NetWorker Overview, Page 1-13

NetWorker Client Daemon: nsrexecd

y Listens for, authenticates, and supports remote

Sample contents of a resource file in /nsr/res/nsrdb//