Networker Overview

EMC's Networker is their flagship backup application.  It is software that integrates with a large number of backup storage systems and clients, and has plug-ins for a large number of applications.

A Data Zone is comprised of a Networker Server (which contains a server node and a backup client), one or more storage nodes which can be on the Server node or separated.  The storage node writes data to media nad reads from media during restore.  The clients then generate backup data and tracking information regarding what data is located where.

Control Data is sent along with backup data.  It is kept in the following locations:

• /nsr/index/CFI - client file index telling what data is in what save set
• /nsr/mm/Media Database - tracks volumes and save sets
• /nsr/res/ - resource files
• On Windows hosts these are located in <drive>:\Program Files\Legato\nsr

Resource files include the nsrdb, which is a bunch of text files (not an actual database) of clients, devices, etc.  nsrladb is the drictory that holds resource info for RPC ports available for use, and jobsdb holds statistics and information on backup jobs.

The Media Database lists all media available to the Networker server and clients, as well as info on all save sets.

The Client File Index is where clients send tracking info regarding which data is stored on which node and which save set.

The NMC, or Networker Management Console is a java application that can configure and manage multiple Networker Servers and Data Zones.  It requires Networker 7.3 or newer.

Core Networker Daemons:

NW Client:

• nsrexecd listens for backup requests, authorizes and determines which RPC ports to use
•  nsrfsra is the utility for browsing the client filesystem

Storage Node:

• nsrsnmd - listens for RPC commands and spawns processes
• nsrmmd - PRIMARY PROCESS which receives data from teh client and writes to storage, also send tracking data to server.  Can run multiple processes at one time for multiple backup jobs
• nsrlcpd - resources to control libraries

Server Node:

• nsrd - PRIMARY PROCESS, starts schedule, starts jobs, manages resource database
• nsrindexd - client talks to this process to write data
• nsrmmdbd - talks to the database
• nsrjobd - coordinates scheduled jobs, manages the resulting info
• nsrmmgd - handles library operations

Console Server:

• httpd - web server
• gstd - PRIMARY PROCESS, runs the GUI and talks to the server process
• dbsrv12 - manages the database and gathers data

BACKUP PROCESS FLOW:

1. nsrd on the Networker server starts backup on the client
1. nsrd->nsrjobd->nsrexecd->save
2. save command on client figures out where to put data
1. save->nsrjobd->nsrd
3. Storage node is matched to a job and storage media is mounted
1. nsrd->nsrmmd->nsrd
4. Server tells the client where to send data
1. nsrd->nsrjobd->nsrexecd->save
5. Client sends data and tracking info simultaneously
1. save->nsrindexd and save->nsrmmd
6. Storage node sends tracking info the its media database
1. nsrmmd->nsrmmdbd