NetWorker 9.0 Overview - SRG PDF

Welcome to the NetWorker 9.0 Technical Differences Overview.
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.
Copyright 2015 EMC Corporation. All rights reserved.
NetWorker 9.0 Technical Differences: Overview
This course overview covers the features and enhancements introduced in the NetWorker
9.0 release. Topics include interface changes, licensing improvements, platform support,
NetWorker Virtual Edition, snapshot management, and improvements in the NetWorker
Module for Microsoft.
This module focuses on changes to the NetWorker Management Console, new licensing
model, installation changes, and NetWorker database improvements.
The NetWorker Management Console (NMC) has been changed in a few areas. In the
administration view, the Configuration tab from version 8.2 has been divided into three new
tabs; Protection, Hosts, and Server.
The Protection tab is where a user can locate the resources to create clients, modify
groups and schedules, and define new backup polices (which is a new feature in 9.0.)
The Hosts tab is where a user can manage the NetWorker hosts known to the NetWorker
server. Within this area is the Known Hosts tab which displays configuration information,
Software Inventory tab which displays available NetWorker updates, and the Software
Repository tab to manage the software updates available to push to NetWorker clients.
The Server tab is where a user can find the resources to administer the NetWorker server,
such as registrations, user groups, and Restricted Data Zones. Clicking on the NetWorker
server from the tree on the left displays information about the server in the center as well
as provide links to NetWorker resources on the right.
In addition to the changes described on the previous slide, there have been a number of less
noticeable, but very important changes made to NMC.
The Client Configuration Backup Wizard has been streamlined to prompt for the most often
used options. Additional options can be specified in the client properties. Some properties
are only displayed in Diagnostic Mode.
Save sets have one browse or retention policy time assigned to either a backup or a clone
operation.
Backup levels have been reduced to five choices; full, incremental, cumulative incremental,
logs only, and synthetic full. The choices in earlier versions of NetWorker, such as levels
19 and incremental synthetic full, are no longer available.
For Data Domain and Advanced File Type Devices (AFTD), a user can create an incremental
forever strategy. If no full backup exists, a full backup would be performed first followed by
incrementals. For AFTD, backups will automatically be promoted to full after every 38 th
incremental.
Policies and workflows have been introduced in 9.0 to take the place of groups, scheduled
clones, and other resources from older versions of NetWorker. A policy consists of a set of
independent workflows. Each workflow is associated with a group resource and a set of
actions which define when and how often a backup or clone should run. A workflow may
contain actions that run sequentially or in parallel. When performing an upgrade to version
9.0, resources from the older versions of NetWorker will be converted into new data
protection policies.
Notifications can be set for each policy. The notifications could be logged to a log file or
email address. By default, policy backup logs are located in the
/nsr/logs/policy/policy_name directory of the NetWorker server.
Here is a visual representation of the default Silver policy. It consists of two workflows;
Filesystem and Application. Each object in the workflow represents a resource which can be
modified from this view by right clicking on the object.
The Applications workflow consists of multiple default actions and pools:
Silver-Application represents the group where a user can add and remove clients.
Backup is the action. This is where a user can use the action wizard to specify options such
as the backup schedule and storage node.
Default is the media pool. In the media pool properties the user can specify the label
template and target device.
Clone is a secondary action. The action wizard will provide clone specific options here.
Default Clone is another media pool which is independent of the backup pool.
Actions within a workflow will not proceed unless the previous action has finished.
NetWorker 9.0 uses the EMC Common Licensing Platform (CLP) which requires the EMC
Licensing Solution server be installed in the NetWorker environment. This allows
administrators to distribute entitlements across more than one NetWorker data zone. Each
entitlement is associated with a customer ID and not a specific NetWorker server. This is in
order to add more flexibility in license management. The master license file on the license
server contains information about the type of license and acceptable capacity. It uses this
information when responding to a NetWorker server request for a license by means of the
CLP API.
Previously, users had to manage enablers and authorization codes specific to a NetWorker
server. Now they are able to self-manage and distribute entitlements across more than one
NetWorker data zone.
Here is a generalization of how to implement the new licensing solution into a users
environment.
First, install the EMC License Server package onto either the Windows or Linux 64-bit host.
The license server install packages are available from the same download location as the
NetWorker 9.0 packages. This can be the same host as the NetWorker server, but must be
accessible from all the data zones for which it will be managing licenses.
Next, request a license file from EMC at licensing@emc.com and provide the license server
hostname and IP address.
Then, copy the license file to both the license server and every NetWorker server
designated to receive these entitlements. Please note, if the NetWorker server is the license
server, the file must be copied to two different directories.
Finally, run the LMTools utility for Windows or lmgrd for Linux to configure and start the
license server service and install the file.
NetWorker Authentication Services (AuthC) is new to NetWorker 9.0. It provides token

