How To Find Site Recovery Manager Version

This post volition walk through an inplace upgrade of VMware Site Recovery Managing director (SRM) to version 8.ane, which introduces support for the vSphere HTML5 client and recovery / migration to VMware on AWS. Read more near what'south new in this blog post. The upgrade is relatively simple but we need to cross-bank check compatibility and perform validation tests afterward running the upgrade installer.

Planning

• The Site Recovery Manager upgrade retains configuration and information such equally recovery plans and history just does non preserve any avant-garde settings
• Protection groups and recovery plans besides need to be in a valid land to be retained, whatever invalid configurations or non migrated
• Check the upgrade path here, for Site Recovery Manager viii.1 we tin can upgrade from 6.ane.2 and afterwards
• If vSphere Replication is in apply and then upgrade vSphere Replication first, following the steps outlined here
• Site Recovery Manager eight.1 is compatible with vSphere half dozen.0 U3 onwards, and VMware Tools 10.1 and onwards, meet the compatibility matrices page here for full details
• Ensure the vCenter and Platform Services Controller are running and available
• In Site Recovery Manager 8.1 the version number is decoupled from vSphere, however check that yous do not need to perform an upgrade for compatibility
• For other VMware products check the product interoperability site hither
• If y'all are unsure of the upgrade order for VMware components run into the Order of Upgrading vSphere and Site Recovery Manager Components folio here
• Brand a note of any advanced settings you may have configured nether Sites > Site > Manage > Advanced Settings
• Ostend you lot take Platform Services Controller details, the ambassador@vsphere.local password, and the database details and countersign

Download the VMware Site Recovery Manager 8.i.0.4 self extracting installer hither to the server, and if applicative; the updated Storage Replication Adapter (SRA) – for storage replication. Review the release notes hither, and SRM upgrade documentation centre hither.

Database Backup

Before starting the upgrade make sure y'all take a backup of the embedded vPostgres database, or the external database. Full instructions tin be found hither, in summary:

• Log into the SRM Windows server and end the VMware Site Recovery Manager service
• From command prompt run the post-obit commands, replacing the db_username and srm_backup_name parameters, and the install path and port if they were changed from the default settings

                                                            cd C:\Plan Files\VMware\VMware vCenter Site Recovery Manager Embedded Database\bin                                                    

                                                            pg_dump -Fc --host 127.0.0.i --port 5678 --username=db_username srm_db >srm_backup_name                                                                      

• If you need to restore the vPostgres database follow the instructions here

In addition to backing up the database check the health of the SRM servers and confirm there are no pending reboots. Log into the vSphere web client and navigate to the Site Recovery department, verify there are no pending cleanup operations or configuration bug, all recovery plans and protection groups should be in a Ready state.

Process

As identified in a higher place, vSphere Replication should exist upgraded earlier Site Recovery Manager. In this case we are using Nimble storage replication, so the Storage Replication Adapter (SRA) should be upgraded offset. Download and run the installer for the SRA upgrade, in near cases it is a simple side by side, install, stop.

Nosotros can now commence the Site Recovery Managing director upgrade, it is advisable to take a snapshot of the server and ensure backups are in place. On the SRM server run the executable downloaded earlier.

• Select the installer language and click Ok, and so Next
• Click Next on the patent screen, accept the EULA and click Next again
• Double-check you have performed all pre-requisite tasks and click Next
• Enter the FQDN of the Platform Services Controller and the SSO admin password, click Next
• The vCenter Server address is auto-populated, click Side by side
• The administrator email address and local host ports should once more be automobile-populated, click Next
• Click Yeah when prompted to overwrite registration
• Select the appropriate certificate pick, in this example keeping the existing certificate, click Next
• Check the database details and enter the countersign for the database account, click Adjacent
• Configure the service account to run the SRM service, once more this volition exist retain the existing settings by default, click Next
• Click Install and Terminate one time consummate

Mail service-Upgrade

After Site Recovery Manager is upgraded log into the vSphere client. If the Site Recovery option does not announced immediately you may need to articulate your browser cache, or restart the vSphere client service.

