emc protectpoint 3.5 primary and protection storage ... · pdf fileprimary and protection...

EMC ProtectPointVersion 3.5

Primary and Protection Storage Configuration Guide302-003-475

REV 02

Copyright © 2014-2017 Dell Inc. or its subsidiaries. All rights reserved.

Published May 2017

Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND

WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED

IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.

Published in the USA.

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

2 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

Preface 5

ProtectPoint Storage Configuration Overview 9ProtectPoint family overview......................................................................10

ProtectPoint file system agent.......................................................10ProtectPoint database application agent........................................ 11ProtectPoint Microsoft application agent....................................... 11

Application storage configuration overview.................................................12Data Domain sizing considerations.............................................................. 12Discovering application storage...................................................................13Host considerations.................................................................................... 14

VMAX Application Storage Configuration 15ProtectPoint environment...........................................................................16

Additional information.................................................................... 16ProtectPoint for VMAX prerequisites..........................................................16

ProtectPoint file system agent prerequisites................................. 16Database application agent and Microsoft application agentprerequisites.................................................................................. 16VMAX prerequisites........................................................................17Data Domain prerequisites..............................................................18DD Boost prerequisites...................................................................18Data Domain block services prerequisites.......................................18

Discovering device geometry...................................................................... 19Provision VMAX storage and encapsulate the Data Domain devices on theVMAX array................................................................................................20

ProtectPoint performance considerations for VMAX Gen0 backups...................................................................................................... 20Provisioning FAST.X restore LUNs to the application recovery host...................................................................................................... 20Encapsulating Data Domain devices on the VMAX array................23

Additional storage configuration.................................................................34N_Port ID Virtualization.................................................................35

Next steps..................................................................................................36

XtremIO Application Storage Configuration 37ProtectPoint for XtremIO with RecoverPoint environment........................ 38ProtectPoint for XtremIO with RecoverPoint prerequisites........................38

ProtectPoint file system agent prerequisites.................................38Database application agent and Microsoft application agentprerequisites..................................................................................38RecoverPoint prerequisites........................................................... 39XtremIO prerequisites....................................................................39Data Domain prerequisites.............................................................40DD Boost prerequisites.................................................................. 40Data Domain block services prerequisites......................................40

Configure XtremIO storage and connect the Data Domain system,RecoverPoint cluster, and XtremIO cluster................................................ 42

Chapter 1

Chapter 2

Chapter 3

CONTENTS

EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide 3

Creating an XtremIO initiator group...............................................42Configuring XtremIO storage for a single volume...........................43Configuring XtremIO storage for multiple volumes........................ 44Configuring Data Domain services and users................................. 46Enabling encryption over a WAN connection................................. 47Configuring the DD Boost over Fibre Channel service................... 48Configuring DD Boost storage units...............................................49Configuring block services for ProtectPoint objects......................50Configuring a Data Domain access group for the applicationrecovery host................................................................................ 52Logging into RecoverPoint............................................................ 53Install a license in RecoverPoint.................................................... 54Register storage in RecoverPoint.................................................. 55Define storage login credentials in RecoverPoint...........................57Register block services for ProtectPoint pools in RecoverPoint.... 58Protect XtremIO volumes using RecoverPoint.............................. 60

Additional storage configuration.................................................................65N_Port ID Virtualization.................................................................65

Next steps..................................................................................................66

Data Domain Collection Replication 69Data Domain collection replication overview...............................................70

Registering the DD Boost storage units and vdisk pools used by thedatabase application agent............................................................ 70Deleting the collection replication pair........................................... 72

Restoring directly from Data Domain for VMAX configurations.................. 72Preparing application agent restore devices on a secondary DataDomain system.............................................................................. 72Configuring a Data Domain access group for the applicationrecovery host.................................................................................73Performing a database application agent restore from a secondaryData Domain system...................................................................... 75

Restoring via VMAX FAST.X devices.......................................................... 75Preparing database application agent restore devices on asecondary Data Domain system..................................................... 75Encapsulating secondary Data Domain system vdisk devices onVMAX............................................................................................ 77Provisioning FAST.X restore LUNs to the application recovery host.......................................................................................................81Performing an application agent object level restore from asecondary Data Domain system.....................................................83Performing an application agent rollback restore from a secondaryData Domain system...................................................................... 84

Restoring directly from Data Domain for XtremIO with RecoverPointconfigurations............................................................................................ 84

Preparing database application agent restore devices on asecondary Data Domain system.....................................................84Configuring a Data Domain access group for the applicationrecovery host................................................................................ 85Performing an application agent restore from a secondary DataDomain system.............................................................................. 87Database application agent rollback restore via a RecoverPointappliance .......................................................................................87

Chapter 4

CONTENTS


Preface

As part of an effort to improve product lines, periodic revisions of software andhardware are released. Therefore, all versions of the software or hardware currently inuse might not support some functions that are described in this document. Theproduct release notes provide the most up-to-date information on product features.

If a product does not function correctly or does not function as described in thisdocument, contact a technical support professional.

Note

This document was accurate at publication time. To ensure that you are using thelatest version of this document, go to the Support website at https://support.emc.com.

PurposeThis document includes instructions to provision the primary and protection storagefor a ProtectPoint deployment.

AudienceThis document is intended for administrators who need to configure the primary andprotection storage for the ProtectPoint environment. This document is relevant forboth the ProtectPoint file system agent and ProtectPoint application agents.

Revision HistoryThe following table presents the revision history of this document

Table 1 Revision history

Revision Date Description

02 May 19, 2017 Removed references to specific component versions.To view the supported versions of components, go to:

http://compatibilityguide.emc.com:8080/CompGuideApp/getProtectPointCompGuidePage.do

01 December 21, 2016 Initial release of the EMC ProtectPoint 3.5 Primary andProtection Storage Configuration Guide.

The ProtectPoint file system agent documentation set includes the followingpublications:

l EMC ProtectPoint Solutions Guide

l EMC ProtectPoint Primary and Protection Storage Configuration Guide

l EMC ProtectPoint File System Agent Installation and Administration Guide

l EMC ProtectPoint File System Agent Release Notes

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

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

Preface 5

https://support.emc.com




l EMC Data Domain Boost for Enterprise Applications and ProtectPoint DatabaseApplication Agent Release Notes

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

l EMC Data Domain Boost for Enterprise Applications and EMC ProtectPoint MicrosoftApplication Agent Release Notes

For compatibility information, including specific backup software and hardwareconfigurations that ProtectPoint supports, go to the following website:


The following Data Domain system documents provide additional information:

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

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 Guide

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 Guide

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, orDS60

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 Manager (DPM), see the RSA DataProtection Manager Server Administrator's Guide, available with the RSA DPM product.

The following VMAX system documents provide additional information:

l EMC Solutions Enabler TimeFinder Family CLI User Guide

l EMC Solutions Enabler Array Management CLI User Guide

Special notice conventions that are used in this documentThe following conventions are used for special notices:

NOTICE

Identifies content that warns of potential business or data loss.

Preface




Note

Contains information that is incidental, but not essential, to the topic.

Typographical conventionsThe following type style conventions are used in this document:

Table 2 Style conventions

Bold Used for interface elements that a user specifically selects or clicks,for example, names of buttons, fields, tab names, and menu paths.Also used for the name of a dialog box, page, pane, screen area withtitle, table label, and window.

Italic Used for full titles of publications that are referenced in text.

Monospace Used for:

l System code

l System output, such as an error message or script

l Pathnames, file names, file name extensions, prompts, andsyntax

l Commands and options

Monospace italic Used for variables.

Monospace bold Used for user input.

[ ] Square brackets enclose optional values.

| Vertical line indicates alternate selections. The vertical line means orfor the alternate selections.

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

... Ellipses indicate non-essential information that is omitted from theexample.

You can use the following resources to find more information about this product,obtain support, and provide feedback.

Where to find product documentation

l https://support.emc.com

l https://community.emc.com

Where to get supportThe Support website at https://support.emc.com provides access to licensinginformation, product documentation, advisories, and downloads, as well as how-to andtroubleshooting information. This information may enable you to resolve a productissue before you contact Support.

To access a product specific Support page:

1. Go to https://support.emc.com/products.

2. In the Find a Product by Name box, type a product name, and then select theproduct from the list that appears.

3. Click the following button:

Preface

7


https://community.emc.com


https://support.emc.com/products

4. (Optional) To add the product to My Saved Products, in the product specificpage, click Add to My Saved Products.

KnowledgebaseThe Knowledgebase contains applicable solutions that you can search for by solutionnumber, for example, 123456, or by keyword.

To search the Knowledgebase:

1. Go to https://support.emc.com.

2. Click Advanced Search.The screen refreshes and filter options appear.

3. In the Search Support or Find Service Request by Number box, type a solutionnumber or keywords.

4. (Optional) To limit the search to specific products, type a product name in theScope by product box, and then select the product from the list that appears.

5. In the Scope by resource list box, select Knowledgebase.The Knowledgebase Advanced Search panel appears.

6. (Optional) Specify other filters or advanced options.

7. Click the following button:

Live chatTo participate in a live interactive chat with a support agent:


2. Click Chat with a Support Agent.

Service requestsTo obtain in-depth help from Support, submit a service request. To submit a servicerequest:


2. Click Create a Service Request.

Note

To create a service request, you must have a valid support agreement. Contact a salesrepresentative for details about obtaining a valid support agreement or with questionsabout an account.

To review an open service request:


2. Click Manage service requests.

Online communitiesGo to the Community Network at https://community.emc.com for peer contacts,conversations, and content on product support and solutions. Interactively engageonline with customers, partners, and certified professionals for all products.

How to provide feedbackFeedback helps to improve the accuracy, organization, and overall quality ofpublications. You can send feedback to [email protected].

Preface






https://community.emc.com

mailto:[email protected]

CHAPTER 1

ProtectPoint Storage Configuration Overview

This section includes the following topics:

l ProtectPoint family overview............................................................................. 10l Application storage configuration overview........................................................ 12l Data Domain sizing considerations......................................................................12l Discovering application storage.......................................................................... 13l Host considerations............................................................................................ 14

ProtectPoint Storage Configuration Overview 9

ProtectPoint family overviewThe ProtectPoint family consists of the ProtectPoint file system agent, theProtectPoint database application agent, and the ProtectPoint Microsoft applicationagent.

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 Data Domainworkflow 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 DataDomain block services for ProtectPoint management libraries, respectively.

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

Use the ProtectPoint file system agent to perform the following operations:

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

l Trigger the movement of data that is created from the backups on the primarystorage system to the Data Domain devices.

l Create a static image for each LUN in the dataset on the Data Domain system.

l Securely manage the credentials for the Data Domain systems and RecoverPointcluster.

l Scan the Data Domain system for backups that other ProtectPoint and EnterpriseCopy Data Management applications create in addition to backups created by theProtectPoint file system agent.

l Roll back a specified backup to its source devices.

l Restore a backup to the restore devices.

l Manage the ProtectPoint backup and scan catalog.

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

l Display the ProtectPoint version number.

l Validate the content and format of the configuration files.

Configuration fileThe ProtectPoint file system agent configuration file specifies information about:

l The ProtectPoint file system agent protected environment, including the DataDomain name and username.

l Backup and restore source devices or groups.

l Restore devices.

l Performing restores and rollbacks.

The ProtectPoint file system agent provides the following template configuration files:

l ProtectPoint for VMAX environments



l ProtectPoint for RecoverPoint environments

Select the environment-appropriate template and modify it as required.

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

You can have any number of configuration files. You must also update the lockbox withthe Data Domain and optionally the RecoverPoint passwords.

ProtectPoint database application agentThe ProtectPoint database application agent includes the following features:

l Provides the ability to perform backups and restores of DB2, Oracle, or SAP withOracle database data that resides on the primary storage system to protectionstorage on a Data Domain system.

l Provides an integrated experience by using the database-specific backup andrecovery tools, such as DB2 CLI, Oracle RMAN, or SAP BR*Tools.

l Provides application-consistent ProtectPoint backups without manual interventionby the application administrator.

l Operates on the database level, so the database application agent softwareautomatically discovers the primary storage devices where database objectsreside.

l Restores automatically from a replicated backup on a secondary Data Domainsystem when the primary Data Domain system is unavailable.

l Supports listing and lifecycle management of backups using the native databasebackup functionality, and deletion of backups that are no longer required.

l Discovers the corresponding backup devices based on the backup link establishedwith the VMAX primary storage.

l Provides the ability to perform backups and restores over an Ethernet (IP) or FibreChannel (FC) connection.

l Provides support for Internet Protocol version 6 (IPv6) for backups and restores,and supports the Data Domain IPv6, IPv4, and mixed IPv4 and IPv6 networks.

