Agent EMC ProtectPoint File System · PDF filel EMC Data Domain Expansion Shelf Hardware Guide...

EMC® ProtectPoint™ File SystemAgentVersion 3.1

Installation and Administration Guide302-001-921

REV 03

Copyright © 2014-2016 EMC Corporation. All rights reserved. Published in the USA.

Published June 2016

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind withrespect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for aparticular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and othercountries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

EMC CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.EMC.com

2 EMC ProtectPoint File System Agent 3.1 Installation and Administration Guide

Preface 7

Revision History 11

EMC ProtectPoint Storage Configuration Overview 13

EMC ProtectPoint documentation set.............................................................14ProtectPoint file system agent....................................................................... 15Host considerations...................................................................................... 16

ProtectPoint File System Agent for VMAX 17

ProtectPoint with VMAX overview.................................................................. 18Basic backup workflow.................................................................... 21Basic restore workflow..................................................................... 22

ProtectPoint environment..............................................................................25Additional Information..................................................................... 25ProtectPoint with Symmetrix Remote Data Facility (SRDF)................. 25

ProtectPoint prerequisites............................................................................. 25Data Domain block services for ProtectPoint prerequisites............... 26ProtectPoint file system agent prerequisites.....................................29

ProtectPoint file system agent setup overview............................................... 29

Setting Up the ProtectPoint File System Agent for VMAX on Linux orUNIX hosts 31

Setting up the ProtectPoint file system agent with VMAX............................... 32Installing the ProtectPoint file system agent on a Linux or UNIX host..............33Modifying the ProtectPoint configuration file................................................. 33Verify the ProtectPoint installation................................................................ 42

Setting Up the ProtectPoint File System Agent for VMAX on Windowshosts 45

Setting up the ProtectPoint file system agent with VMAX............................... 46Installing the ProtectPoint file system agent on a Windows host.................... 47Modifying the ProtectPoint configuration file................................................. 48Verify the ProtectPoint installation................................................................ 56

ProtectPoint File System Agent for RecoverPoint 59

ProtectPoint with RecoverPoint overview....................................................... 60Basic backup workflow.................................................................... 62Basic restore workflow..................................................................... 63

ProtectPoint with RecoverPoint environment................................................. 64ProtectPoint prerequisites............................................................................. 65

Data Domain block services for ProtectPoint prerequisites............... 66ProtectPoint file system agent prerequisites.....................................68

Chapter 1

Chapter 2

Chapter 3

Chapter 4

Chapter 5

CONTENTS

EMC ProtectPoint File System Agent 3.1 Installation and Administration Guide 3

Setting Up the ProtectPoint File System Agent for RecoverPoint onLinux or UNIX Hosts 71

Setting up the ProtectPoint file system agent with RecoverPoint.................... 72Installing the ProtectPoint file system agent on a Linux or UNIX host..............73Modifying the ProtectPoint configuration file................................................. 73Verify the ProtectPoint installation................................................................ 81

Setting Up the ProtectPoint File System Agent for RecoverPoint onWindows Hosts 83

Setting up the ProtectPoint file system agent with RecoverPoint.................... 84Installing the ProtectPoint file system agent on a Windows host.................... 85Modifying the ProtectPoint configuration file................................................. 86Verify the ProtectPoint installation................................................................ 93

ProtectPoint Administration 97

ProtectPoint administration overview............................................................ 98Application changes........................................................................ 98

ProtectPoint file system agent....................................................................... 98Specifying the ProtectPoint configuration file................................... 98Performing a backup of ProtectPoint with VMAX............................... 98Restoring a VMAX backup.............................................................. 100Performing a backup of ProtectPoint with RecoverPoint.................. 104Restoring a RecoverPoint backup................................................... 105Deleting a backup.......................................................................... 110Scanning for and displaying arbitrary ProtectPoint backups........... 111Rebuilding the ProtectPoint catalog................................................113Showing the ProtectPoint file system agent version........................113Upgrading the ProtectPoint file system agent................................. 114

Troubleshooting 117

ProtectPoint log file..................................................................................... 118Check connectivity in the ProtectPoint environment.................................... 118ProtectPoint troubleshooting scenarios.......................................................119

Failure of a host at the primary site................................................ 119Failure of host with a new host on the secondary site..................... 119Primary site failure (both primary and protection storage).............. 119Secondary site failure (both primary and protection storage)..........120Failure of primary storage at the production site.............................120Failure of primary storage at the secondary site..............................120Failure of protection storage at the production site.........................121Failure of protection storage at the secondary site..........................121

ProtectPoint Command Reference 123

protectpoint change history.........................................................................124ProtectPoint filesystem agent with VMAX command reference..................... 125

protectpoint guidelines and restrictions.........................................125protectpoint backup.......................................................................126protectpoint catalog.......................................................................128protectpoint config.........................................................................128protectpoint rollback......................................................................129protectpoint restore....................................................................... 129

Chapter 6

Chapter 7

Chapter 8

Chapter 9

Appendix A

CONTENTS


protectpoint security...................................................................... 130protectpoint show..........................................................................131protectpoint snapshot....................................................................131

ProtectPoint filesystem agent with RecoverPoint command reference..........131protectpoint guidelines and restrictions.........................................132protectpoint backup.......................................................................132protectpoint catalog.......................................................................134protectpoint config.........................................................................135protectpoint restore....................................................................... 135protectpoint rollback......................................................................136protectpoint security...................................................................... 136protectpoint show..........................................................................138protectpoint snapshot....................................................................138

CONTENTS

EMC ProtectPoint File System Agent 3.1 Installation and Administration Guide 5

CONTENTS


Preface

As part of an effort to improve its product lines, EMC periodically releases revisions of itssoftware and hardware. Therefore, some functions described in this document might notbe supported by all versions of the software or hardware currently in use. The productrelease notes provide the most up-to-date information on product features.

Contact your EMC technical support professional if a product does not function properlyor does not function as described in this document.

Note

