NetWorker+Integration+Workshop VMware

NetWorker Integration with VMware
Introduction
This module focuses on integrating NetWorker with VMware for backup and
recovery.
Upon completing this module, you will be able to:

 Identify best practices for VMware backup and recovery with NetWorker
 Describe how to integrate VMware backup and recovery environments with
NetWorker and the vProxy appliance
 Perform backups and recoveries of VMware virtual machines with
NetWorker and the vProxy appliance
NetWorker Integration Workshop_FINAL
Page 432 © Copyright 2019 Dell Inc.

VMware Data Protection Fundamentals
Introduction
This lesson covers the fundamentals of data protection in a VMware environment,

including virtual machine protection strategies for backup and recovery of VMware
virtual machines, and NetWorker backup solutions for virtual machines.
This lesson covers the following topics:

 Considerations and challenges for backup and recovery of VMware virtual
machines
 NetWorker backup and recovery support for VMware virtual client
 NW vCenter HTML5 support plug in
© Copyright 2019 Dell Inc. Page 433

VMware vSphere
Overview
VMware vSphere is the industry-leading server virtualization software and the heart
of a modern SDDC (Software Defined Data Center) that includes ESXi and vCenter
Server. vSphere helps you run, manage, connect, and secure your applications in a
common operating environment across clouds. With vSphere, you can support new
workloads and use cases while keeping pace with the growing needs and
complexity of your infrastructure. vSphere uses virtualization to do the following
tasks:
 Run multiple operating systems on a single physical machine simultaneously

 Reclaim idle resources and balance workloads across multiple physical
machines
 Work around hardware failures and scheduled maintenance
VMware vCenter Server unifies resources from individual hosts so that those
resources can be shared among virtual machines in the entire data center. It
accomplishes this by managing the assignment of virtual machines (VMs) to the
hosts and the assignment of resources to the virtual machines within a given host
based on the policies that the system administrator sets.

vCenter Server enables the use of advanced vSphere features such as VMware
Distributed Resource Scheduler (DRS), VMware High Availability (HA), VMware
vMotion, and VMware Storage vMotion. VMware vSphere components include data
center, host, and virtual machine.
Datacenter is a structure under which you add hosts and their associated virtual
machines to the inventory.
Host is a computer that uses ESXi virtualization software to run virtual machines.
Hosts provide CPU and memory resources, access to storage, and network
connectivity for virtual machines that reside on them.
Virtual Machine is a software computer that, like a physical computer, runs an

operating system and applications. Multiple virtual machines can run on the same
host simultaneously. Virtual machines that vCenter Server manages can also run
on a cluster of hosts.

vSphere 6.7 Features
Overview
vSphere 6.7 is the last release for vCenter Server on Windows, it is a universal
application platform that supports new workloads, including 3D Graphics, Big Data,
HPC, Machine Learning, In-Memory, Cloud-Native, and existing mission critical
applications.
vSphere 6.7 further enhances the support and capabilities that are introduced for
GPUs through VMware’s collaboration with Nvidia, by virtualizing Nvidia GPUs
even for non-VDI and non-general-purpose-computing use cases such as artificial
intelligence, machine learning, big data and more. With enhancements to Nvidia
GRID™ vGPU technology in vSphere 6.7, instead of having to power off workloads
running on GPUs, customers can simply suspend and resume those VMs, enabling
for better life cycle management of the underlying host and significantly reducing
disruption for end users. VMware continues to invest in this area, with the goal of
bringing the full vSphere experience to GPUs in future releases.
With vSphere Persistent Memory, customers using supported hardware modules,

such as those available from Dell EMC and HPE, can use them either as super-fast
storage with high IOPS, or expose them to the guest operating system as non-
volatile memory. This will significantly enhance performance of the operating
system as well as applications across various use cases, making existing

applications faster and more performant and enabling customers to create new
high-performance applications that can use vSphere Persistent Memory.
vSphere 6.7 introduces new protocol support for Remote Directory Memory
Access (RDMA) over Converged Ethernet, a new software Fibre Channel over
Ethernet (FCoE) adapter, and iSCSI Extension for RDMA (iSER). These features
enable enterprises to integrate with even more high-performance storage systems,
providing greater flexibility to use the hardware that best complements their
workloads.
Another new capability being introduced in vSphere 6.7 is Instant Clone. It

enables creation of powered-on VMs from the running state of another powered-on
VM, without losing its state. The cloned VM can be created on the same or different
host than the source VM. Instant Clone supports vMotion, DRS as well as HA. It
enables customers to move into a new paradigm of just-in-time (JIT) provisioning,
which is given the speed, and state-persisting nature of this operation.

VMware Backup Challenges
Overview
Virtual data centers present many challenges for the backup environment. Prior to
virtualization, physical server utilization commonly ran as low as 5% to 20%.
Because virtualization makes a single physical server act like multiple logical
servers, it drives up server utilization by combining numerous computing resources
on a single server. With VMware, users commonly run 10 or more virtual machines
on a single server, increasing utilization to 60% to 80%.
Virtual server backups can be accomplished using a traditional approach with

conventional backup software. The backup software is simply installed and
configured on each virtual machine, and backups run normally through a backup
server to conventional backup targets, including tape drives, virtual tape libraries,
or disk storage. However, applying traditional backup techniques to virtual server
backups does have drawbacks. The most significant challenge is resource
contention. Backups demand significant processing power, and the added
resources that are needed to execute a backup may compromise the performance
of that VM and all VMs running on the system—constraining the VMware host
server's CPU, memory, disk, and network components, and often making it
impossible to back up within available windows.

Backup processes must evolve to deliver greater efficiencies in a highly

consolidated environment. How is this possible with larger workloads and shared
resources?

Simplifying VMware Backups with vProxy
Overview
NetWorker provides you with the ability to perform virtual machine protection and
recovery by using the NetWorker VMware Protection solution with the vProxy
appliance, also known as NVP. This solution is about simplifying the user
experience and addressing the gaps in the previous ways for image backups and
restores of VMware virtual machines.
The NVP solution is less complex, easy to use, and easy to scale. Plus, it uses the
native NetWorker user interface for most workflows.

NetWorker VMware Protection Solution with vProxy Appliance
Overview
NetWorker provides you with the ability to perform virtual machine protection and
recovery by using the NetWorker VMware Protection solution with the vProxy
appliance, also known as NVP, which provides following features.
Uses stand-alone data-mover proxy appliances, or vProxy appliances, to backup

and restore virtual machines that run in a virtualized infrastructure, with the ability
to offload the data mover from NetWorker and run the backup as a virtual workload.
NetWorker directly manages the vProxy appliances without the use of an external
node for proxy management and load balancing.
Stores the virtual machine backups as raw virtual machine disk files (VMDKs) on
the Data Domain device, which reduces overhead. NetWorker does not convert the
backup to any backup streaming formats.
Provides the ability to clone virtual machine backups. When you use streaming
devices such as tape, NetWorker converts the save set directories format (SSDF)
to Common Data Storage Format (CDSF) during a clone operation, and converts
back to SSDF on Data Domain for recovery from streaming devices.
Provides user interfaces to perform image-level recovery or file-level recovery.

