Dell EMC ProtectPoint

(1)

Dell EMC ProtectPoint

Version 4.7

Primary and Protection Storage Configuration Guide

(2)

Published January 2019

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.

Dell EMC

Hopkinton, Massachusetts 01748-9103

(3)

7

ProtectPoint Storage Configuration Overview 11

ProtectPoint family overview... 12

File system agent... 12

Database application agent... 13

Microsoft application agent...14

Application storage configuration overview...14

Data Domain sizing considerations... 15

Discovering application storage...16

Host considerations... 16

VMAX Application Storage Configuration 17 ProtectPoint for VMAX environment... 18

Additional information... 18

ProtectPoint for VMAX prerequisites...18

File system agent prerequisites... 18

Database application agent and Microsoft application agent prerequisites... 19

VMAX prerequisites... 19

Data Domain prerequisites...20

DD Boost prerequisites...21

Data Domain block services prerequisites...21

Discovering device geometry...23

Provision VMAX storage and encapsulate the Data Domain devices on the VMAX array... 23

ProtectPoint performance considerations for VMAX Gen0 backups ... 23

Provision FAST.X restore LUNs to the application recovery host.... 24 Encapsulate Data Domain devices on the VMAX array...27

Gatekeepers... 38

Additional storage configuration...39

N_Port ID Virtualization...39

Next steps...41

XtremIO Application Storage Configuration 43 ProtectPoint for XtremIO overview...44

ProtectPoint for XtremIO components...44

ProtectPoint for XtremIO prerequisites...45

File system agent prerequisites... 45

Database application agent and Microsoft application agent prerequisites...45

RecoverPoint prerequisites... 45

XtremIO prerequisites...46

Data Domain prerequisites...46 Preface

Chapter 1

Chapter 2

Chapter 3

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.

Note

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

To access the ProtectPoint user documentation: 1. Go to https://support.emc.com/products.

2. In the search box, type ProtectPoint, and then select the product name that

appears.

3. Click Documentation.

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 the file system agent, database application agent, and Microsoft application agent.

Revision History

The following table presents the revision history of this document

Table 1 Revision history

Revision Date Description

02 January 4, 2019 Removed all references to ProtectPoint for virtual machines, as the feature is not supported in this release.

01 December 14, 2018 Initial release of the ProtectPoint Primary and Protection Storage Configuration Guide version 4.7.

The following publications provide additional information: l ProtectPoint Solutions Guide

l ProtectPoint Primary and Protection Storage Configuration Guide l File System Agent Installation and Administration Guide

l File System Agent Release Notes

l Database Application Agent Installation and Administration Guide

(8)

l Database Application Agent Release Notes l Microsoft Application Agent Installation Guide

l Microsoft Application Agent Exchange Server User Guide l Microsoft Application Agent SQL Server User Guide l Microsoft Application Agent Release Notes

For compatibility information, including specific backup software and hardware configurations, visit:

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

The documentation for the following products provides additional information: l Data Domain

l Data Protection Manager (DPM) l VMAX

l XtremIO l RecoverPoint

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

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

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

l System code

l _{System output, such as an error message or script} l Pathnames, file names, file name extensions, prompts, and

syntax

l _{Commands and options} Monospace italic Used for variables.

Monospace bold Used for user input.

(9)

Table 2 Style conventions (continued)

| 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 l https://www.dell.com/support l https://community.emc.com Where to get support

The Support website https://www.dell.com/support provides access to product licensing, documentation, advisories, downloads, and how-to and troubleshooting information. The information can enable you to resolve a product issue before you contact Support.

To access a product-specific page: 1. Go to https://www.dell.com/support.

2. In the search box, type a product name, and then from the list that appears, select the product.

Knowledgebase

The Knowledgebase contains applicable solutions that you can search for either by solution number (for example, KB000xxxxxx) or by keyword.

To search the Knowledgebase:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Knowledge Base.

3. In the search box, type either the solution number or keywords. Optionally, you can limit the search to specific products by typing a product name in the search box, and then selecting the product from the list that appears.

Live chat

To participate in a live interactive chat with a support agent: 1. Go to https://www.dell.com/support.

2. On the Support tab, click Contact Support.

3. On the Contact Information page, click the relevant support, and then proceed.

Service requests

To obtain in-depth help from Licensing, submit a service request. To submit a service request:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Service Requests.

(10)

Note

To create a service request, you must have a valid support agreement. For details about either an account or obtaining a valid support agreement, contact a sales representative. To get the details of a service request, in the Service Request Number field, type the service request number, and then click the right arrow. To review an open service request:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Service Requests.

3. On the Service Requests page, under Manage Your Service Requests, click

View All Dell Service Requests. Online communities

For peer contacts, conversations, and content on product support and solutions, go to the Community Network https://community.emc.com. Interactively engage with customers, partners, and certified professionals online.

How to provide feedback

(11)

CHAPTER 1 ProtectPoint Storage Configuration Overview

Topics include:

l ProtectPoint family overview...12

l Application storage configuration overview... 14

l Data Domain sizing considerations...15

l Discovering application storage... 16

l Host considerations... 16

(12)

ProtectPoint family overview

The ProtectPoint family consists of the file system agent, the database application agent, and the Microsoft application agent.

ProtectPoint for VMAX provides data protection for application data that is hosted on VMAX storage systems.

ProtectPoint for XtremIO uses RecoverPoint to provide data protection for application data hosted on XtremIO storage systems.

The following terms describe the supported replication topologies: Backup

Data protection method that provides block movement of the application data on primary storage LUNs to a Data Domain system. Also used to refer to the copies created on the Data Domain system.

Full application rollback restore

Block movement of the data from the copies on the Data Domain system to the restore destination LUNs on primary storage.

Object level restore

Makes the copies that are on Data Domain available for mount to the recovery host. The database application agent and the Microsoft application agent also restore the files that are required for recovery automatically.

File system agent

The file system agent includes the following features:

l Provides commands that you can use to trigger the primary storage to Data Domain workflow for backup and restore operations.

l Provides commands for lifecycle management of the backups.

l Triggers backup and restore operations on the primary storage system and Data Domain system through the use of primary storage system features and Data Domain block services (called Data Domain vdisk) for ProtectPoint management libraries, respectively.

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

The file system agent cannot operate in a non-English environment or locale, and does not support any non-ASCII input or output.

Use the file system agent to perform the following operations:

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

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

l Create a static image for each LUN in the dataset on the Data Domain system. l Securely manage the credentials for the Data Domain systems and RecoverPoint

(13)

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

l Roll back a specified backup to its original source devices. l Restore a backup to the restore devices.

l Manage the ProtectPoint backup and scan catalog.

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

l Display the ProtectPoint version number.

l Validate the content and format of the configuration files. Configuration file

The file system agent configuration file specifies information about:

l The file system agent protected environment, including the Data Domain name and username.

l Backup and restore source devices or groups. l Performing restores and rollbacks.

The file system agent provides the following template configuration files: l ProtectPoint for VMAX environments

l ProtectPoint for RecoverPoint environments

Select a template, make a copy of the template, and then modify the copy as required. After you make the copy of the configuration template file, specify the environment information in the copy. When you set up the file system agent on the application recovery host, modify the configuration file to include the specific details about the devices. You can have any number of configuration files.

You must also update the lockbox with the Data Domain and optionally the RecoverPoint passwords.

Database application agent

The database application agent includes the following features:

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

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

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

l Operates on the database level, so the database application agent software automatically discovers the primary storage devices where database objects reside.

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

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

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

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

(14)

l Provides support for Internet Protocol version 6 (IPv6) for backups and restores except on Windows, and supports the Data Domain IPv6, IPv4, and mixed IPv4 and IPv6 networks. IPv6 IP addresses are not supported on Windows.

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

Microsoft application agent

The Microsoft application agent includes the following features:

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

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

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

l Operates on the database level, so the database application agent software automatically discovers the primary storage devices where database objects reside.

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

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

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

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

l Provides support for Internet Protocol version 6 (IPv6) for backups and restores, and supports the Data Domain IPv6, IPv4, and mixed IPv4 and IPv6 networks. The 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 16 includes information about discovering the existing application storage.

When configuring application storage, complete the following high level processes: l Provision primary storage LUNs to the application recovery host.

