Emc Legato Networker Foundations

Copyright © 2005 EMC Corporation. Do not Copy - All Rights Reserved.
EMC Legato NetWorker Foundations
© 2005 EMC Corporation. All rights reserved.
Welcome to EMC Legato NetWorker Foundations training.

The AUDIO portion of this course is supplemental to the material and is not a replacement for the
student notes accompanying this course. EMC recommends downloading the Student Resource Guide
from the Supporting Materials tab, and reading the notes in their entirety.
Copyright © 2005 EMC Corporation. All rights reserved. These materials may not be copied without EMC's written
consent. Use, copying, and distribution of any EMC software described in this publication requires an applicable software
license.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS”. EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE.
Celerra, CLARalert, CLARiiON, Connectrix, Dantz, Documentum, EMC, EMC2, HighRoad, Legato, Navisphere,
PowerPath, ResourcePak, SnapView/IP, SRDF, Symmetrix, TimeFinder, VisualSAN, “where information lives” are
registered trademarks.
Access Logix, AutoAdvice, Automated Resource Manager, AutoSwap, AVALONidm, C-Clip, Celerra Replicator, Centera,
CentraStar, CLARevent, CopyCross, CopyPoint, DatabaseXtender, Direct Matrix, Direct Matrix Architecture, EDM, E-
Lab, EMC Automated Networked Storage, EMC ControlCenter, EMC Developers Program, EMC OnCourse, EMC Proven,
EMC Snap, Enginuity, FarPoint, FLARE, GeoSpan, InfoMover, MirrorView, NetWin, OnAlert, OpenScale, Powerlink,
PowerVolume, RepliCare, SafeLine, SAN Architect, SAN Copy, SAN Manager, SDMS, SnapSure, SnapView,
StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix DMX, Universal Data Tone, VisualSRM are
trademarks of EMC Corporation. All other trademarks used herein are the property of their respective owners.
Legato NetWorker Foundations 1

EMC Legato NetWorker
Upon completion of this course, you will be able to:

y Understand the EMC Legato NetWorker solution
y Explain NetWorker advantages
y Explain NetWorker hosts and their roles
y Explain NetWorker control data and its use
y Explain NetWorker resources and their purpose
y Explain the NetWorker data-tracking process
y List NetWorker-supported device types and devices
y Understand the NetWorker backup process, types, and
levels
y Understand the NetWorker recovery process and types
© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 2
The objectives of this course are listed here. Please take a moment to review them.

OVERVIEW
Let’s begin with a brief overview of NetWorker.

The NetWorker Solution
App
App Oracle
SQL
SQL App
Legato
IT App
App NetWorker
Solution
TCP/IP O.S.
TCP/IP O.S.
Hardware
Hardware
There are many pieces in an overall solution for your business computing needs. EMC Legato
NetWorker works within the existing framework of hardware, operating system software, and network
communication protocols to provide protection for the critical application data that the framework
supports.

NetWorker Hosts
The NetWorker
Server Storage
Server supports
Node
the backup and The NetWorker
Storage
stores tracking Storage Node
Node Client
and configuration reads and
information writes data to
Client
the device
The NetWorker
Client
Client generates
the backup data
NetWorker Data Zone

The three types of NetWorker hosts are:

y NetWorker Clients
y NetWorker Storage Nodes
y NetWorker Server
The NetWorker Server supports the backup and stores tracking and configuration information.
The NetWorker Storage Node reads and writes data to the device.
And the NetWorker Client generates the backup data.
Together, a single NetWorker Server, with its Storage Nodes and Clients, forms a NetWorker data
zone within which data is protected.

NetWorker Client
Server
Storage Storage
Node Node
Client Client
z Generates backups
Save Set
z Generates tracking information Client
z Performs recoveries
z Provides user and administrative
interfaces
The NetWorker Client is the largest NetWorker software component and the fundamental host.
The client’s most important functions are to generate backups called save sets, push them to the
storage node, and retrieve them during a recovery. NetWorker Clients are usually the data servers in an
IT solution. The types of data that can be backed up as save sets are filesystem data or applications.
While performing a backup, the client also generates tracking information, including the file and
directory names in the backup and the time of the backup, and sends it to the server to facilitate point-
in-time recoveries.
In addition, the client provides the user backup, recover, and administrative interfaces that allow you to
configure and monitor NetWorker for your specific environment. NetWorker Client software is
installed on all participating hosts in the data zone, including hosts that also play the roles of server and
storage node.
Every host in a NetWorker data zone is a NetWorker Client.

NetWorker Storage Node
Server
Storage Storage
Node Node
Client Client
z Organizes the data