NetWorker VMware Protection with vProxy Appliance
Overview
The diagram that is shown on slide provides a high-level overview of the

components in the NetWorker VMware Protection Solution with the vProxy
appliance. The solution contains the following components.
vProxy appliances — Provide the data movement services between the VMware
host and the target protection storage, for example Data Domain.
NetWorker server — Provides the ability to manage vProxy appliances, configure

data protection policies for backup and clone operations. Integrates with file-level
restore to provide centralized management in a virtual environment.
NMC server — Provides the ability to start, stop, and monitor data protection
policies and perform recovery operations.
Dell EMC Data Protection Restore client—Provides the ability to perform file-
level restore by using a web interface.
DDR1 and DDR2 — Data Domain appliances that receive and clone backup data
in SSDF format.
Tape device — Media that receives backup data in CDSF format, and managed by
a typical NetWorker storage node.

NetWorker VMware Protection Solution
Overview
The table that is shown on slide lists the required components and their
configuration requirements for NetWorker VMware Protection with the vProxy
appliance.
When you install or upgrade NetWorker and deploy the vProxy appliance, ensure
that the NetWorker server and storage node are at the same version if storage
node will be installed, and that you use the latest version of the vProxy appliance.

NetWorker VMware Protection Solution Port Requirement
Overview
The NetWorker VMware Protection solution requires the incoming ports that are
outlined in the table that is shown on slide.

NetWorker VMware Protection Solution Port Requirement
Overview
The NetWorker VMware Protection solution requires the outgoing ports that are
outlined in the table that is shown on slide.

Processing Backups with the NVP vProxy Solution
Overview
This diagram illustrates the process flow for backups with NetWorker VMware
Protection vProxy solution. VMware backups are configured and initiated using the
NetWorker policy framework. The NetWorker server discovers vCenter information
directly. This discovery data is used to build protection policies.
There is an action binary, nsrvproxy_save. This binary is a multi-threaded process

that is launched by nsrworkflow as part of running the workflow. At a high level,
nsrvproxy_save is doing these tasks: reading configuration information from the
NetWorker server, reading input work items from the policy engine, reading
metadata related to the work items from vCenter, and creating save jobs for each
work item.
nsrvproxy_save spawns a thread to start a save session with the NetWorker media
broker. The broker determines the vProxy to use.
The backup request goes to the vProxy. Unless specified, the vProxy determines
the most efficient method for backup. vProxy will choose either the Hotadd or NBD
transport mode. Hotadd is the default transport mode; NBD transport is used when
the Hotadd transport does not have access to the datastores where the data
resides. The vProxy acquires the virtual machine data from the datastore and
sends the data to the specified Data Domain device. All backups are CBT

incremental backups based on previous backups residing in backup or clone

volumes on the Data Domain system. Only changed blocks are passed to storage.
The NetWorker server monitors the backup request on the vProxy until it
completes. The main nsrvproxy_save thread updates the save job-based state that
is maintained in the worker thread. NetWorker is integrated with the vProxy to
pause, restart, or cancel the workflow. NetWorker stores metadata for save set
status and details as it does for traditional backups.

NetWorker VMware Protection Solution Considerations
Overview
Before deploying the NetWorker VMware Protection Solution with vProxy, review
the limitations as shown on this slide.
Network configuration settings are not backed up with the virtual machine as part of
a vApp backup in NetWorker. As a result, when you restore a vApp backup, you
must manually reconfigure the network settings.
When you upgrade vCenter, the vCenter version does not get updated immediately
in the RAP database since NetWorker does not periodically query vCenter. After
the upgrade, refresh VMware View in NMC's Administration window for the vCenter
version to update.
When cloning VMware backups using NetWorker VMware Protection with the
vProxy appliance, if the clone is performed to the same Data Domain system as the
backup, a REPLICATION license is required on the Data Domain system.
After upgrading to a NetWorker 18.x release with the vProxy appliance, new
policies can only be created with the vProxy appliance. You cannot run or edit
existing VMware Backup Appliance policies, and once you delete a VMware
Backup appliance policy, it is no longer available.

After performing a successful recovery of a virtual machine through vCenter

version 6, an alert may be displayed indicating a "VM MAC conflict" for the
recovered virtual machine, even though the new virtual machine will have a
different and unique MAC address. You must manually acknowledge the alert or
clear the alert after resolving the MAC address conflict. This alert can be triggered
even when the MAC address conflict is resolved.
When deploying a new vProxy that is not yet registered with NetWorker, wait for
the registration event to complete successfully with NetWorker before performing
an emergency recovery in the NMC Recovery wizard. The event appears in the
logs and in NMC.
When you delete a resource pool in vCenter and then re-create a resource pool
with the same name, backups fail. Re-configure the protection group with the newly
created resource pool.
The NetWorker VMware Protection Solution supports only the hotadd and NBD
transport modes. The hotadd mode is the default transport mode. If you want to
use both modes, the maximum sessions value for each must be set to the same
non-zero value. For example, set hotadd = 13 and nbd = 13. If you only want to use
one transport mode, ensure that you set the maximum sessions value for the other
transport mode to 0. For example, if you want to use hotadd mode only, set hotadd
= 25 and nbd = 0.
For proxies that only use NBD transport mode (proxies where you specify a value
greater than 0 for the NBD maximum sessions limit), you must also specify the
datastores for which you want the proxy to perform only NBD backups to ensure
that any backups of virtual machines running on these datastores are always
performed using NBD mode. This also ensures that the same NBD-only proxies are
never used for backups of virtual machines residing on any other datastores.
When you create a new protection group, you cannot select vProxy or clones of the
vProxy from the hosts list. To use the clone vProxy as a normal virtual machine,
clear the annotation string This is Dell EMC Backup and Recovery vProxy
Appliance in the Notes section of the cloned vProxy virtual machine.

Note: Hotadd is a transport mode where the backup-related I/O

happens internally through the ESX I/O stack using SCSI hot-add
technology. NBD, network block device, is a transport mode over the
LAN that is typically slower than the hotadd mode. In NBD mode, the
CPU, memory and I/O loads get directly placed on the ESX hosting
the production virtual machines since the backup data moves through
the ESX server to reach the proxy over the network. Hotadd provides
better backup performance than the NBD transport mode and is
recommended for faster backups and restores, and less exposure to
network routing, firewall and SSL certificate issues.

NetWorker VMware Protection Solution Considerations
Overview
The vProxy appliance does not support dual stack (IPv4 and IPv6) addressing. If
you want to run backups and restores using the vProxy appliance, use IPv4 only
addressing or IPv6 only addressing for the vProxy.
NetWorker does not support running multiple vProxy workflows concurrently

(backup, image-level recovery, or file-level restore operations) on the same virtual
machine when not using a vCenter server in your environment.
The NetWorker VMware Protection Solution does not support Data Domain Boost
over fibre channel (DFC). The NetWorker VMware Protection Solution does not
support Data Domain SMT (Secure Multi-Tenancy). You can create different
DDBoost users to segregate access to specific DD Boost devices. However DD
Admin credentials are required for performing instant access and file-level restore
workflows.
The NetWorker VMware Protection Solution only supports image-level backup and
disk-level backup. You cannot perform backups of individual folders within the
Virtual Machine.
When using independent disks, you cannot perform VMware snapshot for backup.

