RecoverPoint 5.1 Customer Installation and Upgrade Guide

Dell EMC RecoverPoint Version 5.1

Customer Installation and Upgrade Guide P/N 302-003-996 REV 01

Copyright © Dell Inc. or its subsidiaries subsidiaries All rights reserved. reserved. Published July 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 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. subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA.

Dell EMC Hopkinton, Massachusetts 01748-9103 1-508-435-1000 In North America 1-866-464-7381 www.DellEMC.com

2

RecoverPoint 5.1 Customer Installation Installation and Upgrade Upgrade Guide

CONTENTS

Tables

5

Preface

7

Chapter 1

Preparing for customer installation

9

SolVe Desktop.............................................................................................10 Verifying prerequisites......................................... ............................ ........... 10 Unpacking and racking RPAs............................. RPAs......................................................... ............................ .............. 11 Rear panel panel description.................................................................................12 Connecting Connecting RPAs.......................... RPAs...................................................... ............................ ............................. ..... 13 NTP server..................................................................................................14 server..................................................................................................14 Zoning.........................................................................................................15 Zoning.........................................................................................................15 LUN mapping..................................... ............................ ............................. 16 Multiple WWNs................................... ............................ ............................ 16

Chapter 2

Creating vRPAs

17

Deploying OVF template........................................... ............................ ...... 18

Chapter 3

Customer installation

21

Installing a new cluster.................................... ............................ ............... 22

Chapter 4

Connecting clusters

29

Connecting a cluster.................................. ............................. ................... 30

Chapter 5

Customer upgrade

33

Upgrading RPA software............................... ............................. ................ 34

Chapter 6

IP and SA SAN setup details templates

37

Requirements Requirements and recommendations..........................................................38 IP and SAN SAN setup details details for physical RPA clusters.................................... 38 IP and SAN SAN setup details for virtual RPA clusters.......................................39


3

CONTENTS

4


TABLES 1

vRPA performance profiles.................................... ..................................................... 18

RecoverPoint 5.1 Customer Installation and Upgrade Guide

5

TABLES

6


Preface

As part of an effort to improve its product lines, we periodically release revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. Contact your technical support professional if a product does not function properly or does not function as described in this document. Note

This document was accurate at publication time. Go to Online Support ( https:// support.emc.com) to ensure that you are using the latest version of this document. Purpose This document describes how to install RecoverPoint/SE, connect RPA clusters, and upgrade RPA software. Audience This document is intended for customers who need to perform RecoverPoint/SE operations using the Deployment Manager. Related documentation The following publications provide additional information: l

RecoverPoint Release Notes

l

RecoverPoint Deployment Manager Release Notes

l

RecoverPoint Customer Installation and Upgrade Guide

l

RecoverPoint Installation and Deployment Guide

l

RecoverPoint Product Guide

l

RecoverPoint Administrator's Guide

l

RecoverPoint CLI Reference Guide

l

RecoverPoint Performance Guide

l

RecoverPoint REST API Programming Guide

l

Recov erPoint Security C onfiguration Guide

l

RecoverPoint Simple Support Matrix

In addition to the core documents, we also provide White papers and Technical Notes on applications, arrays, and splitters. Typographical conventions This document uses the following style conventions: Bold

Used for names of interface elements, such as nam es of windows, dialog boxes, buttons, fields, tab names, key names, and menu paths (what the user specifically selects or clicks)

Italic

Used for full titles of publications referenced in text

Monospace

Used for:


7

Preface

Monospace italic Monospace bold

l

System code

l

System output, such as an error message or script

l

Pathnames, filenames, prompts, and syntax

l

Commands and options

Used for variables Used for user input

[]

Square brackets enclose optional values

|

Vertical bar indicates alternate selections - the bar means “or”

{}

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

...

Ellipses indicate nonessential information omitted from the example

Where to get help Technical support, product, and licensing information can be obtained as follows: For documentation, release notes, software updates, or information about products, go to Online Support at https://support.emc.com.

Go to Online Support and click Service Center. You will see several options for contacting Technical Support. Note that to open a service request, you must have a valid support agreement. Contact your sales representative for details about obtaining a valid support agreement or with questions about your account. Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to [email protected].

8


CHAPTER 1 Preparing for customer installation

The Deployment Manager is a tool that guides you in the deployment and upgrade of classic RecoverPoint systems. NOTICE

Do not use Deployment Manager to deploy RecoverPoint for Virtual Machines systems; instead use RecoverPoint for VMs Deployer.

l l l l l l l l l

SolVe Desktop .................................................................................................... 10 Verifying prerequisites ........................................................................................10 Unpacking and racking RPAs ...............................................................................11 Rear panel description ........................................................................................ 12 Connecting RPAs................................................................................................13 NTP server ......................................................................................................... 14 Zoning................................................................................................................ 15 LUN mapping......................................................................................................16 Multiple WWNs ...................................................................................................16


9


SolVe Desktop Customer procedures on SolVe Desktop are now customer viewable. SolVe Desktop gathers critical information from existing content to generate a concise procedural document. To download and authorize:

1. Go to online support: https://support.emc.com/. 2. Search for SolVe Desktop. 3. Click the executable and download. 4. Follow the prompts to install. 5. Accept the End User License Agreement. 6. Click Not yet authorized for content. 7. Click Authorize and download list of available products . 8. Click OK. 9. Click OPEN. 10. Open the SolVe Desktop (Start > All Programs > EMC SolVe Desktop > EMC SolVe Desktop) and click the RecoverPoint icon to update or install the content.

For feedback and questions, send an email to: mailto:%[email protected].

Verifying prerequisites 1. Download the RecoverPoint Customer Installation Kit: a. At https://support.emc.com, select Downloads. b. In the Type a Product Name field, enter RecoverPoint SE. c. Click RecoverPoint Customer Installation Kit to download it. 2. Collect the infrastructure data in "IP & SAN Setup Details Templates" (Appendix A). 3. Ensure the following items are available: Type of RPA

Required items

Physical

Two Ethernet cables per RPA (one for LAN and one for WAN) At least four available dedicated storage ports on the storage array A dedicated resource pool mapped to each RPA cluster for automatic repository volume provisioning Fibre Channel cables: l

10

For dual fabric topology: two cables per RPA



Type of RPA

Required items l

Virtual

For direct attach topology: four cables per RPA

Four Ethernet cables per ESX server (LAN, WAN, iSCSI1, iSCSI2) At least four available dedicated iSCSI ports on the storage array

4. Ensure that you have a dedicated computer running Windows workstation with Java™ 8 (or later), 32-bit. 5. Ensure that your workstation can communicate with the management (LAN) networks for the RPAs at both sites. If communication from the workstation to both sites is not possible, you can perform the deployment independently at each site. 6. Ensure that TCP ports 21, 22, 8081, and 8082 are open on your workstation. To enable log retrieval from the array-based splitter, ensure that TCP port 443 (HTTPS) is open to each storage array. To verify that these ports are open, you can use Telnet: telnet 7. Verify that the VNX splitter is active: a. In Unisphere for VNX, right-click the storage array, and select Properties. b. In the Storage System Properties dialog box, select the Software tab. c. Verify that the status of the RecoverPointSplitter is installed. d. If it is not installed, refer to the "RecoverPoint VNX Splitter Activation Procedure," which is included in your RecoverPoint Customer Installation Kit.

Unpacking and racking RPAs Use these instructions to unpack RPAs and install them in their racks.

Verify that each RPA package contains: l

1 RecoverPoint Appliance

l

1 standard rackmount kit

l

1 bezel

l

2 country-specific power cables

If items are missing from the package, promptly notify customer support.

1. From https://support.emc.com, obtain the hardware guide for the RPAs: RPA version

Hardware guide

Gen6

RecoverPoint Gen6 Hardware Guide

Ensure that you complete the instructions in this guide, including these topics:

Unpacking and racking RPAs

11


RPA version

Hardware guide l

See "Rear panel description" for location and descriptions of modules, ports, and indicators.

l

Complete steps in "Preparing the Gen6 appliance for first use."

l

Observe practices described in "Configuring network connections."

Gen5

SRV-I1U-1208 Server Installation and Maintenance Guide

Gen4

SRV-D1U-R610 Installation and Replacement Guide

2. Install all RPAs in cabinet before proceeding to "Connecting RPAs."

Rear panel description This section describes the rear panel controls and indicators Rear panel view A

B C D E

N M

G

F

H

I

J

K

L

Item

Control/Indicator/Port

Purpose

A

1 Gbe BMC Management

Dedicated BMC service port

B

1 Gbe/NCSI port #3

1000Base T network port

C

1 Gbe/NCSI port #1


D

USB 2.0 port

USB port

E

Dual-stacked DB-9 ports

COM 1 (top), COM 2 (lower)

F

Reset/Power Button

The Reset/Power button has the following function: 1) System is off: l

Action: Any duration button press

l

Result: System powers on

2) System is on:

G

12

I/O Module, Slot 0


l

Action: Short button press (less than 10 seconds).

l

Result: System reset.

l

Action: Long power button press (longer than 10 seconds)

l

Result: System powers off

Houses I/O module


Item

Control/Indicator/Port

Purpose

H

I/O Module, Slot 1

Houses I/O module

I

Power supply 0

Supplies power to a CPU module and system components

J

Power supply LEDs

(top to bottom)

K

Power supply 1

L

I/O module power/service LED

l

AC power good (green)

l

DC power good (green)

l

Fault (amber)

Supplies power to a CPU module and system components l

Green (good)

l

Amber (fault)

M

1 Gbe/NCSI port #0


N

1 Gbe/NCSI port #2


SP system LEDs Top to bottom: l

Do not remove - White

l

System power applied - Blue

l

SP service - Blue (good)/Amber (fault)

Connecting RPAs 1. Connect the RPA Fibre Channel ports.

