EMC ProtectPoint. Primary and Protection Storage Configuration Guide. Version REV 02

Transcription

1 EMC ProtectPoint Version 3.5 Primary and Protection Storage Configuration Guide REV 02

2 Copyright 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 Corporation Hopkinton, Massachusetts In North America EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

3 CONTENTS Preface 5 Chapter 1 ProtectPoint Storage Configuration Overview 9 ProtectPoint family overview...10 ProtectPoint file system agent...10 ProtectPoint database application agent ProtectPoint Microsoft application agent Application storage configuration overview...12 Data Domain sizing considerations Discovering application storage...13 Host considerations Chapter 2 VMAX Application Storage Configuration 15 ProtectPoint environment...16 Additional information ProtectPoint for VMAX prerequisites...16 ProtectPoint file system agent prerequisites Database application agent and Microsoft application agent prerequisites VMAX prerequisites...17 Data Domain prerequisites...18 DD Boost prerequisites...18 Data Domain block services prerequisites...18 Discovering device geometry Provision VMAX storage and encapsulate the Data Domain devices on the VMAX array...20 ProtectPoint performance considerations for VMAX Gen0 backups Provisioning FAST.X restore LUNs to the application recovery host Encapsulating Data Domain devices on the VMAX array...23 Additional storage configuration...34 N_Port ID Virtualization...35 Next steps...36 Chapter 3 XtremIO Application Storage Configuration 37 ProtectPoint for XtremIO with RecoverPoint environment ProtectPoint for XtremIO with RecoverPoint prerequisites...38 ProtectPoint file system agent prerequisites...38 Database application agent and Microsoft application agent prerequisites...38 RecoverPoint prerequisites XtremIO prerequisites...39 Data Domain prerequisites...40 DD Boost prerequisites Data Domain block services prerequisites...40 Configure XtremIO storage and connect the Data Domain system, RecoverPoint cluster, and XtremIO cluster EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide 3

4 CONTENTS Creating an XtremIO initiator group...42 Configuring XtremIO storage for a single volume...43 Configuring XtremIO storage for multiple volumes Configuring Data Domain services and users Enabling encryption over a WAN connection Configuring the DD Boost over Fibre Channel service Configuring DD Boost storage units...49 Configuring block services for ProtectPoint objects...50 Configuring a Data Domain access group for the application recovery host Logging into RecoverPoint Install a license in RecoverPoint Register storage in RecoverPoint Define storage login credentials in RecoverPoint...57 Register block services for ProtectPoint pools in RecoverPoint Protect XtremIO volumes using RecoverPoint Additional storage configuration...65 N_Port ID Virtualization...65 Next steps...66 Chapter 4 Data Domain Collection Replication 69 Data Domain collection replication overview...70 Registering the DD Boost storage units and vdisk pools used by the database application agent Deleting the collection replication pair Restoring directly from Data Domain for VMAX configurations Preparing application agent restore devices on a secondary Data Domain system Configuring a Data Domain access group for the application recovery host...73 Performing a database application agent restore from a secondary Data Domain system Restoring via VMAX FAST.X devices...75 Preparing database application agent restore devices on a secondary Data Domain system Encapsulating secondary Data Domain system vdisk devices on VMAX Provisioning FAST.X restore LUNs to the application recovery host...81 Performing an application agent object level restore from a secondary Data Domain system...83 Performing an application agent rollback restore from a secondary Data Domain system Restoring directly from Data Domain for XtremIO with RecoverPoint configurations Preparing database application agent restore devices on a secondary Data Domain system...84 Configuring a Data Domain access group for the application recovery host Performing an application agent restore from a secondary Data Domain system Database application agent rollback restore via a RecoverPoint appliance EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

5 Preface As part of an effort to improve product lines, periodic revisions of software and hardware are released. Therefore, all versions of the software or hardware currently in use might not support some functions that are described in this document. The product 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 this document, contact a technical support professional. This document was accurate at publication time. To ensure that you are using the latest version of this document, go to the Support website at support.emc.com. Purpose This document includes instructions to provision the primary and protection storage for a ProtectPoint deployment. Audience This document is intended for administrators who need to configure the primary and protection storage for the ProtectPoint environment. This document is relevant for both the ProtectPoint file system agent and ProtectPoint application agents. Revision History The 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: CompGuideApp/getProtectPointCompGuidePage.do 01 December 21, 2016 Initial release of the EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide. The ProtectPoint file system agent documentation set includes the following publications: EMC ProtectPoint Solutions Guide EMC ProtectPoint Primary and Protection Storage Configuration Guide EMC ProtectPoint File System Agent Installation and Administration Guide EMC ProtectPoint File System Agent Release s The following Data Domain Boost for Enterprise Applications and ProtectPoint documents provide additional information: EMC Data Domain Boost for Enterprise Applications and EMC ProtectPoint Database Application Agent Installation and Administration Guide Preface 5

6 Preface EMC Data Domain Boost for Enterprise Applications and ProtectPoint Database Application Agent Release s EMC Data Domain Boost for Enterprise Applications and EMC ProtectPoint Microsoft Application Agent Installation and Administration Guide EMC Data Domain Boost for Enterprise Applications and EMC ProtectPoint Microsoft Application Agent Release s For compatibility information, including specific backup software and hardware configurations that ProtectPoint supports, go to the following website: getprotectpointcompguidepage.do The following Data Domain system documents provide additional information: EMC Data Domain Installation and Setup Guide for the particular Data Domain system EMC Data Domain Operating System Release s EMC Data Domain Operating System Initial Configuration Guide EMC Data Domain Operating System Command Quick Reference Guide EMC Data Domain Operating System Command Reference Guide EMC Data Domain Operating System Administration Guide EMC Data Domain Operating System MIB Quick Reference Guide EMC Data Domain Operating System Offline Diagnostics Suite User's Guide Hardware overview guide for the system Field replacement guides for the system components EMC Data Domain System Controller Upgrade Guide EMC Data Domain Expansion Shelf Hardware Guide for shelf model ES20, ES30, or DS60 EMC Data Domain Boost for OpenStorage Administration Guide EMC Data Domain Boost for OpenStorage Release s EMC Data Domain Boost for Oracle Recovery Manager Administration Guide EMC Data Domain Boost for Oracle Recovery Manager Release s EMC Data Domain Boost SDK Programmer's Guide Statement of Volatility for the system If you have the optional RSA Data Protection Manager (DPM), see the RSA Data Protection Manager Server Administrator's Guide, available with the RSA DPM product. The following VMAX system documents provide additional information: EMC Solutions Enabler TimeFinder Family CLI User Guide EMC Solutions Enabler Array Management CLI User Guide Special notice conventions that are used in this document The following conventions are used for special notices: NOTICE Identifies content that warns of potential business or data loss. 6 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

7 Preface Contains information that is incidental, but not essential, to the topic. Typographical conventions The following type style conventions are used in this document: Table 2 Style conventions Bold Italic Monospace 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 with title, table label, and window. Used for full titles of publications that are referenced in text. Used for: System code System output, such as an error message or script Pathnames, file names, file name extensions, prompts, and syntax Commands and options Monospace italic Monospace bold Used for variables. Used for user input. [ ] Square brackets enclose optional values. Vertical line indicates alternate selections. The vertical line means or for 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 the example. You can use the following resources to find more information about this product, obtain support, and provide feedback. Where to find product documentation Where to get support The Support website at provides access to licensing information, product documentation, advisories, and downloads, as well as how-to and troubleshooting information. This information may enable you to resolve a product issue before you contact Support. To access a product specific Support page: 1. Go to 2. In the Find a Product by Name box, type a product name, and then select the product from the list that appears. 3. Click the following button: 7