(15)

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

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

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

l Number: The number of LUNs to back up. l Size: The size of each LUN to back up. l Copies: The number of backups to keep.

l To account for copies of the data on both the backup and restore devices, add 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 5 + 2 Required capacity 700 GB

(16)

Note

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:

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

l Actual capacity is reported at the system level.

Discovering application storage

Configure ProtectPoint after storage provisioning is complete by identifying all the existing application storage and computing the Data Domain storage requirements. 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 storage area network (SAN) zoning. The process to provision the Data Domain storage and connect the storage to the primary storage system is identical to provisioning new storage.

Host considerations

The following host considerations can impact the ProtectPoint performance: l 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. Note

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

(17)

CHAPTER 2 VMAX Application Storage Configuration

Topics include:

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

array...23 l Additional storage configuration... 39 l Next steps... 41

(18)

ProtectPoint for VMAX environment

The ProtectPoint for VMAX environment consists of the following components: l Data Domain:

n A Data Domain system with a supported Data Domain operating system. n Data Domain block services for ProtectPoint.

n (Optional) Data Domain replication license.

l VMAX:

n A VMAX array.

n A VMAX license is required for ProtectPoint.

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

n Application host.

n ProtectPoint agent on the application host. To view the supported versions of components, go to:

Additional information

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

File system agent prerequisites

The following are file system agent prerequisites for VMAX operations:

l The required software licenses must be installed for ProtectPoint, for example, the license for Solutions Enabler or any other software component for VMAX. Contact your sales representative for more details about the required licenses for your environment.

l The file system agent can be installed on any host that has access to VMAX or RecoverPoint, and is configured to operate the agent.

l The vdisk service must be enabled, and the vdisk user account must be created. You can run the vdisk status command to confirm that the vdisk service is enabled. For example:

vdisk status

(19)

l DD Boost must be enabled, and the DD Boost user account must be created. You can run the ddboost status command to confirm that DD Boost is enabled. For example:

ddboost status

DD Boost status: enabled

l Solutions Enabler must be installed on the file system agent host.

If you have a user that is not root, the Solutions Enabler documentation provides information about how to configure a user account without root access.

l Solutions Enabler requires gatekeepers that are configured and masked to the application host. The ProtectPoint Primary and Protection Storage Configuration Guide provides more information about configuring gatekeepers.

l The Solutions Enabler configuration database must be up-to-date on any host where a backup or recovery might run. To update the database with the complete VMAX information for the host, run the symcfg discover command prior to a backup. The Solutions Enabler documentation provides more information.

Database application agent and Microsoft application agent prerequisites

The database and Microsoft application agent prerequisites for ProtectPoint operations are as follows:

l The required software licenses must be installed for ProtectPoint. Contact your sales representative for more details about the required licenses for your environment.

l The application agent must be installed on the production host and recovery host. l The vdisk service must be enabled, and the vdisk user account must be created. l DD Boost must be enabled, and the DD Boost user account must be created. l The Solutions Enabler database must be up-to-date on any host where a backup or

recovery might run. To update the Solutions Enabler database, type the symcfg discover command. The Solutions Enabler documentation provides more information.

l Solutions Enabler requires gatekeepers that are configured and masked to the application host. The ProtectPoint Primary and Protection Storage Configuration Guide provides more information about configuring gatekeepers.

VMAX prerequisites

The following are VMAX prerequisites for all ProtectPoint for VMAX operations: l A VMAX array.

l Solutions Enabler in local mode on the application recovery host. l The required VMAX source capacity licenses.

l DX directors on the VMAX system are available to encapsulate the Data Domain protection storage.

l If the application data is located on LUNs from multiple VMAX arrays, the restore devices are configured in the same Data Domain vdisk pool.

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

(20)

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

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

n 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

Data Domain prerequisites

The following are Data Domain prerequisites for all ProtectPoint for VMAX operations: l A Data Domain system that ProtectPoint supports.

l IP connectivity to the Data Domain systems on TCP port 3009. l DD Boost service is enabled and then a storage unit is created.

l Block services for ProtectPoint are enabled on the Data Domain 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 Data Domain Operating System Command Reference Guide provides more information about the block services for ProtectPoint and the vdisk commands that control them.

