NetWorker Modules Overview - SRG

Welcome to NetWorker Modules Overview.
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-NWMODS
Copyright © 2017 Dell Inc. NetWorker Modules Overview 1

This course covers NetWorker application modules and their usage. It provides an overview of the
NetWorker modules architecture and discusses the benefits and features of the various NetWorker
application modules.

This module focuses on the NetWorker module solution and its advantages.

NetWorker modules provide a comprehensive data protection solution for databases, messaging, content,
and enterprise software. NetWorker application modules integrate with vendor-specific APIs, so there’s no
need to develop or maintain custom backup and recovery scripts. NetWorker modules enable applications
to be backed up in an open and consistent state.
NetWorker Module for Databases and Applications works with NetWorker snapshot technology to provide
a backup and recovery strategy for protecting data on supported primary storage systems. NetWorker
application modules build on the core NetWorker infrastructure to provide automated, online protection
and granular recovery for popular database, messaging, content, and ERP applications.
Backups are performed locally or over the network to a centralized NetWorker server or storage node, or
directly from the client to backup storage using the NetWorker client direct feature. Both database and file
system backups are integrated with NetWorker and NetWorker modules. Management is easy, as
administrators can define schedules and execute backup operations centrally from the NetWorker web-
based user interface. NetWorker provides automatic storage management through automated backup
scheduling, data tracking, cloning, staging, and aging.
NetWorker delivers even more application protection advantages with deduplication by integrating with
Data Domain, which solves the challenges associated with traditional backup, enabling fast, reliable
backup and recovery. Integration with Data Domain and CloudBoost provides efficient and cost-effective
protection of applications in remote offices, virtual environments, and cloud environments, as well as data
center LANs.
Let us now look at some of the advantages of NetWorker modules.

The two methods for performing application backups are offline backups and online backups. They are
categorized based on the state of the application when the backup is performed.
In a offline or cold backup, the application is not active during the backup process. A cold backup requires
the application to be shutdown in order to back up its data. Hence, this type of backup is also referred as
offline backup. The application is restarted after the backup completes. NetWorker alone, without using
NetWorker modules, can back up closed applications with traditional, file system backups.
In a hot or online backup, the application is running and open during the backup process with users
accessing the data without any interruptions. NetWorker, when used with an appropriate NetWorker
module, supports online backups.
A primary concern with online backups is backing up open files. Most backup applications offer various
backup agents to perform these operations. There are different agents for different types of data and
applications. NetWorker modules use an application API or utility to extract data for backup without the
need to shut down the application. The application remains open after the backup completes. This
maintains the consistency of the backup and ensures that the application data is protected using the
manufacturer’s recommended and supplied APIs and processes.

Consistency is critical to ensure that a backup can be used in the restore of a file, directory, file system, or
database to a specific point-in-time. Consistency is achieved in various ways through the storage device,
application, or operating system.
For file systems, consistency can be achieved by taking the file system offline, or by keeping the file
system online and flushing host buffers before creating the backup to ensure that all writes are committed.
No further writes are allowed to the data while the backup is being created.
A database may be spread over numerous files, file systems, and devices. Data in one file may be
dependent upon data in another. A single transaction may cause updates to several files and these
updates may need to occur in a defined order. A consistent backup of a database means that all files need
to be backed up to the same ‘point’ or ‘state’. It doesn’t necessarily mean that all files need to be backed
up at the same time, but they must be in sync with each other, so that the database can come up
consistently in case of a restore.
To create a consistent backup, either the database is shutdown or a hot backup mode is used. If the
database is offline, it is not available for I/O operations. Because no updates are occurring, the backup will
be consistent. If the database is online, it is available for I/O operations. Transactions to the database will
be occurring continuously. Performing an online backup requires additional procedures during backup and
restore. Various methods are employed to ensure consistency of the backup, such as holding the changes
to the production data while the backup is created. NetWorker also supports the use of 'probes' to kick-off
backups based on events that makes protection even easier.

NetWorker modules support the most commonly used third-party applications. NetWorker modules
include:
NetWorker Module for Databases and Applications (NMDA) which is a single module that can be used to
protect IBM DB2, IBM Domino, Oracle, MySQL, Sybase, and Informix.
NetWorker Module for Microsoft (NMM) leverages Volume Shadow Copy Service (VSS) technology to
back up Microsoft Exchange, SQL, SharePoint, Hyper-V, and Active Directory. Additionally, this module
provides the capability to leverage Microsoft VDI for SQL server to provide a second method for
performing Microsoft SQL backups.
NetWorker Module for SAP provides backup and recovery of SAP applications, including SAP HANA.
NetWorker Module for MEDITECH is used to protect MEDITECH implementations.