NetWorker VMware Protection with the vProxy appliance does not currently
support the protection of virtual machines within a Restricted Data Zone. When you
create a VMware policy in NMC, ensure that you leave the Restricted Data Zone
field blank.

Performance and Scalability Considerations
Overview
Performance and scalability of the NetWorker VMware Protection Solution depends

on several factors, including the number of vCenter servers and proxies and the
number of concurrent virtual machine backups. The table that is shown on slide
provides information about these scalability factors and maximum
recommendations, in addition to concurrency recommendations for sessions
created from backups of the vProxy appliance. The count of sessions is driven by
the number of proxies, clone jobs, and other backups running through this server.
Each vProxy Appliance can run up to 25 sessions.
See the latest Dell EMC NetWorker 18.2 VMware Integration Guide for a complete
and most recent list of recommendations and best practices for performance and
scalability of the NetWorker VMware Protection solution with vProxy.

NetWorker VMware Protection Best Practice
Overview
Ensure that the NetWorker server and storage node are at the same version, and
that all the vProxy appliances you deploy are compatible with this version.
Install VMware Tools on each virtual machine by using the vSphere Web Client.
VMware Tools add extra backup and recovery capabilities that quiesce certain
processes on the guest operating system prior to backup.
Installation of third-party tools or applications in the virtual appliance for the

purposes of monitoring the appliance status and protecting the appliance from
computer viruses can have a negative impact on system performance. Therefore,
Dell EMC recommends that you do not install any additional tools or applications in
the appliance.

Overview
Ensure that the vCenter server's Datastore Browser feature is enabled, which
enables you to browse all datastores associated with the vSphere environment.
NetWorker VMware Protection requires this feature to download configuration files
for a virtual machine during backup and recovery operations. This feature is
enabled by default, but you can verify the feature status by opening the vpxd.cfg
file within your vCenter configuration, and ensuring that the entry for
enableHttpDatastoreAccess is either set to true or is not contained in the file.
Information on how to locate the vpxd.cfg file within your vCenter configuration is
provided in the VMware documentation.
vProxy remote site configurations with a storage node communication latency

greater than 50 ms require a storage node in the remote site.
Avoid deploying VMs with IDE virtual disks; using IDE virtual disks degrades
backup performance. Use SCSI virtual disks instead whenever possible.
During policy configuration, assign virtual machines to a protection group based on

logical grouping to enable for better scheduling of backups that help you avoid
resource contention and create more organized logs for review.

When you plan the backups, ensure that NetWorker VMware Protection supports
the disk types that you use in the environment. Currently, NetWorker VMware
Protection does not support the following disk types:
 Independent (persistent and non-persistent)

 RDM Independent - Virtual Compatibility Mode
 RDM Physical Compatibility Mode
The vProxy Appliance uses Changed Block Tracking (CBT) by default. If CBT is
disabled on the virtual machine, and then it enables CBT automatically. If you add
a disk to the virtual machine after the first full backup, for the next policy run a full
backup will be performed automatically for the newly added disk, and an
incremental backup will be performed for the existing disk. For information about
disabling CBT.
When backing up thin-provisioned Virtual Machines or disks for Virtual Machines

on NFS datastores, an NFS datastore recovery does not preserve thin provisioning.
VMware knowledge base article 2137818 at http://kb.vmware.com/kb/2137818
provides more information.
Dell EMC recommends you set an appropriate NetWorker server/storage

parallelism value, according to the available resources, to reduce queuing. For
example, five vProxy appliances with backup and clone operations require more
than 125 parallel sessions. Therefore, setting the parallelism for the NetWorker
server to 128 or higher (while also setting the server with 32+ GB memory and 8+
CPUs) will suit such an environment. The NetWorker Performance Optimization
Planning Guide provides more details.
Note: You cannot use hotadd mode with IDE Virtual disks and
therefore backup of these disks will be performed using NBD mode.

Overview
The following configuration recommendations apply specifically to SDK sessions as

opposed to VI client sessions.
Each Virtual Machine backup to a Data Domain system consumes more than one
session on the Data Domain device. The default device configuration is target
sessions = 20 and max session = 60, however Dell EMC recommends that you
configure extra devices for more than 10 parallel backups, for example, when you
backup your database data to several backup devices in parallel.
Virtual Machines with extremely high IO may face hangs during consolidation due
to the ESXi forced operation called synchronous consolidate. Plan your backups of
such Virtual Machines according to the amount of workload on the Virtual Machine.

Overview
Use hotadd transport mode for faster backups and restores and less exposure to
network routing, firewall, and SSL certificate issues. The vProxy appliance currently
supports a maximum of 25 concurrent hotadd sessions. To support hotadd mode,
deploy the vProxy on an ESXi host that has a path to the storage that holds one or
more target virtual disks for backup. Hotadd mode requires VMware hardware
version 7 or later. Ensure that all virtual machines that you back up with Hotadd
mode are using Virtual Machine hardware version 7 or later.
For sites that contain many virtual machines that do not support hotadd
requirements, NBD transport mode is used. This can cause congestion on the ESXi
host management network. Plan your backup network carefully for large-scale NBD
installs. You may consider configuring one of the following options:
 Set up Management network redundancy

 Set up backup network to ESXi for NBD
 Set up storage heartbeats
If you have vFlash-enabled disks and are using hotadd transport mode, ensure that
you configure the vFlash resource for the vProxy host with sufficient resources
(greater than or equal to the virtual machine resources), or migrate the vProxy to a

host with vFlash already configured. Otherwise, backup of any vFlash-enabled

disks fail with the error "VDDK Error: 13: You do not have access rights to this file,"
and the error "The available virtual flash resource '0' MB ('0' bytes) is not sufficient
for the requested operation" on the vCenter server.
If you only want to use one transport mode, ensure that you set the maximum
sessions value for the other transport mode to 0. For example, if you want to use
hotadd mode only set hotadd = 25 and nbd = 0. If you want to use NBD mode only,
set hotadd = 0 and nbd = 10.
In order for backup and recovery operations to use Hotadd mode on a VMware
Virtual Volume (VVol) datastore, the vProxy should reside on the same VVol as the
virtual machine.
Important: http://www.vmware.com/files/pdf/techpaper/vmw-vsphere-
high-availability.pdf provides more information about setting up
storage heartbeats.

HTML5-based vSphere Client
Overview
VMware introduced a HTML5-based vSphere web client, and NetWorker has also
introduced an HTML5 version of vSphere Web Client Plug-In.

HTML5-based vCenter Plug-in
Overview
You can use the NetWorker Management Web UI to install either the HTML-based
or flash-based vCenter plug-in to enable virtual machine backup and recovery in
the vSphere Client or vSphere Web Client. The procedure of installing HTML-
based vCenter plug-in is as following:
1. Select Protection > VMware vCenters in the left pane.

