HPE 3PAR Storage Replication Adapter 6.5 for VMware

HPE 3PAR Storage Replication Adapter 6.5 for VMware
HPE 3PAR Storage Replication
Adapter 6.5 for VMware® vCenter
Site Recovery Manager™ User
Guide
Abstract
HPE 3PAR Storage Replication Adapter 6.5 for VMware® vCenter Site Recovery Manager™ (HPE 3PAR SRA) is an
integration component that communicates with HPE 3PAR StoreServ to execute specific storage and HPE 3PAR
Remote Copy functions needed for VMware vCenter Site Recovery Manager operation. This document provides
relevant information for installing and configuring the 3PAR SRA. This document also provides relevant information
for the 3PAR Remote Copy Software configuration so that the 3PAR SRA can execute specific 3PAR Remote Copy
functions to build, manage, test, and execute disaster recovery.
The information contained in this document must be used along with the documentation set provided by Hewlett Packard
Enterprise for the HPE 3PAR StoreServ Storage system, HPE 3PAR Operating System Software, the documentation
provided by VMware for vCenter, Site Recovery Manager, and other related products.
Part Number: QL226-99411B
Published: April 2017
Edition: 5
© Copyright 2017 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services
are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting
an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not
responsible for information outside the Hewlett Packard Enterprise website.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR
12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed
to the U.S. Government under vendor's standard commercial license.
Acknowledgements
Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
VMware® and Site Recovery Manager™ are U.S. registered trademarks of VMware, Inc.
Contents
1 Introduction..........................................................................................................4
2 VMware vCenter Site Recovery Manager overview............................................5
Stretched Storage.................................................................................................................................6
3 Supported configurations.....................................................................................8
4 Prerequisites for installing and configuring HPE 3PAR SRA ..............................9
5 Installing and configuring HPE 3PAR SRA........................................................10
Removing HPE 3PAR SRA.................................................................................................................10
Installing HPE 3PAR SRA 6.5.............................................................................................................10
Verifying installation............................................................................................................................10
Configuring HPE 3PAR SRA..............................................................................................................11
HPE 3PAR storage system setup..................................................................................................11
Configuring HPE 3PAR StoreServ Storage system at protected and recovery sites....................11
Configuring HPE 3PAR StoreServ Storage system for Non-stretched storage.............................12
Configuring HPE 3PAR StoreServ Storage system for Stretched storage....................................13
Configuring VMware vCenter Server for hosts and clusters.........................................................13
Asynchronous Streaming Mode ...................................................................................................13
HPE 3PAR SRA Command Line Interface.........................................................................................13
Managing HPE 3PAR StoreServ Storage SSL Certificates................................................................15
Steps to configure HPE 3PAR SRA in VMware vCenter Site Recovery Manager.............................16
Configuring VMware vCenter Site Recovery Manager..................................................................16
Configuring HPE 3PAR SRA.........................................................................................................16
6 SRA behavior during SRM operations..............................................................20
State diagram for SRM and HPE 3PAR Remote Copy environment..................................................22
A Important notes.................................................................................................23
SRM....................................................................................................................................................23
SRM configuration.........................................................................................................................23
SRM behavior................................................................................................................................23
SRA behavior......................................................................................................................................23
Host configuration...............................................................................................................................25
3PAR Remote Copy............................................................................................................................25
Remote Copy Configuration..........................................................................................................25
Remote Copy Behavior.................................................................................................................26
Support for virtual volume sets and host sets.....................................................................................27
Support for multiple array pair configuration.......................................................................................28
Support for SLD..................................................................................................................................28
Workarounds for SLD error codes.................................................................................................29
Limitations of SLD configuration....................................................................................................29
Support for Stretched Storage............................................................................................................30
B Support and other resources.............................................................................31
Accessing Hewlett Packard Enterprise Support.................................................................................31
Accessing updates..............................................................................................................................31
Websites.............................................................................................................................................31
Related documents and terminology..................................................................................................32
Typographic conventions....................................................................................................................34
Customer self repair...........................................................................................................................34
Remote support..................................................................................................................................34
Documentation feedback....................................................................................................................35
Contents
3
1 Introduction
HPE 3PAR Storage Replication Adapter 6.5 for VMware® vCenter Site Recovery Manager™
(HPE 3PAR SRA) is an adapter to VMware vCenter Site Recovery Manager™ (SRM).
HPE 3PAR SRA enables SRM to work with HPE 3PAR StoreServ Storage systems for array-based
replication. HPE 3PAR SRA is installed on SRM servers and enables communications between
SRM and HPE 3PAR StoreServ Storage systems thus facilitating remote replication.
For information on VMware and the VMware Site Recovery Manager, see the VMware website
http://www.vmware.com/products/site-recovery-manager/.
4
Introduction
2 VMware vCenter Site Recovery Manager overview
SRM works as a plug-in component for VMware vCenter and integrates its functionality in VMware
vCenter.
VMware vCenter Site Recovery Manager:
•
Builds, manages, tests, and executes disaster recovery solutions for virtual infrastructure
implementations.
•
Uses the storage replication mechanism between the protected site and the recovery site
for disaster recovery of the protected site virtual infrastructure.
•
Creates a recovery point objective by creating a protection group at the protected site. The
protection group contains replicated virtual machines.
•
Creates a recovery plan at the recovery site for the protection group at the protection site.
◦
The recovery plan can be tested at any time at the recovery site to verify that recovery
point objective can be achieved at the time of disaster.
◦
The recovery plan can be executed at disaster time or at any desired time at the recovery
site to guarantee that recovery point objective is met.
5
vSphere Web Client
vSphere Web Client
SRM plug-in
SRA
SRA
SRM
server
vCenter
server
ESXi
server
3PAR
ESXi
server
Server
LAN Network
vCenter
server
SRM
server
ESXi
server
ESXi
server
3PAR
ESXi
server
3PAR
Storage
Array
Based Replication
Storage
VMFS
Protected Site
3PAR
VMFS
Recovery Site
SRM communicates with HPE 3PAR Remote Copy Software for storage replication through HPE
3PAR SRA. You can get information about Remote Copy volume groups that exist in HPE 3PAR
StoreServ to SRM from HPE 3PAR SRA. The Site Recovery Manager identifies datastores and
RDM devices in the Remote Copy volume group (also known as consistency groups). These
datastores and RDM devices have corresponding virtual volumes in the Remote Copy volume
group and replicates between the protected site and the recovery site.
Stretched Storage
HPE 3PAR SRA supports a new feature called stretched storage with the SRM 6.5 release.
Stretched storage is implemented in environments where disaster/downtime avoidance is a key
requirement. This combines synchronous replication with array-based clustering.
6
VMware vCenter Site Recovery Manager overview
Platform Service
Controller
vSphere Web Client
vSphere Web Client
SRM plug-in
SRA
SRA
SRM
server
vCenter
server
LAN Network
vCenter
server
ESXi
server
Server
3PAR
SRM
server
ESXi
server
3PAR
3PAR
3PAR
Array
Based Replication
Storage
VMFS
Protected Site
Storage
VMFS
Recovery Site
The integration of stretched storage with Site Recovery Manager 6.5 allows users to achieve:
•
Planned maintenance downtime avoidance
•
Zero-downtime disaster avoidance
NOTE: You must install vCenter in Enhanced Linked mode, for Stretched storage to function
correctly. For details, refer https://blogs.vmware.com/consulting/2015/03/
vsphere-datacenter-design-vcenter-architecture-changes-vsphere-6-0-part-1.html
For more information see VMWare vCenter installation procedure documentation, https://
www.vmware.com/support/pubs/.
Stretched Storage
7
3 Supported configurations
For information about the supported hardware and software platforms, see the Single Point of
Connectivity Knowledge for HPE Storage Products (SPOCK) website http://www.hpe.com/
storage/spock.
8
Supported configurations
4 Prerequisites for installing and configuring HPE 3PAR
SRA
HPE 3PAR SRA is packaged in MSI format and installed on the host where SRM is installed.
•
HPE 3PAR SRA requires the following companion packages to be installed on the host
before you start the installation:
◦
VMware vCenter Site Recovery Manager 5.0 or later
◦
Microsoft .NET Framework 4.6.1
NOTE:
2012.
•
HPE 3PAR SRA does not require Microsoft .Net Framework to operate in Windows
HPE 3PAR SRA requires the following configurations on the HPE 3PAR StoreServ Storage
system:
◦
HPE 3PAR Remote Copy Software license on the 3PAR storage system
◦
HPE 3PAR Virtual Copy Software license on the 3PAR storage system
◦
For using Stretched storage in HPE 3PAR SRA, you must have Peer persistence license.
◦
HPE 3PAR StoreServ Storage system user with edit permission
NOTE: The HPE 3PAR SRA supports partial licensing facility to purchase licenses
based on the capacity used on your storage system. The Remote Copy and Virtual
Copy features are available with partial licenses. SRA 6.5 supports partial licensing only
with HPE 3PAR OS 3.1.2 MU2 or later.
◦
All LUNs used by VMware Virtual Machines to form a protection group that are failed
over together during test and recovery must be part of a single HPE 3PAR Remote
Copy group. For more information about setting up and configuring Remote Copy groups,
see the HPE 3PAR Remote Copy Software User's Guide.
◦
All members of a virtual volume set must belong to the same Remote Copy group.
◦
In an SLD configuration with three HPE 3PAR StoreServ Storage systems (A, B, and
C), where A–B is configured in synchronous mode, A–C in asynchronous periodic mode,
and B–C is the standby link in asynchronous periodic mode. Then, SRM/SRA must be
configured between A–C only, implying that StoreServ A is configured in the protected
site and StoreServ C is configured in the recovery site.
9
5 Installing and configuring HPE 3PAR SRA
This chapter explains how to install and configure HPE 3PAR SRA.
NOTE: The steps to install and configure HPE 3PAR SRA remains same for Stretched and
Non-stretched storage.
Upgrade from an earlier version of the software to HPE 3PAR SRA 6.5 not supported.
This section describes how to:
•
Remove an existing version of HPE 3PAR SRA
•
Install the latest version of HPE 3PAR SRA
•
Verify that the installation is successful
You cannot upgrade to HPE 3PAR SRA 6.5 from an earlier version. Therefore, you must remove
the earlier version before installing HPE 3PAR SRA 6.5.
Removing HPE 3PAR SRA
To remove HPE 3PAR SRA, do the following:
1. Log on as system administrator.
2. Click Start→Control Panel→Programs and Features.
3. Select HPE 3PAR SRA Software Version <x.x>.
NOTE: The installer name remains HP 3PAR SRA Software Version <x.x> for the earlier
versions of SRA.
4.
Click Remove.
The Program Maintenance dialog box appears.
5.
Select Remove and click Next.
NOTE: HPE 3PAR SRA configuration is not deleted in the Windows registry when the HPE
3PAR SRA package is uninstalled.
Installing HPE 3PAR SRA 6.5
To install HPE 3PAR SRA 6.5:
1. Double-click the installation executable file to launch the installation wizard. Click Next to
continue.
NOTE:
2.
3.
4.
HPE 3PAR SRA and SRM must be installed on the same host.
Click I Agree to acknowledge the User License Agreement, and click Next to continue.
Click Next to start installation at the default path.
After the installation is complete, restart the VMware vCenter Site Recovery Manager
service to ensure that HPE 3PAR SRA is recognized by SRM.
NOTE: This package can only be installed under the existing VMware vCenter Site Recovery
Manager installed path. No other installation location is provided as an option.
Verifying installation
To verify the installation of HPE 3PAR SRA 6.5:
1. Click Start →Control Panel→Programs and Features.
10
Installing and configuring HPE 3PAR SRA
2.
Verify that HPE 3PAR SRA Software Version 6.5 or any older versions appears under
Currently installed programs.
NOTE: HPE 3PAR SRA installation adds the SRA\3PARInServ folder to VMware vCenter
Site Recovery Manager storage folder (for example, C:\Program Files (x64)\VMware\
VMware vCenter Site Recovery Manager\storage) and TPDSrm.exe is the adapter
driver program that is invoked by SRM.
Configuring HPE 3PAR SRA
This section describes how to configure HPE 3PAR SRA.
•
“Configuring HPE 3PAR StoreServ Storage system at protected and recovery sites” (page
11)
•
“Configuring HPE 3PAR StoreServ Storage system for Non-stretched storage” (page 12)
•
“Configuring HPE 3PAR StoreServ Storage system for Stretched storage” (page 13)
•
“Configuring VMware vCenter Server for hosts and clusters” (page 13)
•
“Asynchronous Streaming Mode ” (page 13)
HPE 3PAR storage system setup
Any HPE 3PAR StoreServ storage system acting as an array manager (at the protected site or
at the recovery site) in SRM setup must be configured with HPE 3PAR Remote Copy Software.
HPE 3PAR SRA supports synchronous and periodic replication modes in 1:1, 1:N, N:1, and M:N
configurations as supported by HPE 3PAR Remote Copy Software, where M and N indicates
the number of storage systems at primary and recovery sites respectively. HPE 3PAR SRA also
supports synchronous long distance configurations. For more information about Remote Copy
configurations, see the HPE 3PAR Remote Copy Software User's Guide.
NOTE:
•
•
HPE 3PAR SRA 6.5 supports SLD Remote Copy environment on:
◦
HPE 3PAR OS 3.1.2 MU3 P16 or later MUs
◦
HPE 3PAR OS 3.1.3, 3.2.1 P01 or later MUs
HPE 3PAR SRA supports both Periodic (RCIP) and Sync (RCFC) configurations.
NOTE: When using Peer Motion to perform data migration, the Remote Copy configurations
and SRM setup must be re-established with the new array after migration. For more information
about re-establishing Remote Copy configurations, see the HPE 3PAR Peer Motion Manager
User Guide or HPE 3PAR Remote Copy Software User's Guide.
Configuring HPE 3PAR StoreServ Storage system at protected and recovery sites
This section describes the HPE 3PAR StoreServ Storage configurations that you need to perform
at the protected and recovery sites.
IMPORTANT:
sites.
1.
2.
Make sure that you do these configurations both at the protected and recovery
Make sure that the correct version of HPE 3PAR Operating System with the appropriate
licensed features are available.
Create a user on the HPE 3PAR StoreServ Storage system.
Configuring HPE 3PAR SRA
11
3.
Register ESXi hosts on the HPE 3PAR StoreServ Storage system.
Before a LUN from the HPE 3PAR StoreServ storage system can be exported to the ESXi
host, register the ESXi host WWNs/iSCSI names on the HPE 3PAR storage system by
creating a host entry. Perform this operation on both the protected and recovery sites.
NOTE: When you export LUNs to an ESXi host using Persona 11 at the recovery site,
the system stops responding while executing the Rescan All function. Therefore, you must
remove all LUN exposures of the Remote Copy group member on the recovery site, except
the Peer Persistence configuration to the host with Persona 11, to prevent any delayed
response during ESXi rescan.
4.
5.
Create Common Provisioning Groups (CPGs) to use during the creation of virtual volume.
Create virtual volumes.
Create the required number of virtual volumes to meet the replication requirement of the
virtual infrastructure. For more information about creating virtual volumes, see the HPE
3PAR OS CLI Administrator’s Manual.
6.
Set up the HPE 3PAR Remote Copy Software.
HPE 3PAR Remote Copy Software provides the capability to copy virtual volumes from a
protected site to a recovery site.
Set up a Remote Copy link between the protected and recovery site. Create a Remote Copy
volume group at the protected site. A corresponding Remote Copy group is automatically
created at the recovery site. Ensure that the HPE 3PAR storage system hardware is set up
appropriately for creating a Remote Copy configuration between the protected site and
recovery site. For more information about setting up HPE 3PAR Remote Copy Software,
see the HPE 3PAR Remote Copy Software User Guide.
NOTE:
•
You can create a Remote Copy configuration between the protected and recovery sites
using one of the following protocols:
◦
RCIP
◦
RCFC
For information about implementing Remote Copy, see the HPE 3PAR Remote Copy
Software User's Guide.
•
Remote Copy is supported on HPE 3PAR OS 2.3.1 or later.
Configuring HPE 3PAR StoreServ Storage system for Non-stretched storage
This section describes the HPE 3PAR StoreServ Storage configurations that you need to perform
only at the protected site.
1. Create Remote Copy Group on the primary storage system.
2.
Admit the virtual volume to the Remote Copy volume group.
A virtual volume contains virtual infrastructure data (datastore, virtual disk, and RDM disk).
Replication of virtual infrastructure data is enabled by admitting virtual volumes to the Remote
Copy volume group. Each virtual volume at the protected site is mapped to a corresponding
virtual volume at the recovery site. Data in each virtual volume at the protected site is synced
with the data in the corresponding virtual volume at the recovery site whenever Remote
Copy is active. For more information about adding virtual volumes to Remote Copy volume
groups, see the HPE 3PAR Remote Copy Software User Guide.
12
Installing and configuring HPE 3PAR SRA
3.
Export the virtual volume to the ESXi host (create a VLUN).
It is assumed that ESXi host(s) are already connected to the HPE 3PAR StoreServ storage
system and configured per the recommendations in the VMware ESX Servers Implementation
Guide. Create a VLUN for the ESXi host(s) corresponding to the virtual volume. For more
information, see the HPE 3PAR OS VMware ESX Server Implementation Guide.
Configuring HPE 3PAR StoreServ Storage system for Stretched storage
This section describes the HPE 3PAR StoreServ Storage configurations that you must perform
on both the protected and recovery sites.
•
Create Remote Copy Group from primary to recovery storage system.
NOTE:
You must create Remote copy in Sync mode for stretched storage support.
•
Admit the virtual volumes to the Remote Copy volume group.
•
All associated hosts are connected to both the primary and secondary arrays.
•
Set the same WWN for the replicated volumes which are admitted to the Remote Copy group
in primary to recovery storage system.
•
Set path management policy for Remote Copy volume group using the following command:
setrcopygroup pol path_management
•
Export the virtual volumes to the ESXi hosts on both sites (create a VLUN).
Configuring VMware vCenter Server for hosts and clusters
This section describes how to configure the VMware vCenter Server for hosts and clusters.
1. Discover LUNs on the ESXi hosts.
2. Rescan the HBA to verify if the VLUN is visible to the ESXi host. Perform rescan only after
you export the VLUNs to the ESXi host.
3. Create a VMFS Datastore.
4. Deploy VMs as required on the protected site.
NOTE: The steps to configure VMware vCenter Server for hosts and clusters remain same
for stretched storage. Make sure that the datastore is visible on the recovery site also.
Asynchronous Streaming Mode
HPE 3PAR SRA 6.5 supports Asynchronous streaming mode.
Note the following for asynchronous streaming mode:
•
Asynchronous streaming is supported in 1:1 configurations.
•
In an asynchronous streaming remote-copy configuration, RCFC connections must be used.
•
Refer HPE 3PAR Remote Copy Software User Guide HPE 3PAR OS 3.2.2 for detail
information on Asynchronous streaming.
HPE 3PAR SRA Command Line Interface
HPE 3PAR SRA supports the TPDSrm.exe command line interface. SRM requests are sent
using a Perl script command.pl in the HPE 3PAR SRA installed directory. The Perl script internally
processes the data to an XML file and spawns an instance of TPDSrm.exe to process the XML
file. The XML file is removed once TPDSrm.exe returns to command.pl.
The HPE 3PAR SRA for VMware SRM 6.0 utility supports the following commands:
HPE 3PAR SRA Command Line Interface
13
Commands
•
-v
To display version information.
Syntax: TPDSrm.exe <-v>
•
cleansnaps
To remove any snapshots created for test failover on the HPE 3PAR Storage system.
Syntax: TPDSrm.exe cleansnaps <-sys StorageSystemName -user UserName
-pass Password [-loglevel Num]>
◦
-sys <StorageSystem>
The HPE 3PAR storage system name or IP address to connect.
◦
-user <UserName>
The HPE 3PAR storage system user name.
◦
-pass <Password>
The HPE 3PAR storage system password.
◦
-loglevel <Num>
Optional. Overrides the default output message level using a numeral from 1 to 5. The
default value is 3 (1-error, 2-warning, 3-info, 4-verbose, 5-trivia).
•
viewstate
To view the local disaster recovery state cache information. Only prepareFailover and
failover states are available.
Syntax: TPDSrm.exe viewstate
•
cleanstate
To remove the local disaster recovery state cache created during the failover operation.
Syntax: TPDSrm.exe cleanstate <-sysid StorageSystemID> <-rcgroup
RCGroupName>
◦
-sysid <StorageSystemID>
The system ID of the HPE 3PAR storage system where the Remote Copy group name
is found. Use the viewstate command to see currently cached information.
◦
-rcgroup <RCGroupName>
The Remote Copy group name.
•
viewcert
To view the currently accepted StoreServ certificate.
Syntax: TPDSrm.exe viewcert <-sysid StorageSystemID>
◦
sysid <StorageSystemID>
Optional. System ID of the HPE 3PAR StoreServ. Displays all certificates if this option
is not specified.
•
validatecert
To accept and save HPE 3PAR StoreServ certificate.
14
Installing and configuring HPE 3PAR SRA
This operation must be done prior to SRM configuration with HPE 3PAR Storage system.
Syntax: TPDSrm.exe validatecert <-sys StorageSystemIP -user UserName
-pass Password>
◦
-sys <StorageSystem>
HPE 3PAR StoreServ name or IP address to connect.
◦
-user <UserName>
HPE 3PAR StoreServ user name.
◦
-pass <Password>
HPE 3PAR StoreServ password.
•
removecert
To delete the accepted HPE 3PAR StoreServ certificate from cache.
Syntax: TPDSrm.exe removecert <-sysid StorageSystemID>
◦
-sysid <StorageSystemID>
System ID of the HPE 3PAR StoreServ.
•
log
To view or modify the current log size limit and the maximum number of log history files to
maintain.
Syntax: TPDSrm.exe log [-size LogSize] [-cnt Num]
◦
-size <LogSize>
Specify the log file size limit in MB. The default size is 2 MB.
◦
-cnt <Num>
Specify the maximum log history files besides the latest log file to maintain. The default
is 20 histories.
Managing HPE 3PAR StoreServ Storage SSL Certificates
HPE 3PAR StoreServ Storage enables management and validation of SSL certificates by the
host and client applications to establish a secure connection.
HPE 3PAR CLI and HPE 3PAR OS versions 2.3.1 MU5 P35, 3.1.1 MU3 P27, 3.1.2 MU3
P16, or later, supports a self-signed 2048-bit RSA SSL certificate for HPE 3PAR StoreServ
Storage system.
After upgrade, SRA requires that you accept and validate the HPE 3PAR StoreServ server SSL
certificate to perform any operations related to HPE 3PAR StoreServ. You must validate the HPE
3PAR StoreServ certificate using the SRA command line interface (TPDSrm.exe) before you
configure arrays from SRM. If you do not accept the specific HPE 3PAR StoreServ certificate,
then the connection is not established with HPE 3PAR StoreServ and SRA returns an error
message to SRM.
For non-stretched storage configuration retrieve the respective array certificates for the protected
and recovery sites at SRM.
For stretched storage configuration retrieve the array certificates for both protected and recovery
sites at the individual site before you proceed with stretched storage configuration at SRM.
Managing HPE 3PAR StoreServ Storage SSL Certificates
15
Certificate validation is supported using the SRA command line options. SRA supports the
following commands to view, validate, and remove the HPE 3PAR StoreServ certificate:
•
TPDSrm.exe viewcert—To view the currently accepted StoreServ certificate.
•
TPDSrm.exe validatecert—To accept and save the HPE 3PAR StoreServ certificate.
NOTE: You must accept and validate the HPE 3PAR StoreServ certificate using the
TPDSrm utility before you configure SRM with HPE 3PAR StoreServ Storage System. If you
do not validate the certificate, connection to HPE 3PAR StoreServ is denied.
Configure the remote copy between HPE 3PAR StoreServ storage systems on the Protected
and Recovery sites to accept and validate HPE 3PAR StoreServ certificates.
For more information on configuring remote copy, refer HPE 3PAR Remote Copy User
Guide.
•
TPDSrm.exe removecert—To delete the accepted HPE 3PAR StoreServ certificate from
the cache memory.
If you have configured an SLD remote copy environment with three HPE 3PAR StoreServ Storage
systems (A, B, and C), where A—B is configured in synchronous mode, A—C in asynchronous
periodic mode, and B—C is the standby link in asynchronous periodic mode. SRM/SRA is
configured between HPE 3PAR StoreServ Storage systems A and C, then HPE 3PAR SRA
requires that you accept and validate the HPE 3PAR StoreServ Storage SSL certificate for the
primary and secondary HPE 3PAR StoreServ Storage systems on both the Protected and
Recovery sites.
NOTE:
You must accept the certificate when the link between A and C is UP.
For example, HPE 3PAR StoreServ A and SRM Server 1 are part of the protected site. HPE
3PAR StoreServ B and SRM Server 2 are part of the recovery site. In SRM Server 1, you
must accept and validate the HPE 3PAR StoreServ A and HPE 3PAR StoreServ B
certificates. Perform a similar procedure for SRM Server 2.
Steps to configure HPE 3PAR SRA in VMware vCenter Site Recovery
Manager
This section describes how to configure VMware vCenter Site Recovery Manager and HPE 3PAR
SRA.
Configuring VMware vCenter Site Recovery Manager
Click Start→VMware→vCenterServer→VMware vSphere WebClient to launch SRM using
VMware vSphere WebClient.
NOTE: For more information about configuring VMware vCenter SRM, see the VMware vCenter
Site Recovery Manager documentation.
IMPORTANT: Ensure that both vCenter Servers are configured with each other and can be
accessed from the respective sites.
Configuring HPE 3PAR SRA
You need to do the following HPE 3PAR SRA configurations in SRM.
1. Click VMware vSphere WebClient→Site Recovery.
The Add Array Manager window appears.
2.
16
Enter the following information in the Configure array manager section.
Installing and configuring HPE 3PAR SRA
1.
2.
3.
Display Name—Enter a display name for the HPE 3PAR StoreServ Storage System.
Host name or IP Address of HPE 3PAR Storage system—Enter the host name or
IP address of the storage system located at the protected or recovery sites providing
storage replication.
Remote Copy group name prefix limiting discovery—The filtering condition to
discover an RC group.
NOTE:
4.
5.
3.
•
You can use the asterisk (*) wildcard to search for an RC group in an array. Filtering
reduces the time to discover the RC groups in an HPE 3PAR StoreServ Storage
System.
•
If you do not specify any filtering conditions, then SRA discovers all Remote Copy
groups in the HPE 3PAR StoreServ Storage System.
User name of the HPE 3PAR Storage system—The user name that HPE 3PAR SRA
uses to connect to the storage system.
Password of the HPE 3PAR Storage system—The password that HPE 3PAR SRA
uses to connect to the storage system.
Click Next.
The wizard displays the message Ready to complete.
Steps to configure HPE 3PAR SRA in VMware vCenter Site Recovery Manager
17
4.
Click Finish.
After configuration, the wizard displays both HPE 3PAR StoreServ Storage System arrays
in a paired state.
The discovery of the devices starts automatically after the arrays are paired and they are
displayed as shown in the figure:
For an SLD configuration, after the Array Manager is added successfully, if you select the primary
array, two target arrays are listed. You must configure SRM/SRA between HPE 3PAR StoreServ
Storage systems A and C.
Figure 1 shows the SLD configuration of a primary and recovery array:
Figure 1 SLD configuration
The array pair between HPE 3PAR StoreServ Storage systems A and C is automatically enabled
and paired as shown here:
18
Installing and configuring HPE 3PAR SRA
NOTE: Linked mode is not a prerequisite for using Site recovery manager. However, with SRM
5.1, linked mode has a new prerequisite. That is if you want to use SRM 5.1 ensure that you
install SSO at both sites. Also, install SRM specifically in Multisite mode.
For more information on configuring SRA in Linked mode, see http://blogs.vmware.com/vsphere/
2013/02/linked-mode-with-sso-for-srm.html.
Steps to configure HPE 3PAR SRA in VMware vCenter Site Recovery Manager
19
6 SRA behavior during SRM operations
This chapter describes the SRA behavior during SRM operations, such as test, failover, and
failback.
Test
Use this option to perform nondisruptive recovery operations.
SRM communicates with HPE 3PAR SRA using the remote storage information obtained during
the discovery process. SRA creates snapshots of the remote virtual volumes and presents them
to the recovery ESXi server. During this recovery process, the VMs continue to run at the
production site (protected site). You can verify that the VMs are running at the recovery site.
Clean Up
Perform the Cleanup operation after you have verified that the VMs are running at the recovery
site using the Test operation. SRA does a cleanup (unpresent and delete) of the previously
created snapshots.
Recovery
A recovery operation is executed when an SRM recovery plan is configured with SRM protection
groups that use replicated HPE 3PAR Virtual Volumes as a Datastore.
Perform a recovery operation by shutting down the VMs at the protected site and recover those
VMs at the recovery site.
•
Planned migration—SRM shuts down the VMs at protected site and unmounts the Datastores.
SRA changes the status of the source Datastores to read-only, and then creates the
snapshots of the source device. SRA reverses the replication direction and swaps the
read/write relation between the Datacenters. SRM then rescans the Datastores at the
recovery site and restarts the VMs.
•
Disaster recovery—If the protected Datacenter is unavailable due to any disasters or failures,
you must run the SRM recovery plan to start the VMs at the recovery site. The SRA recovery
process is similar to planned migration, except for the snapshot creation operations performed
at the protected site.
For SLD configurations:
Consider the following scenarios for SLD configuration where A is the Primary System, C the
Asynchronous Periodic Backup System, and B the Synchronous Backup System, and SRM/SRA
is configured between 3PAR StoreServ Storage systems A and C.
•
All links are up:
SRM initiates data transfer from A to C through HPE 3PAR SRA. After the sync is complete,
SRA stops the RC groups between A–B and also between A–C. Then, SRA initiates failover
at C so that C becomes the Failover System and takes the role of the Primary System.
•
A–C link is down:
HPE 3PAR SRA initiates the data transfer from B to C.
After the sync is complete, SRA stops the RC groups between A–B. SRA then initiates
failover at C so that C becomes the Failover System and takes the role of the Primary System.
For more information, see the “Limitations of SLD configuration” (page 29) section.
•
A–B link is down:
When the A–C link is up:
20
SRA behavior during SRM operations
SRM initiates data transfer from A to C through HPE 3PAR SRA. Once the sync is complete,
SRA stops the RC groups between A–C. SRA then initiates a failover at C so that C becomes
the Failover System and takes the role of the Primary System.
When A–C link is down:
Depending on the situation, either B or C will have the most current data since the
synchronous link between A—B is down. In such a scenario, as per the design, HPE 3PAR
SRA does not initiate any data transfer from B to C. With the available data, C becomes the
failover system and takes the role of the primary system.
CAUTION: If C does not contain the most current data then any data replicated to B that
is not replicated to C is discarded.
•
B–C link is down:
When A–C link is up:
SRM initiates data transfer from A to C through HPE 3PAR SRA. Once the sync is complete,
SRA stops the RC groups between A–B and also between A–C. SRA then initiates failover
at C so that C becomes the failover system and takes the role of the primary system.
When the A–C link is down:
HPE 3PAR SRA will not initiate data transfer between B–C, because the B–C standby link
is not available for data transfer. SRA stops the RC groups between A–B. SRA then initiates
failover at C. With the available data, C becomes the Failover System and takes the role of
the Primary System.
CAUTION: If C does not contain the most current data and any data replicated to B that
is not yet replicated to the C is discarded.
Reprotect
Perform the reprotect operation to configure protection in the reverse direction (from Site B to
Site A), as a preparation for failback to the original state. The SRA operations are similar to the
planned migrations, and deletes the earlier snapshots that were created during failover from Site
A to Site B.
For SLD configurations, the reprotect operation requires that the remote copy links between the
new primary and both the targets to be up. If array C is the new primary system and if the links
between C–A and C–B are up, then SRA starts the remote replication from C–A and C–B and
waits until the sync is complete as part of the reprotect operation.
During the reprotect operation, SRA triggers delta resync operation from C–A and C–B where
C is the new primary system after failover. If the SRM recovery operation was performed when
either A–B or B–C or both the remote copy links are down. As per the remote copy behavior,
reprotect operation triggered by SRM through SRA will initiate a full copy from C–B only (from
C–A, delta resync will be initiated).
The recovery and reprotect operations can be executed in sequence for the failover and failback
processes.
Failover is a process that sets the replication environment at the recovery site in case of a disaster
or a planned migration.
Failback is a process that sets the replication environment back to its original state at the protected
site (local site), prior to a failover. A failback is managed as a normal server migration process.
21
State diagram for SRM and HPE 3PAR Remote Copy environment
22
SRA behavior during SRM operations
A Important notes
SRM
SRM configuration
•
It is strongly recommended to configure one protected group per Remote Copy group.
•
If multiple Remote Copy groups are included in one protected group, it is recommended to
set the same sync time on all the periodic Remote Copy groups.
•
Support for Dynamic Access Groups. The concept of Dynamic Access Group support is to
expose LUNs only to the specified HBA initiators provided by SRM. Any exposure of the
participating LUNs made to other initiators not on the requested list is removed. This feature
is always enabled.
•
Multiple Remote Copy groups in one protected group is not recommended. HPE 3PAR SRA
logs a warning to user if multiple instances of such configurations are detected during the
Test or Recovery operation since this might be an indication that VMs are using virtual
volumes from different Remote Copy groups.
SRM behavior
SRM might potentially time out if multiple test failover or recovery operations are run
simultaneously. Rerun the operation if the time out error occurs. Alternatively, the time out error
might be avoided if the operations are run sequentially.
SRA behavior
•
The reserved virtual volume naming conventions for HPE 3PAR SRA are as follows:
◦
SRM_RO_<VVID>
◦
SRM_RW_<VVID>
◦
SRM_RECOVER_RO_<VVID>
◦
SRM_TARGETBK_RO_<VVID>
•
If SRM runs into a virtual volume promote operation during reprotect, you must retry the
reprotect operation.
•
Devices on the protected storage system must be read-only after prepareFailover and
optionally take snapshots of the source devices for restoration if needed. The way to make
a device read-only to meet SRM's specification before failover is to remove VLUN exposure
so that no one has access to it. Remote Copy will internally manage taking the snapshots
if something goes wrong during the failover process. HPE 3PAR SRA also takes a snapshot
of the devices on the protected site of SRM (Remote Copy role Primary or Primary-Rev)
for restore purposes since the user might activate the Remote Copy sync after failback
(setrcopygroup restore) that might destroy the data content. The snapshot name must
have the SRM_RECOVER_RO_<VVID> prefix.
•
After failover, the devices on the protected storage system must be read-only. This is same
for prepareFailover. The only difference is that, if the failover is part of the failback
workflow, the protected storage system becomes secondary after failback using the
setrcopygroup restore command. Devices under the secondary Remote Copy group
will automatically have read-only access.
•
Additional protection to the data on the recovery storage system. HPE 3PAR SRA takes a
snapshot of the devices on the recovery storage system of the SRM before failover for
optional restore purpose. The snapshot name will have the following prefix:
SRM_TARGETBK_RO_<VVID>.
SRM
23
•
•
If a failover operation is unsuccessful, be sure to clean up the local disaster state cache.
Otherwise, the subsequent SRM operations will fail.
On both protected and recovery sites where HPE 3PAR SRA is installed, run the following
commands:
◦
TPDSrm viewstate
◦
TPDSrm cleanstate -sysid <StorageSystemID> -rcgroup <RCGroupName>
Primary Array is down or is taken offline.
When the primary array is down or the remote copy link between the primary and secondary
array is down, and if you need to run the recovery operation, do the following:
1. Click Disaster Recovery with Forced Recovery to execute the recovery.
After completing this step, SRM displays the Recovery Required prompt. This implies
that after bringing the storage array or link up, you must run recovery again.
2.
After bringing up the storage array or link, navigate to the Devices tab in SRM and click
Refresh to rediscover the devices.
Make sure that the devices are discovered again in SRM.
3. Execute the Recovery and Reprotect operations.
For more information about Disaster Recovery—Forced Recovery option, see the VMware
vCenter Site Recovery Manager documentation.
•
24
Snapshots Management
SRA creates snapshots during Test and Recovery operation as described previously.
◦
Test
During Test, SRA creates snapshots of the remote virtual volumes and presents them
to the recovery ESXi server. Naming conventions for these snapshots are
SRM_RO_<VVID> and SRM_RW_<VVID>. Snaphsots created during Test operation is
deleted during Cleanup operation.
◦
Recovery
During SRM recovery from protected site to recovery site (failover operation), HPE
3PAR SRA takes a snapshot of the devices on the protected site of SRM during
preparefailover for restoration if needed. Naming conventions for these snapshots
are SRM_RECOVER_RO_<VVID>. HPE 3PAR SRA also takes a snapshot of the devices
on the recovery storage system of the SRM before failover for optional restore purpose.
The snapshot name has the prefix SRM_TARGETBK_RO_<VVID>. These snapshots will
be deleted in the next SRM recovery from protected site to recovery site.
During SRM recovery from recovery site to protected site (failback operation), similar
logic is followed in SRA. But the names of the snapshot in the protected site 3PAR will
be SRM_TARGETBK_RO_<VVID> (already SRM_RECOVER_RO_<VVID> snapshots exist
during the first failover) and the names of the snapshot in the recovery site will be
SRM_RECOVER_RO_<VVID> (already SRM_TARGETBK_RO_VVID snapshots exist during
the first failover). These snapshots will be deleted in the next SRM recovery from recovery
site to protected site.
Therefore, there will be maximum of two snapshots existing for each VV of the RC
groups in the 3PAR arrays at any point of time.
SRA does not have any automatic function to delete these snapshots. User can decide
to delete these snapshots manually after a successful failover. When a failover or failback
operations is executed next time, SRA deletes the snapshots if exists and create new
snapshots.
Important notes
CAUTION: When the remote copy links are up and running between the HPE 3PAR arrays,
do not execute the SRM forced recovery operation during the failback scenario. That is, when
you want to move VM workloads from recovery site to the protected site. If you perform the forced
recovery operation during failback scenario, then subsequent recovery required operation fails.
Host configuration
If an ESXi host has both FC and iSCSI definitions created on the 3PAR storage system and the
vCenter Server also has both FC and iSCSI software adapter configured, per the vCenter Server's
request, LUNs will be exposed to both host definitions in the event of a failover. However, if only
one host definition is presented on the HPE 3PAR storage system (either FC or iSCSI), HPE
3PAR SRA will only expose LUNs to whichever is defined on the HPE 3PAR Storage system.
3PAR Remote Copy
Remote Copy Configuration
•
If a single virtual machine sits on two datastores and two virtual volumes, it is recommended
to include both virtual volumes in the same Remote Copy group.
•
If a virtual machine sits on a spanned datastore, all virtual volumes used for the spanned
datastore must be included in a single Remote Copy group.
•
Remote Copy group reserves .r for naming. Do not include the reserved naming in your
Remote Copy group name.
•
If the same virtual volume IDs are part of a single RC group across two storage arrays that
are part of an SRM array pair, then during failback reprotect operation SRM service might
stop. To avoid this issue, maintain unique ids for the virtual volumes in the RC group across
the storage arrays.
For Example, run the showrcopy command from the HPE 3PAR CLI interface.
The output for an RC Group is as follows:
showrcopy
Group Information
Name
Target
Status
Role
Mode
Options
TestRCG
rsra
Started Primary
Periodic Last-Sync 2014-10-20 12:44:24
SGT , over_per_alert
LocalVV
ID
RemoteVV
ID
SyncStatus
LastSyncTime
TestVV_Pri.0 1741 TestVV_Sec.0 1740 Synced
2014-10-20 12:44:24 SGT
TestVV_Pri.1 1742 TestVV_Sec.1 1741 Synced
2014-10-20 12:44:24 SGT
As displayed in the above result, the virtual volume id 1741 is same between the primary
and secondary volumes in the same RC group. In an RC Group, none of the virtual volumes
must have the same virtual volume ID.
Host configuration
25
Do the following to resolve this issue:
◦
Process 1
1. Identify all serial ID numbers on Primary_array and Secondary_array by running
the showrcopy command using HPE 3PAR CLI interface.
Sample output:
Primary_array Secondary_array
Group Information
Name
Target
Status
Role
Mode
Options
TestRCG
rsra
Started Primary
Periodic Last-Sync 2014-10-20
12:44:24 SGT , over_per_alert
LocalVV
ID
RemoteVV
ID
SyncStatus
LastSyncTime
TestVV_Pri.0 1741 TestVV_Sec.0 1740 Synced
2014-10-20 12:44:24
SGT
TestVV_Pri.1 1742 TestVV_Sec.1 1741 Synced
2014-10-20 12:44:24
SGT
In the sample set of replications seen above, the serial ID 1741 is used on both
arrays.
2.
3.
4.
5.
6.
Stop the replication between Primary_array and Secondary_array by running the
stoprcopygroup <group_name> command using HPE 3PAR CLI interface for
RC groups that have the same serial IDs used by source and target devices.
Destroy the target device (Secondary Virtual volume) TestVV_Sec.1 with serialID
1741 on Secondary_array.
Recreate the target device TestVV_Sec.1 on Secondary_array. The
Secondary_array assigns a new serialID automatically. This new serialID, one
above the largest serialID currently used by Secondary_array. For example, if the
highest current serialID on Secondary_array is 400, the new device TestVV_Sec.1
assigned is serialID 401.
Ensure that the serialID of the new device TestVV_Sec.1 is not used by any device
on Primary_array.
Re-establish the replication relationship between device TestVV_Pri.1 on
Primary_array and device TestVV_Sec.1 on Secondary_array.
IMPORTANT: This solution destroys the designated target devices only. Do not
make any changes to the source devices. However, if it is not possible to achieve
uniqueness of serial IDs between the two Arrays, it might be necessary to recreate
the source devices. To recreate source devices safely, migrate the data to new
storage devices before the source (Primary_array) device is destroyed.
◦
Process 2
Create a series of small volumes that are sufficient to bring the serialIDs list out of sync
between the two Sites. For example,
1. Ensure that Primary_array has serialIDs starting from 250.
2. Ensure that Secondary_array has serialIDs starting from 240.
3. Create 30 to 40 small volumes or devices on Primary_array to use all the indexes
from 250 to 280.
4. Delete these small volumes or devices which also delete these serialIDs.
NOTE: The next serialID on Primary_array would be 281 thus preventing any
duplication.
26
Important notes
Remote Copy Behavior
In a disaster recovery scenario, when the Remote Copy links are down, the Remote Copy group
status might still be Started. A failover attempt is successful only when the Remote Group
status becomes Stopped.
Support for virtual volume sets and host sets
HPE 3PAR SRA supports virtual volume set (vvset) and host set features of HPE 3PAR StoreServ
Storage system.
The following are the HPE 3PAR SRA prerequisites for HPE 3PAR virtual volume set and HPE
3PAR host set features:
•
For HPE 3PAR OS versions 3.1.3 or later:
When an RC group is created, virtual volume set is automatically generated for the remote
copy group virtual volumes in both primary and secondary HPE 3PAR StoreServ Storage
systems. To use the vv set feature for presenting LUNs to a host, then Hewlett Packard
Enterprise recommends that you use automatically created vv sets to present the virtual
volumes to the host.
•
For HPE 3PAR OS version 3.1.2 MU3:
To use the vv set feature for presenting the primary LUNs to a host, you must manually
create the vv set and map the remote copy group virtual volumes to the created vv set in
the primary HPE 3PAR StoreServ Storage system. Hewlett Packard Enterprise recommends
that you create the vv set manually in the secondary HPE 3PAR StoreServ Storage system
and map the RC group virtual volumes to the created vv set. In the event of a failover, HPE
3PAR SRA uses the manually created vv set to present LUNs to the host and HPE 3PAR
SRA does not create the vv set by itself.
All virtual volumes exposed using the same HPE 3PAR virtual volume set and protected by
SRM must belong to the same remote copy group.
If virtual volumes are from a virtual volume set with multiple VMs created, be sure to include
all virtual volumes in a single remote copy group and in the same protection group. Otherwise,
there is a potential of losing connectivity to the VMs if virtual volumes are included in more
than one remote copy group and all remote copy groups are not included in the same
protection group.
Support for virtual volume sets and host sets
27
NOTE:
•
IMPORTANT:
If a remote copy group has virtual volumes that are not participating in datastore creation
and if these virtual volumes are exposed to a different host, then the data might get corrupted.
•
You must make sure that all virtual volumes in a remote copy group are participating in
datastore. The virtual volumes in a remote copy group that are not participating in datastore
creation must not be presented to a host.
•
If the virtual volumes participating in an SRM configuration are exposed using a virtual volume
set, any virtual volume member in this set, not used by SRM in the same protected group
loses connectivity to the LUN after a failover.
•
In the event of a failover, if the participating virtual volumes and hosts are part of vv set and
host set respectively, then the LUNs are exposed using vv set and host set features.
•
If the participating virtual volumes and hosts are not part of vv set and host set features,
then the LUNs are individually exposed to the ESXi hosts.
•
For HPE 3PAR OS versions 3.2.1 or later:
Volumes which are a part of Remote Copy group configured for protection must not be added
in any manually created VVSets.
◦
If the same volumes are a part of Auto Created VVSets and manually created VVSets,
SRA would export all the VVSets separately , leading to Multiple exports of the same
Volumes.
◦
If a manually created VVSet contains volumes which are a part of Remote Copy group
,and also other volumes , then during failover SRA would unexport both the VVSets
separately , hence all volumes contained in the Manually created VVSet would be
unexported.
Support for multiple array pair configuration
HPE 3PAR SRA supports multiple array pair configurations. Different remote copy groups from
the array pairs can be part of a single recovery plan or different recovery plans.
Support for SLD
•
HPE 3PAR SRA supports synchronous long distance remote copy groups on HPE 3PAR
OS 3.1.2 MU3 P16 or later MUs, and HPE 3PAR OS 3.1.3 or later.
•
HPE 3PAR SRA can coexist with a synchronous long distance remote copy group on HPE
3PAR OS version 3.1.1 to HPE 3PAR OS 3.1.2 MU2.
•
For HPE 3PAR OS versions up to 3.1.2 MU2:
◦
SRM supports only one-to-one replication. If one of the pairs in an SLD setup is selected
for an SRM configuration, only the selected pair is started after reprotect in the failover
workflow.
◦
Before failback, all the pairs in the SLD setup must be started as a requirement for
setrcopygroup restore operation. You can run the showrcopy groups
<groupname> command to see the status of the SLD groups. All virtual volume members
in the SLD setup must be in Synced status for the failback operation to be successful.
NOTE:
28
Important notes
You cannot use Stretched storage feature in HPE 3PAR SLD configuration.
Workarounds for SLD error codes
This section describes workaround for the following SLD error codes:
•
Error code 1110: One of the failure reasons might be remote copy replication role of the
RC Group <RC group name> in target storeserv system <target name> is not secondary.
Manually issue the HPE 3PAR remote copy setrcopygroup CLI command with reverse option
to change the role.
To resolve this:
1. Run the showrcopy groups <RC group name> command on the original protected
storage system.
2. Run the setrcopygroup reverse –local –current <RC group name>
command to change remote copy role, if the group role is Primary-Rev.
•
Error code 1112: HPE 3PAR SRA is unable to connect to target storeserv system <target
name> to execute the failover operation with restore option. HPE 3PAR SRA fails to connect
to target HPE 3PAR storeserv system with the available credentials. Try the following options:
1. Try accepting target HPE 3PAR SSL certificate again.
2. Verify the connectivity to target 3PAR array from SRM host and retry the operation.
If above options do not resolve the issue, manually issue the HPE 3PAR remote copy
setrcopygroup CLI command with restore option to change the replication roles.
To resolve this:
1. Run the showrcopy groups <RC group name> command on the protected storage
system.
2. Run the showrcopy groups <RC group name> the command on the recovery
storage system.
3. Run the setrcopygroup restore -t <targetname> <RC group name>
command on the protected storage system to change the remote copy roles, if the group
role is Primary-Rev on the protected storage system, and Secondary-Rev on the
recovery storage system.
Limitations of SLD configuration
In an SLD remote copy environment with three HPE 3PAR StoreServ Storage systems (A, B,
and C), where A—B is configured in synchronous mode, A—C in asynchronous periodic mode,
and B—C is the standby link in asynchronous periodic mode. SRM/SRA is configured between
HPE 3PAR StoreServ Storage systems A and C.
•
During the reprotect operation, SRA triggers a delta resync operation from C—A and C—B,
where C is the new primary system after failover. If the SRM recovery operation was
performed when either A—B or B—C or both the remote copy links were down, then as per
the remote copy behavior, the reprotect operation triggered by SRM through SRA will initiate
a full copy from C—B only (from C—A delta resync will be initiated).
•
SRM recovery operation initiated at C does a delta sync from B to C and then initiate the
failover operation at C. If the A—C link is down, as per the remote copy behavior, the data
transfer from B—C becomes full-sync mode during SRM recovery operation at C.
Workaround: When all the remote copy links are UP, run the SRM Test operation at least
once before executing the disaster recovery at ‘C’ when the A—C link is down, to avoid
B—C going to FULL SYNC.
Support for SLD
29
Support for Stretched Storage
CAUTION:
3PAR Remote Copy links down, Storage arrays and all IO paths operational
Do not perform SRM Failover/Failback operation whenever the recovery plan includes VMs
residing on stretched devices and when Remote Copy links are down between two 3PAR storage
arrays and both the arrays and all IO paths are operational to avoid any potential data corruption
issues.
•
In stretched storage, failover and failback is executed when RC links are down. Failover
disaster recovery reprotect is completed with error message Error-Failed to sync data on
replica devices. A specified parameter was not correct: deviceGroup, whereas failback
reprotect is completed without any error message.
•
In case of an inoperable protected array, when you execute recovery (failover) (disaster
recovery with forced recovery) to migrate VMs to the recovery site in SRM , the recovery
operation succeeds and prompts you to execute recovery once again.
The protected storage array and links between storage arrays must be functional before
executing recovery again. After performing these steps, run Discover Devices for the
selected array pair in SRM GUI to complete the recovery operation.
•
In case of an inoperable recovery array, when you execute recovery (failback) (disaster
recovery with forced recovery) to migrate VMs back to the protected site in SRM , the recovery
operation succeeds and prompts you to execute recovery once again.
The recovery storage array and links between storage arrays must be functional before
executing recovery again. After performing these steps, run Discover Devices for the
selected array pair in SRM GUI to complete the recovery operation.
•
Error in recovery plan when you shut down the protected VMs.
Error
Operation timed out: 900 seconds during Shutdown of VMs at Protected Site.
If you use SRM to protect datastores on arrays that support dynamic swap, then running a
disaster recovery when the protected site is partially operable or running a force recovery
might cause errors when rerunning the recovery plan to complete protected site operations.
One such error occurs when the protected site become operational, but SRM is unable to
shut down the protected virtual machines. This error usually occurs when 3PAR array enables
the protected LUNs as read-only, which renders ESXi unable to complete I/O for powered
on protected virtual machines.
To complete the recovery workflow, reboot ESXi hosts on the protected site that are affected
by read-only LUNs.
•
When you execute Recovery→Planned Migration without vMotion in SRM, the recovery
operation might fail due to SyncFailed.
SyncFailed: Failed to sync data for group or Cannot process consistency group
<groupname> with role 'target' when expected consistency group with role 'source'.
To complete the recovery workflow, run Discover Devices operation manually for the
selected array pair in SRM GUI and execute Recovery→Planned Migration without
vMotion.
30
Important notes
B Support and other resources
Accessing Hewlett Packard Enterprise Support
•
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
www.hpe.com/assistance
•
To access documentation and support services, go to the Hewlett Packard Enterprise Support
Center website:
www.hpe.com/support/hpesc
Information to collect
•
Technical support registration number (if applicable)
•
Product name, model or version, and serial number
•
Operating system name and version
•
Firmware version
•
Error messages
•
Product-specific reports and logs
•
Add-on products or components
•
Third-party products or components
Accessing updates
•
Some software products provide a mechanism for accessing software updates through the
product interface. Review your product documentation to identify the recommended software
update method.
•
To download product updates, go to either of the following:
•
◦
Hewlett Packard Enterprise Support Center Get connected with updates page:
www.hpe.com/support/e-updates
◦
Software Depot website:
www.hpe.com/support/softwaredepot
To view and update your entitlements, and to link your contracts and warranties with your
profile, go to the Hewlett Packard Enterprise Support Center More Information on Access
to Support Materials page:
www.hpe.com/support/AccessToSupportMaterials
IMPORTANT: Access to some updates might require product entitlement when accessed
through the Hewlett Packard Enterprise Support Center. You must have an HP Passport
set up with relevant entitlements.
Websites
Website
Link
Hewlett Packard Enterprise Information Library
www.hpe.com/info/enterprise/docs
Hewlett Packard Enterprise Support Center
www.hpe.com/support/hpesc
Contact Hewlett Packard Enterprise Worldwide
www.hpe.com/assistance
Accessing Hewlett Packard Enterprise Support
31
Website
Link
Subscription Service/Support Alerts
www.hpe.com/support/e-updates
Software Depot
www.hpe.com/support/softwaredepot
Customer Self Repair
www.hpe.com/support/selfrepair
Insight Remote Support
www.hpe.com/info/insightremotesupport/docs
Serviceguard Solutions for HP-UX
www.hpe.com/info/hpux-serviceguard-docs
Single Point of Connectivity Knowledge (SPOCK) Storage www.hpe.com/storage/spock
compatibility matrix
Storage white papers and analyst reports
www.hpe.com/storage/whitepapers
Related documents and terminology
For information about:
See:
Locating HPE 3PAR documents
http://www.hpe.com/support/hpesc
Search on the product name "HPE 3PAR StoreServ
Storage." Click the link for your product, and then click
Manuals.
HPE 3PAR storage system software
Storage concepts and terminology
HPE 3PAR StoreServ Storage Concepts Guide
Using the HPE 3PAR Management Console (GUI) to
configure and administer 3PAR storage systems
HPE 3PAR Management Console User's Guide
Using the HPE 3PAR CLI to configure and administer
storage systems
HPE 3PAR Command Line Interface Administrator’s
Manual
CLI commands
HPE 3PAR Command Line Interface Reference
Analyzing system performance
HPE 3PAR System Reporter Software User's Guide
Installing and maintaining the Host Explorer agent to
HPE 3PAR Host Explorer User’s Guide
manage host configuration and connectivity information
Creating applications compliant with the Common
HPE 3PAR CIM API Programming Reference
Information Model (CIM) to manage HPE 3PAR storage
systems
Migrating data from one HPE 3PAR storage system to
another
HPE 3PAR-to-3PAR Storage Peer Motion Guide
Configuring the Secure Service Custodian server to
monitor and control 3PAR storage systems
HPE 3PAR Secure Service Custodian Configuration Utility
Reference
Using the CLI to configure and manage HPE 3PAR
Remote Copy
HPE 3PAR Remote Copy Software User’s Guide
Updating HPE 3PAR operating systems
HPE 3PAR Upgrade Pre-Planning Guide
Identifying storage system components, troubleshooting HPE 3PAR F-Class, T-Class, and StoreServ 10000 Storage
information, and detailed alert information
Troubleshooting Guide
Installing, configuring, and maintaining the HPE 3PAR
Policy Server
HPE 3PAR Policy Server Installation and Setup Guide
HPE 3PAR Policy Server Administration Guide
Planning for HPE 3PAR storage system setup, including hardware specifications, installation considerations,
power requirements, networking options, and cabling information for HPE 3PAR storage systems
HPE 3PAR 7200 and 7400 storage systems
32
Support and other resources
HPE 3PAR StoreServ 7000 Storage Site Planning Manual
For information about:
See:
HPE 3PAR 8000 storage systems
HPE 3PAR StoreServ 8000 Storage Site Planning Manual
HPE 3PAR 10000 storage systems
HPE 3PAR StoreServ 10000 Storage Physical Planning
Manual
HPE 3PAR StoreServ 10000 Storage Third-Party Rack
Physical Planning Manual
HPE 3PAR 20000 storage systems
HPE 3PAR StoreServ 20000 Storage Site Planning Manual
Installing and maintaining HPE 3PAR storage systems
Installing 7200 and 7400 storage systems and initializing HPE 3PAR StoreServ 7000 Storage Installation Guide
the Service Processor
HPE 3PAR StoreServ 7000 Storage SmartStart Software
User’s Guide
Installing 8000 storage systems and initializing the
Service Processor
HPE 3PAR StoreServ 8000 Storage Installation Guide
Maintaining, servicing, and upgrading 7200 and 7400
storage systems
HPE 3PAR StoreServ 7000 Storage Service Guide
Servicing and upgrading 8000 storage systems
HPE 3PAR StoreServ 8000 Storage Service and Upgrade
Guide
Servicing 20000 storage systems
HPE 3PAR StoreServ 20000 Storage Drive Servicing Guide
Troubleshooting 7200 and 7400 storage systems
HPE 3PAR StoreServ 7000 Storage Troubleshooting Guide
Maintaining the Service Processor
HPE 3PAR Service Processor Software User Guide
HPE 3PAR Service Processor Onsite Customer Care
(SPOCC) User's Guide
HPE 3PAR host application solutions
Backing up Oracle databases and using backups for
disaster recovery
HPE 3PAR Recovery Manager Software for Oracle User's
Guide
Backing up Exchange databases and using backups for HPE 3PAR Recovery Manager Software for Microsoft
disaster recovery
Exchange 2007 and 2010 User's Guide
Backing up SQL databases and using backups for
disaster recovery
HPE 3PAR Recovery Manager Software for Microsoft SQL
Server User’s Guide
Backing up VMware databases and using backups for
disaster recovery
HPE 3PAR Management Plug-in and Recovery Manager
Software for VMware vSphere User's Guide
Installing and using the HPE 3PAR VSS (Volume
Shadow Copy Service) Provider software for Microsoft
Windows
HPE 3PAR VSS Provider Software for Microsoft Windows
User's Guide
Best practices for setting up the Storage Replication
Adapter for VMware vCenter
HPE 3PAR Storage Replication Adapter for VMware
vCenter Site Recovery Manager User Guide
Troubleshooting the Storage Replication Adapter for
VMware vCenter Site Recovery Manager
HPE 3PAR Storage Replication Adapter for VMware
vCenter Site Recovery Manager Troubleshooting Guide
Installing and using vSphere Storage APIs for Array
HPE 3PAR VAAI Plug-in Software for VMware vSphere
Integration (VAAI) plug-in software for VMware vSphere User's Guide
HPE 3PAR terminology updates
•
The server previously known as the "InServ" is now called "HPE 3PAR StoreServ Storage
system."
•
The operating system previously known as the "InForm OS" is now called "HPE 3PAR OS."
Related documents and terminology
33
•
The user interface previously known as the "InForm Management Console (IMC)" is now
called "HPE 3PAR Management Console."
•
All products previously known as “3PAR” products are now called "HPE 3PAR" products.
Typographic conventions
Table 1 Document conventions
Convention
Element
Bold text
• Keys that you press
• Text you typed into a GUI element, such as a text box
• GUI elements that you click or select, such as menu items,
buttons, and so on
Monospace text
• File and directory names
• System output
• Code
• Commands, their arguments, and argument values
<Monospace text in angle brackets> • Code variables
• Command variables
Bold monospace text
• Commands you enter into a command line interface
• System output emphasized for scannability
WARNING! Indicates that failure to follow directions could result in bodily harm or death, or in
irreversible damage to data or to the operating system.
CAUTION:
data.
NOTE:
Indicates that failure to follow directions could result in damage to equipment or
Provides additional information.
Required
Indicates that a procedure must be followed as directed to achieve a functional and supported
implementation based on testing at Hewlett Packard Enetrprise.
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product.
If a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at
your convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized
service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website:
www.hpe.com/support/selfrepair
Remote support
Remote support is available with supported devices as part of your warranty or contractual support
agreement. It provides intelligent event diagnosis, and automatic, secure submission of hardware
event notifications to Hewlett Packard Enterprise, which will initiate a fast and accurate resolution
based on your product’s service level. Hewlett Packard Enterprise strongly recommends that
you register your device for remote support.
34
Support and other resources
For more information and device support details, go to the following website:
www.hpe.com/info/insightremotesupport/docs
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To
help us improve the documentation, send any errors, suggestions, or comments to Documentation
Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document
title, part number, edition, and publication date located on the front cover of the document. For
online help content, include the product name, product version, help edition, and publication date
located on the legal notices page.
Documentation feedback
35
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising