NetWorker Fundamentals 9.1 SRG
NetWorker Fundamentals 9.1 SRG
Copyright ©2015 EMC Corporation. All Rights Reserved. Published in the USA. EMC believes the information in this publication is accurate as of its publication date. The information is subject
to change without notice.
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.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. The trademarks, logos, and service marks (collectively "Trademarks")
appearing in this publication are the property of EMC Corporation and other parties. Nothing contained in this publication should be construed as granting any license or right to use any
Trademark without the prior written permission of the party that owns the Trademark.
EMC, EMC² AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager,
AutoStart, AutoSwap, AVALONidm, Avamar, Bus-Tech, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, EMC CertTracker. CIO Connect,
ClaimPack, ClaimsEditor, Claralert ,cLARiiON, ClientPak, CloudArray, Codebook Correlation Technology, Common Information Model, Compuset, Compute Anywhere, Configuration
Intelligence, Configuresoft, Connectrix, Constellation Computing, EMC ControlCenter, CopyCross, CopyPoint, CX, DataBridge , Data Protection Suite. Data Protection Advisor, DBClassify, DD
Boost, Dantz, DatabaseXtender, Data Domain, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, DLS ECO, Document Sciences, Documentum, DR Anywhere, ECS, elnput, E-Lab,
Elastic Cloud Storage, EmailXaminer, EmailXtender , EMC Centera, EMC ControlCenter, EMC LifeLine, EMCTV, Enginuity, EPFM. eRoom, Event Explorer, FAST, FarPoint, FirstPass, FLARE,
FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, Illuminator , InfoArchive, InfoMover, Infoscape, Infra, InputAccel, InputAccel
Express, Invista, Ionix, ISIS,Kazeon, EMC LifeLine, Mainframe Appliance for Storage, Mainframe Data Library, Max Retriever, MCx, MediaStor , Metro, MetroPoint, MirrorView, Multi-Band
Deduplication,Navisphere, Netstorage, NetWorker, nLayers, EMC OnCourse, OnAlert, OpenScale, Petrocloud, PixTools, Powerlink, PowerPath, PowerSnap, ProSphere, ProtectEverywhere,
ProtectPoint, EMC Proven, EMC Proven Professional, QuickScan, RAPIDPath, EMC RecoverPoint, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN
Advisor, SAN Copy, SAN Manager, ScaleIO Smarts, EMC Snap, SnapImage, SnapSure, SnapView, SourceOne, SRDF, EMC Storage Administrator, StorageScope, SupportMate, SymmAPI,
SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, TwinStrata, UltraFlex, UltraPoint, UltraScale, Unisphere, Universal Data Consistency, Vblock, Velocity, Viewlets, ViPR,
Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, Virtualize Everything, Compromise Nothing, Virtuent, VMAX, VMAXe, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, VSAM I/O
PLUS, VSET, VSPEX, Watch4net, WebXtender, xPression, xPresso, Xtrem, XtremCache, XtremSF, XtremSW, XtremIO, YottaYotta, Zero-Friction Enterprise Storage.
A backup is a copy of production data created and retained for the sole purpose of
recovering deleted or corrupted data. 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 and reporting is the process of storing and accessing information about the
backups. 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.
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 a single file or restore an entire file system.
Aging determines the length of time that the backup data is available for recovery.
NetWorker allows you to specify how long individual copies of data are maintained.
Staging is the process of moving a save set from one storage volume, which is the physical
medium where the backup data is stored, to another.
Cloning is similar to staging however instead of moving data it simply makes a copy of it.
This copy or clone can then be managed independently with its own retention time.
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.
NetWorker uses the client/server model which distributes the workload and improves
performance. It is supported on numerous operating systems as listed in the NetWorker
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.
One of the ways that Networker achieves backup efficiency with tapes is by interleaving, or
multiplexing, multiple backups onto a backup device. Multiplexing enables more than one
save stream to write to the same device at the same time. 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.
As shown on the slide, clients wrap their backup data into packages containing platform-
independent data, which are called save set chunks, before sending them to the storage
node. The storage node receives the packages and arranges them in media records and
files.
These are then stored in tape volume. The way the storage node organizes the data is also
platform-independent allowing any NetWorker storage node to read the data. Through the
use of Open Tape Format, a NetWorker storage node can be migrated to a host running a
different operating system.
These methods can be employed to reduce complexity in the backup environment, reduce
the impact of backups on production servers and reduce backup storage requirements.
A save stream is a single save set in the process of being backed up. The save program
runs on the NetWorker client and is used to back up a save set.
Data protection policies enable you to protect client data automatically throughout the
data protection lifecycle.
Actions are the key resources in a workflow for a data protection policy. An action defines
the data protection operation to be performed, such as backup or clone.
A single NetWorker server, along with its storage nodes and clients, forms a NetWorker
data zone within which data is protected.
An enterprise may have more than one NetWorker data zone; however, NetWorker servers
and storage nodes may belong to only one data zone.
NetWorker clients may be backed up by multiple NetWorker servers and therefore, may
belong to multiple data zones.
Additionally, NetWorker provides the ability to create multiple restricted data zones (RDZ)
on a single NetWorker server to support multi-tenancy requirements of organizations like IT
service providers and cloud hosting providers.
The client’s most important functions are to generate backups called save sets, push them
to a NetWorker storage node or device, and retrieve them during a recovery.
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. This data is sent to the
server where it is stored and used to facilitate browsable point-in-time (PIT) recoveries.
Additionally, the client software will also contain graphical user interfaces or command line
utilities that allow users to manually perform backup and recovery operations from the
client.
During a backup, a NetWorker client sends backup data to a particular storage node based
on that client’s configuration. The storage node organizes the client’s data and writes the
client’s data to one of its devices.
Storage nodes also send tracking information about the save sets written to the volume
during the backup to the NetWorker server. This information is used for future backups as
well as for recoveries.
During a recovery, the client reads from the storage node. The storage node provides the
device that contains the necessary volume.
The NetWorker server is always a storage node and is the default storage node for backups.
A NetWorker server can manage many storage nodes, but a NetWorker storage node can be
managed by only one NetWorker server. In other words, a storage node cannot exist in two
data zones at the same time. Storage node hosts have both the NetWorker client and
storage node software installed on them.
The NetWorker server stores the configuration information for the data zone including client
configurations, devices, policies, and schedules in its resource database.
Additionally, the server hosts the media database responsible for tracking volume and save
set location information.
Finally, the NetWorker server tracks the contents of all save sets backed up from all clients
in its client file indexes.
There can only be one 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 the
NetWorker client, storage node, and server software installed and is configured to
automatically back up its databases and client file indexes to ensure recoverability in the
event of a disaster.
NMC provides a Java-based graphical user interface accessible from any supported web
browser.
The Console server provides a global view of the NetWorker environment, allowing you to
centrally configure and manage one or more NetWorker data zones as well as run a number
of preconfigured and customizable reports.
The Console server gathers information about backups from the data zone and can be
hosted on the NetWorker server or on a separate host. One NetWorker Management
Console server can be used to manage multiple NetWorker servers and data zones across
an enterprise.
The Media Database is the NetWorker database used to track the backups and the
volumes they are stored on.
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.
Nearly all NetWorker resources are stored on and managed by the NetWorker server in the
resource database.
The Client File Index (CFI) is the database maintained by the NetWorker server that
tracks each backed up save set. The CFI information answers the question, "What files were
backed up and when?" for each client. The NetWorker server maintains a single index file
for each client computer. The NetWorker server is also a client and has its own index file.
The CFI information is used to support browsable recoveries using file selection and allows
clients to more easily recovery files to a specific point in time.
The Media Database tracks the NetWorker labeled volumes, the save sets contained on
them, and the life cycle status of the save sets and volumes. The NetWorker server uses
the media database records to determine which volumes are needed for backing up and
recovering data.
Networker manages this backup data, which includes client and tracking information, and
directs it to the proper destination. NetWorker also enables you to automate and schedule
the backup process.
During NetWorker backup, the NetWorker client pushes the data to the destination storage
node where it formats the data and writes it to a volume in a backup device which it
manages. Alternatively, newer NetWorker versions offer the ability for the client to send
data directly to the target device bypassing the storage node. Tracking information is sent
to the NetWorker server from the backup client and/or the storage node. The NetWorker
server is always responsible for storing the tracking information.
A client-initiated backup is started from a NetWorker client and is a manual process that the
user performs. It is usually a one-time event and is performed using a backup command or
GUI.
You can also start a server-initiated backup manually from either the NetWorker
Administration window or the command line.
Here, we see an example of a run of the Filesystem Backups policy displayed in the
NetWorker Administration Monitoring window. The policy has a backup action called
Backup and backs up five save sets.
• Full backup results in a back up of all files, regardless of whether the files have
changed. The advantage of full backup is faster recovery.
• Incremental backup results in the back up of the files that have changed since the last
backup, regardless of the level of the last backup. The advantages are, it is typically
faster than a full backup, less load on the server, and uses less volume space than a full
backup.
• Cumulative incremental backup results in the back up of all files that have changed
since the last full backup. The advantages are, it is typically faster than a full backup,
less load on the server, and uses the least amount of space.
• Logs only backup performs a backup of only database transaction logs. The advantages
are, it is faster than a full or incremental backup and there is less load on the server.
• Synthetic full backup performs an incremental backup and then combines the most
recent full backup and subsequent incremental backups to produce a new full backup.
The advantages are, it is faster than a full backup, faster recovery, low load on the
server, client, and network, and requires fewer volumes for recovery.
• Skip backup, skips the scheduled backup. For example, you can skip a backup on a
holiday if no one is available to change or add more tape media volumes.
• AFTD: Advanced file type devices (AFTDs) refers to an existing file system directory
configured in NetWorker as a backup to disk resource. Once the device resource is
configured, NetWorker uses the directory as a backup volume.
• DD Boost devices: DD Boost devices reside on Data Domain storage systems that have
the DD Boost features enabled. The DD Boost API accesses the DD Boost devices over a
network.
• Cloud disk device types: Cloud devices are specific to cloud storage services, such as
Atmos. Backups to a cloud device occur over the TCP/IP network.
The cloning operation reads save sets from a volume within a backup pool and writes the
data to a volume in a clone pool as shown in the example on the slide. You can clone save
sets multiple times, but NetWorker must write each clone to a separate volume. The clone
operation validates that NetWorker can read the original backup data successfully in the
media database and on the media volume, which provides additional assurance that you
can recover the data.
Staging is often used to move save sets from advanced file type devices to long term
storage media, such as tape. This allows the most recent backups to be written to and
recovered from disk and then moved to tape to free space on disk for subsequent backups.
In this example, the staging operation results in the deletion of the original save sets, once
they have been successfully staged to other volumes as indicated by the Xs in the diagram.
This is the difference between a clone and a stage operation. The save sets appear to move
from one volume to another. The resulting save set is identical to that of the first, but in a
different location.
Recovered files retain the modification time and permissions they had when backed up. The
modification time does not change when the file is recovered.
Recoveries are manual processes and can be categorized by the method used to recover
the data. There are three types of recoveries: browsable, save set, and directed.
During the recovery, the user selects the set of files and directories to be recovered. When
recovering an entire directory or file system, a point-in-time recovery is automatically
performed. This restores the directory or file system to the way it looked as of the most
recent backup. You can also recover a version of a file other than the most recent version.
Consider using a browsable recovery when you want to recover only the files that you mark
for recovery and no other files. Also, when you don’t know the exact name of a file, the file
can be located by browsing through the file system. Because of the point-in-time feature,
browsable recoveries are useful when the most recent backup is not a full backup and files
have been deleted or renamed since the full backup.
Since a save set recovery does not utilize client file index information, it does not perform a
point-in-time recovery. Recovering to a specific point in time using save set recoveries may
require multiple recovery operations followed by manual deletion and renaming of files.
A save set recovery is useful when recovering an entire save set or a large number of files
from a single save set. A save set recovery is also commonly performed when information
about the save set being recovered is no longer in the client file index.
A directed recovery is useful when you cannot log on to the source client to perform the
recovery, you want to perform all recoveries from a single NetWorker client, or you want to
transfer files from one computer to another. The directed recovery capability gives you a
high degree of flexibility and convenience in recovering and redirecting data.
Recoveries can be performed from the command line on any NetWorker client, by running
the recover command.
Additionally, the graphical user interfaces allow the user to mark one or more items for
recovery.
On Microsoft Windows clients, NetWorker User provides a front-end graphical interface for
recoveries.
NetWorker provides the Recovery Wizard that allows the administrator to perform most
NetWorker recoveries through the NetWorker Management Console without having to log
into the client or any other application. The Recovery Wizard supports browsable, save set,
and directed recoveries. With the Wizard, you can create and save a configuration that you
can reuse and modify later. Note that the wizard does not support cross-platform
recoveries.
With PSS, a single save set entry can be backed up in multiple, parallel save streams. A
save set is split into several save points, each taking a separate save session or stream.
Only as many streams as the client parallelism permits are running at any given time. As a
backup on a stream finishes, the stream is reclaimed and may be reallocated.
PSS is implemented for both UNIX and Windows platforms for file system type backups.
Block based backups are not yet supported with PSS.
Data Domain can be used for deduplicated backup storage in several ways, including
virtual tape and AFTD devices. When integrated with Data Domain through the use of the
NetWorker Data Domain device type, DD Boost technology is used. This significantly
increases backup performance by performing the deduplication process on the backup client
and reduces the amount of data traveling over the network to the Data Domain system.
CloudBoost translates these clones into generic objects which are sent to an object store,
which can be a public, private, or hybrid cloud. The CloudBoost appliance presents itself as
a NetWorker Advanced File Type Device. The enabled workflow is a clone operation to the
cloud; it is not a backup to the cloud. With this low cost tape replacement solution, each
CloudBoost appliance can support up to 6 PB of addressable backend storage.
NetWorker provides the NetWorker VMware Protection option for image-level backups.
With this option, an EMC Backup and Recovery appliance is deployed in the vSphere server.
Backups are configured and monitored using NetWorker Administration. Virtual machines
are backed up without installing backup agents on every virtual machine and are not
impacted by backup processing. Image-level and file-level recoveries can be performed.
At the parent level, NetWorker simplifies full protection for the Hyper-V physical server.
Users can easily back up and recover the server operating system, system state, data
volumes, and Hyper-V configuration database. Leveraging the Hyper-V VSS Writer,
NetWorker with NetWorker Module for Microsoft also executes full-image backups or
snapshots of Hyper-V child partitions. Within the child partition, NetWorker executes
application-consistent backups of Microsoft Exchange, SQL, and SharePoint. Application-
aware backups provide fine-grain recovery with application log management to ensure
maximum flexibility in data recovery. Support for off-host backup of child partitions
removes the impact of backup from production Hyper-V servers. The persistent snapshot
management of NetWorker enables fast and efficient snapshot restore and rollback for quick
Hyper-V recovery. Hyper-V data saved on secondary media such as disk, virtual tape, or
tape is also quickly recovered in a single step when needed. To ensure recoverability in
dynamic virtual environments, data can be directed to original or alternate locations.
If the checkpoint restart feature has not been enabled, a failure encountered during a
scheduled backup operation might require a rerun of an entire backup save set. This can be
costly when a limited backup window of time is available.
Using Client Direct has the potential for reducing bandwidth usage as the backup data
travels directly from the client to the storage device. Also, any bottlenecks at the storage
node are avoided.
The Client Direct feature is enabled for a client by default. Client Direct clients require a
network connection and remote access to the storage device such as a CIFS or NFS path. If
a Client Direct backup cannot be performed, a traditional backup via the storage node is
performed.
Block based incremental backups use the Change Block Tracking (CBT) driver to identify the
changed blocks, and back up only the changed blocks. Block based full and incremental
backups are fast backups with reduced backup times because the backup process backs up
only the occupied disk blocks and changed disk blocks respectively.
Block based backups use Client Direct and support only these target devices:
NSM supports several EMC array-based, software-based, and NAS environments including
VMAX, VNX, RecoverPoint, Isilon, and NetApp. With data on supported hardware, NSM
provides snapshot backup support for file system clients, NMDA for Oracle and DB2, and
NMSAP with Oracle.
NetWorker application modules fully integrate with the third-party vendor-specific APIs,
eliminating the need to develop or maintain custom backup and recovery scripts. They
provide fast, online, automated, and reliable granular backup and recovery for popular
database, messaging, content, and ERP applications.
The restricted data zone feature results in autonomy for tenants in a hosted or service
provider environment, and a simplified experience for NetWorker administrators.
• Resource update logging provides for the tracking of all resource changes made on a
NetWorker server. The security audit logging feature records auditable security events
related to the security and integrity of the NetWorker data zone. This information is
useful for accountability where there are multiple NetWorker administrators, for security
in the event of a system intrusion and for general auditing of modifications. In addition to
these two logs, NetWorker maintains log files that allow users to trace the sequence of
activities for the NetWorker server, Console server and NetWorker clients.
• Through the use of user authentication and authorization, user access to backup data for
restores can be restricted. Security from disclosure of backup data can also be enabled
through the use of encryption. When enabled, the data is encrypted on the client as the
save stream is generated.
In addition to the Console, two other administrative interfaces may be available depending
on whether the user is on a UNIX or Windows host.
nsradmin is a command line utility used to view, create, delete, and modify resources.
nsrwatch, available only on UNIX hosts, is a monitoring tool used to view current device
operations, active sessions, messages concerning recent activity, and any pending
messages such as an unfulfilled volume mount request.
With NMC, NetWorker can be administered from any host having a supported web browser.
For example, you can administer a Linux NetWorker server from a Windows machine and
vice versa. NetWorker also provides many command line utilities.
Note: The Devices window is used to configure and manage backup devices.
Note: The Media window is used to manage pools and to view information contained in the
media database and client file indexes.
NetWorker drill-down reports enable the user to double-click items within the report to view
more detailed information.
• Centralized monitoring and reporting across the backup environment, with long term
trending capabilities to improve planning, provisioning, utilization, and chargeback.
• Monitoring of capacity utilization, CPU utilization, memory, and port performance which
provides insight into performance bottlenecks.
With the EMC Licensing Solution, one or more EMC Licensing Solution License servers are
installed in a NetWorker environment. A single License Server can manage the NetWorker
license and capacity allocation for one or more data zones. A license file stores all licensing
information for the environment. This file is read to determine the type of licenses and the
amount of capacity purchased.
With the EMC Licensing Solution, license files are node-locked to the License server. The
entitlements are tied to a user’s ID and not to a specific NetWorker server. This makes for
flexibility in license management.
An EMC Licensing Solution License server is configured and managed by using LMTOOLS in
Windows or lmgrd in Linux.