2. In the Protection window's VMware vCenters pane, click the Install icon, and
select Install vCenter Plugin. The Install vCenter Plugin dialog displays.
3. Select the Plugin Type that you want to install. HTML installs the Dell EMC
NetWorker interface in the vSphere Client.
4. Provide the required HTTPS port that is configured for the vCenter server, or
leave the default value 443.
5. Type the username and password for the NetWorker administrator user.
6. Click Install.

Note: Note: If you installed the HTML-5 based plug-in, you can use
the vcui log file available at /nsr/authc/logs/vcui.log to assist with
troubleshooting issues with the Dell EMC NetWorker interface. If you
installed the flash-based plug-in, you can use the ebr-server log file
available at /nsr/authc/logs/ebr-server.log to assist with
troubleshooting issues with the VM Backup and Recovery interface.

NetWorker vProxy Appliance Overview
Introduction
This lesson covers an overview of the NetWorker vProxy appliance components,

processes, and how to deploy them in a VMware protection environment.

 vProxy components and processes
 Deployment, configuration, and selection of vProxy appliances

vProxy Architecture and Workflow
Overview
The vProxy is a Linux OVA which is deployed in vCenter and discovered in

NetWorker. NetWorker 18.2.0.1 vProxy OVA uses Linux SLES12 SP1 (64-bit) as
the operating system and requires four CPUs and 8 GB of memory. REST API is
used to communicate with the NetWorker server. RabbitMQ acts as a message bus
to communicate between the vProxy’s engine processes and NetWorker Server. A
Virtual Disk Development Kit, or VDDK, is used to access the VM storage. DD
Boost is used to communicate with a Data Domain system.
When a backup action is performed by the NetWorker server, a request is sent to

the vProxy using REST APIs. The vProxy acquires VM data from the datastores
and uses DD Boost to send the data to the Data Domain target storage. This is all
managed by NetWorker. vProxies can be configured in NMC to automatically
assign to VMs based on load for both backup and recovery.

vProxy Appliance Processes
Overview
The vProxy virtual appliance communicates with the NetWorker server through the
REST API daemon, or “vr-api-d” process. The message bus, “rabbit-mq” process,
is at the center of the engine processes and communicates between the REST API
daemon process and the vProxy engine. These engine processes are responsible
for backup as the “v-backup-d” process, image recovery as the “v-recover-d”
process, and file recovery as the “v-flr-d” process.

NetWorker VMware Protection Solution with vProxy Appliance
Overview
Before backing up VMware data, use the following configuration checklist to ensure
that all configurations are done. The basic configuration includes the following:
 Synchronize system time between vCenter, ESX/ESXi/vSphere, and the vProxy

appliance
 Assign IPs carefully
 Use FQDNs (Fully Qualified Domain Names) everywhere
 For any network-related issue, confirm that forward and reverse DNS lookups
work for each host in the datazone
The following are for Data Domain system configuration:
 Upgrade all Data Domain systems to use DDOS version 5.7, 6.0.0.30, 6.0.1-10,
or 6.1. The Data domain Retention Lock feature is also supported for vProxy
backup and clone actions but requires DDOS 6.1
 Ensure that the Data Domain system does not reach the MTree limit and
maximum stream count limit for the Data Domain model being used
 Ensure that only devices from the same Data Domain system host be displayed
in Data Domain system pool when used in any Action

 Check the NFS settings. By default, only NFS v3 is enabled from the ESXi host.
If using NFS v4, you might be required to disable and use NFS v3 instead to
avoid issues with file-level restore operations
 For virtual machines within in application-consistent data protection policy,
network zoning must be configured to enable network connectivity between the
virtual machines and the Data Domain system
The following applies to NetWorker configuration:
 Ensure that the relevant devices are mounted

 Ensure that vProxy IP addresses are populated in DNS, and that the NetWorker
server has name resolution for the vProxy host names
 Wait until you successfully configure a policy before you run the policy
 A message is displayed after successful vProxy registration in NMC
The following applies to Virtual machine configuration:
 Ensure that the virtual machine network is zoned for access to Data Domain
 Ensure that the virtual machine has name resolution for the Data Domain
system
 Ensure that the virtual machine firewall has port rules for Data Domain
 For Microsoft SQL server, ensure that the databases instances are enabled for
data protection using a SYSTEM account
When using IPv6 instead of IPv4 for NetWorker VMware Protection with the vProxy
appliance, register vProxy with FQDN instead of IPv6 IP address in the NetWorker
Management Console and the NetWorker Management Web user interface When
you register the vProxy appliance in the NetWorker Management Console or the
NetWorker Management Web user interface, if you are using the IPv6 internal
protocol ensure that you specify the fully qualified domain name (FQDN) of the
vCenter server to register the appliance instead of the IPv6 address.
Note: Maximum stream count limit for the Data Domain model being
used can be found in the Dell EMC Data Domain Administration
Guide.

vProxy REST API Engine
Overview
The REST API engine on the vProxy appliance handles all HTTP communication
between the vProxy appliance and the NetWorker server. The REST APIs on the
vProxy are not directly accessible. A REST API client cannot be used to make
changes with custom HTTP operations, such as DELETE or POST, to any of the
resources on the vProxy.

vProxy Backup Engine
Overview
The backup engine on the vProxy appliance handles the backup requests coming
from the NetWorker server. This engine is responsible for locking the VM to prevent
conflicts such as requests from multiple vProxies or to prevent a backup and a
recovery from happening at the same time. Multiple backup sessions can occur
simultaneously. The sessions are performed in parallel. However, the VMDK
backups in each session happen sequentially.

vProxy Backup Files
Overview
The vProxy appliance writes three types of files to a directory on the target device
that is named for the save set ID:
 Backup descriptor file (backupdescriptor.json) describes the backup request,

VM, virtual disks, and pointer to configuration and data files
 VM Configuration files (.cfg file), contains the virtual machine settings
 Copies of VMDK files (.json files) for used blocks, changed blocks, metadata,
and user data

vProxy Recover Engine
Overview
The recovery engine on the vProxy appliance handles the image recovery requests
coming from the NetWorker server. This engine is also responsible for locking the
VM to prevent conflicts such as requests from multiple vProxies or to prevent a
backup or file recovery from happening at the same time. Multiple image recovery
sessions can occur simultaneously. The sessions are performed in parallel.
However, just like in the backup engine, the VMDK image recoveries in each
session happen sequentially.

vProxy Recovery Types
Overview
There are five different types of image recovery available, and they are:
 Virtual machine image recovery, which creates a new VM in vCenter from

backup which will be a clone of the original VM at the time of the backup
 Revert VM Recovery, which replaces a VM with the backup image essentially
restoring the VM to a previous state using change block tracking metadata
 Virtual disk recovery, which recovers a VMs disk as a new disk, mounts it, and
populates it with data from the backup
 Instant Recovery, which creates a new VM in vCenter and runs it off the backup
image on the target device
 Emergency VM Recovery, which is intended to be used to recover the vCenter