NetWorker modules use snapshot technology for backups and recoveries of supported databases and
applications.
NetWorker Module for Database Applications supports integration with NetWorker Snapshot Management
(NSM) for both DB2 and Oracle when data is on supported primary storage.
NetWorker Module for SAP supports SAP with Oracle for data on supported primary storage by integrating
with NetWorker Snapshot Management.

NetWorker provides integrated snapshot management for supported clients through the NetWorker
Snapshot Management (NSM) feature. NSM leverages storage system-based snapshots to provide
snapshot backups on disk that can be tracked and managed in NetWorker. Impact-free backups are
configured by using a server other than the production host to perform backups to backup media. The
alternate proxy host or mount host will take on the performance burden of backups instead of the
production server. In the diagram, critical application data is stored on supported storage systems. At the
time of backup, an array-based point-in-time snapshot is created. NetWorker uses cloning to rollover or
copy the snapshot to backup media, DD Boost, or AFTD devices. There can be multiple point-in-time
snapshots taken throughout the day, any one of which may be cloned to backup media as needed. NSM
provides snapshot restore or recovery capabilities to retrieve data directly from a snapshot (snapshot
restore) or from a clone copy. You can also replace data on a source disk from a snapshot by performing
a rollback restore. NetWorker configuration wizards include options to configure snapshots and backups,
including the ability to use optional mount hosts in the backup workflow. NetWorker provides NSM
snapshot backups with the same benefits that are offered for conventional backups such as monitoring,
lifecycle policies, and granular file system recoveries. NSM supports various replication technologies and
platforms, including VMAX, VNX, RecoverPoint, and some NetApp filers. Supported applications with
NSM include NMDA for DB2, NMDA for Oracle, and NMSAP for SAP Oracle when production data
resides on supported storage systems.

NSM with ProtectPoint increases the time and bandwidth efficiency by backing up production data on
VMAX3 or XtremIO to deduplicated storage on a Data Domain system, through snapshots. NSM with
ProtectPoint uses a user provisioned set of VMAX3 storage array LUNs or XtremIO and Data Domain
vDisk devices to efficiently create deduplicated snapshot backups of production data on Data Domain
storage. A ProtectPoint snapshot can be cloned to other ProtectPoint devices or to conventional media,
such as DD Boost and AFTD.
There is minimal backup load on the production application host. Also, a backup storage node is not
involved in the backup.
NSM integration with ProtectPoint is available for NMDA DB2, NMDA Oracle, and NMSAP SAP with
Oracle clients.
NMC supports NSM ProtectPoint backups and restores through configuration, monitoring and restore
windows and wizards as it does with other types of backups and restores.

This module covered an overview of NetWorker modules. It also covered the advantages of NetWorker
modules, online backup of databases and applications, NetWorker Snapshot Management (NSM), and
NSM integration with ProtectPoint.

This module covers the role of NetWorker hosts and the backup and recovery processes used with
NetWorker modules. It also focuses on the review of special considerations for configuring NetWorker
resources to support backup and recovery using NetWorker modules.

NetWorker modules act as an intermediate layer between NetWorker and third-party native application
backup and recovery API’s or utilities.
NetWorker modules are client applications that are either installed on an application host or on a proxy
host. Both the application host and a proxy host, if used, are clients of a NetWorker server. As shown in
the slide, two NetWorker software components reside on a NetWorker module client: NetWorker module
software and NetWorker client software. NetWorker module software is installed after installing NetWorker
client software. Depending on the environment, the NetWorker server or storage node may also be
installed on a NetWorker module client.

To implement an application backup and recovery strategy, it is important to understand how NetWorker
modules and the NetWorker server work with third-party applications. The data flow illustrated in this
diagram shows what happens during a scheduled NetWorker backup with a NetWorker module.
The NetWorker server software provides configuration support and performs all scheduling tasks. When a
backup starts, a NetWorker module-specific backup command runs on the client, which will in turn
generate one or more save sets.This module-specific backup command runs on the client instead of the
standard NetWorker save command.
The backup command interfaces with the database’s backup Application Programming Interface (API).
With some NetWorker modules, scripts are executed which in turn, invoke the application’s native backup
utility. The API or utility provides the application data to NetWorker and determines what gets included
within the save streams and stored as save sets. NetWorker provides the interfaces for devices. This
diagram illustrates a client direct backup which sends the backup data directly to a backup storage device
bypassing the storage node. If a backup cannot use the client direct feature, the backup uses a path to the
storage node instead. At the end of the backup, the NetWorker server tracks the save sets and volumes.