8 Preface 4. (Optional) To add the product to My Saved Products, in the product specific page, click Add to My Saved Products. Knowledgebase The Knowledgebase contains applicable solutions that you can search for by solution number, for example, , or by keyword. To search the Knowledgebase: 1. Go to 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 solution number or keywords. 4. (Optional) To limit the search to specific products, type a product name in the Scope 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 chat To participate in a live interactive chat with a support agent: 1. Go to 2. Click Chat with a Support Agent. Service requests To obtain in-depth help from Support, submit a service request. To submit a service request: 1. Go to 2. Click Create a Service Request. To create a service request, you must have a valid support agreement. Contact a sales representative for details about obtaining a valid support agreement or with questions about an account. To review an open service request: 1. Go to 2. Click Manage service requests. Online communities Go to the Community Network at for peer contacts, conversations, and content on product support and solutions. Interactively engage online with customers, partners, and certified professionals for all products. How to provide feedback Feedback helps to improve the accuracy, organization, and overall quality of publications. You can send feedback to DPAD.Doc.Feedback@emc.com. 8 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

9 CHAPTER 1 ProtectPoint Storage Configuration Overview This section includes the following topics: ProtectPoint family overview Application storage configuration overview Data Domain sizing considerations...12 Discovering application storage Host considerations ProtectPoint Storage Configuration Overview 9

10 ProtectPoint Storage Configuration Overview ProtectPoint family overview ProtectPoint file system agent The ProtectPoint family consists of the ProtectPoint file system agent, the ProtectPoint database application agent, and the ProtectPoint Microsoft application agent. The ProtectPoint file system agent includes the following features: Provides a CLI that you can use to trigger the primary storage to Data Domain workflow for backup and restore operations. Provides commands for lifecycle management of the backups. Triggers backup and restore operations on the primary storage system and Data Domain system through the use of primary storage system features and Data Domain block services for ProtectPoint management libraries, respectively. Operates on the device level. ProtectPoint works with primary storage LUNs and Data Domain block services for ProtectPoint devices, not with file system objects. Use the ProtectPoint file system agent to perform the following operations: Create a snapshot of the production application LUNs on the primary storage system. Trigger the movement of data that is created from the backups on the primary storage system to the Data Domain devices. Create a static image for each LUN in the dataset on the Data Domain system. Securely manage the credentials for the Data Domain systems and RecoverPoint cluster. Scan the Data Domain system for backups that other ProtectPoint and Enterprise Copy Data Management applications create in addition to backups created by the ProtectPoint file system agent. Roll back a specified backup to its source devices. Restore a backup to the restore devices. Manage the ProtectPoint backup and scan catalog. Manage the lifecycles of the data backups by listing and optionally deleting existing backups. Display the ProtectPoint version number. Validate the content and format of the configuration files. Configuration file The ProtectPoint file system agent configuration file specifies information about: The ProtectPoint file system agent protected environment, including the Data Domain name and username. Backup and restore source devices or groups. Restore devices. Performing restores and rollbacks. The ProtectPoint file system agent provides the following template configuration files: ProtectPoint for VMAX environments 10 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

11 ProtectPoint Storage Configuration Overview 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 a copy of the configuration template file, and specify the environment information in the copy. You can have any number of configuration files. You must also update the lockbox with the Data Domain and optionally the RecoverPoint passwords. ProtectPoint database application agent The ProtectPoint database application agent includes the following features: Provides the ability to perform backups and restores of DB2, Oracle, or SAP with Oracle database data that resides on the primary storage system to protection storage on a Data Domain system. Provides an integrated experience by using the database-specific backup and recovery tools, such as DB2 CLI, Oracle RMAN, or SAP BR*Tools. Provides application-consistent ProtectPoint backups without manual intervention by the application administrator. Operates on the database level, so the database application agent software automatically discovers the primary storage devices where database objects reside. Restores automatically from a replicated backup on a secondary Data Domain system when the primary Data Domain system is unavailable. Supports listing and lifecycle management of backups using the native database backup functionality, and deletion of backups that are no longer required. Discovers the corresponding backup devices based on the backup link established with the VMAX primary storage. Provides the ability to perform backups and restores over an Ethernet (IP) or Fibre Channel (FC) connection. 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 network types (LAN, WAN, or MAN) and can successfully operate where packet loss is strictly 0% and latency is less than 20 ms. ProtectPoint Microsoft application agent The ProtectPoint Microsoft application agent includes the following features: Provides the ability to perform backups and restores of Microsoft Exchange and Microsoft SQL database data that resides on the primary storage system to protection storage on a Data Domain system. Provides an integrated experience by using the database-specific backup and recovery tools. Provide application-consistent ProtectPoint backups without manual intervention by the application administrator. Operates on the database level, so the database application agent software automatically discovers the primary storage devices where database objects reside. ProtectPoint database application agent 11

12 ProtectPoint Storage Configuration Overview Restores automatically from a replicated backup on a secondary Data Domain system when the primary Data Domain system is unavailable. Supports listing and lifecycle management of backups using the native database backup functionality, and deletion of backups that are no longer required. Discovers the corresponding backup devices based on the backup link established with the VMAX primary storage. Provides the ability to perform backups and restores over an Ethernet (IP) or Fibre Channel (FC) connection. 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 network types (LAN, WAN, or MAN) and can successfully operate where packet loss is strictly 0% and latency is less than 20 ms. Application storage configuration overview Application storage is the primary storage for application data. This storage often consists of a number of separate LUNs that have file systems. Mount points or drive letters make the storage available to the application host. These LUNs are the source for any ProtectPoint backup. The following sections provide information about configuring or discovering LUNs, and using that information to create the equivalent snapshot target and recovery LUNs. If it is not necessary to provision new application storage. Discovering application storage on page 13 includes information about discovering the existing application storage. When configuring application storage, complete the following high-level processes: Provision primary storage LUNs to the application recovery host. For VMAX configurations, connect Data Domain devices to the primary storage system. For XtremIO with RecoverPoint configurations, register the Data Domain to RecoverPoint. Provision the LUNs on the primary storage system to the application recovery host first. Then connect the Data Domain devices to the primary storage system. The second procedure, connecting the Data Domain devices to the primary storage system, requires storage management visibility into both system environments. You complete some tasks in the primary storage environment and other tasks in the Data Domain environment. Therefore, you must have one window open to the primary storage environment and one window open to the Data Domain environment. You switch between environments as you connect the Data Domain devices to the primary storage system. Data Domain sizing considerations To plan for provisioning the primary storage for ProtectPoint, use the best practices and limits that are defined in the documentation for the primary storage system. The following guidelines apply to provisioning an appropriate amount of storage on the primary Data Domain system, and if applicable, providing an appropriate amount of storage at the secondary site: 12 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

13 ProtectPoint Storage Configuration Overview To accommodate all the application recovery hosts in the deployment, verify that sufficient capacity is available on the primary Data Domain system. Each primary storage LUN requires block services devices of equal or greater size on the primary Data Domain system. If VMAX devices are being protected, a total of two block services devices are needed, one for backups and one for restores. If XtremIO devices are being protected, only one block services device is needed, for restores only. If applicable, verify that the primary storage system and Data Domain system at the secondary site have available storage capacity that is greater than or equal to the storage capacity at the production site. To estimate the required logical capacity on the Data Domain system, use the following values: Number: The number of LUNs to back up. Size: The size of each LUN to back up. Copies: The number of backups to keep. To account for copies of the data on both the backup and restore devices, add two to 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, keeping five backups. Table 3 Sizing calculation example Element Value Number 10 Size 10 GB Copies Required capacity 700 GB Logical capacity is calculated before compression and deduplication. Compression and deduplication reduce the actual amount of capacity consumed. Capacity monitoring is available at the following levels: Logical capacity is reported at the system, MTree (block services for ProtectPoint pool), and file (static-image) levels. Actual capacity is reported at the system level. Discovering application storage Configure ProtectPoint after storage provisioning is complete by discovering existing application storage, and then using the storage to determine the Data Domain storage requirements. The storage administrator can help identify all the necessary storage configuration information. The information that is required includes, but is not limited to, the number of devices allocated to the application, the geometry of the devices created, and awareness of the masking views, ports used, and SAN zoning. The process to provision the Data Discovering application storage 13