VM itself when vCenter is not available
In the Instant Recovery, the Data Domain performs a fast copy of the backup
image so not to alter the original backup. This is intended as a temporary solution
to get the VM up and running quickly. VMware Storage vMotion can be used to
move the VM to a permanent location if necessary.
In the Emergency VM Recovery, the VM is recovered directly to the ESXi host

instead of the vCenter server like in VM Image Recovery.

vProxy FLR Engine
Overview
The FLR engine on the vProxy appliance handles file restore requests coming from
the NetWorker server. To browse the backup image for specific files and folders,
the backup image must be mounted to the target recovery VM. Just like the Instant
Recovery, the VMDK is a fast copy image of the backup that is created by the Data
Domain system so not to impact the original backup image.
The agent exists as an RPM or MSI installation file on target VM. The FLR engine
installs the FLR agent, mounts the VMDK, and directs the agent to discover the file
system. The agent is needed because the operating system requires either root or
administrator privileges to perform host operations. Then, the engine performs the
copy of the files to the selected location on the target VM.

FLR Agent
Overview
The vProxy server performs a one time installation of the agent to the recovery VM.
Using the agent eliminates the need for operating system administrator or root
credentials to perform actions such as disk and partition discovery and file system
mounts. However, operating system credentials are required for the agent
installation.
Stop and start of the agent is possible because the agent installs as either a
Windows service or Linux daemon. The FLR agent interacts with the vProxy by
using vCenter APIs. This ensures that the interaction is possible even when the
VMs do not have a virtual network connection. In case an upgrade of the agent is
necessary, the vProxy server performs the upgrade automatically.

vProxy Backup Logs
Overview
You can use vProxy session log files to troubleshoot backup failures. The following
table provides information about the vProxy backup log files. Located in
/opt/emc/vproxy/runtime/logs/vbackupd/ on the vProxy host. Old daemon and
session logs are located in /opt/emc/vproxy/runtime/logs/recycle/.
On the NetWorker server, the locations of log files for individual backups differ on
Windows and LINUX:
 Linux—/nsr/logs/policy/policy_name
 Windows—C:\Program Files\EMC NetWorker\logs\policy\policy_name
The policy_name in above locations of log files is the name of the policy resource
that is associated with the backup action.
Note: A few minutes after completion, Recover App sessions logs are
moved to /opt/emc/vproxy/runtime/logs/recycle/.

vProxy Recovery Logs
Overview
The vProxy appliance contains log files, which you can configure to display debug
information. The table that is shown on slide provides information about the vProxy
recovery log files.

Deploy OVA on a vCenter Server
Overview
You can deploy the vProxy appliance from either the vCenter server, or the ESXi
host. Registration and configuration of the vProxy appliance must then be
completed in the NMC NetWorker Administration window's VMware Proxy
Configuration wizard, or the NetWorker Management Web UI.
When deploying the vProxy OVA on a vCenter server, configure the host with a
trusted SSL certificate, and then perform the following steps to deploy the OVA for
the vProxy host from a vCenter server by using the vSphere Web Client.
Install or upgrade to the latest version of the VMware Client Integration Plug-in.
This plug-in is required to run the vSphere Web Client. Download information is
provided in the knowledgebase article at https://kb.vmware.com/s/article/2145066.
The procedure of deploying OVA on A vCenter Server is as following.
1. Log in to the vSphere Client with an administrator account.

2. In the Main menu, expand vCenter and then expand Hosts.
3. Right-click the ESXi host on which you deploy the OVA and select Deploy OVF
template.

4. On the Source window, type a URL path to the OVA package or click Browse
and navigate to the OVA package location, and then click Next.
5. On the Review details window, review the product details such as the product
name, version, vendor, publisher, and download size, and then click Next.
6. On the Accept License Agreements window, the EULA is displayed. Review the
EULA and then click Accept.
7. On the Select name and folder window, specify a name for the virtual appliance,
and optionally the inventory location, for example a datacenter or VM folder.
Click Next.
8. On the Select storage window, select disk format and the destination datastore
on which to store the virtual appliance files and then click Next. It is
recommended that you select Thick Provision Lazy Zeroed to ensure that
amount of storage space that is allocated to the virtual appliance is available.
9. This step is optional. On the Select resource window, select the host, vApp, or
resource pool in which to deploy the OVA, and then click Next.
10. On the Select networks window, select the Source and Destination networks to
use with the appliance, and then select either IPv4 or IPv4 from the IP protocol
drop-down. Click Next.
11. On the Customize template window, specify the proper attributes, and then click
Next
12. On the Ready to Complete window, review the deployment configuration
details. If you will immediately configure the appliance, select Power on after
deployment, and then click Finish.
The Deploying window is displayed and provides status information about the
deployment.

Deploy OVA on an ESXi Host
Overview
Procedure of deploying OVA on an ESXi host is as following.
1. Log into the ESXi host with an administrator account.

2. From the File menu, select Deploy OVF Template.
3. On the Source window, type a URL path to the OVA package or click Browse
and navigate to the OVA package location, and then click Next.
4. On the OVF Template Details window, review the product details such as the
product name, version, vendor, publisher, and download size, and then click
Next.
5. On the Accept License Agreements window, the EULA is displayed. Review
the EULA and then click Accept.
6. On the Name and Location window, specify a name for the virtual appliance,
and optionally the inventory location, for example a datacenter or VM folder.
Click Next.
7. If the location you selected in the previous step has more than one available
host, the Host / Cluster window is displayed. Select the ESXi host or cluster on
which you want to deploy the virtual appliance, and then click Next.

8. On the Resource Pool window, perform one of the following tasks, and then
click Next.
9. On the Storage window, select the destination datastore on which to store the
virtual appliance files, and then click Next.
10. On the Disk Format window, select the disk format. Dell EMC recommends that
you select Thick Provision Lazy Zeroed to ensure that amount of storage space
that is allocated to the virtual appliance is available.
11. On the Network Mapping window, select the Source and Destination networks
to use with the appliance, and then click Next.
12. On the Ready to Complete window, review the deployment configuration
details. If you will immediately configure the appliance, select Power on after
deployment, and then click Finish.
The Deploying window is displayed and provides status information about the
deployment.

Configure The Network Settings
Overview
After you deploy the vProxy appliance on the ESXi host, configure the network
settings from a console window, and the procedure is as following.
1. From the vSphere Client application, open a console window on the vProxy
appliance or use ssh to connect to the appliance from a host that has network
access to the vProxy appliance.
2. Log in to the appliance with the root account. The default password for the root
account is changeme.
3. Use the /opt/emc/vproxy/bin/config_network.sh command to configure the
network settings.
For example: /opt/emc/vproxy/bin/config_network.sh fqdn IP address

netmask/prefix gateway "dns_server1, dns_server2, ... dns_serverN", where:
 fqdn is the Fully Qualified Domain Name of the appliance

 IP address is the IP address of the appliance
 netmask/prefix is the IPv4 netmask or IPv6 prefix length of the appliance
 gateway is the name or IP address of the gateway host
 " dns_server1, dns_server2, ... dns_serverN" is a comma-separated

Note: After you configure these settings shown on the notes section,
any subsequent network configuration changes, including DNS name
resolution, require a restart of all vProxy services.