z Writes data to the device Client
z Generates tracking information
z Reads data from the device
NetWorker Storage Nodes are data zone hosts with directly-attached or SAN-accessible devices that
provide the NetWorker interface for the devices and volumes. If devices are not accessed through the
NetWorker Server, they are considered remote devices, and the host through which the devices are
accessed is a remote storage node.
The NetWorker Server is always a storage node in any data zone and is the default storage node for
backups. Using remote storage nodes is optional, although they distribute the backup workload and
reduce network traffic. Storage node hosts in the data zone have both the NetWorker Client and
storage node software installed.
In a backup, NetWorker Clients send backup data to a particular storage node based on that client’s
configuration. The storage node organizes the client’s data.
Then the storage node writes the client’s data to one of its devices.
Storage nodes also send tracking information about the volume and any data written to it to the
NetWorker Server to store it as online tracking information about the volume and its contents.
In a recovery, the client reads from the storage node. The storage node provides the device that
contains the necessary volume.

NetWorker Server
CFI
CFI
Server CFI
Storage Storage
Node Media Node
Database
Client Client
Resource
Directory
z Supports client backups/recoveries

z Stores tracking and configuration Client
information
z Backs up tracking and configuration
information
The NetWorker Server is the data zone host that stores the configuration information, such as
supported clients, devices, when to run the backups, and so on.
The NetWorker Server also stores the online NetWorker databases that track the backups and volumes.
The NetWorker Server, as a client of itself, automatically backs up the configuration 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. The NetWorker Server has NetWorker Client, Storage Node, and
Server software installed.

NetWorker Advantages
Ease of administration Network-based backup protection
z GUI (X/Motif and Microsoft z WAN and SAN
Windows)
z Open-system Protocols
z Command Line Interface (CLI) (TCP/IP, NDMP)
z Highly Configurable
z Cross-platform (UNIX, W2K, etc.)
Client
UNIX NAS/NDMP Host

NetWorker
UNIX
Server
W2K3 SAN
UNIX
Client Remote
NetWorker
Data Zone Storage Node
EMC Legato NetWorker is an award-winning, extremely efficient, highly configurable, distributed

storage management solution that offers ease of administration, network-based backup protection,
efficient backups, and a full range of data protection functions
You can easily administer NetWorker software on any NetWorker host on any supported platform
within the network. For example, you can administer a Microsoft® Windows® NetWorker Server
from a UNIX machine.
NetWorker provides both X/Motif and Microsoft® GUIs and a rich command line interface, or CLI.
NetWorker is also highly configurable, which allows you to tailor 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, or NDMP.
NetWorker uses the client/server model, which distributes the workload and improves performance. It
is supported on several platforms. The supported platforms seamlessly co-exist, cross platform, within
the data zone. For example, a Microsoft NetWorker Client can backup to a UNIX NetWorker Storage
Node.

Efficient Backups
NetWorker supports:
y Multiple concurrent backups
y Data created on different operating systems
y Backups to multiple devices
Save Set 1
Save Set 2
W2K3
UNIX
Save Set 3
Save Set 4 NetWare

Save Set 5
Save Set 6
EMC Legato 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 local devices only.
NetWorker is not bound by these restrictions and is capable of backing up multiple save sets from
different platforms to any NetWorker-configured device.

NetWorker Uses Multiplexing
Collective Data Rate 3 MB/s
1 MB/s
1 MB/s
1 MB/sSave
1 MB/sSet
1 MB/s 1
1 MB/s
1 MB/s
1 MB/s1Save
1 MB/s
MB/s Set
1 MB/s 2
1 MB/s
1 MB/s
1 MB/s 1Save
1 MB/s
1 MB/s
MB/s
1 MB/sSet
1 MB/s 3 Device Volume
Multiple Data Streams
Multiplexing enables the device to simultaneously write more than one save set to a storage volume.
This allows the device to write to the volume at the collective data rate of the savestreams, up to the
maximum data rate of the device.

Without Multiplexing
1 MB/s 1 MB/s
Save Set 1
Save Set 2
Save Set 3
Device Volume
Single Data Stream
In an environment without multiplexing, only one stream of data is written to the device or volume at a
time. This situation is not ideal because as more clients perform simultaneous backups, the tape drive’s
throughput is not optimized.

Open Tape Format

The NetWorker client packs the
data into boxes (save set chunks)
UNIX
SS1
NT
SS2
SS
OTF
1
SS2
The pallets are stored in the

warehouse (tape volume)
The Storage Node organizes the
boxes on a pallet (media records)
Open Tape Format, or OTF, is the structure that allows multiplexed, heterogeneous (UNIX, Windows,
NetWare, etc.) data to reside on the same tape.
As shown in the diagram:
Clients wrap their backup data into platform-independent data format, like boxes, which are called
save set chunks, before sending it to the storage node. The storage node receives the information and
arranges it on a pallet, or media records and files.
These pallets are then stored in the warehouse, or tape volume. The way the storage node organizes the
pallets is also platform independent because of Open Tape Format which allows any other NetWorker
Storage Node to read the data. This feature supports NetWorker migration to other platforms.