On the summary page ostend both sites are connected, y'all may need to reconfigure the site pair if yous encounter connection bug.

Validate the recovery plan and run a test to confirm there are no configuration errors.

The test should complete successfully.

I can besides check the replication condition and Storage Replication Adapter status.

This postal service will walk through the configuration of Site Recovery Manager; we'll protect some virtual machines with a Protection Group, and then fail over to the DR site using a Recovery Program. The pre-requisites for this post are for Site Recovery Manager (SRM) and the Storage Replication Adapter (SRA) to exist installed at both sites forth with the corresponding vSphere infrastructure, and replication to exist configured on the storage array. Information technology is too possible to use vSphere Replication, for more information come across the previous posts referenced beneath.

Role 1 – Nimble Storage Integration with SRM

Part 2 – Site Recovery Manager Install Guide

Part 3 – Site Recovery Director Configuration and Failover Guide

Site Recovery Director now has integration with the HTML5 vSphere client, see VMware Site Recovery Manager 8.10 Upgrade Guide for more data.

Before creating a Recovery Plan ensure that you have read the documentation listed in the installation guide above and take the required components for each site. Yous should likewise brand further pattern considerations around compute, storage, and network. In this mail service we will exist using storage based replication and stretched VLANs to ensure resource are bachelor at both sites. If yous desire to assign a different VLAN at the failover site then you can utilise SRM to reconfigure the network settings, see this department of the documentation centre.

Configuring SRM

Log into the vSphere spider web customer for the primary site as an ambassador, and click the Site Recovery Manager icon.

The offset pace is to pair the sites together. When sites are paired either site tin can be configured as the protected site.

• Click Sites, both installed sites should be listed, select the primary site.
• On the Summary tab, in the Guide to configuring SRM box, click ane. Pair sites.
• The Pair Site Recovery Manager Servers sorcerer will open. Enter the IP address or FQDN of the Platform Services Controller for the recovery site, and click Side by side.
• The wizard then checks the referenced PSC for a registered SRM install. Select the corresponding vCenter Server from the list and enter SSO administrator credentials.
• Click Finish to pair the sites together.

At present the sites are paired they should both show continued. When we configure protection one will be made the protected site and the other failover.

Side by side we volition configure mappings to decide which resource, folders, and networks will be used at both sites.

• Locate the Guide to configuring SRM box and the subheading ii. Configure inventory mappings.
• Click 2.1 Create resource mappings.
• Expand the vCenter servers and select the resources, then click Add mappings and Next.
• On the adjacent page you can choose to add opposite mappings as well, using the tick box if required.
• Click Finish to add together the resource mappings.

• Click 2.2 Create folder mappings.
• Select whether you lot want the organisation to automatically create matching folders in the failover site for storing virtual machines, or if y'all desire to manually choose which folders at the protected site map to which folders at the failover site. Click Next.
• Select the folders to map for both sites, including reverse mappings if required, and click Finish.

• Click 2.3 Create network mappings.
• Select whether you desire the system to automatically create networks, or if you lot want to manually cull which networks at the protected site map to which networks at the failover site. Click Next.
• Select the networks to map for both sites and click Next.
• Review the test networks, these are isolated networks used for SRM test failovers. Information technology is all-time to leave these as the default settings unless you take a specific isolated exam network you want to use. Click Side by side.
• Include any contrary mappings if required, then click Terminate.

Next we will configure a placeholder datastore. SRM creates placeholder virtual machines at the DR site, when a failover is initiated the placeholder virtual machines are replaced with the live VMs. A small datastore is required at each site for the placeholder data, placeholder VMs are generally a couple of KBs in size.

• Click 3. Configure placeholder datastore.
• Select the datastore to be used for placeholder information and click Ok.

The screenshot below shows the placeholder VMs in the failover site on the left, and the live VMs in the protected site on the correct.

Although we followed the magician on the site summary page for the higher up tasks, it is also possible to configure, or change the settings subsequently, by selecting the site and so the Manage tab, all the different mappings are listed.