14 ProtectPoint Storage Configuration Overview Host considerations Domain storage and connect the storage to the primary storage system is identical to provisioning new storage. The following host considerations can impact the ProtectPoint implementation: For FC multipathing, verify that enough FC ports are available on the primary storage system, the Data Domain system, the host, and the FC switch. The number of paths that are required depends on the I/O load and the environment performance requirements. For IP network redundancy, verify that enough Ethernet ports and interfaces are available to create the redundant configuration. 14 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

15 CHAPTER 2 VMAX Application Storage Configuration This chapter includes the following topics: ProtectPoint environment ProtectPoint for VMAX prerequisites Discovering device geometry...19 Provision VMAX storage and encapsulate the Data Domain devices on the VMAX array Additional storage configuration...34 Next steps...36 VMAX Application Storage Configuration 15

16 VMAX Application Storage Configuration ProtectPoint environment The ProtectPoint environment consists of the following components: Data Domain: A Data Domain system with a supported Data Domain operating system. Data Domain block services for ProtectPoint license. (Optional) Data Domain replication license. VMAX: A VMAX array. A VMAX license is required for ProtectPoint. Solutions Enabler in local mode on the application recovery host. Application: Application recovery host. ProtectPoint agent on the application recovery host. To view the supported versions of components, go to the following website: getprotectpointcompguidepage.do Additional information VMAX devices protected by SRDF/M cannot be used by ProtectPoint. The EMC ProtectPoint Solutions Guide provides more detailed information about the components that make up the ProtectPoint solution. ProtectPoint for VMAX prerequisites The following are prerequisites for all ProtectPoint for VMAX operations. ProtectPoint file system agent prerequisites The following are ProtectPoint file system agent prerequisites for VMAX operations: 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 provides information on how to configure a user account without root access. DX directors on the VMAX system must be available to encapsulate the Data Domain protection storage. The ProtectPoint file system agent must be installed on the application recovery host. Database application agent and Microsoft application agent prerequisites The database and Microsoft application agent prerequisites for ProtectPoint operations are as follows: 16 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

17 VMAX Application Storage Configuration VMAX prerequisites A valid license for the ProtectPoint environment. The application agent must be installed on the production and recovery host. User accounts for block services for ProtectPoint, and DD Boost must be created on the Data Domain system. (Optional) Create a user account on the RecoverPoint appliance. The following are VMAX prerequisites for all ProtectPoint for VMAX operations: A VMAX array. Solutions Enabler in local mode on the application recovery host. The required VMAX source capacity licenses. In multiple VMAX environments, the recovery devices must be configured in the same Data Domain vdisk pool. SAN zoning between the VMAX FA and DX ports and the application recovery hosts: Ensure that one DX emulation exists on each director within the same engine. Each DX emulation requires two ports exclusively for zoning to the Data Domain system. For FC zoning with a single SAN switch, create zones between four VMAX DX ports and two Data Domain ports. For FC zoning with two SAN switches, create zones between four VMAX DX ports and four Data Domain ports. The following figure displays an example of a single SAN switch zoning configuration. Figure 1 SAN zoning example VMAX prerequisites 17

18 VMAX Application Storage Configuration Data Domain prerequisites DD Boost prerequisites The following are Data Domain prerequisites for all ProtectPoint for VMAX operations: A Data Domain system that ProtectPoint supports. IP connectivity to the Data Domain systems on TCP port Block services for ProtectPoint must be enabled on the Data Domain system. Enable the DD Boost service, and then create a storage unit. Data Domain block services prerequisites Data Domain storage layout The prerequisites for Data Domain block services operations are as follows: (Optional) Create the Data Domain file system (DDFS). Configure a username and password for ownership of the Data Domain block services for ProtectPoint devices. It is recommended that you create this user with the none role. If required, other roles can be configured. Apply a Data Domain block services for ProtectPoint license. The following figure displays the storage layout of the DDFS. Figure 2 DDFS storage layout 1. /data 2. /data/col1 3. /data/col1/backup 4. /data/col1/mtree2 5. /data/col1/mtree3 The following table describes each element of the DDFS storage layout. 18 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

19 VMAX Application Storage Configuration Table 4 DDFS storage elements DDFS directory /data /data/col1 /data/col1/backup /data/col1/mtree<x> Description Top-level directory of the Data Domain storage file system. This directory cannot be changed. Represents a collection of data, and enables the expansion of the file system by creating additional collections, col2, col3, col4, and so on. Contains backups of the data and directory structure of the collection. This MTree cannot be deleted or renamed. Subdirectories can be created to organize and separate the data. Represents the lowest level of the Data Domain storage file system. Each MTree is an independently managed directory. Data Domain allows up to 100 MTrees to be created, but performance degradation occurs when more than 32 MTrees are active at one time. Data Domain block services for ProtectPoint Data Domain file system Data Domain block services for ProtectPoint allow you to create devices, device groups, 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 more information about the block services for ProtectPoint and the vdisk commands that control them. The Data Domain file system (DDFS) stores the block services for ProtectPoint objects. For example, a block services static-image can be treated as a file that resides within 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 for ProtectPoint can efficiently create static-images of LUNs. Discovering device geometry The DDFS automatically defragments backups that are created in a ProtectPoint environment to prevent performance degradation over time. The EMC Data Domain Operating System Administration Guide provides more information about the DDFS. You will need the geometry of any existing primary storage devices. For VMAX arrays, Encapsulating Data Domain devices on the VMAX array on page 23 provides instructions on identifying the VMAX device geometry and mapping it to the required geometry for Data Domain devices. Discovering device geometry 19

20 VMAX Application Storage Configuration Provision VMAX storage and encapsulate the Data Domain devices on the VMAX array Provision primary storage LUNs on the VMAX array, and encapsulate the Data Domain block services devices on the VMAX array. Create a separate Data Domain device-group for each application host that is part of the configuration. If multiple applications will run on a single host, create a separate device-group for each application. Place all restore devices intended for use with an application into a single device-group for that application. To make use of Data Domain Fastcopy for restore operations, place all the associated device-groups in the same pool. ProtectPoint performance considerations for VMAX Gen0 backups The full SnapVX copy that is associated with a ProtectPoint Gen0 backup, combined with the increased backend load related to SnapVX write handling can result in increased I/O response time. The QOS speed setting can be changed online, and has and immediate effect on copies in progress: SnapVX copy QOS defaults to maximum speed (0 from a range of 0-16) to achieve minimum copy duration. When response time is a concern, use a speed value of 4 to achieve a moderate reduction 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 volumes being backed up are under light or moderate write loads. Snapshot overhead is most significant 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 requires additional steps, which add overhead to the backend components. If this period must coincide with a busy time for the system, additional CPU resources may be required to support the increased load. Provisioning FAST.X restore LUNs to the application recovery host This procedure is for provisioning FAST.X LUNs on the VMAX array for new installations. 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 the following tasks on the VMAX array: Create a storage group. Add the devices to the storage group. Create a port group. 20 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

21 VMAX Application Storage Configuration Add the front-end ports to the port group where the server is zoned. Create an initiator group. Add the initiator WWNs of the application recovery host to the initiator group. Create a masking view. 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>...] ] ] ] symaccess -sid 0129 create -name group1 -type storage This storage group is different from the NsrSnapSG mentioned in the Encapsulating 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> symsg -sg group1 -sid 0129 add dev 0001A Provisioning FAST.X restore LUNs to the application recovery host 21

