This module begins with a review of NetWorker data protection functions, components and terms that were

first covered in the prerequisite eLearning course, NetWorker Fundamentals. Then, we take a detailed look
at the role of each NetWorker process in a backup operation and the content and use of NetWorker control
data.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 1

 To gain the most benefit from this course, certain prerequisite knowledge is required. The prerequisite
eLearning, NetWorker Fundamentals, provides an effective overview of NetWorker provided data protection
functions, architecture, and terminologies.

This lesson provides a brief review of these prerequisites along with cross-references to the prerequisite
course to help you obtain this knowledge.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 2

 EMC NetWorker works within the existing framework of hardware, operating system software, and network
communication protocols to provide a comprehensive and consolidated data protection solution.

NetWorker protects critical business data by centralizing, automating, and accelerating backup and recovery
operations across an enterprise. NetWorker provides backup and recovery support for diverse computing
and storage environments including business applications and virtual environments. Performance
enhancements, such as block based backups, improve backup performance and reduce the impact of
backups on production environments. User authentication, authorization and encryption support ensure
information security. Backup storage options include the leading deduplication technologies, disk backup and
snapshot technologies, as well as integration with the latest databases and applications.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 3

 In addition to backup and recovery, NetWorker provides a full range of data protection functions including
tracking and reporting, aging, cloning, and staging. The NetWorker Fundamentals prerequisite eLearning
introduces these functions and looks at how NetWorker supports these functions.

• A backup is a copy of production data, created and retained for the sole purpose of recovering deleted or
corrupted data.

• Recovery is the process of restoring data to a given point in time.

• Tracking is the process of storing information or metadata about backup save sets. The Management
Console server uses this information to generate reports.

• Aging determines the length of time that backup data is available for recovery. NetWorker allows you to
specify how long individual copies of data are maintained.

• Cloning is the process of copying a save set from one NetWorker backup volume to another. The clone
can then be managed independently with its own retention time.

• Staging is the process of moving a save set from one volume to another.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 4

 To implement a backup and recovery strategy, it is important to understand the roles and functions of the
various components in a NetWorker datazone. A detailed description of each component is discussed in the
NetWorker Fundamentals eLearning course and is summarized here:

• The NetWorker server is a physical or virtual machine that manages the datazone and facilitates client
backups and recoveries. The NetWorker server maintains tracking and configuration information.

• NetWorker storage nodes are dedicated hosts with direct-attached or SAN/LAN-accessible devices to
support the storage of backup data. Storage nodes write data to and read data from backup devices. The
NetWorker server is also a NetWorker storage node.

• The Management Console Server provides a global view of the NetWorker backup environment for
centralized management of one or more NetWorker datazones.

• The Management Console client is a Java-based graphical user interface accessible from any supported
web browser.

• NetWorker supports many types of devices that can be used to store backup data. Device types include
virtual and physical tape, disk, and cloud storage devices. Backup to deduplication storage is supported
with Data Domain. Configuring and managing backup devices is covered in detail later in this course.

• Finally, the most fundamental NetWorker component is the NetWorker client. NetWorker client software
provides the functionality for generating backups, pushing the data to a NetWorker storage node or
directly to a backup device, and retrieving data for a recovery. Client software is installed on all
NetWorker hosts.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 5

 To understand the backup process, you need to understand the backup terminology associated with the
NetWorker product. Listed here are some common NetWorker terms that were introduced in NetWorker
Fundamentals.

• A save set is one or more files, directories, and/or file systems, or application-generated data, residing on
a NetWorker client, that is backed up as a unit to a NetWorker storage node and written to backup
storage. A save stream is a single save set in the process of being backed up or recovered. The save
program is used to back up a save set.

• A volume is a unit of media, such as a tape cartridge or file system directory, to which backup data is
written.

• A pool is defined as a collection of NetWorker labelled volumes. Pools are used in NetWorker to assign
specific backup data to specific volumes.

• A protection group defines a set of data sources to protect, such as clients or save sets.

• A workflow defines an action or set of actions to be performed on an assigned protection group.