The ProtectPoint database application agent does not distinguish TCP/IP networktypes (LAN, WAN, or MAN) and can successfully operate where packet loss is strictly0% and latency is less than 20 ms.

ProtectPoint Microsoft application agentThe ProtectPoint Microsoft application agent includes the following features:

l Provides the ability to perform backups and restores of Microsoft Exchange andMicrosoft SQL database data that resides on the primary storage system toprotection storage on a Data Domain system.

l Provides an integrated experience by using the database-specific backup andrecovery tools.

l Provide application-consistent ProtectPoint backups without manual interventionby the application administrator.

l Operates on the database level, so the database application agent softwareautomatically discovers the primary storage devices where database objectsreside.


ProtectPoint database application agent 11

l Restores automatically from a replicated backup on a secondary Data Domainsystem when the primary Data Domain system is unavailable.

l Supports listing and lifecycle management of backups using the native databasebackup functionality, and deletion of backups that are no longer required.

l Discovers the corresponding backup devices based on the backup link establishedwith the VMAX primary storage.

l Provides the ability to perform backups and restores over an Ethernet (IP) or FibreChannel (FC) connection.

l Provides support for Internet Protocol version 6 (IPv6) for backups and restores,and supports the Data Domain IPv6, IPv4, and mixed IPv4 and IPv6 networks.

The ProtectPoint Microsoft application agent does not distinguish TCP/IP networktypes (LAN, WAN, or MAN) and can successfully operate where packet loss is strictly0% and latency is less than 20 ms.

Application storage configuration overviewApplication storage is the primary storage for application data. This storage oftenconsists of a number of separate LUNs that have file systems. Mount points or driveletters make the storage available to the application host. These LUNs are the sourcefor any ProtectPoint backup. The following sections provide information aboutconfiguring or discovering LUNs, and using that information to create the equivalentsnapshot target and recovery LUNs.

If it is not necessary to provision new application storage. Discovering applicationstorage on page 13 includes information about discovering the existing applicationstorage.

When configuring application storage, complete the following high-level processes:

l Provision primary storage LUNs to the application recovery host.

l For VMAX configurations, connect Data Domain devices to the primary storagesystem.

l For XtremIO with RecoverPoint configurations, register the Data Domain toRecoverPoint.

Provision the LUNs on the primary storage system to the application recovery hostfirst. Then connect the Data Domain devices to the primary storage system.

The second procedure, connecting the Data Domain devices to the primary storagesystem, requires storage management visibility into both system environments. Youcomplete some tasks in the primary storage environment and other tasks in the DataDomain environment. Therefore, you must have one window open to the primarystorage environment and one window open to the Data Domain environment. Youswitch between environments as you connect the Data Domain devices to the primarystorage system.

Data Domain sizing considerationsTo plan for provisioning the primary storage for ProtectPoint, use the best practicesand limits that are defined in the documentation for the primary storage system.

The following guidelines apply to provisioning an appropriate amount of storage on theprimary Data Domain system, and if applicable, providing an appropriate amount ofstorage at the secondary site:



l To accommodate all the application recovery hosts in the deployment, verify thatsufficient capacity is available on the primary Data Domain system. Each primarystorage LUN requires block services devices of equal or greater size on theprimary Data Domain system. If VMAX devices are being protected, a total of twoblock services devices are needed, one for backups and one for restores. IfXtremIO devices are being protected, only one block services device is needed, forrestores only.

l If applicable, verify that the primary storage system and Data Domain system atthe secondary site have available storage capacity that is greater than or equal tothe storage capacity at the production site.

To estimate the required logical capacity on the Data Domain system, use thefollowing values:

l Number: The number of LUNs to back up.

l Size: The size of each LUN to back up.

l Copies: The number of backups to keep.

l To account for copies of the data on both the backup and restore devices, add twoto the number of backups to keep.

The formula for calculating the logical capacity is: (Number * Size) * (Copies + 2)

The following table displays an example with 10 LUNs that are each 10 GB, keepingfive backups.

Table 3 Sizing calculation example

Element Value

Number 10

Size 10 GB

Copies 5 + 2

Required capacity 700 GB

Note

Logical capacity is calculated before compression and deduplication. Compression anddeduplication reduce the actual amount of capacity consumed.

Capacity monitoring is available at the following levels:

l Logical capacity is reported at the system, MTree (block services for ProtectPointpool), and file (static-image) levels.

l Actual capacity is reported at the system level.

Discovering application storageConfigure ProtectPoint after storage provisioning is complete by discovering existingapplication storage, and then using the storage to determine the Data Domain storagerequirements. The storage administrator can help identify all the necessary storageconfiguration information.

The information that is required includes, but is not limited to, the number of devicesallocated to the application, the geometry of the devices created, and awareness ofthe masking views, ports used, and SAN zoning. The process to provision the Data


Discovering application storage 13

Domain storage and connect the storage to the primary storage system is identical toprovisioning new storage.

Host considerationsThe following host considerations can impact the ProtectPoint implementation:

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

Note

The number of paths that are required depends on the I/O load and theenvironment performance requirements.

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



CHAPTER 2

VMAX Application Storage Configuration

This chapter includes the following topics:

l ProtectPoint environment.................................................................................. 16l ProtectPoint for VMAX prerequisites................................................................. 16l Discovering device geometry..............................................................................19l Provision VMAX storage and encapsulate the Data Domain devices on the VMAX

array.................................................................................................................. 20l Additional storage configuration.........................................................................34l Next steps..........................................................................................................36

VMAX Application Storage Configuration 15

ProtectPoint environmentThe ProtectPoint environment consists of the following components:

l Data Domain:

n A Data Domain system with a supported Data Domain operating system.

n Data Domain block services for ProtectPoint license.

n (Optional) Data Domain replication license.

l VMAX:

n A VMAX array.

n A VMAX license is required for ProtectPoint.

n Solutions Enabler in local mode on the application recovery host.

l Application:

n Application recovery host.

n ProtectPoint agent on the application recovery host.

To view the supported versions of components, go to the following website:


Note

VMAX devices protected by SRDF/M cannot be used by ProtectPoint.

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

ProtectPoint for VMAX prerequisitesThe following are prerequisites for all ProtectPoint for VMAX operations.

ProtectPoint file system agent prerequisitesThe following are ProtectPoint file system agent prerequisites for VMAX operations:

l Solutions Enabler must be installed on the ProtectPoint file system agent host.If you have a user that is not root, the Solutions Enabler documentation providesinformation on how to configure a user account without root access.

l DX directors on the VMAX system must be available to encapsulate the DataDomain protection storage.

l The ProtectPoint file system agent must be installed on the application recoveryhost.

Database application agent and Microsoft application agent prerequisitesThe database and Microsoft application agent prerequisites for ProtectPointoperations are as follows:





l A valid license for the ProtectPoint environment.

l The application agent must be installed on the production and recovery host.

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

l (Optional) Create a user account on the RecoverPoint appliance.

VMAX prerequisitesThe following are VMAX prerequisites for all ProtectPoint for VMAX operations:

l A VMAX array.

l Solutions Enabler in local mode on the application recovery host.

l The required VMAX source capacity licenses.

l In multiple VMAX environments, the recovery devices must be configured in thesame Data Domain vdisk pool.

l SAN zoning between the VMAX FA and DX ports and the application recoveryhosts:

n Ensure that one DX emulation exists on each director within the same engine.Each DX emulation requires two ports exclusively for zoning to the DataDomain system.

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

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

The following figure displays an example of a single SAN switch zoningconfiguration.

Figure 1 SAN zoning example


VMAX prerequisites 17

Data Domain prerequisitesThe following are Data Domain prerequisites for all ProtectPoint for VMAX operations:

l A Data Domain system that ProtectPoint supports.

l IP connectivity to the Data Domain systems on TCP port 3009.

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

DD Boost prerequisitesEnable the DD Boost service, and then create a storage unit.

Data Domain block services prerequisitesThe prerequisites for Data Domain block services operations are as follows:

l (Optional) Create the Data Domain file system (DDFS).

l Configure a username and password for ownership of the Data Domain blockservices for ProtectPoint devices.It is recommended that you create this user with the none role. If required, otherroles can be configured.

l Apply a Data Domain block services for ProtectPoint license.

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

Figure 2 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 4 DDFS storage elements

DDFS directory Description

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

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

/data/col1/backup Contains backups of the data and directory structure of thecollection. This MTree cannot be deleted or renamed.Subdirectories can be created to organize and separate the data.

/data/col1/MTree<X> Represents the lowest level of the Data Domain storage filesystem. Each MTree is an independently managed directory. DataDomain allows up to 100 MTrees to be created, but performancedegradation occurs when more than 32 MTrees are active at onetime.

Data Domain block services for ProtectPointData Domain block services for ProtectPoint allow you to create devices, devicegroups, and device pools. The DD Boost service allows you to configure storage units.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 Data Domain file system (DDFS) stores the block services for ProtectPointobjects. For example, a block services static-image can be treated as a file that resideswithin the DDFS. Therefore, replicating a static-image is the same as replicating a file.By leveraging the services that are provided by the DDFS, the block service forProtectPoint can efficiently create static-images of LUNs.

Note

The DDFS automatically defragments backups that are created in a ProtectPointenvironment to prevent performance degradation over time.

The EMC Data Domain Operating System Administration Guide provides moreinformation about the DDFS.

Discovering device geometryYou will need the geometry of any existing primary storage devices.

For VMAX arrays, Encapsulating Data Domain devices on the VMAX array on page23 provides instructions on identifying the VMAX device geometry and mapping it tothe required geometry for Data Domain devices.


Discovering device geometry 19

Provision VMAX storage and encapsulate the Data Domaindevices on the VMAX array

Provision primary storage LUNs on the VMAX array, and encapsulate the Data Domainblock services devices on the VMAX array.

Create a separate Data Domain device-group for each application host that is part ofthe configuration. If multiple applications will run on a single host, create a separatedevice-group for each application. Place all restore devices intended for use with anapplication into a single device-group for that application. To make use of DataDomain Fastcopy for restore operations, place all the associated device-groups in thesame pool.

ProtectPoint performance considerations for VMAX Gen0 backupsThe full SnapVX copy that is associated with a ProtectPoint Gen0 backup, combinedwith the increased backend load related to SnapVX write handling can result inincreased I/O response time. The QOS speed setting can be changed online, and hasand immediate effect on copies in progress:

l SnapVX copy QOS defaults to maximum speed (0 from a range of 0-16) to achieveminimum copy duration.

l When response time is a concern, use a speed value of 4 to achieve a moderatereduction of the copy rate and lower the response time overhead.

To change the QOS speed setting, type the following command:

symqos -sid <SymmetrixID> -sg <SgName> set clone pace {0-16 | stop | urgent}

When possible, schedule backups with speed settings of 0 to begin when the volumesbeing backed up are under light or moderate write loads. Snapshot overhead is mostsignificant after the snapshot is established, when nearly all writes are intercepted.There is no impact to the write I/O, but the write destage to come later requiresadditional steps, which add overhead to the backend components. If this period mustcoincide with a busy time for the system, additional CPU resources may be required tosupport the increased load.

Provisioning FAST.X restore LUNs to the application recovery hostThis procedure is for provisioning FAST.X LUNs on the VMAX array for newinstallations.

Before you begin

Ensure that FC zoning is complete.

To determine the devices in use, use Solutions Enabler.

To provision the VMAX FAST.X LUNs to the application recovery host, complete thefollowing tasks on the VMAX array:

l Create a storage group.

l Add the devices to the storage group.

l Create a port group.



l Add the front-end ports to the port group where the server is zoned.

l Create an initiator group.

l Add the initiator WWNs of the application recovery host to the initiator group.

l Create a masking view.

l Discover newly provisioned LUNs on the application recovery host.

Procedure

1. From the application recovery host, to configure the VMAX FAST.X devices,use Solutions Enabler.

2. To view the existing VMAX devices, run the following commands:

a. To list the VMAX devices, complete the following steps:

symdev list -sid <SymmetrixID>

b. To view a specific FAST.X device, run the following command:

symdev show [<device number>] -sid <SymmetrixID>

3. To create a storage group, run the following command:

symaccess -sid <SymmetrixID> create -name <GroupName> -type storage [devs <SymDevStart>:<SymDevEnd> | <SymDevName>[, <SymDevName>[, <SymDevName>. . .]] | <-g <DgName> [-std] [-bcv] [-vdev] [-tgt]> | <sg <SgName> [, <SgName1>, <SgName2> . . . <SgNamen>]> <-file <DeviceFileName> [src] [tgt]> [-reserve_id <ResvID> [, <ResvID> [, <ResvID>. . .] ] ] ]