The following topics provide more details about the block services prerequisites. l The Data Domain file system (DDFS) stores the block services for ProtectPoint

(21)

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

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

The Data Domain Operating System Administration Guide provides more information about the DDFS.

DD Boost prerequisites

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

l 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 4 Block services for ProtectPoint object hierarchy mappings

Storage object Mapping level

Pool Department Device group Application Device Device

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

Data Domain storage layout

The following figure displays the storage layout of the Data Domain File System (DDFS).

(22)

Figure 2 DDFS storage layout

In this figure the numbers represent the following: 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 5 DDFS storage elements

DDFS directory Description

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

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

/data/col1/backup 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. /data/col1/MTree<X> 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

(23)

Block services also provide additional functionality, such as creating static images (snapshots) and replicating data.

The Data Domain Operating System Command Reference Guide provides more

information about the block services for ProtectPoint and the vdisk commands that control them.

Data Domain file system

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.

Note

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

The Data Domain Operating System Administration Guide provides more information about the DDFS.

Discovering device geometry

You will need the geometry of any existing primary storage devices.

For VMAX arrays, Encapsulate Data Domain devices on the VMAX array on page 27 provides instructions on identifying the VMAX device geometry and mapping it to the required geometry for Data Domain devices.

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 an immediate effect on copies in progress:

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

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

(24)

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

symqos -sid <SymmID> -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.

Provision FAST.X restore LUNs to the application recovery host

Provision FAST.X LUNs on the VMAX array for new installations. Before you begin

Ensure that Fibre Channel 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:

l Create a storage group.

l Add the devices to the storage group. l Create a port group.

l Add the front end ports to the port group where the server is zoned. l Create an initiator group.

l Add the initiator WWNs of the application recovery host to the initiator group. l Create a masking view.

l Discover newly provisioned LUNs on the application recovery host. Procedure

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

2. To view the existing VMAX devices, perform the following steps: a. To list the VMAX devices, type the following command:

symdev list -sid <SymmID>

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

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

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

(25)

<SymDevName>[, <SymDevName>[, <SymDevName>. . .]]

| <-g <DgName> [-std] [-bcv] [-vdev] [-tgt]> | <sg

<SgName> [, <SgName1>, <SgName2> . . . <SgNamen>]>

<-file <DeviceFileName> [src] [tgt]> [-reserve_id <ResvID> [, <ResvID> [, <ResvID>. . .] ] ] ]

For example:

symaccess -sid 0129 create -name group1 -type storage

Note

This storage group is different from the NsrSnapSG mentioned in the

Encapsulating secondary Data Domain system vdisk devices on VMAX section. 4. To add FAST.X devices to the storage group, type the following command:

symsg -sg <SgName> -sid <SymmID> [-i <Interval>] [-c

<Count>] add dev <SymDevNumber> For example:

symsg -sg group1 -sid 0129 add dev 0001A

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

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

For example:

symaccess -sid 0129 create -name group1 -type port

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

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

For example:

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

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

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

symaccess -sid <SymmID> create -name <GroupName> -type initiator [-wwn <wwn> | -iscsi <iscsi> | -file

(26)

<InitiatorFilename> | -ig <InitiatorGroupName>]

[-consistent_lun]

For example:

symaccess sid 0129 create name group1 type initiator -consistent_lun

Note

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

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

symaccess sid <SymmID> name <GroupName> type initiator -wwn <-wwn> | -iscsi <iscsi> | -ig <InitiatorGroupName> | -f

<InitiatorFilename> add For example:

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

Initiators can be added to an existing initiator group by specifying the initiator type (-wwn or -iscsi), the initiator group name, or by using an input file. 9. To create a masking view, type the following command:

symaccess create view -sid <SymmID> -name <ViewName> -sg

<StorageGroupName> -pg <PortGroupName> -ig

<InitiatorGroupName> [-reserve_id <ResvID> [, <ResvID>[, <ResvID>...] ] ] [-lun addr] [-ckd] [-celerra] [-rp] For example:

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

After you put the storage group, the port group, and the initiator group in 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, type the following command:

(27)

Encapsulate 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:

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

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

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

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

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