Connect one RPA Fibre Channel port to Fabric A and a different RPA Fibre Channel port to Fabric B on each RPA. For example, connect odd-numbered RPA ports (1, 3) to Fabric A and even-numbered ports (0, 2) to Fabric B. Note

In a quad-fabric topology, connect each port to a different fabric. Connect one RPA Fibre Channel port to Storage Processor A, and a different RPA Fibre Channel port to Storage Processor B. Connect the remaining RPA Fibre Channel ports to the other RPA in the cluster. A RecoverPoint cluster can support up to two Xbricks. The RecoverPoint cluster must have exactly two RPAs. Every RPA must be connected to all storage controllers.

Connecting RPAs

13


NOTICE

A dual fabric configuration is required at all clusters for RPA, host, and storage connectivity. 2. For each RPA, connect an Ethernet cable from the: a. Management (LAN) interface to the eth1 port. b. WAN to eth0 port. 3. Connect a country-specific electrical power cable to each of the two power plugs on each RPA. 4. Connect each RPA to a monitor and keyboard or via a KVM. If these options are not available (Gen6 does not support KVM and does not have a VGA port), use one of the following options:

Attach an external computer using a console cable to the RPA serial port. Attach an external computer using an Ethernet crossover cable to the RPA WAN port. 5. Power on the RPA. The following prompt appears: localhost.localdomain login: Password:

If the login prompt does not appear, press Enter until it does. 6. Log in to the RPA using boxmgmt credentials. You are prompted for a temporary subnet, and gateway IP addresses. If DHCP is configured for all RPAs in the cluster, these IP addresses are optional. When the configuration is completed, the boxmgmt main menu appears. The IP addresses you assigned are used throughout the deployment process. Verify that a single workstation can access all IP addresses assigned to RPAs at all clusters. As an alternative, you may install one site at a time, in which case, it is necessary only to be able to reach the RPAs of one cluster at a time. Java™ 8 is required on the workstation that is running the installation wizard. It is recommended to have the latest version of Java installed.

NTP server Network Time Protocol (NTP) synchronizes the clocks across all of the machines that are attached to a particular installation. Best practice is to configure an external NTP server, running on Linux machines, before RecoverPoint installation. When an external NTP server is configured at a site, the first RPA in a cluster at that site synchronizes to the external NTP server. All other RPAs in all clusters of the 14



RecoverPoint system synchronize to the first RPA. To increase the accuracy of the time, you may type secondary external NTP server addresses. Best practice is that the first RPA you install is one of the RPAs at the site at which the NTP server is configured. Designate this RPA as RPA 1 in this cluster. If you are not using an external NTP server, the first RPA that you install at site 1, RPA 1, uses its internal clock as an NTP server. This RPA serves as the NTP server for all RPAs in the system. In this scenario, although all RPAs in the installation are internally synchronized, they may not necessarily keep correct time.

Zoning Zoning must adhere to the guidelines.

Best practice is to use the RPA HBA ports as both initiators and targets. If you must zone RPA HBA ports separately either in the initiator zone or in the target zone, you observe only minor differences in performance and availability. However, initiator-target separation is not supported when: l

Mixing different splitter types in the same site

l

Using remote replication over Fibre C hannel

l

Using distributed consistency groups

The best practice is to zone RPA Fibre Channel ports in the same zone. In some configurations, it is required.

Every server must be able to access its production storage. In most installations, these zones exist as part of the SAN implementation. Confirm that these zones exist. Single-initiator zoning is required.

RecoverPoint - All RPA ports in a fabric must be zoned with all storage ports that are available for RecoverPoint replication. The best practice is always to use only one zone per fabric RPAs and storage. This practice applies to all splitters. RecoverPoint with Unity, VNXe, or VNX using SE licenses - On each fabric, there should be a zone for each RPA, which includes: l

One HBA port of that RPA

l

One port for each Unity/VNX/VNXe storage processor (SP A and SP B)

RecoverPoint with XtremIO - Create one zone per fabric and include all RPA Fibre Channel ports and all XtremIO Storage Controller ports in that fabric.

Distributed consistency groups require that all RPA Fibre Channel ports in the fabric can communicate with each other. All RPA ports in a fabric must be in one zone. Normally, the RPA-to-storage zone satisfies this requirement.

Create one zone per fabric that includes all of the site 1 RPA ports together with all of the site 2 RPA ports. Zoning

15


Best practice is not to share Unity/VNXe/VNX ports between array-based replication technologies and RecoverPoint. For Unity/VNXe/VNX splitters, not sharing ports between array-based replication technologies and RecoverPoint is required. Array-based replication technologies should be excluded from RecoverPoint zones.

LUN mapping RecoverPoint operation requires proper LUN mapping at each site. Production and replica volumes must be exposed to all relevant hosts (all hosts that write to the volume) and all RPA ports in the fabric. l

l

Repository and all journal volumes must be exposed to all RPA ports in the fabric. For LUN mapping instructions when using a specific splitter, refer to the Technical Notes for that splitter. NOTICE