As with backups, NetWorker modules work in conjunction with third-party applications to perform
recoveries. The slide shows the data flow during recovery using NetWorker modules.
Recoveries are performed through a NetWorker interface or the third-party application’s recovery
interface. When a recovery starts, NetWorker locates the save sets and volumes needed for the restore
and communicates with the native recovery command to coordinate the recovery. The module-specific
recovery command runs on the client instead of the standard NetWorker recover command. This is the
executable interfacing with the application’s recovery API or utility that performs the recovery.
NetWorker reads data from the backup volume for the restore. NetWorker also provides status during the
restore and at completion.

With NetWorker, clients are protected throughout the data protection lifecycle through the use of policies.
A policy is defined simply as a set of workflows. Each workflow is independent of any other workflow in the
policy. A workflow is associated with a group and a set of actions. Workflows specify when and how often
to run. A group defines the data sources to protect clients and their save sets. There is a single group per
workflow. An action defines a data protection operation like backup or clone. There may be multiple
actions within a workflow. In addition to a table view, NetWorker provides a visual representation of each
workflow when you click the workflow name in the Protection view tree.

Data protection policies and workflows can be configured to suit a specific backup environment.
NetWorker comes with several pre-configured policies along with corresponding groups and workflows to
facilitate setup of a NetWorker environment based on type of backup and application criticality. These pre-
configured policies are the Bronze, Gold, Platinum, and Silver policies that are highlighted here along with
the groups used in the workflows. You can modify the pre-configured resources and also create your own.
Groups, policies, and workflows can also be copied or deleted. Workflows can be moved from one policy
to another.

The client resource specifies the backup command and arguments, the save sets to be backed up, and
other information necessary for client backups and recoveries. Multiple client definitions can be created for
a single host to allow application and non-application backups of the same host, as well as multiple
instances of an application on a single host.
The save set attribute lists which databases the client should back up or the name of a backup script to
run during a server-initiated backup. Finally, add the client to a protection group. NetWorker provides the
New Client Wizard to walk users through the steps to quickly create a client with the required
specifications.

Consider creating media pools dedicated to NetWorker module client data backups. To have a scheduled
module backup, use a media pool associated with a specific protection group, select the pool when
creating the backup action in the workflow associated with the group. Using pools together with groups
facilitates the ability to maintain different retention times on application data from what is maintained on
the file system data.

The primary elements of planning a backup strategy consisting of both traditional and module backups are
policies, workflows, groups and their assigned client resources, and media pools. You will probably need
to create or configure multiple workflows and client resources to perform different types of backups and for
different backup schedules. Here are few considerations to plan your backup strategy.
To ensure you are prepared in the event of a system failure or data loss, it is essential to develop a
backup plan that includes regular file system backups along with NetWorker module backups. It is
recommended that you configure separate workflow resources for file system backups and application
backups. To avoid backing up the same data twice, exclude database/application data from the file system
backups. Ensure that file system and database backups for the same client do not run at the same time.
Also, document recovery procedures, train staff and conduct regular recovery tests to ensure a complete,
consistent recovery.
By configuring multiple workflows, backups can be distributed to alleviate network traffic and can be
scheduled for a time of day when performance demands on the application server, or client, are lower.
There may be specific requirements for different backup levels for certain applications or for multiple
configurations for online, offline and transaction log backups. These situations call for placing those clients
into separate workflows.
Another reason to use multiple workflows is that you may want to associate backups of a specific
database or type, or different retention periods, with specific media pools.

This module covered the role of NetWorker hosts and backup and recovery processes used with
NetWorker modules. It also covered considerations for configuring NetWorker resources to support
backup and recovery with NetWorker modules.

This module focuses on the features and functions of NetWorker Module for Databases and Applications
(NMDA) and its architecture. It also covers NMDA backup and recovery features for supported databases
and applications

NetWorker Module for Databases and Applications (NMDA) is a unified backup solution providing
protection for IBM DB2, Informix, Lotus Domino/Notes, MySQL, Oracle, and Sybase ASE databases.
NMDA is an add-on module that operates with NetWorker software and the supported database software
or application software.
NMDA also supports several types of virtualization software, including VMware, Solaris zones, and
Microsoft Hyper-V with NMDA installed in a guest operating system.
NMDA provides high performance backups and restores of databases and applications to and from
supported Networker backup devices, including Data Domain, Cloud Boost and tape devices, by
integrating the database backups and file system backups to a centralized backup server and relieving the
burden of backup from the database administrator.
NMDA provides configuration wizards for configuring backup and recovery. The wizards are integrated
with the Networker Management Console (NMC). Because NMDA is a single module supporting multiple
database applications, users also benefit from simplified Networker licensing.
The NetWorker Software Compatibility Guide provides the latest details about the platforms, operating
systems, database servers, application servers, and other software components that NMDA supports. The
NetWorker Module for Databases and Applications Administration Guide provides details about the
environment, supported features, and system configurations required to operate NMDA. NetWorker
guides are available at https://support.emc.com/products/.

