How to Install VMware SRM 6.5

How to Install Site Recovery Manager 6.5

Pre-requisites to install Site Recovery Manager 6.5:

  1.  Install the same version of Platform Services Controller,vCenter Server and Site Recovery Manager on both sites(Protected and Recovery site)
  2. Site Recovery Manager can be installed on a dedicated server or on the same system as the vCenter server is installed. SRM requires a supported version of Windows operating system. In case of vCenter Server appliance, You need to install SRM on dedicated windows server.
  3. Make use of fully qualified domain names (FQDN) rather than IP addresses when you install and configure Platform Services Controller, vCenter Server, vSphere Replication and Site Recovery Manager.
  4. You should have Platform Services Controller and vCenter Server ready before proceeding with the install Site Recovery Manager 6.5. Obtain the address of the Platform Services Controller instance for both sites. The Platform Services Controller must be running and accessible during Site Recovery Manager installation.
  5. Obtain the vCenter Single Sign-On administrator username and password for both of the local and remote sites
  6. Make use of centralized NTP servers to synchronize the clock settings of the systems on which Platform Services Controller, vCenter Server,vSphere Replication and Site Recovery Manager Server. Maintain the consistency time between all systems.
  7. Obtain a Windows user account with the appropriate privileges to install and run SRM service. You can configure the Site Recovery Manager service to run under a specified user account. The account can be a local user or a domain user.
  8. Site Recovery Manager requires a database. SRM can be installed either with embedded Embedded vPostgres Database or an external database source like Microsoft SQL or Oracle. If you are using an external database for SRM installation, Site Recovery Manager requires a database source name (DSN) for 64-bit open database connectivity (ODBC). You can create the ODBC system DSN before you run the Site Recovery Manager installer, or you can create the DSN during the installation process
  9. To use Site Recovery Manager with vSphere Replication, deploy the appropriate version of vSphere Replication on both of the protected and recovery sites before you install Site Recovery Manager Server.
  10. Download the Site Recovery Manager 6.5 installation file to a folder on the machine on which to install Site Recovery Manager on both primary site and recovery site.

VMware Site Recovery Manager 6.5 Installation

As we already discussed, SRM can be installed on the same machine as vCenter or on a dedicated server. If you are using vCenter Server appliance, You need to install Site Recovery Manager 6.5 on separate windows server.  I have 2 vCenter servers (one in Production and another one as recovery site (DR site)). We need to run the SRM setup in both protected and recovery site. I will be running the SRM installation on my Protected vCenter first (protection site). Right-click the SRM  6.5 installation file and Run as Administrator to initiate VMware SRM 6.5 installation.
Install Site Recovery Manager 6.5
SRM 6.5 installer file will decompress all the necessary installation files in the temporary folder.
Install Site Recovery Manager 6.5
In the SRM installation wizard, Click on Next to start the installation.
Install Site Recovery Manager 6.5
Select “I agree to the terms in the license agreement” to accept the VMware End User License Agreement. Click Next.

 Install Site Recovery Manager 6.5
Since We are already discussed about the SRM 6.5 installation pre-requisites. Click Next.
Install Site Recovery Manager 6.5
Select the destination folder to install  Site Recovery Manager  6.5 and click Next.
Install Site Recovery Manager 6.5
For SRM 6.5 installation, We need to specify the Platform Services Controller address to register SRM with PSC. You can specify hostname or IP address of PSC during the installation. As a best practice, It is recommended to use FQDN names throughout the installation of all components like vCenter, SRM, vSphere Replication etc. Specify the Single sign-on (SSO) administrative credentials to perform administrative actions on the Platform services controller. Click Next.
Install Site Recovery Manager 6.5
Click on Accept to accept the Platform services controller (PSC) certificate.
Install Site Recovery Manager 6.5
Select the vCenter Server instance from the drop-down to register Site Recovery Manager and click Next. My Production vCenter server is “md-vc-1″
Install Site Recovery Manager 6.5
Specify the  Local Site name for the SRM site. This specified name will appear in SRM interface. By default, vCenter Server address will be used, if you didn’t specify any name during the installation. Enter administrator email address for this site and Select the IP address of the local host from the drop-down to be used by SRM. If you have dual IP address
Enter administrator email address for this site and Select the IP address of the local host from the drop-down to be used by SRM. If you have the dual IP address on the server, Select the appropriate IP address for the SRM installation. Click Next.
Install Site Recovery Manager 6.5
Select the default Site Recovery Manager plug-in identifier (if you are installing SRM with a standard configuration with one protected site and one recovery site) or select Create a Custom Site Recovery Manager Plug-in identifier (when you install Site Recovery Manager in a shared recovery site configuration, with multiple protected sites and one recovery site). In my Lab, I am going to install with standard configuration i.e one Protected and one recovery So selected the option of default SRM
In my Lab, I am going to install with standard configuration i.e one Protected and one recovery So selected the option of default SRM Plug-in. Click Next.
Install Site Recovery Manager 6.5
You can either use the option to automatically generate a certificate or Use Custom certificate file if you have any and click Next.
Install Site Recovery Manager 6.5
Specify the Organization and Organization Unit. Click on Next.
Install Site Recovery Manager 6.5
You can use either the embedded database (vPostgres database) or a custom external database for the SRM 6.5 installation. To use an external database, Select an existing 64-bit DSN from the drop-down menu or Click on DSN setup to create a new 64-bit DSN for SRM database. I am going to use embedded database option for my SRM 6.5 installation. Proceed with the next step
Install Site Recovery Manager 6.5
Provide the data source name, DB username and password.  Leave the remaining settings to default and click Next.
Install Site Recovery Manager 6.5
Select the user account under which to run the Site Recovery Manager Server service and click Next. It can be a Local system account or an Active Directory domain account. Click  Next.
Install Site Recovery Manager 6.5
Click Install to start the SRM installation.It will take few minutes to complete the Site Recovery Manager installation.
Install Site Recovery Manager 6.5The installation will take few minutes to complete.
 Install Site Recovery Manager 6.5