NetWorker in a SAN
Symmetrix
FC Switch
Fibre Channel
W2K3 UNIX NetWare
NetWorker Storage Client Client Client

Server Node
EMC Legato NetWorker can be used in a SAN to back up data to disk or library devices on the SAN.
The configuration shown in the diagram is called LAN-free backup because no backup data travels
over the LAN.

NetWorker and NDMP

NetWorker Server
NDMP Command
bongo Tracking Data
Backup Data
NAS Device
NDMP, Network Data Management Protocol, 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.
NDMP is able to communicate with several different interface types for data transfer during backup
and recovery. NDMP enables disparate vendors to use a common protocol for the backup architecture.
Data is copied from disk to tape using NDMP, regardless of the operating system or platform. Tracking
information is also passed to and from backup software using the same protocol, regardless of software
type.
NDMP works with NetWorker for backups, cloning, recoveries, and updates or queries to resource
files. Any communication to and from the NetWorker Server to any NDMP device including servers,
disk, and storage is done via NDMP.
By using NDMP with NetWorker, the NDMP-enabled NAS device sends data to the NDMP-enabled
tape device where NetWorker keeps track of the backed up files. The NDMP-controlled tape device
attaches directly to the NAS device or another location on the network.
With NetWorker 7.2 and later, NDMP hosts have the option to send their data to a storage node.

NetWorker Software Editions
Max Remote Max Immediate

NetWorker Max Add-on Max
Jukeboxes Storage Parallel Save
Edition Clients Modules Devices
/Slots Node -ism Recover
Workgroup 1/32
8 No Limited 12 4 No
/Business 1-26
10 - Unlimited/
Network Yes Yes 32-512 16-512 Yes
unlimited unlimited
10 - Unlimited/
Power Yes Yes 64-512 32-512 Yes
unlimited unlimited
Four NetWorker software editions are offered to meet your data protection needs as shown in the table:
y Workgroup Edition
y Business Edition
y Network Edition
y Power Edition
The table shows the different combinations of client connections, add-on modules, and architectural
and performance improvements that are available with each edition.

NetWorker Add-on Modules

Add-on Module Description License
Required?
Client Connections A connected client is a computer Yes
that is configured on the NetWorker
Server and has contact with the
server to attempt a backup
ClientPaks Required for any NetWorker client Yes

that has a different operating
system from the NetWorker Server
Storage Node Allow the NetWorker Server to use Yes

remote devices
NetWorker Modules Allows online application and Yes
database backups
As shown in the table, several add-on modules that provide additional features and benefits are
available. Add-on modules work in conjunction with your base edition of EMC Legato NetWorker.
Client Connections licenses are required for any computer that is configured on the NetWorker Server
and has contact with the server to attempt a backup.
ClientPak licenses are required for any NetWorker client that has a different operating system from the
NetWorker Server.
Storage Node licenses allow the NetWorker Server to use remote devices.
NetWorker Module licenses allow online applications and databases to be backed up. Some add-on
modules require a license and additional software.

ARCHITECTURE
Next, we will review the NetWorker architecture.

Data Protection Functions
Backup
Recovery Tracking
Aging Staging
(optional)
Cloning
(optional)
EMC Legato NetWorker performs the data protection functions listed in the diagram. Following is a
description of each function.
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.
Tracking is the process of storing and accessing information about the backup. NetWorker saves and
tracks information such as the location and volumes of the backup, the client that generated the
backup, the backup creation date and time, and the backup type.
Staging is the optional process of moving the backup data from one storage volume, the physical
medium where the data is stored, to another.
Cloning is the optional process of making a copy of the backup save set or volume.
Aging determines the length of time that the backup data is available for recovery. NetWorker allows
you to specify how long to keep the tracking information viewable and how long to protect each
volume from recycling.
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 enables users to retrieve single
files or restore an entire filesystem.
These data protection functions are presented in more detail throughout the course.

NetWorker Control Data
<nsr>/index/
Server CFI
CFI
CFI
Storage
Node
Media
Client Database
Resource Directory <nsr>/mm/

<nsr>/res/
NetWorker control data collectively represents the NetWorker configuration information and the
backup tracking information stored on the NetWorker Server.
The Resource Directory is the directory that contains the configuration resource files. The resource
directory is also called the resource database.
The Media Database is the NetWorker database used to track the backups and the volumes that store
the backups.
Client File Indexes, or CFIs, are the NetWorker databases that track each file or pathname in a client’s
backup, allowing clients to browse their backups for files from a particular point in time. The
NetWorker Server creates and maintains one client file index per client.