Let us look at some of the backup and recovery features that are common to all the databases and
applications supported by NMDA.
Online backup feature allows NMDA to back up an online database or online application without requiring
any downtime. NMDA supports full and incremental backups and backups of transaction logs and other
files required for recovery. Also, backups can be either scheduled or manually initiated through a database
or application-specific command. Parallelism allows NMDA to support concurrent data streams for a
backup or restore.
The recovery feature allows NMDA to recover databases or applications to the current time or to an
arbitrary point-in-time. The data can be recovered to the original location or to an alternate location.
Depending upon the application, an entire database, an individual tablespace, or an individual datafile can
be backed up and recovered with NMDA.
NMDA also supports deduplicated backup with Data Domain. Using a Data Domain system for backup
storage is extremely flexible. You can configure the Data Domain system as NetWorker AFTDs, virtual
tape library devices, or DD Boost devices.
Other supported features include client direct, snapshot backups with NetWorker Snapshot Management
(NSM) for DB2 and Oracle data, backups of virtual machines, and backups and restores in cluster
environments.

This diagram shows the interactions between the application and NetWorker components for a scheduled
backup operation.
1. At the scheduled backup start time, the main NetWorker server-side service, nsrd, starts the
configured group’s backup by invoking the savegrp program.
2. The savegrp program requests that the NetWorker client-side service, nsrexecd runs the savefs
program, which sends information back to the savegrp program.
3. For each NMDA client in the backup group and each of the client’s save sets, the savegrp program
contacts the nsrexecd service to start the nsrdasv program.
4. The NMDA shared library for DB2, Informix, MySQL, Oracle and Sybase, or the child nsrdasv process
for Domino, performs the following actions:
a. Contacts the NetWorker server service, nsrd, to obtain the required authorization
b. Sends the backup data to the NetWorker media service, nsrmmd, for storing on the appropriate
backup volumes
5. The NetWorker online indexes store the tracking information. The nsrmmd service records tracking
information in the NetWorker media database by using the nsrmmdbd service. The backup session
sends tracking information to the NetWorker client file index by using the nsrindexd service.

NMDA is integrated with Oracle Recovery Manager (RMAN), through the Oracle SBT interface for Oracle
backup and restore operations.
NMDA supports both full and incremental backups for Oracle data.
A full backup, or stand-alone full backup includes every used block of the database objects specified in the
RMAN backup script. The backup skips the unused blocks. This type of backup occurs when you do not
specify a backup level with the RMAN backup command.
An incremental backup on the other hand includes blocks that have changed since the previous specified
backup. Incremental backups occur when you specify either incremental level = 0 or incremental level =1
with the RMAN backup command. Incremental backups are dependent on preceding incremental backups
in the same scheduled backup cycle.
A level 0 incremental is physically identical to a full backup, but is recorded as incremental in the RMAN
repository.
A level 1 incremental can be either a differential backup or a cumulative backup.

• A differential backup contains only the data blocks that changed since the most recent
incremental backup, whether the level is 0 or 1. The differential backup is dependent on the
preceding level 0 or 1 backup. Incremental backups are differential by default.
• A cumulative backup contains only the data blocks changed since the most recent level 0
incremental backup. The cumulative backup is dependent on the preceding level 0 backup.
NMDA supports the NMC wizards for configuring scheduled backups and the NMC Oracle Recovery
wizard for restore and recovery of Oracle data backed up by NMDA.
Copyright © 2017 Dell Inc. Course Name 26

NMDA can be configured to perform online and offline backups of DB2. With NMDA the entire DB2
database or an individual DB2 tablespace, or multiple DB2 tablespaces can be selected as backup
objects.
Three backup levels can be specified: full, incremental, and incremental delta.
• In a Full backup, DB2 backs up all database objects.
• In an Incremental backup, DB2 only backs up data pages that have changed since the last Full
Backup. This is also known as cumulative backup.
• In a Delta backup, DB2 backs up data pages that have changed since the last backup of any
kind.
NMDA also supports DB2 backups of transaction logs and roll forward recovery with the DB2 transaction
logs.
The NMDA recovery wizard can be run from the NMC Administration window to configure and run the
restore and recovery of NMDA backups.

NMDA supports specific features of IBM Domino backup and restore operations. This includes the backup
of Domino databases, the transaction logs, and the Domino Attachment Object Service (DAOS) directory
at both incremental and full backup levels.
Backups can be configured for DAOS base directory, for DAOS subdirectories, or individual DAOS
objects. The backup process can either run as a stand-alone backup or as an integrated backup.
The integrated backup, backs up the DAOS files after the completion of Domino database backup. NMDA
also supports the backup of Domino transaction logs only, without the backing up of other Domino files.
Restores are supported at the database and document levels.
The NetWorker User for IBM Domino interface is available on Windows servers and provides a graphical
tool for performing manual backup and recovery operations.The NMDA recovery wizard can be run from
the NMC Administration window to configure and run the restore and recovery of NMDA backups.

