Professional Documents
Culture Documents
Implementation Guide
By Michael Nakamura
Feedback
Hitachi Data Systems welcomes your feedback. Please share your thoughts by sending an email message to SolutionLab@hds.com. Be sure to include the title of this white paper in your email message.
Table of Contents
Tested Solution Components..........................................................................................3 Hardware Components..........................................................................................4 Software Components ...........................................................................................5 Solution Implementation..................................................................................................8 Configure the Storage Area Network.....................................................................8 Configure the Storage Replication Link ...............................................................10 Configure Storage................................................................................................15 Configure vSphere environment ..........................................................................21 Configure Command Control Interface (CCI) for Replication .............................23 Implement Storage Replication for Site Recovery Manager................................29 Configure Storage Replication Adapter with VMware Site Recovery Manager ...31 Other Implementation Actions .............................................................................33 Configuration Files .........................................................................................................34 Hitachi TrueCopy Remote Replication Bundle Files............................................34 Hitachi Universal Replicator Files ........................................................................35 Hitachi ShadowImage Heterogeneous Replication Files.....................................37
1
1
Deploying VMware Site Recovery Manager 5.0 with VMware vSphere 5.0 on Hitachi Virtual Storage Platform
Implementation Guide
Virtualizing a data center with VMware vSphere provides several benefits to IT infrastructures:
Reduce capital expenses through server consolidation Reduce operating expenses through automation to allow a data center to run more efficiently Protect critical applications running on a central infrastructure with features such as VMware High Availability, which reduces planned and unplanned downtime
Expanding data centers across multiple locations provides an opportunity to increase these layers of protection beyond a single data center. VMware vCenter Site Recovery Manager is a business continuity and disaster recovery solution that integrates VMware vSphere infrastructures with data replication on storage systems to protect large sites and business critical applications. It does the following:
Provides centralized management of disaster recovery plans Enables non-disruptive testing Automates site recovery and migration processes
Using an automated and tested recovery plan, a production data center can do a disaster recovery failover in an organized and proven manner. Remote data replication is a key function in building out stable and reliable disaster recovery environments. Replicating data to a remote secondary site represents the most effective insurance policy against a catastrophic failure. Although you can perform data replication at the server level, you can perform data replication more effectively within the storage infrastructure.
2
2 Hitachi Virtual Storage Platform is an integral piece in building out a robust business continuity and disaster recovery solution. VMware vCenter Site Recovery Manager integrates tightly with Hitachi Virtual Storage Platform using the Hitachi Storage Replication Adapter. The advanced functions found in Virtual Storage Platform fulfills the requirements of a virtual infrastructure and provide reliable protection by managing data replication across data centers. This paper's intended use is by IT administrators charged with the storage, deployment, or administration of VMware vSphere infrastructures on Hitachi Virtual Storage Platform and Hitachi Compute Blade 2000. It assumes familiarity with storage area network (SAN)-based storage systems, VMware vSphere, Hitachi data replication technologies, and common IT storage practices.
3
3
The platform for virtualized data centers in local and remote locations:
Two server blades installed with ESXi 5.0 configured in a high availability cluster Virtual machines running on ESXi 5.0 for management and disaster recovery administration. Virtual machines running on ESXi 5.0 protected by storage replication and VMware Site Recovery Manager.
Figure 1
4
4 This describes the hardware and software components required to deploy the solution described in this white paper.
Hardware Components
Table 1 describes the hardware needed to deploy this solution.
Table 1. Solution Hardware
Quantity 2
Configuration
8 8 Gb/sec Fibre Channel ports used 8 600 GB, 10K RPM, SAS disks 8-blade chassis 2 Fibre Channel switch modules 8 1 Gb/sec network ports 2 management modules 8 cooling fan modules 4 power supply modules 2 8 core processor with 64 GB of memory 2 8 core processor with 64 GB of memory
Blade chassis
Hitachi Compute Blade 2000 X57A1 server blades Hitachi Compute Blade 2000 X57A1 server blades
Protected site virtual infrastructure running VMware ESXi 5.0 Recovery site virtual infrastructure running VMware ESXi 5.0
Scale Up Meet increasing demands by dynamically adding processors, connectivity, and capacity in a single unit. Provide the highest performance for both open and mainframe environments. Scale Out Meet multiple demands by dynamically combining multiple units into a single logical system with shared resources. Support increased demand in virtualized server environments. Ensure safe multi-tenancy and quality of service through partitioning of cache and ports. Scale Deep Extend storage value by virtualizing new and existing external storage systems dynamically. Extend the advanced functions of Hitachi Virtual Storage Platform to multivendor storage. Offload less demanding data to external tiers to save costs and to optimize the availability of tier one resources.
5
5 For more information, see Hitachi Virtual Storage Platform on the Hitachi Data Systems website.
A balanced system architecture that eliminates bottlenecks in performance and throughput Configuration flexibility Eco-friendly power-saving capabilities Fast server failure recovery using a N+1 cold standby design that allows replacing failed servers within minutes
For more information, see Hitachi Compute Blade Family on the Hitachi Data Systems website.
Software Components
Table 2 lists the software needed to deploy this solution.
Table 2. Solution Software
Software Hitachi Storage Navigator Hitachi Storage Replication Adapter Hitachi Command Control Interface Hitachi TrueCopy Remote Replication bundle Hitachi Universal Replicator Hitachi ShadowImage Heterogeneous Replication VMware vCenter VMware vSphere ESXi VMware Site Recovery Manager
Version Microcode dependent 02.01.01 01-25-03/11 Note: Ver. 01-24/03/13 or later is required Licensed feature available with Hitachi Virtual Storage Platform Licensed feature available with Hitachi Virtual Storage Platform Licensed feature available with Hitachi Virtual Storage Platform 5.0.0 build 455964 5.0.0 build 469512 5.0 build 474459
6
6 For more information, see TrueCopy Synchronous Remote Replication Software on the Hitachi Data Systems website.
Replication across any distance without significant negative effect on host performance Hitachi Universal Replicator has been successfully used in replication configurations that span thousands of miles. No acknowledgement dependencies from secondary site Hitachi Universal Replicator replicates to a remote site without the performance impact of waiting to acknowledge each individual record. Instead, Hitachi Universal Replicator manages the remote relationship at a controller level. During a disruption of communication to the remote unit or while exceeding the capability of the replication circuit, Hitachi Universal Replicator retains replicated write data in local journals, then updates the write data when the condition is corrected.
There is a potential for some data lag between remote and primary sites, particularly at longer distances. Manage the recovery point objective with the configuration of the data communication lines. When I/O activity at the primary site exceeds the capacity of the communication channel, the data is staged and moved to the secondary site in the same order as it was written at the primary site.
7
7 On Hitachi Virtual Storage Platform, use ShadowImage Heterogeneous Replication to implement clones, a full copy of the primary data. Each clone is available for use by secondary applications. The unique value of working with a clone is that any operation on a clone has no effect on the primary data. Detailed information on using Shadow Image Heterogeneous Replication is in Hitachi Command Control Interface User and Reference Guide (MK-90RD7010).
ESXi 5.0 This is a hypervisor that loads directly on a physical server. It partitions one physical machine into many virtual machines that share hardware resources. vCenter Server This allows management of the vSphere environment through a single user interface. With vCenter, there are features available such as vMotion, Storage vMotion, Distributed Resource Scheduler, high availability, and fault tolerance.
8
8
Solution Implementation
Follow these steps to deploy this solution: 1. Configure the Storage Area Network 2. Configure the Storage Replication Link 3. Configure Storage 4. Configure vSphere environment 5. Configure Command Control Interface (CCI) for Replication 6. Implement Storage Replication for Site Recovery Manager 7. Implement Storage Replication for Site Recovery Manager
Host Protected Site - ESXi 1 Protected Site - ESXi 1 Protected Site - ESXi 2 Protected Site - ESXi 2
Host HBA Number HBA 2 Port 1 HBA 2 Port 2 HBA 2 Port 1 HBA 2 Port 2
Storage 5B 6B 5D 6D 5B 6B 5D 6D
9
9 Table 4 shows the multipath configuration for the recovery site.
Table 4. Recovery Site Multipath Configuration
Host Recovery Site - ESXi 3 Recovery Site - ESXi 3 Recovery Site - ESXi 4 Recovery Site - ESXi 4
Host HBA Number HBA 2 Port 1 HBA 2 Port 2 HBA 2 Port 1 HBA 2 Port 2
Storage Port 5B 6B 5D 6D 5B 6B 5D 6D
In addition, replication requires dedicated Fibre Channel connections between storage systems at the local and the remote site. For this solution, each Hitachi Virtual Storage Platform uses a total of two initiator ports and two RCU target ports. Table 5 shows the storage replication paths and zoning between storage systems on each site.
Table 5. Recovery Site Multipath Configuration
2B Initiator
VSP1_2B_VSP2_2D
2D RCU Target
1B Initiator
VSP2_1B_VSP1_1D
1D RCU Target
2B Initiator
VSP2_2B_VSP1_2D
2D RCU Target
10
10 Figure 2 shows the storage network configuration of the virtual infrastructure at each site.
Figure 2
Storage Replication Technology Hitachi TrueCopy Heterogeneous Remote Replication Bundle Hitachi Universal Replicator
11
11 The following describes how to configure the storage replication link between the local and remote storage systems for the respective replication technologies.
Hitachi TrueCopy Heterogeneous Remote Replication Bundle Hitachi Universal Replicator Creating Journal Groups for Hitachi Universal Replicator
12
12 iv. Select the Default check box for the Path Group ID. v. Click the local storage system port and its corresponding pair port in the MCU-RCU Path area. This solution uses the following MCU - RCU port configuration: 1B - 1D, 2B - 2D (3) Set options. i. ii. Click Option. Type values in Minimum Paths, RIO MIH Time (sec.) and Round Trip Time (ms).
iii. Click Set. 4. Accept the changes and complete the changes. (1) Click Apply. A confirmation dialog box opens. (2) Click OK to confirm applying the changes. Another confirmation dialog box opens. (3) Click OK. Repeat these steps on the remote storage system to add an RCU (Fibre) connection for reverse replication. This is necessary for VMware Site Recovery Manager to perform failback operations.
13
13 (5) Click LDKC#00 on the navigation tree. (6) Right-click the blank space on the left pane. A menu displays. 3. Add the DKC connections. (1) Click DKC Operation and then click Add DKC from the list. The Add DKC dialog box opens. (2) Provide the following information in the Add DKC dialog box: i. ii. Type the serial number for the remote storage system in S/N. Click the LDKC of the remote storage system from the LDKC list.
iii. Click 6 (VSP) from the Controller ID list. iv. Click the local storage system ports and its corresponding pair-port in the M-R path area. (3) Set options. i. ii. Click Option. Type values in Minimum Paths and RIO MIH Times (sec).
iii. Click Set. 4. Accept the changes and complete the changes. (1) Click Apply. A confirmation dialog box opens. (2) Click OK to confirm applying the changes. Another confirmation dialog box opens. (3) Click OK. Repeat these steps on the remote storage system to add a DKC connection for reverse replication. This is necessary for VMware Site Recovery Manager to perform failback operations.
14
14
15
15
Configure Storage
This is how to configure your storage for this solution using Hitachi Dynamic Provisioning on Hitachi Virtual Storage Platform. The storage configuration for this solution includes the following:
This solution uses a dynamic provisioning pool comprised of a single RAID group with eight 600 GB 10k RPM SAS drives in a RAID-6 (6D+2P) configuration for each storage system. To increase performance and capacity needs of your virtual environment, add more RAID groups to the dynamic provisioning pool. Using a RAID-6 configuration lowers the risk of data loss or pool failure, which is a primary concern for virtual machines protected by VMware Site Recovery Manager. Figure 3 shows the configuration for the dynamic provisioning pool on each storage system.
16
16
Figure 3
This solution provisions three LDEVs to the VMware infrastructure at both sites for:
Management (VMFS datastore) Hitachi TrueCopy or Hitachi Universal Replicator replicated datastore (VMFS datastore) Command device (raw device mapping LUN)
17
17 The creation and presentation of the LDEVs in Figure 3 on the storage system involves the following steps: 1. Create Host Groups 2. Create LDEVs in a RAID Group 3. Create Dynamic Provisioning Pools 4. Create LDEVs within a Dynamic Provisioning Pool 5. Create a Command Device The following describe in detail how to configure your storage for this solution.
54 Support Option for the EXTENDED COPY command 63 Support option for vStorage APIs based on T10 standards
Following recommended practice, these Host Mode Options allow the LDEV to take advantage of VMware VAAI features. 7. Click Add. The Selected Host Groups area populates. 8. Click Finish. The Create Host Groups window opens. 9. Click Apply.
18
18
19
19
20
20
21
21
Database Microsoft Windows 2008 R2 virtual machine running Microsoft SQL Server 2008. This serves database instances for VMware vCenter Server 5.0 and VMware Site Recovery Manager 5.0. VMware vCenter Microsoft Windows 2008 R2 virtual machine running VMware vCenter Server 5.0 for overall management of the virtualized infrastructure. VMware Site Recovery Manager Microsoft Windows 2008 R2 virtual machine running VMware Site Recovery Manager, Hitachi Storage Replication Adapter, and command control interface from Hitachi. This handles replication communication between the virtual and storage infrastructure as well as site-to-site communications between Site Recovery Manager instances to facilitate an integrated disaster recovery process. Install VMware Site Recovery Manager 5.0 prior to installing Hitachi Storage Replication Adapter. This action permits Site Recovery Manager to register the installed adapter properly.
22
22
Command device (raw device mapping LUN) Present to the VMware Site Recovery Manager virtual machine as a physical Raw Device Mapping (RDM) disk. You cannot map command devices as virtual RDMs.
Figure 4
23
23
24
24
Storage System Command devices and Hitachi TrueCopy or Hitachi Universal Replicator volumes (P-VOL and S-VOL) Server Hitachi Open Remote Copy Manager (HORCM), configuration definition files (for example, horcm0.conf), and command control interface commands
The Hitachi Open Remote Copy Manager operates as a daemon process on the VMware Site Recovery Manager virtual machines. When activated, Open Remote Copy Manager refers to the configuration definition files. The instance communicates with the storage sub-system and remote servers. Modify the services file in the C:\Windows\System32\drivers\etc folder to register the port name and number for each Open Remote Copy Manager instance on each server. The port name entries for Open Remote Copy Manager in the services file must be the same on all the servers. For example, if the service number for port name horcm0 is 11000/udp, the service number for port name horcm1 must be 11001/udp in the services file on the Site Recovery Manager server at the local and the remote site.
25
25 Figure 5 shows a two-server, two-HORCM instance configuration used with command control interface to manage TrueCopy or Universal Replicator replication.
Figure 5
Hitachi TrueCopy and Hitachi Universal Replicator require two instances of Open Remote Copy Manager to be operational.
One instance manages the P-VOLs, The other instance manages the S-VOLs.
The Open Remote Copy Manager configuration file defines the communication path and the logical units to be controlled. Each instance has its own configuration file saved in the C:\Windows directory. The content of the horcm0.conf file and the horcm1.conf file used to define a TrueCopy pair are available in Hitachi TrueCopy Remote Replication Bundle Files." The content of the horcm0.conf file and the horcm1.conf file used to define a Universal Replicator pair are available in "Hitachi Universal Replicator Files."
26
26 After adding the port name entries and defining the configuration files, start the Hitachi Open Remote Copy Manager instance. At the command prompt, type the following: cd c:\HORCM\etc horcmstart.exe * An asterisk [*] is used in place of the instance number in the command. For example, for the server containing horcm0.conf, type horcmstart.exe 0. After executing the instructions described in the previous section at both sites, Open Remote Copy Manager instances should be running on the Site Recovery Manager servers at both sites. Verify the pair relationship by running the pairdisplay command from the horcm0 instance on the primary site's Site Recovery Manager server: pairdisplay.exe -g <grp> -IH<HORCM instance #> -fcx Initially, the volumes are in simplex (SMPL) mode. The volumes are not paired and synchronized until running the paircreate command. Figure 6 shows a pairdisplay output of the TrueCopy pair defined in "Hitachi TrueCopy Remote Replication Bundle."
Figure 6
Figure 7 shows a pairdisplay output of the Universal Replicator pair defined in "Hitachi Universal Replicator."
Figure 7
For more information about setting up the Open Remote Copy Manager instances and Open Remote Copy Manager configuration file, see the Hitachi Command Control Interface (CCI) Users and Reference Guide that accompanies the Hitachi Command Control Interface software.
27
27
28
28
Figure 8
After adding the port name entries and the defining the configuration files, start the Hitachi Open Remote Copy Manager instance. At a command prompt, type the following: cd c:\HORCM\etc horcmstart.exe * An asterisk [*] is substituted for the instance number in the command. For example, to start the remote server containing horcm1.conf and horcm2.conf, type horcmstart.exe 1 2. Verify the pair relationship by running the pairdisplay command from the horcm1 instance on the recovery site's Site Recovery Manager server: pairdisplay.exe -g <grp> -IM<HORCM instance #> -fcx Initially, the volumes are in simplex (SMPL) mode. The volumes do not pair and synchronize until running the paircreate command.
29
29 Figure 9 shows a pairdisplay output of the ShadowImage pair defined in "Hitachi ShadowImage Heterogeneous Replication ."
Figure 9
Figure 10
30
30 Figure 11 shows the command and the output of a Universal Replicator pair creation based on the HORCM configuration files in "Hitachi Universal Replicator Files."
Figure 11
Figure 12
31
31
Figure 13
3. In the Array Managers pane, click the local site and click Add Array Manager. The Add Array Manager wizard opens. 4. Type a Display Name, click RAID Manager Storage Replication Adapter from the SRA Type list, and then click Next.
32
32 5. In the Connection to HORCM Server window, add the following connection parameters: (1) For HORCMINST and IP Address of HORCM(CCI) Server, type the following: HORCMINST=X For X, use the HORCM instance number. For example, in Figure 14, shows adding the Array Manager to the primary site, HORCMINST=0 was typed in the box.
Figure 14
The parameters are case-sensitive. Always use ALL CAPS. (2) Type the Username and Password.
If user authentication is not configured on the command device, type user for Username and password for Password. If user authentication is configured on the command device, use your user name and password.
(3) Click Next. The wizard says Array Manager was added successfully. (4) Click Finish.
33
33 6. Enable the use of the array pairs. (1) Click one of the array managers and click the Array Pairs tab. (2) Click Enable to use the array pair with VMware Site Recovery Manager. (3) Click the Devices tab to confirm that Site Recovery Manager reports the storage replication correctly. Figure 15 shows a Site Recovery Manager environment configured to monitor a TrueCopy and Universal Replicator pair. If the storage replication status does not report correctly, verify the pair relationship as follows: 1. Use the pairdisplay command with command control interface. 2. Refresh the array pair by clicking Refresh (circled in red in Figure 15).
Figure 15
Protect your virtual machines on the storage replicated datastore Automate the disaster recovery process
For more information about setting up Site Recovery Manager, see the Site Recovery Manager Administration Guide (http://www.vmware.com/support/pubs/ srm_pubs.html).
34
34
Configuration Files
These are the configuration files you need for this implementation.
HORCM_MON Contains information needed to monitor a HORCM instance such as IP address, HORCM instance or service, pooling interval for monitoring paired volumes, and timeout period for communication with remote server HORCM_CMD Contains device path information about the command device HORCM_LDEV Defines the storage sub-system device address for the paired logical volume names HORCM_INST Network address of the remote server.
Copy horcm0.conf, shown in Figure 16, to the C:\Windows folder on the Site Recovery Manager server at the local site. Copy horcm1.conf, shown in Figure 17, to the C:\Windows folder on the Site Recovery Manager server at the remote site. Use the IP addresses and serial numbers for your environment in the configuration files.
Figure 16
35
35
Figure 17
HORCM_MON Contains information needed to monitor a HORCM instance such as IP address, HORCM instance or service, pooling interval for monitoring paired volumes, and timeout period for communication with remote server HORCM_CMD Contains device path information about the command device HORCM_LDEV Defines the storage sub-system device address for the paired logical volume names HORCM_INST Network address of the remote server
Copy horcm0.conf, as shown in Figure 18, to C:\Windows on the Site Recovery Manager server at the local site. Copy horcm1.conf, as shown in Figure 19, to C:\Windows on the Site Recovery Manager server at the remote site. Use the IP addresses and serial numbers for your environment in the configuration files.
36
36
Figure 18
Figure 19
37
37
HORCM_MON Contains information needed to monitor a HORCM instance such as IP address, HORCM instance or service, pooling interval for monitoring paired volumes, and timeout period for communication with remote server HORCM_CMD Contains device path information about the command device HORCM_LDEV Defines the storage sub-system device address for the paired logical volume names HORCM_INST Network address of the remote server
This pair definition uses the TrueCopy pair's S-VOL as the ShadowImage pair's PVOL and modifies the TrueCopy horcm1.conf configuration file in Hitachi TrueCopy Remote Replication Bundle Files. Only specify mirror unit numbers (MU#) when defining ShadowImage pairs. Only initiate ShadowImage replication after establishing TrueCopy replication. Copy the horcm1.conf (Figure 20) and horcm2.conf (Figure 21) configuration files to C:\Windows on the Site Recovery Manager server at the remote site. Use the IP addresses and serial numbers for your environment in the configuration files.
38
38
Figure 20
Figure 21
Corporate Headquarters 750 Central Expressway, Santa Clara, California 95050-2627 USA www.HDS.com Regional Contact Information Americas: +1 408 970 1000 or info@HDS.com Europe, Middle East and Africa: +44 (0) 1753 618000 or info.emea@HDS.com Asia-Pacific: +852 3189 7900 or hds.marketing.apac@HDS.com
Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries. All other trademarks, service marks, and company names in this document or website are properties of their respective owners.
Notice: This document is for informational purposes only, and does not set forth any warranty, expressed or implied, concerning any equipment or service offered or to be offered by Hitachi Data Systems Corporation. Hitachi Data Systems Corporation 2012. All Rights Reserved. AS-130-00 March 2012