Site Protection

The following steps will configure site protection, nosotros'll kickoff past calculation the storage arrays.

• Click 4. Add together array manager and enable array pair.
• Select whether to use a single array managing director, or add a pair of arrays, depending on your environment, and click Next. I'm adding 2 separate arrays.

• Select the site pairing and click Next.
• Select the installed Storage Replication Adapter and click Side by side.

• Enter the details for the two storage arrays where volumes are replicated and click Next.
• Select the array pair to enable and click Next.
• Confirm the details on the review folio and click Finish.

An array pair can be managed past selecting the SRM site and clicking the Related Objects tab, and so Array Based Replication. If you add together new datastores to the datastore group, you lot can check they take appeared by selecting Array Based Replication from the Site Recovery Manager home folio, select the array, and click the Manage tab. Array pairs and replicated datastores volition be listed, click the bluish sync icon to observe new devices.

Now the storage arrays are added nosotros can create a Protection Group.

• Click 5. Create a Protection Group.
• Enter a proper name for the protection group and select the site pairing, click Next.

• Select the direction of protection and the blazon of protection group. In this example I am using datastore groups provided by array based replication so I'll demand to select the array-pair configured to a higher place, and Next.

• Select the datastore groups to protect, the datastores and virtual machines will be listed, click Next.
• Review the configuration and click Finish.

The terminal step is to group our settings together in a Recovery Plan.

• Click 6. Create a Recovery Plan.
• Enter a proper noun for the recovery plan and select the site pairing, click Side by side.
• From the sites detected select the recovery site and click Next.
• Select the Protection Group we created above and click Next.
• Review the exam networks, these are isolated networks used for SRM exam failovers. It is best to get out these as the default settings unless you lot accept a specific isolated examination network you want to utilise. Click Adjacent.
• Review the configuration and click Terminate.

At present we have green ticks confronting each item in the Guide to configuring SRM box, we tin can move on to testing site failover. The assortment based replication, Protection Groups, and Recovery Plans settings can all be changed, or new ones created, using the menus on the left handside of the Site Recovery Director home page.

Site Failover

SRM allows us to do a test failover, as well as an bodily failover in the issue of a planned or unplanned site outage. The examination failover brings online the replicated volumes and starts upwardly the virtual machines, using VMware Tools to confirm the Os is responding. It does not connect the network or bear upon the production VMs.

• Log in to the vSphere web client for the vCenter Server located at the DR site.
• Click Site Recovery, click Recovery Plans and select the appropriate recovery plan.
  • To examination the failover program click the green start push button (Test Recovery Program).
  • In one case the test has completed click the cleanup icon (Cleanup Recovery Programme) to remove the test information, previous results tin still be viewed nether History.
• To initiate an actual neglect over click the white kickoff button within a red circle (Run Recovery Plan).
• Select the tick-box to confirm you empathize the virtual machines will be moved to different infrastructure.
• Select the recovery type; if the primary site is available and then employ Planned migration, datastores volition be synced earlier fail over. If the primary site is unavailable then utilize Disaster recovery, datastores will be brought online using the almost contempo replica on the storage array.
• Click Next and and so Finish.

During the failover you lot will come across the various tasks taking place in vSphere. One time consummate the placeholder virtual machines in the DR site are replaced with the live virtual machines. The virtual machines are brought online in the priority specified when we created the Recovery Plan.

Ensure the virtual machines are protected once more as soon as the main site is available by following the re-protection steps beneath.

Site Re-Protection

When the main site is available the virtual machines must be re-protected to let failback. Too subsequently failing back to the primary site the virtual machines must be re-protected to allow failover once again to the DR site.

• Log in to the vSphere web client for either site and click Site Recovery, Recovery Plans and select the appropriate Recovery Plan.
• Under Monitor, Recovery Steps, the Programme status needs to show Recovery complete, before nosotros tin re-protect.

If the status shows incomplete then you tin can troubleshoot which virtual machine(south) are causing the problem nether Related Objects, Virtual Machines. VMware Tools must exist running on the VMs to detect the full recovery process.