NMDA provides the services that connect NetWorker functionality to the Informix backup and restore
utility, ON-Bar. NMBA backs up and recovers Informix dbspaces and logical logs.
NMDA supports all the Informix backup levels that the Informix Dynamic Server (IDS) ON-Bar utility
supports, including levels 0, 1, and 2.
• Level 0 backs up all records in the selected dbspaces.
• Level 1 backs up the records that have changed since the last level 0 backup in the selected
dbspaces.
• Level 2 backs up the records that have changed since the last level 1 backup in the selected
dbspaces.
NMDA supports IDS logical log backups, including automatic, continuous logical log backups, and manual
logical log backups.

NMDA interacts with the MySQL Enterprise Backup (MEB) software through the Oracle Serial Backup
Tapes (SBT) interface to perform MySQL backups and restores.
NMDA support includes online and offline modes of backup. Supported backups and recoveries include
data from MySQL instance, databases and tables, MySQL binary logs and MySQL replicated slave
servers. Point-in-time restores are also supported.
Backup levels include full, incremental or cumulative, and incremental or differential. Incremental or
cumulative backs up changes since the last full backup, whereas, incremental or differential backs up
changes since the last full or incremental backup.
Binary log backup support includes backup of the binary logs immediately after a full backup of a whole
instance and backup of only the binary logs for an instance. You can optionally configure NMDA to delete
the binary logs from the disk after completing a binary log backup. Also, MySQL data and binary logs can
be sent to separate backup pools during a single NMDA backup.
NMDA can be used to validate the integrity of the backup image produced by an NMDA MySQL backup
without actually restoring any files.

NMDA supports backup and restore of Sybase databases which includes both data and transaction logs.
Supported backup levels for Sybase backups include full, cumulative, and incremental. A full backup
backs up the entire database, which includes both the data and transaction log. A cumulative backup
backs up the database data and logs that have changed since the last full database backup. An
incremental Sybase backup backs up the transaction log and truncates the inactive portion of the
transaction log.
On Windows systems, NMDA provides the NetWorker User for Sybase GUI program for configuring and
performing Sybase manual backup and recovery operations. The NMDA recovery wizard can be run from
the NMC Administration window to configure and run the restore and recovery of NMDA backups.
NMDA supports password protection for Sybase database backups and restores.

This module covered an overview of NetWorker Module for databases and applications. It also covered its
specific features and functions for each supported product.

This module focuses on the features and functions of NetWorker Module for Microsoft (NMM), its
architecture, and backup data flow. It also covers NMM features for supported databases and applications.

NetWorker Module for Microsoft (NMM) provides a single, unified backup, and recovery solution for
Microsoft server operating systems and applications including Exchange, SQL, SharePoint, Active
Directory, and Hyper-V. NMM is a single module supporting all Microsoft applications with a single
interface. Users benefit from simplified installation, configuration, and upgrades.
NMM leverages Microsoft Volume Shadow Copy Service (VSS) technology to provide snapshot-based
backup and recovery support for Microsoft Exchange Server, SQL Server, SharePoint Server, Active
Directory, and Hyper-V.
NMM can also use Microsoft Virtual Device Interface (VDI) technology for backup and recovery of SQL
Server data.
Block Based Backup (BBB) is a backup method where the backup client analyzes the volume and backs
up only the changed or new blocks that make up a file. NMM uses BBB technology for backups of
Exchange Server and Hyper-V data.
Consult the latest NMM release notes and the EMC NetWorker Software Compatibility Guide for
supported hardware, operating system, service pack, and application versions. The NetWorker Module for
Microsoft Administration Guide provides details about the environment, supported features, and system
configurations for NMM. NetWorker documentation is available at https://support.emc.com/products/

Let’s look at some of the features and benefits of NMM backup and recovery.
NMM leverages Microsoft VSS technology to create and manage consistent point-in-time snapshots.
NMM uses the VSS Common Requestor for all VSS framework related operations and
workflows.
NetWorker Management Console is used to create resources for scheduled NMM backups. The Client
Configuration wizard is available to create client resources. The NetWorker User for NMM is used to
recover applications using VSS, and NetWorker User for SQL can be used to back up and recover SQL
Server using VDI technology.
NMM supports deduplication backups and restores with Data Domain.
When using Client Direct, the client backup data is sent directly to DD Boost or AFTD storage devices,
bypassing the NetWorker storage node. This reduces bandwidth usage and bottlenecks at the storage
node, and provides highly efficient transmission of backup data.