NetWorker Resources
Client:bongo
Save: /oracle
Group:XXX Device:rmt3
Client:HostB… Type: DLT
Device: rmt0
Save: C:\ Client:HostA Disabled
Type: LTO
Device: rmt1
E:\ Save: /usr …
enabled
Type: LTO
Group:xgrp /opt enabled
… Group:Default …
…
Jukebox:
Jukebox:ajuke
ajuke
Group:xgrp devices:
devices:rmt0,1
rmt0,1
Start: 11pm Inventory
Inventory
Group:XXX Slot0:
… Slot0:AFR123
AFR123
Start: 4am ……
…
Group:Default
Start: 3:33am
…
Policy: Policy:
Acct Legal
Policy: Eng 7years
3 years
6 months
NetWorker
Server
NetWorker manages its configuration via resources which are stored as configurable objects to the
NetWorker administrator. Examples of resources include clients, devices, tape libraries, backup start
times and so on. Nearly all of the resources are stored on and managed by the NetWorker Server, in the
resource database. A few resources are managed on NetWorker Clients.
NetWorker uses resources to manage its configuration. Resources are managed as configurable objects
to the administrator. NetWorker supports a resource type for each configurable component and there
can be multiple configurations for each type.

NetWorker Tracking Databases
NetWorker Server
/nsr
/index /mm
/hostname /hostname /mmvolume6
/db6 /db6
CFI CFI Media

Database
/nsr/index/hostname/db6 /nsr/mm/mmvolume6
The NetWorker Server maintains tracking information for save sets and volumes in a client file index
for each client and in the media database.
The CFI stores the records for each backed up file for each NetWorker Client. There is one CFI per
client host. The information answers the question “what files were backed up and when?” for each
client. This information is used to support browsable recoveries which allow clients to more easily
recover to a point in time. As the save sets age, the CFI records are deleted automatically to save
space. The amount of time the records are kept is configurable through the browse policy.
The Media Database tracks the NetWorker labeled volumes and the save sets on the volumes. The
information answers the question, “on which volumes are the save sets located?” All volumes and save
sets are listed in the Media Database and the records are critical to support recoveries.

Save Set and Volume Aging
CFI
DATA
Media Database
NetWorker Server
recoverable
browsable
recyclable
Tape is recycled
appendable
Recyclable
(relabeled) bongo.001
Save sets and volume records in the media database are checked for aging based on its browse and
retention policies. The browse policy determines how long file entries remain in the CFI. The retention
policy determine how long data, or save sets and volumes, is protected from automatic recycling.
The media database is checked, and the browse and retention policies are enforced.
Status changes are made to the CFI when a save set changes from browsable to recoverable to
recyclable to appendable.

NetWorker Administrative Interfaces

UNIX Microsoft
Windows
Administer nwadmin (NetWorker NetWorker
NetWorker Server Administrator) Administrator
nsradmin (character- nsradmin (character-
based) based)
Backup NetWorker User nwbackup
Recover NetWorker User nwrecover
All NetWorker tasks can also be performed from the command line
NetWorker provides administrative interfaces, including GUI and command line interfaces to manage,
configure, and monitor the NetWorker Server.
The interfaces for administering the NetWorker Server are nwadmin on UNIX and NetWorker
Administrator on Windows. nsradmin is a character-based interface and command line interface for
configuring NetWorker.
Each interface is provided with the NetWorker Client software. Each interface can run from the
NetWorker Client to administer and monitor the NetWorker Server.
These interfaces are discussed in more detail later in this course.

nwadmin Administrative GUI Interface: UNIX

Configure/
Administer
Menus Configuration
Speedbar
Monitoring
On UNIX, the NetWorker Administrator program, or nwadmin, is a graphical user interface for
XWindows environments. From this interface, you can manage, configure, and monitor the NetWorker
Server.
The three components in the main nwadmin window are Menus, a Speedbar, and Monitoring panels.

NetWorker Administrator GUI: Windows

Menu Bar
Toolbar
Network Server
Monitoring
As with nwadmin on UNIX, the NetWorker Administrator GUI on Windows provides administrative
and monitoring interfaces. nwadmin and NetWorker Administrator provide the same functionality
although they have somewhat different appearances and workflows.

NetWorker Pools
y Match save sets to volumes
y Logically group data onto specific media
y Make it easier to locate data by grouping savestreams
onto specific media
save set 1
save set 3 bongo.003

Pool 1 bongo.002
save set 11
bongo.001
save set 7
Volumes
Pool
A pool is a NetWorker resource that represents a collection of NetWorker-labeled volumes. Pools

enable the NetWorker Server to match save sets to volumes based on the save set attributes. Each
volume is associated with a pool when the volume is labeled.
In the diagram, save sets 1, 3, 11, and 7 are matched to Pool 1 based on their save set attributes. The
volumes in Pool 1 are labeled bongo.001, bongo.002, and bongo.003.

NetWorker Devices and Supported Device Types
Tape
Optical
File
Standalone Device Autochanger
There are two types of NetWorker devices.

