EMC VIPR SRM: VAPP BACKUP AND RESTORE USING EMC ® NETWORKER ®
This white paper provides a working example of how to back up and restore an EMC ViPR SRM vApp using EMC NetWorker.
To learn more about how EMC products, services, and solutions can help solve your business and IT challenges, contact your local representative or authorized reseller, visit www.emc.com, or explore and compare products in the EMC Store
Copyright © 2015 EMC Corporation. All Rights Reserved.
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.
For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.
VMware and vCenter are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other trademarks used herein are the property of their respective owners.
Part Number H14571
TABLE OF CONTENTS
EXECUTIVE SUMMARY ... 4
AUDIENCE ... 4
INTRODUCTION ... 4
Terminology ... 4
Prerequisites ... 5
VIPR SRM PRE-BACKUP CHECKS ... 5
BACKUP AND RESTORE PROCEDURES ... 5
Registering vCenter with NetWorker Appliance ... 5
Backing up the SRM vApp Using the NetWorker Management Console ... 5
Accessing VMware Protection in NMC ... 5
VMware Backup Appliance in NMC ... 7
VMware Protection Policies in NMC ... 7
Setup and configure policies in NMC ... 8
VMware View in NMC ... 11
Assigning policies within VMware View ... 12
Starting a policy manually from the NMC Monitoring window ... 12
Stopping a policy from the NMC Monitoring window ... 12
Viewing policy progress from the NMC Monitoring window ... 12
Managing the VMware Environment Using the vSphere Web Client ... 12
Connecting to EMC Backup and Recovery in the vSphere Web Client ... 12
Assigning VMs to a policy ... 13
Manually starting the backup policy using Backup Now ... 14
Viewing policy progress in the vSphere Web Client ... 15
Restoring the SRM vApp Using NetWorker ... 16
FULLVM (Image-level) Restore ... 16
Performing a FULLVM restore ... 16
File backup and restore of ViPR SRM VMs ... 20
Adding a SRM client and scheduling for file backup ... 20
Initiating file backup manually for ViPR SRM client ... 25
ViPR SRM File Restore ... 27
Validate Operational Status ... 31
This white paper provides a working example of how to use EMC® NetWorker® software, version 8.2 to provide a backup and restore capability for a EMC ViPR SRM vApp deployment. While this document specifically covers ViPR SRM vApp deployments, the guidelines apply to larger deployments as well. For information related to NetWorker installation and administration, refer to NetWorker documentation on the EMC Online Support site. Alternatively, you can perform a Web search to obtain the appropriate NetWorker documentation.
EMC ViPR SRM is a software solution that provides multi-vendor capacity, performance, and configuration dashboards and reports for traditional and software-defined storage resources. ViPR SRM leverages state-of-the-art visibility and forecasting from various devices and technologies processing and storing millions of indicators. When designing a ViPR SRM solution it should be taken into consideration how to avoid common availability pitfalls and in the case of a failure how to gracefully reestablish the services to maintain consistency and performance. This white paper is applicable to all current versions of ViPR SRM.
Backups have two distinct purposes. The primary purpose is to recover data after its loss, be it by data deletion or corruption. The secondary purpose of backups is to recover data from an earlier time, according to a user-defined data retention policy, typically configured within a backup application for how long copies of data are required. This white paper will provide general guidelines on how to perform backup for your existing ViPR SRM deployment using EMC NetWorker. Once established, you should periodically test data restoration to ensure backup works as intended to prepare your organization for when a disaster actually occurs and you need to recover data quickly.
This white paper is intended for system administrators, solution architects, system implementers, support and EMC Partners who are responsible for the setup and maintenance of EMC NetWorker software used to backup and restore data for a ViPR SRM vApp deployment. Readers should have a working knowledge of ViPR SRM and EMC NetWorker.
Backup Policy The methods, procedures, policies and rules that are used as guidelines to safeguard data. Typically involves detailed information on how a backup should proceed, what systems should the data be saved to, schedule for a backup window and to what sort of media and destination a backup should be delivered.
Backup Window The time period required to finish a backup process.
Recovery Point Objective Recovery Point Objective (RPO) is the maximum amount of data that an organization can tolerate to lose.
Recovery Time Objective After a service disruption, the Recovery Time Objective (RTO) is the maximum period of time a business or process can endure for restoring data accesses.
Snapshots A snapshot is the state of a system in a specific point in time. In a virtual environment, this could mean the state and data of a virtual machine, including the files that make the virtual machine disk and information about the state of the virtual machine (i.e.:
powered off or powered on).
Review the following prerequisites:
• EMC NetWorker is installed.
• NetWorker Server and Proxy Servers should be reachable from the ViPR SRM vApp appliances.
• Reverse DNS lookup should work between all hosts participating in backup and restore.
• The data store should have enough space to hold backup images. Space can be allocated based on backup frequency and the type of backup policy configured.
• The NetWorker Client should be installed on the target backup hosts/Proxy for file backup.
• Ensure that the NetWorker daemon processes are running on all associated hosts.
• Firewalls should be turned off to avoid connection errors. All firewall ports between the networker processes on backup client/server/Proxy should be configured to ensure connectivity. Refer to NetWorker documentation – specifically the EMC NetWorker 8.2 SP1 Security Guide.
VIPR SRM PRE-BACKUP CHECKS
Do the following:
• Verify and document the current environment before starting the backup process.
• Refer to EMC documentation on managing ViPR SRM system health for details about verifying the health of your system.
• Look for blank reports and graphs. Determine if there are any blank reports caused by collection errors. Resolve any issues or document them for later follow up.
• Look for broken links. Resolve any issues or document them for later follow up.
• Validate that the end-to-end topology is working. Resolve any issues found.
BACKUP AND RESTORE PROCEDURES
REGISTERING VCENTER WITH NETWORKER APPLIANCE
1. From a web browser, type:
2. The EMC Backup and Recovery Configure window displays.
3. Click the Configuration tab and unlock the vCenter registration.
4. Provide the appropriate credentials and vCenter details, and then save and reboot the appliance.
BACKING UP THE SRM VAPP USING THE NETWORKER MANAGEMENT CONSOLE
You can create VMware protection policies and assign VMs, VMDKs and so on to the policies for backup and recovery using the NetWorker Management Console (NMC). NMC is the user interface for the NetWorker Console server.
Accessing VMware Protection in NMC
When you connect to the NMC server, the Console window appears. To access the VMware Protection solution in NMC:
1. On the Enterprise tab, select the appropriate server.
2. Right-click on the server in the left pane of the Console window, and select Launch Application. The Administration window displays.
3. You can access most of the options for the VMware Protection solution by selecting the Configuration tab, as shown in the following figure.
VMware Backup Appliance in NMC
When you select VMware Backup Appliances, the available VMware Backup Appliances display in the right pane. From the right-pane, you can monitor the state (offline/online) of the VMware Backup Appliance, as shown in the following figure.
VMware Protection Policies in NMC
When you expand VMware Protection Policies, NMC displays the default policy, which gets created after NetWorker registers the first VMware Backup Appliance. The following figure displays the Default VMware Protection policy.
NetWorker automatically applies the default VMware Protection policy to all VMware Backup Appliances after you register the first appliance, and enables the policy to run once every 24 hours starting at 21:00. NetWorker saves the backups created by this policy
on the internal storage of the appliance. The backup level used is determined by the levels defined in the Default schedule, and a one month data retention policy is used.
Setup and configure policies in NMC
You may require more than one policy to back up the VMs in your environment. For example, there may be VMs you want to protect based on retention, how many clones you need, and so on. To create a new protection policy:
1. On the Configuration tab of the NMC Administration window, right-click VMware Protection Policies in the left pane and select New, as shown in the following figure.
2. On the Definition tab of the Create VMware Policy window, type a descriptive name for the policy, and specify a Start Time and Interval. NetWorker provides default values in these fields. In the following figure, a policy named
BackuptoDDRandClone is being created to backup and clone VMs to a Data Domain system.
Note: Autostart is enabled by default.
3. To create the VMware action (for example, action type=VMware backup), click the New button in the VMware Actions pane.
The following page displays.
4. Repeat the following steps for each action type:
o Type a name that describes the action.
o In the Action type field, select the action type.
o Select the type of VMware backup:
- Select Virtual Machine to back up VMs only. This is the default selection. When you select this backup type, VMware View will display contents down to the VM level.
- Select VMDK to back up individual virtual disk files, which store the contents of the virtual machine's hard disk drive. When you select this backup type, VMware View will display contents down to the VMDK level.
o Choose a destination pool:
- For VBA checkpoint backup, select the Data Domain backup pool.
- For VMware backup actions, select Default Pool VBA Internal to backup to internal storage, or the Data Domain backup pool to backup to a Data Domain device.
o For clone actions, select the pool for your created Data Domain device, or a clone pool containing tapes for cloning to tape. When you select the pool for the Data Domain device, the VMware backup occurs to the Data Domain device instead of VBA internal storage. For example, to create the BackuptoDDRandClone policy, the Data Domain device requires a backup pool, because you cannot clone a backup to Default Pool VBA Internal.
o Select a retention policy for Index Management, or use the default value.
- On the Schedule tab, NetWorker uses the default VMware Incremental Forever schedule. You can use the default schedule, select an alternate schedule from the drop-down, or click the green + to create a new schedule or edit a schedule.
When you click OK to create the VMware backup action, the Create/Edit VMware Protection Policy window displays again, with the new action in the VMware Actions pane, along with all of the policy details. You must now assign a VMware Backup Appliance to the policy.
5. In the Create/Edit VMware Protection Policy window, select an appliance on the VMware Backup Appliance Selection tab, as shown in the following figure, and then click OK.
When you complete these steps, the following page displays, showing the completed VMware Protection Policy and associated actions. A map also appears at the bottom of the window displaying a visual representation of the policy and actions.
To avoid waiting until all backups complete before the clone action begins, you can choose to make the operations concurrent, similar to NetWorker’s immediate cloning option which allows a group to start cloning upon each save set completion. To enable and mark actions to run concurrently with their preceding actions, open the Create VMware Policy or Edit VMware Protection Policy window, and then select the appropriate checkboxes under the Definition tab, as shown in the following figure.
Once you create the policy and complete the Actions, select the VMware backup appliance that the policy applies by selecting the VMware Backup Appliance Selection tab, available from the Create VMware Policy or Edit VMware Protection Policy windows.
VMware View in NMC
After detecting VMware environments, the NetWorker console provides a visual representation of these environments when you select VMware View in the left pane of the NMC Configuration window. Using VMware View, you can also assign the policies you created in “Setup and configure policies in NMC”.
You can refine items displayed in the right details pane by selecting containers in the Virtualization node hierarchy in the left pane. For example, if an individual Cluster is selected in the Virtualization node, only child elements associated with that Cluster display.
Assigning policies within VMware View
Right-click on any container, or expand the container and right-click on an element within VMware View.
Select Add Policy-VBA. The available policies display, as shown in the following figure.
When you select a policy, VMware View refreshes and displays the new association.
To assign a policy at the VMDK level, expand a VM and highlight the VMDK(s) you want to associate to the policy, and then right- click and select Add Policy-VBA. Ensure that you select a policy that has been specifically configured to back up VMDKs using the backup type option specified in the section “Setup and configure policies in NMC”.
Starting a policy manually from the NMC Monitoring window
You can manually start a VMware Protection policy by right-clicking the policy in the Groups and Policies section on the Monitoring window and selecting Start. Otherwise, wait for NetWorker to start the backup policy based on the scheduled start time.
Stopping a policy from the NMC Monitoring window
To cancel a policy in NMC, right-click the backup policy in the Groups and Policies section on the NMC Monitoring window and select the Stop option.
Viewing policy progress from the NMC Monitoring window
You can view the progress of a policy in the Policy Details dialog box, which appears when you double-click the policy in the Groups and Policies section on the Monitoring window. NetWorker displays the session progress for a policy in the All Sessions section on the NMC Monitoring window. You can view NMC Reports for completed policies on the Reports tab by selecting NetWorker Data Protection Policy reports.
MANAGING THE VMWARE ENVIRONMENT USING THE VSPHERE WEB CLIENT
The vSphere Web Client provides access to the EMC Backup and Recovery user interface. The EMC Backup and Recovery user interface functions as a plug-in within the vSphere Web Client that connects to the EMC Backup and Recovery appliance, allowing you to perform several operations including assigning VMs/VMDKs to policies created in NMC
Connecting to EMC Backup and Recovery in the vSphere Web Client
1. From a web browser, open the vSphere Web Client: https://IP_address_vCenter_Server:9443/vsphere-client/
2. In the Credentials window, type the vCenter user name and password for the dedicated EMC Backup and Recovery user you created and then click Login.
3. In the vSphere Web Client, select EMC Backup and Recovery.
4. In the Welcome to EMC Backup and Recovery window, select a Backup Appliance from the drop-down. The drop-down lists all the EMC Backup and Recovery appliances registered in the vCenter.
Each vCenter Server supports up to 10 EMC Backup and Recovery appliances. The EBR Appliance field, as shown in the following figure, displays the appliance names alphabetically in a drop-down list. In the EMC Backup and Recovery user interface, the name of the active appliance displays on the left pane, and the appliance name in the drop-down list is the first in the list of available appliances.
5. Click Connect.
Assigning VMs to a policy
You can assign collections of VMs (such as all VMs in a datacenter), individual VMs, and VMDKs to be included in a policy backup using the EMC Backup and Recovery user interface in the vSphere Web Client. If you select an entire resource pool, host, datacenter, or folder, any new VMs in that container are included in subsequent backups. If you select a VM, then any disk added to the VM is included in the backup. If you move the VM from the selected container to another unselected container, then the VM is no longer part of the backup. You can also manually select a VM to be backed up, which ensures that NetWorker backs up the VM, even when you move the VM.
1. Select EMC Backup and Recovery in the vSphere Web Client.
2. On the Getting Started tab, select Assign Backup Policies. The Backup tab displays, which shows the available policies in upper half of the window, and the Backup Policy Details in the lower half.
The policy description matches the description in NMC (for example, Default). Backup to internal disk means that any VMs you assign to this default policy will go to the storage of the deployed EMC Backup and Recovery appliance. When you perform backups to the internal storage of an EMC Backup and Recovery appliance, these details appear in NMC and as part of the policy description in EMC Backup and Recovery in vCenter.
3. Click Edit. All the VMs in the vCenter display.
4. Use the checkboxes next to the VMs to select the VMs that you want to include in the selected policy, as shown in the following figure.
5. Click Finish. A dialog box displays to indicate that the backup policy was saved successfully. To return at any time to the Backup Policy Details window and verify which VMs that you selected, click Edit. This information also appears in the lower half of the window, in the Show Items link next to the Sources field.
Manually starting the backup policy using Backup Now
You can manually start the backup policy in the EMC Backup and Recovery user interface by selecting Backup Now in one of the following ways:
• Click Backup Now on the EMC Backup and Recovery user interface’s Backup tab. Two options display:
• Backup all sources
• Backup only out of date sources
• Right-click individual VMs in vCenter and select Backup Now.
Otherwise, you can wait for NetWorker to start the backup policy based on the scheduled start time.
Viewing policy progress in the vSphere Web Client
To view the progress for a backup policy, select Tasks in the left pane of the vSphere Web Client.
The Task Console displays, as shown in the following figure.
After the backup completes, you can recover the backed up VMs in the vSphere Web Client or perform a file-level restore by using the EMC Data Protection Restore Client.
RESTORING THE SRM VAPP USING NETWORKER
A FULLVM (image-level) restore will restore an entire backup image or selected drives to the original VM, another existing VM, or a new VM. These restores are less resource intensive and are best used for restoring large amounts of data quickly.
FULLVM (Image-level) Restore
When the backup completes, you can restore full VMs by selecting either of the following options in the EMC Backup and Recovery user interface:
• Click Restore Backup on the Getting Started tab.
• Select the Restore tab.
When you select the Restore tab, available VMs appear, as shown in the following figure. For every clone, a backup is listed under the restore point.
The following sections describe FULLVM restore options.
Performing a FULLVM restore To perform a full restore:
1. Power off each VM that you want to restore.
2. On the Restore tab, expand the VM that you want to restore. You can filter by using the Filter drop-down to show a specific VM and related items. You can also browse to the VMDK level and select a single VMDK for restore if you only want to restore that disk.
3. Select a restore point and click Restore. The Restore backup wizard launches.
4. On the Select Backup page, select the correct restore point (the wizard displays all restore points for the backup by date and time). Typically, you only select one restore point at a time. Click Next.
5. On the Set Restore Options page, specify where you want to restore the backup:
o Restore to Original Location — when you select Restore to Original Location, then the backup restores to its original location. If the VMDK file still exists at the original location, then the restore process overwrites the file.
o Restore to New Location — when you unselect Restore to Original Location, then you can specify a new location (new Name, destination, and datastore) where the VM/VMDK will be restored.
6. On the Ready to complete page, verify the selections. The wizard displays a summary of the number of machines that will be replaced (restore to the original location) and the number of machines that will be created (restore to a new location).
7. To change any of the settings for your restore request, either use the Back button to return to the appropriate screen, or click on the appropriate numbered step title to the left of the wizard. If the settings are correct, click Finish. If the settings are not correct, then click Back to go back to create the correct configuration. The Restore wizard displays a message that
the restore process initiated successfully. Click OK. You can monitor the Restore progress by using the Recent Tasks pane.
When the recovery starts, a recovery session also displays in NMC. Any activities that occur on the vCenter side are visible on the NMC side (in the log section).
FILE BACKUP AND RESTORE OF VIPR SRM VMS
Adding a SRM client and scheduling for file backup
To create a file backup and restore, agent must be installed on the client intended to backup.
1. Right click on client, and select New Client Wizard.
2. Provide the client name, select the appropriate option and click Next.
3. Verify the client details shown on the wizard and click Next.
4. Provide the appropriate information based on your installation type, and click Next.
5. Complete folder structure will be displayed to choose files/directories for backup. You can expand to subfolders by clicking on + signs.
6. Select/create the retention, backup policy and schedule based on your requirements. Provide the Comments and Remote access details if required.
7. Add the client to an existing group or create a new group, depending on your requirements.
8. Choose the Backup Storage Node based on your networker configuration.
9. Verify the results and create the client for backup.
Initiating file backup manually for ViPR SRM client
1. Browse to the Groups node in the left pane and expand for list of groups.
2. Right click on the Group name and select Start option to initiate manual backup of that group.
3. You can monitor the progress of backup under Monitoring tab.
ViPR SRM File Restore
File-level restores will restores specific folders or files from a file backup. These restores are more resource intensive and are best used to restore relatively small amounts of data.
1. Selecting Clients node in the left pane populates client list in the right.
2. Right-click on the client name and click Recover to restore the backup files.
3. Verify the backup details and choose the Destination host. In the case of a different host provide the new host name.
4. Choose the backup set and file/directory for restore.
5. Choose the destination path for restore and options as required.
6. Choose an option to proceed with restore.
7. Provide a recovery name and Schedule/Start the restore of selected File/Directory.
8. Monitor the progress in the log view. You can also cancel the operation.
VALIDATE OPERATIONAL STATUS
Do the following:
• Ensure that the VIPR SRM VM launches successfully with all of the APG services in a running state.
• Look for broken links. Resolve issues or document them for later follow up.
• Validate that the end-to-end topology is working. Resolve any issues.