l On the Data Domain system, complete the following tasks: 1. Log in to an SSH session on the Data Domain system.

2. Enable block services for ProtectPoint if not already enabled. 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. l To complete the following steps on the VMAX array, use Solutions Enabler:

1. View the back end ports (DX ports) on the VMAX array and display the WWNs. 2. Display the LUNs that are visible for a specific WWN.

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

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

l Encapsulating an external LUN creates the VMAX LUN that enables access to the external LUN. Manually set the encapsulated LUN as the snapshot target.

(28)

Encapsulating the block services for ProtectPoint restore LUNs is required for restoration operations.

l 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 18 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, type 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.

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

vdisk enable

Note

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, type the following command:

vdisk status

(29)

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

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

For example:

user add user1 role none

Note

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

4. To create the block services for ProtectPoint device pool, type the following command:

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

For example:

vdisk pool create demo-1 user user1

To name device pools, use the guidelines in Block services for ProtectPoint object hierarchy on page 21.

5. To create the required number of block services for ProtectPoint device-groups within the device pool, type the following command:

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

For example:

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

To name device-groups, use the guidelines in Block services for ProtectPoint object hierarchy on page 21.

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, type the following commands:

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

symdev list -sid <SymmID>

(30)

For example:

symdev list -sid 0129

Symmetrix ID: 000196700129

Device Name Dir Device

--- --- Cap Sym Physical SA :P Config Attribute Sts (MB) --- --- ---00001 Not Visible ???:??? TDEV N/Grp'd ACLX RW 11 00002 Not Visible ???:??? TDEV N/Grp'd RW 6 00003 Not Visible ???:??? TDEV N/Grp'd RW 6 00004 Not Visible ???:??? TDEV N/Grp'd RW 6 …

(output truncated for display) …

00019 Not Visible ???:??? TDEV N/Grp'd RW 6 0001A Not Visible ???:??? TDEV N/Grp'd RW 23016 0001B Not Visible ???:??? TDEV N/Grp'd RW 23016 0001C Not Visible ???:??? TDEV N/Grp'd RW 23016 0001D Not Visible ???:??? TDEV N/Grp'd RW 23016 000A6 Not Visible ???:??? TDEV N/Grp'd RW 215719 000A7 Not Visible ???:??? TDEV N/Grp'd RW 215719 000A8 Not Visible ???:??? TDEV N/Grp'd RW 215719

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

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

For example:

symdev show 0001A -sid 0129

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

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

Table 6 VMAX to Data Domain device geometry mappings

VMAX device geometry value Equivalent Data Domain device geometry value

(31)

Table 6 VMAX to Data Domain device geometry mappings (continued)

VMAX device geometry value Equivalent Data Domain device geometry value

Tracks per cylinder Heads Cylinders 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, type the following command:

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

device-group <device-group-name>

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

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

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

vdisk pool show detailed pool <pool-name> vdisk device-group show detailed <group-name> vdisk device show detailed <device-name>

For example:

vdisk pool show detailed pool demo-1

vdisk device-group show detailed demo-devgrp vdisk device show detailed device-demo

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

scsitarget group create <group-name> service vdisk

(32)

For example:

scsitarget group create demo-accgrp service vdisk

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

vdisk group add <group-name> {device <device-spec> | pool

<pool-name>

device-group <device-group-name> [device <device-spec>]} [lun

<lun>]

[primary-endpoint {all | none | <endpoint-list>}] [secondary-endpoint {all | none | <endpoint-list>}]

For example:

vdisk group add demo-accgrp device vdisk-dev16

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

scsitarget initiator show list

Initiator System Address Group Service --- -- --- ---initiator-1 2a:10:00:21:88:00:82:74 n/a n/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.

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

scsitarget initiator rename <src-initiator-name>

<dst-initiator-name> For example:

scsitarget initiator rename initiator-1 vmax4d_3_08

(33)

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

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

For example:

vdisk group add demo-accgrp initiator symm_9h0

14. Switch to the VMAX environment.

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

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

For example:

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

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

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

For example:

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

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

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

symsg create <SgName>

For example:

symsg create storage-group-5

Note

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

(34)

18. To add the source VMAX devices to the storage group, type the following command:

symsg -g <DgName> add dev <device_ID>

For example:

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

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

l To encapsulate disks individually, type the following command:

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

For example:

symconfigure -sid 0129 -cmd "add external_disk, wwn=6002189000002DDB5D0525EEE8A00011,

encapsulate_data=yes;" commit -v -nop

It takes approximately seven minutes to encapsulate each device. l To encapsulate a group of devices, perform the following steps:

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

Note

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

b. On the application recovery host, to encapsulate the block services for ProtectPoint devices that are listed in the text file, type the following command:

symconfigure commit -f devs.txt

…

Establishing a configuration change session....Established. Processing symmetrix 000196700129

(35)

Initiating COMMIT of configuration changes...Queued. COMMIT requesting required resources...Obtained. Step 008 of 064 steps...Executing. … Step 091 of 214 steps...Executing. … Step 210 of 219 steps...Executing. Local: COMMIT...Done. New symdev: 0004C [DATA device]

New symdev: 000BA [TDEV]

Terminating the configuration change session...Done. The configuration change session has successfully

completed.

Note

The VMAX array returns a contiguous range of new device 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, type the following command:

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

For example:

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

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

symsnapvx -sid <SymmID> -sg <SgName> establish -name

<SnapshotName> For example:

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

Note

If additional devices or device groups are added to the ProtectPoint

environment after the initial configuration, this step must be repeated for the new devices or device groups.

(36)

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

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

For example:

symsnapvx sid 0129 sg storagegroup5 link copy -snapshot_name dg5-snap

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

Note

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, type the following command:

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

Note

If you must change the clone pace, start with a setting of 4. This value results 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, type the following command:

symsnapvx list -detail -sid <SymmID> {-sg <SgName> | -devs

<First DeviceInRange>:<LastDeviceInRange>} -linked For example:

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

25. If the environment is to use FAST.X restore operations, create a VMAX 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 file system agent or application agent configuration files.

(37)

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

symsg -sid <SymmID> create ProtectPointRestoreGroup

For example:

symsg -sid 0129 create ProtectPointRestoreGroup

Note

The storage group name is case-insensitive.

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

symsg -sid <SymmID> -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. Note

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 file system agent, type Ctrl + C in the terminal window to abort any backups in progress.

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

symdev list -lock

c. If required, to unlock the VMAX devices being deleted, type the following command:

symdev release -lock -nop -sid <SymmID>

(38)

For example:

symdev release -lock -nop -sid 0129

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

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

symdev -sid <SymmID> {-devs

<FirstDeviceInRange>:<LastDeviceInRange>} not_ready For example:

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

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

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

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

For example:

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

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

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

Gatekeepers

ProtectPoint requires Solutions Enabler to communicate to VMAX to control

ProtectPoint operations. Solutions Enabler requires VMAX gatekeeper devices to be configured. VMAX gatekeeper devices are small sized VMAX LUNs that act as the target of command requests to Enginuity based functionality. These commands arrive in the form of disk I/O requests. As more commands are issued in parallel from the host, and as the commands grow in complexity, more gatekeepers are required to handle the commands in a timely manner.

(39)

Provision gatekeepers example

Procedure

1. To list the available storage devices, type the following command:

symdev list -mb

2. If there are existing gatekeepers in the device list output, ProtectPoint automatically uses the existing gatekeepers, otherwise you must create gatekeepers, for example:

symconfigure -sid 531 -cmd "create gatekeeper count=8 ;" commit

3. For the application recovery host with the gatekeepers, create a masking view, for example:

#!/bin/bash

# To find HBA port WWNs run the following command: # cat /sys/class/fc_host/host?/port_name

set -x

export SYMCLI_SID=000196700531

symaccess -type storage -name mgmt_gk create devs 2D:31 # gatekeepers for management host

symaccess -type initiator -name mgmt_ig create symaccess -type initiator -name mgmt_ig add -wwn <hba1_port1_wwn>

symaccess -type initiator -name mgmt_ig add -wwn <hba2_port1_wwn>

symaccess -type port -name mgmt_pg create -dirport 1D:8,2D:8 symaccess create view -name mgmt_mv –sg mgmt_gk –ig mgmt_ig – pg mgmt_pg