based authentication for NMC and CLI users. AuthC is a web-based application installed on
each NetWorker server. It uses a local database and optionally, an LDAP or Active Directory
server, for authentication. When a NetWorker Management Console server is installed, the
user specifies the name of the NetWorker server that will authenticate access to the NMC
server. Optionally, AuthC can be managed by a separate server for external authentication.
10
During the installation wizard for NMC, authentication service information should be
entered, such as the authentication host and port.
Trust is required between each NetWorker server and the server running AuthC. When
AuthC is installed on the same host as NetWorker, trust is established automatically.
Otherwise, use the nsrauthtrust command on the host where a user would be adding the
trust.
11
After creating new users, the administrator must configure the NMC server to enable access
for both the local and external users. To set the level of access the user has to the NMC
server, map the NMC roles to the users and groups. NMC roles define the activities that a
user is authorized to perform. By default, NMC assigns all roles to the NetWorker
Authentication Service local database administrator.
From within NetWorker Administrators user groups, token-based authentications are
defined by the new External roles attribute. With authorization enabled, administrators
are validated to perform operations in NMC. Non token-based authentications are defined
by the Users attribute.
In order to use token-based authentication with the CLI command and perform backup or
recovery operations from a client, issue the nsrlogin command. Once authentication has
succeeded, the user can perform operations such as save and recover until the token
expires. By default, the time until a token expires is 8 hours.
12
As a way to maximize the utilization of all available save streams, client parallelism was
enhanced. NetWorker 9.0 introduces dynamic parallel save streams (DPSS) for file system
backup types. Save sets are split into several save points where each point utilizes a
separate save stream. The number of parallel streams is limited by the client configuration.
When a save stream finishes, it is automatically reclaimed and reallocated. Dynamic
parallelism handles save streams in batches and is more efficient than the static division of
save streams in previous releases. This allows for a lower parallelism setting per client. The
default client setting has been reduced to four (4) in NetWorker 9.0.
13
The DPSS function is enabled with the Parallel save streams per save set attribute in the
client resource properties. During backups, NMC will display the progress of each partial
save set in the NetWorker Administration Monitoring window.
In this example, the client parallelism value for the nwwindows client is set to the default
value of (four) 4. The client is backing up the All save set consisting of two volumes, C:\
and D:\. Here we can see that four (4) save streams started at 2:03:21 and ran in parallel.
As the backup of a stream finishes, it is taken up by another save point.
14
The number of supported platforms for NetWorker Server 9.0 has been reduced. NetWorker
Server only supports the x64 platforms for Windows and Linux. However, NetWorker
Storage Nodes and Clients continue to include platforms such as Solaris, AIX, and HP-UX.
Please note, support for IA64 Linux has been dropped for all NetWorker 9.0 packages.
15
The NetWorker 9.0 installation software for Windows consists of three separate packages.
NetWorker no longer uses the InstallShield setup.exe file.
NetWorker-9.0.x.x.exe is a comprehensive, all-in-one installer for Windows. With this
single package, a user could install the NetWorker server, storage node, client, NMC, AuthC,
NetWorker adaptor and Avamar client.
lgtoclnt-9.0.x.x.exe (LGTOclnt) is recommended to be used when installing just the
NetWorker base client. It is also the preferred installer when installing NMM and all add-ins
that require the NetWorker client first.
lgtoxtdclnt-9.0.x.x.exe (LGTOxtdclnt) provides additional feature support for NetWorker
clients including NetWorker Snapshot Management, NetWorker Authentication Service, NAS
snapshot, CLI utilities, NetWorker Module for Meditech, and SCVMM features. This client is
installed after the base client package.
By separating the advanced client capabilities into a different install package, the base
client package is smaller and more manageable. It gives the user additional flexibility to
install only the features required by a client host.
In Windows, the extended client is automatically installed when using the all-in-one installer
for the NetWorker server or storage node. It is not installed when selecting the client only
feature from this package.
Please note, when installing a NetWorker 9.0 client or server, the user may skip the
NetWorker License Manager software option during installation. This is for the legacy license
manager and is not required to use the new EMC Licensing Solution.
16
In addition to the installation changes mentioned on the previous slide, there are a few
more changes to be aware of.
The minimum supported version of Java is 64-bit Java 7 update 60 or Java 8. Java must be
installed before the installation of the NetWorker server or NetWorker Authentication
Service software.
The EMC Licensing Solution server is installed after NetWorker server in order to use the
new license model.
The System Configuration Checker can be run on Windows based client installations to
check for OS related configuration issues before installation. The tool can be run again once
any warnings have been addressed and the client installation has been completed.
For NetWorker integration with Avamar clients, the Avamar binary avtar is used instead of
the binary from the previous version nsravtar. Avtar is included with NetWorker 9.0 and
part of the base client install package.
17
Two of the databases used by the NetWorker Server have been enhanced in version 9.0.
One database is for NMC and the other is for media.
The Sybase SQL Anywhere database used for NMC in version 8.2 has been changed to
PostgreSQL in 9.0. The database is backed up automatically by the Server Protection Policy.
The default location has changed as well. The database destination folder is chosen during
the NMC 9.0 installation.
The WiSS database used for media in version 8.2 has been changed to SQLite in 9.0. The
benefits from the new database type include reduced media footprint complexity and
operational performance. Some of the new features include object caching, parallel request
processing (or multi-threading), request handling, and bootstrap compatibility.
18
As a result of the database changes described in the previous slide, database migrations
need to take place when upgrading to version 9.0.
To unload data from the older NMC Sybase database to the new PostgreSQL database, the
user must use a tool called gstdbunload which is part of the NetWorker installation
package. The gstdbunload tool can be run from the command line in both Windows and
Linux. This tool must be used before uninstalling the older NMC version or upgrading to
version 9.0. For Windows, the user can bypass command line and do the unload process as
part of the NMC upgrade wizard.
As for the media database migration, the process happens automatically during the first
startup of NetWorker 9.0. Once the upgrade is complete, the migration is initiated by the
nsrmmdbd process without any user intervention. Should there be a problem with the
migration, the user would be notified and NetWorker would run off the old database until
the problem is resolved.
19
This module covered changes in NetWorker 9.0 NetWorker Management Console, data
protection policies, authorization, installation, and database architecture.
20
This module focuses on the NetWorker Virtual Edition appliance (NVE), NetWorker Snapshot
Manager (NSM), ProtectPoint, block based backups for Linux, and the nsrimport command.
21
The NetWorker Virtual Edition solution (NVE) is a NetWorker server that runs as a virtual
appliance in a VMware environment. It is deployed from an OVA file on supported ESXi
servers. The SUSE Linux operating system, NetWorker software components (which
includes the NetWorker Installation Manager), VMware tools, and the latest security rollups
are preinstalled. After the deployment, installation configuration is performed using the
NetWorker Installation Manager for the NetWorker Server, NMC, AuthC, and the EMC
Licensing Solution.
NVE enables rapid deployment and simplified management by virtualizing all aspects of the
backup and recovery solution. It lowers the cost of ownership by sharing server and storage
infrastructure, and reduces the cost of support and maintenance for additional hardware.
22
Once NVE is deployed and powered on, a user can log into the NetWorker Installation
Manager using a web browser. Use the hostname as the URL and default login credentials of
root with changeme as the password. From here, a user will be required to change the
AuthC settings, passwords and server settings. Once the installation is complete, launch the
NMC from here or the default web address (http://NetWorker-Server:9000) to configure the
console similar to a physical installation.
23
The NetWorker Snapshot Manager feature (NSM) works with qualified storage arrays and
appliances to create copies of data. The NetWorker server manages the copies for recovery
and cloning to Data Domain or conventional media. NSM is part of the extended client
package. Each application server and mount host must be running both the base client and
the extended client packages. The extended client provides all the functionality that the
EMC NetWorker PowerSnap module previously handled. There are a few new enhancements
of NSM in NetWorker 9.0:
NSM utilizes RestAPI to communicate with RecoverPoint 4.0+
VMAX3 arrays and SnapVX mirroring are supported when using Solutions Enabler
VNXe,VNXe2 arrays and VNXe-Snap mirroring are supported when using Naviseccli or
UEMCLI
DB2 is now supported in addition to NMDA Oracle and NMSAP with Oracle.
24
Performing a backup with NSM in NetWorker 9.0 is done by creating a workflow containing a
snapshot backup action. The backup snapshot action performs a snapshot of data on the
supported snapshot hosts as defined in the client resource. The Policy Action Wizard
configures the snapshot options such as duration based retention. When the minimum
amount of time has expired, the save set is removed from the media database and the
snapshot is deleted.
A few additional examples of NSM workflows are shown as well.
25
The ProtectPoint solution is an efficient method to reduce time and bandwidth to backup
data from VMAX3 LUNs to a Data Domain by integrating with NSM. ProtectPoint utilizes
user-provisioned VMAX3 Federated Tiered Storage LUNs (FTS) and Data Domain vdisk pools
to create deduplicated snapshot backups on Data Domain storage. There is minimal backup
load on the production application servers. The ProtectPoint solution is only available for
NMDA DB2, NMDA Oracle, and NMSAP databases with Oracle clients. It is not supported for
general file system backups.
26
ProtectPoint devices are created in NetWorker as one of the device choices in the New
Device Wizard. This is where the user will choose the Data Domain and vdisk pool. A new
workflow will need to be created using the snapshot backup action. Include the backup
media pool containing the ProtectPoint device. When data transfers are complete,
ProtectPoint uses the vdisk API to take a static image of the Data Domain LUN. This is
recorded in the NetWorker media database and becomes the recoverable snapshot.
27
Previously available for only the Windows Server operating system, Linux block based
backups (BBB) are available in NetWorker 9.0. For BBB, NetWorker scans a volume or a
disk in a file system, determines all the blocks that have been used or changed, and backs
up only those blocks in a single, sequential pass. It does this by taking an image-based
backup at the volume level, rather than walking an entire file system in the backup process.
Incremental backups are performed using the changed block tracking methodology. By
using block based backups for Linux, backups complete up to twice as fast as traditional file
level backups.
In order for BBB to be successful, the following requirements must be met for the Linux
client:
The install package must be version 9.0.
The Linux OS must be qualified.
The client must be using a supported volume manager.
The volume must be formatted with a supported file system.
The volume group must contain at least 10% free space.
If the requirements are not met, either a traditional file system backup will be performed or
the backup will fail.
28
In addition to the client package, the user must install the BBB package on the Linux
server, LGTObbb. The backup target must either be a Data Domain or AFTD device. To
enable block based backup, select the Block based backup and the Client direct options
on the client resource.
29
The new nsrimport command in NetWorker 9.0 allows a user to script a one-time operation
to import Data Domain enterprise application backups such as DDBDA (for Oracle, DB2, and
SAP) and DDBMA (for Microsoft SQL). These direct backups use DD Boost instead of a
backup application.
A user can utilize the features of NetWorker and maintain the same backups by using
nsrimport. Uninstall the DDBDA or DDBMA package and install the appropriate NetWorker
modules. Use nsrimport to copy the backup records to NetWorker. When the import is
complete, the backups will be indexed and cataloged in NetWorker. Backups can be
restored similar to any other NetWorker backup using NMDA, NMSAP, and NMM modules.
30
The user writes the script file and issues the nsrimport command. nsrimport requires a
Data Domain target device in NetWorker to clone the backups. When nsrimport connects
to the Data Domain, all the backups found in the repository will be copied to a new SQLite
database in NetWorker. The Data Domain repository will not be affected by the import
process.
31
This module covered the NetWorker Virtual Edition appliance, NetWorker Snapshot
Manager, ProtectPoint, block based backups for Linux servers, and the nsrimport
command.
32
This module focuses on the changes to NetWorker Module for Microsoft (NMM) to backup
applications, recover files in Hyper-V environments, and compatibility with older versions of
NMM.
33
Prior to NMM 9.0, the NetWorker architecture and workflow were very complex, consisting
of multiple components for backup and interaction with the Microsoft VSS framework. Also,
there were multiple products to be installed including the NetWorker base client, multiple
application logics, PowerSnap (for data movement and snapshot life cycle management),
and Replication Manager (as the VSS requestor). All these components contributed to
product complexity. If there were problems, it could be difficult to determine where to start
troubleshooting.
With NMM 9.0 simplification, NMM uses the VSS Common Requestor for all VSS framework
related operations and workflows, replacing Replication Manager. Also, PowerSnap snapshot
management is no longer needed. NetWorker uses the traditional save for SQL Server and
SharePoint VSS backups as well as the block based backup framework for Hyper-V and
Exchange. Please note, hardware providers are no longer supported.
Shown here are the differences these changes have made in reducing complexity by
comparing the NMM 8.2 diagram on the left with the NMM 9.0 diagram on the right.
34
Besides complexity in earlier versions, the process model for VSS backups included seven
processes. Nsrexecd spawned nsrsnap that spawned nsrsnap_vss_sv and on to more
processes. With NMM 9.0 clients, nsrexecd initiates one process, nsrnmmsv. For recover,
the recovery client interface starts one process, nsrnmmrc.
Consequently, the nsrsnap_vss_save and nsrsnap_vss_recover commands are no longer
used for VSS backup and recovery. They are replaced by the new backup command,
nsrnmmsv, and the new recovery command, nsrnmmrc.
Here is an example of specifying the new backup command when creating a SQL client
configuration for a VSS backup.
35
NMM 9.0 brings additional options to backup Microsoft SQL. For example, SQL VDI
transaction level backups now have the ability to turn off log gap detection.
During SQL VDI transaction log backup operations, there are checks for existing full and
transaction log backups which are already saved for a database. This functionality ensures
there are valid chains of SQL transaction logs, thereby enabling point-in-time recoveries. If
a log gap is detected, the backup is promoted to a full database backup. This is the default
behavior. However, SQL log gap checking can take anywhere from 5 to 30 seconds per
database, which can add up to a significant amount of time in a backup of a SQL server
with thousands of databases. With NMM 9.0, the user has the option to turn off log gap
detection to improve the performance for SQL database backups.
Please note, with log gap detection disabled, no other product should be backing up SQL.
36
In addition to the log gap detection behavior described on the previous slide, SQL VDI also
has two new backup levels; Logs Only and Cumulative Incremental. The previous backup
levels of Incremental and Differential for SQL VDI backups are deprecated. Internally,
however, things remain the same. The Cumulative Incremental level will internally perform
a differential backup. Likewise, the Logs Only backup level will internally perform a
transaction log or incremental backup.
37
NMM 9.0 offers support for Microsoft SharePoint federated backups. Users can offload
SharePoint backups to SQL Server 2012/2014 secondary servers and databases. There is no
backup load on the primary or active SQL server or database. As a result, NMM SharePoint
includes support for the following options.
Copy only full backup of an AlwaysOn database on a secondary server, available only in
the federated workflow.
Automatic determination of the preferred node of the AlwaysOn availability group and
spawning backup on that node.
Configuration of backup of both AlwaysOn databases and non-AlwaysOn databases via a

single cluster client.
Using the NMM Configuration Wizard to configure the SharePoint machine will create the
dependent clients for SharePoint clients, Windows Cluster clients (required for Federated
backup), and SQL clients.
38
NMM 9.0 supports SharePoint Server federated backups using the

AUTOMATED_BACKUP_PREFERENCE and BACKUP PRIORITY settings made in a SQL Server
2012/2014 AlwaysOn database via SQL Management Studio. This is consistent with SQL
Server federated backups supported prior to NetWorker 9.0. These options specify the SQL
Server backup preference for the availability group and determine where the backups are
run.
As shown here, the Prefer Secondary option specifies that backups occur on a secondary
replica except when the primary replica is the only replica online. In that case, the backup
occurs on the primary replica. This is the default option.
39
NMM for Exchange backups utilizes block based backups for the logs and Exchange
databases. As mentioned in previous slides, BBB can only use NetWorker Advanced File
Type and Data Domain devices. All backups are Exchange VSS FULLS and utilize the new
'nsrnmmsv' and 'nsrnmmrc' commands. Each incremental backup depends on changed
block tracking for improved backup performance. Both standalone and Federated Exchange
DAGs are supported. However, if an Exchange DAG contains a standalone database, it must
be configured separately.
The same three types of recoveries are still available for Exchange BBB using the NMM GUI:
Exchange Database Recover
Exchange RDB Data Recover
Exchange Granular Level Recover
40
A new user configuration tool called NMM Exchange Admin Configuration is available. The
configuration tool is designed to simplify the creation and management of users with
privileges to perform backup and recovery operations on the Exchange server. The tool runs
automatically after installation of NMM 9.0 for Exchange and can also be run at any time by
a domain administrator. There are three tasks the Exchange Admin Configuration tool can
perform:
Create Admin User
Update Admin Password
Validate an existing admin
41
Similar to Exchange, NMM 9.0 utilizes BBB to protect Hyper-V backups. As a result, changed
block tracking makes incremental backups of Hyper-V virtual machines possible. BBB also
takes advantage of Microsofts partial writer support. This ensures that a save set consisting
of multiple virtual machines will complete even if one or more virtual machines are found to
be in a bad state and unable to backup.
NMM 9.0 permits the use of Hyper-V VMs to perform as virtual proxy backup hosts as well.
Mixtures of virtual and physical proxy hosts are permitted. This allows for multiple VM
backups to be performed in parallel on either Cluster Shared Volumes (CSV) or Server
Message Block (SMB) volumes. NMM must be installed on each virtual proxy host. Load
balancing of the virtual proxies is possible by enabling the Move CSV Ownership option in
the backup options of the client configuration.
42
A new web-based GUI is available to perform restores of NMM protected Hyper-V data. File
Level Recovery (FLR) permits NetWorker admins to recover individual files from the backup
of Hyper-V virtual machines in two different ways. A user can either download files to their
workstation using the web browser or direct the recovery to a different virtual machine.
These two options are called browser download restore and directed restore,
respectively. Monitoring the restore progress is possible using the Restore Monitor tool
located at the bottom of the FLR page.
43
NetWorker 9.0 server supports backups and restores existing NMM 8.2x an 3.0x clients.
NMM 9.0 has undergone extensive changes to simplify the architecture. In order for NMM
9.0 to recover data from NMM 8.2.x and earlier VSS backups, a user must select a new
option during the installation process. Restore previous NMM release backups is
deselected by default and must be chosen during the installation wizard. This creates a
separate subfolder containing the necessary NMM 8.2.1 binaries. The extended client
package is also required. The install permits restores of SQL, SharePoint, Exchange, and
Hyper-V VSS data which was backed up with NMM versions 3.0.1 and 8.2.x. A shortcut with
the same name is created for the purpose of launching the 8.2.1 NMM application to recover
the data backed up with an older version.
Restores of pre-9.0 NMM VDI backup save sets can be performed with 9.0 without having to
change the NMM installation options.
44
Upgrades to NMM 9.0 are possible from NMM versions 3.0.x and 8.2.x. However, some user
intervention is required. For example, after upgrading, the backup command for VSS
backups must be changed on each client resource from the old nsrsnap_vss_save
command to the new nsrnmmsv command. The NMC bulk edit feature can be used for
changing multiple client resources.
45
This module covered the simplified architecture of NMM, changes for NMM application
backups, the Hyper-V FLR GUI, and NMM backward compatibility.
46
This course covered changes to the NetWorker Server software, the NetWorker Virtualized
Edition appliance, increased integration with storage hardware, and enhancements to
support Microsoft environments.
This concludes the training. Proceed to the course assessment on the next slide.
47

NetWorker 9.0 Overview - SRG PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

NetWorker 9.0 Overview - SRG PDF

Transféré par

Droits d'auteur :

Formats disponibles

Welcome to the NetWorker 9.0 Technical Differences Overview.

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

NetWorker Authentication Services (AuthC) is new to NetWorker 9.0. It provides token

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.

NetWorker 9.0 Technical Differences: Overview

Copyright 2015 EMC Corporation. All rights reserved.