Once the SRM 6.5 installation is completed, Click on Finish.
Install Site Recovery Manager 6.5
Once the installation is completed, you can notice the 2 windows related services “VMware vCenter Site Recovery Manager Server” & VMware vCenter Site Recovery Manager Embedded database” running on the server, where SRM is installed. Ensure both the services are started.
Once installation completed and SRM related services are started, Login to your Protected site vCenter Server using vSphere Web Client. You can notice the Site Recovery Icon will start appearing in the Web Client.
Install Site Recovery Manager 6.5

Comments

Post a Comment

Popular posts from this blog

Avamar falied to take backup of all virtual machine

Recently I encountered an issue where Avamar failed to take backup. Logs stating  insufficient Permission in the host OS 2018-02-19 06:59:56 avvcbimage Error <0000>: [IMG0008] Failed to connect to virtual disk [VMAXDS] VM/VM-000002.vmdk (3014) (3014) Insufficient permissions in the host operating system (Log #2)  We verified the permission on the vCenter but no luck,However on demand backup from local Account is with same level of access is successful. While investigation further we found that there are errors related to DNS, and even some DNS server are getting backed up via avamar. We asked to remove DNS from Avamar back considering VM stun operation during the backup but it did not help to resolve the issue. Later on we found that DNS server which is hardcoded in Avamar was decommission due which Domain ID's were unable to run backup on vCenter
Read more

How to Configure IPsec VPN within VMware NSX Edge

Image
This article shows you how to create an IPsec VPN between a NSX Edge Gateway with a vCloud Director/NSX Manager and a remote Client site. First you need basic details from client so that you can configure IPSec VPN from your end.Like you need Phase 1 and Phase 2 Details. (This document related to NSX Edge 6.3.2) Image Credit VMware Note: NSX Edge supports Main Mode for Phase 1 and Quick Mode for Phase 2. Phase 1 Parameters Phase 1 sets up mutual authentication of the peers, negotiates cryptographic parameters, and creates session keys. The Phase 1 parameters used by NSX Edge are: Main mode TripleDES / AES [Configurable] SHA-1 MODP group 2 (1024 bits) pre-shared secret [Configurable] SA lifetime of 28800 seconds (eight hours) with no kbytes rekeying ISAKMP aggressive mode disabled In 6.3.2 you Can see basic details or you can say this is mixed mode like Phase 1 and Phase 2 they don’t have different tabs or options. Here are details which you have to ...
Read more

vRealize Operations Manager (vROps) 6.2 Configuration – Step-by-Step : Part-1.1

Image
his is my Second blog in the Series of vRealize Operations Manager a.k.a vRops . We will learn how to configure the vROps Appliance and integrate with your infrastructure. For Reading the deployment of the vROps . vRealize Operations Manager (vROps) 6.2 Deployment– Step-by-Step : Part-1 Before Going Through need to keep in mind that like vCops, vRops is also having the UI and ADMIN console. For both URL’s they have different use cases. UI Console gives you access to manage your environment (Add/Remove etc.) Monitor the health risk and lets you explore all the other features here. Even ADMIN console having the very limited but holding big responsibility like System Staus, software update and Support etc. So we will keep in touch with both of them in this part. ADMIN URL : https://fqdn or ip of your vrops appliance/admin/ UI URL         : https://fqdn or ip of your vrops appliance/ui/   or just entering the FQDN or IP will...
Read more