RecoverPoint supports the mixing of splitters within an RPA cluster at a site, and the mixing of storage systems with which RPA clusters are deployed within the same RecoverPoint system, subject to certain limitations. Refer to the relevant RecoverPoint Release Notes . l

LUN mapping should be done during RecoverPoint installation. The best practice is to avoid changing the LUN mapping after installation. If changes must be made later, follow the instructions in the RecoverPoint Changing LUN Mapping Technical Notes .

Multiple WWNs In some configurations, you can use virtual ports to enable an RPA to belong to several storage groups simultaneously. The menu option for configuring this feature is located in the boxmgmt menus under Setup > Modify settings.

16


CHAPTER 2 Creating vRPAs

Virtual RPAs (vRPAs) can be deployed on RecoverPoint. If you are creating vRPAs, deploy the OVF template. l

Deploying OVF template ..................................................................................... 18

Creating vRPAs

17

Creating vRPAs

Deploying OVF template l

l

l

l

If possible, all vRPAs should be on separate ESXi servers. Minimally, vRPA 1 and 2 must be on separate ESXi servers. Ensure that you are running supported versions of VMware vCenter and vSphere. See the RecoverPoint for Virtual Machines Simple Support Matrix at https:// support.emc.com. Ensure that you have a copy of the RecoverPoint OVA file. This file is included in the installation package. Assign enough resources (CPU, memory, disk) for the virtual system based on performance requirements: vRPA performance profiles

vRPA Less than 256 VMs performance Low performance profile

256+ VMs Low performance

256+ VMs Medium performance

256+ VMs High performance

Virtual CPUs

2

2

4

8

RAM

4 GB

8 GB

8 GB

8 GB

35 GB

35 GB

35 GB

VMDK capacity 35 GB

When using 4CPU/8GB or 8CPU/8GB configurations to run vRPA, the best practice is to reserve all RAM for RecoverPoint.

1. In the vSphere Web Client, right-click an ESXi host and select Deploy OVF Template.... 2. In the Select source screen, specify the vRPA OVF package location. 3. In the Review details screen, review the general properties of the OVF template. To accept, click Next. 4. In the Accept License Agreements screen, if you accept the terms of the EndUser License Agreement, click Accept and Next. 5. In the Select name and folder screen, type a name for this vRPA and select a folder or data center. If you type the name of an existing vRPA, you are not permitted to continue. 6. In the Select configuration screen, select the desired vRPA performance profile. 7. If prompted to select a resource, in the Select a resource screen, select a cluster, host, or resource pool. 8. In the Select storage screen, select a disk format, storage policy, and highperformance data store (best practice) to host the vRPA virtual machine files. All ESXi hosts in the cluster where the vRPAs reside must share the data store where the repository VMDK resides. 9. In the Setup networks screen, select a destination network for the RecoverPoint Management Network, and select an IP protocol. 18


Creating vRPAs

10. In the Customize template screen, type these vRPA LAN settings: IP address, subnet mask, and gateway. Follow instructions on the screen for using DHCP or static IP addresses depending on the network adapter topology. 11. The Ready to Complete screen summarizes all the selections. Select Power on after deployment. To create the vRPA, click Finish. The Deploying vRPA screen appears, showing the progress. 12. To create additional vRPAs, repeat this procedure.

When the vRPA is created, the vRPA Summary tab shows the vRPA package contents as specified. The selected IP policy is implemented automatically when the vRPA is powered on.

Deploying OVF template

19

Creating vRPAs

20


CHAPTER 3 Customer installation

This chapter contains these topics: l

Installing a new cluster .......................................................................................22


21


Installing a new cluster Customers may use this procedure to install RecoverPoint on an RPA cluster, physical or virtual. This wizard installs RecoverPoint with Unity, VNXe, or VNX arrays and a RecoverPoint/SE license. These RecoverPoint systems can contain one or two clusters. The Installer wizard installs one cluster at a time. Run again to install a second cluster. RecoverPoint/EX and /CL licenses support systems with more than two clusters. Contact customer support to arrange installation by support personnel.

1. Ensure that you have the latest version of the RecoverPoint_DM.exe application file. Launch Deployment Manager by opening RecoverPoint_DM.exe . Follow instructions on screen. 2. Select the RecoverPoint version to install. 3. On the login screen, select Customer installation and click Login. 4. On the RecoverPoint Deployment Manager wizard screen, select RecoverPoint with VNX Installer or RecoverPoint with Unity/VNXe Installer. 5. On the Prerequisites screen, if any of the conditions are not fulfilled, close the wizard, fulfill the conditions, and run the wizard again. 6. On the Configuration file screen, select an installation mode:

Create a new installation configuration file

To save your settings to a file in case you need to repeat this installation. By default, the file name and directory location is C: \Users\\RecoverPoint \RPSE_config.properties . File name cannot contain the following characters: \/ *?“:<>|

Create or continue an installation from a saved configuration file

If you previously saved a configuration file, to load the saved settings as defaults for this installation.

7. On the Environment settings screen, specify the settings.

Select WAN and LAN traffic on separate network adapters (default) or on the same network adapter. l

l

l

22