NMM uses the VSS Common Requestor for all VSS framework related operations and workflows.
NetWorker uses the traditional save for SQL Server and SharePoint VSS backups and the block based
backup framework for Hyper-V and Exchange server backups. VSS hardware providers are not
supported. The logging model includes a single log file for save and a single log file for recover. The
backup command is nsrnmmsv and the recovery command is nsrnmmrc.

NMM can back up your data automatically or manually, as required. The backed up data can be recovered
as a specific item or an entire volume. You can also fully recover a disabled computer.
The backups supported by NMM include:
• Scheduled backups are available for all Microsoft applications. The NetWorker server backs up client
data regularly by using scheduled backups. You can configure and schedule backups using traditional
backup data protection policies and workflows.
• Federated backups is an internal backup architecture that is available for SharePoint Server, Hyper-V,
Exchange Server, and SQL Server (VDI). Federated backup protects databases running across
multiple application servers within Microsoft Failover Cluster with a single NetWorker save set.
• Granular backups are available for Active Directory. A granular backup does not use snapshot
technology (non-VSS). Instead, the backup is routed directly to a granular backup medium. A traditional
granular Active Directory backup enables you to recover individual objects and object attributes.

NMM supports three methods of recovering data. They are conventional, disaster, and granular recovery.
• A conventional recovery recovers data from conventional backup media, such as disk or tape. This is
the default recovery method. The entire volume or database is recovered as a whole.
• Granular Level Recovery (GLR) recovers individual object(s) within a database without recovering the
entire database. GLR is supported for Active Directory, Exchange Server, SharePoint Server, Hyper-V
and SQL VDI.
• Disaster recovery uses the basic Windows BMR process of bringing up a server after a disaster and
ensures that the system recovers with the operating system, the applications, and the data.

NMM supports stand-alone and clustered/DAG configurations for Exchange Server 2010, 2013, and 2016.
NMM supports block based full and incremental backups. A block based full backup backs up every
selected database and necessary log files. A block based incremental backup backs up only the changed
blocks of selected databases and necessary logs. Incremental backups stored on a Data Domain device
are stored as virtual synthetic full backups. Client direct must be enabled for BBB backups. Supported
backup device types are AFTD and Data Domain devices.
NMM supports only federated backups for Exchange Server DAGs. Exchange federated backups allow
you to back up all DAG members with a single save set without running a separate backup of each node.

The types of Exchange recoveries supported by NMM include roll-forward and point-in-time recoveries,
database and mailbox recoveries with Exchange RDB, remote database recoveries, GLR, and recovery to
an alternate mailbox database. Mailbox level recovery to an alternate mailbox is also supported.

NMM supports backup and recovery of Microsoft SQL Server in two ways: VSS and VDI technologies.
For VSS backup and recovery, NMM uses the VSS writer, SqlServerWriter. Only level full backups are
supported.
Backup and recovery granularity with NMM is available only at the database or instance level.
Directed recoveries can be performed to the same or different hosts.
Using VSS, NMM only supports databases in SQL simple recovery mode.

NMM provides an alternative for backing up Microsoft SQL Server by using Microsoft’s Virtual Device
Interface API, VDI.
NMM for SQL VDI supports manual, scheduled, and federated backups of SQL Server. NMM provides
support for SQL Server federated backup functionality for SQL Server AlwaysOn databases.
NMM supports three levels of backup: full, logs only, and cumulative incremental. A full backup backs up
the entire database, including all file groups or files in the database. A logs only backup corresponds to a
SQL Server transaction log backup and cannot by itself be used to recover a database. A cumulative
incremental backup captures all changes since the last full backup.
Recovery support includes point-in-time recoveries to a specific date, time or SQL log mark, partial
database restores, and directed database recoveries. Beginning with release 9.1, NMM supports flat file
recovery of SQL Server backups. With flat file recovery, NMM writes the backup to files instead of directly
to the SQL database. NMM supports granular level recovery using EMC ItemPoint.
NMM also supports NetWorker SQL plugin option for manual backup and recovery from the SQL Server
Management Studio GUI.

NMM leverages the Windows VSS framework and Microsoft Office SharePoint Server VSS Writers for
consistent point-in-time snapshots of SharePoint farms in standalone and distributed configurations.
Backup of a distributed farm includes content and configuration databases, search and service
applications, and web applications.
NMM supports only level full backups. NMM supports Microsoft SharePoint Server client direct backups to
Data Domain and AFTD devices.
Recovery of the SharePoint farm is supported at the farm and content database level. With granular level
recovery, you can recover specific items, such as files and folders, from a single full backup without
recovering the full backup. Granular recovery is supported by NMM with EMC ItemPoint. Directed
recoveries are also supported.

NMM supports granular backup of Active Directory. A granular backup does not use VSS snapshot
technology. Instead, the backup is routed directly to a granular backup medium. A traditional granular
Active Directory backup enables the recovery of individual objects and object attributes.
NMM supports full and incremental level backups. It does not support data deduplication for Active
Directory.

NMM supports backup and recovery of Microsoft Hyper-V. NMM utilizes the Hyper-V VSS Writer to back
up and recover each virtual machine and the Hyper-V host component.
NMM supports scheduled, block based full and incremental backups. Client direct must be enabled for
BBB backups. Supported backup device types are AFTD and Data Domain devices. Incremental backups
stored on a Data Domain device are stored as virtual synthetic full backups.
NMM provides the web-based Hyper-V File Level Restore GUI that enables NetWorker administrators to
select a backup for recovery, browse and select files, and perform browser-based local recoveries or
directed recoveries to a different virtual machine.
NMM supports both standalone and clustered configurations. NMM supports failover clustering for Hyper-
V through Clustered Shared Volumes (CSV) and supports federated Hyper-V image level backup of
Hyper-V clusters.
NMM supports Hyper-V VMs over Server Message Block (SMB) 3.0 file shares.
NMM supports Microsoft private cloud and Hyper-V management by using the System Center Virtual
Machine Manager (SCVMM) add-in for EMC data protection. This enables you to perform NMM Hyper-V
recoveries of SCVMM-managed virtual machines from within the SCVMM Console.
Alternatively or in addition to, you can perform individual backups of each VM and supported Microsoft
applications with guest level backup and restore. For guest-level backup and recovery, install an NMM
client on each virtual machine that hosts databases or specific applications supported by NMM on the
Hyper-V server. NMM considers each of these VMs to be a separate client.

This demo covers configuring VDI-based backup of SQL Server, performing recovery of SQL Server Data
(VDI), configuring VSS-based backup of SQL Server, and performing recovery of SQL Server Data (VSS).
Click the Launch button to view the video.

This module covered the features and functions of NetWorker Module for Microsoft. It also covered NMM
architecture and backup data flow. NMM features for supported databases and applications were also
discussed.

This module focuses on the features and functions of NetWorker modules for SAP and MEDITECH.

NetWorker Module for SAP (NMSAP) is used to protect SAP HANA and SAP Oracle data. NMSAP
provides a backup and restore interface between SAP interfaces, the NetWorker server, and NetWorker
Management Console.
Scheduled and on-demand backups are supported by NMSAP. It also supports wizard-based
configuration management. Full, differential, and incremental backup levels are supported for scheduled
backups with the NetWorker server.
NMSAP supports deduplication backups and restores with Data Domain systems.
NMSAP supports Client Direct backups to AFTD and DD Boost devices. The Client Direct feature enables
the NMSAP client to bypass the storage node and write the backup data directly to the backup device by
using direct file access. These features can improve backup performance and reduce network usage.
NMSAP with SAP Oracle can back up and recover Oracle database, archived redo logs, SAP specific
configuration files, logs, and other files. NMSAP interacts with SAP BR Tools for backup and
restore services. NMSAP is integrated with the SAP Oracle backint program, Oracle RMAN, and SAP BR
Tools for backup, restore, and inquiry operations.
For SAP HANA, NMSAP is integrated with the SAP HANA interface program, hdbbackint, to provide
backup and restore services for SAP HANA database data and redo logs.

NetWorker Module for MEDITECH is used with NetWorker to schedule, create, and manage local and
remote replicas of MEDITECH data on supported storage systems. NetWorker is integrated with the
MEDITECH application to enable the system administrator to perform scheduled NetWorker save set
backups and also to create disaster recovery replicas of the data without interrupting the application. You
can create local or remote replicas, view backup and restore process information, and recover to the main
host from any generation of the data.
NetWorker integrates with MEDITECH Backup Facility (MBF) to take hardware or array point-in-time
snapshots to back up the MEDITECH data to the NetWorker devices.
NetWorker Module for MEDITECH supports local replicas of the MEDITECH volumes with VNX,
Symmetrix VMAX, Unity and XtremIO storage systems. It also supports local and remote replicas of
MEDITECH volumes with VNX, Symmetrix VMAX, Unity, VPLEX, XtremIO and along with the
RecoverPoint storage system.
NetWorker Module for MEDITECH performs Integrated Serverless Backups (ISBs) of the LUNs that VNX,
Symmetrix VMAX, Unity, XtremIO, and RecoverPoint support to a NetWorker device. It also supports
Integrated Disaster Recovery (IDR) backups.
The NetWorker Module for MEDITECH supports NetWorker devices such as disk, tape, and Data
Domain.