A stand-alone device is any type of device that does not have a robotic arm for loading tapes. Media
are manually loaded or preloaded before a backup runs. NetWorker does not have to load the media as
part of the backup procedure.
An autochanger, sometimes called a library, silo, medium changer, TLU, or jukebox, is a multiple-
volume device that uses a robotic arm. Several systems in the network can share autochangers if the
autochanger has more than one drive.
In the NetWorker environment, three types of devices can be used to back up data – tape, optical, or
file.
Tape devices have several associated media types such as 8mm, AIT, DLT, and LTO.
Magneto-optical device are also supported.
A file-type device is an existing filesystem directory configured in NetWorker as a device as type file
or advanced file. Once configured, NetWorker uses the directory as a backup volume to read or write
save set data. Storing data to a file device often reduces the time it takes to both save and recover data.
For a current list of NetWorker devices, refer to the Legato Hardware Compatibility Guide at
www.legato.com.

Local and Remote Devices

3 2 The Storage
The NetWorker
Server stores Node writes
tracking information the data to the
remote device
CFI
Media
DB
1 The client generates

the backup.
The NetWorker Server manages the flow of save sets sent to a device. To accomplish this, the server
needs to know whether the device is attached to the NetWorker Server or to a Remote Storage Node.
A local device is one that is physically attached to the NetWorker Server.
A remote device is any device that is attached to a NetWorker Storage Node.
Another advantage of NetWorker that promotes efficient backups is the ability to support remote
devices. This feature allows you to distribute the backup workload within the data zone.
1. The NetWorker Client generates the backup.
2. The storage node writes data to the remote device.
3. The NetWorker Server stores tracking information.

Shared Autochanger
NetWorker Server Storage Node
Cable to Robotic Arm
Cable to Drive #2
Cable to Drive #1
Cable to Drive #3
Cable to Drive #4
A NetWorker Server can

have many Storage
Nodes, but a Storage
Node can have only one
NetWorker Server in a
data zone
Storage Node
A shared autochanger is one in which multiple NetWorker Storage Nodes have access to individual
drives and the robot in an autochanger. Autochanger sharing allows one host to control the robotic arm,
while other hosts, and the host controlling the robotic arm, can each control and use the drives within
the autochanger. In a shared Autochanger definition, a specific drive is dedicated to a single
NetWorker host. Autochangers cannot be shared across data zones.
A non-shared autochanger is attached to a single host. Backup data from hosts other than the
NetWorker Server must be sent to the storage node using the TCP/IP network.

NetWorker Dynamic Drive Sharing (DDS)
SAN
Storage Node Storage Node
NetWorker Server
Soprano
Use NetWorker Dynamic Drive Sharing to

configure and manage tape drives accessible
to two or more hosts
Dynamic Drive Sharing, or DDS, enables the configuration, management and access control for
devices accessible to two or more storage nodes in the same data zone. The devices can be stand-alone
or in an autochanger. Dynamic Drive Sharing is useful in reducing hardware needs and costs by
allowing multiple storage nodes to use the same device. Once configured, the administration for shared
drives is the same as non-shared drives.

Disk Backup Option

NetWorker provides an advanced file-type device
Media type is adv_file
Provides benefits over file-type devices
Simultaneous backup and recover
Supports Network Storage on Windows (CIFS) or NFS
Designed for use with NetWorker’s staging feature
Advanced File-type
Device
File-type Device
Additional space
Volume Marked Full Another Volume Save

Savesuspended
continues
NetWorker’s Disk Backup Option provides benefits over file-type devices. Advanced file-type devices
support multiple backups and one read operation simultaneously. This allows you to recover, clone, or
stage data from the device while backups are in progress. An advanced file type device can reside on
an NFS or CIFS filesystem.
Because of these benefits, advanced file type devices are well-suited for use with NetWorker’s staging
feature.
Advanced file-type devices respond differently than file type devices to the disk full condition. File-
type devices behave much like tape devices. When there is no more room on the device, NetWorker
marks the volume full and spans the backup onto another volume. This may be another disk volume or
a tape volume.
Advanced file-type devices are designed so a save never spans onto another volume. When the disk
becomes full NetWorker suspends any saves destined for that device until more space is made
available on that device.

Cloning and Staging Save Sets
Task Description Commands

Cloning Copies save sets, or a volume of save nsrclone
sets, to another volume nwadmin
Staging Moves save sets to another volume nsrstage
NetWorker provides the ability to further manage and protect save sets and volumes through cloning
and staging.
Cloning copies save sets or a volume of save sets to another volume.
Staging moves save sets to another volume.

BACKUPS
Now we turn our attention to backups.

Backup Overview
NetWorker Server
NetWorker Client
Data Tracking &
Tracking Management
Data
Storage Node
Data Source
Physical
Storage Device
Backup
Data Backup
Data
Data Destination
A backup is the process of copying data and storing it in another location. The destination can be
another directory on the same system, another server, or some type of storage media.
NetWorker manages this backup data, which includes client and tracking data, and directs it to the
proper destination. NetWorker also enables you to automate and schedule the backup process.
In a NetWorker backup, the NetWorker Client pushes the data to the storage node, where it formats the
data and an attached device writes it to a backup volume. The NetWorker Server stores the tracking
information.