RecoverPoint 5.0 and later supports more than one network traffic type on a network adapter. The network adapter topology must be the same for every RPA in the cluster and for every cluster in the RecoverPoint system. To modify an existing network adapter topology, change it for every RPA in every cluster in the RecoverPoint system. To change, detach



the RPA, use boxmgmt to change the network adapter topology, and reattach the RPA to the cluster. Repeat for all RPAs in all clusters.

l

l

l

l

If the WAN and LAN are on the same network adapter, they may be on the same subnet. If the WAN and LAN are on different network adapters, they must be different subnets. All WAN interfaces in a cluster must reside on the same subnet. All LAN interfaces and the cluster IP address in a cluster must reside on the same subnet.

IP type must be the same for all clusters.

Default value is 1500 (do not modify unless instructed to do so).

The cluster domain name is optional. 8. On the RPA discovery screen, select discovery options. 9. On the IP and connectivity settings screen, specify IP and connectivity settings. RecoverPoint 5.0 and later allows you to select Dynamic Host Configuration Protocol (DHCP) to assign IP addresses to RPAs. When IP addresses are provided by DHCP and an RPA reboots, the RPA will acquire a new IP address from the DHCP server. If the DHCP server is not available, the RPA will not be able to return to the operational state; therefore it is recommended to supply redundant, high-available DHCP servers in the network when using the DHCP option. If both control RPAs in the cluster reboot and are assigned new IP addresses, operations cannot resume unless the repository is available. Click Add route to add additional gateways. 10. On the Login credentials screen, enter the RecoverPoint boxmgmt login credentials. 11. When all statuses appear OK (green check mark), click Next to continue. You must resolve any error on the Connectivity results screen before you can proceed. When ready, click Retry. 12. The Cluster iSCSI settings screen appears only if you are replicating virtual machines. On the storage array, register the IQNs of both initiators of each vRPA. Map LUNs to the IQNs of the vRPAs that need to access those LUNs. 13. On the Cluster iSCSI settings screen, select the network adapter topology for iSCSI traffic.

Installing a new cluster

23


NOTICE

If the RecoverPoint iSCSI traffic is on a different network adapter from the LAN and WAN, it is recommended to put the iSCSI traffic on a different subnet from the LAN and WAN, to avoid iSCSI communication errors. 14. Also on the Cluster iSCSI settings screen, enter the iSCSI settings for RPAs. MTU — Default value is 1500 (do not modify unless instructed to do so). If replicating midrange storage volumes over iSCSI, select the Configure CHAP credentials for the RPAs iSCSI ports checkbox and enter the CHAP credentials. 15. The RPA iSCSI ports screen appears only if you are replicating virtual machines. Follow instructions on screen.

Cannot be modified.

To add additional gateways. 16. On the EMC Online Support credentials screen, select how to obtain the RecoverPoint software and Installation Change Management information:

Enter EMC Online Support login credentials.

Select Use an offline Change Management XML file and browse to a local version of the file. To obtain an upto-date XML file for offline installation, browse to https://rplicense.emc.com/download. This page provides an option to download or email the a-cca.xml file. If this option is not available, open an Upgrade Service Request with customer support (severity level 3). In the request, ask for the latest Upgrade Change Management XML file for the RecoverPoint Deployment Manager, and indicate the intended date of the upgrade. The file will be provided within one (1) business day. The file must be u sed within 30 days. 17. On the Update RecoverPoint Release screen, select an option. If you select Update with an ISO image available locally , select the download source on the ISO file information screen. 18. On the Installation Change Management procedures screen, follow the instructions. 19. The Apply Configuration results screen shows the installation progress on each RPA. When installation has completed, press Next. 20. On the Security configuration screen, select the RPA communication security level for communication between RPAs and RPA clusters.

24



Not authenticated, not encrypted

Communication between RPAs is not authenticated nor encrypted.

Authenticated and encrypted

RPAs use certificates to authenticate each other before communicating, and all communication between RPAs is encrypted.

21. On the Security configuration screen, select the Local users' security level.

Basic

Minimum five characters.

High

Minimum eight characters, including two lower case, two upper case, and two non-alphabetical (digits or special characters). Change passwords immediately.

22. If deploying with VNX storage, the Storage Registration screen appears. Follow instructions on screen.

Select whether the scope of the user account is Global, Local, or LDAP. Default value is Global. For authentication within the local security directory, specify Global or Local scope. 23. If deploying with VNX storage, the Storage connectivity screen appears. Resolve any errors that are detected, and click Refresh. 24. If deploying with VNX storage, The VNX/CLARiiON Zoning screen appears only if you are using physical RPAs. Select an option.

Automatic

Only for: Cisco fabric switches with an active zoneset or Brocade (Connectrix B-Series) fabric switches running FOS 6.0 and higher with an active zone configuration. A Telnet connection to Cisco and Brocade switches is mandatory. Enter the required information. The system creates an RPA-tostorage zone for each new RPA at the site, where each zone includes:

Semiautomatic

l

One HBA port of that RPA

l

One port for each midrange storage processor

