Resiliency Replication Appliance Installation Guide Version 7.2
DISCLAIMER IBM believes that the information in this publication is accurate as of its publication date. The information is subject to change without notice. COPYRIGHT Copyright IBM Corporation 2017. All Rights Reserved. Printed September 2017. Use, copy, and distribution of any IBM software described in this publication needs an applicable software license. No part of this product or document may be reproduced, stored in a retrieval system, or transmitted, in any form by any means, electronic, mechanical, photocopy, recording, or otherwise, without prior written authorization of IBM Corporation and its licensers, if any.
CONTENTS PREFACE... 4 Introduction... 4 Purpose... 4 Audience... 4 Conventions... 4 Acronyms... 4 IBM RESILIENCY ORCHESTRATION ARCHITECTURE... 6 PREREQUISITES... 7 AWS Prerequisites... 7 VMware Prerequisites... 7 COMPATIBILITY INFORMATION... 9 Supported Platforms... 9 Supported Browsers... 9 File Replication Appliance... 10 Limitations... 10 1. DEPLOYMENT OF REPLICATION APPLIANCE OVA... 12 Deployment Procedure... 12 2. DEPLOYMENT OF REPLICATION APPLIANCE AMI... 15 3. DEPLOYMENT OF PROXY REPLICATION APPLIANCE AMI... 17
Preface Introduction Defining, Deploying, and Managing application continuity and recovery to the cloud, which is simple, seamless, and SLA driven from VMware VM to AWS cloud. Purpose IBM Resiliency Orchestration is an ideal option for enterprises and service providers who are looking to build a cloud data center on Amazon Web Services (AWS) platform. It eases out the process as well as reduces the cost in terms of infrastructure investment, while ensuring optimal performance. It can be used for any application environment including the following common workloads that are moving into the cloud: Business critical and mission critical applications Batch Analytic applications Dev/Test workloads Virtualized application environment Audience This manual is for administrators who are responsible for installation and configuration of IBM Resiliency Replication Appliance Software. Conventions Typeface/Font Boldface Italic Courier New Usage Boldface font is used in table headings and in paragraphs, to convey especially strong events. Italics are used to emphasis special information, or additional information and examples. Terminal input and output. Acronyms Acronyms ADC VM IP OVF OVA LAN Definition Application Defined Continuity Virtual Machine Internet Protocol Open Virtualization Format Open Virtualization Appliance Local Area Network
Acronyms RAM ROM URL NIC AMI VPC Definition Random Access Memory Read Only Memory Uniform Resource Locator Network Interface Card Amazon Machine Image Virtual Private Cloud
IBM Resiliency Orchestration Architecture IBM Resiliency Orchestration Deployment architecture consists of IBM Resiliency Orchestration Server and Replication Appliance, which are installed in the On Premise data center, which interfaces with the VMware vsphere infrastructure. A Replication Appliance is deployed in the VPC of your AWS account, and interfaces with AWS. The IBM Resiliency Orchestration Server connects to vsphere for discovering the applications and captures the application s performance characteristics like CPU, memory, and disk I/O. Once the application s characteristics is captured, the intelligent resource optimizer powered by IBM Application Defined Continuity platform analyzes the application and recommends the optimum resources that needs to the provisioned on the cloud based on the chosen continuity plan.
Prerequisites AWS Prerequisites The following are the AWS prerequisites: Support only for Windows 2008/2012, RHEL 5x, RHEL 6x, and RHEL 7x. Create a specific user for AWS to access Amazon services. Provide the user full permission on VPC, EC2, and S3. On Cloud side file system point should be double the size of the On Premise file system mount point. Create VPC, configure the VPN gateway, and test the on premise to AWS communication link. Launch Replication Appliance instance on AWS VPC. Launch IBM Resiliency Orchestration Server on AWS VPC. Enable internet on IBM Resiliency Orchestration and Replication Appliance Server on AWS Cloud. For AWS related information, refer to http://docs.aws.amazon.com/awsec2/latest/userguide/vmimportprerequisites.html VMware Prerequisites The following are the VMware prerequisites: The Host is ESX/ESXi 5.0 or later. The virtual machine owning the disks to be tracked is hardware version 7 or 8. I/O operations go through the ESX/ESXi storage stack. So supports NFS, as is RDM in virtual compatibility mode; however RDM do not support in physical compatibility mode. Supports VMFS, whether backed by SAN, iscsi, or local disk. The CBT is enabled on the virtual machine. For enabling CBT, refer to the link https://kb.vmware.com/selfservice/microsites/search.do?language=en_us&cmd=displaykc &externalid=1031873. Refer to https://kb.vmware.com/selfservice/microsites/search.do?language=en_us&cmd=displaykc &externalid=1031873 to install the VMware tool on the virtual machine. Virtual machine storage cannot be (persistent or nonpersistent) independent disk, meaning unaffected by snapshots. The virtual disk is located on a VMFS volume, backed by SAN, iscsi. The virtual machine is with zero (0) snapshots when CBT is enabled, for a clean start. End user need not create any snapshots when the VM is protected by IBM Product.
The CBT is enabled and VMware tool should be installed in the VM, which is protected. For Replication Appliance, the disk space On Cloud should be twice the disk space On Premise. The VM should have at least 500MB of free space in the root volume prior to starting provisioning/failover test exercise/failover. The file system mount point configured should be equal to or greater than the VMware VMs size under the application stack. Concurrent conversion limit of the AWS account is greater than the maximum number of VMs configured in AppStack.
Compatibility Information Supported Platforms Hypervisors The following Hypervisors are supported: VMware ESXi 5.0 and higher. Virtual Machine hardware version 8 and 9. Cloud The following AWS cloud service is supported: Amazon Web Services VPC Guest OS The following Operating Systems are supported: Linux (64-bit) RHEL 5x, 6x (RHEL 6.0 is not supported by AWS), 7x Windows 64 Windows Server 2008, 2012 Supported Browsers IBM Resiliency Orchestration is compatible with the following browsers: Google Chrome 51.0.2704 (released on 2016-05-25) for OS X and Windows. Mozilla Firefox 46 (released on 2016-04-26) for OS X and Windows.
File Replication Appliance Version: 6.4.0 OS: CentOS (64 bit) CPU: 2 vcpu s Memory: 8 GB HDD: 22 GB Note: You can change the configuration of Replication Appliance based on the current infra and workload continuity plan. Prepackaged OVA comes with the above mentioned specification which are the minimum resource requirement for Replication Appliance. One Replication Appliance is required per site (AWS and VM infra ) For high load utilization, the following resource configuration in terms storage for Replication Appliance is recommended: On Premise Disk Space = (no of VMs) x (size of each VM) On Cloud Disk Space = (no of VMs) x (size of each VM) x 2 Limitations The following are the limitations of Replication Appliance Server: Once Replication Appliance is discovered, you cannot increase the size of the mount point on Replication Appliance Server. While provisioning, you cannot add or use the new mount point on Replication Appliance Server. The minimum configuration of Replication Appliance Servers is mentioned in the following table. IBM Resiliency Orchestration Replication Appliance On Premise 2 CPU, 8 GB RAM, 30 GB Storage 30 GB Storage Extra Storage 45 GB ((3VM)* 5 GB) 3 Servers The configuration for On Premise servers is as follows: 2 Linux servers (1 CPU, 4 GB RAM, and 5 GB Storage) A Windows server (1 CPU, 4 GB RAM, and 5 GB Storage) AWS 2 CPU, 8 GB RAM, 30 GB Storage30GB Storage Extra Storage 45 GB ((3 VM)* 5 GB*2) The configuration for AWS servers is as follows: 2 Linux servers (1 CPU, 4 GB RAM, and 5 GB Storage) A Windows server (1 CPU, 4 GB RAM, and 5 GB Storage)
Network Link Network Requirement Ports Internet Explorer Hypervisor On Premise Dual Network Card IP Address VMware ESX 5.0 or higher AWS Shared 1 MBPS VPC VPN gateway 45000, 46000, and 46001 (Also 1099 for CBT) TCP port Chrome 36 or higher or Mozilla Firefox 28 or higher
1. Deployment of Replication Appliance OVA This chapter describes the deployment procedure to generate Replication Appliance OVA. Deployment Procedure You need to perform the following steps to generate Replication Appliance OVA: 1. Download the IBM Resiliency Orchestration OVA file from FTP location (ftp1.sanovi.com or ftp1.sanovi.com) and save it in your computer. 2. Log in to vcenter using the VMware vsphere Client. 3. In the Navigation pane, select Data Center for IBM Resiliency Orchestration Replication Appliance Server deployment. 4. Select File Deploy OVF Template. 5. The Deploy OVF Template window displays. 6. In the Source pane, browse to the location where Replication Appliance OVA OVF10.ova is located, choose the file, and then click Open. 7. In the OVF Template Details pane, verify the details, and then click Next. 8. In the End User License Agreement pane, read the license agreement, and then click Accept. 9. In the Name and Location pane, enter the name for the VM and select the Data Center where you need to deploy Replication Appliance OVA. 10. In the Host/Cluster pane, choose the required host, cluster, or resource pool, and then click Next. 11. In the Datastore pane, specify the location to save Resiliency Orchestration VM files, and then click Next. 12. In the Disk Format pane, choose one of the following radio buttons: a. Thin Provisioned format: To allocate storage on demand as data is written to disk. b. Thick Provisioned (Lazy Zeroed) format: To allocate storage immediately in thick format. c. Thick Provisioned (Eager Zeroed) format: To allocate storage in thick format. This procedure to create disk can take longer duration. 13. Click Next to create disks.
14. In the Network Mapping pane, choose your network and click Next. 15. In the IP Address Allocation pane, leave the fields blank for DHCP, or enter the values for static IP. 16. Click Next. 17. In the Ready to complete pane, verify the options selected, and click Finish. 18. Power on VM when the upload is completed. The default credential, username and password, are root and Sanovi123. After Replication Appliance OVA deployment, log in to the Replication Appliance machine and configure the following parameters: 1. Edit the PanacesAgentGeneric.cfg file in the $EAMSROOT/DRMAgents/installconfig folder. You need to enter the IP address of IBM Resiliency Orchestration Server as the Master Server address, secondary Resiliency Orchestration Server as the Slave Server address and Local IP as the agent node, as shown in the following snippet: PANACES_MASTER_SERVER_ADDRESS=<Resiliency Orchestration IP> PANACES_SLAVE_SERVER_ADDRESS=<Secondary Resiliency Orchestration_IP > PANACES_AGENT_NODE_ADDRESS=<LOCAL_IP> 2. Edit the PanacesAgentGeneric.cfg file in the $EAMSROOT/SRA/installconfig folder. You need to enter the IP address of IBM Resiliency Orchestration Server as the Master Server address, secondary Resiliency Orchestration Server as the Slave Server address and the Local IP as the agent node, as shown in the following snippet: PANACES_MASTER_SERVER_ADDRESS=<Resiliency Orchestration IP> PANACES_SLAVE_SERVER_ADDRESS=<Secondary Resiliency Orchestration_IP> PANACES_AGENT_NODE_ADDRESS=<LOCAL_IP> 3. Edit the sra_env file in the $EAMSROOT/SRA/bin folder. You need to enter the Local IP as the Server IP, as shown in the following snippet: RMI_SERVER_IP=<local_IP> 4. Edit the svrdiskresources.cfg file in the $EAMSROOT/SRA/installconfig folder. You need to configure the FileSystem Mount point in the svrdiskresources.cfg file with comma separated values, as shown in the following snippet: svr.disk.path=/<mountpath_1>,/<mountpath_2>
The FileSystem Mount point configured should be equal to or greater than the VMware Vms size under the application stack, and on On Cloud side FileSystem, Mount point should be double the size of the On Premise FileSystem Mount point. 5. In the $EAMSROOT/SVR/bin folder, edit the svr_env file. You need to enter the Local IP as the Server IP, as shown in the following snippet: RMI_SERVER_IP=<local_IP> 6. Configure the SSH_PATH in /opt/pfr/installconfig/pfrconfiguration.cfg, as shown in the following snippet: SSH_PATH = "/usr/bin/ssh -i <Pem file location> For Example: SSH_PATH = "/usr/bin/ssh -i /opt/locationofpem/demo_sra.pem" The following are the steps for starting all the process in Replication Appliance Server: 1. Run the SVRService.sh file in the $EAMSROOT/SVR/bin folder to start the SVR service. 2. Run the SRAAgent.sh file in the $EAMSROOT/SRA/bin folder to start Replication Appliance Agent. 3. Run the PFR.sh file in the /opt/pfr/bin folder to start the PFR service. 4. Run the PFRAgent.sh file in the $EAMSROOT/DRMAgents folder to start PFR Agent.
2. Deployment of Replication Appliance AMI The Replication Appliance AMI will be shared to you from IBM Account to your account. You can launch the Replication Appliance instance using the Replication Appliance AMI, and perform the following steps for configuring the AWS Replication Appliance: 1. Log in to the Replication Appliance machine using a password file (.pem file), which is created when you launch the Replication Appliance instance. Each availability zone where VM needs to be replicated requires minimum one Replication Appliance installed. 2. Edit the PanacesAgentGeneric.cfg file in the $EAMSROOT/SRA/installconfig folder. You need to enter the IP address of IBM Resiliency Orchestration Server as the Master Server address, secondary Resiliency Orchestration Server as the Slave Server address and Local IP as the agent node, as shown in the following snippet: PANACES_MASTER_SERVER_ADDRESS=<Resiliency Orchestration_IP> PANACES_SLAVE_SERVER_ADDRESS=<Secondary Resiliency Orchestration_IP> PANACES_AGENT_NODE_ADDRESS=<LOCAL_IP> 3. Edit the sra_env file in the $EAMSROOT/SRA/bin folder. You need to enter Local IP as Server IP, as shown in the following snippet: RMI_SERVER_IP=<local_IP> 4. Edit the svrdiskresources.cfg file in the $EAMSROOT/SRA/installconfig folder. You need to configure the file system mount point in the svrdiskresources.cfg file with comma separated values, as shown in the following snippet: svr.disk.path=/<mountpath_1>,/<mountpath_2> The file system mount point configured should be double the size of the On Premise file system mount point. 5. Edit the panacesagentgeneric.cfg file in the $EAMSROOT/DRMAgents/installconfig folder. You need to enter the IP address of the Resiliency Orchestration as the Master Server address, Secondary Resiliency Orchestration as the Slave Server address and the Local IP as the agent node. PANACES_MASTER_SERVER_ADDRESS=<Resiliency Orchestration_IP> PANACES_SLAVE_SERVER_ADDRESS=<Secondary Resiliency Orchestration_IP> PANACES_AGENT_NODE_ADDRESS=<LOCAL_IP>
6. Perform the following steps for starting all the process in Replication Appliance Server: 1. Run the SRAAgent.sh file in the $EAMSROOT/SRA/bin folder to start the Replication Appliance Agent. 2. Run the PFR.sh file in the /opt/pfr/bin folder to start the PFR service. 3. Run the PFRAgent.sh file in the $EAMSROOT/DRMAgents folder to start the PFR Agent. 7. Attach Elastic IP for SRA instance, which is created from SRA AMI.
3. Deployment of Proxy Replication Appliance AMI The Proxy Replication Appliance AMI will be shared with you from IBM Account to your account. You need to launch the Proxy Replication Appliance instance and perform the following steps to deploy proxy Replication Appliance AMI: 1. Log in to Proxy Replication Appliance machine using password file (.pem file), which is created when you launch the Proxy Replication Appliance instance. Note: While launching the SRA instance in AWS, it is recommended to select the check box enabling encryption of the volumes to enable security of data at rest. 2. Edit the PanacesAgentGeneric.cfg file in the $EAMSROOT/SRA/installconfig folder. You need to enter the IP address of IBM Resiliency Orchestration Server as the Master Server address, Secondary Resiliency Orchestration Server as the Slave Server address and Local IP as the agent node, as shown in the following snippet: PANACES_MASTER_SERVER_ADDRESS=<Resiliency Orchestration Server_IP> PANACES_SLAVE_SERVER_ADDRESS=<Secondary Resiliency Orchestration Server_IP> PANACES_AGENT_NODE_ADDRESS=<LOCAL_IP> 3. Edit the sra_env file in the $EAMSROOT/SRA/bin folder. You need to enter Local IP as Server IP, as shown in the following snippet: RMI_SERVER_IP=<local_IP> 4. Run the SRAAgent.sh file in the $EAMSROOT/SRA/bin folder to start the Replication Appliance Agent and all the process in Replication Appliance Server.