22 VMAX Application Storage Configuration 5. To create a port group, run the following command: symaccess -sid <SymmetrixID> create -name <GroupName> -type port [-dirport <Dir>:<Port> [, <Dir>:<Port>..]] 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] symaccess -sid name group1 -type port add -dirport 1e:8 The front-end ports are the ones that connect the application recovery host to the 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] symaccess -sid 0129 create -name group1 -type initiator - consistent_lun The -consistent_lun option forces all devices that are masked to the initiator 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 symaccess -sid name group1 -type initiator -wwn ddb5d0525eee8a00011 add 22 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

23 VMAX Application Storage Configuration Initiators can be added to an existing initiator group by specifying the initiator type (-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] symaccess create view -sid name view1 -sg group2 -pg portgroup1 -ig initator_group1 After you put the storage group, the port group, and the initiator group in the masking view, the initiators in the initiator group can see the devices via the port in the port group. 10. To update the local symapi database on the application recovery host, run the following command: symcfg discover Encapsulating Data Domain devices on the VMAX array This procedure is for encapsulating Data Domain devices on the VMAX array for new installations. Some of these steps may not be needed in all cases. To encapsulate the Data Domain devices on the VMAX array, complete the following steps on the application recovery host. Use the application recovery host to access both the VMAX and Data Domain environments. Before you begin Verify that the following prerequisites are met: Before you begin, to determine the devices in use, use the commands in the Data Domain Operating System Administration Guide and the Solutions Enabler functionality. Then use that information to complete the tasks in this section, as applicable. You must have already provisioned LUNs on the VMAX array to the application recovery host. You know or can obtain the geometry of the devices that are created on the VMAX array. You are logged in to the host where Solutions Enabler is installed. You complete some tasks in the VMAX environment, and other tasks in the Data Domain environment. Therefore, you must have one window open to the VMAX environment and one window open to the Data Domain environment. 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

24 VMAX Application Storage Configuration 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 or larger geometry as the VMAX primary LUNs. Create two block services for ProtectPoint devices for every device that is created on the VMAX array, one for 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 the Data Domain. 8. Verify that the VMAX DX ports and the Data Domain endpoint ports are zoned together. 9. View the list of VMAX initiators on the Data Domain. 10. Add the VMAX initiators to the access group on the Data Domain. 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 the VMAX array. Encapsulating an external LUN creates the VMAX LUN that enables access to the external LUN. Manually set the encapsulated LUN as the snapshot target. Encapsulating the block services for ProtectPoint restore LUNs is required for restoration operations. The VMAX array must have four paths to the Data Domain system to correctly enable the relationship between the two systems. ProtectPoint for VMAX prerequisites on page 16 provides more information about path requirements. Procedure 1. From the application recovery host, log in to the Data Domain system as the system administrator, sysadmin. 2. In the Data Domain environment, enable the block services for ProtectPoint protocol if not already enabled. a. To verify the block services for ProtectPoint license is enabled, run the following command: license show b. If a license is not already enabled, add the license by using the following command: license add <license_key> Output that is similar to the following appears: License AAAA-BBBB-CCCC-DDDD added. 24 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

25 VMAX Application Storage Configuration c. To enable block services for ProtectPoint, run the following command: vdisk enable Enabling block services for ProtectPoint enables a limited set of DD Boost features for ProtectPoint clients only. To enable full access to DD Boost functionality for all clients, add a DD Boost license. d. To verify block services for ProtectPoint are enabled, run the following command: vdisk status Output that is similar to the following appears: 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 backupoperator none}] user add user1 role none The Data Domain Operating System Version Command Reference Guide provides more information about the user add command and its options. 4. To create the block services for ProtectPoint device pool, run the following command: vdisk pool create <pool-name> user <user-name> vdisk pool create demo-1 user user1 To name device pools, use the guidelines in Block services for ProtectPoint object hierarchy on page 40. Encapsulating Data Domain devices on the VMAX array 25

26 VMAX Application Storage Configuration 5. To create the required number of block services for ProtectPoint device-groups within the device pool, run the following command: vdisk device-group create <device-group-name> pool <pool-name> vdisk device-group create demo-devgrp pool demo-1 To name device-groups, use the guidelines in Block services for ProtectPoint object 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 VMAX devices, run the following commands: a. To list the VMAX devices, run the following command: symdev list -sid <SymmetrixID> symdev list -sid 0129 Output that is similar to the following appears: Symmetrix ID: Device Name Dir Device Cap Sym Physical SA :P Config Attribute Sts (MB) Not Visible???:??? TDEV N/Grp'd ACLX RW Not Visible???:??? TDEV N/Grp'd RW Not Visible???:??? TDEV N/Grp'd RW Not Visible???:??? TDEV N/Grp'd RW 6 (output truncated for display) Not Visible???:??? TDEV N/Grp'd RW A Not Visible???:??? TDEV N/Grp'd RW B Not Visible???:??? TDEV N/Grp'd RW C Not Visible???:??? TDEV N/Grp'd RW D Not Visible???:??? TDEV N/Grp'd RW A6 Not Visible???:??? TDEV N/Grp'd RW A7 Not Visible???:??? TDEV N/Grp'd RW A8 Not Visible???:??? TDEV N/Grp'd RW b. To view the geometry of a specific device, run the following command: symdev show [<device number>] -sid <SymmetrixID> symdev show 0001A -sid EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

27 VMAX Application Storage Configuration Output that is similar to the following appears:... Geometry : Native { Sectors/Track : 256 Tracks/Cylinder : 15 Cylinders : byte Blocks : MegaBytes : KiloBytes : }... Use the geometry mappings in the following table to create the Data Domain block services for ProtectPoint devices. Table 5 VMAX to Data Domain device geometry mappings VMAX device geometry value Sectors per track Tracks per cylinder Cylinders Equivalent Data Domain device geometry value Sectors per track Heads Cylinders 7. On the Data Domain system, to create the block services for ProtectPoint devices that matches the geometry of the devices that are created on the VMAX 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> Output that is similar to the following appears: vdisk device create heads 15 cylinders sectors-per-track 256 pool demo-1 device-group demo-devgrp Create two devices on the Data Domain for each VMAX device, one for backup and 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> Encapsulating Data Domain devices on the VMAX array 27

28 VMAX Application Storage Configuration 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 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>}] vdisk group add demo-accgrp device vdisk-dev To view the list of initiators, run the following command: scsitarget initiator show list Output that is similar to the following appears: Initiator System Address Group Service initiator-1 2a:10:00:21:88:00:82:74 n/a n/a initiator-2 2b:10:00:21:88:00:82:74 n/a n/a initiator-3 50:02:18:82:08:a0:02:14 n/a n/a initiator-4 50:02:18:81:08:a1:03:cc n/a n/a ucs16d_2a 21:00:00:24:ff:3f:25:1a n/a n/a ucs16d_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 the Data Domain system. 28 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

29 VMAX Application Storage Configuration 12. To rename (alias) the initiators, run the following command: scsitarget initiator rename <src-initiator-name> <dstinitiator-name> scsitarget initiator rename initiator-1 vmax4d_3_08 Output that is similar to the following appears: 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> 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 system from the VMAX array, run the following command: symsan list -sid <SymmetrixID> -sanports -DX all -port all symsan list -sid sanports -DX all -port all 16. To copy the WWN for one of the ports and use the WWN to determine which LUNs are visible through this WWN, run the following command: symsan -sid <SymmetrixID> -dir All -p All list -sanluns -wwn <wwn> symsan -sid dir All -p All list -sanluns -wwn DDB5D The LUN is exposed but is not ready for use yet. The LUN must be encapsulated on to the VMAX array with FAST.X. 17. To create a VMAX storage group, run the following command: symsg create <SgName> Encapsulating Data Domain devices on the VMAX array 29