NetWorker Backup Types
Client-initiated Backup Server-initiated Backup
Manual Automatic (scheduled) or manual
Attended Attended or unattended
The user initiates the backup The server software requests the
backup from the client
EMC Legato NetWorker allows you to perform two types of backups. The NetWorker user initiates a
client-initiated backup. A client-initiated backup is a manual process that the user must attend.
A server-initiated backup is automatic, meaning that the NetWorker Server initiates the backup by
requesting it from the client. This is an unattended backup. A server-initiated backup can also be
performed manually via the GUI or command line and is attended by the administrator.

Client-initiated Backup
Server
Tracking
Data
Tracking
save
Data
Save Set
Client
Save Set
Volume
Storage Node
A client-initiated backup is a manual process that you perform on the NetWorker Client from the GUI
or the command line. This type of backup is not automatic and is useful any time you want to perform
a backup outside of the regular backup schedule. The user specifies which files, directories, or
filesystems to save.
The NetWorker Server does not request a client-initiated backup and does not know that it is coming,
but it manages the backup when the client makes a request.
For a NetWorker Client to execute any type of backup, it must first be configured as a Client resource
on the NetWorker Server. This can be as simple as specifying the client TCP/IP host name to the
NetWorker Server and using all Default settings, or as complex as customizing all settings.
When the client performs a save, it creates a save set, sends it to the assigned storage node, and sends
tracking information to the server.
The storage node also generates tracking information and sends it to the server.

nwbackup GUI
Connect to other
NetWorker Servers
Start the backup.
Server Client
Search the client’s file

system and select the
files to back up.
NetWorker provides UNIX and Windows GUIs for performing client-initiated backups.
On UNIX, the nwbackup command is the NetWorker Client utility that starts the X/Motif GUI
interface and is the GUI front end to the save command. The nwbackup interface provides a File
Manager look and feel from which you select the files and directories to back up.
The nwbackup GUI allows you to perform additional tasks:
y You can connect to other NetWorker Servers of which the host is a configured NetWorker Client.
y You can search for files to backup.

NetWorker User GUI (winworkr)
Start the backup.
Search the client’s file

system and select the
files to back up
On Windows, the winworkr command starts the NetWorker User GUI. This is the GUI front end to the
save command. The NetWorker User interface provides a Windows Explorer look and feel from which
you select the files and directories to back up.

Server-initiated Backup Overview

Server
Tracking
Backup Request Data Backup
from the Server
Volume
Tracking
Data
Tracking
save
Data
Bootstrap Notification
Save Set &

Tracking Data
Client
Report Logs
Save Set &

Tracking Data
Storage Node Volume
A server-initiated backup is a backup request from the NetWorker Server to a configured group of
clients.
The remote execution request causes the clients to run their backup commands for their configured
save sets. The client and other configured resources determine what, when, and how to back up.
Tracking information is sent to the NetWorker Server and is also stored on the backup volumes.
Server-initiated backups also cause the NetWorker Server to back up the client file indexes and the
bootstrap save set to protect the NetWorker configuration and tracking data.
NetWorker generates a savegroup completion report and either mails it to root on the NetWorker
Server on UNIX or sends it to the savegroup log on the NetWorker Server on Windows. The report
contains information about the backup status, backup contents, data size, and backup creation date and
time.
If possible, the NetWorker Server generates and prints information about the bootstrap save set such as
the volume used and the bootstrap’s save set id or SSID. This information is needed to recover the
bootstrap in the event of a NetWorker Server disaster. If the print fails, the bootstrap report is included
in the savegroup completion report.
The NetWorker Server also does a consistency check on the client file indexes and media database and
enforces the aging status of save sets.

Server- vs. Client-initiated: Similarities

3. The Storage Node
receives the
savestream and sends
Server it to the backup device Storage Node
Media
DB
5. The server receives
volume location
information from the 4. The backup device
Storage Node passes data from the
Storage Node to a
volume
CFI
Volume
2. The server writes

tracking info to the
client file index save
1. The client sends the

savestream
© 2005 EMC Corporation. All rights reserved.

Client
Legato NetWorker Foundations - 41
The diagram shows the similarities between a server-initiated backup and a client-initiated backup.
1. The client sends the savestream.
2. The server writes tracking information to the client file index.
3. The storage node receives the savestream and sends it to the backup device.
4. The backup device passes the data from the storage node to a volume.
5. The NetWorker Server receives the volume location information from the storage node.

Server- vs. Client-initiated: Differences

