NW Funda
NW Funda
Copyright © 2017 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or
its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” DELL EMC 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 DELL 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 DELL 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.
AccessAnywhere Access Logix, AdvantEdge, AlphaStor, AppSync ApplicationXtender, ArchiveXtender, Atmos, Authentica,
Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Aveksa, 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, CoprHD,
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, DSSD, 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, Isilon, ISIS,Kazeon, EMC LifeLine,
Mainframe Appliance for Storage, Mainframe Data Library, Max Retriever, MCx, MediaStor , Metro, MetroPoint, MirrorView, Mozy,
Multi-Band Deduplication,Navisphere, Netstorage, NetWitness, NetWorker, EMC OnCourse, OnRack, 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, Silver Trail, 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, VCE. 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.
Revision Date: February 2017
Revision Number: MR-1WP-NWFUN 9.1
• It provides centralized control of traditional and deduplicated backups along with cloud data protection
using a common management interface.
• By leveraging Data Domain deduplication, NetWorker helps users reduce the amount of disk storage
needed to retain and protect data without adding administrative complexity. It also provides a common
management interface for deduplicated backup.
• NetWorker provides support for backup and recovery of virtual clients with guest level backups.
NetWorker supports VMware image-level backups and block based backups for Microsoft Hyper-V.
• It provides fast, secure, and granular disaster recovery to ensure required service levels are met and
helps keep the business running.
• It provides NetWorker application modules for fast, online, automated, and reliable backup and
recovery of database, messaging, content, and enterprise resource planning (ERP) applications.
• NetWorker accelerates backup and recovery with security, and scalability to meet demanding service
level requirements.
• NetWorker provides the same enterprise-level user experience whether data is residing within the data
center or on the public cloud. When integrated with Dell EMC CloudBoost and Data Domain Cloud Tier,
it delivers highly efficient and secure long-term retention of backups in leading private or public cloud
offerings.
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 and schedule 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 a 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 generates
the backup, the backup creation date and time, and the backup type.
Recovery is a process of restoring data to a given point-in-time. NetWorker makes this process possible
from anywhere within the NetWorker datazone. This feature enables users to retrieve a single file or 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 a process of moving backup data from one storage volume 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.
NetWorker uses the client-server model which distributes the workload and improves performance. It is
supported on various operating systems as listed in the NetWorker Software Compatibility Guide. The
supported platforms seamlessly co-exist within the datazone. For example, a Microsoft NetWorker client
can back up to a Linux NetWorker storage node and vice versa.
Note that a NetWorker datazone is composed of a single NetWorker server, its clients, and storage nodes.
• License file
These methods can be employed to reduce complexity in the backup environment, the impact of backups
on production servers and the backup storage requirements.
NetWorker server is a collection of processes and programs that are installed on a host that performs
NetWorker services. The NetWorker Server also acts as a storage node and can control multiple remote
storage nodes.
NetWorker client is a physical computer where you install the NetWorker client software. The NetWorker
client computer can be any computer in a datazone that contains data, you want to back up. The NMC
server, NetWorker server, and NetWorker storage node hosts are also NetWorker clients.
NetWorker can back up data to local devices on a NetWorker server or remote devices on a storage
node. A storage node controls storage devices, such as tape drives, disk devices, autochangers, and
silos.
A single NetWorker server along with its storage nodes and clients, forms a NetWorker datazone within
which data is protected. An enterprise may have more than one NetWorker datazone. However,
NetWorker servers and storage nodes may belong to only one datazone. NetWorker clients may be
backed up by multiple NetWorker servers and therefore may belong to multiple datazones.
Additionally, NetWorker provides the ability to create multiple restricted datazones (RDZ) on a single
NetWorker server to support multi-tenancy requirements of organizations like IT service providers and
cloud hosting providers.
The NetWorker server stores the configuration information for the datazone including client configurations,
devices, policies, and schedules in its resource database.
Additionally, the server hosts the media database which is 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 datazone and it must be available for any NetWorker activity
to be supported in that datazone. 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.
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 recoveries.
Additionally, the client software contains 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 datazones at the same time. Storage
node hosts have both the NetWorker client and storage node software installed on them.
The Console server provides a global view of the NetWorker environment, allowing you to centrally
configure and manage one or more NetWorker datazones, as well as run a number of preconfigured and
customizable reports.
The Console server gathers information about backups from the datazone 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 datazones across an enterprise.
The Client File Indexes (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 PIT. The NetWorker server
creates and maintains one client file index per client.
The Media Database is the NetWorker database used to track the backups and the volumes they are
stored on.
Each configurable component in NetWorker is represented by a resource and there can be multiple
configurations for each type. Examples of resource types include clients, devices, tape libraries, and
policies.
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 easily recover files to a specific PIT.
The Media Database tracks the NetWorker labeled volumes, the save sets in the volumes, 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 the backup data, which includes client data and tracking information and directs it to
the 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. Once the data is written to
a volume, the storage node and the backup client send the tracking information to the NetWorker server.
The NetWorker server is always responsible for storing the tracking information.
With Client Direct, the client sends data directly to the target device bypassing the storage node.
A server-initiated backup is started from the NetWorker server and is configured to start automatically
through the use of NetWorker policies and workflows. Server-initiated backups may also be started
manually either by using the NetWorker Management Console or the command line.
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 the NetWorker User GUI or a backup
command.
A server-initiated backup can be started manually either from the NetWorker Administration window or the
command line.
The example shown here is the Filesystem Backup policy displayed in the NetWorker Administration
Monitoring window. The policy has a backup action called backup.
• Full backup, which results in a back up of all files, regardless of whether the files have changed. The
advantage of a 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,
results in less load on the server, and uses less backup storage 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, results in less load on the server,
and uses the least amount of space.
• Logs only backup performs a backup of database transaction logs that are created by a NetWorker
module. The advantages are, it is faster than a full or incremental backup and there is less load on the
server.
• Synthetic full backup is created by the back up of all data that has changed since the last full backup
and subsequent incremental backups. The advantages are, provides faster backups than a full backup,
faster recovery, less load on the server, client, and network, and requires fewer volumes for recovery.
• Tapes include tape drives and cartridges which may be physical or virtual.
• Advanced file type devices also known as AFTD, 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 are the Data Domain storage systems that have the DD Boost feature enabled.
Backup data stored on a DD Boost device is in deduplicated format.
• Cloud devices support backup to cloud. Cloud devices are specific to cloud storage services, such as
Atmos, CloudBoost, and Data Domain Cloud Tier.
During the backup operation, the save sets are backed up from the production host to the backup pool.
The cloning operation reads save sets from a volume within a backup pool and writes the data to a volume
on a clone pool. The target volume can be the same media type or a different media type than the original.
You can clone save sets multiple times, but NetWorker must write each clone to a separate volume. The
cloning operation validates that NetWorker can read the backup data successfully in the media database
and on the media volume, which provides additional assurance to recover the data.
Staging is often used to move save sets from advanced file type devices to long term storage media, such
as tape. Staging allows the movement of files with least recent backup data to tapes. This helps free up
space on the disk for subsequent backups.
The difference between a clone and a stage operation is that in staging, the save sets are moved from one
volume to another. The resulting save set is identical to the original data, but in a different location.
During a recovery operation, the backup data is retrieved from the device to the storage node, the storage
node then passes the backup data to the NetWorker client. Once the data is received, the client and the
storage node send the tracking information to the NetWorker server. NetWorker ensures necessary
security to avoid recovery of data by unauthorized persons. Files can be recovered to a directory other
than the directory from which they were backed up.
Recovered files retain the modification time and permissions they had when they were backed up. The
modification time does not change when the file is recovered.
Where supported, data may be recovered from the backup device directly to the client, bypassing the
storage node.
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 recovery is 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. It is also commonly used 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.
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 schedule recoveries and create and save a configuration that you can reuse and modify later.
Note that the wizard does not support cross-platform recoveries.
For Microsoft Windows clients, recoveries can be performed using the NetWorker User GUI on the
NetWorker client. The graphical user interfaces allow the user to mark one or more items for recovery.
Recoveries can be performed from the command line on any NetWorker client, by running the recover
command. This option is available for all platforms.
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. Checkpoint
restart is not supported when you use 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.
If the checkpoint restart feature is disabled, then a failure encountered during a scheduled backup
operation might require a re-run of an entire backup save set. This can be costly when a limited backup
window is available.
By default, the Client Direct feature is enabled for a client. 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, then a traditional backup through the storage node is performed.
With DD Boost backups using Client Direct, the deduplication processing occurs on the client.
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 AFTD and Data Domain as target devices.
NSM provides snapshot restore and recovery capabilities to retrieve data directly from a snapshot or from
a clone copy. Data on disk can be replaced from a snapshot by performing a rollback restore.
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 volumes. 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.
The restricted datazone feature results in autonomy for tenants in a hosted or service provider
environment, and a simplified experience for NetWorker administrators.
• Resource update logging provides 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 datazone. 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.
• Access control features to the NetWorker infrastructure include token-based authentication and role-
based authorization of users. NetWorker hosts and daemons use the nsrauth GSS mechanism to
authenticate components and to verify hosts. Firewalls monitor all traffic flow between two or more
networks, and allow only authorized traffic as defined by administrative policies.
• 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.
• Secure communications involve HTTPS, self-signed certificates, secure channels, and firewalls for
protecting the information that is being communicated.
AuthC is a web-based application installed on each NetWorker server. It uses a local database and
optionally an LDAP or Active Directory (AD) server, for authentication of external users.
A NetWorker with CloudBoost environment can extend on-site data protection to the cloud with the
following solutions:
• Backup in the cloud using Microsoft Azure port up to 6 PB of addressable backend storage.
CloudBoost decouples metadata from data, which removes a bottleneck for cloud reads and writes.
Encryption keys, metadata, and file system information are housed separately from the data. All advanced
data services, such as chunking, encryption, in-line deduplication, compression, and bulk data transfers
are performed separately from the metadata. The CloudBoost library is used to achieve data deduplication
before transferring data to the cloud, similar to Data Domain.
NetWorker can back up directly to the cloud without cloning data first to a staging server. The CloudBoost
appliance is a device type in NetWorker 9.0.1 or later.
The app-based policy is used implicitly as the data movement policy. The app-based data movement
policy tells Data Domain that the save sets being cloned are eligible for moving to the cloud.
Two types of NetWorker devices need to be created to implement NetWorker integration with Data
Domain Cloud Tier - the first one is a Data Domain device and the second one is a Data Domain Cloud
Tier device.
NetWorker provides the NetWorker VMware Protection (NVP) option for image-level backups. 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.
With the NVP solution the NetWorker server drives all operations. Data is protected under the control of
the NetWorker server. The natively-driven vProxies send data to Data Domain storage in native VMDK
format. The VMDK data format is kept as long as the data remains on a Data Domain device. The backup
environment is easily scaled by adding vProxies. The NetWorker server manages the data protection
environment using policies along with the screens and wizards provided by NMC for backup configuration,
recoveries, monitoring, and troubleshooting. There is also a FLR web user interface that works with the
NetWorker server to provide file level recovery from image backups.
As illustrated in the diagram, when using clone controlled replication or CCR, backup data can be
replicated to a second Data Domain system while still maintaining the native VMDK format. Less time is
required to complete backups and recoveries as there is no CDSF overhead. However, if tape or AFTD
storage is required, backup data can be replicated from Data Domain storage to tape under the control of
the NetWorker server.
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.
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.
Available NetWorker application modules include the modules listed on the slide.
NetWorker Management Console (NMC) provides a global view of all NetWorker servers involved in a
backup environment.
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 that the Devices window is used to configure and manage backup devices.
Note that the Media window is used to manage pools and to view information contained in the media
database and client file indexes.
A report can be displayed in a number of different formats, including a table and several types of charts.
Reports can be printed and also can be exported onto a file in one of several different formats.
NetWorker drill-down reports enable the user to double-click items within the report to view more detailed
information.
Data Protection Advisor provides advanced capabilities for your Networker environment which includes:
• 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.