30 VMAX Application Storage Configuration symsg create storage-group-5 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 groups on the VMAX array, run the symdg list -sid <SymmetrixID> command. 18. To add the source VMAX devices to the storage group, run the following command: symsg -g <DgName> add dev <device_id> symsg -g storage-group-5 add dev 0001A 19. Encapsulate the Data Domain disk on the VMAX array. There are two ways to encapsulate disks: To encapsulate disks individually, run the following command: symconfigure -sid <SymmetrixID> -cmd "add external_disk, wwn=<wwn>, encapsulate_data=yes;" commit -v -nop symconfigure -sid cmd "add external_disk, wwn= ddb5d0525eee8a00011, encapsulate_data=yes;" commit -v -nop It takes approximately seven minutes to encapsulate each device. To encapsulate a group of devices, run the following commands: a. In a BASH shell on the application recovery host, to capture all the block services for ProtectPoint devices to encapsulate in a text file, run the following 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 The command fails if there are fewer than two devices that are specified in the text file. 30 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

31 VMAX Application Storage Configuration b. On the application recovery host, to encapsulate the block services for ProtectPoint devices that are listed in the text file, run the following command: symconfigure commit -f devs.txt Output that is similar to the following appears: Establishing a configuration change session...established. Processing symmetrix Performing 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. The VMAX array returns a contiguous range of new device names whenever possible. However, the range of device names is not always contiguous. The system performs the following steps: a. Takes the device with the specified WWN. The device is now visible to the VMAX 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, run the following command: symsg -g <SgName> add dev <device-number> -tgt 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> Encapsulating Data Domain devices on the VMAX array 31

32 VMAX Application Storage Configuration symsnapvx -sid sg storage-group-5 establish -name sg5- snap If additional devices or device groups are added to the ProtectPoint environment after the initial configuration, this step must be repeated for the new devices or device groups. 22. To move the data from the VMAX array on to the Data Domain system, run the following command: symsnapvx -sid <SymmetrixID> -sg <SgName> link -copy - snapshot_name <SnapshotName> symsnapvx -sid sg storage-group-5 link -copy - snapshot_name dg5-snap This command moves the changed blocks on the source device to the target device. If additional devices or device groups are added to the ProtectPoint environment after the initial configuration, this step must be repeated for the new devices or device groups. 23. (Optional) To set the data transfer rate for moving data from the VMAX array to the Data Domain system when a snapshot is created and activated for the first time, run the following command: symqos -sid <SymmetrixID> -sg <SgName> set clone pace {0-16 stop urgent} If you must change the clone pace, start with a setting of 4. This value results in a moderate reduction of the copy rate for Gen0 backups, which lowers the response 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 32 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

33 VMAX Application Storage Configuration symsnapvx list -detail -sid sg storage-group-5 -linked 25. If the environment is to use FAST.X restore operations, create a VMAX storage group 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 for the storage group, that name must be specified in the ProtectPoint file system agent or application agent configuration files. Perform the following steps: a. To create a storage group, run the following command: symsg -sid <SymmetrixID> create ProtectPointRestoreGroup symsg -sid 0129 create ProtectPointRestoreGroup 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 ProtectPoint devices that are encapsulated on the VMAX system can be deleted from the ProtectPoint configuration. You complete some tasks in the VMAX environment, and other tasks in the Data Domain environment. Therefore, you must have one window open to the VMAX environment and one window open to the Data Domain environment. Also, it is extremely important that you remove the devices from the VMAX before you remove the devices from the Data Domain. Procedure 1. Terminate all snapshot and replication sessions to the encapsulated disk you intend to delete. Perform the following steps: a. On the ProtectPoint file system agent, type Ctrl + C in the terminal window to abort any backups in progress. Encapsulating Data Domain devices on the VMAX array 33