Discover vProxy
Overview
The vProxy server is managed using NMC in the Devices window. However, the
vCenter must be discovered first in the Protection window. When the vCenter
server, where the vProxy was deployed, is discovered by NMC create a new RAP
resource for the vProxy under the Devices window. Right-click VMware Proxies,
and select New.
In the General tab, specify the hostname of the vProxy and ensure that the enabled
status is set to Yes.
In the Configuration tab, choose the vCenter server where the vProxy server was
deployed and specify the maximum sessions for either hotadd or NBD.
Finally, confirm the VM proxy port and the admin user and password. The vProxy
server displays in the VMware Proxies window in NMC.
The vProxy engine status is checked in the background periodically, approximately

every five minutes. When everything is completed, VM proxy service engines have
a value of All under the Miscellaneous tab. At this point, the vProxy will be
considered for selection.

vProxy Selection
Overview
A NetWorker broker, nsrd, considers available vProxy servers for selection during
the backup or restore of a VM client. Each vProxy is deployed to only one vCenter
so only those vProxies for the specific vCenter are considered for selection. The
vProxy servers are load balanced in a simple round robin method based on the
total number of sessions being serviced by each one.
A vProxy server can be restricted to a specific datastore in the properties of the

VMware proxy device.
Backups can be configured to prefer only a certain vProxy server, or servers, in the
actions of the NetWorker backup policy. However, it must have available sessions
in order for the broker to select it. The number of sessions that a vProxy can handle
is specified in the VMware proxy device properties for either maximum Hotadd or
NBD sessions. If all vProxies are running at capacity, and then the broker indicates
a busy condition and waits until one is available.

vProxy Maintenance
Overview
The vProxy server is intended to be maintenance free. All maintenance happens

automatically. However, control over the vProxy is available by connected to the
vProxy appliance directly through SSH and using the Linux command line.
The engine daemon process, such as vrecoverd, vbackupd, and vflrd, can be
stopped, started, or restarted using systemctl. For example, “systemctl stop
vflrd”. The stop command is intended to prevent the vProxy from trying to restart
the process.
If the network settings need to be changed, use the config_network.sh command.

Help with this command can be found by typing man config_network.sh.
All backup and recovery sessions should be managed in NetWorker. Do not

attempt to stop or clean up the sessions from the vProxy server.

vProxy Appliance Integration
Introduction
This lesson covers the integration of the vProxy appliance with NetWorker for
backup and restores of VMware virtual machines.

 Discovering VMware environment
 Overview of the backup workflow
 Cloning vProxy backups to Data Domain
 Performing image recoveries
 Performing file level restores
 Recover VBA backups using vProxy

High-Level Phases for NetWorker VMWare Protection
Overview
Here is a high-level description of the phases that are involved in providing data
protection for a VMware environment using the NetWorker VMware Protection
Solution with vProxy.
The first step is to discover the vCenter inventory by adding the vCenter host to the
NetWorker VMware View. When you add the vCenter server to VMware View, a
representation of the vCenter environment displays in the right pane of the view.
Next, add each vProxy virtual machine as a device on the NetWorker server.
Then, create a NetWorker VMware protection policy for backup and clone of one or
more VMware virtual machines or VMDK’s.
The next step is to perform image-level recoveries from the image-level backups.
Lastly, we will look at how to perform file-level restores using the Dell EMC Data
Protection Restore Client.

Discover the vCenter Inventory
Overview
Discovering the vCenter environment enables you to identify resources like virtual
machines and disks that you want to back up. In this phase, NetWorker performs a
discovery of the vCenter inventory and stores the information in RAP. When you
add a vCenter host to the NetWorker VMware View, the NetWorker process
nsrvim accesses vCenter through the vSphere API, takes a snapshot of the entire
vCenter, and stores the information in RAP. This information is periodically
refreshed. Also, when a new virtual machine is added to the vCenter environment,
NetWorker forces a RAP update.
To trigger discovery, you add the vCenter server to the NetWorker VMware View in
NetWorker Administration or using the NetWorker Management Web UI. Use the
FQDN to identify the vCenter server. You must supply the name and password of a
user account that has permissions to perform backups. NetWorker automatically
creates a client resource for the vCenter and displays the discovered vCenter
environment in the right-pane of VMware View. You can choose to display either a
map or tabular view. In map view, expanding the view shows a hierarchical view of
the vCenter. Clicking on any container shows a detailed map of that container and
its children. In the tabular view, you will see information for only virtual machines
including the group, policy, and workflow protecting each machine, where
applicable. Here we see an example of a display in map view.

Define a vProxy Device
Overview
There is a device category in the NetWorker Devices window for VMware Proxies.
Use this category to add each vProxy to the backup environment. Use the FQDN to
identify the vProxy appliance. You must select the vCenter where the vProxy is
deployed, supply the admin user account and password for the vProxy, and provide
the maximum NBD and hotadd sessions. Remember that the maximum value of
concurrent hotadd sessions per vProxy is 25. When complete, the vProxy service
engine shows a value of All on the Miscellaneous tab, indicating that the vProxy
can be considered for selection. Status of the vProxy is displayed in the right-pane
of the Devices window. The vProxy engine status will be checked periodically in the
background, approximately every five minutes.

Configure Backup and Clone Workflow
Overview
You use the NetWorker protection policy framework to configure NetWorker

VMware Protection Solution with vProxy backups as you would traditional backups
with a few exceptions.
For vProxy backups, you use a VMware protection group with a sub-type of All.
After selecting the vCenter to use for the backup, you will see a list of objects from
which to select the items to back up.
For the backup action, use the backup sub-type of VMware (vProxy). This
performs a backup of the virtual machines or VMDK’s in the vCenter selected in the
protection group to a specified Data Domain system. You then select a method for
vProxy selection, either auto where NetWorker chooses the proxy for backups, or
manual where you provide the name of the vProxy host to be used. Also, the media
pool for the backup data must contain a NetWorker Data Domain device.
If it is desired to have a clone action in the workflow, you can clone the backup data
to another Data Domain device or to a tape or AFTD device. Multiple clone actions
are supported, and they must occur after the backup action.

Configure Backup and Clone Workflow - Backup Optimization
Overview
NetWorker supports two types of backup optimization modes for vProxy backup to
Data Domain systems—Optimized for Capacity, and Optimized for Performance.
You can apply the optimization mode to vProxy protection groups during backup.
The Optimized for Capacity mode uses variable size segmentation, which produces
more overhead in data processing due to the higher deduplication rate, but reduces
the capacity that is consumed on the Data Domain system. Virtual machines
backed up prior to NetWorker 9.1 use the Optimized for Capacity mode.
Optimized for Performance provides performance improvements when you back up

virtual machines using Changed Block Tracking (CBT) and replicate data to a Data
Domain system, and is particularly effective when backing up large VMDK files.
Although Optimized for Performance results in extra space use on the Data
Domain device, around 20%, this mode significantly improves random I/O
performance for instant access restores.
New and upgraded installations of NetWorker use the Optimized for Capacity mode
by default. For a vProxy protection group, you can change this setting to Optimized
for Performance by using NMC, nsradmin, or nsrpolicy. The figure that is shown on
slide displays the backup optimization setting within a vProxy protection group in
NMC.