For example:

symaccess -sid 0129 create -name group1 -type storage

Note

This storage group is different from the NsrSnapSG mentioned in theEncapsulating secondary Data Domain system vdisk devices on VMAX section.

4. To add FAST.X devices to the storage group, run the following command:

symsg -sg <SgName> -sid <SymmetrixID> [-i <Interval>] [-c <Count>] add dev <SymDevNumber>

For example:

symsg -sg group1 -sid 0129 add dev 0001A


Provisioning FAST.X restore LUNs to the application recovery host 21

5. To create a port group, run the following command:

symaccess -sid <SymmetrixID> create -name <GroupName> -type port [-dirport <Dir>:<Port> [, <Dir>:<Port>..]]

For example:

symaccess -sid 0129 create -name group1 -type port

6. To add the front-end ports to the port group, run the following command:

symaccess -sid <SymmetrixID> -name <GroupName> -type <port> [-dirport <Dir>:<Port>[, <Dir>:<Port>[, <Dir>;:<Port>. . .]][-ckd] add [-celerra] [-rp]

For example:

symaccess -sid 0129 -name group1 -type port add -dirport 1e:8

The front-end ports are the ones that connect the application recovery host tothe VMAX array.

7. To create an initiator group, run the following command:

symaccess -sid <SymmetrixID> create -name <GroupName> -type initiator [-wwn <wwn> | -iscsi <iscsi> | -file <InitiatorFilename> | -ig <InitiatorGroupName>] [-consistent_lun]

For example:

symaccess -sid 0129 create -name group1 -type initiator -consistent_lun

Note

The -consistent_lun option forces all devices that are masked to theinitiator group to connect to the same LUN with all available ports.

8. To add the initiator WWNs to the initiator group, run the following command:

symaccess -sid <SymmetrixID> -name <GroupName> -type initiator -wwn <wwn> | -iscsi <iscsi> | -ig <InitiatorGroupName> | -f <InitiatorFilename> add

For example:

symaccess -sid 0129 -name group1 -type initiator -wwn 6002188000002ddb5d0525eee8a00011 add



Initiators can be added to an existing initiator group by specifying the initiatortype (-wwn or -iscsi), the initiator group name, or by using an input file.

9. To create a masking view, run the following command:

symaccess create view -sid <SymmetrixID> -name <ViewName> -sg <StorageGroupName> -pg <PortGroupName> -ig <InitiatorGroupName> [-reserve_id <ResvID> [, <ResvID>[, <ResvID>...] ] ] [-lun addr] [-ckd] [-celerra] [-rp]

For example:

symaccess create view -sid 0129 -name view1 -sg group2 -pg portgroup1 -ig initator_group1

After you put the storage group, the port group, and the initiator group in themasking view, the initiators in the initiator group can see the devices via theport in the port group.

10. To update the local symapi database on the application recovery host, run thefollowing command:

symcfg discover

Encapsulating Data Domain devices on the VMAX arrayThis procedure is for encapsulating Data Domain devices on the VMAX array for newinstallations. Some of these steps may not be needed in all cases. To encapsulate theData Domain devices on the VMAX array, complete the following steps on theapplication recovery host. Use the application recovery host to access both the VMAXand Data Domain environments.

Before you begin

Verify that the following prerequisites are met:

l Before you begin, to determine the devices in use, use the commands in the DataDomain Operating System Administration Guide and the Solutions Enablerfunctionality. Then use that information to complete the tasks in this section, asapplicable.

l You must have already provisioned LUNs on the VMAX array to the applicationrecovery host.

l You know or can obtain the geometry of the devices that are created on theVMAX array.

l You are logged in to the host where Solutions Enabler is installed.

l You complete some tasks in the VMAX environment, and other tasks in the DataDomain environment. Therefore, you must have one window open to the VMAXenvironment and one window open to the Data Domain environment.

l Complete the following tasks on the Data Domain system:

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

2. Enable block services for ProtectPoint if not already enabled.


Encapsulating Data Domain devices on the VMAX array 23

3. Create a block services for ProtectPoint device pool.

4. Create a block services for ProtectPoint device-group.

5. Create block services for ProtectPoint devices that have the equivalent orlarger geometry as the VMAX primary LUNs. Create two block services forProtectPoint devices for every device that is created on the VMAX array, onefor backups and one for restores.

6. Create an access group on the Data Domain.

7. Add the block services for ProtectPoint devices to the access group on theData Domain.

8. Verify that the VMAX DX ports and the Data Domain endpoint ports are zonedtogether.

9. View the list of VMAX initiators on the Data Domain.

10. Add the VMAX initiators to the access group on the Data Domain.

l To complete the following steps on the VMAX array, use Solutions Enabler:

1. View the back-end ports (DX ports) on the VMAX array and display the WWNs.

2. Display the LUNs that are visible for a specific WWN.

3. List the disk groups that are available on the VMAX array.

4. Use the FAST.X functionality to encapsulate the Data Domain disks on theVMAX array.

l Encapsulating an external LUN creates the VMAX LUN that enables access to theexternal LUN. Manually set the encapsulated LUN as the snapshot target.Encapsulating the block services for ProtectPoint restore LUNs is required forrestoration operations.

l The VMAX array must have four paths to the Data Domain system to correctlyenable the relationship between the two systems. ProtectPoint for VMAXprerequisites on page 16 provides more information about path requirements.

Procedure

1. From the application recovery host, log in to the Data Domain system as thesystem administrator, sysadmin.

2. In the Data Domain environment, enable the block services for ProtectPointprotocol if not already enabled.

a. To verify the block services for ProtectPoint license is enabled, run thefollowing command:

license show

b. If a license is not already enabled, add the license by using the followingcommand:

license add <license_key>

Output that is similar to the following appears:

License “AAAA-BBBB-CCCC-DDDD” added.



c. To enable block services for ProtectPoint, run the following command:

vdisk enable

Note

Enabling block services for ProtectPoint enables a limited set of DD Boostfeatures for ProtectPoint clients only. To enable full access to DD Boostfunctionality for all clients, add a DD Boost license.

d. To verify block services for ProtectPoint are enabled, run the followingcommand:

vdisk status


VDISK admin state: enabled, process is running, licensed

3. To create a user to own the new block services for ProtectPoint device pool,run the following command:

user add <user> [role {admin | security | user | backup-operator | none}]

For example:

user add user1 role none

Note

The Data Domain Operating System Version Command Reference Guide providesmore information about the user add command and its options.

4. To create the block services for ProtectPoint device pool, run the followingcommand:

vdisk pool create <pool-name> user <user-name>

For example:

vdisk pool create demo-1 user user1

To name device pools, use the guidelines in Block services for ProtectPointobject hierarchy on page 40.



5. To create the required number of block services for ProtectPoint device-groupswithin the device pool, run the following command:

vdisk device-group create <device-group-name> pool <pool-name>

For example:

vdisk device-group create demo-devgrp pool demo-1

To name device-groups, use the guidelines in Block services for ProtectPointobject hierarchy on page 40.

Create a separate device-group for each application recovery host.

6. From the host running Solutions Enabler, to view the geometry of the VMAXdevices, run the following commands:

a. To list the VMAX devices, run the following command:


For example:

symdev list -sid 0129


Symmetrix ID: 000196700129 Device Name Dir Device-------------------- ------- -------------------------------- CapSym Physical SA :P Config Attribute Sts (MB)-------------------- ------- --------------------------------00001 Not Visible ???:??? TDEV N/Grp'd ACLX RW 1100002 Not Visible ???:??? TDEV N/Grp'd RW 600003 Not Visible ???:??? TDEV N/Grp'd RW 600004 Not Visible ???:??? TDEV N/Grp'd RW 6…(output truncated for display)…00019 Not Visible ???:??? TDEV N/Grp'd RW 60001A Not Visible ???:??? TDEV N/Grp'd RW 230160001B Not Visible ???:??? TDEV N/Grp'd RW 230160001C Not Visible ???:??? TDEV N/Grp'd RW 230160001D Not Visible ???:??? TDEV N/Grp'd RW 23016000A6 Not Visible ???:??? TDEV N/Grp'd RW 215719000A7 Not Visible ???:??? TDEV N/Grp'd RW 215719000A8 Not Visible ???:??? TDEV N/Grp'd RW 215719

b. To view the geometry of a specific device, run the following command:


For example:

symdev show 0001A -sid 0129




...Geometry : Native{Sectors/Track : 256Tracks/Cylinder : 15Cylinders : 12275512-byte Blocks : 47136000MegaBytes : 23016KiloBytes : 23568000}...

Use the geometry mappings in the following table to create the Data Domainblock services for ProtectPoint devices.

Table 5 VMAX to Data Domain device geometry mappings

VMAX device geometry value Equivalent Data Domain devicegeometry value

Sectors per track Sectors per track

Tracks per cylinder Heads

Cylinders Cylinders

7. On the Data Domain system, to create the block services for ProtectPointdevices that matches the geometry of the devices that are created on theVMAX array, run the following command:

vdisk device create [count <count>] heads <head-count> cylinders <cylinder-count> sectors-per-track <sector-count> pool <pool-name> device-group <device-group-name>


vdisk device create heads 15 cylinders 109227 sectors-per-track 256 pool demo-1 device-group demo-devgrp

Create two devices on the Data Domain for each VMAX device, one for backupand one for restore.

8. (Optional) To display the block services for one or more ProtectPoint pools,device-groups, and devices, run one or more of the following commands:

vdisk pool show detailed pool <pool-name>

vdisk device-group show detailed <group-name>

vdisk device show detailed <device-name>



For example:

vdisk pool show detailed pool demo-1

vdisk device-group show detailed demo-devgrp

vdisk device show detailed device-demo

9. To create an access group, run the following command:

scsitarget group create <group-name> service vdisk

For example:

scsitarget group create demo-accgrp service vdisk

10. To add the new block services for ProtectPoint devices to the access group,run the following command:

vdisk group add <group-name> {device <device-spec> | pool <pool-name> device-group <device-group-name> [device <device-spec>]} [lun <lun>] [primary-endpoint {all | none | <endpoint-list>}] [secondary-endpoint {all | none | <endpoint-list>}]

For example:

vdisk group add demo-accgrp device vdisk-dev16

11. To view the list of initiators, run the following command:

scsitarget initiator show list


Initiator System Address Group Service------------ ----------------------- ----- -------initiator-1 2a:10:00:21:88:00:82:74 n/a n/ainitiator-2 2b:10:00:21:88:00:82:74 n/a n/ainitiator-3 50:02:18:82:08:a0:02:14 n/a n/ainitiator-4 50:02:18:81:08:a1:03:cc n/a n/aucs16d_2a 21:00:00:24:ff:3f:25:1a n/a n/aucs16d_2b 21:00:00:24:ff:3f:25:1b n/a n/a------------ ----------------------- ----- -------

The list displays the VMAX back-end (DX) ports that have logged on to theData Domain system.



12. To rename (alias) the initiators, run the following command:

scsitarget initiator rename <src-initiator-name> <dst-initiator-name>

For example:

scsitarget initiator rename initiator-1 vmax4d_3_08


Initiator 'initiator-1' successfully renamed.

13. To add the initiators to the access group, run the following command:

vdisk group add <group-name> initiator <initiator-spec>

For example:

vdisk group add demo-accgrp initiator symm_9h0

14. Switch to the VMAX environment.

15. To review the list of DX ports, which are connected to the Data Domain systemfrom the VMAX array, run the following command:

symsan list -sid <SymmetrixID> -sanports -DX all -port all

For example:

symsan list -sid 0129 -sanports -DX all -port all

16. To copy the WWN for one of the ports and use the WWN to determine whichLUNs are visible through this WWN, run the following command:

symsan -sid <SymmetrixID> -dir All -p All list -sanluns -wwn <wwn>

For example:

symsan -sid 0129 -dir All -p All list -sanluns -wwn 2800002182DDB5D

The LUN is exposed but is not ready for use yet. The LUN must be encapsulatedon to the VMAX array with FAST.X.

17. To create a VMAX storage group, run the following command:

symsg create <SgName>



For example:

symsg create storage-group-5

Note

If an existing device group is appropriate for the ProtectPoint implementation,you can use it instead of creating a device group. To see all the device groupson the VMAX array, run the symdg list -sid <SymmetrixID> command.

18. To add the source VMAX devices to the storage group, run the followingcommand:

symsg -g <DgName> add dev <device_ID>

For example:

symsg -g storage-group-5 add dev 0001A

19. Encapsulate the Data Domain disk on the VMAX array. There are two ways toencapsulate disks:

l To encapsulate disks individually, run the following command:

symconfigure -sid <SymmetrixID> -cmd "add external_disk, wwn=<wwn>, encapsulate_data=yes;" commit -v -nop

For example:

symconfigure -sid 0129 -cmd "add external_disk, wwn=6002189000002DDB5D0525EEE8A00011, encapsulate_data=yes;" commit -v -nop

It takes approximately seven minutes to encapsulate each device.

l To encapsulate a group of devices, run the following commands:

a. In a BASH shell on the application recovery host, to capture all the blockservices for ProtectPoint devices to encapsulate in a text file, run thefollowing command:

ssh sysadmin@ {<DD-hostname>} vdisk device show list pool {<pool-name>} device-group {<device-group-name>} | awk '/^vdisk-dev/{print "add external_disk wwn=" $5 ", encapsulate_data=YES;"}' | sed 's/://g' > devs.txt

Note

The command fails if there are fewer than two devices that are specifiedin the text file.



b. On the application recovery host, to encapsulate the block services forProtectPoint devices that are listed in the text file, run the followingcommand:

symconfigure commit -f devs.txt


…Establishing a configuration change session....Established.Processing symmetrix 000196700129Performing Access checks.......................Allowed.Checking Device Reservations...................Allowed.Initiating COMMIT of configuration changes.....Queued.COMMIT requesting required resources...........Obtained.Step 008 of 064 steps..........................Executing.…Step 091 of 214 steps..........................Executing.…Step 210 of 219 steps..........................Executing.Local: COMMIT..................................Done.New symdev: 0004C [DATA device]New symdev: 000BA [TDEV]Terminating the configuration change session........Done.The configuration change session has successfully completed.

Note

The VMAX array returns a contiguous range of new device nameswhenever possible. However, the range of device names is not alwayscontiguous.

The system performs the following steps:

a. Takes the device with the specified WWN. The device is now visible to theVMAX array.

b. Encapsulates the device.

c. Puts the device into the external device group.

d. Assigns a name to the device.

20. To add the encapsulated Data Domain target devices to the storage group, runthe following command:

symsg -g <SgName> add dev <device-number> -tgt

For example:

symsg -g storage-group-5 add dev 0002A -tgt

21. To establish the relationship between the VMAX array and Data Domain system,and activate the snapshot, run the following command:

symsnapvx -sid <SymmetrixID> -sg <SgName> establish -name <SnapshotName>



For example:

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

Note

If additional devices or device groups are added to the ProtectPointenvironment after the initial configuration, this step must be repeated for thenew devices or device groups.

22. To move the data from the VMAX array on to the Data Domain system, run thefollowing command:

symsnapvx -sid <SymmetrixID> -sg <SgName> link -copy -snapshot_name <SnapshotName>

For example:

symsnapvx -sid 0129 -sg storage-group-5 link -copy -snapshot_name dg5-snap

This command moves the changed blocks on the source device to the targetdevice.

Note

If additional devices or device groups are added to the ProtectPointenvironment after the initial configuration, this step must be repeated for thenew devices or device groups.

23. (Optional) To set the data transfer rate for moving data from the VMAX arrayto the Data Domain system when a snapshot is created and activated for thefirst time, run the following command:

symqos -sid <SymmetrixID> -sg <SgName> set clone pace {0-16 | stop | urgent}

Note

If you must change the clone pace, start with a setting of 4. This value results ina moderate reduction of the copy rate for Gen0 backups, which lowers theresponse time overhead.

24. To check the status of the link copy operation, run the following command:

symsnapvx list -detail -sid <SymmetrixID> {-sg <SgName> | -devs <First DeviceInRange>:<LastDeviceInRange>} -linked



For example:

symsnapvx list -detail -sid 0129 -sg storage-group-5 -linked

25. If the environment is to use FAST.X restore operations, create a VMAX storagegroup for the restore LUNs, and then add the encapsulated devices to it.

The default storage group name is NsrSnapSG. To use a non-default name forthe storage group, that name must be specified in the ProtectPoint file systemagent or application agent configuration files.

Perform the following steps:

a. To create a storage group, run the following command:

symsg -sid <SymmetrixID> create ProtectPointRestoreGroup

For example:

symsg -sid 0129 create ProtectPointRestoreGroup

Note

The storage group name is case-insensitive.

b. To add the restore devices to the storage group, run the following command:

symsg -sid <SymmetrixID> -sg ProtectPointRestoreGroup add dev <device-number>

Deleting an encapsulated disk

If the environment requirements change, Data Domain block services for ProtectPointdevices that are encapsulated on the VMAX system can be deleted from theProtectPoint configuration.

Note

You complete some tasks in the VMAX environment, and other tasks in the DataDomain environment. Therefore, you must have one window open to the VMAXenvironment and one window open to the Data Domain environment. Also, it isextremely important that you remove the devices from the VMAX before you removethe devices from the Data Domain.

Procedure

1. Terminate all snapshot and replication sessions to the encapsulated disk youintend to delete.

Perform the following steps:

a. On the ProtectPoint file system agent, type Ctrl + C in the terminalwindow to abort any backups in progress.



b. To list all the locked VMAX devices, run the following command:

symdev list -lock

c. If required, to unlock the VMAX devices being deleted, run the followingcommand:

symdev release -lock -nop -sid <SymmetrixID>

For example:

symdev release -lock -nop -sid 0129

2. Place the encapsulated device in a not-ready state.

To set the devices to a not-ready state, run the following command:

symdev -sid <SymmetrixID> {-devs <FirstDeviceInRange>:<LastDeviceInRange>} not_ready

For example:

symdev -sid 0129 -devs 0001A:0001B not_ready

3. From any hosts that have access to the encapsulated device to be deleted,unmap the device so the hosts cannot access it.

4. To delete the encapsulated disk on the VMAX, run the following command:

symconfigure -sid <SymmetrixID> -cmd "remove external_disk <wwn=<wwn> | spid=<spindleID>>;" commit -nop

For example:

symconfigure -sid 0129 -cmd "remove external_disk wwn=2800002182DDB5D;" commit -nop

5. To delete the corresponding block services for ProtectPoint device from theData Domain system, run the following command:

vdisk device destroy <device-name> [destroy static-images {yes | no}

Additional storage configurationOptionally complete the following additional storage configuration tasks.



N_Port ID VirtualizationTo enable N_Port ID Virtualization (NPIV) on the Data Domain system, complete thefollowing steps.

Enabling N_Port ID VirtualizationN_Port ID Virtualization (NPIV) is a Fibre Channel feature in which multiple endpointscan share a single physical port. NPIV eases hardware requirements and providesendpoint failover/failback capabilities. NPIV is not configured by default, except in aHA configuration.

NPIV provides simplified multiple-system consolidation:

l NPIV is an ANSI T11 standard that allows a single HBA physical port to registerwith a Fibre Channel fabric using multiple WWPNs.

l The virtual and physical ports have the same port properties and behave the same.

l There may be m:1 relationships between the endpoints and the port, that is,multiple endpoints can share the same physical port.

Specifically, enabling NPIV enables the following features:

l Multiple endpoints are allowed per physical port, each using a virtual (NPIV) port.The base port is a placeholder for the physical port and is not associated with anendpoint.

l Endpoint failover/failback is automatically enabled when using NPIV.

Note

After NPIV is enabled, the Secondary System Address must be specified at eachof the endpoints. If not, endpoint failover does not occur.

l Multiple Data Domain systems can be consolidated into a single Data Domainsystem, however, the number of HBAs remains the same on the single DataDomain system.

l The endpoint failover is triggered when FC-SSM detects when a port goes fromonline to offline. If the physical port is offline before scsitarget is enabled, and theport is still offline after scsitarget is enabled, an endpoint failover is not possible.The endpoint failover is not possible because FC-SSM does not generate a portoffline event. If the port comes back online and auto-failback is enabled, any failedover endpoints that use that port as a primary port fail-back to the primary port.

The Data Domain HA feature requires NPIV to move WWNs between the nodes of anHA pair during the failover process.


N_Port ID Virtualization 35

Note

Before enabling NPIV, the following conditions must be met:

l The Data Domain system must be running a supported version of Data Domain OS.

l All ports must be connected to 4Gb, 8Gb, and 16 Gb Fibre Channel HBA and SLIC.

l The Data Domain system ID must be valid, that is, it must not be 0.

In addition, port topologies and port names are reviewed and may prevent NPIV frombeing enabled:

l NPIV is allowed if the topology for all ports is loop-preferred.

l NPIV is allowed if the topology for some of the ports is loop-preferred. However,NPIV must be disabled for ports that are loop-only, or you must reconfigure thetopology to loop-preferred for proper functionality.

l NPIV is not allowed if none of the ports have a topology of loop-preferred.

l If port names are present in access groups, the port names are replaced with theirassociated endpoint names.

Procedure

1. Select Hardware > Fibre Channel.

2. Next to NPIV: Disabled, select Enable.

3. In the Enable NPIV dialog box, you are warned that all Fibre Channel ports mustbe disabled before NPIV can be enabled. If you are sure that you want tocontinue, select Yes.

Next stepsAfter the storage configuration is complete, the application or database administratormust install the agent to protect their environment. The next stages of theProtectPoint configuration and installation process are covered in:

l EMC ProtectPoint File System Agent Installation and Configuration Guide

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

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



CHAPTER 3

XtremIO Application Storage Configuration

This chapter includes the following topics:

l ProtectPoint for XtremIO with RecoverPoint environment................................38l ProtectPoint for XtremIO with RecoverPoint prerequisites............................... 38l Configure XtremIO storage and connect the Data Domain system, RecoverPoint

cluster, and XtremIO cluster.............................................................................. 42l Additional storage configuration........................................................................ 65l Next steps......................................................................................................... 66

XtremIO Application Storage Configuration 37

ProtectPoint for XtremIO with RecoverPoint environmentThe ProtectPoint for XtremIO with RecoverPoint environment consists of thefollowing components:

l Data Domain:

n A Data Domain system with a supported Data Domain operating system.

n Data Domain block services for ProtectPoint.

n DD Boost.

n (Optional) Data Domain MTree replication.

l RecoverPoint:

n A RecoverPoint cluster with two to eight RecoverPoint appliances.

l XtremIO:

n An XtremIO cluster running storage array software.

l Application:

n Application recovery host.

n ProtectPoint agent on the application recovery host.

To view the supported versions of components, go to the following website:


ProtectPoint for XtremIO with RecoverPoint prerequisitesThe following are prerequisites for all ProtectPoint for XtremIO with RecoverPointoperations.

ProtectPoint file system agent prerequisitesThe ProtectPoint file system agent prerequisites for all ProtectPoint for XtremIO withRecoverPoint operations are as follows:

l User accounts for block services for ProtectPoint, and DD Boost must be createdon the Data Domain system.


l The ProtectPoint file system agent must be installed on the application recoveryhost.

Database application agent and Microsoft application agent prerequisitesThe database and Microsoft application agent prerequisites for ProtectPointoperations are as follows:

l A valid license for the ProtectPoint environment.

l The application agent must be installed on the production and recovery host.

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






RecoverPoint prerequisitesThe RecoverPoint prerequisites for all ProtectPoint for XtremIO operations are asfollows:

l A RecoverPoint backup (BK) license.

l A RecoverPoint cluster with RecoverPoint appliances, running RecoverPointsoftware.

l 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.

l Port 11111 must be open between the RecoverPoint appliances and XtremIO SYMmodule on X1-SC1 and X1-SC2.

l IP connectivity must be configured between the RecoverPoint appliance and theData Domain system.For IP connections between the RecoverPoint appliances and the Data Domainsystem, the Data Domain ifgroup feature provides improved network performanceby spreading the network traffic across multiple network interfaces. The EMC DataDomain Operating System Administration Guide provides more details aboutifgroups.

l FC zoning between the RPA and the XtremIO cluster. FC zoning is optionalbetween the RecoverPoint appliance and the Data Domain system.

l (Optional) FC zoning between the RecoverPoint appliance and the Data Domainsystem is only required if DD Boost over FC is used for communication betweenthe RecoverPoint appliance and the Data Domain system:

n Zone at least two initiators from the RecoverPoint appliance to the DataDomain system.

n One zone per fabric between the RecoverPoint appliance and the XtremIOcluster. Include all the RecoverPoint appliance ports that are intended forXtremIO connectivity, and all the XtremIO ports that are intended forRecoverPoint appliance connectivity in the zone.

n Zone the RecoverPoint initiators to multiple targets on the Data Domainsystem or XtremIO cluster in accordance with RecoverPoint best practices.

XtremIO prerequisitesThe XtremIO prerequisites for all ProtectPoint for XtremIO operations are as follows:

l An XtremIO cluster running XtremIO software.

l FC zoning must be configured between the XtremIO cluster and the applicationrecovery host:

n Use a single-initiator per single-target (1:1) zoning scheme or use multipathingbetween XtremIO and the hosts for failover and redundancy. If the FCswitchzone count limitation has been reached, it is also possible to use single-initiator per multiple-target (1:many) zoning scheme.


RecoverPoint prerequisites 39

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

n Enable MPIO if two or more paths are zoned to a Windows application recoveryhost.

Data Domain prerequisitesThe Data Domain prerequisites for all ProtectPoint for XtremIO operations are asfollows:

l A Data Domain system that ProtectPoint supports.

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

l A Data Domain system with DD Boost enabled.

l Data Domain Cloud Tier can be enabled, but the Data Domain storage unit thatProtectPoint uses cannot have a data movement policy.

DD Boost prerequisitesEnable the DD Boost service, and then create a storage unit.

Data Domain block services prerequisitesThe prerequisites for Data Domain block services operations are as follows:

l (Optional) Create the Data Domain file system (DDFS).

l Configure a username and password for ownership of the Data Domain blockservices for ProtectPoint devices.It is recommended that you create this user with the none role. If required, otherroles can be configured.

l Apply a Data Domain block services for ProtectPoint license.

Block services for ProtectPoint object hierarchyTo plan the ProtectPoint configuration, use the object hierarchy mappings in thefollowing table.

Table 6 Block services for ProtectPoint object hierarchy mappings

Storage object Mapping level

Pool Department

Device-group Application

Device Device

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 storage layoutThe following figure displays the storage layout of the DDFS.



Figure 3 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 7 DDFS storage elements

DDFS directory Description

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

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

/data/col1/backup Contains backups of the data and directory structure of thecollection. This MTree cannot be deleted or renamed.Subdirectories can be created to organize and separate the data.

/data/col1/MTree<X> Represents the lowest level of the Data Domain storage filesystem. Each MTree is an independently managed directory. DataDomain allows up to 100 MTrees to be created, but performancedegradation occurs when more than 32 MTrees are active at onetime.

Data Domain block services for ProtectPointData Domain block services for ProtectPoint allow you to create devices, devicegroups, and device pools. The DD Boost service allows you to configure storage units.Block services also provide additional functionality, such as creating static-images(snapshots) and replicating data.


Data Domain block services prerequisites 41

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 Data Domain file system (DDFS) stores the block services for ProtectPointobjects. For example, a block services static-image can be treated as a file that resideswithin the DDFS. Therefore, replicating a static-image is the same as replicating a file.By leveraging the services that are provided by the DDFS, the block service forProtectPoint can efficiently create static-images of LUNs.

Note

The DDFS automatically defragments backups that are created in a ProtectPointenvironment to prevent performance degradation over time.

The EMC Data Domain Operating System Administration Guide provides moreinformation about the DDFS.

Configure XtremIO storage and connect the Data Domainsystem, RecoverPoint cluster, and XtremIO cluster

Provision primary storage Volumes on the XtremIO cluster, and connect the DataDomain system, RecoverPoint cluster, and XtremIO cluster to configure theprotection storage.

RecoverPoint automatically creates the Data Domain block services for ProtectPointdevice-groups and devices for backups, and places the devices in the device-groups.The device-groups and devices for restores must be created and populated manually.The device-group must contain at least as many restore devices as there are backupdevices, and the restore devices must be the same size or larger than the static-images to be restored.

Note

Do not place restore devices into the backup device-group created by RecoverPointon the Data Domain system.

Creating an XtremIO initiator groupBefore you begin

Perform the following tasks:

l Ensure that the RecoverPoint cluster is zoned so it can see the XtremIO cluster.

l Ensure that the RecoverPoint cluster is configured and running.

l Obtain the port address for each RecoverPoint appliance FC port.

To create an XtremIO initiator group that contains all of the RecoverPoint FC ports,complete the following steps.

Procedure

1. In XMS, click Configuration > Initiator Groups > Create Initiator Group.

2. Specify a name for the initiator group.



3. Click Add.

4. Specify a name for the initiator.

5. Select the initiator operating system.

6. From the list box, select the initiator Port Address.

7. To add all the RecoverPoint appliance initiators to the initiator group, repeatsteps 3 to 6.

8. To optionally assign Tags to the Volumes, click Next, or to skip creating tags,click Finish.

9. Select an existing Tag, or to create a Tag, click Create Tag, and then specifythe following information:

l In Tag caption, specify a descriptive name for the Tag, such asprotectpoint.

l Tag color.

l Tag nesting path.

10. Click OK.

11. To apply the new Tag to the new Volumes, select the new Tag.

12. Click Finish.

13. To create an initiator group for the primary application recovery host, using thehost FC port addresses for steps 6 and 7, repeat steps in this procedure.

Configuring XtremIO storage for a single volumeTo configure primary storage on the XtremIO system by creating a single Volume at atime, complete the following steps.

Procedure

1. Login to the XtremIO Management Server (XMS).

2. In XMS, click Configuration > Volumes > Create Volume.

3. Specify the following information:

a. A name for the Volume (up to 128 characters).

b. The amount of disk space that is allocated for the Volume.

Note

Be aware of the following requirements for creating Volumes:

l The minimum Volume size is 1 MB.

l The volume size should be in multiples of 8 KB.

l The volume size can be specified in KB, MB, GB, TB, and PB.

c. Select Normal (512 LBs) as the logical block size and alignment-offset.

d. Optionally enable Small I/O Alerts.

e. Optionally enable Unaligned I/O Alerts.

f. Optionally enable VAAI TP Alerts.


Configuring XtremIO storage for a single volume 43




l Tag color.

l Tag nesting path.

Note

Tagging objects enables you to logically group, locate and manage multipleentities, and perform operations on multiple objects, using a single usercommand. You can use tagging to aggregate objects based on businessrequirements, and assign Tags according to related applications for ease-of-management. Each object can have multiple Tags to reflect the object'sfunction and position.

6. Click OK.

7. To apply the new tag to the newly created Volumes, select the new Tag.

8. Click Finish.

9. Present the Volumes to the host.

a. Select a Volume.

b. Select Configuration > Volumes.

c. Click Create/Modify Mapping.

d. Select the initiator groups to which to expose the volume.

Note

Volumes must be exposed to both the RecoverPoint appliance initiatorgroup, and the host initiator group.

e. Click Next.

f. Click Finish.

Configuring XtremIO storage for multiple volumesTo configure primary storage on the XtremIO system by configuring multiple volumesat one time, complete the following steps.

Procedure

1. Login to the XtremIO Management Server (XMS).

2. In XMS, click Configuration > Volumes > Create Volume.

3. Click Add Multiple.

4. Specify the following information:

a. The number of Volumes to create.

b. A name for the Volume (up to 128 characters).



c. The Start Index for the Volumes.

Note

Each Volume must have a unique name. Each time that you add multipleVolumes, the suffix automatically starts at 1. Therefore, adding multipleVolumes more than once while using the same prefix, results in repeatingnames.

d. The amount of disk space that is allocated for the Volume.

Note

Be aware of the following requirements for creating Volumes:

l The minimum Volume size is 1 MB.

l The volume size should be in multiples of 8 KB.

l The volume size can be specified in KB, MB, GB, TB, and PB.

e. Select Normal (512 LBs) as the logical block size and alignment-offset.

f. (Optional) Enable Small I/O Alerts.

g. (Optional) Enable Unaligned I/O Alerts.

h. (Optional) Enable VAAI TP Alerts.




l Tag color.

l Tag nesting path.

7. Click OK.

8. To apply the new tag to the new Volumes, select the new Tag.

9. Click Finish.

10. Present the Volumes to the host.

a. Select Volumes.

b. Select Configuration > Volumes.

c. Click Create/Modify Mapping.

d. Select the initiator groups to which to expose the volume.

Note

Volumes must be exposed to both the RecoverPoint appliance initiatorgroup, and the host initiator group.


Configuring XtremIO storage for multiple volumes 45

e. Click Next.

f. Click Finish.

Configuring Data Domain services and usersTo configure Data Domain services and users, complete the following steps.

Before you begin

l The DDFS must be configured.

l Obtain a block services for ProtectPoint license key.

Procedure

1. From the application recovery host, log in to the Data Domain system as thesystem administrator, sysadmin.

2. If not already enabled, enable the block services for ProtectPoint protocol.

a. To verify the block services for ProtectPoint license is enabled, run thefollowing command:

license show

b. If the license is not already enabled, to add the license, run the followingcommand:

license add <license_key>


License “AAAA-BBBB-CCCC-DDDD” added.

c. To enable block services for ProtectPoint, run the following command:

vdisk enable

Note

Enabling block services for ProtectPoint enables a limited set of DD Boostfeatures for ProtectPoint clients only. Optionally, to enable full access to DDBoost functionality for all clients, add a DD Boost license.

d. To verify block services for ProtectPoint are enabled, run the followingcommand:

vdisk status


VDISK admin state: enabled, process is running, licensed



3. To verify that DD Boost is enabled, run the following command:

ddboost status

4. To create a user to own the new block services for ProtectPoint device pooland the DD Boost storage-unit, run the following command:

user add <user> [role {admin | security | user | backup-operator | none}]

For example:

user add user1 role none

Note

The Data Domain Operating System Version Command Reference Guide providesmore information about the user add command and its options.

5. To add DD Boost privileges to the new username, run the following command:

ddboost user assign <user>

For example:

ddboost user assign user1

6. Do not log out of the Data Domain system.

Enabling encryption over a WAN connectionThe database application agent provides support for DD Boost clients to have in-flightdata encryption with a Data Domain 5.5 or later operating system over a WANconnection.

To enable the in-flight data encryption over a WAN connection, you can configure theData Domain system with either medium-strength or high-strength TLS encryption.For example, run the following ddboost command to set the required TLS encryptionfor the client systems:

ddboost clients add <client_list> [encryption-strength {medium | high} authentication-mode {one-way | two-way | anonymous}] | [authentication-mode kerberos]

The configuration is transparent to the application agent. The Data Domain BoostAdministration Guide provides details.


Enabling encryption over a WAN connection 47

Configuring the DD Boost over Fibre Channel serviceTo configure the DD Boost over Fibre Channel (DFC) service, complete the followingsteps.

Before you begin

Ensure that the application recovery host and the Data Domain system can see eachother over the FC SAN.

Procedure

1. To enable DFC, run the following command:

ddboost option set fc enabled

2. (Optional) To set the DFC-server-name, run the following command:

ddboost fc dfc-server-name set <server-name>

For example:

ddboost fc dfc-server-name set ddboost-fc-server

Alternatively, accept the default, which has the format DFC-<basehostname>. The hostname cannot be the fully qualified domain name.

A valid DFC server name consists of one or more of the following characters:

l Lowercase letters (a-z)l Uppercase letters (A–Z)l Digits (0–9)l Underscore (_)l Dash (–)

Note

The dot or period character (.) is not valid within a dfc-server-name. Thisprecludes using the fully qualified domain name of a Data Domain system as itsdfc-server-name.

Similar to IP hostnames, the dfc-server-name is not case-sensitive. MultipleData Domain systems accessible by the same clients using DDBoost-over-FCshould be configured without case-sensitive dfc-server-name.

3. To create a DD Boost FC group, run the following command:

ddboost fc group create <group-name>

For example:

ddboost fc group create boost-fc-group



4. To populate the DD Boost FC group, add DFC devices.

When creating devices:

l For Linux or UNIX hosts, create one device per host initiator.

l For Windows hosts, create one device per path to the host.

Run the following command:

ddboost fc group modify <group-name> device-set count <count> endpoint {all|none|<endpoint-list>}

For example:

ddboost fc group modify boost-fc-group device-set count 8 endpoint all

5. To allow the host to see the DD Boost FC group and the devices it contains, addinitiators to the DD Boost FC group.


ddboost fc group add <group-name> initiator "<initiator-spec>"

For example:

ddboost fc group add initiator "initiator-15, initiator-16"


7. From the application recovery host, ensure that the user who performs thebackups and restores has the required permission to access the DFC devices.

Configuring DD Boost storage unitsTo configure the DD Boost storage units that are required for ProtectPoint, completethe following steps.

Before you begin


l Ensure that DD Boost is configured.

l Ensure that a username exists with DD Boost privileges to own the storage units.

Procedure

1. To create a DD Boost storage unit for RecoverPoint to use, run the followingcommand:

ddboost storage-unit create <storage-unit> user <user>

For example:

ddboost storage-unit create RecoverPointStorageUnit user user1


Configuring DD Boost storage units 49

Note

The storage unit is automatically created as /data/col1/<storage-unit>.Specify a descriptive name when creating the storage unit.

2. To serve as the ProtectPoint catalog, create a DD Boost storage unit.


ddboost storage-unit create <storage-unit> user <user>

For example:

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.


Configuring block services for ProtectPoint objectsTo configure block services for ProtectPoint pools, device-groups, and devices,complete the following steps.

Before you begin


l Ensure that Block services for ProtectPoint is enabled.

l Ensure that Block services for ProtectPoint privileges are assigned to the sameusername that owns the DD Boost storage-units.

Procedure

1. To create the block services for ProtectPoint backup device pool, run thefollowing command:


For example:

vdisk pool create backup-demo-1 user user1

Note




2. To create the block services for ProtectPoint restore device pool, run thefollowing command:


For example:

vdisk pool create restore-demo-1 user user1

Note


3. To create the block services for ProtectPoint restore device-group, run thefollowing command:


For example:

vdisk device-group create restore-group pool restore-demo-1

Note

To name device-groups, use the guidelines in Block services for ProtectPointobject hierarchy on page 40.

4. To create the block services for ProtectPoint restore devices, run the followingcommand:

vdisk device create count <count> capacity <n> {MiB|GiB|TiB|PiB|sectors} pool <pool-name> device-group <device-group-name>

For example:

vdisk device create count 5 capacity 1 GiB pool restore-demo-1 device-group restore-group

Note

Create at least as many restore devices as there are backup devices. Therestore devices must be the same size or larger than the largest backup devicecreated by RecoverPoint.



Configuring block services for ProtectPoint objects 51

Configuring a Data Domain access group for the application recovery hostFor Fibre Channel environments, to configure an access group to mask the restoredevices to the application recovery host, complete the following steps.

Before you begin


l Ensure that the Data Domain system and the application recovery host can seeeach other over the FC SAN.

l Ensure that the block services for ProtectPoint restore devices and device-groupsare configured.

Procedure


scsitarget group create <scsi-group-name> service vdisk

For example:

sysadmin@lfcp1158# scsitarget group create lfcp1011 service vdisk


Group 'lfcp1011' successfully created.




Initiator System Address Group Service----------- ----------------------- ----- -------initiator-1 2a:10:00:21:88:00:82:74 n/a n/ainitiator-2 2b:10:00:21:88:00:82:74 n/a n/ainitiator-3 50:02:18:82:08:a0:02:14 n/a n/ainitiator-4 50:02:18:81:08:a1:03:cc n/a n/aucs16d_2a 21:00:00:24:ff:3f:25:1a n/a n/aucs16d_2b 21:00:00:24:ff:3f:25:1b n/a n/a----------- ----------------------- ----- -------

The list displays the application recovery host HBA ports that have logged on tothe Data Domain system.



For example:

scsitarget initiator rename initiator-1 arhost_3_08





4. To add host initiators to the access group, run the following command:

scsitarget group add <scsi-group-name> initiator <host-WWN>

For example:

scsitarget group add restore-access-group initiator 2a:10:00:21:88:00:82:74

5. To add the restore devices to the access group, run the following command:

scsitarget group add <scsi-group-name> device <device-name>

For example:

scsitarget group add restore-access-group device vdisk-dev0

6. To verify that the host can see the block services for ProtectPoint devices, runthe following command:

scsitarget group show list


Group Name Service # Initiators # Devices-------------------- ------- ------------ ---------restore-access-group VDISK 3 8-------------------- ------- ------------ ---------

The Data Domain system displays all the host initiators and block devices addedto the access group.

Logging into RecoverPointBefore you begin

l Obtain your RPA cluster management IP.

l Optionally obtain your RecoverPoint username and password.

Procedure

1. Open a web browser and enter the cluster management IP into your browseraddress bar. The RecoverPoint login screen is displayed.


Logging into RecoverPoint 53

2. In the RecoverPoint login screen, log in with your username and password, orenter the default RecoverPoint Username admin and Password admin.

Results

Unisphere for RecoverPoint is displayed.

After you finish

Select RPA Clusters > RPA-Cluster-Name > RPAs. Click the tab of each RPA clusterand ensure that a green checkbox appears in both the Status and Connectivitycolumns of all RPAs at each RPA cluster.

Install a license in RecoverPointBefore you begin

l Access and activate your entitlements.

l Obtain a RecoverPoint license file.

Procedure

1. Select Admin > Manage Licenses to display the Manage Licenses screen.

2. Then for each license file:

a. Click Add.



b. Click Browse...

c. Select the license file.

d. Click OK.

Register storage in RecoverPointRegister your Data Domain systems and the XtremIO Management servers on the RPAcluster and define whether to transfer data using FC or IP.

Before you begin

l Configure access to the XtremIO arrays you want to protect, and SAN and FCaccess to your Data Domain.

l Zone and mask your XtremIO arrays, Data Domains and their block services forProtectPoint pools to the relevant RPA clusters.

l Before you register the Data Domain system on the RPA cluster:

n Ensure the RPA cluster and the Data Domain system can see each other overthe IP LAN and (optionally) FC SAN.

n Obtain the Data Domain IP address in IPv4 or IPv6 format.

n Obtain the DD Boost username and password.

n Obtain the name of the DD Boost storage unit to use.

l Before you register the XtremIO Management Server on the RPA cluster:

n Ensure the RPA cluster and the XtremIO cluster can see each other over theFC SAN.

n Ensure network connectivity exists between the RPA cluster and the XtremIOcluster.

n Obtain the XtremIO Management Server (XMS) IP address in IPv4 or IPv6format.

n Obtain the product serial number of the XtremIO cluster.

Procedure

1. Select RPA Clusters, and select the tab of the relevant RPA cluster.

2. In the left pane, click Storage.


Register storage in RecoverPoint 55

In the right pane, the Registered Storage table is displayed. The RegisteredStorage table contains the list of all of the XtremIO arrays and Data Domainsystems that are currently registered at the selected RPA cluster.

3. In the right pane, in the Registered Storage tab, click Add. The RegisterStorage dialog box is displayed.

4. In the Register Storage dialog box:

l Register an array seen by this RPA cluster

Note

This is the preferred method of storage registration in ProtectPoint.

To register any Data Domain system or XtremIO array that has already beenmasked to the RPA cluster:

a. Select an array from the list

b. Define the storage login credentials:

n Define Data Domain login credentials

n Define XtremIO login credentials

l Register any storage

To register any Data Domain system or XtremIO array, regardless of whetheror not it is masked to the RPA cluster:



a. Select the storage type from the drop-down.

b. Define the storage login credentials:

n Define Data Domain login credentials

n Define XtremIO login credentials

Define storage login credentials in RecoverPointDefines the login credentials for your Data Domain systems and XtremIO arrays inRecoverPoint, and whether to transfer data using FC or IP.

l For Data Domain systems:

n Enter the Data Domain IP address.

n Enter the username and password for the block services for ProtectPoint pooland DD Boost storage-unit in the Username and Password fields.

n Enter the DD Boost Storage Unit to use as the ProtectPoint catalog.

n By default, the Use FC for data transfer checkbox is selected. Uncheck to useIP only for data transfer.


Define storage login credentials in RecoverPoint 57

l For XtremIO arrays:

n Enter the IP address of the XtremIO Management Server (XMS). If theXtremIO Management Server manages more than one cluster, register eachcluster separately.

n Enter the Serial number (PSNT) of the XtremIO cluster.n Enter the XtremIO rp_user as the User.n Enter the rp_user password as the Password. This password can only be

changed using the XtremIO user interface.

Register block services for ProtectPoint pools in RecoverPointRegisters Data Domain block services for ProtectPoint pools at an RPA cluster.

Before you begin

l Pre-configure resource pools on the Data Domain in the same user Storage Unitand block services for ProtectPoint pool.



l Register storage in RecoverPoint on page 55

Note

After registering a block services for ProtectPoint pool, a manual change on the DataDomain will be required to unregister them and make them available for other clustersor uses.

Procedure

1. Select RPA Clusters.

2. Select the tab of the relevant RPA cluster.

3. In the left pane, select Storage.In the right pane, the Registered Storage tab is displayed. The RegisteredStorage tab contains the list of all of the storage systems that are currentlyregistered at the selected RPA cluster and their storage information.

4. In the Registered Storage tab, select a Data Domain.

5. Under the Registered Resource Pools table, click Add.The Register Available Resource Pools dialog box is displayed.


Register block services for ProtectPoint pools in RecoverPoint 59

6. In the Register Available Resource Pools dialog box:

a. Select the block services for ProtectPoint pools that you want to register.

b. Click OK.

Protect XtremIO volumes using RecoverPointCreates a new consistency group.

Before you begin

l Adding a Data Domain volume to a consistency group automatically sets its volumeaccess mode to Read-Only. Data Domain volumes in a consistency group becomewriteable when:

n image access is enabled.

n the copy or consistency group containing the Data Domain volume is disabled.

l Backup copy LUNs can be located on up to two Data Domain systems, per RPAcluster.

l A single Data Domain device may exist in more than one consistency group.

l Configure your Data Domains and XtremIOs.

l Create XtremIO initiator groups.

l Register your Data Domains and XtremIOs and your block services forProtectPoint pools.

l If one volume at a copy is on an XtremIO array, all other XtremIO volumes at thatcopy must be on the same array.

l For applications running on a host cluster:The RecoverPoint system supports both local and remote high-availability hostclusters.

n Place all volumes that are resources of the host cluster in a single consistencygroup. Simplify management by assigning the name of the host cluster as thename of the consistency group.

Note

The Journal volumes must not be resources of the host cluster.

n Assign each replication set the same name as its disk resource in the cluster. Ifall cluster nodes (hosts) at the side are down, you may not be able to createreplication volumes. To correct this problem, either bring up the nodes, or run arescan_san command (from the CLI), with volumes=FULL.

n Prior to enabling a consistency group, the system Dashboard may show anError on the source-side storage and display the message “Volume cannot beaccessed by any RPA.” The errors are removed when the consistency group isenabled.

Procedure

1. Select Protection > Protect Volumes.

2. In the Select Production Volumes screen:

a. Define the consistency group name, the production name, and the RPAcluster that will manage the production.



b. Select your production volumes in the volume list.

Note

If one volume at a copy is on an XtremIO array, all other XtremIO volumes atthat copy must be on the same array. Use the toolbar at the top-right cornerof the screen to help you identify the volumes.

Table 8 Toolbar options

Icon Description

To filter the volumes in the list by Size, Product, Vendor, Name, UID,LUN, or VPLEX Group.

To select the table columns that you want to display.

Note

You can also click and drag the column dividers to make the columnswider or thinner. In most cases, RecoverPoint will remember the columnwidth that you define, and display the columns accordingly in eachsubsequent launch of this wizard.

To export the data in the volume list to a *.CSV file.

To display context-sensitive help for this wizard screen.

c. Optionally, click Modify Policies to define the group policies and copypolicies now, or skip this step and define the policies later.

The policy settings are optional. The default values provide a practicalconfiguration. It is recommended to accept the default settings unless thereis a specific business need to set other policies.

d. Click Next Define the Production Journal.

3. In the Define Production Journal screen:


Protect XtremIO volumes using RecoverPoint 61

l Select Provisioned Journal Volumes:

In the volume list:

a. Select the volumes to add to the journal.For XtremIO arrays, the journal need not be more than 10 GB for non-distributed consistency groups and 40 GB for distributed consistencygroups, since the XtremIO journal contains only pointers to snapshotsand metadata.

For best performance, select volumes that are identical in size. Ifidentically sized volumes are not available, select volumes that are similarin size.

Use the toolbar icons at the top-right corner of the screen to help youidentify the required volumes in the volume list.

b. Click Next Add a Copy.

4. In the Add a Copy screen:

a. Define the Copy Name.

b. Select the same RPA Cluster as the one managing the XtremIO productionvolumes.



Note

Ensure one or more Data Domains have been masked to this RPA cluster.

The screen display changes to the following:

c. Select the Add Data Domain Copy checkbox.

d. Optionally, set the snap replication mode and the RPO to define the way inwhich RecoverPoint replicates the production data to the selected copy.

e. Optionally, to enable RecoverPoint to automatically delete the device groupand all of its block services for ProtectPoint pools and static images on theData Domain if this copy is deleted, click Modify Policies, and select theDelete journal upon removal checkbox in the Copy Policy tab.

If you want to change the protection settings using policy templates, in theLink tab, use the Select Template drop-down to select one of yourtemplates. Click Load to load the settings in the template and click OK toapply the settings.

f. Select the Data Domain system to use as the copy, and the block servicesfor the ProtectPoint pool in which to store the Data Domain static-images.

Note

The Data Domain copy journal is automatically provisioned in the sameresource pool as the copy. RecoverPoint automatically creates the backupblock services for ProtectPoint device groups and the devices to populatethe specified pool.

g. To continue configuring the group, click Next Display Group Summary.

5. In the Group Summary screen:


Protect XtremIO volumes using RecoverPoint 63

a. Use the following options until the consistency group diagram reflects yourrequirements:

Table 9 Group summary screen

Action Description

Edit Opens the Add a Copy screen of the copy whose Edit link youclicked, allowing you to edit the copy settings, and modify the copyvolume configuration, replication mode, or protection plan.

Delete Removes the copy whose Delete link you clicked, from theconsistency group.

Note

You cannot delete the production copy.

ReplicationSets

Displays detailed volume information on all replication set volumesthat have been defined for the consistency group. Select a row in thereplication sets table in the top section to display the associatedvolume information in the bottom section.

Click on the replication set name to open the Edit Replication Setdialog box, and rename the replication set.

Startreplication ...when I click'Finish'

When selected, starts transfer for the group as soon as the group iscreated. A first-time initialization (or fast first-time initialization)occurs when a consistency group is enabled for the first time.



Table 9 Group summary screen (continued)

Action Description

Add a Copy Opens the Add a Copy screen, allowing you to create another copy,define the new copy’s settings, and define the copy’s volumeconfiguration, replication mode, and protection plan.

FinishNOTICE

Before you start transfer to a Data Domain copy, unmount the copyvolumes at the relevant Data Domain host.

Creates the group, applies all of the specified settings, and starts afirst-time initialization process to synchronize the productionvolumes to the copy volumes.

b. Click Finish to create the group, and all of its copies.

The group is created and the Manage Protection screen is displayed.

After you finish

You can now manage protection or start recovery.

Additional storage configurationOptionally complete the following additional storage configuration tasks.

N_Port ID VirtualizationTo enable N_Port ID Virtualization (NPIV) on the Data Domain system, complete thefollowing steps.

Enabling N_Port ID VirtualizationN_Port ID Virtualization (NPIV) is a Fibre Channel feature in which multiple endpointscan share a single physical port. NPIV eases hardware requirements and providesendpoint failover/failback capabilities. NPIV is not configured by default, except in aHA configuration.

NPIV provides simplified multiple-system consolidation:

l NPIV is an ANSI T11 standard that allows a single HBA physical port to registerwith a Fibre Channel fabric using multiple WWPNs.

l The virtual and physical ports have the same port properties and behave the same.

l There may be m:1 relationships between the endpoints and the port, that is,multiple endpoints can share the same physical port.

Specifically, enabling NPIV enables the following features:

l Multiple endpoints are allowed per physical port, each using a virtual (NPIV) port.The base port is a placeholder for the physical port and is not associated with anendpoint.

l Endpoint failover/failback is automatically enabled when using NPIV.


Additional storage configuration 65

Note

After NPIV is enabled, the Secondary System Address must be specified at eachof the endpoints. If not, endpoint failover does not occur.

l Multiple Data Domain systems can be consolidated into a single Data Domainsystem, however, the number of HBAs remains the same on the single DataDomain system.

l The endpoint failover is triggered when FC-SSM detects when a port goes fromonline to offline. If the physical port is offline before scsitarget is enabled, and theport is still offline after scsitarget is enabled, an endpoint failover is not possible.The endpoint failover is not possible because FC-SSM does not generate a portoffline event. If the port comes back online and auto-failback is enabled, any failedover endpoints that use that port as a primary port fail-back to the primary port.

The Data Domain HA feature requires NPIV to move WWNs between the nodes of anHA pair during the failover process.

Note

Before enabling NPIV, the following conditions must be met:

l The Data Domain system must be running a supported version of Data Domain OS.

l All ports must be connected to 4Gb, 8Gb, and 16 Gb Fibre Channel HBA and SLIC.

l The Data Domain system ID must be valid, that is, it must not be 0.

In addition, port topologies and port names are reviewed and may prevent NPIV frombeing enabled:

l NPIV is allowed if the topology for all ports is loop-preferred.

l NPIV is allowed if the topology for some of the ports is loop-preferred. However,NPIV must be disabled for ports that are loop-only, or you must reconfigure thetopology to loop-preferred for proper functionality.

l NPIV is not allowed if none of the ports have a topology of loop-preferred.

l If port names are present in access groups, the port names are replaced with theirassociated endpoint names.

Procedure

1. Select Hardware > Fibre Channel.

2. Next to NPIV: Disabled, select Enable.

3. In the Enable NPIV dialog box, you are warned that all Fibre Channel ports mustbe disabled before NPIV can be enabled. If you are sure that you want tocontinue, select Yes.

Next stepsAfter the storage configuration is complete, the application or database administratormust install the agent to protect their environment. The next stages of theProtectPoint configuration and installation process are covered in:

l EMC ProtectPoint File System Agent Installation and Configuration Guide



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

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


Next steps 67

CHAPTER 4

Data Domain Collection Replication

This section includes the following topics:

l Data Domain collection replication overview...................................................... 70l Restoring directly from Data Domain for VMAX configurations..........................72l Restoring via VMAX FAST.X devices..................................................................75l Restoring directly from Data Domain for XtremIO with RecoverPoint

configurations.................................................................................................... 84

Data Domain Collection Replication 69

Data Domain collection replication overviewData Domain collection replication duplicates the entire data store on the source, andtransfers the data store to the destination. The replicated volume is read-only.

In the ProtectPoint 3.5 workflow, the database application agent restores a backupfrom a secondary Data Domain system of Data Domain collection replication. TheDDOS version must be 6.0 or later.

Before you can use database application agent to restore backups from the secondaryData Domain system of Data Domain collection replication, delete the collectionreplication pair. When the replication pair is deleted, the secondary Data Domainsystem becomes a stand-alone read/write system, and the file system is disabled.

The EMC Data Domain Operating System Administration Guide provides informationabout how to configure Data Domain collection replication and how to delete thecollection replication.

The following section describes registering the DD Boost storage units and vdiskpools. This procedure is a mandatory step before you perform any of the followingrestores:

l Restoring directly from Data Domain for VMAX configurations.

l Restoring via VMAX FAST.X devices.

l Restoring directly from Data Domain for XtremIO with RecoverPointconfigurations.

Registering the DD Boost storage units and vdisk pools used by the databaseapplication agent

You can register the DD Boost storage units and vdisk pools while the replication pairis established. You do not have to delete the replication pair for this process.

Before you begin

You must configure the Data Domain collection replication. Refer to the Data Domainstorage units configured on the primary Data Domain system, and decide on theMTrees to be registered on the secondary Data Domain system.

Procedure

1. To discover the MTrees on the secondary Data Domain system, run thefollowing command:

mtree list

Note

The MTrees are identical to those that were created on the primary DataDomain system.

An example of the output is as follows:

sysadmin@lfcp1158# mtree listName Pre-Comp (GiB) Status------------------------------------- -------------- ------/data/col1/appagent-backupsu 2.5 RW



/data/col1/backup 0.0 RW/data/col1/rpa246-injectsu 0.0 RW/data/col1/rpa246_lfcp1024 0.0 RW/data/col1/sym486_pool 179.4 RW/data/col1/symm486_vdisk_restore_pool 64.1 RW------------------------------------- -------------- ------ D : Deleted Q : Quota Defined RO : Read Only RW : Read Write RD : Replication Destination RLGE : Retention-Lock Governance Enabled RLGD : Retention-Lock Governance Disabled RLCE : Retention-Lock Compliance Enabled

2. To find the Data Domain users on the secondary Data Domain system, run thefollowing command:

user show list

3. To register the DD storage unit that is used by the database application agent,run the following command:

ddboost storage-unit modify <storage-unit> [user <user-name>]


sysadmin@lfcp1158# ddboost storage-unit modify appagent-backupsu user fsagent-user

Note

You must register the storage units that the database application agent uses tostore its index. In the ProtectPoint for XtremIO configuration, you do not needto register the storage unit that is used by the RecoverPoint appliance.

4. To register the vdisk pool that is used by the database application agent, runthe following command:

vdisk pool register <pool-name> user <user-name>


sysadmin@lfcp1158# vdisk pool register sym486_pool user fsagent-user-1

Note

You must only register the vdisk pool where the database application agentbackups are created. Do not register the restore device pool even if they arereplicated to the secondary Data Domain system.


Registering the DD Boost storage units and vdisk pools used by the database application agent 71

Deleting the collection replication pairIn case of a disaster that made the primary Data Domain system unavailable, youshould delete the collection replication pair before you can restore from the secondaryData Domain system.

The Data Domain Operating System Administration Guide provides information abouthow to delete the collection replication.

Restoring directly from Data Domain for VMAXconfigurations

To restore directly from a Data Domain system perform a point-in-time restore of thedatabase application agent backups from the secondary DD system by using the DDvdisk as the database application agent restore device. This restore option is directlyfrom Data Domain and does not go through VMAX.

The EMC Data Domain Boost for Enterprise Applications and EMC ProtectPoint DatabaseApplication Agent Installation and Administration Guide provides more information.

Preparing application agent restore devices on a secondary Data Domainsystem

The Data Domain collection replication replicates all the vdisk pools from the sourceData Domain system to the secondary Data Domain system. However, the vdiskdevices in the replicated vdisk pool have no associated WWN. Hence, the databaseapplication agent cannot use them as restore devices. To prepare the restore LUNs ona secondary Data Domain system, you must create a vdisk pool, and create deviceswithin this pool.

Before you begin

Ensure that the Data Domain collection replication pair is deleted. The EMC DataDomain Operating System Administration Guide provides information about how todelete the collection replication.

Procedure

1. To create the vdisk pool, run the following command:



sysadmin@lfcp1158# vdisk pool create symm486_vdisk_restore_pool_repl user fsagent-userVDISK pool "symm486_vdisk_restore_pool_repl" created and assigned to user "fsagent-user".

This pool will be used as the restore device pool of the database applicationagent.



2. To create a vdisk device group, run the following command:



sysadmin@lfcp1158# vdisk device-group create lfcp1011_restore_dg pool symm486_vdisk_restore_pool_replVDISK device-group "lfcp1011_restore_dg" created in pool "symm486_vdisk_restore_pool_repl"

This group will be used as the restore device group of the database applicationagent.

Note

You must name the restore device-group on the secondary Data Domain systemthe same as the restore device-group on the primary Data Domain system.

3. To create the vdisk devices, run the following command:

vdisk device create [count <count>] capacity <n> {MiB|GiB|TiB|PiB|sectors} pool <pool-name> device-group <device-group-name>

The devices will be used as the restore devices for the database applicationagent.


Before you beginPerform the following tasks:



Procedure



For example:





Configuring a Data Domain access group for the application recovery host 73








For example:






For example:




For example:









Performing a database application agent restore from a secondary DataDomain system

To perform a database application agent restore from a secondary Data Domainsystem, refer to the EMC Data Domain Boost for Enterprise Applications and EMCProtectPoint Database Application Agent Installation and Administration Guide.

Restoring via VMAX FAST.X devicesYou can perform a database application agent rollback and an object level restore ifyou are using VMAX FAST.X restore devices. This restore option requires you toconnect the VMAX to the Data Domain target.

Note

Rollback from the secondary Data Domain system is supported, as long as the VMAXconnected to the secondary Data Domain system, is the same VMAX where thesource LUNs are configured.

For more details regarding a database application agent rollback restore, refer to theEMC Data Domain Boost for Enterprise Applications and EMC ProtectPoint DatabaseApplication Agent Installation and Administration Guide.

Preparing database application agent restore devices on a secondary DataDomain system

To prepare the ProtectPoint restore LUNs, create a vdisk pool, and create devicesinside this pool.

Procedure

1. To create a vdisk pool, run the following command:

sysadmin@lfcp1158# vdisk pool create sym486_pool_repl user fsagent-user


Performing a database application agent restore from a secondary Data Domain system 75


VDISK pool "sym486_pool_repl" created and assigned to user "fsagent-user".


sysadmin@lfcp1158# vdisk device-group create sym486_restore_dg pool sym486_pool_repl


VDISK device-group "sym486_restore_dg" created in pool "sym486_pool_repl"


sysadmin@lfcp1158# vdisk device create count 5 heads 15 cylinders 7000 sectors-per-track 256 pool sym486_pool_repl device-group sym486_restore_dg

4. To check the device status, run the following command:

sysadmin@lfcp1158# vdisk device show list pool sym486_pool_repl

Establishing a fibre channel connection between Data Domain Replicator and VMAX

Before you beginEnsure that you have completed the zoning between the secondary Data DomainReplicator (DDR) and the VMAX.

Procedure

1. To identify the initiators, run the following command:

sysadmin@lfcp1158# scsitarget initiator show list


Initiator System Address Group Service

--------------- ----------------------- -------- -------

initiator-1 50:00:09:73:50:07:98:1a n/a n/a

initiator-2 50:00:09:73:50:07:98:06 n/a n/a

initiator-3 50:00:09:73:50:07:98:5a n/a n/a

initiator-4 50:00:09:73:50:07:98:46 n/a n/a

lfcp1011_vmhba1 21:00:00:0e:1e:c2:18:d4 lfcp1011 VDisk

--------------- ----------------------- -------- -------



2. To rename the initiator to proper names, run the following command:

sysadmin@lfcp1158# scsitarget initiator rename initiator-1 vmax_486_dir1_26_dx



3. To create a scsitarget group, run the following command:

sysadmin@lfcp1158# scsitarget group create symm_group service vdisk


Group 'symm_group' successfully created.

4. To add a VMAX initiator to the scsitarget group, run the following command:

sysadmin@lfcp1158# scsitarget group add symm_group initiator vmax_486_dir1_26_dx


Initiator 'vmax_486_dir1_26_dx' successfully added to group.

5. To add Vdisk devices to the scritarget group, run the following command:

sysadmin@lfcp1158# vdisk group add symm_group pool sym486_pool_repl device-group sym486_restore_dg


VDISK Devices in pool "sym486_pool_repl" and device-group "sym486_restore_dg" added to group "symm_group"

Encapsulating secondary Data Domain system vdisk devices on VMAXTo restore from secondary Data Domain system and use VMAX FAST.X LUNs as appagent's restore devices, you should encapsulate the vdisk devices created in theprevious section on VMAX.

Before you begin

Ensure that the following requirements are met:

l The app agent restore devices are configured on the secondary Data Domainsystem.


Encapsulating secondary Data Domain system vdisk devices on VMAX 77

l The secondary Data Domain system and the VMAX can see each other over FSSAN.

l You have obtained the geometry of the source devices created on the VMAXarray.

Procedure

1. Switch to the VMAX environment.

2. To review the list of DX ports, which are connected to the Data Domain systemfrom the VMAX array, run the following command:

symsan list -sid <SymmetrixID> -sanports -DX all -port all

For example:

symsan list -sid 0129 -sanports -DX all -port all

3. Copy the WWN for one of the ports and use the WWN to determine whichLUNs are visible through this WWN.

The LUN is exposed but is not ready for use yet. The LUN must be encapsulatedon to the VMAX array with FAST.X.


symsan -sid <SymmetrixID> -dir All -p All list -sanluns -wwn <wwn>

For example:

symsan -sid 0129 -dir All -p All list -sanluns -wwn 2800002182DDB5D

4. To create a VMAX storage group, run the following command:

symsg create <SgName>

For example:

symsg create storage-group-5

Note

If an existing device group is appropriate for the ProtectPoint implementation,you can use it instead of creating a device group. To see all the device groupson the VMAX array, run the symsg list -sid <SymmetrixID> command.

5. Encapsulate the Data Domain disk on the VMAX array. There are two ways toencapsulate disks:



l To encapsulate disks individually, run the following command:

symconfigure -sid <SymmetrixID> -cmd "add external_disk, wwn=<wwn>, encapsulate_data=yes;" commit -v -nop

For example:

symconfigure -sid 0129 -cmd "add external_disk, wwn=6002189000002DDB5D0525EEE8A00011, encapsulate_data=yes;" commit -v -nop

It takes approximately seven minutes to encapsulate each device.

l To encapsulate a group of devices, complete the following steps:

a. In a BASH shell on the application recovery host, to capture all the blockservices for ProtectPoint devices to encapsulate in a text file, run thefollowing command:

ssh sysadmin@ {<DD-hostname>} vdisk device show list pool {<pool-name>} device-group {<device-group-name>} | awk '/^vdisk-dev/{print "add external_disk wwn=" $5 ", encapsulate_data=YES;"}' | sed 's/://g' > devs.txt

Note

The command fails if there are fewer than two devices that are specifiedin the text file.

b. On the application recovery host, to encapsulate the block services forProtectPoint devices that are listed in the text file, run the followingcommand:

symconfigure commit -f devs.txt


…Establishing a configuration change session....Established.Processing symmetrix 000196700129Performing Access checks.......................Allowed.Checking Device Reservations...................Allowed.Initiating COMMIT of configuration changes.....Queued.COMMIT requesting required resources...........Obtained.Step 008 of 064 steps..........................Executing.…Step 091 of 214 steps..........................Executing.…Step 210 of 219 steps..........................Executing.Local: COMMIT..................................Done.New symdev: 0004C [DATA device]New symdev: 000BA [TDEV]Terminating the configuration change session........Done.The configuration change session has successfully completed.


Encapsulating secondary Data Domain system vdisk devices on VMAX 79

Note

The VMAX array returns a contiguous range of new device nameswhenever possible. However, the range of device names is not alwayscontiguous.

The system performs the following operations:

a. Takes the device with the specified WWN. The device is now visible to theVMAX array.

b. Encapsulates the device.

c. Puts the device into the external device group.

d. Assigns a name to the device.

6. To add the encapsulated Data Domain target devices to the storage group, runthe following command:

symsg -g <SgName> add dev <device-number> -tgt

For example:

symsg -g storage-group-5 add dev 0002A -tgt

7. As the environment uses FAST.X restore operations, create a VMAX storagegroup for the restore LUNs, and then add the encapsulated devices to it.

The default storage group name is NsrSnapSG. To use a non-default name forthe storage group, that name must be specified in the ProtectPoint file systemagent or application agent configuration files.

a. To create a storage group, run the following command:

symsg -sid <SymmetrixID> create ProtectPointRestoreGroup

For example:

symsg -sid 0129 create ProtectPointRestoreGroup

Note

The storage group name is case-insensitive.

b. To add the restore devices to the storage group, run the following command:

symsg -sid <SymmetrixID> -sg ProtectPointRestoreGroup add dev <device-number>



Provisioning FAST.X restore LUNs to the application recovery hostThis procedure is for provisioning FAST.X LUNs on the VMAX array for newinstallations.

Before you begin

Ensure that FC zoning is complete.

To determine the devices in use, use Solutions Enabler.

To provision the VMAX FAST.X LUNs to the application recovery host, complete thefollowing tasks on the VMAX array:

l Create a storage group.

l Add the devices to the storage group.

l Create a port group.

l Add the front-end ports to the port group where the server is zoned.

l Create an initiator group.

l Add the initiator WWNs of the application recovery host to the initiator group.

l Create a masking view.

l Discover newly provisioned LUNs on the application recovery host.

Procedure

1. From the application recovery host, to configure the VMAX FAST.X devices,use Solutions Enabler.

2. To view the existing VMAX devices, run the following commands:

a. To list the VMAX devices, complete the following steps:


b. To view a specific FAST.X device, run the following command:


3. To create a storage group, run the following command:

symaccess -sid <SymmetrixID> create -name <GroupName> -type storage [devs <SymDevStart>:<SymDevEnd> | <SymDevName>[, <SymDevName>[, <SymDevName>. . .]] | <-g <DgName> [-std] [-bcv] [-vdev] [-tgt]> | <sg <SgName> [, <SgName1>, <SgName2> . . . <SgNamen>]> <-file <DeviceFileName> [src] [tgt]> [-reserve_id <ResvID> [, <ResvID> [, <ResvID>. . .] ] ] ]

For example:

symaccess -sid 0129 create -name group1 -type storage


Provisioning FAST.X restore LUNs to the application recovery host 81

Note

This storage group is different from the NsrSnapSG mentioned in theEncapsulating secondary Data Domain system vdisk devices on VMAX section.

4. To add FAST.X devices to the storage group, run the following command:

symsg -sg <SgName> -sid <SymmetrixID> [-i <Interval>] [-c <Count>] add dev <SymDevNumber>

For example:

symsg -sg group1 -sid 0129 add dev 0001A

5. To create a port group, run the following command:

symaccess -sid <SymmetrixID> create -name <GroupName> -type port [-dirport <Dir>:<Port> [, <Dir>:<Port>..]]

For example:

symaccess -sid 0129 create -name group1 -type port

6. To add the front-end ports to the port group, run the following command:

symaccess -sid <SymmetrixID> -name <GroupName> -type <port> [-dirport <Dir>:<Port>[, <Dir>:<Port>[, <Dir>;:<Port>. . .]][-ckd] add [-celerra] [-rp]

For example:

symaccess -sid 0129 -name group1 -type port add -dirport 1e:8

The front-end ports are the ones that connect the application recovery host tothe VMAX array.

7. To create an initiator group, run the following command:

symaccess -sid <SymmetrixID> create -name <GroupName> -type initiator [-wwn <wwn> | -iscsi <iscsi> | -file <InitiatorFilename> | -ig <InitiatorGroupName>] [-consistent_lun]

For example:

symaccess -sid 0129 create -name group1 -type initiator -consistent_lun



Note

The -consistent_lun option forces all devices that are masked to theinitiator group to connect to the same LUN with all available ports.

8. To add the initiator WWNs to the initiator group, run the following command:

symaccess -sid <SymmetrixID> -name <GroupName> -type initiator -wwn <wwn> | -iscsi <iscsi> | -ig <InitiatorGroupName> | -f <InitiatorFilename> add

For example:

symaccess -sid 0129 -name group1 -type initiator -wwn 6002188000002ddb5d0525eee8a00011 add

Initiators can be added to an existing initiator group by specifying the initiatortype (-wwn or -iscsi), the initiator group name, or by using an input file.

9. To create a masking view, run the following command:

symaccess create view -sid <SymmetrixID> -name <ViewName> -sg <StorageGroupName> -pg <PortGroupName> -ig <InitiatorGroupName> [-reserve_id <ResvID> [, <ResvID>[, <ResvID>...] ] ] [-lun addr] [-ckd] [-celerra] [-rp]

For example:

symaccess create view -sid 0129 -name view1 -sg group2 -pg portgroup1 -ig initator_group1

After you put the storage group, the port group, and the initiator group in themasking view, the initiators in the initiator group can see the devices via theport in the port group.

10. To update the local symapi database on the application recovery host, run thefollowing command:

symcfg discover

Performing an application agent object level restore from a secondary DataDomain system

To perform an application agent object level restore from a secondary Data Domainsystem, refer to the EMC Data Domain Boost for Enterprise Applications and EMCProtectPoint Database Application Agent Installation and Administration Guide.


Performing an application agent object level restore from a secondary Data Domain system 83

Performing an application agent rollback restore from a secondary DataDomain system

To perform an application agent rollback restore from a secondary Data Domainsystem, refer to the EMC Data Domain Boost for Enterprise Applications and EMCProtectPoint Database Application Agent Installation and Administration Guide.

Restoring directly from Data Domain for XtremIO withRecoverPoint configurations

This is an object level restore. This restore works directly from Data Domain.

Preparing database application agent restore devices on a secondary DataDomain system

To prepare the ProtectPoint restore LUNs, create a vdisk pool, and create devicesinside this pool.

Procedure

1. To create a vdisk pool, run the following command:

sysadmin@lfcp1158# vdisk pool create sym486_pool_repl user fsagent-user


VDISK pool "sym486_pool_repl" created and assigned to user "fsagent-user".


sysadmin@lfcp1158# vdisk device-group create sym486_restore_dg pool sym486_pool_repl


VDISK device-group "sym486_restore_dg" created in pool "sym486_pool_repl"


sysadmin@lfcp1158# vdisk device create count 5 heads 15 cylinders 7000 sectors-per-track 256 pool sym486_pool_repl device-group sym486_restore_dg



4. To check the device status, run the following command:

sysadmin@lfcp1158# vdisk device show list pool sym486_pool_repl


Before you begin




Procedure



For example:










Configuring a Data Domain access group for the application recovery host 85



For example:






For example:




For example:









Performing an application agent restore from a secondary Data Domainsystem

To perform an application agent restore from a secondary Data Domain system, referto the EMC Data Domain Boost for Enterprise Applications and EMC ProtectPointDatabase Application Agent Installation and Administration Guide.

Database application agent rollback restore via a RecoverPoint applianceRestore from the secondary Data Domain system is not support by the databaseapplication agent.


Performing an application agent restore from a secondary Data Domain system 87

Copyright © 2015 EMC Corporation. All rights reserved. Published in USA. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. 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).

https://support.emc.com/

emc protectpoint 3.5 primary and protection storage ... · pdf fileprimary and protection...

Documents