Additional storage configuration

Optionally complete the following additional storage configuration tasks.

N_Port ID Virtualization

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:

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

l The virtual and physical ports have the same port properties and behave the same. l There may be m:1 relationships between the endpoints and the port, that is,

multiple endpoints can share the same physical port. Enabling NPIV enables the following features:

(40)

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

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

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

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

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

Enable N_Port ID Virtualization on a Data Domain system

Before you begin

The following conditions must be met:

l The Data Domain system must be running a supported version of Data Domain OS. l All ports must be connected to 4 Gb, 8 Gb, and 16 Gb Fibre Channel HBA and

SLIC.

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

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

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

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

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

l If port names are present in access groups, the port names are replaced with 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

(41)

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: l File System Agent Installation and Administration Guide

l Database Application Agent Installation and Administration Guide l Microsoft Application Installation Guide

(42)

(43)

CHAPTER 3 XtremIO Application Storage Configuration

Topics include:

l ProtectPoint for XtremIO overview... 44 l ProtectPoint for XtremIO components... 44 l ProtectPoint for XtremIO prerequisites... 45 l Configuring storage for ProtectPoint for XtremIO... 49 l Next steps...67

(44)

ProtectPoint for XtremIO overview

ProtectPoint for XtremIO is a physical hardware solution that integrates the primary storage on XtremIO and the protection storage on the Data Domain system.

ProtectPoint provides block movement of the data on application source LUNs to the Data Domain system.

ProtectPoint for XtremIO works with the features on the Data Domain system, the RecoverPoint appliance, and the XtremIO cluster to provide primary storage to Data Domain protection. ProtectPoint uses the following features:

l On the Data Domain system: n Block services for ProtectPoint n FastCopy

n DD Boost

l On the RecoverPoint appliance: n Catalog for RecoverPoint appliance n Consistency groups

l On the XtremIO cluster: n Snapshots

ProtectPoint for XtremIO enables an application administrator to leverage the ProtectPoint workflow to protect applications and application data. The storage administrator configures the underlying storage resources on the primary storage system and the Data Domain system. With this storage configuration information, RecoverPoint, and the ProtectPoint software, the application administrator can trigger the workflow to protect the application. Before triggering the workflow, the application administrator must quiesce the application to ensure that an application consistent snapshot will be preserved on the Data Domain system.

Note

The ProtectPoint database application agent works with the application to quiesce the application automatically.

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

For restoring data, ProtectPoint enables the application administrator to select a specific backup and make that backup available to the application host. With the file system agent, the operations to mask, mount, and restore the data must be performed manually on the primary storage system. The file system agent provides a copy of the data but not any application intelligence.

ProtectPoint for XtremIO components

A ProtectPoint for XtremIO solution consists of the following components: l Data Domain:

(45)

n Data Domain block services for ProtectPoint. n DD Boost.

n (Optional) Data Domain MTree replication. l RecoverPoint:

n A RecoverPoint cluster with two to eight RecoverPoint appliances. l XtremIO:

n An XtremIO cluster running storage array software. l Application:

n Application host.

n ProtectPoint agent on the application host. To view the supported versions of components, go to:

ProtectPoint for XtremIO prerequisites

The following are ProtectPoint for XtremIO prerequisites.

File system agent prerequisites

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

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

l (Optional) On the RecoverPoint appliance (RPA), create a user account. l The file system agent must be installed on the application host.

Database application agent and Microsoft application agent prerequisites

The database and Microsoft application agent prerequisites for ProtectPoint operations are as follows:

l A valid license for the ProtectPoint environment.

l The application agent must be installed on the production and recovery host. l User accounts for block services for ProtectPoint, and DD Boost must be created

on the Data Domain system.

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

RecoverPoint prerequisites

The RecoverPoint prerequisites for all ProtectPoint for XtremIO operations are as follows:

l A RecoverPoint backup (BK) license.

l A RecoverPoint cluster with RecoverPoint appliances, running RecoverPoint software.

l Port 443 must be open between the RecoverPoint appliances, the XtremIO Management System, and the XtremIO System-wide Management (SYM) module

Dell EMC ProtectPoint