This module covered NetWorker Modules for SAP and NetWorker Module for MEDITECH.

This course covered NetWorker application modules and their uses. It also provided an overview of the
NetWorker module architecture and discussed the benefits and features of the various NetWorker
application modules including database applications, Microsoft applications, and others.
This concludes the training.


NetWorker Modules Overview - SRG

Uploaded by

Copyright:

Available Formats

You might also like

NetWorker Modules Overview - SRG

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

NetWorker Modules Overview - SRG

Uploaded by

Copyright:

Available Formats

Welcome to NetWorker Modules Overview.

Copyright © 2017 Dell Inc. NetWorker Modules Overview 1

Copyright © 2017 Dell Inc. NetWorker Modules Overview 2

Copyright © 2017 Dell Inc. NetWorker Modules Overview 3

Let us now look at some of the advantages of NetWorker modules.

Copyright © 2017 Dell Inc. NetWorker Modules Overview 4

Copyright © 2017 Dell Inc. NetWorker Modules Overview 5

Copyright © 2017 Dell Inc. NetWorker Modules Overview 6

NetWorker Module for MEDITECH is used to protect MEDITECH implementations.

Copyright © 2017 Dell Inc. NetWorker Modules Overview 7

Copyright © 2017 Dell Inc. NetWorker Modules Overview 8

Copyright © 2017 Dell Inc. NetWorker Modules Overview 9

Copyright © 2017 Dell Inc. NetWorker Modules Overview 10

Copyright © 2017 Dell Inc. NetWorker Modules Overview 11

Copyright © 2017 Dell Inc. NetWorker Modules Overview 12

Copyright © 2017 Dell Inc. NetWorker Modules Overview 13

Copyright © 2017 Dell Inc. NetWorker Modules Overview 14

Copyright © 2017 Dell Inc. NetWorker Modules Overview 15

Copyright © 2017 Dell Inc. NetWorker Modules Overview 16

Copyright © 2017 Dell Inc. NetWorker Modules Overview 17

Copyright © 2017 Dell Inc. NetWorker Modules Overview 18

Copyright © 2017 Dell Inc. NetWorker Modules Overview 19

Copyright © 2017 Dell Inc. NetWorker Modules Overview 20

Copyright © 2017 Dell Inc. NetWorker Modules Overview 21

Copyright © 2017 Dell Inc. NetWorker Modules Overview 22

Copyright © 2017 Dell Inc. NetWorker Modules Overview 23

Copyright © 2017 Dell Inc. NetWorker Modules Overview 24

Copyright © 2017 Dell Inc. NetWorker Modules Overview 25

A level 1 incremental can be either a differential backup or a cumulative backup.

Copyright © 2017 Dell Inc. Course Name 26

Copyright © 2017 Dell Inc. NetWorker Modules Overview 27

Restores are supported at the database and document levels.

Copyright © 2017 Dell Inc. NetWorker Modules Overview 28

Copyright © 2017 Dell Inc. NetWorker Modules Overview 29

Copyright © 2017 Dell Inc. NetWorker Modules Overview 30

Copyright © 2017 Dell Inc. NetWorker Modules Overview 31

Copyright © 2017 Dell Inc. NetWorker Modules Overview 32

Copyright © 2017 Dell Inc. NetWorker Modules Overview 33

Copyright © 2017 Dell Inc. NetWorker Modules Overview 34

NMM supports deduplication backups and restores with Data Domain.

Copyright © 2017 Dell Inc. NetWorker Modules Overview 35

Copyright © 2017 Dell Inc. NetWorker Modules Overview 36

The backups supported by NMM include:

Copyright © 2017 Dell Inc. NetWorker Modules Overview 37

Copyright © 2017 Dell Inc. NetWorker Modules Overview 38

Copyright © 2017 Dell Inc. NetWorker Modules Overview 39

Copyright © 2017 Dell Inc. NetWorker Modules Overview 40

Directed recoveries can be performed to the same or different hosts.

Copyright © 2017 Dell Inc. NetWorker Modules Overview 41

Copyright © 2017 Dell Inc. NetWorker Modules Overview 42

Copyright © 2017 Dell Inc. NetWorker Modules Overview 43

Copyright © 2017 Dell Inc. NetWorker Modules Overview 44

Copyright © 2017 Dell Inc. NetWorker Modules Overview 45

Click the Launch button to view the video.

Copyright © 2017 Dell Inc. NetWorker Modules Overview 46

Copyright © 2017 Dell Inc. NetWorker Modules Overview 47

Copyright © 2017 Dell Inc. NetWorker Modules Overview 48

Copyright © 2017 Dell Inc. NetWorker Modules Overview 49