• To re-protect virtual machines click Reprotect from the Actions carte at the peak of the folio.
• Click the tick-box to confirm yous understand the machines will be protected based on the sites specified.

• Click Adjacent and Finish. The re-protect job volition now run, follow the condition in the Monitor tab.

Once consummate the Program Status, and Recovery Status, will show Complete. The virtual machine Protection Condition will testify Ok. The VMs are now protected and can be failed over to the recovery site. If you are failing back to the primary site follow the same steps equally outlined in the SRM Failover section above. Recollect to then re-protect the VMs so they tin can failover to the DR site again in the consequence of an outage. When a Protection Plan is active the condition will evidence Gear up, the program is ready for examination or recovery.

_______________

Part one – Nimble Storage Integration with SRM

Part 2 – Site Recovery Manager Install Guide

Office 3 – Site Recovery Managing director Configuration and Failover Guide

This mail service will walk through the installation of Site Recovery Manager (SRM) to protect virtual machines from site failure. SRM plugs into vCenter to protect virtual machines replicated to a failover site using array based replication or vSphere replication. In the event of a site outage, or outage of components inside a site significant production virtual machines can no longer run in that location; SRM brings online the replicated datastore and VMs in vSphere, with a whole bunch of automated customisation options such as assigning new IP addresses, boot orders, dependencies, running scripts, etc. Afterwards a failover SRM tin can reverse the replication direction and protect virtual machines ready to fail back, all from within the vSphere web client.

Site Recovery Managing director now has integration with the HTML5 vSphere client, see VMware Site Recovery Manager 8.ten Upgrade Guide for more data.

Requirements