34 VMAX Application Storage Configuration 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 following command: symdev release -lock -nop -sid <SymmetrixID> symdev release -lock -nop -sid 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 symdev -sid 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 symconfigure -sid cmd "remove external_disk wwn= ddb5d;" commit -nop 5. To delete the corresponding block services for ProtectPoint device from the Data Domain system, run the following command: vdisk device destroy <device-name> [destroy static-images {yes no} Additional storage configuration Optionally complete the following additional storage configuration tasks. 34 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

35 VMAX Application Storage Configuration N_Port ID Virtualization Enabling N_Port ID Virtualization To enable N_Port ID Virtualization (NPIV) on the Data Domain system, complete the following steps. N_Port ID Virtualization (NPIV) is a Fibre Channel feature in which multiple endpoints can share a single physical port. NPIV eases hardware requirements and provides endpoint failover/failback capabilities. NPIV is not configured by default, except in a HA configuration. NPIV provides simplified multiple-system consolidation: NPIV is an ANSI T11 standard that allows a single HBA physical port to register with a Fibre Channel fabric using multiple WWPNs. The virtual and physical ports have the same port properties and behave the same. 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: 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 an endpoint. Endpoint failover/failback is automatically enabled when using NPIV. After NPIV is enabled, the Secondary System Address must be specified at each of the endpoints. If not, endpoint failover does not occur. Multiple Data Domain systems can be consolidated into a single Data Domain system, however, the number of HBAs remains the same on the single Data Domain system. The endpoint failover is triggered when FC-SSM detects when a port goes from online to offline. If the physical port is offline before scsitarget is enabled, and the port 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 port offline event. If the port comes back online and auto-failback is enabled, any failed over 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 an HA pair during the failover process. N_Port ID Virtualization 35

36 VMAX Application Storage Configuration Before enabling NPIV, the following conditions must be met: The Data Domain system must be running a supported version of Data Domain OS. All ports must be connected to 4Gb, 8Gb, and 16 Gb Fibre Channel HBA and SLIC. 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 from being enabled: NPIV is allowed if the topology for all ports is loop-preferred. 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 the topology to loop-preferred for proper functionality. NPIV is not allowed if none of the ports have a topology of loop-preferred. If port names are present in access groups, the port names are replaced with their associated 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 must be disabled before NPIV can be enabled. If you are sure that you want to continue, select Yes. Next steps After the storage configuration is complete, the application or database administrator must install the agent to protect their environment. The next stages of the ProtectPoint configuration and installation process are covered in: EMC ProtectPoint File System Agent Installation and Configuration Guide EMC Data Domain Boost for Enterprise Applications and ProtectPoint Database Application Agent Version Installation and Administration Guide EMC Data Domain Boost for Enterprise Applications and ProtectPoint Microsoft Application Agent Version Installation and Administration Guide 36 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

37 CHAPTER 3 XtremIO Application Storage Configuration This chapter includes the following topics: ProtectPoint for XtremIO with RecoverPoint environment...38 ProtectPoint for XtremIO with RecoverPoint prerequisites Configure XtremIO storage and connect the Data Domain system, RecoverPoint cluster, and XtremIO cluster Additional storage configuration Next steps XtremIO Application Storage Configuration 37

38 XtremIO Application Storage Configuration ProtectPoint for XtremIO with RecoverPoint environment The ProtectPoint for XtremIO with RecoverPoint environment consists of the following components: Data Domain: A Data Domain system with a supported Data Domain operating system. Data Domain block services for ProtectPoint. DD Boost. (Optional) Data Domain MTree replication. RecoverPoint: A RecoverPoint cluster with two to eight RecoverPoint appliances. XtremIO: An XtremIO cluster running storage array software. Application: Application recovery host. ProtectPoint agent on the application recovery host. To view the supported versions of components, go to the following website: getprotectpointcompguidepage.do ProtectPoint for XtremIO with RecoverPoint prerequisites The following are prerequisites for all ProtectPoint for XtremIO with RecoverPoint operations. ProtectPoint file system agent prerequisites The ProtectPoint file system agent prerequisites for all ProtectPoint for XtremIO with RecoverPoint operations are as follows: User accounts for block services for ProtectPoint, and DD Boost must be created on the Data Domain system. (Optional) Create a user account on the RecoverPoint appliance. The ProtectPoint file system agent must be installed on the application recovery host. Database application agent and Microsoft application agent prerequisites The database and Microsoft application agent prerequisites for ProtectPoint operations are as follows: A valid license for the ProtectPoint environment. The application agent must be installed on the production and recovery host. User accounts for block services for ProtectPoint, and DD Boost must be created on the Data Domain system. 38 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

39 XtremIO Application Storage Configuration RecoverPoint prerequisites XtremIO prerequisites (Optional) Create a user account on the RecoverPoint appliance. The RecoverPoint prerequisites for all ProtectPoint for XtremIO operations are as follows: A RecoverPoint backup (BK) license. A RecoverPoint cluster with RecoverPoint appliances, running RecoverPoint software. Port 443 must be open between the RecoverPoint appliances, the XtremIO Management System, and the XtremIO System-wide Management (SYM) module on X1-Storage Controller 1 (X1-SC1) and X1-Storage Controller 2 (X1-SC2) IP addresses. Port must be open between the RecoverPoint appliances and XtremIO SYM module on X1-SC1 and X1-SC2. IP connectivity must be configured between the RecoverPoint appliance and the Data Domain system. For IP connections between the RecoverPoint appliances and the Data Domain system, the Data Domain ifgroup feature provides improved network performance by spreading the network traffic across multiple network interfaces. The EMC Data Domain Operating System Administration Guide provides more details about ifgroups. FC zoning between the RPA and the XtremIO cluster. FC zoning is optional between the RecoverPoint appliance and the Data Domain system. (Optional) FC zoning between the RecoverPoint appliance and the Data Domain system is only required if DD Boost over FC is used for communication between the RecoverPoint appliance and the Data Domain system: Zone at least two initiators from the RecoverPoint appliance to the Data Domain system. One zone per fabric between the RecoverPoint appliance and the XtremIO cluster. Include all the RecoverPoint appliance ports that are intended for XtremIO connectivity, and all the XtremIO ports that are intended for RecoverPoint appliance connectivity in the zone. Zone the RecoverPoint initiators to multiple targets on the Data Domain system or XtremIO cluster in accordance with RecoverPoint best practices. The XtremIO prerequisites for all ProtectPoint for XtremIO operations are as follows: An XtremIO cluster running XtremIO software. FC zoning must be configured between the XtremIO cluster and the application recovery host: Use a single-initiator per single-target (1:1) zoning scheme or use multipathing between XtremIO and the hosts for failover and redundancy. If the FC switchzone count limitation has been reached, it is also possible to use singleinitiator per multiple-target (1:many) zoning scheme. RecoverPoint prerequisites 39

40 XtremIO Application Storage Configuration Data Domain prerequisites DD Boost prerequisites The optimal number of paths depends on the operating system and server information. To avoid multipathing performance degradation, do not use more than 16 paths per device. Enable MPIO if two or more paths are zoned to a Windows application recovery host. The Data Domain prerequisites for all ProtectPoint for XtremIO operations are as follows: A Data Domain system that ProtectPoint supports. Block services for ProtectPoint must be enabled on the Data Domain system. A Data Domain system with DD Boost enabled. Data Domain Cloud Tier can be enabled, but the Data Domain storage unit that ProtectPoint uses cannot have a data movement policy. Enable the DD Boost service, and then create a storage unit. Data Domain block services prerequisites The prerequisites for Data Domain block services operations are as follows: (Optional) Create the Data Domain file system (DDFS). Configure a username and password for ownership of the Data Domain block services for ProtectPoint devices. It is recommended that you create this user with the none role. If required, other roles can be configured. Apply a Data Domain block services for ProtectPoint license. Block services for ProtectPoint object hierarchy To plan the ProtectPoint configuration, use the object hierarchy mappings in the following table. Table 6 Block services for ProtectPoint object hierarchy mappings Storage object Pool Device-group Device Mapping level Department Application Device Data Domain storage layout By default, access control is implemented at the pool level. If additional granularity is required, create the pools based on the access control requirements. The following figure displays the storage layout of the DDFS. 40 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

41 XtremIO Application Storage Configuration Figure 3 DDFS storage layout 1. /data 2. /data/col1 3. /data/col1/backup 4. /data/col1/mtree2 5. /data/col1/mtree3 The following table describes each element of the DDFS storage layout. Table 7 DDFS storage elements DDFS directory /data /data/col1 /data/col1/backup /data/col1/mtree<x> Description Top-level directory of the Data Domain storage file system. This directory cannot be changed. Represents a collection of data, and enables the expansion of the file system by creating additional collections, col2, col3, col4, and so on. Contains backups of the data and directory structure of the collection. This MTree cannot be deleted or renamed. Subdirectories can be created to organize and separate the data. Represents the lowest level of the Data Domain storage file system. Each MTree is an independently managed directory. Data Domain allows up to 100 MTrees to be created, but performance degradation occurs when more than 32 MTrees are active at one time. Data Domain block services for ProtectPoint Data Domain block services for ProtectPoint allow you to create devices, device groups, 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

42 XtremIO Application Storage Configuration Data Domain file system The EMC Data Domain Operating System Command Reference Guide provides more information about the block services for ProtectPoint and the vdisk commands that control them. The Data Domain file system (DDFS) stores the block services for ProtectPoint objects. For example, a block services static-image can be treated as a file that resides within 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 for ProtectPoint can efficiently create static-images of LUNs. The DDFS automatically defragments backups that are created in a ProtectPoint environment to prevent performance degradation over time. The EMC Data Domain Operating System Administration Guide provides more information about the DDFS. Configure XtremIO storage and connect the Data Domain system, RecoverPoint cluster, and XtremIO cluster Provision primary storage Volumes on the XtremIO cluster, and connect the Data Domain system, RecoverPoint cluster, and XtremIO cluster to configure the protection storage. RecoverPoint automatically creates the Data Domain block services for ProtectPoint device-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 backup devices, and the restore devices must be the same size or larger than the staticimages to be restored. Creating an XtremIO initiator group Do not place restore devices into the backup device-group created by RecoverPoint on the Data Domain system. Before you begin Perform the following tasks: Ensure that the RecoverPoint cluster is zoned so it can see the XtremIO cluster. Ensure that the RecoverPoint cluster is configured and running. 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. 42 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

43 XtremIO Application Storage Configuration 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, repeat steps 3 to 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 specify the following information: In Tag caption, specify a descriptive name for the Tag, such as protectpoint. Tag color. 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 the host FC port addresses for steps 6 and 7, repeat steps in this procedure. Configuring XtremIO storage for a single volume To configure primary storage on the XtremIO system by creating a single Volume at a time, 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. Be aware of the following requirements for creating Volumes: The minimum Volume size is 1 MB. The volume size should be in multiples of 8 KB. 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

44 XtremIO Application Storage Configuration 4. To optionally assign Tags to the Volumes, click Next, or to skip creating tags, click Finish. 5. Select an existing Tag, or to create a Tag, click Create Tag, and then specify the following information: In Tag caption, specify a descriptive name for the Tag, such as protectpoint. Tag color. Tag nesting path. Tagging objects enables you to logically group, locate and manage multiple entities, and perform operations on multiple objects, using a single user command. You can use tagging to aggregate objects based on business requirements, and assign Tags according to related applications for ease-ofmanagement. Each object can have multiple Tags to reflect the object's function 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. Volumes must be exposed to both the RecoverPoint appliance initiator group, and the host initiator group. e. Click Next. f. Click Finish. Configuring XtremIO storage for multiple volumes To configure primary storage on the XtremIO system by configuring multiple volumes at 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). 44 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

45 XtremIO Application Storage Configuration c. The Start Index for the Volumes. Each Volume must have a unique name. Each time that you add multiple Volumes, the suffix automatically starts at 1. Therefore, adding multiple Volumes more than once while using the same prefix, results in repeating names. d. The amount of disk space that is allocated for the Volume. Be aware of the following requirements for creating Volumes: The minimum Volume size is 1 MB. The volume size should be in multiples of 8 KB. 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. 5. To optionally assign Tags to the Volumes, click Next, or to skip creating tags, click Finish. 6. Select an existing Tag, or to create a Tag, click Create Tag, and then specify the following information: In Tag caption, specify a descriptive name for the Tag, such as protectpoint. Tag color. 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. Volumes must be exposed to both the RecoverPoint appliance initiator group, and the host initiator group. Configuring XtremIO storage for multiple volumes 45

46 XtremIO Application Storage Configuration e. Click Next. f. Click Finish. Configuring Data Domain services and users To configure Data Domain services and users, complete the following steps. Before you begin The DDFS must be configured. Obtain a block services for ProtectPoint license key. Procedure 1. From the application recovery host, log in to the Data Domain system as the system 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 the following command: license show b. If the license is not already enabled, to add the license, run the following command: 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 Enabling block services for ProtectPoint enables a limited set of DD Boost features for ProtectPoint clients only. Optionally, to enable full access to DD Boost functionality for all clients, add a DD Boost license. d. To verify block services for ProtectPoint are enabled, run the following command: vdisk status Output that is similar to the following appears: VDISK admin state: enabled, process is running, licensed 46 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

47 XtremIO Application Storage Configuration 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 pool and the DD Boost storage-unit, run the following command: user add <user> [role {admin security user backupoperator none}] user add user1 role none The Data Domain Operating System Version Command Reference Guide provides more 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> ddboost user assign user1 6. Do not log out of the Data Domain system. Enabling encryption over a WAN connection The database application agent provides support for DD Boost clients to have in-flight data encryption with a Data Domain 5.5 or later operating system over a WAN connection. To enable the in-flight data encryption over a WAN connection, you can configure the Data Domain system with either medium-strength or high-strength TLS encryption. For example, run the following ddboost command to set the required TLS encryption for 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 Boost Administration Guide provides details. Enabling encryption over a WAN connection 47

48 XtremIO Application Storage Configuration Configuring the DD Boost over Fibre Channel service To configure the DD Boost over Fibre Channel (DFC) service, complete the following steps. Before you begin Ensure that the application recovery host and the Data Domain system can see each other 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> ddboost fc dfc-server-name set ddboost-fc-server Alternatively, accept the default, which has the format DFC-<base hostname>. The hostname cannot be the fully qualified domain name. A valid DFC server name consists of one or more of the following characters: Lowercase letters (a-z) Uppercase letters (A Z) Digits (0 9) Underscore (_) Dash ( ) The dot or period character (.) is not valid within a dfc-server-name. This precludes using the fully qualified domain name of a Data Domain system as its dfc-server-name. Similar to IP hostnames, the dfc-server-name is not case-sensitive. Multiple Data Domain systems accessible by the same clients using DDBoost-over-FC should 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> ddboost fc group create boost-fc-group 48 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

49 XtremIO Application Storage Configuration 4. To populate the DD Boost FC group, add DFC devices. When creating devices: For Linux or UNIX hosts, create one device per host initiator. 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>} 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, add initiators to the DD Boost FC group. Run the following command: ddboost fc group add <group-name> initiator "<initiator-spec>" ddboost fc group add initiator "initiator-15, initiator-16" Configuring DD Boost storage units 6. Do not log out of the Data Domain system. 7. From the application recovery host, ensure that the user who performs the backups and restores has the required permission to access the DFC devices. To configure the DD Boost storage units that are required for ProtectPoint, complete the following steps. Before you begin Perform the following tasks: Ensure that DD Boost is configured. 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 following command: ddboost storage-unit create <storage-unit> user <user> ddboost storage-unit create RecoverPointStorageUnit user user1 Configuring DD Boost storage units 49