Using Optimized for Performance requires DDOS version 5.7.x or version 6.0.0.30
and later. If using a DDOS 5.7 version, DDOS 5.7.1 or later is recommended for
this mode. When you request Optimized for Performance mode but it is not
supported by the DDOS version, the backup automatically falls back to using
Optimized for Capacity. A warning log message is generated. Also, cloning of
Optimized for Performance save sets is supported only between DDOS platforms
that natively support this mode (DDOS version 5.7 and later).

Configure Backup and Clone Workflow - Change Optimization
Overview
Changing a virtual machine from one backup optimization mode to another (for
example, from Optimized for Capacity to Optimized for Performance) requires
performing a new full level-zero backup as the starting point for subsequent
backups. Ensure that the Data Domain device has sufficient capacity. Since
backups for each optimization mode must coexist during this period, backups will
consume twice the usual storage capacity until the last Optimized for Capacity
backup expires, as defined by the retention period. After this, storage consumption
will return to normal.

Configure Backup and Clone Workflow - Create a Rule
Overview
When you create or edit a VMware protection group, enabling the Dynamic
Association option for the group will enable you to assign rules. Rules can be used
to determine which virtual machines and containers will be protected by the group
in addition to any objects that have been manually selected for inclusion. You can
use the NMC NetWorker Administration window or the NetWorker Management
Web user interface to create rules and assign rules to a group. These operations
are not supported from the command line or the vCenter plug-in.
A VMware group with Dynamic Association enabled can include both static and
dynamic objects. Virtual machines and containers from the vCenter that are
manually selected when you create or edit the group in NMC are known as static
objects, because their inclusion in the group does not change unless you unselect
an item. Virtual machines and containers that are only included in the group
according to the rules assigned when you create or edit the group in NMC are
known as dynamic objects, because their inclusion in the group can change over
time based on whether the items continue to match the rule criteria.
When creating or editing the group, you can preview both static and dynamic
contents to ensure that the protection policy will include all the virtual machines and
containers that you want protect in the backup. Also, you can specify a virtual

machine exclusion list for the VMware protection group to exclude particular virtual
machines or VMDKs from being backed up as part of the group.
When a VMware protection group is associated with one or more rules, the rules
are executed against the vCenter inventory when the policy backup is started in
order to filter the group contents according to the rule criteria.
Rules can only be applied to VMware groups in NMC when you enable the
Dynamic Association option. When a group is enabled with Dynamic Association,
rules are executed against the vCenter inventory to determine which VMware
objects will be dynamically added to the VMware protection group's contents,
based on matching the rule criteria.

Perform Image-Level Recovery
Overview
Image-level recoveries are initiated using the Recover wizard in NetWorker

Administration. Select the option for Virtual Machine Recovery and you will be
prompted for the vCenter and one or more source virtual machines to recover from.
After selecting a recovery method, the subsequent wizard pages will reflect the
options pertaining to that specific recovery method. When selecting a virtual
machine recovery, you can perform a recovery of individual virtual machines or
recover from multiple virtual machines for the Revert and Virtual Machine recovery
methods.

Virtual Machine Recovery Methods
Overview
With NetWorker VMware Protection image level recovery, you can recover full
virtual machines and VMDKs. Recovery is controlled by nsrproxy_recover that
makes a direct request to a vProxy based on supplied arguments.
nsrproxy_recover can also be run from CLI.
Recovery can be performed from the original backup or a clone copy. If a clone is
not on a Data Domain device, recovery will first recall the data to a Data Domain
device and then perform the recovery. Retention of the recalled data is 1 day.
Recovery can be from an individual virtual machine or multiple virtual machines.
Recovery across vCenters is supported. Supported recovery types or methods
include the followings.
Revert, or rollback, a virtual machine, which restores an existing virtual machine

to a previous state. The restore replaces blocks that have changed since the
backup was performed.
Instant recovery or instant access, this type of recovery creates a new virtual
machine running directly off the backup image without performing any data
movement. The vProxy mounts the backup on a temporary NFS datastore, and the
virtual machine is immediately available. The recovery does not alter the backup

image that is saved in NetWorker. The copy is destroyed when the session is
deleted by the user.
Virtual machine recovery, which is a virtual machine recovery that recovers the
selected virtual machine as a new virtual machine.
Virtual disk recovery, with this type of recovery, also known as a VMDK recovery,
the user can recover one or more disks to an existing virtual machine.
Emergency recovery, an emergency recovery recovers a selected virtual machine

to an ESX host. This type of recovery is intended for use when vCenter is not
available.
File level recovery, with file level recovery, you can recover individual files from
backups of virtual machines or VMDKs to a primary or secondary vCenter server,
and for application-consistent backups, you can also restore the transaction log
from Data Domain to the SQL database. NetWorker only supports file level
recovery operations from a primary or cloned backup if the save set is on a Data
Domain device. If a cloned backup does not exist on the Data Domain device, you
must manually clone a save set from the tape device to Data Domain before
launching the Recovery wizard. For the Data Domain resource, ensure that you
provide the management credentials and, if required, type the export path
appropriately.
Also, if recovering to a virtual machine on a secondary vCenter using file level

recovery, ensure that a vProxy appliance has been deployed on the secondary
vCenter server and configured with the NetWorker server.

Perform File Level Recovery
Overview
You can perform File-level recovery in the following ways:
 In the NetWorker Management Web UI

 In the NMC or the Dell EMC Data Protection Restore Client
To perform a file-level recovery in the NetWorker Management Web UI, select File
Level to recover individual files from backups of virtual machines or VMDKs to a
primary or secondary vCenter server; to perform a file-level restore as a domain
user in the NMC NetWorker Administration window's Recovery wizard or the Dell
EMC Data Protection Restore Client, you need to register a tenant user and
provide the FLR Domain user Permissions before performing the recovery.

Perform File-Level Restore with Web Browser
Overview
With a file-level restore, you restore selected files and folders from virtual machines
using the Dell EMC Data Protection Restore Client which is accessed through a
web browser. There are two types of supported restores: Admin and User.
The Dell EMC Data Protection Restore Client enables you to restore specific files
and folders from virtual machines in User and Admin modes, and also restore
individual SQL databases from SQL server application-aware backups. The Dell
EMC Data Protection Restore Client is part of the NetWorker client installation.
To perform a file-level restore as a domain user in the NMC NetWorker

Administration window's Recovery wizard or the Dell EMC Data Protection Restore
Client, you need to register a tenant user and provide the FLR Domain user
Permissions before performing the recovery operation. A NetWorker user group,
VMware FLR Users, is used to provide the necessary NetWorker privileges for
User and Admin users for file-level restore operations. FLR privilege requirements
for User and Admin include remote access all clients, operate NetWorker, monitor
NetWorker, operate devices and jukeboxes, recover local data and backup local
data. Admin has an extra privilege of view security settings. Select folders and files
can be restored to the original virtual machine using the User mode for items that
the user has the required access permissions. To restore specific folders or files to
a virtual machine from a different source virtual machine, select the Admin mode.