Workflows specify when and how often to run. An action defines a data protection operation like backup,
clone or snapshot. Within an action, you specify the backup level(s) and pool to be used when the action
runs.

• Protection policies provide an organizational container for the workflows, actions and groups.

As we progress through this course, we will cover these terms in more detail and build upon these
definitions.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 6

 This lesson covers the NetWorker processes associated with NetWorker client, storage node, server and
NetWorker Management Console. The lesson concludes with a high-level process and data flow of a typical
NetWorker scheduled backup.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 7

 NetWorker processes (or daemons) are involved in almost all NetWorker operations, including backups and
recoveries. There are one or more NetWorker processes to support each of the three NetWorker host
functions:

• Client

• Storage node

• Server

In a Microsoft Windows environment, the core NetWorker processes are started via two NetWorker services.

The following pages provide summary information about the main NetWorker daemons. For more detailed
information, please see the EMC NetWorker Command Reference Guide or the man pages.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 8

 The NetWorker client process, 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.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 9

 The NetWorker storage node management daemon, nsrsnmd (network save and recover storage node
management daemon), provides an RPC-based service that manages all device operations and the nsrmmd
processes on the storage node on behalf of the nsrd process on the NetWorker server. The nsrsnmd
daemon is responsible for ensuring that the device operations get performed when needed by nsrd. There
is one nsrsnmd process running on each configured storage node.

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. The nsrmmd daemon
writes the backup data sent by save to a volume in the backup device it is controlling, sends information to
the NetWorker server to track data written to the volume, and reads data from the volume during operations
such as recoveries and cloning. One nsrmmd is started for each device configured as a NetWorker resource.

Note: For disk-type devices there may be more than one nsrmmd per device.

For each enabled library (jukebox) in a datazone, nsrmmgd on the NetWorker server spawns a nsrlcpd
(network save and recover library control daemon) to control the actual jukebox resources, such as media,
slots, drives, and access ports. After performing a task, nsrlcpd returns status information to nsrmmgd,
which in turn provides it to nsrd.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 10

 The NetWorker server processes provide access to NetWorker services such as configuration information,
support for backup and recovery requests, and access to the media database, client file indexes, and jobs
database. NetWorker server daemons include:

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. Once started, nsrd starts the other
server daemons and the nsrsnmd process on the storage node.

nsrmmdbd - (network save and recover media management database daemon) provides the read and write
service for the media database.

nsrindexd - (network save and recover index daemon) provides the read and write service for the client file
index databases.

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.

nsrmmgd – (network save and recover media management daemon) manages all library operations. It is
started on the NetWorker server by nsrd when the NetWorker services are started or when the first jukebox
resource is configured and enabled.

In a Windows environment, these processes are started via the NetWorker Backup and Recover Server
service.

Note: For more detailed information, refer to the NetWorker Command Reference Guide.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 11

 The three NetWorker Management Console server processes are:

• httpd – Apache httpd is the embedded web server.

• gstd – (general services toolkit daemon) is the master Console process and is responsible for starting the
gsttclsh and postgres processes. After a Console client has established communication with the
Console server, all further communication is performed through gstd.

• postgres – This process manages the PostgreSQL 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 Linux environment, the processes are started automatically during system boot up. On a Microsoft
Windows host, the processes are started via the EMC GST Service which is configured to start automatically
during boot up; httpd is registered as the EMC GST Web Service.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 12

 This slide shows a high-level inter-process communication and data flow of a typical NetWorker scheduled
backup to a Data Domain device.

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 requests nsrsnmd for backup support, nsrsnmd 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
• Sends tracking information to the media database via the server’s nsrmmdbd

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 13

 Resources are used to configure a NetWorker environment. Resources are managed as configurable objects
by the NetWorker administrator. Resource types include policies, clients, devices, tape libraries, and
numerous other configurable components of the backup environment. Anything configurable to NetWorker is
configured as a resource.

A resource is defined by its attributes and the values of those attributes. There can be multiple configurations
or instances for each resource type.