Volume
Bootstrap
Server
Media 2. NetWorker backs up metadata :
DB • The NetWorker Server backs up
CFI databases for all clients in
4. The server Resource the group
enforces data Directory
life-cycling • The NetWorker Server backs up
policies through the Media Database and
database Resource files as the bootstrap
management save set
CFI
CFI
Email 1. The server

root@nwserver requests the
backup from the
client
3. The server triggers preconfigured
notifications
Client
The diagram shows the differences between a server-initiated backup and a client-initiated backup.
These steps are done by the NetWorker Server:
1. The NetWorker Server requests the backup from the NetWorker Client.
2. NetWorker backs up metadata: The NetWorker Server backs up CFI databases for all clients in the
group; the NetWorker Server backs up the Media Database and Resource files as the bootstrap save
set.
3. The NetWorker Server triggers preconfigured notifications.
4. The NetWorker Server enforces data life-cycling policies through database management.

NetWorker Backup Level Settings
Type Action
Full Backs up all files, regardless of whether they have
changed
Level [1–9] Backs up files that have changed since the last lower level
backup
(Differential)
Incremental Backs up files that have changed since the last backup,
regardless of level
Consolidated Backs up all data that has changed since the last full
backup and subsequently merges these changes with the
last full backup
Skip Skips the scheduled backup
NetWorker supports several backup level settings.

Full backups back up all files and directories in a save set and are the lowest level backup. This type of
backup requires the most storage space.
Level 1-9 backups only back up files that changed since a previous lower level backup, similar to the
UNIX dump command. For example, level 5 backs up any files and directories that changed since a
previous level 4 or lower level backup.
Incremental backups back up a save set’s files and directories that changed since the last backup of any
level.
Using level [1–9] and incremental backups can help control the amount of data backed up but can also
slow file recovery if several save sets are required to recover to a particular point in time.
Consolidated backups merge the most recent level 1 backup with a save set’s last full backup, creating
a new full backup. The difference between a full and a consolidated backup is that consolidated
backups are typically less taxing on the network and client. As a result, they increase backup
performance.
Skip backups do not back up the client’s save sets on a specific day. The savegrp program generates a
savegroup completion report that shows that the backup for the clients using this schedule were
skipped and that no data was backed up.

RECOVERIES
Having discussed backups, let’s move on to recoveries.

Recovery Overview
Volume
Client
A recovery restores data to its original state at a specific point in time. Recoverable data can include
files, directories, filesystems, or application data.
During the next few pages you learn about recovery types and client roles in a recovery.

Client Roles in a Recovery
Administering Client Destination Client

Client running recover Client where the data will be recovered
Source Client
Client that created the save set
The three client roles that exist for each recovery type are illustrated in the diagram.
The source client is the NetWorker Client whose data is being recovered. It is the client that created
the save set.
The destination client is the NetWorker Client that receives the recovered data. It is the client where
the data will be recovered.
The administering client is the client who initiates the recovery by running the NetWorker recover
program.

Recovery Types
Browsable Recovery Save Set Recovery Directed Recovery

Performed by users and Performed by the root (UNIX) Performed by NetWorker
administrators userid or Administrator administrators
(Windows) on the client
Started from any NetWorker Started from any NetWorker Started from any NetWorker
Client Client Client
Allows you to recover files Allows you to recover files Allows you to centrally
and directories from and save sets administer the recovery of
browsable save sets files, directories, and save
sets
NetWorker provides the three recovery types explained in the table - browsable recovery, save set
recovery, and directed recovery. All three types are manual processes; NetWorker does not schedule
recoveries or perform them automatically. Please take a moment to review the table.

Browsable Recoveries
CFI
Volume
1. Browse the client file index
2. Perform the recovery
Client
Browsable recoveries are recoveries of browsable save sets using interfaces that require information
from the client file index.
To perform a browsable recovery:
1. Use the nwrecover GUI or recover command to browse the index and mark the files and directories
you want to recover.
2. Start the recovery, which restores the files from the media to the client.

nwrecover GUI
Browse
directories. Click to select.
NetWorker provides UNIX and Windows GUI’s for performing browsable recoveries.
On UNIX, the nwrecover GUI allows you to perform browsable recoveries through a graphical user
interface that is installed with the client software. When using this program, you browse a
representation of a client’s filesystem as it existed at a specific point in time. The nwrecover program
only shows files from browsable save sets.
The GUI enables a user to:
y Browse the filesystem for a file
y Mark one or more files for recovery
y Execute the recover command
When the user makes a recover request, NetWorker automatically handles file or directory renaming
and deleting.
Recovered files retain the modification time and permissions they had when backed up. The
modification time does not change when the file is recovered.

NetWorker User GUI (winworkr)
Click to start
the recover.
Look for Click to select.