Only for Brocade and Cisco fabric switches. Enter the required information. The RPA creates a script that can be used to create the zoning. To export the script, click Export to clipboard. Paste the script into the CLI of the fabric switch.


25


Manual

Zone and map LUNs using the RPA port WWNs displayed in the RPA WWNs tables and the midrange storage array port WWNs displayed in the Array table. To create RPA-to-storage zones: a. On each fabric, create a zone for each RPA, which includes: l

l

One RecoverPoint Fibre Channel port of that RPA. If the RecoverPoint FC port has virtual WWNs, include all of them in the zone. One port for each VNX storage processor.

b. Add the new RPAs to the RPA-to-RPA zone containing all local RPA FC ports that are not used in RPA-to-storage zones (best practice). Directattach Storage

Select this option if each RPA is directly connected to SP A and SP B of the midrange storage array.

For manual zoning, use the following example for r eference.

Storage Port (SPA): [pwwn 50:06:01:64:3d:e0:0a:99] Storage Port (SPB): [pwwn 50:06:01:6c:3d:e0:0a:99] RPA 1, Port 0: [pwwn 50:01:24:82:00:92:4a:86] RPA 2, Port 2: [pwwn 50:01:24:82:00:89:9a:c2]

Storage Port (SPA): [pwwn 50:06:01:65:3d:e0:0a:99] Storage Port (SPB): [pwwn 50:06:01:6d:3d:e0:0a:99] RPA 1, Port 2: [pwwn 50:01:24:82:01:b2:4a:86] RPA2, Port 0: [pwwn 50:01:24:82:01:a9:9a:c2]

Zoning: RPA 1, Port 0 to Storage Port (SPA, SPB): zone name RP_London_0_0 vsan 25 [pwwn 50:01:24:82:00:92:4a:86] [pwwn 50:06:01:64:3d:e0:0a:99] [pwwn 50:06:01:6c:3d:e0:0a:99] RPA2, Port 2 to Storage Port (SPA, SPB): zone name RP_ London _1_0 vsan 25 [pwwn 50:01:24:82:00:89:9a:c2] [pwwn 50:06:01:64:3d:e0:0a:99] [pwwn 50:06:01:6c:3d:e0:0a:99] RPA 1, Port 0 to RPA2, Port 2: zone name RP_London_COMMON_0 vsan 25 [pwwn 50:01:24:82:00:89:9a:c2] [pwwn 50:01:24:82:00:92:4a:86]

Zoning: RPA 1, Port 2 to Storage Port (SPA, SPB): zone name RP_ London _0_0 vsan 55 [pwwn 50:01:24:82:01:b2:4a:86] [pwwn 50:06:01:65:3d:e0:0a:99] [pwwn 50:06:01:6d:3d:e0:0a:99] RPA2, Port 0 to Storage Port (SPA, SPB): zone name RP_ London _1_0 vsan 55 [pwwn 50:01:24:82:01:a9:9a:c2] [pwwn 50:06:01:65:3d:e0:0a:99] [pwwn 50:06:01:6d:3d:e0:0a:99] RPA 1, Port 2 to RPA2, Port 0: zone name RP_London_COMMON_0 vsan 55 [pwwn 50:01:24:82:01:b2:4a:86] [pwwn 50:01:24:82:01:a9:9a:c2]

25. If deploying with Unity or VNXe storage, the Storage configuration - Zoning and LUN masking screen appears. To save this information, click Export to CSV file. 26. On the SAN diagnostics screen, resolve any errors that are detected. Then, click Refresh. It is recommended to resolve all SAN discovery warnings. 27. If deploying with VNX storage, on the Select repository option screen, select an option.

26



Automatic In step 28 on page 27, you will select a resource pool. Minimum size of a repository volume automatically provisioned is 5.72 GB. Manual

In step 28 on page 27, you will select a LUN. Minimum size is 2.86 GB.

28. On the Repository volume screen, select a resource pool or LUN. NOTICE

l

The RPA formats the repository volume. Ensure that the LUN is new and does not contain any valuable data.

l

The repository volume must be highly available.

l

Capacity beyond 5.72 GB (automatic) or 2.86 GB (manual) is not used. Configure a repository volume on Unity or VNXe storage manually.

l

The repository volume may be provisioned on a thin or non-thin LUN.

l

The repository volume must be accessible to all RPAs in the cluster.

29. On the Apply storage configuration screen, resolve any errors that are detected. You may click on an error for more details. When all errors are resolved, click Retry. If there are errors that you are unable to resolve, contact customer support.

Install a second cluster

Repeat this procedure.

Connect two clusters

Proceed to the Connect Cluster wizard.

To begin local replication (on a single cluster)

Use the link on the Summary screen to open Unisphere for RecoverPoint management GUI.


27


28


CHAPTER 4 Connecting clusters


Connecting a cluster .......................................................................................... 30

Connecting clusters

29

Connecting clusters