For example, in the slide above, the client resource for bongo has a Save set attribute configured to back up
the /oracle directory. This client is a member of the Payroll group and the Payroll group is assigned to the
File system backups workflow which is configured to start backups at 9:00 P.M.

Nearly all of the resources are stored on the NetWorker server and managed by the nsrd daemon. A small
number of resources are managed on the NetWorker client.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 14

 This lesson covers the directory structure and content of the CFI, media and jobs databases.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 15

 The NetWorker server maintains tracking information for save sets in both the client file indexes (CFIs) and
in the media database. Volume information is maintained only in the media database.

A client file index (CFI) stores information about each file backed up by a NetWorker client. There is one CFI
per physical NetWorker client. The stored information includes file characteristics such as owner, size,
permissions, and modification and access times, as well as the timestamp of when the file was backed up.
All files in a given save set have the exact same backup timestamp. This information is used to support
browsable recoveries, which allow you to easily recover a client to a specific point in time.

As a save set ages, its CFI records are automatically purged to save space. The length of time that the
records are retained is determined by the Browse policy attribute in the client resource. CFIs may require
large amounts of space on the NetWorker server. Each record in a CFI uses approximately 160 bytes. The
default path of a CFI is /nsr/index/hostname_of_client/db6.

The media database contains information about all NetWorker volumes and the save sets on those volumes.
For each volume there is a volume record. For each save set on a volume, there is a save set record. This
information is critical for supporting recoveries and is also used during incremental backups to determine the
timestamp of a previous backup. The location of the media database is /nsr/mm/mmvolrel.

Important: Beginning with NetWorker 9, you specify only a retention period when backing up a save set.
NetWorker uses this value for both the Browse time and the Retention time for the save set.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 16

 A CFI directory contains a header and journal file as well as a series of directories whose names are
hexadecimal time stamps. Each save set tracked in a CFI has a record and a key file which are stored in a
subdirectory determined by the time stamp of the save set (nsavetime value). The record and key files are
named nsavetime.rec, nsavetime.k0 and nsavetime.k1.

The data in the CFI files is XDR encoded for NetWorker use. Therefore, only NetWorker GUI/CLI interfaces
should be used to view and manage the CFI data.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 17

 Each record in a CFI contains the path name of a backed up file or directory, and the timestamp associated
with the save set that it is part of. The timestamp matches the timestamp of a save set record in the media
database, and is used in determining which save set and volume is needed when recovering the file. File
attribute and backup information are also stored in the CFI.

nsrinfo displays the timestamp in two formats. The nsavetime format is the number of seconds since January
1, 1970. This is the time format used internally by NetWorker. The save time format is a more human-
readable form of the date and time.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 18

 The media database directory structure includes a header file and files to store client records, save set
records and volume records. Each client record, save set record, and volume record file has a set of
supporting index files.

All the files under /nsr/mm make up the media database.

To maintain its integrity only use NetWorker GUI or CLI interfaces to view and manage the data contained in
the media database.

Note: The media database is a SQLite database. Operational requests are handled in parallel and a targeted
cache facility is employed, thus optimizing performance.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 19

 The media database contains a record for each NetWorker volume and for each save set written to a
volume.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 20

 The jobs database in NetWorker is responsible for managing and monitoring all jobs within the environment.
These jobs include server activities such as cloning, staging, and recovery operations as well as client
activities, like save or save groups. When the jobs are started, the jobs database collects all the runtime
information as well as completion information.

The jobs database consists of an embedded SQLite database server which is a full database engine that can
handle high loads without performance concerns. The database itself is stored in a single file on the
NetWorker server and is managed via time-based purging. The default expiration period is 72 hours. The
database should not exceed 1 GB in size. The jobs database is re-created empty during NetWorker server
disaster recovery procedures.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 21

 This module covered a refresh of NetWorker data protection functions, components and terms that were first
covered in the prerequisite eLearning course, NetWorker Fundamentals. Then, we took a detailed look at the
role of each NetWorker process in a backup operation and the content and use of NetWorker control data,
including the CFI, media and jobs databases.

Copyright © 2017 Dell Inc.. Module: NetWorker Basics 22