directories
and files.
On Windows, the NetWorker User GUI allows you to perform browsable recoveries through a
graphical user interface that is installed with the client software. When using this program, you browse
a representation of a client’s filesystem as it existed at a specific point in time. The winworkr program
only shows files from browsable save sets.
As with nwrecover, NetWorker User enables a user to:
y Browse the filesystem for a file
y Mark one or more files for recovery
y Execute the recover command

Save Set Recoveries

y Does not require the user to browse the client file index to
select data for recovery
y Is useful when
– Recovering an entire save set
– The save set being recovered is no longer in the CFI (the browse
policy has expired)
y Can be used to recover individual files

– Specific files or directories that have passed their browse period can
be recovered provided the exact pathname is known
y These interfaces can be used to recover save sets:

– nwrecover on UNIX
– NetWorker Administrator on Windows
– recover command
A save set recovery allows you to recover data from a save set rather than browsing and marking data
for recovery. Data that you can recover in a save set includes individual files, directories, and the entire
save set itself.
You can perform a save set recovery to recover entire save sets or files in save sets that have exceeded
or not exceeded their browse policy.
Files that have exceeded their browse policy no longer qualify for a browsable recovery. You can
restore them on a per-file basis with a save set recovery if you know the pathname.
You can use the nwrecover program on UNIX, or the NetWorker Administrator on Windows, or the
recover command to perform save set recoveries.

Directed Recoveries
1. Data is backed up NetWorker Server

from the Source Client bongo Administering
Client (W2K)
tuba
2. The Administering
Client issues a
#recover
recover command
3. Data is recovered to
the Destination Client
Source Client Destination Client

(UNIX) (UNIX)
soprano flute
A directed recovery is a recover request executed from the administering client that causes the
destination client to execute the recover program to recover the specified data. The data recovered is
provided from a source client’s save set. If the administering client and the destination client are not
the same machine, then the directed recovery interface is the recover command line only.
1. First, data is backed up from the source client.
2. The NetWorker administrator starts the directed recovery from the administering client. The
administering client issues a recover command.
3. Data is recovered to the destination client.
In a directed recovery, the source and destination clients must be the same platform type, even though
the administering client can be a different platform type.
Often the administering client is the NetWorker Server. However any NetWorker administrator can
initiate a directed recovery. In the example in the diagram, a NetWorker administrator on tuba initiates
a directed recovery causing flute to recover data from soprano’s save sets.
Directed recovery is useful when you cannot log on to the destination client to perform the recovery.
This remote administration capability gives you a high degree of flexibility and convenience in
recovering and redirecting data.

Course Summary
Key points covered in this course:

y EMC Legato NetWorker solution
y NetWorker advantages
y NetWorker host roles
y NetWorker data protection functions
y NetWorker administrative interfaces
y NetWorker-supported device topologies
y NetWorker backup process
y NetWorker recovery process
These are the key points covered in this training. Please take a moment to review them.
This concludes the training. In order to receive credit for this course, please proceed to the Course
Completion slide to update your transcript and access the Assessment.

Emc Legato Networker Foundations

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

Emc Legato Networker Foundations

Uploaded by

Copyright:

Available Formats

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

EMC Legato NetWorker Foundations

© 2005 EMC Corporation. All rights reserved.

Welcome to EMC Legato NetWorker Foundations training.

Legato NetWorker Foundations 1

EMC Legato NetWorker

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

Legato NetWorker Foundations 2

EMC Legato NetWorker

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 3

Let’s begin with a brief overview of NetWorker.

Legato NetWorker Foundations 3

The NetWorker Solution

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 4

Legato NetWorker Foundations 4

NetWorker Data Zone

The three types of NetWorker hosts are:

Legato NetWorker Foundations 5

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 6

Legato NetWorker Foundations 6

NetWorker Storage Node

z Organizes the data

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 7

Legato NetWorker Foundations 7

z Supports client backups/recoveries

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 8

Legato NetWorker Foundations 8

UNIX NAS/NDMP Host

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

Legato NetWorker Foundations 9

y Data created on different operating systems

y Backups to multiple devices

Save Set 4 NetWare

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 10

Legato NetWorker Foundations 10

NetWorker Uses Multiplexing

Collective Data Rate 3 MB/s

Multiple Data Streams

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 11

Legato NetWorker Foundations 11

Single Data Stream

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 12

Legato NetWorker Foundations 12

Open Tape Format

The pallets are stored in the

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 13

Legato NetWorker Foundations 13

W2K3 UNIX NetWare

NetWorker Storage Client Client Client

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 14

Legato NetWorker Foundations 14

NetWorker and NDMP

bongo Tracking Data

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 15

Legato NetWorker Foundations 15

NetWorker Software Editions

Max Remote Max Immediate

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 16

Legato NetWorker Foundations 16

NetWorker Add-on Modules

ClientPaks Required for any NetWorker client Yes

Storage Node Allow the NetWorker Server to use Yes

© 2005 EMC Corporation. All rights reserved. Legato NetWorker Foundations - 17