Connecting a cluster Use this procedure to connect a new RecoverPoint cluster to an existing RecoverPoint system. The computer running the Connect Cluster Wizard must communicate with all the cluster management IP addresses. Both clusters in the system must have the same supported storage type and the RecoverPoint/SE license.

1. Launch Deployment Manager by opening the RecoverPoint_DM.exe application file. 2. On the RecoverPoint Deployment Manager Wizard screen, select the Connect Cluster wizard. 3. On the Connect Cluster Wizard screen, select the Prepare new cluster for connection option. 4. On the Prerequisites screen, if any of the conditions are not fulfilled, close the wizard, fulfill the conditions, and run the wizard again. 5. On the New cluster login credentials screen, enter boxmgmt credentials for the new cluster. 6. On the Connect Now or Later screen, select the Connect the new cluster to an existing RecoverPoint system option. Do not install a license in, or modify the settings of, the new cluster before connecting it to the existing system. 7. In the Existing cluster login credentials screen, enter the cluster management IP address and boxmgmt credentials of the existing cluster. 8. (Optional) On the Cluster connection settings screen, add a WAN gateway for additional network connectivity between RPA clusters, if required. 9. The Additional cluster connections screen appears if the system you are connecting to contains more than one RPA cluster. The added cluster receives the security settings of the existing cluster. 10. When the Summary screen appears, you have completed the connection of the new cluster, and you can start using Unisphere for RecoverPoint.

After installing a RecoverPoint system, you must complete the RecoverPoint PostDeployment Form and send it to the Install Base (IB) group to register your RecoverPoint system. If you are installing RecoverPoint 4.1 or later, and you have external connectivity, you can perform this process automatically, using the Unisphere for RecoverPoint Getting Started wizard or Admin > Register RecoverPoint screen. See the RecoverPoint Administrator’s Guide for further instruction on how to automatically fill out the PostDeployment form and send it to the IB group. If you are installing a RecoverPoint version prior to 4.1 or are installing a RecoverPoint version later than 4.1 without connectivity: 1. Download the form from online support at https://support.emc.com. In the online support site: a. Click Support by Product. 30


Connecting clusters

b. Type RecoverPoint CL in the Find a Product search field. c. On the RecoverPoint CL page, click Documentation. d. Download the form from the list of documents. 2. Fill out the form. 3. Send the form to the IB group: l

l

Customers and partners: Email the post-deployment form to the Install Base group at [email protected]. Employees: n

n

(Preferred) Use the IB Portal at http://emc.force.com/BusinessServices. Call in the information to the Install Base group at 1-866-436-2411 – Monday to Friday (regular Eastern Time Zone working hours).

You are now ready to install your RecoverPoint/SE licenses, enable support, and register RecoverPoint. Refer to the RecoverPoint Administrator’s Guide for instructions.

Connecting a cluster

31

Connecting clusters

32


CHAPTER 5 Customer upgrade


Upgrading RPA software ....................................................................................34

Customer upgrade

33

Customer upgrade

Upgrading RPA software Use this procedure to upgrade the RPA software. l

l

When upgrading the RecoverPoint system, do not try to upgrade multiple connected clusters simultaneously. This scenario is not supported. Upgrade connected RPA clusters sequentially until they have been upgraded to the same release. Upgrades are performed in one of the following ways: n

n

l

l

l

l

l

By Customer Support and authorized partners, who must open an Update Service Request and begin the RecoverPoint Change Control Activity (CCA) process, which is required for all upgrades. By customers who are performing their own upgrades of RecoverPoint/SE or RecoverPoint with Unity/VNXe/VNX. Download the RecoverPoint Customer Upgrade Kit, available on the “RecoverPoint SE” product page on online support.

The Upgrade Cluster wizard upgrades a cluster to the next major version. Repeat the upgrade for each connected cluster until all the clusters have been upgraded to the next release. If you want to upgrade the clusters through two releases, repeat this process again. You cannot run a RecoverPoint system with clusters that are more than one major version apart. Best practice is to upgrade splitters to the same RecoverPoint release as the software. To upgrade RecoverPoint splitters, refer to Technical Notes of the splitter. Completing the upgrade procedure may take several hours, depending on the ISO file version, network speed, and size of environment being upgraded. The Upgrade Cluster Wizard supports auto-recovery. If a step fails, run the wizard again. It continues from the failed step. Some failures may require manual intervention before rerunning the wizard. Logs of operations are stored in the following locations: n

n

n

n