See Dell EMC NetWorker 18.2 Vmware Integration Guide for more detail about
how to register a tenant user and provide the FLR domain user permission.
For file-level recovery of high-density file systems (more than few hundred
files/folders), Dell EMC recommends to use either the NetWorker Management
Web UI or the Dell EMC Data Protection Restore Client (User or Admin mode, as
applicable) instead of the NMC Recovery wizard.

Perform File-Level Restore with Recover Wizard
Overview
A file-level restore can also be initiated from the NetWorker Administration Recover
wizard. From the list of recovery methods choose File Level Recovery and proceed
through the wizard to specify the virtual machine to recover and the host to mount
the saveset. Just like the web-based FLR, the FLR agent must be installed.
Credentials for the mount host will be needed to install the agent. There is an
option to keep or remove the agent once the recovery is complete. Browse the
mounted filesystem to locate the files to recover and specify a restore location on
the mount host. The recovery can be monitored in NMC.

vSphere Web Client VM Backup and Recovery Plug-in
Overview
You can also use VMware View in NMC to install either the HMTL5 or flash-based
vCenter plug-in to enable virtual machine backup and recovery in the vSphere
Client or vSphere Web Client. Recoveries may be performed to the original virtual
machine or to a new virtual machine.
After the VMware vCenter is discovered in NetWorker, install the plug-in by right
clicking VMware View in the Protection window and choosing Install vCenter
Plugin. NetWorker shows a success message. Log in to the vSphere web client
and find Dell EMC NetWorker in the left pane. Select it and enter the NetWorker
server information to establish a connection to the NetWorker server. Once a
connection to the NetWorker server is established, go to Administration in the left
pane, and then you see the installed plug-ins.

vProxy Restore from VMware Backup Appliance Backups
Overview
If you have VMware Backup appliance (VBA) backups from previous Networker
releases, you can recover those backups from the NetWorker Management Web UI
by using the vProxy. Running VBA backups in NetWorker 18.2 is not supported.
You can only perform image-level recoveries of legacy VBA backups (the Revert or
New Virtual Machine recovery types). Other types of recovery are not supported
using the NetWorker Management Web UI. You can, however, use the EMC
Backup and Recovery plug-in within the vSphere Web Client for other types of VBA
recovery, provided that you still have an active VBA instance. For the recovery of
VBA backups, the staging pool must be a clone pool of type Data Domain. The
procedure of recovering data from VMware Backup Appliance backups is as
following.
 In the NetWorker Management Web UI, go to Recover > VMware Recovery.

The VMware Recovery window is displayed.
 From the Select vCenter drop-down, select a vCenter server. A list of virtual
machines in the vCenter displays.
 Select the desired virtual machine, and then select one of the duration options
from the Showing results for drop-down in the Backups and Clones pane. A list
of primary and clone backups of the virtual machine that is performed within that
duration appear in a table within the Backups and Clones pane. The table

contains a column that enables you to identify which backups are legacy VBA
backups.
 Click the filter icon in the lower left corner of the Backups and Clones pane,
and select VBA Backups and click OK. A column is displayed in the table that
enables you to identify which backups are legacy VBA backups.
 Select one of the available primary or cloned backups that indicates VBA, and
then click the Recovery drop-down.
 From the drop-down, select Image Level, and then select the Revert or New
Virtual Machine recovery type. These are the only supported types for
recoveries of VBA backups. The Recover wizard launches.
 Complete the Recover wizard according to the type you selected.
When you select the staging pool for recovery, ensure that at least one volume
does not contain a copy of the selected save set. Alternatively, if a save set is
already recovered, and then you can select the recovered save set for further
recoveries of the same virtual machine.
Note: When the recovery is initiated, the vProxy performs resurrection

on a staging pool to convert the VBA backups to a vProxy-readable
format, and then restores the virtual machine. Note that the staging
pool should reside on a Data Domain system.

Summary
Summary

NetWorker+Integration+Workshop VMware

Uploaded by

Copyright:

Available Formats

NetWorker+Integration+Workshop VMware

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+Integration+Workshop VMware

Uploaded by

Copyright:

Available Formats

NetWorker Integration with VMware

Upon completing this module, you will be able to:

NetWorker Integration Workshop_FINAL

Page 432 © Copyright 2019 Dell Inc.

VMware Data Protection Fundamentals

This lesson covers the fundamentals of data protection in a VMware environment,

This lesson covers the following topics:

NetWorker Integration Workshop_FINAL

© Copyright 2019 Dell Inc. Page 433

 Run multiple operating systems on a single physical machine simultaneously

NetWorker Integration Workshop_FINAL

Page 434 © Copyright 2019 Dell Inc.

Virtual Machine is a software computer that, like a physical computer, runs an

NetWorker Integration Workshop_FINAL

© Copyright 2019 Dell Inc. Page 435

vSphere 6.7 Features

With vSphere Persistent Memory, customers using supported hardware modules,

NetWorker Integration Workshop_FINAL

Page 436 © Copyright 2019 Dell Inc.

Another new capability being introduced in vSphere 6.7 is Instant Clone. It

NetWorker Integration Workshop_FINAL

© Copyright 2019 Dell Inc. Page 437

VMware Backup Challenges

Virtual server backups can be accomplished using a traditional approach with

NetWorker Integration Workshop_FINAL

Page 438 © Copyright 2019 Dell Inc.

Backup processes must evolve to deliver greater efficiencies in a highly

NetWorker Integration Workshop_FINAL

© Copyright 2019 Dell Inc. Page 439

Simplifying VMware Backups with vProxy

NetWorker Integration Workshop_FINAL

Page 440 © Copyright 2019 Dell Inc.

NetWorker VMware Protection Solution with vProxy Appliance

Uses stand-alone data-mover proxy appliances, or vProxy appliances, to backup

Provides user interfaces to perform image-level recovery or file-level recovery.

NetWorker Integration Workshop_FINAL

© Copyright 2019 Dell Inc. Page 441

NetWorker VMware Protection with vProxy Appliance

The diagram that is shown on slide provides a high-level overview of the

NetWorker server — Provides the ability to manage vProxy appliances, configure

NetWorker Integration Workshop_FINAL

Page 442 © Copyright 2019 Dell Inc.

NetWorker VMware Protection Solution

NetWorker Integration Workshop_FINAL

© Copyright 2019 Dell Inc. Page 443

NetWorker VMware Protection Solution Port Requirement

NetWorker Integration Workshop_FINAL

Page 444 © Copyright 2019 Dell Inc.

NetWorker VMware Protection Solution Port Requirement

NetWorker Integration Workshop_FINAL

© Copyright 2019 Dell Inc. Page 445

Processing Backups with the NVP vProxy Solution

There is an action binary, nsrvproxy_save. This binary is a multi-threaded process

NetWorker Integration Workshop_FINAL

Page 446 © Copyright 2019 Dell Inc.

incremental backups based on previous backups residing in backup or clone

NetWorker Integration Workshop_FINAL

© Copyright 2019 Dell Inc. Page 447

NetWorker VMware Protection Solution Considerations