This document was accurate at publication time. Go to EMC Online Support (https://support.emc.com) to ensure that you are using the latest version of this document.

PurposeThis guide explains how to install, configure, and administer the functionality available inthe EMC ProtectPoint solution. Use this administration guide in conjunction with thestorage configuration information documented in the EMC ProtectPoint Primary andProtection Storage Configuration Guide, the solution overview information documented inthe EMC ProtectPoint Solutions Guide, and the EMC commands documented in the EMCProtectPoint File System Agent Command Reference Guide.

Note

A command line interface (CLI) command may offer more options than those described inthis document. The EMC Data Domain Operating System Command Reference Guide and theEMC Solutions Enabler CLI Command Reference provide complete descriptions of thesupported commands and options.

AudienceThis guide is intended for system administrator-level or equivalent users who are familiarwith standard backup software packages and general backup administration.

Related documentationThe following EMC Data Domain system documents provide additional information:

l EMC Data Domain Installation and Setup Guide for the particular Data Domain system

l EMC Data Domain Operating System Release Notes

l EMC Data Domain Operating System Initial Configuration Guide

l EMC Data Domain Operating System Command Quick Reference

l EMC Data Domain Operating System Command Reference Guide

l EMC Data Domain Operating System Administration Guide

l EMC Data Domain Operating System MIB Quick Reference

l EMC Data Domain Operating System Offline Diagnostics Suite User's Guide

l Hardware overview guide for the system

l Field replacement guides for the system components

l EMC Data Domain System Controller Upgrade Guide

l EMC Data Domain Expansion Shelf Hardware Guide for shelf model ES20, ES30, or DS60

Preface 7

https://support.emc.com/

https://support.emc.com/

l EMC Data Domain Boost for OpenStorage Administration Guide

l EMC Data Domain Boost for OpenStorage Release Notes

l EMC Data Domain Boost for Oracle Recovery Manager Administration Guide

l EMC Data Domain Boost for Oracle Recovery Manager Release Notes

l EMC Data Domain Boost SDK Programmer's Guide

l Statement of Volatility for the system

If you have the optional RSA Data Protection (DPM) Key Manager, see the latest version ofthe RSA Data Protection Manager Server Administrator's Guide, available with the RSA KeyManager product.

The following VMAX system documents provide additional information:

l EMC Solutions Enabler TimeFinder Family CLI User Guide

l EMC Solutions Enabler V8.0.2 Array Management CLI User Guide

The following Data Domain Boost for Enterprise Applications and EMC ProtectPointdocuments provide additional information:

l EMC Data Domain Boost for Enterprise Applications and EMC ProtectPoint DatabaseApplication Agent Release 3.0 Installation and Administration Guide

l EMC Data Domain Boost for Enterprise Applications and EMC ProtectPoint MicrosoftApplication Agent Release 3.0 Installation and Administration Guide

Special notice conventions used in this documentEMC uses the following conventions for special notices:

NOTICE

Addresses practices not related to personal injury.

Note

Presents information that is important, but not hazard-related.

Typographical conventionsEMC uses the following type style conventions in this document:

Table 1 Typographical Conventions

Bold Indicates interface element names, such as names of windows, dialogboxes, buttons, fields, tab names, key names, and menu paths (whatthe user specifically selects or clicks)

Italic Highlights publication titles listed in text

Monospace Indicates system information, such as:

l System code

l System output, such as an error message or script

l Pathnames, filenames, prompts, and syntax

l Commands and options

Monospace italic Highlights a variable name that must be replaced with a variable value

Monospace bold Indicates text for user input

[ ] Square brackets enclose optional values

Preface


Table 1 Typographical Conventions (continued)

| Vertical bar indicates alternate selections—the bar means “or”

{ } Braces enclose content that the user must specify, such as x or y or z

... Ellipses indicate nonessential information omitted from the example

Where to get helpEMC support, product, and licensing information can be obtained as follows:

Product information

For documentation, release notes, software updates, or information about EMCproducts, go to EMC Online Support at https://support.emc.com.

Technical support

Go to EMC Online Support and click Service Center. You will see several options forcontacting EMC Technical Support. Note that to open a service request, you musthave a valid support agreement. Contact your EMC sales representative for detailsabout obtaining a valid support agreement or with questions about your account.

Your commentsYour suggestions will help us continue to improve the accuracy, organization, and overallquality of the user publications. Send your opinions of this document to [email protected].

Preface

9

https://support.emc.com

mailto:[email protected]

Preface


Revision History

Table 2 Document revision history

Revision Date Description

03 (3.1.0) June 2016 Updated for the release of ProtectPoint 3.1, whichincorporates the functionality of ProtectPoint 2.0 andProtectPoint 3.0 into a single software package.

02 (3.0.0) December 2015 Updated for the release of ProtectPoint 3.0.

01 (2.0.0) June 2015 This is the initial release of this document.

Revision History 11

Revision History


CHAPTER 1

EMC ProtectPoint Storage Configuration Overview

This chapter includes the following topics:

l EMC ProtectPoint documentation set.....................................................................14l ProtectPoint file system agent............................................................................... 15l Host considerations.............................................................................................. 16

EMC ProtectPoint Storage Configuration Overview 13

EMC ProtectPoint documentation setThe EMC® ProtectPoint™ documentation set contains multiple documents, each servinga distinct purpose. Familiarize yourself with the function and audience of each documentbefore proceeding.

The following figure shows the ProtectPoint documentation hierarchy.

Figure 1 ProtectPoint documentation hierarchy

The following table lists the ProtectPoint documents and describes the target audienceand function of each document.

Table 3 ProtectPoint documents

Document title Document function Audience

EMC ProtectPoint SolutionsGuide

Provides conceptual andoverview informationabout the ProtectPointsolution.

Application administrators, backupadministrators, storage administrators,and IT decision-makers looking forinformation about the ProtectPointsolution to determine if it is the right fitfor their environments. This document isrelevant for both the ProtectPoint filesystem agent and ProtectPointapplication agents.

EMC ProtectPoint Primaryand Protection StorageConfiguration Guide

Provides instructions toprovision the primary andprotection storage for aProtectPoint deployment.

Storage administrators who need toconfigure the primary and protectionstorage for the ProtectPointenvironment. This document is relevant



Table 3 ProtectPoint documents (continued)

Document title Document function Audience

for both the ProtectPoint file systemagent and ProtectPoint applicationagents.

EMC ProtectPoint FileSystem Agent Installationand Configuration Guide

Provides instructions toinstall and administer theProtectPoint file systemagent.

Application administrators who will beinstalling and using the ProtectPoint filesystem agent to create backups of theirapplications, manage the lifecycle of thebackups, optionally replicate thebackups to remote protection storage,and restore from the backups whennecessary.

EMC Data Domain Boost forEnterprise Applications andEMC ProtectPoint DatabaseApplication AgentInstallation andAdministration Guide

Provides instructions toinstall and administer theProtectPoint databaseapplication agent.

Application administrators anddatabase administrators who will beinstalling and using the ProtectPointdatabase application agent to createbackups of their applications, managethe lifecycle of the backups, optionallyreplicate the backups to remoteprotection storage, and restore from thebackups when necessary.

EMC Data Domain Boost forEnterprise Applications andEMC ProtectPoint MicrosoftApplication AgentInstallation andAdministration Guide

Provides instructions toinstall and administer theProtectPoint Microsoftapplication agent.

Application administrators anddatabase administrators who will beinstalling and using the ProtectPointMicrosoft application agent to createbackups of their applications, managethe lifecycle of the backups, optionallyreplicate the backups to remoteprotection storage, and restore from thebackups when necessary.

ProtectPoint file system agentThe ProtectPoint file system agent includes the following features:

l Provides a CLI that you can use to trigger the primary storage to EMC Data Domain®

workflow for backup and restore operations.

l Provides commands for lifecycle management of the backups.

l Triggers backup and restore operations on the primary storage system and DataDomain system through the use of primary storage system features and Data Domainblock services for ProtectPoint management libraries, respectively.

l Operates on the device level. ProtectPoint works with primary storage LUNs and DataDomain block services for ProtectPoint devices, not with file system objects.

You can use the ProtectPoint file system agent to complete the following tasks:

l Create a snapshot of the production application LUNs on the primary storage system.

l Trigger the movement of data created from the backups on the primary storagesystem to the Data Domain devices.


ProtectPoint file system agent 15

l Create a static-image for each LUN in the data set on the Data Domain system.

l Securely manage the credentials for the Data Domain systems and EMCRecoverPoint® cluster.

l Scan the Data Domain system for backups created by other ProtectPoint applicationsin addition to backups created by the file system agent.

l Manage the ProtectPoint backup and restore catalog.

l Manage the lifecycles of the data backups by listing and optionally deleting existingbackups.

l Show the ProtectPoint version number.

l Validate the content and format of the configuration files.

Configuration fileThe file system agent configuration file specifies information about the file system agent-protected environment, including the Data Domain name and username, the sourcedevices, the restore devices, and the relationships between these devices for both theprimary storage system, and primary and optional secondary Data Domain systems. Thefile system agent provides two template configuration files, one for ProtectPoint for EMCVMAX® environments and one for ProtectPoint for RecoverPoint environments. Select theenvironment-appropriate template and modify it as required.

When you set up the ProtectPoint file system agent on the application/recovery (AR) host,modify the configuration file to include the specific details about your devices. Make acopy of the configuration template file, and specify the environment information in thecopy.

Note

You can have any number of configuration files.

Host considerationsThe following host considerations can impact the ProtectPoint implementation:

l For FC multipathing, verify that enough FC ports are available on the primary storagesystem, the Data Domain system, and the FC switch.

Note

The number of paths required depends on the I/O load and the environmentperformance requirements.

l For IP network redundancy, verify that enough Ethernet ports and interfaces areavailable to create the redundant configuration.



CHAPTER 2

ProtectPoint File System Agent for VMAX


l ProtectPoint with VMAX overview.......................................................................... 18l ProtectPoint environment...................................................................................... 25l ProtectPoint prerequisites..................................................................................... 25l ProtectPoint file system agent setup overview....................................................... 29

ProtectPoint File System Agent for VMAX 17

ProtectPoint with VMAX overviewThe ProtectPoint solution integrates primary storage and protection storage for backupson a Data Domain system. ProtectPoint provides block movement of the data onapplication source LUNs to Data Domain LUNs.

The ProtectPoint solution requires both IP network (LAN or WAN) and Fibre Channel (FC)storage area network (SAN) connectivity. The following table lists the required topologiesfor connecting each component of the solution.

Table 4 ProtectPoint topology requirements

Connected components Connection type

Primary application host to primary storage system FC SAN

Primary application host to primary Data Domain system IP LAN or FC SAN

Primary recovery host to primary storage system FC SAN

IP LAN or FC SANPrimary recovery host to primary Data Domain system

Primary storage system to primary Data Domain system FC SAN

(Optional) Secondary recovery host to secondary storage system FC SAN

(Optional) Secondary recovery host to secondary Data Domain system IP LAN or FC SAN

(Optional) Secondary storage system to secondary Data Domain system FC SAN

(Optional) Primary application host to secondary Data Domain system IP WAN or FC SAN

(Optional) Primary Data Domain system to secondary Data Domain system IP WAN

The following figure shows a sample primary site topology.



Figure 2 Sample primary site ProtectPoint topology

1. Application host2. Recovery host3. Primary storage production device 0001A4. Primary storage production device 0001B5. Backup device 000BA (Data Domain device connected to the primary storagesystem)6. Backup device 000BB (Data Domain device connected to the primary storagesystem)7. Primary storage restore device 0001C8. Primary storage restore device 0001D9. Recovery device 000BC (Data Domain device connected to the primary storagesystem)10. Recovery device 000BD (Data Domain device connected to the primary storagesystem)11. Data Domain block services for backup device 00BA12. Data Domain block services for device 00BB13. Data Domain block services for device 00BC14. Data Domain block services for device 00BD

The ProtectPoint solution works with the features on the Data Domain system and theprimary storage system to provide primary storage to Data Domain protection.ProtectPoint uses the following features:

l On the Data Domain system:

n Block services for ProtectPoint.


ProtectPoint with VMAX overview 19

n FastCopy.l On the EMC VMAX storage array:

n EMC FAST.X.n EMC SnapVX.

The following figure shows the data movement from the application/recovery (AR) host tothe VMAX array, and then to the Data Domain system.

Figure 3 Data movement

1. AR hostAR host software:2. Application3. Host file system4. Host operating system5. Solutions EnablerVMAX system:6. Primary storage software features that work with Data Domain features7. Primary storage production device8. Primary storage backup device9. Copy changed blocks to the Data DomainData Domain system:10. Data Domain block services for ProtectPoint device11. Data Domain static-image

The solution enables an application administrator to leverage the ProtectPoint workflowto protect applications and application data. The storage administrator configures theunderlying storage resources on the primary storage system and the Data Domainsystem. With this storage configuration information and the ProtectPoint softwareexecutable, the application administrator can trigger the workflow to protect theapplication. Before triggering the workflow, the application administrator must quiescethe application to ensure that an application-consistent snapshot is preserved on theData Domain system.

In addition to backing up and protecting data, the application administrator must retainand replicate copies, restore data, and recover applications. The combination ofProtectPoint and the primary storage to Data Domain workflow enables the applicationadministrator to complete all of these operations.



For restoring data, ProtectPoint enables the application administrator to select a specificbackup and make that backup available on selected primary storage devices. Theoperations to mount, mask, and restore the data must be performed manually on the ARhost. The ProtectPoint workflow provides a copy of the data, but not any applicationintelligence.

Basic backup workflowIn the basic backup workflow, data is transferred from the primary storage system to theData Domain system. ProtectPoint manages the data flow, but does not modify the data.

To create a copy or backup of application data, the application administrator or otherappropriate user must ensure that the copy or backup is application-consistent. Thismeans that the application administrator must quiesce the application before initiatingthe backup operation. Using ProtectPoint to create a snapshot on the primary storagesystem while the application is quiesced enables the application administrator tominimize the disruption to the application.

After creating the snapshot, the application administrator uses ProtectPoint to move thesnapshot to the Data Domain system. The primary storage system keeps track of the datathat has changed since the last snapshot was moved to the Data Domain system, andonly copies the changed data. Once all the data captured in the snapshot has been sentto the Data Domain system, ProtectPoint creates a static-image on the Data Domainsystem containing the data that reflects the application-consistent copy initially createdon the primary storage system.

The static-image and any additional metadata can be managed separately from thesnapshot on the primary storage system, and can be a source from which to createadditional copies of the backup. Static-images that are complete with metadata arecalled backup images. ProtectPoint creates one backup image for every protected LUN.Backup images can be combined into backup sets that represent an entire applicationpoint-in-time backup.

The backup workflow consists of the following steps:

1. On the application host, the application administrator quiesces the application.

2. On the primary storage system, ProtectPoint creates a snapshot of the primarystorage device. It is safe to unquiesce the application when this step is complete.

3. The primary storage system analyzes the data and copies the changed data to anencapsulated Data Domain storage device.

4. The Data Domain system creates and stores a static-image of the snapshot.

The following figure shows the basic backup workflow.


Basic backup workflow 21

Figure 4 Basic backup workflow

1. Application host2. Primary storage production device 0001A3. Primary storage production device 0001B4. Backup device 000BA5. Backup device 000BB6. Data Domain block services for ProtectPoint device 000BA7. Data Domain block services for ProtectPoint device 000BB

Basic restore workflowThe application administrator can perform four types of restores:

l Object-level restore from FAST.X-encapsulated devices with SnapVX—The applicationadministrator selects and restores one or more files from a backup image.

l Full-application rollback restore from FAST.X-encapsulated devices with SnapVX—Theapplication administrator restores the application to a previous point-in-time.

l Restore directly to the host from FAST.X-encapsulated devices.

l Restore directly to the host from Data Domain restore devices—The applicationadministrator selects and restores one or more files from a backup image.

For any type of restore, the application administrator selects the backup image to restorefrom the Data Domain system.

For an object-level restore, after selecting the backup image on the Data Domain system,the application administrator mounts Data Domain block services for ProtectPoint



devices that the primary storage system presents to the AR host and performs the restoreoperation.

The object-level restore from FAST.X-encapsulated devices with SnapVX workflowconsists of the following steps:

1. The Data Domain system writes the static-image to the encapsulated storage device,making it available on the primary storage system via the FAST.X restore device.

2. The application administrator mounts the FAST.X restore device on the host, and usesOS- and application-specific tools and commands to restore specific objects to arecovery device on the VMAX.

The following figure shows the object-level restore workflow.

Figure 5 Object-level restore workflow

1. Recovery host2. Primary storage restore device 0001C3. Primary storage restore device 0001D4. Recovery device 000BC5. Recovery device 000BD6. Data Domain block services for ProtectPoint device 27. Data Domain block services for ProtectPoint device 3

The full-application rollback restore from FAST.X-encapsulated devices with SnapVXworkflow consists of the following steps:

1. The Data Domain system writes the static-image to the encapsulated storage device,making it available on the primary storage system.

2. The FAST.X restore devices are copied to the production devices, overwriting thecontents of the production devices.


Basic restore workflow 23

The following figure shows the full-application rollback restore workflow to the VMAXproduction devices.

Figure 6 Full-application rollback restore to the production devices

1. Recovery host2. Primary storage production device 0001A3. Primary storage production device 0001B4. Recovery device 000BC5. Recovery device 000BD6. Data Domain block services for ProtectPoint device 27. Data Domain block services for ProtectPoint device 3

The restore directly to the host from FAST.X-encapsulated devices workflow consists ofthe following steps:

1. The Data Domain system writes the static-image to the encapsulated storage device,making it available on the primary storage system.

2. The application administrator mounts the encapsulated storage device to the host,and uses OS- and application-specific tools and commands to restore specificobjects directly to the AR host.

The restore from Data Domain restore devices consists of the following steps:

1. The application administrator makes the Data Domain restore device available to thehost.

2. The application administrator uses OS- and application-specific tools and commandsto restore specific objects.



ProtectPoint environmentThe ProtectPoint environment consists of the following components:

l Data Domain:

n A Data Domain system with the Data Domain Operating System (DDOS) 5.7.1.0 orhigher.

n Data Domain block services for ProtectPoint.

n (Optional) Data Domain replication.

l VMAX:

n A VMAX array.

n Solutions Enabler 8.2 in local mode on the AR host.

l Application:

n AR host.

n ProtectPoint agent on the AR host.

Additional InformationThe EMC ProtectPoint Solutions Guide provides more detailed information about thecomponents that make up the ProtectPoint solution.

ProtectPoint with Symmetrix Remote Data Facility (SRDF)ProtectPoint can be used in conjunction with the Symmetrix remote replicationfunctionality, EMC SRDF®. No special configuration or configuration changes are requiredbecause ProtectPoint does not change any of the rules governing the interaction betweenSRDF and SnapVX on the VMAX array.

Note

The first full backup after a full restore triggers a full SRDF replication.

The following VMAX documentation provides details about the interaction between SRDFand SnapVX:

l Appendix B SRDF Operations and TimeFinder sessions of the EMC Solutions Enabler SRDFFamily Version 8.2 CLI User Guide

l Appendix B SRDF State Rules Reference of the EMC Solutions Enabler TimeFinder FamilyVersion 8.2 CLI User Guide

ProtectPoint prerequisitesYou must meet the following prerequisites for all ProtectPoint operations:

Note

The prerequisites in this section apply to all ProtectPoint agents.

l Data Domain:


ProtectPoint environment 25

n You must have a Data Domain system that is supported by ProtectPoint. The EMCProtectPoint Version 3.1 Release Notes provides the list of supported Data Domainsystems.

n You must establish IP connectivity to the Data Domain systems TCP port 3009.

l VMAX:

n A VMAX array.

n Solutions Enabler 8.2 in local mode on the AR host.

n You must have the appropriate VMAX source capacity licenses.

n You must configure SAN zoning between the VMAX FA ports and the AR hosts.

– You must ensure one DX emulation exists on each director within the sameengine. Each DX emulation requires two ports exclusively for zoning to theData Domain system.

– For FC zoning with a single SAN switch, create zones between four VMAX DXports and two Data Domain ports.

– For FC zoning with two SAN switches, create zones between four VMAX DXports and four Data Domain ports.

The following figure shows an example of a single SAN switch zoning configuration.

Figure 7 SAN zoning example

Data Domain block services for ProtectPoint prerequisitesYou must meet the following prerequisites for Data Domain block services forProtectPoint operations:

l You must configure a username and password for ownership of the Data Domainblock services for ProtectPoint devices.



Note

Create this user with the none role.

l You must apply a Data Domain block services for ProtectPoint license.

l You must create the Data Domain file system (DDFS).

Block services for ProtectPoint object hierarchyUse the object hierarchy mappings in the following table to plan the ProtectPointconfiguration.

Table 5 Block services for ProtectPoint object hierarchy mappings

Storage object Mapping level

Pool Department

Device-group Application

Device Device

Note

By default, access control is implemented at the pool level. If additional granularity isrequired, create the pools based on the access control requirements.

Data Domain supports the following maximum numbers of pools, device-groups, andblock services for ProtectPoint devices:

l Pools: 128

l Device-groups: 1024 per pool

l Block services for ProtectPoint devices: 2048

Note

MTree quotas can be set to limit the logical size of a block services for ProtectPoint pool.

Use the following commands to determine if additional pools, device-groups, or devicescan be created:

l filesys show space displays the space available to and used by Data Domainstorage devices.

l mtree show compression {<mtree-path>|tenant-unit <tenant-unit>} displays compression statistics, where <mtree-path> is the ProtectPointpool.

l quota capacity show all displays the capacity quotas and usage of allstorage devices.

l vdisk pool show list displays a list of the pools on the Data Domain system.

Data Domain storage layoutThe following figure shows the storage layout of the DDFS.


Data Domain block services for ProtectPoint prerequisites 27

Figure 8 DDFS storage layout

1. /data2. /data/col13. /data/col1/backup4. /data/col1/MTree25. /data/col1/MTree3

The following table describes each element of the DDFS storage layout.

Table 6 DDFS storage elements

DDFS directory Description

/data Top-level directory of the Data Domain storage file system. This directorycannot be changed.

/data/col1 Represents a collection of data, and enables the expansion of the filesystem by creating additional collections, col2, col3, col4, and so on.

/data/col1/backup

Contains backups of the data and directory structure of the collection. ThisMTree cannot be deleted or renamed. Subdirectories can be created toorganize and separate the data.

/data/col1/MTree<X>

Lowest level of the Data Domain storage file system. Each MTree is anindependently managed directory. Data Domain allows up to 100 MTreesto be created, but performance degradation occurs when more than 32MTrees are active at one time.

Data Domain block services for ProtectPointThe block services for ProtectPoint allows you to create devices, device-groups, anddevice pools. Block services also provide additional functionality, such as creating static-images (snapshots) and replicating data.



The EMC Data Domain Operating System Command Reference Guide provides moreinformation about the block services for ProtectPoint and the vdisk commands thatcontrol them.

Data Domain file systemThe DDFS stores the block services for ProtectPoint objects. For example, a block servicesstatic-image can be treated as a file that resides within the DDFS. Therefore, replicating astatic-image is the same as replicating a file. By leveraging the services provided by theDDFS, the block service for ProtectPoint is able to efficiently create static-images of LUNs.

Note

The DDFS automatically defragments backups created in a ProtectPoint environment toprevent performance degradation over time.

The EMC Data Domain Operating System Administration Guide provides more informationabout the DDFS.

ProtectPoint file system agent prerequisitesThe following ProtectPoint file system agent prerequisites must be met beforeproceeding:

l ProtectPoint file system agent users must also be authorized Solutions Enabler users.

Note

Refer to the Solutions Enabler documentation to configure a user account withoutroot access.

l A DX director on the VMAX system must be available in order to encapsulate the DataDomain protection storage.

l The ProtectPoint file system agent must be installed on the AR host.

ProtectPoint file system agent setup overviewWhen you set up the ProtectPoint file system agent, you complete some tasks in theprimary storage system environment, and other tasks in the Data Domain environment.Therefore, open one window to the primary storage environment and one window to theData Domain environment. You will switch between environments as you set up theProtectPoint environment.

Note

You receive a password with the software license. You must use the password when youunpack the downloaded software package.


ProtectPoint file system agent prerequisites 29

CHAPTER 3

Setting Up the ProtectPoint File System Agent forVMAX on Linux or UNIX hosts


l Setting up the ProtectPoint file system agent with VMAX....................................... 32l Installing the ProtectPoint file system agent on a Linux or UNIX host......................33l Modifying the ProtectPoint configuration file......................................................... 33l Verify the ProtectPoint installation........................................................................ 42

Setting Up the ProtectPoint File System Agent for VMAX on Linux or UNIX hosts 31

Setting up the ProtectPoint file system agent with VMAXYou must install any primary storage-specific host software, and the file system agent 3.1package on the AR host. You must also create one or more file system agent configurationfiles for the applications and devices per application, save the Data Domain credentialssecurely on the host, and validate the configuration and connectivity.

Before you begin

Before you set up the ProtectPoint file system agent, verify the following prerequisites aremet:

l SAN connectivity is established for the primary storage system, the Data Domainsystem, and the AR host.

l VMAX to Data Domain SAN connectivity has been established over a SAN switch thatis either single or dual fabric.

l You have the required licenses for the products and systems you are installing.

l You have provisioned LUNs on the primary storage system and the Data Domainsystem, as applicable. The EMC ProtectPoint Primary and Protection StorageConfiguration Guide provides more information about storage provisioning.

l You have configured the appropriate applications on the AR host.

l You have the password provided with the software license to unpack the ProtectPointsoftware package.

The following figure shows an example where three ProtectPoint configuration files arerequired for three separate applications.Figure 9 Multiple configuration files for multiple applications

The setup process consists of two main tasks:

1. Install the ProtectPoint file system agent.

2. Edit the ProtectPoint configuration file.

Follow the instructions to install the ProtectPoint file system agent on the appropriate ARhost operating system:

Setting Up the ProtectPoint File System Agent for VMAX on Linux or UNIX hosts


l Installing the ProtectPoint file system agent on a Linux or UNIX host on page 33

l Installing the ProtectPoint file system agent on a Windows host on page 47

Installing the ProtectPoint file system agent on a Linux or UNIXhost

Procedure

1. Log in to the AR host as a system administrator, such as root.

2. Copy the ProtectPoint software package to a local directory.

3. Unpack the ProtectPoint software package.

a. Run the following command for Linux:gunzip ppfsagent31_<platform>.tar.gz

b. Run the following command for UNIX:tar xf ppfsagent31_<platform>.tar

4. Install the EMC ProtectPoint software using the native OS packaging software.

Modifying the ProtectPoint configuration fileBefore you begin

If you are installing the ProtectPoint file system agent on an AR host where theProtectPoint database application agent is already installed, or planned to be installed, aseparate lockbox location is required for each agent.

Procedure

1. Make a copy of the protectpoint.config.template.vmax configuration file.The default configuration file name is protectpoint.config. Create one or moreconfiguration files as needed. For example:

l Create a separate configuration file for each application.

l Create a separate configuration file for each set of devices per application.

l If necessary, create a separate configuration file for the data and log files.

Note

Edit the default values in the protectpoint.config file. Do not use the included

configuration file template as an actual configuration file.

The configuration file contains the following subsections:

l GeneralThe general information section contains information about the application, thepath for the RSA lockbox, and log files.

l Primary systemThe primary system section contains information associated with the primary DataDomain and VMAX storage systems used in the workflow.

l (Optional) Secondary system (used for replicating data)


Installing the ProtectPoint file system agent on a Linux or UNIX host 33

Note

This section is required for Data Domain replication. The ProtectPoint file systemagent supports Data Domain MTree replication to replicate data from one DataDomain system to another, but does not provide a mechanism to manage thereplication. Use the MTree replication controls in DD OS.

The secondary system section contains information associated with replicating/copying data from the primary Data Domain system to the secondary Data Domainsystem.

l Backup source devicesThe information in the backup source devices section of the configuration filecontains information identifying the VMAX production devices (holding thedatabase to back up).

l (Optional) Restore source devicesThe information in the restore source devices section of the configuration filecontains information identifying a subset of the backup source devices to restorewith the protectpoint restore prepare command.

You need to modify the content in each of these sections according to your topology.

Each section can contain multiple key-value pairs in the key = value format. Valuescan be indicated with single (') or double (") quotation marks. Key-value pairs caninclude spaces as well as special characters, such as the equal sign ( =), but cannotinclude the pound symbol (#), and the semi-colon ( ;). Use only one key-value pair perline.

a. Modify the content in the General section.

Table 7 General section

Key-value pair Description Mandatory or optional: additionalinformation

PP_ARRAY_TYPE =VMAX

Specifies that theprimary storage ison a VMAX array.

Mandatory.

APP_NAME =application name

Application nameon the AR hostcontaining thedata that will bebacked up.

Optional. When the data is backed up, thisinformation is written to the Data Domaindevice-group and the static-imageproperties.

APP_VERSION=applicationversion

Applicationversion.


APP_INFO =application info

Applicationinformation.


LOCKBOX_DIR =path

RSA lockboxdirectory.

Optional. By default, the ProtectPoint filesystem agent saves the RSA lockbox file asprotectpoint.clb in the path $<install-



Table 7 General section (continued)


directory>/lockbox/protectpoint.clb.

LOG_DIR = path Log directory. Optional. By default, the ProtectPoint filesystem agent saves the log files in the path<install-directory>/log .

DEBUG_LEVEL =log level

Log level. Optional. By default, the log level value is2. The possible values are:

1: Error

2: Error and warning

3: Error, warning, and information

4: Error, warning, information, anddebug

LOGFILE_SIZE =file-size

Log file size inmegabytes (MB).

Optional. By default, the maximum log filesize is 4 MB.

LOGFILE_COUNT =number-of-files

Number of log filesretained.

Optional. By default, 16 files are retained.

b. Modify the content in the Primary system section.

Table 8 Primary system section


DD_SYSTEM =hostname/ip-address

Hostname or IPaddress of theprimary DataDomain systemused for backup.

Mandatory.

Note

To use IPv6, specify the hostname ofthe Data Domain system in theconfiguration file instead of the IPaddress.

DD_PORT = port-number Port numberused to connectto the primaryData Domainsystem.

Optional. By default, the port numberis 3009.

DDVDISK_USER = user-name

Owner of theblock servicesfor ProtectPointpool.

Mandatory. This value is also used forDD Boost operations unlessDDBOOST_USER is also specified.

DD_POOL = pool-name Name of blockservices forProtectPoint

May be optional or mandatory. If thisvalue is specified:


Modifying the ProtectPoint configuration file 35

Table 8 Primary system section (continued)


pool containingthe Data Domainrestore deviceson the primaryData Domainsystem.

l Specify DD_DEVICE_GROUPl Do not specify

VMAX_FASTX_RESTORE_SGIf DD_POOL and DD_DEVICE_GROUPare not specified, FAST.X restore LUNsare selected from the defaultNsrSnapSG storage group on theVMAX, or the storage group specifiedin VMAX_FASTX_RESTORE_SG.

DD_DEVICE_GROUP =vdisk-device-group-name

Name of blockservices forProtectPointdevice-groupcontaining theData Domainrestore deviceson the primaryData Domainsystem.

Mandatory if DD_POOL is specified,

otherwise this parameter is ignored.

DDBOOST_USER = ddboost user

The usernameassociated withDD Boost on theprimary DataDomain system.

Optional. If this parameter is notspecified, the username in theDDVDISK_USER parameter is used.

DD_PATH = dd_boost-storage-unit-name

Path of the DDBoost storageunit or top-leveldirectory withinthe storage unitwhere theProtectPointcatalog on theprimary DataDomain systemis maintained.

Mandatory.

VMAX_FASTX_RESTORE_SG= VMAX Storage Group

The name of thestorage groupcreated on theVMAX fromwhich the FAST.Xrestore LUNs areselected

Optional. If this parameter is notspecified, and DD_POOL and

DD_DEVICE_GROUP are not

specified, the default VMAX storagegroup, NsrSnapSG, is used.

c. (Optional) Modify the content in the Secondary system section.



Table 9 Secondary system section (optional)



Hostname or IPaddress of thesecondary DataDomain systemused for backup.

Mandatory.

Note


DD_PORT = port-number Port numberused to connectto the secondaryData Domainsystem.





DD_POOL = pool-name Name of blockservices forProtectPointpool containingthe Data Domainrestore deviceson thesecondary DataDomain system.



VMAX_FASTX_RESTORE_SGIf DD_POOL and DD_DEVICE_GROUPare not specified, FAST.X restoresLUNs are selected from the defaultNsrSnapSG storage group on theVMAX, or the storage group specifiedin VMAX_FASTX_RESTORE_SG.


Name of blockservices forProtectPointdevice-groupcontaining theData Domainrestore deviceson thesecondary DataDomain system.




The usernameassociated withDD Boost on thesecondary DataDomain system.



Path of the DDBoost storage

Mandatory.



Table 9 Secondary system section (optional) (continued)


unit or top-leveldirectory withinthe storage unitwhere theProtectPointcatalog on thesecondary DataDomain systemis maintained.






d. Modify the content in the Backup source device section.

Create one set of key-value pairs in the Backup source device section for eachproduction device with the naming convention SRC_DEVICE<n> where <n> is anumber starting from 1, for example, SRC_DEVICE1, SRC_DEVICE2, and so on.

Table 10 Backup source device section


SRC_DEVICE<n> =VMAXSymID:DeviceID

VMAX array anddevice identifier.

Mandatory. One device identifier isrequired for every source LUN to beprotected. Multiple VMAX array IDs can bespecified.

Note

ProtectPoint will accept a SymID as smallas one digit as long as it uniquelyidentifies the VMAX array.

e. (Optional) Modify the content in the Restore source device section.

Create one set of key-value pairs in the Restore source device section for eachproduction device with the naming convention SRC_DEVICE<n> where <n> is anumber starting from 1, for example, SRC_DEVICE1, SRC_DEVICE2, and so on.



Table 11 Restore source device section


SRC_DEVICE<n> =VMAX SymID:DeviceID


Optional. Specify a subset of thebackup source devices to restore.

Note

ProtectPoint will accept a SymID assmall as one digit as long as it uniquelyidentifies the VMAX array.

The following example shows a sample of the protectpoint.config.vmaxconfiguration file.

####################################################################### ProtectPoint 3.1 example input file for vmax configuration# Indentation used for readability## THIS IS JUST A SAMPLE AND MUST BE MODIFIED TO SUIT YOUR ENVIRONMENT######################################################################## Mandatory - ProtectPoint environment[GENERAL] # Mandatory, no default value - ProtectPoint Array Type, VMAX=Symmetrix 3 # Do NOT change this value PP_ARRAY_TYPE=VMAX

# Application Name, optional, no default value # APP_NAME = <Application name>

# Application version, optional, no default value # APP_VERSION = <Application version>

# Application information/description, optional, no default value # APP_INFO = <Application information>

# Optional, default value=<install dir>/lockbox - The directory of the ProtectPoint RSA lock box # LOCKBOX_DIR = <Directory path>

# Optional, default value=<install dir>/logs - the directory of the ProtectPoint log files # LOG_DIR = <Directory path>

# Optional, default value=2 # 2: error+warning, 3: error + warning + info, 4: error + warning + info + debug # DEBUG_LEVEL = <Log Level 2, 3 or 4>

# Optional, default value=4MB - The log file size # LOGFILE_SIZE = <Log file size in MB>

# Optional, default=16 - Number of ProtectPoint log files to retain # LOGFILE_COUNT = <Number of log files>

##################### Primary Data Domain ################################## Mandatory - The Primary Data Domain system where VMAX-managed devices will be backed up to[PRIMARY_SYSTEM] # Mandatory, no default value - The Primary Data Domain vdisk and Boost hostname or IP # If DD_BOOST_FC is set to true, DD_SYSTEM is the name of the Data Domain Fiber Channel server DD_SYSTEM = <Hostname/IP>



# Optional, indicates that ProtectPoint should use Fibre-Channel communications to the # Data Domain server instead of standard network communications. # DD_BOOST_FC = TRUE

# Optional, no default value - The Primary Data Domain Boost port number # DD_PORT = <Port number>

# Mandatory, no default value - The Primary Data Domain vdisk username # Note: Only one of DDVDISK_USER and DDBOOST_USER is required. If only # one is supplied, its value will be used for both. DDVDISK_USER = <Username>

# Optional, no default value - The Primary Data Domain # pool name containing vdisk devices used for restore # # By default, restores are performed using FAST.X restore devices which are selected from the VMax # storage group "NsrSnapSG". However, if this and the RESTORE_DEVICE_GROUP fields are specified, # then restores are done by selecting restore devices from the specified Data Domain pool and # group of restore devices. If either RESTORE_DEVICE_POOL or RESTORE_DEVICE_GROUP are specified, # both must be specified and VMAX_FASTX_RESTORE_SG cannot be specified # RESTORE_DEVICE_POOL = <Pool name>

# Optional, no default value - The Primary Data Domain device group used for vdisk restore # If either DD_POOL or DD_DEVICE_GROUP are specified, then both must # be specified and VMAX_FASTX_RESTORE_SG cannot be specified. # RESTORE_DEVICE_GROUP = <Device group name>

# Mandatory, no default value - The Primary Data Domain DDBOOST user name # Note: Only one of DDVDISK_USER and DDBOOST_USER is required. If only # one is supplied, its value will be used for both. DDBOOST_USER = <Username>

# Mandatory, no default value - The name of the storage unit or a top-level directory within # the Primary Data Domain where the ProtectPoint catalog is maintained DD_PATH = <ddboost path>

# Optional, Default = "NsrSnapSG" - the name of the VMax storage group # to use during VMax restores to select appropriate FAST.X restore devices. # If specified, then DD_POOL and DD_DEVICE_GROUP cannot be specified. # VMAX_FASTX_RESTORE_SG = <name>

# Optional, default is false. Indicates whether restore devices to be selected must be visible to the host. # SELECT_VISIBLE_RESTORE_DEVICES = TRUE

################## Secondary Data Domain ################################### Optional - The Secondary Data Domain system where a user-replicated backup will be recovered from# [SECONDARY_SYSTEM] # Mandatory, no default value - The Secondary Data Domain Boost hostname or IP # If DD_BOOST_FC is set to true, DD_SYSTEM is the name of the Data Domain Fiber Channel server # DD_SYSTEM = <Hostname/IP>


# Optional, no default value - The Secondary Data Domain Boost port number # DD_PORT = <Port number>

# Mandatory, no default value - The Secondary Data Domain vdisk username # Note: Only one of DDVDISK_USER and DDBOOST_USER is required. If only



# one is supplied, its value will be used for both. # DDVDISK_USER = <Username>

# Optional, no default value - The Secondary Data Domain # pool name containing vdisk devices used for restore # # By default, restores are performed using FAST.X restore devices which are selected from the VMax # storage group "NsrSnapSG". However, if this and the RESTORE_DEVICE_GROUP fields are specified, # then restores are done by selecting restore devices from the specified Data Domain pool and # group of restore devices. If either RESTORE_DEVICE_POOL or RESTORE_DEVICE_GROUP are specified, # both must be specified and VMAX_FASTX_RESTORE_SG cannot be specified # RESTORE_DEVICE_POOL = <Pool name>

# Optional, no default value - The Secondary Data Domain device group used for vdisk restore # If either DD_POOL or DD_DEVICE_GROUP are specified, then both must # be specified and VMAX_FASTX_RESTORE_SG cannot be specified. # RESTORE_DEVICE_GROUP = <Device group name>

# Mandatory, no default value - The Secondary Data Domain DDBOOST user name # Note: Only one of DDVDISK_USER and DDBOOST_USER is required. If only # one is supplied, its value will be used for both. # DDBOOST_USER = <Username>

# Mandatory, no default value - The name of the storage unit or a top-level directory within # the Secondary Data Domain where the ProtectPoint catalog is maintained # DD_PATH = <ddboost path>



#################### VMax Devices ######################### Mandatory - The VMax device information section[BACKUP_SOURCE_DEVICES] # Mandatory, no default value - The VMAX symid+sym_deviceid (format "VMax ID:VMax Device ID") SRC_DEVICE1 = <SYMID:DEVID>

# Optional - Additional VMax device device information # SRC_DEVICEn = <SYMID:DEVID>

# Optional - A subset of the source devices that will be restored during the "restore prepare" and "rollback" operations.# [RESTORE_SOURCE_DEVICES] # Optional, no default value - The VMAX symid+sym_deviceid (format "VMax ID:VMax Device ID") # SRC_DEVICE1 = <SYMID:DEVID> # SRC_DEVICEn = <SYMID:DEVID>

2. Store the Data Domain user credentials securely.

Run the following command:protectpoint security add dd-credentials [dd-system {primary| secondary}] {ddboost | vdisk}



Note

l If the dd-system parameter is not specified, the command uses the primary Data

Domain system by default.

l The dd-system parameter is required to specify ddboost or vdisk.

protectpoint security add dd-credentials config-file protectpoint.config

Verify the ProtectPoint installationBefore you begin

Before you complete this task, run the following command to save either the primary orsecondary Data Domain system credentials to the RSA lockbox:protectpoint security add dd-credentials [dd-system {primary |secondary}] {ddboost | vdisk}Validate the content and format of the configuration file modified when the ProtectPointfile system agent was set up on the AR host.

Procedure

1. Log in to the AR host as a system administrator.

2. Start the validation process.

Run the following command:protectpoint config validate [config-file <file-path>] [dd-system secondary] [full]By default, the protectpoint config validate command only validates theprimary Data Domain system. Use the dd-system secondary option to validate thesecondary Data Domain system if it exists in the environment.

The full option provides a deeper validation of the restore devices.

protectpoint config validateValidating application settings.........................[OK]Validating host requirements............................[OK]Validating Primary System: VDisk Connection Information........................[OK] Boost Connection Information........................[OK] FAST.X Restore Group................................[OK] DD Boost Path.......................................[OK]Validating VMax Devices: VMax Device 1032:4F5................................[OK] VMax Device 1032:4F6................................[OK]

3. Create and backup a snapshot to verify the ProtectPoint implementation.

a. Log in to the AR host as a system administrator.

b. Run the appropriate host-specific command to quiesce the application.

c. Establish the relationship between the VMAX array and Data Domain system, andactivate the snapshot.

Run the following command:symsnapvx -sid <SymmetrixID> -sg <SgName> establish -name<SnapshotName>

symsnapvx -sid 0129 -sg storage-group-5 establish -name dg5-snap



d. Move the data from the VMAX array on to the Data Domain system. This commandmoves the changed blocks on the source device to the target device.

Run the following command:symsnapvx -sid <SymmetrixID> -sg <SgName> link -copy -snapshot_name <SnapshotName>symsnapvx -sid 0129 -sg storage-group-5 link -copy -snapshot_name dg5-snap

e. Check the status of the link copy operation, and wait for it to complete.

Note

VMAX symsnapvx commands are asynchronous. Verify that all symsnapvxlink -copy operations are complete before you perform a file system agent

backup; otherwise the backup will fail. The operations are complete when thecommand indicates the link status is destaged.

Run the following command:symsnapvx -sid <SymmetrixID> list -sg <storage-group> -linkedsymsnapvx -sid 0129 -sg storage-group-5 -linked

f. Use the ProtectPoint file system agent to take a snapshot of the devices holdingthe data on the VMAX array.

Run the following command:protectpoint snapshot create description "<description>"config-file <file-path>

protectpoint snapshot create description "EnvironmentVerification" config-file protecpoint.config

g. Use the ProtectPoint file system agent to create a backup on the Data Domainsystem of the SnapVX snapshot created above.

Note

The backup ID is displayed by the protectpoint snapshot createcommand.

Run the following command:protectpoint backup create backup-id <id> config-file<file-path>

protectpoint backup create backup-id 1454601272 config-file protectpoint.config

Note

If system displays the error message "SYMAPI_C_SNAPSHOT_NOT_FOUND", one

or more of the source LUNs being operated on is missing its required NSM SnapVXsnapshot. Create the required snapshot and retry the backup operation.

h. Run the appropriate host-specific command to unquiesce the application.

i. Display the status of the backup.

Run the following command:protectpoint backup show list


Verify the ProtectPoint installation 43

The new backup is listed with a status of snap-ready.

j. Use the ProtectPoint file system agent to create the backup on the Data Domainsystem.

Run the following command:protectpoint backup create backup-id <backup-ID>

Note


The backup status changes to in-progress, and remains in that state until theoperation completes and the status changes to complete.

Note

The command ends execution when the backup is complete.

k. Verify the backup status is complete.


The new backup is listed with a status of complete.



CHAPTER 4

Setting Up the ProtectPoint File System Agent forVMAX on Windows hosts


l Setting up the ProtectPoint file system agent with VMAX....................................... 46l Installing the ProtectPoint file system agent on a Windows host............................ 47l Modifying the ProtectPoint configuration file......................................................... 48l Verify the ProtectPoint installation........................................................................ 56

Setting Up the ProtectPoint File System Agent for VMAX on Windows hosts 45

Setting up the ProtectPoint file system agent with VMAXYou must install any primary storage-specific host software, and the file system agent 3.1package on the AR host. You must also create one or more file system agent configurationfiles for the applications and devices per application, save the Data Domain credentialssecurely on the host, and validate the configuration and connectivity.

Before you begin


l SAN connectivity is established for the primary storage system, the Data Domainsystem, and the AR host.

l VMAX to Data Domain SAN connectivity has been established over a SAN switch thatis either single or dual fabric.


l You have provisioned LUNs on the primary storage system and the Data Domainsystem, as applicable. The EMC ProtectPoint Primary and Protection StorageConfiguration Guide provides more information about storage provisioning.


l You have the password provided with the software license to unpack the ProtectPointsoftware package.

The following figure shows an example where three ProtectPoint configuration files arerequired for three separate applications.Figure 10 Multiple configuration files for multiple applications

The setup process consists of two main tasks:




Setting Up the ProtectPoint File System Agent for VMAX on Windows hosts




Installing the ProtectPoint file system agent on a Windows hostBefore you begin

The Windows installer is signed with a certificate. Click Package Properties > DigitalSignature to view the digital signature of the installer.

Note

If file system agent commands are initiated when Quick Edit mode is enabled onWindows hosts, the commands will not complete until you press Enter.

Procedure


2. Copy the ProtectPoint installer to a local directory.

3. Double-click the ProtectPoint executable to launch the installer.

4. Click Next.

5. Select I accept the terms in the License Agreement and click Next.

6. Click Next to accept the default installation directory.

7. Click Install.

8. Click Finish.

Note

The ProtectPoint installer for Windows does not automatically create the ProtectPointconfiguration file, protectpoint.config.

9. Create the ProtectPoint configuration file, protectpoint.config.

Note

Do not use the protectpoint.config.template.vmax file as the configuration

file without making a copy of it and changing the filename.

a. Navigate to the install directory and make a copy of theprotectpoint.config.template.vmax file.

b. Rename the new copy as protectpoint.config.

Note the following considerations for working with the configuration file in aWindows environment:

l Save the configuration file in ANSI format.

l IPv6 IP addresses are not supported.


Installing the ProtectPoint file system agent on a Windows host 47



Procedure

1. Make a copy of the protectpoint.config.template.vmax configuration file.The default configuration file name is protectpoint.config. Create one or moreconfiguration files as needed. For example:




Note




l GeneralThe general information section contains information about the application, thepath for the RSA lockbox, and log files.

l Primary systemThe primary system section contains information associated with the primary DataDomain and VMAX storage systems used in the workflow.

l (Optional) Secondary system (used for replicating data)

Note

This section is required for Data Domain replication. The ProtectPoint file systemagent supports Data Domain MTree replication to replicate data from one DataDomain system to another, but does not provide a mechanism to manage thereplication. Use the MTree replication controls in DD OS.

The secondary system section contains information associated with replicating/copying data from the primary Data Domain system to the secondary Data Domainsystem.

l Backup source devicesThe information in the backup source devices section of the configuration filecontains information identifying the VMAX production devices (holding thedatabase to back up).



Each section can contain multiple key-value pairs in the key = value format. Valuescan be indicated with single (') or double (") quotation marks. Key-value pairs can



include spaces as well as special characters, such as the equal sign ( =), but cannotinclude the pound symbol (#), and the semi-colon ( ;). Use only one key-value pair perline.




PP_ARRAY_TYPE =VMAX

Specifies that theprimary storage ison a VMAX array.

Mandatory.


Application nameon the AR hostcontaining thedata that will bebacked up.



Applicationversion.





LOCKBOX_DIR =path


Optional. By default, the ProtectPoint filesystem agent saves the RSA lockbox file asprotectpoint.clb in the path $<install-directory>/lockbox/protectpoint.clb.

LOG_DIR = path Log directory. Optional. By default, the ProtectPoint filesystem agent saves the log files in the path<install-directory>/log .

DEBUG_LEVEL =log level

Log level. Optional. By default, the log level value is2. The possible values are:

1: Error






Optional. By default, the maximum log filesize is 4 MB.



Optional. By default, 16 files are retained.







Hostname or IPaddress of theprimary DataDomain systemused for backup.

Mandatory.

Note


DD_PORT = port-number Port numberused to connectto the primaryData Domainsystem.





DD_POOL = pool-name Name of blockservices forProtectPointpool containingthe Data Domainrestore deviceson the primaryData Domainsystem.



VMAX_FASTX_RESTORE_SGIf DD_POOL and DD_DEVICE_GROUPare not specified, FAST.X restore LUNsare selected from the defaultNsrSnapSG storage group on theVMAX, or the storage group specifiedin VMAX_FASTX_RESTORE_SG.


Name of blockservices forProtectPointdevice-groupcontaining theData Domainrestore deviceson the primaryData Domainsystem.




The usernameassociated withDD Boost on theprimary DataDomain system.



Path of the DDBoost storage

Mandatory.





unit or top-leveldirectory withinthe storage unitwhere theProtectPointcatalog on theprimary DataDomain systemis maintained.










Hostname or IPaddress of thesecondary DataDomain systemused for backup.

Mandatory.

Note


DD_PORT = port-number Port numberused to connectto the secondaryData Domainsystem.





DD_POOL = pool-name Name of blockservices forProtectPointpool containingthe Data Domainrestore devices



VMAX_FASTX_RESTORE_SG





on thesecondary DataDomain system.

If DD_POOL and DD_DEVICE_GROUPare not specified, FAST.X restoresLUNs are selected from the defaultNsrSnapSG storage group on theVMAX, or the storage group specifiedin VMAX_FASTX_RESTORE_SG.


Name of blockservices forProtectPointdevice-groupcontaining theData Domainrestore deviceson thesecondary DataDomain system.




The usernameassociated withDD Boost on thesecondary DataDomain system.



Path of the DDBoost storageunit or top-leveldirectory withinthe storage unitwhere theProtectPointcatalog on thesecondary DataDomain systemis maintained.

Mandatory.






d. Modify the content in the Backup source device section.




Table 15 Backup source device section


SRC_DEVICE<n> =VMAXSymID:DeviceID


Mandatory. One device identifier isrequired for every source LUN to beprotected. Multiple VMAX array IDs can bespecified.

Note

ProtectPoint will accept a SymID as smallas one digit as long as it uniquelyidentifies the VMAX array.

e. (Optional) Modify the content in the Restore source device section.


Table 16 Restore source device section


SRC_DEVICE<n> =VMAX SymID:DeviceID


Optional. Specify a subset of thebackup source devices to restore.

Note

ProtectPoint will accept a SymID assmall as one digit as long as it uniquelyidentifies the VMAX array.

The following example shows a sample of the protectpoint.config.vmaxconfiguration file.

####################################################################### ProtectPoint 3.1 example input file for vmax configuration# Indentation used for readability## THIS IS JUST A SAMPLE AND MUST BE MODIFIED TO SUIT YOUR ENVIRONMENT######################################################################## Mandatory - ProtectPoint environment[GENERAL] # Mandatory, no default value - ProtectPoint Array Type, VMAX=Symmetrix 3 # Do NOT change this value PP_ARRAY_TYPE=VMAX



# Application information/description, optional, no default value



# APP_INFO = <Application information>






##################### Primary Data Domain ################################## Mandatory - The Primary Data Domain system where VMAX-managed devices will be backed up to[PRIMARY_SYSTEM] # Mandatory, no default value - The Primary Data Domain vdisk and Boost hostname or IP # If DD_BOOST_FC is set to true, DD_SYSTEM is the name of the Data Domain Fiber Channel server DD_SYSTEM = <Hostname/IP>




# Optional, no default value - The Primary Data Domain # pool name containing vdisk devices used for restore # # By default, restores are performed using FAST.X restore devices which are selected from the VMax # storage group "NsrSnapSG". However, if this and the RESTORE_DEVICE_GROUP fields are specified, # then restores are done by selecting restore devices from the specified Data Domain pool and # group of restore devices. If either RESTORE_DEVICE_POOL or RESTORE_DEVICE_GROUP are specified, # both must be specified and VMAX_FASTX_RESTORE_SG cannot be specified # RESTORE_DEVICE_POOL = <Pool name>

# Optional, no default value - The Primary Data Domain device group used for vdisk restore # If either DD_POOL or DD_DEVICE_GROUP are specified, then both must # be specified and VMAX_FASTX_RESTORE_SG cannot be specified. # RESTORE_DEVICE_GROUP = <Device group name>










# Mandatory, no default value - The Secondary Data Domain vdisk username # Note: Only one of DDVDISK_USER and DDBOOST_USER is required. If only # one is supplied, its value will be used for both. # DDVDISK_USER = <Username>

# Optional, no default value - The Secondary Data Domain # pool name containing vdisk devices used for restore # # By default, restores are performed using FAST.X restore devices which are selected from the VMax # storage group "NsrSnapSG". However, if this and the RESTORE_DEVICE_GROUP fields are specified, # then restores are done by selecting restore devices from the specified Data Domain pool and # group of restore devices. If either RESTORE_DEVICE_POOL or RESTORE_DEVICE_GROUP are specified, # both must be specified and VMAX_FASTX_RESTORE_SG cannot be specified # RESTORE_DEVICE_POOL = <Pool name>

# Optional, no default value - The Secondary Data Domain device group used for vdisk restore # If either DD_POOL or DD_DEVICE_GROUP are specified, then both must # be specified and VMAX_FASTX_RESTORE_SG cannot be specified. # RESTORE_DEVICE_GROUP = <Device group name>







#################### VMax Devices ######################### Mandatory - The VMax device information section[BACKUP_SOURCE_DEVICES] # Mandatory, no default value - The VMAX symid+sym_deviceid (format "VMax ID:VMax Device ID") SRC_DEVICE1 = <SYMID:DEVID>

# Optional - Additional VMax device device information # SRC_DEVICEn = <SYMID:DEVID>

# Optional - A subset of the source devices that will be restored during the "restore prepare" and "rollback" operations.# [RESTORE_SOURCE_DEVICES] # Optional, no default value - The VMAX symid+sym_deviceid (format "VMax ID:VMax Device ID") # SRC_DEVICE1 = <SYMID:DEVID> # SRC_DEVICEn = <SYMID:DEVID>

2. Store the Data Domain user credentials securely.


Note




protectpoint security add dd-credentials config-file protectpoint.config

Verify the ProtectPoint installationBefore you begin

Before you complete this task, run the following command to save either the primary orsecondary Data Domain system credentials to the RSA lockbox:protectpoint security add dd-credentials [dd-system {primary |secondary}] {ddboost | vdisk}Validate the content and format of the configuration file modified when the ProtectPointfile system agent was set up on the AR host.

Procedure





protectpoint config validateValidating application settings.........................[OK]Validating host requirements............................[OK]



Validating Primary System: VDisk Connection Information........................[OK] Boost Connection Information........................[OK] FAST.X Restore Group................................[OK] DD Boost Path.......................................[OK]Validating VMax Devices: VMax Device 1032:4F5................................[OK] VMax Device 1032:4F6................................[OK]


a. Log in to the AR host as a system administrator.


c. Establish the relationship between the VMAX array and Data Domain system, andactivate the snapshot.


symsnapvx -sid 0129 -sg storage-group-5 establish -name dg5-snap

d. Move the data from the VMAX array on to the Data Domain system. This commandmoves the changed blocks on the source device to the target device.


e. Check the status of the link copy operation, and wait for it to complete.

Note

VMAX symsnapvx commands are asynchronous. Verify that all symsnapvxlink -copy operations are complete before you perform a file system agent

backup; otherwise the backup will fail. The operations are complete when thecommand indicates the link status is destaged.

Run the following command:symsnapvx -sid <SymmetrixID> list -sg <storage-group> -linkedsymsnapvx -sid 0129 -sg storage-group-5 -linked

f. Use the ProtectPoint file system agent to take a snapshot of the devices holdingthe data on the VMAX array.


protectpoint snapshot create description "EnvironmentVerification" config-file protecpoint.config

g. Use the ProtectPoint file system agent to create a backup on the Data Domainsystem of the SnapVX snapshot created above.



Note


Run the following command:protectpoint backup create backup-id <id> config-file<file-path>


Note

If system displays the error message "SYMAPI_C_SNAPSHOT_NOT_FOUND", one

or more of the source LUNs being operated on is missing its required NSM SnapVXsnapshot. Create the required snapshot and retry the backup operation.

h. Run the appropriate host-specific command to unquiesce the application.

i. Display the status of the backup.



j. Use the ProtectPoint file system agent to create the backup on the Data Domainsystem.


Note



Note


k. Verify the backup status is complete.





CHAPTER 5

ProtectPoint File System Agent for RecoverPoint


l ProtectPoint with RecoverPoint overview............................................................... 60l ProtectPoint with RecoverPoint environment......................................................... 64l ProtectPoint prerequisites..................................................................................... 65

ProtectPoint File System Agent for RecoverPoint 59

ProtectPoint with RecoverPoint overviewThe ProtectPoint solution integrates primary storage and protection storage for backupson a Data Domain system. ProtectPoint provides block movement of the data onapplication source LUNs to Data Domain LUNs.

The ProtectPoint solution requires both IP network (LAN or WAN) and Fibre Channel (FC)storage area network (SAN) connectivity. The following table lists the required topologiesfor connecting each component of the solution.

Table 17 ProtectPoint topology requirements



Primary application host to RecoverPoint cluster IP LAN

Primary application host to primary Data Domain system FC SAN and IP LAN

Primary recovery host to primary storage system FC SAN and IP LAN

IP LANPrimary recovery host to RecoverPoint cluster

Primary recovery host to primary Data Domain system FC SAN

Primary storage to RecoverPoint cluster FC SAN and IP LAN

RecoverPoint cluster to primary Data Domain system FC SAN and IP LAN


The following figure shows a sample primary site topology.

Note

The thin gray lines represent IP connections, and the thicker blue lines represent FCconnections.



Figure 11 Sample primary site ProtectPoint topology

1. Application host2. XtremIO system3. Primary Data Domain system4. RecoverPoint appliance5. Recovery host (optional)6. Secondary Data Domain system (optional)7. Secondary recovery host (optional)

The ProtectPoint solution works with the features on the Data Domain system, theRecoverPoint appliance, and the XtremIO cluster to provide primary storage to DataDomain protection. ProtectPoint uses the following features:

l On the Data Domain system:

n Block services for ProtectPoint.

n FastCopy.

n DD Boost.

l On the RecoverPoint appliance:

n Catalog for RecoverPoint appliance

n Consistency groups.

l On the XtremIO cluster:

n Initiator Groups.

The solution enables an application administrator to leverage the ProtectPoint workflowto protect applications and application data. The storage administrator configures theunderlying storage resources on the primary storage system and the Data Domainsystem. With this storage configuration information, RecoverPoint, and the ProtectPointsoftware executable, the application administrator can trigger the workflow to protect theapplication. Before triggering the workflow, the application administrator must quiesce


ProtectPoint with RecoverPoint overview 61

the application to ensure that an application-consistent snapshot is preserved on theData Domain system.

In addition to backing up and protecting data, the application administrator must retainand replicate copies, restore data, and recover applications. The combination ofProtectPoint and the primary storage to Data Domain workflow enables the applicationadministrator to complete all of these operations.

For restoring data, ProtectPoint enables the application administrator to select a specificbackup and make that backup available on selected primary storage devices. Theoperations to mask, mount, and restore the data must be performed manually on theprimary storage system. The workflow provides a copy of the data, but not anyapplication intelligence.

Basic backup workflowIn the basic backup workflow, data is transferred from the primary storage system to theData Domain system. ProtectPoint manages the data flow, but does not modify the data.

To create a copy or backup of an application, the application administrator or otherappropriate user must ensure that the source LUNs are in an application-consistent state.This means that the application administrator must quiesce the application beforeinitiating the backup operation. Using ProtectPoint to create the backup on the primarystorage system enables the application administrator to minimize the disruption to theapplication.

After creating the snapshot, RecoverPoint moves the snapshot to the Data Domainsystem. The primary storage system keeps track of the data that has changed since thelast update to the Data Domain system, and only copies the changed data. Once all thedata captured in the snapshot has been moved, the Data Domain system creates a static-image of the data that reflects the application-consistent copy initially created on theprimary storage system.

The backup workflow consists of the following steps:

1. On the application host, the application administrator quiesces the application.

2. On the primary storage system, ProtectPoint creates a snapshot of the primarystorage device. It is safe to unquiesce the application when this step is complete.

3. RecoverPoint analyzes the data and copies the changed data to a Data Domainstorage device.

4. The Data Domain system creates and stores a static-image of the snapshot.

The following figure shows the basic backup workflow.



Figure 12 Basic backup workflow

Note

The objects in the vdisk pool in the figure above represent static-images. Each columnrepresents one backup operation.

Basic restore workflowProtectPoint with RecoverPoint allows application administrators to restore directly fromthe restore devices on the Data Domain system to the AR host without involving theprimary storage or the RecoverPoint cluster. ProtectPoint with RecoverPoint supportsobject-level restores, and rollback restores.

For an object-level restore, after selecting the backup image on the Data Domain system,the application administrator restores the data to a new set of Data Domain blockservices for ProtectPoint devices (restore devices) to present to the AR host, then copiesindividual files back to the production devices.

The object-level restore workflow consists of the following steps:

1. The Data Domain system writes the static-image to a restore device visible to the ARhost.

2. The application administrator mounts the storage device to the host, and uses OS-and application-specific tools and commands to restore specific objects.

For a rollback restore, after selecting the backup from the catalog, the ProtectPoint agentrestores the data to a new set of Data Domain block services for ProtectPoint devices


Basic restore workflow 63

(restore devices) to present to the AR host, then copies the entire backup back to theoriginal production devices, overwriting the current contents of the production devices.

The rollback restore workflow consists of the following steps:

1. The application administrator selects a backup to use for the rollback restore.

2. The application administrator initiates the rollback operation, and the ProtectPointfile system agent executes the rollback.

The following figure shows the basic restore workflow.

Figure 13 Basic restore workflow

ProtectPoint with RecoverPoint environmentThe ProtectPoint with EMC RecoverPoint environment consists of the followingcomponents:

l Data Domain:

n A Data Domain system with the Data Domain Operating System (DDOS) 5.7.1.0 orhigher.

n Data Domain block services for ProtectPoint.

n DD Boost.

n (Optional) Data Domain MTree replication.



l RecoverPoint

n A RecoverPoint cluster (two to eight Gen5 or later RecoverPoint appliances)running RecoverPoint version 4.4.X.

l EMC XtremIO®:

n An XtremIO cluster running Storage Array Software version 4.0.2 or later.

l Application:

n AR host.

n ProtectPoint agent on the AR host.

ProtectPoint prerequisitesYou must meet the following prerequisites for all ProtectPoint operations:

Note

The prerequisites in this section apply to all ProtectPoint agents.

l Data Domain:

n You must have a Data Domain system that is supported by ProtectPoint. The EMCProtectPoint Version 3.1 Release Notes provides the list of supported Data Domainsystems.

n Block services for ProtectPoint must be enabled on the Data Domain system.

n Data Domain Boost must be enabled on the Data Domain system.

l RecoverPoint:

n RecoverPoint backup (BK) license.

n The RecoverPoint cluster must have Gen5 or later RecoverPoint appliances (RPAs),running RecoverPoint version 4.4.X.

n Port 443 must be open between the RecoverPoint appliances, the XtremIOManagement System, and the XtremIO System-wide Management (SYM) moduleon X1-Storage Controller 1 (X1-SC1) and X1-Storage Controller 2 (X1-SC2) IPaddresses.

n Port 11111 must be open between the RPAs and XtremIO SYM module on X1-SC1and X1-SC2.

n IP connectivity must be configured between the RPA and the Data Domain system.

Note

For IP connections between the RPAs and the Data Domain system, the DataDomain ifgroup feature provides improved network performance by spreading thenetwork traffic across multiple network interfaces. The Data Domain OperatingSystem Administration Guide provides more details about ifgroups.

n FC zoning must be configured between the RPA and the XtremIO cluster, and isoptional between the RPA and the Data Domain system.


ProtectPoint prerequisites 65

Note

FC zoning between the RPA and the Data Domain system is only required if DDBoost over FC is used for communication between the RPA and the Data Domainsystem.

– Zone at least two initiators from the RPA to the Data Domain system.

– Create one zone per fabric between the RPA and the XtremIO cluster, andinclude all the RPA ports intended for XtremIO connectivity and all the XtremIOports intended for RPA connectivity in the zone.

– Zone the RecoverPoint initiators to multiple targets on the Data Domain systemor XtremIO cluster in accordance with RecoverPoint best practices.

l XtremIO:

n The XtremIO cluster must be running XtremIO software version 4.0.2 or later.

n FC zoning must be configured between the XtremIO cluster and the AR host.

– Use a single-initiator per single-target (1:1) zoning scheme. If the FCswitchzone count limitation has been reached, it is also possible to use single-initiator per multiple-target (1:many) zoning scheme.

– The optimal number of paths depends on the operating system and serverinformation. To avoid multipathing performance degradation, do not use morethan16 paths per device.

– Enable MPIO if two or more paths are zoned to a Windows AR host.

Data Domain block services for ProtectPoint prerequisitesYou must meet the following prerequisites for Data Domain block services forProtectPoint operations:

l You must configure a username and password for ownership of the Data Domainblock services for ProtectPoint devices.

Note

Create this user with the none role.

l You must apply a Data Domain block services for ProtectPoint license.

l You must create the Data Domain file system (DDFS).

Block services for ProtectPoint object hierarchyUse the object hierarchy mappings in the following table to plan the ProtectPointconfiguration.

Table 18 Block services for ProtectPoint object hierarchy mappings

Storage object Mapping level

Pool Department

Device-group Application

Device Device



Note

By default, access control is implemented at the pool level. If additional granularity isrequired, create the pools based on the access control requirements.

Data Domain supports the following maximum numbers of pools, device-groups, andblock services for ProtectPoint devices:

l Pools: 128

l Device-groups: 1024 per pool

l Block services for ProtectPoint devices: 2048

Note

MTree quotas can be set to limit the logical size of a block services for ProtectPoint pool.

Use the following commands to determine if additional pools, device-groups, or devicescan be created:

l filesys show space displays the space available to and used by Data Domainstorage devices.

l mtree show compression {<mtree-path>|tenant-unit <tenant-unit>} displays compression statistics, where <mtree-path> is the ProtectPointpool.

l quota capacity show all displays the capacity quotas and usage of allstorage devices.

l vdisk pool show list displays a list of the pools on the Data Domain system.

Data Domain storage layoutThe following figure shows the storage layout of the DDFS.Figure 14 DDFS storage layout

1. /data2. /data/col13. /data/col1/backup


Data Domain block services for ProtectPoint prerequisites 67

Figure 14 DDFS storage layout (continued)

4. /data/col1/MTree25. /data/col1/MTree3

The following table describes each element of the DDFS storage layout.

Table 19 DDFS storage elements

DDFS directory Description

/data Top-level directory of the Data Domain storage file system. This directorycannot be changed.

/data/col1 Represents a collection of data, and enables the expansion of the filesystem by creating additional collections, col2, col3, col4, and so on.

/data/col1/backup

Contains backups of the data and directory structure of the collection. ThisMTree cannot be deleted or renamed. Subdirectories can be created toorganize and separate the data.

/data/col1/MTree<X>

Lowest level of the Data Domain storage file system. Each MTree is anindependently managed directory. Data Domain allows up to 100 MTreesto be created, but performance degradation occurs when more than 32MTrees are active at one time.

Data Domain block services for ProtectPointThe block services for ProtectPoint allows you to create devices, device-groups, anddevice pools. Block services also provide additional functionality, such as creating static-images (snapshots) and replicating data.

The EMC Data Domain Operating System Command Reference Guide provides moreinformation about the block services for ProtectPoint and the vdisk commands thatcontrol them.

Data Domain file systemThe DDFS stores the block services for ProtectPoint objects. For example, a block servicesstatic-image can be treated as a file that resides within the DDFS. Therefore, replicating astatic-image is the same as replicating a file. By leveraging the services provided by theDDFS, the block service for ProtectPoint is able to efficiently create static-images of LUNs.

Note

The DDFS automatically defragments backups created in a ProtectPoint environment toprevent performance degradation over time.

The EMC Data Domain Operating System Administration Guide provides more informationabout the DDFS.

ProtectPoint file system agent prerequisitesThe following ProtectPoint file system agent prerequisites must be met beforeproceeding:

l User accounts for block services for ProtectPoint, and Data Domain Boost must becreated on the Data Domain system.



l User account must be created on the RecoverPoint appliance.

l The ProtectPoint file system agent must be installed on the AR host.


ProtectPoint file system agent prerequisites 69

CHAPTER 6

Setting Up the ProtectPoint File System Agent forRecoverPoint on Linux or UNIX Hosts


l Setting up the ProtectPoint file system agent with RecoverPoint............................ 72l Installing the ProtectPoint file system agent on a Linux or UNIX host......................73l Modifying the ProtectPoint configuration file......................................................... 73l Verify the ProtectPoint installation........................................................................ 81

Setting Up the ProtectPoint File System Agent for RecoverPoint on Linux or UNIX Hosts 71

Setting up the ProtectPoint file system agent with RecoverPointYou must install any primary storage-specific host software required by the file systemagent, and the file system agent 3.1 package on the AR host. You must also create one ormore file system agent configuration files for the applications being protected, save theData Domain and RecoverPoint credentials securely on the host, and validate theconfiguration and connectivity.

Before you begin


l Connectivity is established for the primary storage system, the Data Domain system,and the AR host.


l You have provisioned devices on the primary storage system and the Data Domainsystem, as applicable. The EMC ProtectPoint Primary and Protection StorageConfiguration Guide provides more information about storage provisioning.


The following figure shows an example where three ProtectPoint configuration files arerequired for three separate protected applications.Figure 15 Multiple configuration files for multiple applications

The setup process consists of three main tasks:



3. Enter the appropriate usernames and passwords to allow connectivity between theAR host, Data Domain system, RecoverPoint appliance, and XtremIO cluster.



Setting Up the ProtectPoint File System Agent for RecoverPoint on Linux or UNIX Hosts



Installing the ProtectPoint file system agent on a Linux or UNIXhost

Procedure

1. Log in to the AR host as a system administrator, such as root.

2. Copy the ProtectPoint software package to a local directory.

3. Unpack the ProtectPoint software package.

a. Run the following command for Linux:gunzip ppfsagent31_<platform>.tar.gz

b. Run the following command for UNIX:tar xf ppfsagent31_<platform>.tar

4. Install the EMC ProtectPoint software using the native OS packaging software.



Procedure

1. Make a copy of the protectpoint.config.template.rp configuration file. Thedefault configuration file name is protectpoint.config. Create one or moreconfiguration files as needed. For example:




Note




l GeneralThe general information section contains information about the protected arraytype, the file system agent application, the path for the RSA lockbox, catalog, andlog files.

l Primary systemThe primary system section contains information associated with the primary DataDomain storage system used in the workflow.

l Secondary system


Installing the ProtectPoint file system agent on a Linux or UNIX host 73

Note

This section is required to restore from backups stored on a secondary DataDomain system.

The secondary system section contains information associated with restores andMTree replication between the primary Data Domain system and the secondaryData Domain system.

l RecoverPoint clusterThe RecoverPoint cluster section contains information associated with the primaryRecoverPoint cluster used in the workflow.

l Backup source devicesThe information in the backup source devices section of the configuration filecontains information identifying the production devices (holding the database toback up).







PP_ARRAY_TYPE =RP

Defines theconfiguration file asa ProtectPoint withRecoverPointconfiguration file.

Mandatory.


Application name onthe AR hostcontaining the datathat will be backedup.

Optional. When the data is backed up,this information is written to the DataDomain device-group and the static-image properties.


Application version. Optional. When the data is backed up,this information is written to the DataDomain device-group and the static-image properties.








LOCKBOX_DIR =path


Optional. By default, the ProtectPoint filesystem agent saves the RSA lockbox fileas protectpoint.clb in the lockboxsubdirectory within the ProtectPointinstall directory.

LOG_DIR = path Log directory. Optional. By default, the ProtectPoint filesystem agent saves the catalog files inthe logs subdirectory within the

ProtectPoint install directory.

DEBUGLEVEL = loglevel

Log level. Optional. By default, the log level valueis 2. The possible values are:

1: Error






Optional. By default, the maximum logfile size is 4 MB.



Optional. By default, 16 files areretained.



Key-value pair Description Mandatory or optional:additional information


Hostname or IP address of theprimary Data Domain systemused for backup.

Mandatory.

Note

To use IPv6, specify thehostname of the DataDomain system in theconfiguration file insteadof the IP address.

DD_PORT = port-number

Port number used to connect tothe primary Data Domainsystem.

Optional. By default, theport number is 3009.


Owner of the ProtectPoint poolon the primary Data Domainsystem.

Mandatory. This value isalso used for DD Boostoperations unless





DDBOOST_USER is alsospecified.

DD_POOL = pool-name Name of the ProtectPointrestore pool on the primaryData Domain system.

Mandatory.


Name of the ProtectPointrestore device-group on theprimary Data Domain system.

Mandatory.


The username associated withDD Boost on the primary DataDomain system.

Mandatory.


The name of the storage unit ora top-level directory within theprimary Data Domain where theProtectPoint catalog ismaintained.

Mandatory.


This section is required for restore from the secondary Data Domain system.




Hostname or IP address of thesecondary Data Domain systemused for backup.

Mandatory.

Note



Port number used to connect tothe secondary Data Domainsystem.



Owner of the ProtectPoint poolon the secondary Data Domainsystem.

Mandatory. This value isalso used for DD Boostoperations unlessDDBOOST_USER is alsospecified.

DD_POOL = pool-name Name of the ProtectPointrestore pool on the secondaryData Domain system.

Mandatory.






Name of the ProtectPointrestore device-group on thesecondary Data Domainsystem.

Mandatory.


The username associated withDD Boost on the secondaryData Domain system.

Mandatory.


The name of the storage unit ora top-level directory within thesecondary Data Domain wherethe ProtectPoint catalog ismaintained.

Mandatory.

d. Modify the content in the RecoverPoint cluster section.

Table 23 Primary RecoverPoint cluster section

Key-value pair Description Mandatory oroptional:additionalinformation

RP_MGMT = rpmanagementhostname/ip-address

Hostname or IP address of thePrimary RecoverPoint cluster usedfor backup.

Mandatory.

RP_USER = rpappliance username

Username for the PrimaryRecoverPoint cluster used forbackup.

Mandatory.

e. Modify the content in the Backup source devices section.


Table 24 Backup source devices section


SRC_DEVICE<n> =WWN

WWNs of the primarystorage devices. Place eachdevice on a separate line.

Mandatory. Specify one WWNfor each source device to beprotected.

f. (Optional) Modify the content in the Restore source devices section.



Note

This section is only required if more than one device must be specified.


Table 25 Restore source devices section (Optional)


SRC_DEVICE<n> =WWN


Optional. Specify a subset ofthe backup source devices torestore.

The following example shows a sample configuration file.

####################################################################### ProtectPoint 3.1 example config file# Indentation used for readability## THIS IS JUST A SAMPLE AND MUST BE MODIFIED TO SUIT YOUR ENVIRONMENT######################################################################## Mandatory - ProtectPoint environment for RP configuration[GENERAL] # Mandatory, no default value - ProtectPoint Array Type, RP=RecoverPoint # Do NOT change this value PP_ARRAY_TYPE=RP









##################### Primary Data Domain ################################## Mandatory - The Primary Data Domain system where RecoverPoint-managed devices will be backed up to[PRIMARY_SYSTEM] # Mandatory, no default value - The Primary Data Domain Boost hostname or IP # If DD_BOOST_FC is set to true, DD_SYSTEM is the name of the Data Domain Fiber



Channel server DD_SYSTEM = <Hostname/IP>




# Mandatory, no default value - The Primary Data Domain # pool name containing vdisk devices used for restore RESTORE_DEVICE_POOL = <Pool name>

# Mandatory, no default value - The Primary Data Domain device group used for vdisk restore RESTORE_DEVICE_GROUP = <Device group name>








# Mandatory, no default value - The Secondary Data Domain # pool name containing vdisk devices used for restore # RESTORE_DEVICE_POOL = <Pool name>

# Mandatory, no default value - The Secondary Data Domain device group used for vdisk restore # RESTORE_DEVICE_GROUP = <Device group name>






########### RecoverPoint Cluster and RecoverPoint Devices ######################### Mandatory - RecoverPoint cluster and RecoverPoint device information[RP_CLUSTER_1] # Mandatory, no default value - The RecoverPoint management hostname or IP RP_MGMT_HOST = <Hostname/IP>

# Mandatory, no default value - The RecoverPoint admin username RP_USER = <Username>

# Mandatory - The RecoverPoint device information section[BACKUP_SOURCE_DEVICES] # Mandatory, no default value - The RecoverPoint-managed production device WWN SRC_DEVICE1 = <Device WWN>

# Optional - Additional RecoverPoint device information # SRC_DEVICEn = <Device WWN>

# Optional - A subset of the source devices that will be restored during the "restore prepare" and "rollback" operations.# [RESTORE_SOURCE_DEVICES] # Optional, no default value - The RecoverPoint-managed production device WWN # SRC_DEVICE1 = <Device WWN> # SRC_DEVICEn = <Device WWN>

2. Store the block services for ProtectPoint user credentials securely.


Note




protectpoint security add dd-credentials dd-system primary vdisk3. Store the DD Boost user credentials securely.


Note




protectpoint security add dd-credentials dd-system primary boost4. Store the RecoverPoint user credentials securely.



Run the following command:protectpoint security add rp-credentials rp-cluster[<RP_cluster_X>]protectpoint security add rp-credentials rp_cluster_1

Verify the ProtectPoint installationValidate the content and format of the configuration file modified when the ProtectPointfile system agent was set up on the AR host.

Procedure

1. Log in to the AR host as a system administrator, such as root for Linux or UNIXsystems.




protectpoint config validateValidating application settings.........................[OK]Validating host requirements............................[OK]Validating Primary System: VDisk Connection Information........................[OK] Boost Connection Information........................[OK] DD Boost Path.......................................[OK] DD Restore Pool.....................................[OK] DD Restore Group....................................[OK]Validating RP Management: [lfcp0247.lss.emc.com] Connection Information.......[OK]Validating RP Devices: RP Device 514F0C56C06001CE..........................[OK] RP Device 514F0C56C06001CF..........................[OK] RP Device 514F0C56C06001D0..........................[OK] RP Device 514F0C56C06001D1..........................[OK] RP Device 514F0C56C06001D2..........................[OK]


a. Log in to the application host as a system administrator, such as root for Linux orUNIX systems.


c. Use the ProtectPoint file system agent to take a snapshot of the primary storagedevices.

Run the following command:protectpoint snapshot create description "<description>"protectpoint snapshot create description "protectpoint-rp-test-snap"

d. Run the appropriate host-specific command to unquiesce the application.

e. Display the status of the backup.

Run the following command:



protectpoint backup show list


f. Use the ProtectPoint file system agent to create the backup on the Data Domainsystem.


Note



Note


g. Verify the backup status is complete.





CHAPTER 7

Setting Up the ProtectPoint File System Agent forRecoverPoint on Windows Hosts


l Setting up the ProtectPoint file system agent with RecoverPoint............................ 84l Installing the ProtectPoint file system agent on a Windows host............................ 85l Modifying the ProtectPoint configuration file......................................................... 86l Verify the ProtectPoint installation........................................................................ 93

Setting Up the ProtectPoint File System Agent for RecoverPoint on Windows Hosts 83

Setting up the ProtectPoint file system agent with RecoverPointYou must install any primary storage-specific host software required by the file systemagent, and the file system agent 3.1 package on the AR host. You must also create one ormore file system agent configuration files for the applications being protected, save theData Domain and RecoverPoint credentials securely on the host, and validate theconfiguration and connectivity.

Before you begin


l Connectivity is established for the primary storage system, the Data Domain system,and the AR host.


l You have provisioned devices on the primary storage system and the Data Domainsystem, as applicable. The EMC ProtectPoint Primary and Protection StorageConfiguration Guide provides more information about storage provisioning.


The following figure shows an example where three ProtectPoint configuration files arerequired for three separate protected applications.Figure 16 Multiple configuration files for multiple applications

The setup process consists of three main tasks:



3. Enter the appropriate usernames and passwords to allow connectivity between theAR host, Data Domain system, RecoverPoint appliance, and XtremIO cluster.



Setting Up the ProtectPoint File System Agent for RecoverPoint on Windows Hosts



Installing the ProtectPoint file system agent on a Windows hostBefore you begin

The Windows installer is signed with a certificate. Click Package Properties > DigitalSignature to view the digital signature of the installer.

Note


Procedure


2. Copy the ProtectPoint installer to a local directory.

3. Double-click the ProtectPoint executable to launch the installer.

4. Click Next.

5. Select I accept the terms in the License Agreement and click Next.

6. Click Next to accept the default installation directory.

7. Click Install.

8. Click Finish.

Note

The ProtectPoint installer for Windows does not automatically create the ProtectPointconfiguration file, protectpoint.config.

9. Create the ProtectPoint configuration file, protectpoint.config.

Note

Do not use the protectpoint.config.template.rp file as the configuration

file without making a copy of it and changing the filename.

a. Navigate to the install directory and make a copy of theprotectpoint.config.template.rp file.

b. Rename the new copy as protectpoint.config.

Note the following considerations for working with the configuration file in aWindows environment:

l Save the configuration file in ANSI format.

l IPv6 IP addresses are not supported.


Installing the ProtectPoint file system agent on a Windows host 85



Procedure

1. Make a copy of the protectpoint.config.template.rp configuration file. Thedefault configuration file name is protectpoint.config. Create one or moreconfiguration files as needed. For example:




Note




l GeneralThe general information section contains information about the protected arraytype, the file system agent application, the path for the RSA lockbox, catalog, andlog files.

l Primary systemThe primary system section contains information associated with the primary DataDomain storage system used in the workflow.

l Secondary system

Note

This section is required to restore from backups stored on a secondary DataDomain system.

The secondary system section contains information associated with restores andMTree replication between the primary Data Domain system and the secondaryData Domain system.

l RecoverPoint clusterThe RecoverPoint cluster section contains information associated with the primaryRecoverPoint cluster used in the workflow.

l Backup source devicesThe information in the backup source devices section of the configuration filecontains information identifying the production devices (holding the database toback up).









PP_ARRAY_TYPE =RP

Defines theconfiguration file asa ProtectPoint withRecoverPointconfiguration file.

Mandatory.


Application name onthe AR hostcontaining the datathat will be backedup.



Application version. Optional. When the data is backed up,this information is written to the DataDomain device-group and the static-image properties.




LOCKBOX_DIR =path


Optional. By default, the ProtectPoint filesystem agent saves the RSA lockbox fileas protectpoint.clb in the lockboxsubdirectory within the ProtectPointinstall directory.

LOG_DIR = path Log directory. Optional. By default, the ProtectPoint filesystem agent saves the catalog files inthe logs subdirectory within the

ProtectPoint install directory.

DEBUGLEVEL = loglevel

Log level. Optional. By default, the log level valueis 2. The possible values are:

1: Error






Optional. By default, the maximum logfile size is 4 MB.







Optional. By default, 16 files areretained.





Hostname or IP address of theprimary Data Domain systemused for backup.

Mandatory.

Note



Port number used to connect tothe primary Data Domainsystem.



Owner of the ProtectPoint poolon the primary Data Domainsystem.


DD_POOL = pool-name Name of the ProtectPointrestore pool on the primaryData Domain system.

Mandatory.


Name of the ProtectPointrestore device-group on theprimary Data Domain system.

Mandatory.


The username associated withDD Boost on the primary DataDomain system.

Mandatory.


The name of the storage unit ora top-level directory within theprimary Data Domain where theProtectPoint catalog ismaintained.

Mandatory.


This section is required for restore from the secondary Data Domain system.






Hostname or IP address of thesecondary Data Domain systemused for backup.

Mandatory.

Note



Port number used to connect tothe secondary Data Domainsystem.



Owner of the ProtectPoint poolon the secondary Data Domainsystem.


DD_POOL = pool-name Name of the ProtectPointrestore pool on the secondaryData Domain system.

Mandatory.


Name of the ProtectPointrestore device-group on thesecondary Data Domainsystem.

Mandatory.


The username associated withDD Boost on the secondaryData Domain system.

Mandatory.


The name of the storage unit ora top-level directory within thesecondary Data Domain wherethe ProtectPoint catalog ismaintained.

Mandatory.

d. Modify the content in the RecoverPoint cluster section.

Table 29 Primary RecoverPoint cluster section


RP_MGMT = rpmanagementhostname/ip-address

Hostname or IP address of thePrimary RecoverPoint cluster usedfor backup.

Mandatory.



Table 29 Primary RecoverPoint cluster section (continued)


RP_USER = rpappliance username

Username for the PrimaryRecoverPoint cluster used forbackup.

Mandatory.

e. Modify the content in the Backup source devices section.


Table 30 Backup source devices section


SRC_DEVICE<n> =WWN


Mandatory. Specify one WWNfor each source device to beprotected.

f. (Optional) Modify the content in the Restore source devices section.

Note

This section is only required if more than one device must be specified.


Table 31 Restore source devices section (Optional)


SRC_DEVICE<n> =WWN


Optional. Specify a subset ofthe backup source devices torestore.

The following example shows a sample configuration file.

####################################################################### ProtectPoint 3.1 example config file# Indentation used for readability## THIS IS JUST A SAMPLE AND MUST BE MODIFIED TO SUIT YOUR ENVIRONMENT######################################################################## Mandatory - ProtectPoint environment for RP configuration[GENERAL] # Mandatory, no default value - ProtectPoint Array Type, RP=RecoverPoint



# Do NOT change this value PP_ARRAY_TYPE=RP









##################### Primary Data Domain ################################## Mandatory - The Primary Data Domain system where RecoverPoint-managed devices will be backed up to[PRIMARY_SYSTEM] # Mandatory, no default value - The Primary Data Domain Boost hostname or IP # If DD_BOOST_FC is set to true, DD_SYSTEM is the name of the Data Domain Fiber Channel server DD_SYSTEM = <Hostname/IP>




# Mandatory, no default value - The Primary Data Domain # pool name containing vdisk devices used for restore RESTORE_DEVICE_POOL = <Pool name>

# Mandatory, no default value - The Primary Data Domain device group used for vdisk restore RESTORE_DEVICE_GROUP = <Device group name>



# Optional, default is false. Indicates whether restore devices to be selected must



be visible to the host. # SELECT_VISIBLE_RESTORE_DEVICES = TRUE





# Mandatory, no default value - The Secondary Data Domain # pool name containing vdisk devices used for restore # RESTORE_DEVICE_POOL = <Pool name>

# Mandatory, no default value - The Secondary Data Domain device group used for vdisk restore # RESTORE_DEVICE_GROUP = <Device group name>




########### RecoverPoint Cluster and RecoverPoint Devices ######################### Mandatory - RecoverPoint cluster and RecoverPoint device information[RP_CLUSTER_1] # Mandatory, no default value - The RecoverPoint management hostname or IP RP_MGMT_HOST = <Hostname/IP>

# Mandatory, no default value - The RecoverPoint admin username RP_USER = <Username>

# Mandatory - The RecoverPoint device information section[BACKUP_SOURCE_DEVICES] # Mandatory, no default value - The RecoverPoint-managed production device WWN SRC_DEVICE1 = <Device WWN>

# Optional - Additional RecoverPoint device information # SRC_DEVICEn = <Device WWN>

# Optional - A subset of the source devices that will be restored during the "restore prepare" and "rollback" operations.# [RESTORE_SOURCE_DEVICES] # Optional, no default value - The RecoverPoint-managed production device WWN # SRC_DEVICE1 = <Device WWN> # SRC_DEVICEn = <Device WWN>



2. Store the block services for ProtectPoint user credentials securely.


Note




protectpoint security add dd-credentials dd-system primary vdisk3. Store the DD Boost user credentials securely.


Note




protectpoint security add dd-credentials dd-system primary boost4. Store the RecoverPoint user credentials securely.

Run the following command:protectpoint security add rp-credentials rp-cluster[<RP_cluster_X>]protectpoint security add rp-credentials rp_cluster_1

Verify the ProtectPoint installationValidate the content and format of the configuration file modified when the ProtectPointfile system agent was set up on the AR host.

Procedure





protectpoint config validate



Validating application settings.........................[OK]Validating host requirements............................[OK]Validating Primary System: VDisk Connection Information........................[OK] Boost Connection Information........................[OK] DD Boost Path.......................................[OK] DD Restore Pool.....................................[OK] DD Restore Group....................................[OK]Validating RP Management: [lfcp0247.lss.emc.com] Connection Information.......[OK]Validating RP Devices: RP Device 514F0C56C06001CE..........................[OK] RP Device 514F0C56C06001CF..........................[OK] RP Device 514F0C56C06001D0..........................[OK] RP Device 514F0C56C06001D1..........................[OK] RP Device 514F0C56C06001D2..........................[OK]


a. Log in to the application host as a system administrator, such as root for Linux orUNIX systems.


c. Use the ProtectPoint file system agent to take a snapshot of the primary storagedevices.


d. Run the appropriate host-specific command to unquiesce the application.

e. Display the status of the backup.



f. Use the ProtectPoint file system agent to create the backup on the Data Domainsystem.


Note



Note


g. Verify the backup status is complete.




CHAPTER 8

ProtectPoint Administration


l ProtectPoint administration overview.................................................................... 98l ProtectPoint file system agent............................................................................... 98

ProtectPoint Administration 97

ProtectPoint administration overviewThe application administrator typically performs the following tasks by using theProtectPoint configuration file and ProtectPoint commands:

l Backing up data

l Restoring data (object-level restore or a full-application rollback restore)

l Listing and deleting backups

l Rebuilding (refreshing) the catalog

Application changesIf the storage resources used by an application are changed (for example, by adding ordeleting LUNs), verify that these changes on the primary storage are mirrored on theprotection storage (and, in ProtectPoint for RecoverPoint, on the RecoverPoint appliance).The following issues may occur if changes are not accurately reflected across theProtectPoint implementation:

l Unneeded data may continue to get backed up and consume available storage at ahigher-than-expected rate

l Data on LUNs added to the environment but not to the ProtectPoint configurationmight not get backed up.

ProtectPoint file system agentThis section describes how to perform backup and recovery tasks with the ProtectPointfile system agent.

Note


Specifying the ProtectPoint configuration fileYou can specify the ProtectPoint configuration file in one of the following ways:

l Use the config-file keyword and the file-path argument with the protectpointcommand to use your modified configuration file.

l Use the environment variable, PP_CONFIG_FILE.

l Use the default configuration file, protectpoint.config, in the current workingdirectory.

Performing a backup of ProtectPoint with VMAXBefore you begin

Create a new SnapVX snapshot before you perform a backup operation to ensure that themost recent changes to the source devices are backed up.



Note

VMAX symsnapvx commands are asynchronous. Verify that all symsnapvx link -copy operations are complete before you perform a backup; otherwise the backup will

fail.

In this procedure, the application administrator uses a combination of the application orhost-specific commands and the ProtectPoint file system agent to back up the data.The first time a backup is performed, the entire source or production LUN is backed up.For subsequent backups, only the changed data is backed up, that is, the backups areincremental at the block level. However, if the SnapVX session has to be re-created aftera restore operation that overwrites the original source devices, the next backup operationwill include the entire source production LUN.

The ProtectPoint file system agent creates snapshots on the VMAX array as part of thebackup operation. These snapshots are named NSM_SNAPVX. ProtectPoint manages thegenerations of the VMAX SnapVX snapshot named NSM_SNAPVX according to theexisting VMAX backup and snapshot schedules.

Note

Do not manually create any SnapVX snapshots named NSM_SNAPVX. ProtectPoint will

terminate all snapshots with this name.

The protectpoint backup create command relinks the FAST.X LUN associatedwith the source LUN with the most recent generation snapshot (gen0) created by thesnapshot create command , and deletes the previously linked snapshot. When theoperation is complete, only one NSM_SNAPVX snapshot should exist for each primarystorage device in the ProtectPoint configuration. Other than the requirements relating tothe name of the NSM_SNAPVX snapshot, this snapshot can be treated as a normal VMAXsnapshot.

Procedure


2. Run the appropriate host-specific command to quiesce the application.

3. Establish the relationship between the VMAX array and Data Domain system, andactivate the snapshot.


symsnapvx -sid 0129 -sg storage-group-5 establish -name dg5-snap4. Move the data from the VMAX array on to the Data Domain system. This command

moves the changed blocks on the source device to the target device.


5. Check the status of the link copy operation, and wait for it to complete.

VMAX symsnapvx commands are asynchronous. Verify that all symsnapvx link-copy operations are complete before you perform a file system agent backup;


Performing a backup of ProtectPoint with VMAX 99

otherwise the backup will fail. The operations are complete when the commandindicates the link status is destaged. Run the following command:symsnapvx -sid <SymmetrixID> list -sg <storage-group> -linkedsymsnapvx -sid 0129 -sg storage-group-5 -linked

6. Use the ProtectPoint file system agent to take a snapshot of the devices holding thedata on the VMAX array.


Note

Do not run concurrent snapshot create operations on the same set of VMAX devices,as it will create a new snapshot for each additional snapshot create operation.

protectpoint snapshot create description "ProductionBackup" config-file protecpoint.config7. Use the ProtectPoint file system agent to create a backup on the Data Domain system

of the SnapVX snapshot created above.

Run the following command:protectpoint backup create backup-id <backup-id> config-file<file-path>


Note

If system displays the error message "SYMAPI_C_SNAPSHOT_NOT_FOUND", one or

more of the source LUNs being operated on is missing its required NSM SnapVXsnapshot. Create the required snapshot and retry the backup operation.

If you type Ctrl + C to abort a backup, the FAST.X devices associated with thesource devices on the VMAX may remain in a locked state. This will cause subsequentbackups of these devices to fail with the error message Create backup failed:Error relinking snapvx snapshot to target: Unable to performaction Relink on SnapVX snapshot, errorSYMAPI_C_DEV_LOCK_CANT_ACQUIRE, devices: <device-count>,first device <VMAX-ID:Device-ID>, name [NSM_SNAPVX]. Completethe following steps to determine if the VMAX devices are locked and release the locks.

a. Run the following command to list all the locked VMAX devices:symdev list -locksymdev list -lock

b. Run the following command to unlock the VMAX devices:symdev release -lock -nop -sid <SymmetrixID>symdev release -lock -nop -sid 0129

Restoring a VMAX backupBefore you begin

Obtain the ProtectPoint backup ID and the location, on the primary or secondary DataDomain system, for the backup you want to restore.



Note

When restoring backups using FAST.X, the Data Domain restore devices must beencapsulated on the VMAX array before attempting the restore operation. Encapsulationis not required when restoring directly from the Data Domain restore devices.

In this procedure, the application administrator uses a combination of the application orhost-specific commands and the ProtectPoint file system agent to restore the data.

Procedure


2. View the list of backups previously completed on the primary or secondary DataDomain systems.

Run the following command:protectpoint backup show list [dd-system {primary |secondary}] [{last <n> {count | days | weeks | months}} |{from <MMDDhhmm> [[<CC>] <YY >] [to <MMDDhhmm> [[<CC>]<YY> ]]}] [status {complete | snap-ready | in-progress |restore-ready | rollback | failed | suspect }] [config-file<file-path>]

If you do not specify any of the optional keywords, the system displays informationabout all backups. To limit the output, use one of the available filters. For example:

protectpoint backup show list last 2 days3. Prepare the selected backup for restore on the Data Domain system.

Note

The protectpoint restore prepare command:

l Overwrites the contents of the encapsulated restore devices with the specifiedbackup.

l Gives the AR host read/write access to the restore devices. Do not use thesedevices for anything except ProtectPoint restore operations.

l If there are devices specified in the Restore source devices section of theconfiguration file, protectpoint restore prepare will only prepare the

specified devices.

Run the following command:protectpoint restore prepare backup-id <backup-id> [dd-system {primary | secondary}] [config-file <file-path>][host <hostname> | scan]protectpoint restore prepare backup-id 1454601272 config-file protectpoint.config

The protectpoint restore prepare command completes the followingactions depending on whether the data is being restored from FAST.X-encapsulateddevices, or directly from Data Domain devices:

l For restores from FAST.X devices, protectpoint restore prepare writesthe backup image to a FAST.X-encapsulated restore device in the VMAX storagegroup specified in the ProtectPoint configuration file.


Restoring a VMAX backup 101

l For restores directly from Data Domain restore devices, protectpointrestore prepare writes the data from the backup image to a Data Domainrestore device in the device-group specified in the ProtectPoint configuration file.

4. Choose the type of restore operation to perform, and follow the appropriate steps.

Object-level restore from FAST.X-encapsulated devices with SnapVX

Complete the following steps for an object-level restore.

Procedure

1. Use the application or host-specific tools or commands and Solutions Enabler tomount the VMAX restore devices on the AR host.

2. Use the application or host-specific tool or commands to identify and restore theobject-level data as appropriate.

Object-level restore from Data Domain restore devices

Complete the following steps for an object-level restore.

Procedure

1. Use the application or host-specific tools or commands to mount the Data Domainrestore devices on the AR host.

2. Use the application or host-specific tool or commands to identify and restore theobject-level data as appropriate.

Full-application rollback restore from FAST.X-encapsulated devices with SnapVX

Complete the following steps for a full-application rollback restore. This operationoverwrites the contents of the target LUNs.

Note

Full-application rollback restores can only be completed using FAST.X devices. Therollback operation will fail if the configuration file specifies Data Domain restore devices.

If SRDF is configured on the VMAX array, be aware of the following considerations beforeinitiating a full-application rollback restore:

l After the restore is complete, the SRDF link between the primary VMAX array, and theremote VMAX array must be re-established.

l After a full-application rollback restore, initiating a full backup will trigger a full SRDFreplication.

Procedure

1. Shut down all applications and unmount/deport all LVM structures that access theproduction devices.

2. Make the production devices unavailable to users.

3. Use the application or host-specific tools or commands and Solutions Enabler toprovision and mount the encapsulated restore devices on the AR host.

4. Use the application or host-specific tool or commands to restore the data back to theoriginal production devices.

5. Use Solutions Enabler to present the newly restored source devices to the host if theyare not already masked, and import LVM structures as needed.

6. Recover the application, and perform any appropriate application-specific validation.



Note

For environments that use SRDF, the first full backup after a full restore triggers a fullSRDF replication.

Restore directly to the host from FAST.X-encapsulated devices.

Complete the following steps to restore directly to the AR host from FAST.X-encapsulateddevices:

Procedure

1. Use the application or host-specific tools or commands and Solutions Enabler tomount the FAST.X-encapsulated Data Domain restore devices on the AR host.

2. Use the application or host-specific tool or commands to identify and restore data asappropriate.

Rollback restore

Complete the following steps for a rollback restore:

Note

During an active rollback operation, do not run commands that scan the primary storagedevices, including, but not limited to symcfg discover, inquiry, and LVM rescan.

If SRDF is configured on the VMAX array, the SRDF link between the primary VMAX array,and the remote VMAX array must be re-established after the rollback is complete.

If there are devices specified in the Restore source devices section of the configurationfile, protectpoint restore prepare will only prepare the specified devices.

Procedure

1. Shut down all applications and unmount/deport all LVM structures that access theproduction devices.

2. Make the production devices unavailable to users.

3. Use the application or host-specific tools or commands and Solutions Enabler tomount the encapsulated restore devices on the AR host.

4. Run the protectpoint rollback command to restore the production devicesfrom the specified backup.

When the rollback operation starts, the catalog entry for the backup being restoredchanges from complete to rollback. If the protectpoint rollback commandfails, the backup remains in the rollback state and cannot be used for otheroperations. Run the protectpoint rollback backup-id <backup-id> resetcommand to set the catalog state back to complete.

5. Use Solutions Enabler to present the newly restored source devices to the host if theyare not already masked, and import LVM structures as needed.

6. Recover the application, and perform any appropriate application-specific validation.

Restoring a backup to a different VMAX array

It is possible to restore a backup stored on the Data Domain system to a different VMAXarray. Complete the following steps.


Restoring a VMAX backup 103

Procedure

1. Configure SAN zoning so the Data Domain system can communicate with the newVMAX array.

2. If necessary, set up the ProtectPoint file system agent on a new host that has accessto the new VMAX array as described in Setting up the ProtectPoint file system agentwith VMAX on page 32.

3. If necessary, create new block services for ProtectPoint devices on the Data Domainsystem as described in the EMC ProtectPoint Primary and Protection StorageConfiguration Guide.

4. Encapsulate the restore target devices on the new VMAX array as described in the EMCProtectPoint Primary and Protection Storage Configuration Guide.

5. Complete the following changes in the ProtectPoint configuration file.

a. Specify the Symmetrix ID for the new VMAX array as the primary restoredestination.

b. If the original VMAX array is inaccessible to the host where the restore operation isbeing performed, comment out the backup devices in the configuration file.

Modifying the ProtectPoint configuration file on page 33 provides more informationabout editing the ProtectPoint configuration file.

6. If necessary, copy the ProtectPoint configuration file to the new host.

7. Update the ProtectPoint catalog as described in Rebuilding the ProtectPointcatalog on page 113.

8. Verify the required backup appears as described in Rebuilding the ProtectPointcatalog on page 113.

9. Initiate the restore operation as described in Restoring a VMAX backup on page 100.

Performing a backup of ProtectPoint with RecoverPointIn this procedure, the application administrator uses a combination of the application orhost-specific commands and the ProtectPoint file system agent to back up the data.The first time a backup is performed, the entire source or production LUN is backed up.For subsequent backups, only the changed data is backed up; that is, the backups areincremental at the block level.

A ProtectPoint with RecoverPoint file system agent backup is not application-consistentunless the application and the file system are prepared for backup before starting thebackup operation.

Procedure

1. Log in to the application host as a system administrator, such as root for Linuxsystems.

2. Run the appropriate host-specific command to quiesce the application.

3. Use the ProtectPoint file system agent to take a snapshot of the devices holding thedata.


4. Run the appropriate host-specific command to unquiesce the application.



5. Display the status of the backup.



6. Use the ProtectPoint file system agent to create the backup on the Data Domainsystem.


Note

The backup ID is displayed by the protectpoint snapshot create command.


7. Verify the backup status is complete.



Restoring a RecoverPoint backupBefore you begin

l Obtain the ProtectPoint backup ID and the location, on the primary or secondary DataDomain system, for the backup you want to restore.

l Configure the ProtectPoint restore devices and mask them to the AR host.

Procedure

1. Log in to the AR host as a system administrator, such as root for Linux systems.

2. View the list of backups previously completed on the primary or secondary DataDomain systems.

Run the following command:protectpoint backup show list [dd-system {primary |secondary}] [{last <n> {count | days | weeks | months}} |{from <MMDDhhmm> [[<CC>] <YY >] [to <MMDDhhmm> [[<CC>]<YY> ]]}] [status {complete | snap-ready | in-progress |restore-ready | rollback | failed | suspect }] [config-file<file-path>]

If you do not specify any of the optional keywords, the system displays informationabout all backups. To limit the output, use one of the available filters. For example:

protectpoint backup show list last 2 days3. Prepare the selected backup for restore on the Data Domain system.


Restoring a RecoverPoint backup 105

Note

The protectpoint restore prepare command:

l Overwrites the contents of the restore devices with the specified backup.

l Gives the AR host read/write access to the restore devices. Do not use thesedevices for anything except ProtectPoint restore operations.

l If there are devices specified in the Restore source devices section of theconfiguration file, protectpoint restore prepare will only prepare the

specified devices.

Run the following command:protectpoint restore prepare backup-id <backup-id> [dd-system {primary | secondary}] [host <hostname> | scan]

Note

The following output requires the SELECT_VISIBLE_RESTORE_DEVICES directive

in the configuration file to be set to TRUE. If the directive is set to the default value of

FALSE, the protectpoint restore prepare command will not display the

WWNs of the source and target devices.

protectpoint restore prepare backup-id 1445602842protectpoint restore prepare backup-id 1464286066

*** Using RP config file "/root/smoketest/protectpoint.config" ***Preparing backup-id [1464286066] to be ready for restore################################The following devices are ready to be usedSource: 514f0c54ea6000be Target: /dev/sdhh 60021880004d6001a205683e5d5000ffSource: 514f0c54ea6000af Target: /dev/sdhj 60021880004d6001a205683e5d500101Source: 514f0c54ea6000b8 Target: /dev/sdhi 60021880004d6001a205683e5d500100Source: 514f0c54ea6000b9 Target: /dev/sdhw 60021880004d6001a205683e5d50010eSource: 514f0c54ea6000ba Target: /dev/sdhk 60021880004d6001a205683e5d500102Source: 514f0c54ea6000bb Target: /dev/sdhm 60021880004d6001a205683e5d500104Source: 514f0c54ea6000bc Target: /dev/sdhl 60021880004d6001a205683e5d500103Source: 514f0c54ea6000bd Target: /dev/sdhv 60021880004d6001a205683e5d50010dSource: 514f0c54ea6000b0 Target: /dev/sdhn 60021880004d6001a205683e5d500105Source: 514f0c54ea6000b1 Target: /dev/sdhp 60021880004d6001a205683e5d500107Source: 514f0c54ea6000b2 Target: /dev/sdho 60021880004d6001a205683e5d500106Source: 514f0c54ea6000b3 Target: /dev/sdhu 60021880004d6001a205683e5d50010cSource: 514f0c54ea6000b4 Target: /dev/sdhq 60021880004d6001a205683e5d500108Source: 514f0c54ea6000b5 Target: /dev/sdht 60021880004d6001a205683e5d50010bSource: 514f0c54ea6000b6 Target: /dev/sdhs 60021880004d6001a205683e5d50010aSource: 514f0c54ea6000b7 Target: /dev/sdhr 60021880004d6001a205683e5d500109



Updated the catalog record for backup-id [1464286066] from state "complete" to "restore-ready"

Note

If the catalog was not replicated to the secondary Data Domain system, a backupcannot be restored from the secondary Data Domain system.

The protectpoint restore prepare command writes the data from thebackup image to a Data Domain restore device in the device-group specified in theProtectPoint configuration file. When the command is complete, the status of thebackup changes to restore-ready.

4. Select and perform the appropriate type of restore:

l Perform an object-level restore by using the physical device pathnames displayedby the protectpoint restore prepare command. Use the application orhost-specific tool or commands to identify and restore the object-level data asappropriate.

l Perform a rollback restore by specifying a backup ID to use with theprotectpoint rollback command.If there are devices specified in the Restore source devices section of theconfiguration file, protectpoint restore prepare will only prepare thespecified devices.

Note

During an active rollback operation, do not run commands that scan the primarystorage devices, including, but not limited to symcfg discover, inquiry, and

LVM rescan.

When the rollback operation starts, the catalog entry for the backup being restoredchanges from complete to rollback. If the protectpoint rollback commandfails, the backup remains in the rollback state and cannot be used for otheroperations. Run the protectpoint rollback backup-id <backup-id> resetcommand to set the catalog state back to complete.

5. Reset the backup to a complete state.

Run the following command:protectpoint restore release backup-id <backup-id> [dd-system {primary|secondary}] [host <hostname> | scan]protectpoint restore release backup-id 1445602842Updated the catalog record with status as "complete"

The status of the backup changes to complete, and makes the restore devicesavailable for restore operations.

Restoring a backup from the secondary Data Domain system

Before you begin

l The AR host has access to the restore devices on the secondary Data Domain system.

Note

The ProtectPoint 3.1 Primary and Protection Storage Configuration Guide provides detailson creating the restore devices and presenting them to the AR host.

l Run the replication show config command to verify the Mtree replicationsession is configured on both the primary and secondary Data Domain systems.



Note

The ProtectPoint 3.1 Primary and Protection Storage Configuration Guide provides detailson configuring an MTree replication session between the primary and secondary DataDomain systems.

Procedure


2. Log in to an SSH session on the secondary Data Domain system.

3. On the secondary Data Domain system, verify the replicated backup pool and DDBoost storage-unit are set as RO/RD.

Run the following command:mtree list

4. Verify the catalog matches on both the primary and secondary Data Domain systems.

Run the following commands:

Note

It may take a few minutes for the backup data to fully replicate to the secondary DataDomain system.

a. protectpoint backup show list dd-system primaryb. protectpoint backup show list dd-system secondary

5. Register the replicated backup pool on the secondary Data Domain system.

Run the following command:vdisk pool register <pool-name> user <user-name>vdisk pool register backup-demo-1 user user1

6. Register the replicated DD Boost storage-unit on the secondary Data Domain system.

Run the following command:ddboost storage-unit modify <storage-unit name> user <user-name>

ddboost storage-unit modify RecoverPointStorageUnit user user17. Verify the secondary Data Domain system recognizes the replicated backup pool and

storage-unit as RO/RD.


a. vdisk pool show listb. ddboost storage unit show

8. Create and verify a new MTree with read/write permissions to copy the contents of theDD Boost storage-unit


a. mtree create /data/col1/<mtree-copy-name>mtree create /data/col1/copyMTree

b. mtree list



9. Copy the contents of the DD Boost storage-unit to the new MTree.

Run the following command:filesys fastcopy source /data/col1/<original-replicatedDDBoost storage-unit-name> destination /data/col1/<mtree-copy-name>

filesys fastcopy source /data/col1/RecoverPointStorageUnit destination /data/col1/copyMTree

10. Make the new copied MTree visible to the user and verify it displays as a DD Booststorage-unit.


a. ddboost storage-unit modify <storage-unit name> user<user-name>

ddboost storage-unit modify copyMTree user user1

b. ddboost storage-unit show11. Add the path to the newly created DD Boost storage-unit to the Secondary system

section of the ProtectPoint configuration file.

Note

Modifying the ProtectPoint configuration file on page 73 provides instructions onmodifying the ProtectPoint configuration file.

12. Validate the updated configuration file.

Run the following command:protectpoint config validate

13. Verify the catalog on both the primary and secondary Data Domain systems containsthe new DD Boost storage-unit.


Note

Because the contents of a replicated storage-unit were copied to a new storage-unit,additional replication sessions may be in progress to the replication destination.Therefore, the catalog on the primary Data Domain system may contain backups thatare not listed on the secondary Data Domain system.

a. protectpoint backup show list dd-system primaryb. protectpoint backup show list dd-system secondary

14. Set the restore devices on the secondary Data Domain system to a read-only state.

a. Identify the restore devices.

Run the following command:vdisk show list

b. Change the state for each restore device.

Run the following command:vdisk device modify <device-name> state read-onlyvdisk device modify vdisk-dev0 state read-only



15. Make the secondary Data Domain system restore devices ready on the AR host.

Run the following command:protectpoint restore prepare backup-id <backup-id> dd-systemsecondary [host <hostname> | scan]protectpoint restore prepare backup-id 1445602842 dd-system secondary

16. Verify the secondary catalog displays the desired backup as restore-ready.

Run the following command:protectpoint backup show list dd-system secondary

17. Mount the restore devices assigned by the protectpoint restore preparecommand, and restore files to the AR host as necessary.

Deleting a backupThe application administrator views the list of completed backups on the primary DataDomain system, and then deletes a specific backup, as appropriate.

Note

The [dd-system {primary | secondary}] option is not supported.

Procedure


2. Display the list of backups completed on the primary Data Domain system.

Run the following command:protectpoint backup show list [{last <n> {count | days |weeks | months}} | {from <MMDDhhmm> [[<CC>] <YY> ] [to<MMDDhhmm> [[< CC>] <YY> ]]}] [status {complete | snap-ready| in-progress | restore-ready | rollback | failed |suspect }] [config-file <file-path>]

protectpoint backup show list last 2 days3. (Optional) Display detailed information about a specific backup on the primary or

secondary Data Domain system.

Run the following command:protectpoint backup show detailed backup-id <backup-id> [dd-system {primary | secondary}] [config-file <file-path>]

Note

The backup start and backup end times reported by the protectpoint backupshow detailed command reflect the system time on the AR host. These times may

not match what is reported by the RecoverPoint cluster and Data Domain system. EMCrecommends using a time synchronization service on all systems in a ProtectPointenvironment to minimize this issue.

protectpoint backup show detailed backup-id 1461270787*** Using VMAX config file "c:\protectpoint.config" ***

Backup-id: 1461270787



Storage: VMAXBackup hostname: ledmf131Backup UUID: 1461270787Snapshot/Backup start time: Thu Apr 21 16:33:07 2016Backup end time: Thu Apr 21 16:33:25 2016Backup duration: 000:00:18Backup status: restore-readyBackup description: testing restore for vmaxConsistency Type: <not specified>Agent name: ProtectPointAgent version: 3.1.0.0-151Application info: FilesystemsApplication version: 3.1DD pool: <not specified>DD device group: <not specified>SYMID: 000196701031

Static images: Expected count: 3 Present in catalog: TRUE Present in DD system: TRUE (as of last catalog update)-------- ---------------------------------------- ----------Image Static-Image Present onSequence DD System-------- ---------------------------------------- ----------0 04000000905a056e1a04a02bad004200000002b0 yes1 04000000905a056e1a04a02baf004200000002ad yes2 04000000905a056e1a04a02bb1004200000002ae yes

4. Delete a specific backup from the primary Data Domain system.

Run the following command:protectpoint backup delete backup-id <backup-id > [force]protectpoint backup delete backup-id 1445602842

Note

Be aware of the following caveats when deleting a backup:

l ProtectPoint 3.1 will not delete an in-progress or restore-ready backup. To forciblydelete such backups, use the force option.

l If a backup was replicated more than once, or a static-image was copied manuallyusing the Data Domain CLI, the protectpoint backup delete command will

only delete an instance of the backup created by ProtectPoint. Rebuilding theProtectPoint catalog on page 113 describes how to update the catalog.

l If a backup crashed, static-images related to the failed backup ID may exist on theData Domain system. Update the catalog before deleting the failed backup. Rebuilding the ProtectPoint catalog on page 113 describes how to update thecatalog.

Scanning for and displaying arbitrary ProtectPoint backupsThe ProtectPoint file system agent provides the ability to scan the Data Domain systemfor all backups created by ProtectPoint applications, and place them into a scannedcatalog where they can be managed by the file system agent.

Creating the scan catalog

Be aware of the following considerations when creating the scan catalog:

l The scan catalog is maintained separately from the file system agent catalog.


Scanning for and displaying arbitrary ProtectPoint backups 111

l The scan catalog only contains the static-images owned by the block services forProtectPoint user specified in the file system agent configuration file.

Complete the following steps to create the scan catalog.

Procedure


2. Run the following command:

protectpoint backup scan [dd-system {primary | secondary}][config-file <file-path>]

Displaying static-images

The list of backups in the scan catalog can be optionally filtered by the followingparameters:

l Primary or secondary Data Domain system

l A specific configuration file

l A specific ProtectPoint agent or specific version of a ProtectPoint agent

l Block services for ProtectPoint pool and device-group

l Backup description

l A specific backup host

l A specific time range or timestamp

l Whether the backup is VMAX or RecoverPoint

Complete the following steps to scan the static-image metadata.

Procedure

1. Log in to the AR host as a system administrator, such as root for Linux systems.

2. Run the following command:

protectpoint backup show scan [help | ?] [dd-system {primary| secondary}] [config-file <file-path>] [filter<key=value>]..[filter <keyN=valueN>] [display<key1>[,<key2>,..<keyN>]]

C:\Users\Administrator>protectpoint backup show scan ?

Usage:protectpoint backup show scan [dd-system {primary | secondary}] [config-file <file-path>] [filter agent-name=<agent name>] [filter agent-version=<agent version>] [filter app-info=<application info>] [filter app-version=<application version>] [filter dd-pool=<dd pool name>] [filter dd-devgroup=<dd device group>] [filter description=<backup description>] [filter host=<host name>] [filter last="n {count | days | weeks | months}>"] [filter from=<backup start time {MMDDhhmm[[CC]YY]}>] [filter to=<backup end time {MMDDhhmm[[CC]YY]}>] [filter storage=<{RP| VMAX | ALL, default is ALL}>] [filter symid=<sym-id>] [display agent-name,agent-version,app-info,app-version,dd-pool,dd-devgroup,description,host,snapshot-time,storage,symid | ALL]

The scan option can be used with the following file system agent commands:



l protectpoint backup show detailedl protectpoint restore preparel protectpoint restore releasel protectpoint rollback

Rebuilding the ProtectPoint catalogThe ProtectPoint file system agent creates and maintains a DD Boost-based backupcatalog for each host and its associated configuration file. In normal operatingcircumstances, this catalog accurately reflects the backups available for restore on theprimary Data Domain system. In the rare circumstance that this catalog is deleted orbecomes corrupted, the catalog can be updated by reading the metadata in the blockservices for ProtectPoint objects on the primary Data Domain system. Theprotectpoint catalog update command updates the catalog.

Note

ProtectPoint file system agent 3.1 cannot migrate existing ProtectPoint 1.0 and 2.0catalogs.

The backup catalog showing the backups replicated to the secondary Data Domainsystem is not updated automatically, but can be created or refreshed by running theprotectpoint catalog update dd-system secondary command.

To rebuild (refresh) the catalog, complete the following steps.

Note

The catalog is rebuilt from Data Domain block services for ProtectPoint objects identifiedby information in the ProtectPoint configuration file.

Procedure


2. Create or rebuild (refresh) the backup catalog.

Run the following command:protectpoint catalog update [dd-system {primary |secondary}] [config-file <file-path>]protectpoint catalog update

Showing the ProtectPoint file system agent versionUse this task to view the version of the ProtectPoint file system agent.

Procedure


2. Show the ProtectPoint file system agent version in use.

Run the following command:protectpoint show version

<package name> version: 3.1.0.0-<build-number>


Rebuilding the ProtectPoint catalog 113

Upgrading the ProtectPoint file system agentThis section describes how to upgrade a previous version of the ProtectPoint file systemagent to a newer version.

l Upgrade file system agent 2.0 to file system agent 3.1 on page 114

l Upgrade file system agent 3.0 to file system agent 3.1 on page 116

Upgrading from file system agent 2.0 to file system agent 3.1

Complete the following steps to upgrade an instance of file system agent 2.0 to filesystem agent 3.1.

Procedure

1. Identify or create a DD Boost storage unit to function as the ProtectPoint catalog. Thefile system agent 3.1 configuration file describes the attributes that control thisconfiguration.

Run the following command:ddboost storage-unit create <storage-unit> user <user>ddboost storage-unit create CatalogStorageUnit user user1

Note

The storage unit is automatically created as /data/col1/<storage-unit>.

Specify a descriptive name when creating the storage unit.

2. File system agent 3.1 does not provide any replication functionality. To replicatebackups to a secondary Data Domain system, configure Data Domain MTreereplication. The Data Domain Operating System Administration Guide provides detailsabout configuring MTree replication.

3. Migrate the following values from the file system agent 2.0 configuration file that useoutdated key=value pairs to the new key=value pairs in the file system agent 3.1configuration file.

Table 32 File system agent 2.0 to file system agent 3.1 key=value pair conversions

File system agent 2.0 key=value pair File system agent 3.1 key=value pair

General section

LOGLEVEL DEBUG_LEVEL

LOG_DIR DIAGNOSTIC_DEST

LOCKBOX_DIR LOCKBOX_PATH

New value: PP_ARRAY_TYPE=VMAX

Primary system and Secondary system sections

DD_USER DDVDISK_USER

DD_POOL RESTORE_DEVICE_POOL

DD_DEVICE_GROUP RESTORE_DEVICE_GROUP

DD_SYSTEM DEVICE_HOST



Table 32 File system agent 2.0 to file system agent 3.1 key=value pair conversions (continued)


DD_PATH DEVICE_PATH

New value: DDBOOST_USER

For example, the file system agent 2.0 key=value pair LOCKBOX_DIR=/opt/emc/lockbox becomes LOCKBOX_PATH==/opt/emc/lockbox in the file systemagent 3.1 configuration file.

4. Create a new lockbox with the file system agent 3.1 configuration file.

5. Update the backup identifier from the file system agent 2.0 format to the file systemagent 3.1 format.

File system agent 2.0 format File system agent 3.1 format

[PRIMARY_DEVICE_1] SRC_SYMDEVID = <Source device sym id> FASTX_SYMDEVID=<FAST.X device sym id> DD_WWN = 6002188000000022DB05617163C00002 #SRC_SYMID = <Optional Default={[PRIMARY_SYSTEM].SYMID}> #FASTX_SYMID = <Optional Default=${[PRIMARY_SYSTEM].SYMID}>

[BACKUP_SOURCE_DEVICES]SRC_DEVICE1=<SYMID:DEVID>SRC_DEVICE2=<SYMID_DEVID>

Note

The SRC_DEVICE<N> directive supports standard EMC Solution Enabler VMAX array IDshort name syntax, SRC_DEVICE1=129:00A

6. Optionally create and populate a VMAX storage group with restore LUNs.

The file system agent 2.0 [PRIMARY_SYSTEM_RESTORE_DEVICE] section isremoved from the file system agent 3.1 configuration file. The file system agentautomatically selects restore devices using Intelligent Pairing. To continue usingexisting restore devices, create and populate a VMAX storage group with the existingFAST.X devices. The file system agent searches for a storage group namedNSRSnapSG by default, but a user-defined storage group can be specified in theconfiguration file in the VMAX_FASTX_RESTORE_SG key=value pair. File systemagent 3.1 supports restore operations from devices exposed directly from the DataDomain system, so the use of FAST.X devices is not required. Consider therequirements of the environment when selecting which restore workflow to use.

Run the following commands to create and populate a VMAX storage group:

a. Run the following command to create a VMAX storage group:symsg -sid <SymmetrixID> create ProtectPointRestoreGroupsymsg -sid 0129 create ProtectPointRestoreGroup

b. Run the following command to add a device to the VMAX storage group:symsg -sid <SymmetrixID> -sg ProtectPointRestoreGroup adddev <device_ID>symsg -sid 0129 -sg ProtectPointRestoreGroup add dev 00A


Upgrading the ProtectPoint file system agent 115

c. Repeat step b until all the existing FAST.X devices are added to the storage group.

7. Validate the migrated configuration.

Run the following command:protectpoint config validate [config-file <file-path>]

Upgrading from file system agent 3.0 to file system agent 3.1

Complete the following steps to upgrade an instance of file system agent 3.0 to filesystem agent 3.1.

Procedure

1. Migrate the following values from the file system agent 3.0 configuration file that useoutdated key=value pairs to the new key=value pairs in the file system agent 3.1configuration file.

Table 33 File system agent 3.0 to file system agent 3.1 key=value pair conversions


General section

LOGLEVEL DEBUG_LEVEL

LOG_DIR DIAGNOSTIC_DEST

LOCKBOX_DIR LOCKBOX_PATH

Primary system and Secondary system sections

DD_USER DDVDISK_USER

DD_POOL RESTORE_DEVICE_POOL

DD_DEVICE_GROUP RESTORE_DEVICE_GROUP

DD_SYSTEM DEVICE_HOST

DD_PATH DEVICE_PATH

RP_CLUSTER_1 section

RP_MGMT RP_MGMT_HOST

RP_CLUSTER_1 section BACKUP_SOURCE_DEVICES section

[RP_DEVICE_<N>]DEV_WWN=<WWN>

SRC_DEVICE<N>=<WWN>

For example, the file system agent 3.0 key=value pair LOCKBOX_DIR=/opt/emc/lockbox becomes LOCKBOX_PATH==/opt/emc/lockbox in the file systemagent 3.1 configuration file.

2. Validate the migrated configuration.

Run the following command:protectpoint config validate [config-file <file-path>]



CHAPTER 9

Troubleshooting


l ProtectPoint log file............................................................................................. 118l Check connectivity in the ProtectPoint environment............................................ 118l ProtectPoint troubleshooting scenarios............................................................... 119

Troubleshooting 117

ProtectPoint log fileThe ProtectPoint log file, protectpoint.log, is located in the logs subdirectorywithin the ProtectPoint install directory. The log shows information, error, and auditmessages captured by the ProtectPoint file system agent.

By default, the log level value is 2. The possible values are as follows:

1: Error2: Error and warning3: Error, warning, and information4: Error, warning, information, and debug

Check connectivity in the ProtectPoint environmentIf there is a problem in the ProtectPoint environment, check the connectivity between thesolution components to verify that all the components are communicating with eachother. The following tables indicate the type of connection used by the components in theProtectPoint environment.

Table 34 ProtectPoint with VMAX connectivity



Primary application host to primary Data Domain system IP LAN


IP LANPrimary recovery host to primary Data Domain system

Primary storage system to primary Data Domain system FC SAN

(Optional) Secondary recovery host to secondary storage system FC SAN

(Optional) Secondary recovery host to secondary Data Domain system IP LAN

(Optional) Secondary storage system to secondary Data Domain system FC SAN

(Optional) Primary application host to secondary Data Domain system IP WAN


Table 35 ProtectPoint with RecoverPoint connectivity



Primary application host to RecoverPoint cluster IP LAN


IP LANPrimary recovery host to RecoverPoint cluster

Primary storage to RecoverPoint cluster FC SAN or IP LAN

RecoverPoint cluster to primary Data Domain system FC SAN or IP LAN

Troubleshooting


Table 35 ProtectPoint with RecoverPoint connectivity (continued)



ProtectPoint troubleshooting scenariosThe following sections list some potential troubleshooting scenarios and steps to correctthe issues.

Failure of a host at the primary siteA failure has occurred on the AR host at the primary site, and a new AR host is broughtonline at the primary site to replace it. The application administrator would like tocontinue to leverage the workflow for data protection.

Before you begin

Verify the following elements of the configuration:

l Connectivity has been established between the primary storage system and the newAR host.

l Connectivity has been established between the new AR host and the Data Domainstorage array.

Complete the following high-level tasks.

Procedure

1. Make the primary storage devices accessible to the new AR host.

2. If necessary, re-create the configuration on the new AR host.

Failure of host with a new host on the secondary siteA failure has occurred on the AR host at the primary site, and a new AR host is broughtonline at the secondary site. The application administrator would like to continue toleverage the workflow for data protection.

ProtectPoint with VMAX

Treat this as a failure of the primary and protection storage at the primary site, andinitiate a full failover to the secondary site.

ProtectPoint with RecoverPoint

Verify that the new AR host has the same connections to the ProtectPoint environment asthe original AR host, and has access to the primary storage devices.

Primary site failure (both primary and protection storage)A failure has occurred that disables the primary site, affecting both the storage systemsand AR host. The decision has been made to fail over to the secondary site. Restore LUNs

Troubleshooting

ProtectPoint troubleshooting scenarios 119

and restore devices are already configured on the secondary site primary storage andData Domain systems.

Before you begin


l There is a replicated copy of the primary data on the secondary site.

l There is a replicated copy of the backups on the secondary site.

l There is an AR host on the secondary site that can be used to run the application.

l The WWN for the new production AR host has been provided.


Procedure

1. Set the replicated copy on the secondary site primary storage system as theproduction copy.

2. Create the backup LUNs on the Data Domain system, matching the geometry of thesource devices in the appropriate access group.

3. Connect the Data Domain backup LUNs to the primary storage system. These LUNs willbe referred to as the Data Domain backup target devices.

4. Create the snapshots of the source devices.

5. For ProtectPoint with VMAX environments, link the snapshots to the backup targetdevices.

6. Mask the source devices to the new production host.

7. Re-create the configuration on the new host.

Secondary site failure (both primary and protection storage)A recoverable failure occurs that disables the secondary site, affecting both the primaryand protection storage systems at the secondary site. The storage administrator caneither follow the procedure for provisioning storage resources on the secondary site orstop replication to the secondary site.

Choose one of the following options:

l Provision new primary and protection storage resources at the secondary site, andcreate new replication sessions to the new destination devices.

l Stop replication to the secondary site.

Failure of primary storage at the production siteA failure has occurred on the primary storage at the production site.

For ProtectPoint with VMAX primary storage, initiate a failover to the secondary site asdescribed in Primary site failure (both primary and protection storage) on page 119.

For ProtectPoint with RecoverPoint and XtremIO primary storage, the remainder of theXtremIO cluster will assume the primary storage workload.

Failure of primary storage at the secondary siteA recoverable failure occurs that disables the primary storage at the secondary site. Thisdoes not affect replication of the backup sets, but could impact restores from the

Troubleshooting


secondary site. To allow restores from the secondary site, the storage administrator canuse a different primary storage system for restores on the secondary site.

Before you begin

Note

This scenario only applies to ProtectPoint with VMAX primary storage.


l The WWN for the AR host has been provided.

l The WWN used on the Data Domain storage array for backups has been provided.

l The required licenses are configured on the primary storage system.

l The AR host has access to the primary storage and Data Domain systems.

l SAN zoning is complete between the new primary storage system and the DataDomain system.

l SAN zoning is complete between the AR host and the new primary storage system.


Procedure

1. Modify the existing access groups used by the Data Domain restore LUNs for the newprimary storage initiators.

2. Connect the Data Domain restore LUNs to the primary storage system. These newdevices will be referred to as the restore target devices.

3. Mask the restore target devices to the AR host.

Failure of protection storage at the production siteA failure occurs that disables the protection storage at the primary site. The storageadministrator can provision new protection storage resources on the Data Domainsystem, or initiate a failover to the secondary site.

Choose one of the following options:

l Provision new protection storage resources on the Data Domain system.

l Initiate a failover to the secondary site as described in Primary site failure (bothprimary and protection storage) on page 119.

Failure of protection storage at the secondary siteA recoverable failure occurs that disables the protection storage at the secondary site.The application administrator can stop replication until the error is fixed.

Edit the ProtectPoint configuration file to remove the portion used for replication.

Troubleshooting

Failure of protection storage at the production site 121

Troubleshooting


APPENDIX A

ProtectPoint Command Reference

This appendix includes the following topics:

l protectpoint change history.................................................................................124l ProtectPoint filesystem agent with VMAX command reference............................. 125l ProtectPoint filesystem agent with RecoverPoint command reference..................131

ProtectPoint Command Reference 123

protectpoint change historyThe table below summarizes the command changes since the previous release. Thesecommands are described later in this guide. The EMC Data Domain Operating SystemRelease Notes of the corresponding version provides more details on modifications,including arguments, output, and permissions.

Table 36 protectpoint change history

Version Change

ProtectPoint 3.1(DD OS 5.7.1)

Added the protectpoint rollback command.

Added the protectpoint backup scan command.

Added the scan option to the following commands: commands.

l protectpoint backup showl protectpoint restore preparel protectpoint restore releaseAdded the [app-consistent | crash-consistent] option to the

protectpoint snapshot create command.

Added the hostname option to the following commands:

l protectpoint backupl protectpoint restoreAdded the following options to the protectpoint backup show scancommand: option to the command.

l displayl filterRemoved the protectpoint replication commands.

ProtectPoint 3.0(DD OS 5.7)

Added the following new RecoverPoint-specific commands:

l protectpoint backup show scan commandl protectpoint catalog validatel protectpoint restore preparel protectpoint restore releaseAdded the protectpoint security add rp-credentials rp-cluster [<rp-cluster-x>] command.

Added the protectpoint security del rp-credentials rp-cluster [<rp-cluster-x>] command.

Added the {boost | vdisk} option to the following commands:

l protectpoint security add dd-credentialsl protectpoint security del dd-credentialsAdded the following options to the protectpoint backup showdetailed command:



Table 36 protectpoint change history (continued)

Version Change

l pool <vdisk-pool>l group <vdisk-group>Added RecoverPoint-specific behavior for the protectpoint catalogupdate command.

Added the RecoverPoint-specific description argument to the

protectpoint snapshot create command.

Added the RecoverPoint-specific backup-id argument to the

protectpoint backup create command.

The protectpoint replication commands are not supported in

ProtectPoint 3.0.

The following commands have modified behaviors in ProtectPoint 3.0:

l protectpoint backup deletel protectpoint catalog updatel protectpoint config validatel protectpoint restore prepare

ProtectPoint 1.0(DD OS 5.5)

This is the initial release of this command.

ProtectPoint filesystem agent with VMAX command referenceThe ProtectPoint file system agent with VMAX command reference includes:

l protectpoint guidelines and restrictions on page 125

l protectpoint backup on page 126

l protectpoint catalog on page 128

l protectpoint config on page 128

l protectpoint restore on page 129

l protectpoint security on page 130

l protectpoint show on page 131

l protectpoint snapshot on page 131

protectpoint guidelines and restrictionsMany of the protectpoint commands use the config-file keyword and the <file-path>argument. The <file-path> argument is the name of the fully qualified path plus the nameof the configuration file used or modified when the ProtectPoint file system agent wasinstalled and configured on the AR host. You can use the default file name(protectpoint.config) or modify (and rename) the default file to suit the needs of yourconfiguration.

Access to Solutions Enabler 8.0.2 is required to use the protectpoint commands.


ProtectPoint filesystem agent with VMAX command reference 125

If protectpoint commands are initiated when Quick Edit mode is enabled onWindows hosts, the commands will not complete until you press Enter.

protectpoint backupThis command allows you to create backups, list summary and detailed informationabout backups, as well as delete backups from either a primary or secondary DataDomain system.

protectpoint backup create backup-id <backup-id> [config-file<file-path>]The protectpoint backup create command copies a snapshot from the VMAX tothe Data Domain system.

protectpoint backup scan [dd-system {primary | secondary}][config-file <file-path>]Scans the Data Domain system for backups created by other ProtectPoint applications inaddition to backups created by the file system agent, and creates a scan catalog to keeptrack of these backups. The scan catalog is maintained separately from the file systemagent backup catalog.

Note

The scan catalog only contains the static-images owned by the block services forProtectPoint user specified in the file system agent configuration file.

protectpoint backup show list [dd-system {primary | secondary}][{last <n> {count | days | weeks | months}} | {from <MMDDhhmm>[[<CC>] <YY>] [to <MMDDhhmm> [[<CC>] <YY> ]]}] [status{complete | in-progress | failed | snap-ready | suspect |rollback | restore-ready}] [config-file <file-path>]Shows the list of backups performed on the primary or secondary Data Domain system.

Note

If protectpoint backup show is run before a backup has been created, the

command fails with the message Unable to open catalog file. This is because

the first backup (or first use of the protectpoint catalog update command)

creates the catalog file.

protectpoint backup show list dd-system [primary | secondary]pool <vdisk-pool> group <vdisk-group> [host <hostname>]Shows the list of backups stored in the specified block services for ProtectPoint pool andgroup on the primary or secondary Data Domain system.

The host option allows the command to access the catalog on an alternate host.

protectpoint backup show detailed backup-id <backup-id> [dd-system {primary | secondary}] [config-file <file-path>] [host<hostname> | scan]Lists the detailed information about a specific backup on the primary or secondary DataDomain system. The scan option displays backups from the scan catalog.


protectpoint backup show detailed backup-id 1455031693Backup id: 1455031693Backup start time: 2014-01-17 11:02:43Backup end time: 2014-01-17 11:03:22



Backup duration: 00:59:59 (hh:mm:ss)Status: completeDescription: Oracle Host1Static images:Expected count: 3Present in catalog: 3Present on DD system: 3-------- ---------------------------------------- -------------------Image Static-image Present on Sequence DD System-------- ---------------------------------------- -------------------1 0400002ddb6a052d97be70001200000000000000 yes2 0400002ddb6a052d97be70001400000000000001 yes3 0400002ddb6a052d97be70001600000000000002 yes-------- ---------------------------------------- -------------------

protectpoint backup show detailed dd-system [primary |secondary] pool <vdisk_pool> group <vdisk_group>Lists the detailed information about the backups in the specified vdisk pool and vdiskgroup on the primary or secondary Data Domain system.

protectpoint backup show detailed backup-id <backup-id> [dd-system {primary | secondary}] pool <vdisk_pool> group<vdisk_group>Lists the detailed information the specified backup.

protectpoint backup delete backup-id <backup-id > [config-file<file-path>]Deletes the specified backup from the primary Data Domain system.

The protectpoint backup delete command does not delete the replicated static-images on the secondary Data Domain system.

Argument Definitions

backup-id <backup-id>

Backup Identifier.

config-file <file-path>

Enter the name and path of the modified configuration file.

dd-system {primary | secondary}

Indicate either the primary or secondary Data Domain system.

description <backup-description>

Description for the backup to be created. The description is limited to a maximum of256 characters.

from MMDDhhmm [[<CC>]<YY>] [to <MMDDhhmm> [[<CC>] <YY>]

List the backups in the from-to time and date range specified. If a "To" date is notspecified, the backup range used is the "From" date to the current date.

last <n> {count | days | weeks | months}

List the last number of backups completed based on a number (count) or time period(days, weeks, or months).

status {complete | snap-ready | in-progress | restore-ready | rollback | failed | suspect }

List the backups in the specified state.

pool <vdisk-pool>

Specify the block services for ProtectPoint backup pool.


protectpoint backup 127

group <vdisk-group>

Specify the block services for ProtectPoint backup device-group.

protectpoint catalogThis command creates or rebuilds the backup catalog for either the primary or secondaryData Domain system.

protectpoint catalog update [dd-system {primary | secondary}][config-file <file-path>]Creates or rebuilds the backup catalog for either the primary or secondary Data Domainsystem.






protectpoint configThe protectpoint config validate command validates the format of theconfiguration file modified when the ProtectPoint file system agent was set up on the ARhost. Before using this command, run the protectpoint security add commandto save either the primary or secondary Data Domain system credentials.

protectpoint config validate [config-file <file-path>] [dd-system { primary | secondary }]Validates the format of the configuration file.

*** Using VMAX config file "/test/config.vmax" ***Validating application settings.........................[OK]Validating host requirements............................[OK]Validating Primary System: VDisk Connection Information........................[OK] Boost Connection Information........................[OK] FAST.X Restore Group...................................[OK] DD Boost Path.......................................[OK]Validating VMax Devices: VMax Device 1032:4F5................................[OK] VMax Device 1032:4F6................................[OK]

Configuration is valid.

Note

Comment out unused sections of the ProtectPoint configuration file to prevent theprotectpoint config validate command from generating errors when

processing those sections.






protectpoint rollbackThis command initiates a rollback of the primary storage to the contents of the specifiedbackup.

protectpoint rollback backup-id <id> [reset] [dd-system{primary | secondary}] [config-file <file-path>] [host<hostname> | scan]Overwrites the primary storage devices with the contents of the specified backups.

Note


When the rollback operation starts, the catalog entry for the backup being restoredchanges from complete to rollback. If the protectpoint rollback command fails,the backup remains in the rollback state and cannot be used for other operations. Runthe protectpoint rollback backup-id <backup-id> reset command to set thecatalog state back to complete.

protectpoint restoreThis command prepares either the primary or secondary Data Domain system forrestoring the backup image to the restore devices.

protectpoint restore prepare backup-id <backup-id> [dd-system{primary | secondary}] [config-file <file-path>] [host<hostname> | scan]Restores the content of the backup set identified by <backup-id> to the Data Domainsystem, overwriting the contents of the Data Domain restore devices with the static-images in the backup set specified for restoration.


Note

Use Solutions Enabler symsnapvx commands to copy the data in the encapsulated

restore devices to either the original source devices for full application-rollbackrestoration, or to host-available restore devices for object-level restoration.

protectpoint restore release backup-id <backup-id> [dd-system{primary | secondary}] [host <hostname> | scan]Makes the restore devices for the specified backup available for additional restoreoperations by completing the following actions:

l Retrieves the restore-ready device path names from the catalog.

l Zeroes the restore devices.

l Changes the restore device state to READ_ONLY.

l Removes the prepared device path names from the catalog.

l Changes the backup state to complete.



protectpoint rollback 129

Note

If the protectpoint restore prepare command failed because a static-image on

the Data Domain was not found, the protectpoint restore release command

changes the catalog entry for the specified backup to suspect.



Backup Identifier.





protectpoint securityThis command allows you to add or remove Data Domain credentials from the RSAlockbox, along with modifying the host or client access to the RSA lockbox.

protectpoint security add dd-credentials [dd-system {primary |secondary}] {ddboost | vdisk}Adds the security credentials for either the primary or secondary Data Domain system tothe RSA lockbox.l If the dd-system parameter is not specified, the command uses the primary Data

Domain system by default.l The dd-system parameter is required to specify ddboost or vdisk.

Note

The RSA lockbox must exist. If one does not exist, one will be created with a randomlygenerated password consisting of a minimum of 8 characters. The password is saved forfuture use such as adding additional hosts and updating the System SignatureVerification (SSV) setting threshold. You will be prompted for password associated withthe host and username specified in the ProtectPoint configuration file.

protectpoint security del dd-credentials [dd-system {primary |secondary}] [config-file <file-path>]Removes the security credentials for either the primary or secondary Data Domain systemfrom the RSA lockbox.

protectpoint security access add host <host> [config-file<file-path>]Adds an application host to the RSA lockbox access list.

protectpoint security access remove host <host> [config-file<file-path>]Deletes an application host from the RSA lockbox access list.

protectpoint security access show [config-file <file-path>]Displays information about the application/recovery host access.








host <host>

Name of the host.

rp-cluster <rp-cluster-x>

Specify the RPA in the RecoverPoint cluster.

protectpoint showThis command displays the version of the ProtectPoint file system agent in use.

protectpoint show versionShows the version of the ProtectPoint file system agent in use.

protectpoint show version<package name> version: 3.1.0.0-<build-number>

protectpoint snapshotThis command creates a snapshot of the data on the primary storage system.

protectpoint snapshot create description <description> [config-file <file-path>] [app-consistent | crash-consistent]The protectpoint snapshot create command creates the snapshot of theprimary storage devices.

The optional [app-consistent | crash-consistent] flag is available to tag thesnapshot when it is created. This tag is just for information, it does not impact thecreation of the snapshot in any way. If a snapshot is tagged, the tag will appear in theoutput of the protectpoint backup show detailed command.




description <snapshot-description>

Description for the RecoverPoint snapshot to be created.

ProtectPoint filesystem agent with RecoverPoint commandreference

The ProtectPoint file system agent with RecoverPoint command reference includes:

l protectpoint guidelines and restrictions on page 132

l protectpoint backup on page 132

l protectpoint catalog on page 134

l protectpoint config on page 135

l protectpoint restore on page 135

l protectpoint security on page 136

l protectpoint show on page 138


protectpoint show 131

l protectpoint snapshot on page 138

protectpoint guidelines and restrictionsMany of the protectpoint commands use the config-file keyword and the <file-path>argument. The <file-path> argument is the name of the fully qualified path plus the nameof the configuration file used or modified when the ProtectPoint file system agent wasinstalled and configured on the AR host. You can use the default file name(protectpoint.config) or modify (and rename) the default file to suit the needs of yourconfiguration.

protectpoint backupThis command allows you to create backups, list summary and detailed informationabout backups, as well as delete backups from either a primary or secondary DataDomain system.

protectpoint backup create backup-id <backup-id>The protectpoint backup create command ensures that a backup initiated withthe protectpoint snapshot create command completes, and is marked ascomplete in the catalog if the operation is successful.

protectpoint backup scan [dd-system {primary | secondary}][config-file <file-path>]Scans the Data Domain system for backups created by other ProtectPoint applications inaddition to backups created by the file system agent, and creates a scan catalog to keeptrack of these backups. The scan catalog is maintained separately from the file systemagent backup catalog.

Note

The scan catalog only contains the static-images owned by the block services forProtectPoint user specified in the file system agent configuration file.

protectpoint backup show list [dd-system {primary | secondary}][{last <n> {count | days | weeks | months}} | {from <MMDDhhmm>[[<CC>] <YY>] [to <MMDDhhmm> [[<CC>] <YY> ]]}] [status{complete | in-progress | failed | snap-ready | suspect |rollback | restore-ready}] [config-file <file-path>]Shows the list of backups performed on the primary or secondary Data Domain system.

Note

If protectpoint backup show is run before a backup has been created, the

command fails with the message Unable to open catalog file. This is because

the first backup (or first use of the protectpoint catalog update command)

creates the catalog file.

protectpoint backup show list dd-system [primary | secondary]pool <vdisk-pool> group <vdisk-group> [host <hostname>]Shows the list of backups stored in the specified block services for ProtectPoint pool andgroup on the primary or secondary Data Domain system.


protectpoint backup show detailed backup-id <backup-id> [dd-system {primary | secondary}] [config-file <file-path>] [host<hostname> | scan]



Lists the detailed information about a specific backup on the primary or secondary DataDomain system. The scan option displays backups from the scan catalog.


protectpoint backup show detailed backup-id 1464286066*** Using RP config file "/config.rp" ***

Backup-id: 1464286066Storage: RecoverPointBackup hostname: ledmf068.lss.emc.comRP Bookmark: FSAgent_0dde5d73-0000000e-000044a0-57473b71-0001baa4-b43e33dbSnapshot/Backup start time: Thu May 26 14:07:45 2016Backup end time: Thu May 26 14:08:26 2016Backup duration: 000:00:41Backup status: completeBackup description: Smoketest Thu May 26 14:01:45 EDT 2016Consistency Type: <not specified>Agent name: ProtectPointAgent version: 3.1.0.0-182Application info: yadda yadda yaddaApplication version: fe.fi.fo.fum.123

Static images: Expected count: 16 Present in catalog: TRUE Present in DD system: TRUE (as of last catalog update)-------- ---------------------------------------- ------------------ ----------Image Static-Image Source Device Present onSequence DD System-------- ---------------------------------------- ------------------ ----------1 04004d6001a205745a9740038e000b0000000000 514f0c54ea6000b0 yes 2 04004d6001a205745a9740039c000b0000000000 514f0c54ea6000bc yes 3 04004d6001a205745a9740039a000b0000000000 514f0c54ea6000b3 yes 4 04004d6001a205745a97400382000b0000000000 514f0c54ea6000b9 yes 5 04004d6001a205745a97400384000b0000000000 514f0c54ea6000b2 yes 6 04004d6001a205745a97400386000b0000000000 514f0c54ea6000b8 yes 7 04004d6001a205745a9740039e000b0000000000 514f0c54ea6000bb yes 8 04004d6001a205745a97400394000b0000000000 514f0c54ea6000b4 yes 9 04004d6001a205745a97400392000b0000000000 514f0c54ea6000af yes 10 04004d6001a205745a97400390000b0000000000 514f0c54ea6000b1 yes 11 04004d6001a205745a97400396000b0000000000 514f0c54ea6000b5 yes 12 04004d6001a205745a97400388000b0000000000 514f0c54ea6000bd yes 13 04004d6001a205745a97400398000b0000000000 514f0c54ea6000ba yes 14 04004d6001a205745a9740038c000b0000000000 514f0c54ea6000be yes 15 04004d6001a205745a97400380000b0000000000 514f0c54ea6000b6 yes 16 04004d6001a205745a9740038a000b0000000000 514f0c54ea6000b7 yes

protectpoint backup show detailed dd-system [primary |secondary] pool <vdisk_pool> group <vdisk_group>Lists the detailed information about the backups in the specified vdisk pool and vdiskgroup on the primary or secondary Data Domain system.

protectpoint backup show detailed backup-id <backup-id> [dd-system {primary | secondary}] pool <vdisk_pool> group<vdisk_group>Lists the detailed information the specified backup.

protectpoint backup show scan [help] [dd-system {primary |secondary}] [config-file <file-path>] [filter <key=value>][filter <keyN=valueN>] [display <key1>[,<key2>,..<keyN>]]Lists the backups from the scan catalog on the primary or secondary Data Domainsystem. The filter option displays backups matching the specified filter. The helpoption displays the list of filters.


protectpoint backup 133

protectpoint backup delete backup-id <backup-id >Deletes the specified backup from the primary or secondary Data Domain system.

The protectpoint backup delete command does not delete the replicated static-images on the secondary Data Domain system.



Backup Identifier.

{boost | vdisk}

Indicate whether the specified credentials are for DD Boost or block services forProtectPoint.





from MMDDhhmm [[<CC>]<YY>] [to <MMDDhhmm> [[<CC>] <YY>]

List the backups in the from-to time and date range specified. If a "To" date is notspecified, the backup range used is the "From" date to the current date.

last <n> {count | days | weeks | months}

List the last number of backups completed based on a number (count) or time period(days, weeks, or months).

status {complete | snap-ready | in-progress | restore-ready | rollback | failed | suspect }

List the backups in the specified state.

pool <vdisk-pool>

Specify the ProtectPoint pool.

group <vdisk-group>

Specify the ProtectPoint device-group.

protectpoint catalogThis command verifies and updates the backup catalog of the primary Data Domainsystem.

protectpoint catalog update [config-file <file-path>]Verifies and updates the backup catalog of the primary Data Domain system. If thecatalog already exists prior to running this command, the ProtectPoint file system agentmarks backups for which static-images no longer exist as suspect.

protectpoint catalog validateVerifies the state of each backup on the primary Data Domain system.

protectpoint.exe catalog validate

catalog validate: This command may take a long time to complete..Scanning all backups in the "primary" dd-system [ledmd035.lss.emc.com]Backup [1441919984] is validBackup [1443500358] is validBackup [1443528855]'s static image [04000000905a055ee49e100d7500150000000000] is missing in the DDRBackup [1443528855] cataloged as "suspect" is still not validBackup [1443554334] is valid



Backup [1443554474] state is [failed], ignoring.Backup [1443558375] is validBackup [1443587994] is validBackup [1443640405] state is [in-progress], ignoring.Catalog validate complete.




protectpoint configThis command validates the format of the configuration file modified when theProtectPoint file system agent was set up on the AR host. Before using this command,save either the primary or secondary Data Domain system credentials, and theRecoverPoint credentials. To do this, use the following command:protectpoint security addprotectpoint config validate [config-file <file-path>]Validates the format of the configuration file.

>protectpoint config validateValidating host requirements............................[OK]Validating RP Management [ledmd160.lss.emc.com].........[OK]Validating RP Devices:RP Device 600601604D203700F4CEEE3489DCE411..............[OK]

Note

Comment out unused sections of the ProtectPoint configuration file to prevent theprotectpoint config validate command from generating errors when

processing those sections.




protectpoint restoreThis command prepares either the primary or secondary Data Domain system forrestoring the backup image to the restore devices.

protectpoint restore prepare backup-id <backup-id> [dd-system{primary | secondary}] [config-file <file-path>] [host<hostname> | scan]Restores the content of the backup set identified by <backup-id> to the Data Domainsystem, overwriting the contents of the Data Domain restore devices with the static-images in the backup set specified for restoration.

protectpoint restore release backup-id <backup-id> [dd-system{primary | secondary}] [config-file <file-path>] [host<hostname> | scan]Makes the restore devices for the specified backup available for additional restoreoperations by completing the following actions:

l Retrieves the restore-ready device path names from the catalog.

l Changes the restore device state to READ_ONLY.

l Removes the prepared device path names from the catalog.


protectpoint config 135

l Changes the backup state to complete.

Note

If the protectpoint restore prepare command failed because a static-image on

the Data Domain was not found, the protectpoint restore release command

changes the catalog entry for the specified backup to suspect.

protectpoint rollback backup-id <backup-id> [dd-system {primary| secondary}] [config-file <file-path>] [host <hostname> |scan]Initiate a rollback of the production primary storage devices to match the specifiedbackup.



Backup Identifier.



protectpoint rollbackThis command initiates a rollback of the primary storage to the contents of the specifiedbackup.

protectpoint rollback backup-id <id> [reset] [dd-system{primary | secondary}] [config-file <file-path>] [host<hostname> | scan]Overwrites the primary storage devices with the contents of the specified backups.

Note


When the rollback operation starts, the catalog entry for the backup being restoredchanges from complete to rollback. If the protectpoint rollback command fails,the backup remains in the rollback state and cannot be used for other operations. Runthe protectpoint rollback backup-id <backup-id> reset command to set thecatalog state back to complete.

protectpoint securityThis command allows you to add or remove Data Domain credentials from the RSAlockbox, along with modifying the host or client access to the RSA lockbox.

protectpoint security add dd-credentials [dd-system {primary |secondary} {boost | vdisk}] [config-file <file-path>]Adds the security credentials for either the primary or secondary Data Domain system tothe RSA lockbox.

l If the dd-system parameter is not specified, the command uses the primary DataDomain system by default.




Note


protectpoint security add rp-credentials rp-cluster [<rp-cluster-x>] [config-file <file-path>]Add the security credentials for an individual appliance within a RecoverPoint cluster tothe RSA lockbox.

Note


protectpoint security del dd-credentials [dd-system {primary |secondary} {boost | vdisk}] [config-file <file-path>]Removes the security credentials for either the primary or secondary Data Domain systemfrom the RSA lockbox.

protectpoint security del rp-credentials rp-cluster [<rp-cluster-x>] [config-file <file-path>]Removes the security credentials for an individual appliance within a RecoverPointcluster from the RSA lockbox.

protectpoint security access add host <host> [config-file<file-path>]Adds an application host to the RSA lockbox access list.

protectpoint security access remove host <host> [config-file<file-path>]Deletes an application host from the RSA lockbox access list.

protectpoint security access show [config-file <file-path>]Displays information about the application/recovery host access.


{boost | vdisk}

Indicate whether the specified credentials are for DD Boost or block services forProtectPoint.





host <host>

Name of the host.


protectpoint security 137

rp-cluster <rp-cluster-x>

Specify the RPA in the RecoverPoint cluster.

protectpoint showThis command displays the version of the ProtectPoint file system agent in use.

protectpoint show versionShows the version of the ProtectPoint file system agent in use.

protectpoint show version<package name> version: 3.1.0.0-<build-number>

protectpoint snapshotThis command creates a snapshot of the data on the primary storage system.

protectpoint snapshot create description <snapshot-description>[app-consistent | crash-consistent]The protectpoint snapshot create command creates the snapshot of theprimary storage devices, copies the snapshot to the Data Domain system, and creates theData Domain static-image. Data transfer begins immediately when the protectpointsnapshot create command is run.

The optional [app-consistent | crash-consistent] flag is available to tag thesnapshot when it is created. This tag is just for information, it does not impact thecreation of the snapshot in any way. If a snapshot is tagged, the tag will appear in theoutput of the protectpoint backup show detailed command.


description <snapshot-description>

Description for the RecoverPoint snapshot to be created.



Agent EMC ProtectPoint File System · PDF filel EMC Data Domain Expansion Shelf Hardware Guide...

Documents

Transcript of Agent EMC ProtectPoint File System · PDF filel EMC Data Domain Expansion Shelf Hardware Guide...