Prepare for Upgrade logs are named and found in: / logs/ndu_prepare.log Apply/Resume Upgrade logs are named and found in: / logs/ndu_apply.log Previously run wizard logs (Prepare and Apply [or Resume]) are found in: /oldlogs/*.log Current account settings (such as licensing information) are saved to a CLI script file before the upgrade is applied. This file can be used to recreate the system configuration. The file is named and found in: / logs/account_settings.cli

1. Launch Deployment Manager by opening the RecoverPoint_DM.exe application file. Follow instructions onscreen. For support personnel who want to u se the Customer Upgrade Wizard, it is best practice to select Other operations (EMC personnel), and log in with the RecoverPoint login credentials. 2. On the login screen, select: 34


Customer upgrade

For RecoverPoint with Unity, VNXe or VNX customers who have elected to perform an upgrade on their own. All other upgrades

3. On the Select upgrade screen, select Prepare for upgrade. 4. On the Prepare for upgrade screen, if any of the conditions are not fulfilled, close the wizard, fulfill the conditions, and run the wizard again. 5. On the Login credentials screen, follow instructions. 6. On the Login credentials summary screen, correct any errors before proceeding. 7. On the Update RecoverPoint release screen, follow instructions. 8. If the Image settings screen appears, follow instructions. 9. On the ISO file distribution summary screen, after the ISO has been distributed to all RPAs, click Next. 10. On the System diagnostics screen, if errors or warnings are detected, resolve them and click Refresh to rerun diagnostics. 11. On the Save system files screen, specify where to save the configuration file. If system modifications are found, they are saved to a file. Continue according to system modifications:

Select Apply upgrade now and click Next. Submit the file in an Upgrade Service Request to Customer Support. When you receive a response from Customer Support, go to the Apply upgrade configuration screen. 12. On the Apply upgrade configuration screen, follow instructions. 13. On the Cluster diagnostics screen, if errors or warnings are detected, resolve them and click Refresh. 14. If the upgrade fails, follow instructions on the Collect system information screen. Submit the files to Customer Support. To improve response time, collect and save the Deployment Manager logs (found in /logs) to the FTP server.

1. Verify that splitters, RPAs, and volumes are functioning correctly and consistency groups are running on the same RPAs as before. 2. Configure system reports. Refer to the RecoverPoint Administrator’s Guide . 3. Register RecoverPoint. Refer to the RecoverPoint Administrator’s Guide .

Upgrading RPA software

35

Customer upgrade

36


CHAPTER 6 IP and SAN setup details templates

This chapter contains these topics: l l l

Requirements and recommendations................................................................. 38 IP and SAN setup details for physical RPA clusters ............................................38 IP and SAN setup details for virtual RPA clusters .............................................. 39

IP and SAN setup details templates

37


Requirements and recommendations As you complete the information requested in, observe these requirements and recommendations: l

l

l

l

A RecoverPoint installation requires at least two designated IP addresses per RecoverPoint appliance, one for Management (LAN) and the other for WAN, for physical and virtual RPAs. Two additional IP addresses are required for iSCSI for each virtual RPA. Finally, an additional floating IP is required per cluster, for use by one of the RPAs for management activities. When replicating over Fibre Channel, WAN IPs are not mandatory, but recommended to enable intra-cluster RPA communication. A RecoverPoint installation requires Management (LAN) and WAN default gateways and subnet masks. Use of NTP, DNS, SMTP, and SNMP services, is optional.

IP and SAN setup details for physical RPA clusters Entity

IP and SAN details Cluster #1 Cluster Name Time Zone Local Domain Primary DNS Server (optional) Secondary DNS Server (optional) NTP Server (optional but recommended) Cluster Management IPv4 Management Default Gateway IPv4 Management Subnet Mask IPv4 WAN Default Gateway WAN Subnet Mask SMTP (optional)

RPA 1

RPA Management IP RPA WAN IP

RPA 2


38


Cluster #2


Entity

IP and SAN details Cluster #1

RPA 3

RPA Management IP

Cluster #2

RPA WAN IP RPA 4


RPA 5


RPA 6


RPA 7


RPA 8


Array SPA

Array SPA Mgmt IP

Array SPB

Array SPB Mgmt IP

Fabric A

Switch IP Address

Fabric B

Switch IP Address

Fabric A

SPA Storage port SPB Storage port

Fabric B

SPA Storage port SPB Storage port

IP and SAN setup details for virtual RPA clusters Entity


Cluster #2

Cluster Name Time Zone Local Domain Primary DNS Server (optional) Secondary DNS Server (optional) NTP Server (optional but recommended) Cluster Management IPv4

IP and SAN setup details for virtual RPA clusters

39


Entity

IP and SAN details Cluster #1 Management Default Gateway IPv4 Management Subnet Mask IPv4 WAN Default Gateway WAN Subnet Mask SMTP (optional)

vRPA 1

vRPA Management IP vRPA WAN IP iSCSI1 IP iSCSI2 IP ESXi server iSCSI VMkernel port 1 IP ESXi server iSCSI VMkernel port 2 IP

vRPA 2


vRPA 3


vRPA 4

vRPA Management IP vRPA WAN IP iSCSI1 IP iSCSI2 IP ESXi server iSCSI VMkernel port 1 IP

40


Cluster #2


Entity


Cluster #2

ESXi server iSCSI VMkernel port 2 IP vRPA 5


vRPA 6


vRPA 7


vRPA 8


Array SPA

Array SPA Mgmt IP

Array SPB

Array SPB Mgmt IP

Fabric A

Switch IP Address

Fabric B

Switch IP Address IP and SAN setup details for virtual RPA clusters

41

RecoverPoint 5.1 Customer Installation and Upgrade Guide

Recommend Documents