• SRM is installed on a Windows automobile at the protected site and the recovery site. SRM requires an absolute minimum of 2vCPU, 2 GB RAM and 5 GB disk available, more is recommended for large environments and installations with an embedded database.
• The Windows server should have User Admission Control (UAC) disabled (in the registry, not merely set up to never notify) as this interferes with the install.
• Each SRM installation requires its own database, this can exist embedded for minor deployments, or external for large deployments.
• A vCenter Server must exist in place at both the protected site and the recovery site.
• SRM supports both embedded and external Platform Services Controller deployments. If the external deployment method is used ensure the vCenter at the failover site is able to connect to the Platform Services Controller (i.e. it isn't in the primary site). For more than data click here.
• The vCenter Server, Platform Services Controller, and SRM versions must be the same on both sites.
• You will need the credentials of the vCenter Server SSO administrator for both sites.
• For vCenter Server six.0 U2 compatibility utilize SRM v6.i.1, vCenter Server 6.0 U3 apply SRM v6.i.2 and for vCenter Server half-dozen.five and 6.5 U1 employ v6.5 or v6.5.1 of SRM.
• Check compatibility of other VMware products using the Production Interoperability Matrix.
• If at that place any firewalls between the management components review the ports required for SRM in this KB.
• SRM can be licensed in packs of 25 virtual machines, or for unlimited virtual machines on a per CPU basis with vCloud Suite. Read more about SRM licensing here.
• Array based replication or vSphere Replication should be in place before beginning the SRM install. If you lot are using assortment based replication contact your storage vendor for best practices guide and the Storage Replication Adapter which is installed on the same server as SRM.

As well as the requirements listed above the following points are best practices which should besides exist taken into consideration:

• Modest environments tin host the SRM installation on the aforementioned server every bit vCenter Server, for large environments SRM should be installed on a unlike system.
• For vCenter Server, Platform Services Controller, Site Recovery Manager servers, and vSphere Replication (if applicable) use FQDN where possible rather than IP addresses.
• Time synchronization should exist in place beyond all direction nodes and ESXi hosts.
• It is best do to have Active Directory and DNS servers already running at the failover site.

Installation

In this instance we will be installing Site Recovery Managing director using Nimble array based replication. There is a vCenter Server with embedded Platform Services Controller already installed at each site. The initial screenshots are from an SRM v6.i.ane install, but I have too validated the procedure with SRM v6.5.1 and vCenter 6.5 U1.

The virtual machines nosotros want to protect are in datastores replicated by the Nimble array. For more information on the storage assortment pre-installation steps see the Nimble Storage Integration post referenced below. The Site Recovery Manager install, configuration, and failover guides accept no further references to Nimble and are the aforementioned for all vendors and replication types.

Part ane – Nimble Storage Integration with SRM

Role 2 – Site Recovery Director Install Guide

Part 3 – Site Recovery Manager Configuration and Failover Guide

Installing SRM

The installation is pretty directly forrad, download the SRM installer and follow the steps beneath for each site. We'll install SRM on the Windows server for the primary / protected site first, and repeat the process for the DR / failover site. We can then pair the 2 sites together and create recovery plans.

SRM 6.5.ane (vSphere 6.5 U1) Download | Release Notes | Documentation

SRM six.5 (vSphere 6.5) Download | Release Notes | Documentation

SRM 6.1.2 (vSphere 6.0 U3) Download | Release Notes | Documentation

SRM 6.1.1 (vSphere 6.0 U2) Download | Release Notes | Documentation

Log into the Windows server where SRM will exist installed every bit an administrator, and right click the downloaded VMware-srm-version.exe file. Select Run as aministrator. If you are planning on using an external database then the ODBC data source must be configured, for SQL integrated Windows authentication brand sure you log into the Windows server using the account that has database permissions to configure the ODBC data source, and run the SRM installer.

Select the installer language and click Ok.

Click Next to begin the install wizard.

Review the patent information and click Next.

Accept the EULA and click Next.

Ostend you have read the prerequisites located at http://pubs.vmware.com/srm-61/index.jsp past clicking Next.

Select the destination bulldoze and folder, then click Next.

Enter the IP address or FQDN of the Platform Services Controller that will exist registered with this SRM instance, in this case the primary site. If possible use the FQDN to make IP address changes easier if required at a afterward appointment. Enter valid credentials to connect to the PSC and click Next. If your vCenter Server is using an embedded deployment model then enter your vCenter Server information.

Accept the PSC certificate when prompted. The vCenter Server will be detected from the PSC data provided. Confirm this is correct and click Adjacent. Accept the vCenter certificate when prompted.

Enter the site proper noun that will appear in the Site Recovery Manager interface, and the SRM administrator electronic mail accost. Enter the IP address or FQDN of the local server, again utilize the FQDN if possible, and click Next.

In this instance as nosotros are using a single protected site and recovery site nosotros volition use the Default Site Recovery Manager Plug-in Identifier. For environments with multiple protected sites create a custom identifier. Click Next.

Select Automatically generate a certificate, or upload 1 of your own if required, and click Side by side.

Select an embedded or external database server and click Next. If you are using an external database you volition demand a DSN entry configured in ODBC data sources on the local Windows server referencing the external data source. Click Next.

If you opted for the embedded database y'all will be prompted to enter a new database name and create new database credentials. Click Next.

Configure the business relationship to run the SRM services, if applicative, and click Next.

Click Install to begin the installation.

Site Recovery Manager is now installed. Repeat the process to install SRM on the Windows server in the DR / recovery site, referencing the local PSC and changing the site names as advisable. If you are using storage based replication you too need to install the Storage Replication Adapter (SRA) on the same server equally Site Recovery Manager. In this example I have installed the Nimble SRA, available from InfoSight downloads, which is simply a next and end installer.

Subsequently each site installation of SRM yous will see the Site Recovery Manager icon appear in the vSphere web client for the corresponding vCenter Server.

Providing the datastores are replicated, either using vSphere replication or array based replication, we can now move on to pairing the sites and creating recovery plans in Part three.

_______________

Function 1 – Nimble Storage Integration with SRM

Part two – Site Recovery Manager Install Guide

Part iii – Site Recovery Manager Configuration and Failover Guide

Source: https://esxsi.com/category/srm/

Posted by: hernandezwinger.blogspot.com

Share this post