50 XtremIO Application Storage Configuration 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. Run the following command: ddboost storage-unit create <storage-unit> user <user> ddboost storage-unit create CatalogStorageUnit user user1 The storage unit is automatically created as /data/col1/<storage-unit>. Specify a descriptive name when creating the storage unit. 3. Do not log out of the Data Domain system. Configuring block services for ProtectPoint objects To configure block services for ProtectPoint pools, device-groups, and devices, complete the following steps. Before you begin Perform the following tasks: Ensure that Block services for ProtectPoint is enabled. Ensure that Block services for ProtectPoint privileges are assigned to the same username that owns the DD Boost storage-units. Procedure 1. To create the block services for ProtectPoint backup device pool, run the following command: vdisk pool create <pool-name> user <user-name> vdisk pool create backup-demo-1 user user1 To name device pools, use the guidelines in Block services for ProtectPoint object hierarchy on page EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

51 XtremIO Application Storage Configuration 2. To create the block services for ProtectPoint restore device pool, run the following command: vdisk pool create <pool-name> user <user-name> vdisk pool create restore-demo-1 user user1 To name device pools, use the guidelines in Block services for ProtectPoint object hierarchy on page To create the block services for ProtectPoint restore device-group, run the following command: vdisk device-group create <device-group-name> pool <pool-name> vdisk device-group create restore-group pool restore-demo-1 To name device-groups, use the guidelines in Block services for ProtectPoint object hierarchy on page To create the block services for ProtectPoint restore 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> vdisk device create count 5 capacity 1 GiB pool restoredemo-1 device-group restore-group Create at least as many restore devices as there are backup devices. The restore devices must be the same size or larger than the largest backup device created by RecoverPoint. 5. Do not log out of the Data Domain system. Configuring block services for ProtectPoint objects 51

52 XtremIO Application Storage Configuration Configuring a Data Domain access group for the application recovery host For Fibre Channel environments, to configure an access group to mask the restore devices to the application recovery host, complete the following steps. Before you begin Perform the following tasks: Ensure that the Data Domain system and the application recovery host can see each other over the FC SAN. Ensure that the block services for ProtectPoint restore devices and device-groups are configured. Procedure 1. To create an access group, run the following command: scsitarget group create <scsi-group-name> service vdisk sysadmin@lfcp1158# scsitarget group create lfcp1011 service vdisk Output that is similar to the following appears: Group 'lfcp1011' successfully created. 2. To view the list of initiators, run the following command: scsitarget initiator show list Output that is similar to the following appears: Initiator System Address Group Service initiator-1 2a:10:00:21:88:00:82:74 n/a n/a initiator-2 2b:10:00:21:88:00:82:74 n/a n/a initiator-3 50:02:18:82:08:a0:02:14 n/a n/a initiator-4 50:02:18:81:08:a1:03:cc n/a n/a ucs16d_2a 21:00:00:24:ff:3f:25:1a n/a n/a ucs16d_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 to the Data Domain system. 3. To rename (alias) the initiators, run the following command: scsitarget initiator rename <src-initiator-name> <dstinitiator-name> scsitarget initiator rename initiator-1 arhost_3_08 52 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

53 XtremIO Application Storage Configuration Output that is similar to the following appears: Initiator 'initiator-1' successfully renamed. 4. To add host initiators to the access group, run the following command: scsitarget group add <scsi-group-name> initiator <host-wwn> 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> scsitarget group add restore-access-group device vdisk-dev0 6. To verify that the host can see the block services for ProtectPoint devices, run the following command: scsitarget group show list Output that is similar to the following appears: Group Name Service # Initiators # Devices restore-access-group VDISK The Data Domain system displays all the host initiators and block devices added to the access group. Logging into RecoverPoint Before you begin Obtain your RPA cluster management IP. Optionally obtain your RecoverPoint username and password. Procedure 1. Open a web browser and enter the cluster management IP into your browser address bar. The RecoverPoint login screen is displayed. Logging into RecoverPoint 53

54 XtremIO Application Storage Configuration 2. In the RecoverPoint login screen, log in with your username and password, or enter the default RecoverPoint Username admin and Password admin. Results Unisphere for RecoverPoint is displayed. After you finish Install a license in RecoverPoint Select RPA Clusters > RPA-Cluster-Name > RPAs. Click the tab of each RPA cluster and ensure that a green checkbox appears in both the Status and Connectivity columns of all RPAs at each RPA cluster. Before you begin Access and activate your entitlements. 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. 54 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

55 XtremIO Application Storage Configuration b. Click Browse... c. Select the license file. d. Click OK. Register storage in RecoverPoint Register your Data Domain systems and the XtremIO Management servers on the RPA cluster and define whether to transfer data using FC or IP. Before you begin Configure access to the XtremIO arrays you want to protect, and SAN and FC access to your Data Domain. Zone and mask your XtremIO arrays, Data Domains and their block services for ProtectPoint pools to the relevant RPA clusters. Before you register the Data Domain system on the RPA cluster: Ensure the RPA cluster and the Data Domain system can see each other over the IP LAN and (optionally) FC SAN. Obtain the Data Domain IP address in IPv4 or IPv6 format. Obtain the DD Boost username and password. Obtain the name of the DD Boost storage unit to use. Before you register the XtremIO Management Server on the RPA cluster: Ensure the RPA cluster and the XtremIO cluster can see each other over the FC SAN. Ensure network connectivity exists between the RPA cluster and the XtremIO cluster. Obtain the XtremIO Management Server (XMS) IP address in IPv4 or IPv6 format. 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

56 XtremIO Application Storage Configuration In the right pane, the Registered Storage table is displayed. The Registered Storage table contains the list of all of the XtremIO arrays and Data Domain systems that are currently registered at the selected RPA cluster. 3. In the right pane, in the Registered Storage tab, click Add. The Register Storage dialog box is displayed. 4. In the Register Storage dialog box: Register an array seen by this RPA cluster This is the preferred method of storage registration in ProtectPoint. To register any Data Domain system or XtremIO array that has already been masked to the RPA cluster: a. Select an array from the list b. Define the storage login credentials: Define Data Domain login credentials Define XtremIO login credentials Register any storage To register any Data Domain system or XtremIO array, regardless of whether or not it is masked to the RPA cluster: 56 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

57 XtremIO Application Storage Configuration a. Select the storage type from the drop-down. b. Define the storage login credentials: Define Data Domain login credentials Define XtremIO login credentials Define storage login credentials in RecoverPoint Defines the login credentials for your Data Domain systems and XtremIO arrays in RecoverPoint, and whether to transfer data using FC or IP. For Data Domain systems: Enter the Data Domain IP address. Enter the username and password for the block services for ProtectPoint pool and DD Boost storage-unit in the Username and Password fields. Enter the DD Boost Storage Unit to use as the ProtectPoint catalog. By default, the Use FC for data transfer checkbox is selected. Uncheck to use IP only for data transfer. Define storage login credentials in RecoverPoint 57

58 XtremIO Application Storage Configuration For XtremIO arrays: Enter the IP address of the XtremIO Management Server (XMS). If the XtremIO Management Server manages more than one cluster, register each cluster separately. Enter the Serial number (PSNT) of the XtremIO cluster. Enter the XtremIO rp_user as the User. 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 RecoverPoint Registers Data Domain block services for ProtectPoint pools at an RPA cluster. Before you begin Pre-configure resource pools on the Data Domain in the same user Storage Unit and block services for ProtectPoint pool. 58 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

59 XtremIO Application Storage Configuration Register storage in RecoverPoint on page 55 After registering a block services for ProtectPoint pool, a manual change on the Data Domain will be required to unregister them and make them available for other clusters or 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 Registered Storage tab contains the list of all of the storage systems that are currently registered 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

60 XtremIO Application Storage Configuration 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 RecoverPoint Creates a new consistency group. Before you begin Adding a Data Domain volume to a consistency group automatically sets its volume access mode to Read-Only. Data Domain volumes in a consistency group become writeable when: image access is enabled. the copy or consistency group containing the Data Domain volume is disabled. Backup copy LUNs can be located on up to two Data Domain systems, per RPA cluster. A single Data Domain device may exist in more than one consistency group. Configure your Data Domains and XtremIOs. Create XtremIO initiator groups. Register your Data Domains and XtremIOs and your block services for ProtectPoint pools. If one volume at a copy is on an XtremIO array, all other XtremIO volumes at that copy must be on the same array. For applications running on a host cluster: The RecoverPoint system supports both local and remote high-availability host clusters. Place all volumes that are resources of the host cluster in a single consistency group. Simplify management by assigning the name of the host cluster as the name of the consistency group. The Journal volumes must not be resources of the host cluster. Assign each replication set the same name as its disk resource in the cluster. If all cluster nodes (hosts) at the side are down, you may not be able to create replication volumes. To correct this problem, either bring up the nodes, or run a rescan_san command (from the CLI), with volumes=full. Prior to enabling a consistency group, the system Dashboard may show an Error on the source-side storage and display the message Volume cannot be accessed by any RPA. The errors are removed when the consistency group is enabled. Procedure 1. Select Protection > Protect Volumes. 2. In the Select Production Volumes screen: a. Define the consistency group name, the production name, and the RPA cluster that will manage the production. 60 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

61 XtremIO Application Storage Configuration b. Select your production volumes in the volume list. If one volume at a copy is on an XtremIO array, all other XtremIO volumes at that copy must be on the same array. Use the toolbar at the top-right corner of 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. You can also click and drag the column dividers to make the columns wider or thinner. In most cases, RecoverPoint will remember the column width that you define, and display the columns accordingly in each subsequent 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 copy policies now, or skip this step and define the policies later. The policy settings are optional. The default values provide a practical configuration. It is recommended to accept the default settings unless there is 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

62 XtremIO Application Storage Configuration 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 nondistributed consistency groups and 40 GB for distributed consistency groups, since the XtremIO journal contains only pointers to snapshots and metadata. For best performance, select volumes that are identical in size. If identically sized volumes are not available, select volumes that are similar in size. Use the toolbar icons at the top-right corner of the screen to help you identify 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 production volumes. 62 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide

63 XtremIO Application Storage Configuration 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 in which RecoverPoint replicates the production data to the selected copy. e. Optionally, to enable RecoverPoint to automatically delete the device group and all of its block services for ProtectPoint pools and static images on the Data Domain if this copy is deleted, click Modify Policies, and select the Delete journal upon removal checkbox in the Copy Policy tab. If you want to change the protection settings using policy templates, in the Link tab, use the Select Template drop-down to select one of your templates. Click Load to load the settings in the template and click OK to apply the settings. f. Select the Data Domain system to use as the copy, and the block services for the ProtectPoint pool in which to store the Data Domain static-images. The Data Domain copy journal is automatically provisioned in the same resource pool as the copy. RecoverPoint automatically creates the backup block services for ProtectPoint device groups and the devices to populate the 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

64 XtremIO Application Storage Configuration a. Use the following options until the consistency group diagram reflects your requirements: Table 9 Group summary screen Action Edit Delete Description Opens the Add a Copy screen of the copy whose Edit link you clicked, allowing you to edit the copy settings, and modify the copy volume configuration, replication mode, or protection plan. Removes the copy whose Delete link you clicked, from the consistency group. You cannot delete the production copy. Replication Sets Displays detailed volume information on all replication set volumes that have been defined for the consistency group. Select a row in the replication sets table in the top section to display the associated volume information in the bottom section. Click on the replication set name to open the Edit Replication Set dialog box, and rename the replication set. Start replication... when I click 'Finish' When selected, starts transfer for the group as soon as the group is created. A first-time initialization (or fast first-time initialization) occurs when a consistency group is enabled for the first time. 64 EMC ProtectPoint 3.5 Primary and Protection Storage Configuration Guide