VMware Site Recovery Manager 8.2 – No more Windows

VMware has just announced the release of Site Recovery Manager 8.2. There are a number of new items in SRM 8.2, such as enhancements to the HTML5 user interface, support for vSphere 6.7 Update 2, but most notably is Site Recovery Manager 8.2 virtual appliance!

No more Microsoft Windows license needed! The SRM 8.2 virtual appliance runs on the Photon OS distro, which is similar to what the vCenter virtual appliance has been running on for years now.

What is New in in Site Recovery Manager 8.2

  • Adds compatibility with VMware vSphere 6.7 Update 2
  • Photon OS based SRM virtual appliance available
  • HTML5 User Interface Enhancements:
    • VMware Site Recovery Manager 8.2 Configuration Import/Export Tool is now available in SRM User Interface.
    • You can now change the color schemes in the SRM HTML5 User Interface to display the interface in a dark theme
    • Ability to display capacity information in the Protection Groups Datastores tab
    • Ability to provide in-product feedback with the Site Recovery User Interface
  • Public API Enhancements. SRM 8.2 introduces new methods in the product’s Public API:
    • Listing Array Managers information
    • Listing replicated RDMs.
  • vRealize Operations Management Pack for Site Recovery Manager 8.2
  • vRealize Orchestrator Plug-In for VMware Site Recovery Manager 8.2
  • Ability to send Site Recovery Manager logs to a remote syslog server

How to Migrate from Windows Site Recovery Manager to SRM 8.2 Virtual Appliance

Prerequisites

  • Verify that you have upgraded your Site Recovery Manager for Windows instance to version 8.2
  • Stop the Site Recovery Manager Server on the Windows host machine
  • Deploy the Site Recovery Manager Virtual Appliance

Procedure

  1. Log in to the Site Recovery Manager for Windows host machine
  2. Open a command prompt, and navigate to the bin folder in the Site Recovery Manager installation directory %SRM_INSTALL_DIR%\bin
  3. Run the following script
    export-srm-data.bat 
  4. When prompted, enter a password
  5. Transfer the exported directory to the Site Recovery Manager Virtual Appliance host machine
  6. Shut down the Windows host machine
  7. Log in to the Site Recovery Manager Virtual Appliance host machine as root
  8. (Optional) If in a trusted environment, import the root CA certificates.
    Note: The certificates must be in .pem format.
    • Copy the certificates to /etc/ssl/certs
    • To modify the certificates’ permissions, run the following command:
      chmod a+r .pem
    • Next run:
      c_rehash.
    • To import the Site Recovery Manager Server certificates, use the Site Recovery Manager Appliance Management Interface
  9. Run the following script
    /opt/vmware/srm/bin/import-srm-data.sh 
    • (Optional) If in a trusted environment, enter the OS admin password
    • (Optional) If prompted, enter the Platform Services Controller and the vCenter Server thumbprints
    • Enter the vCenter Single Sign-On administrator user name
    • Enter the vCenter Single Sign-On administrator password
    • Enter the root password
    • Enter the password set during the export of the data for the credentials file
  10. On the Site Recovery home tab, select the site pair, and click Actions > Reconnect.
    • Select the first site from the list. Enter the address of the Platform Services Controller for the Site Recovery Manager Server on the second site, provide the user name and password, and click Next
    • Select the vCenter Server and the services you want to reconfigure, and click Next
    • On the Ready to complete page, review the pairing settings, and click Finish

For more information and details about VMware Site Recovery Manager 8.2 be sure to read the full release notes.

Similar Posts

  • Fix VMware VCSA /storage/log filesystem out of disk space

    This morning I ran into an issue where users were reporting the production VCSA 6.0 was not allowing them to connect into the web or thick client. Another administrator rebooted the VCSA which seemed to work only briefly. I then logged into the VCSA web management (https://<VCENTER_IP>:5480) and noticed the following health status right away:

    The /storage/log filesystem is out of disk space or inodes

    vcsa /storage/log full

    Read More “Fix VMware VCSA /storage/log filesystem out of disk space”

  • VMware ESXi 5 home lab upgrade

    In the past I’ve been using a single server to run my VMware ESXi home lab. it was slow, old, big and loud. I’ve been meaning to upgrade my home lab for a while and just never got around to it, until now! When looking for new hardware I wanted the servers to be as compact as possible, quiet, and low energy usage as possible while still having some horsepower.

    I debated on going the whitebox solution as I build all my own desktops anyway, I also looked at several other solutions such as the HP ML310e server, Shuttle XH61V barebones machine, but ultimately decided to go with two Intel NUC i5’s.

    Intel NUC i5 and 16GB ram

    Intel NUC i5 DC53427HYE Features:

    • Uses very little energy
    • Completely quiet
    • Supports up to 16GB RAM
    • A dual core CPU that scores nearly 3,600 in PassMark benchmarking
    • Includes vPro which allows me to easily run both NUC’s headless
    • Extremely small, nearly 4 1/2″ inch square footprint

    Read More “VMware ESXi 5 home lab upgrade”

  • VMware Recertification Policy

    VMware certified

    Starting today, March 10 2014, new VCP certifications must be re-certified within two years of it’s earned date. Anyone who currently has their VCP certification prior to March 10 2013 has until March 10, 2015 to re-certify.

    The new policy gives you three options to re-certify:

    1. Take the current exam for your existing VCP certification solution track. For example, if you are a VCP3, you could take the current VCP5-Data Center Virtualization (VCP5-DCV) exam.
    2. Earn a new VCP certification in a different solution track. For example, if you are a VCP-Cloud, you could recertify by earning VCP5-Desktop (VCP5-DT) certification.
    3. Advance to the next level by earning a VMware Certified Advanced Professional (VCAP) certification. For example, if you are a VCP5-DCV you could earn VCAP5-DCA certification.

    I can understand why they are doing this but I don’t agree with the changes. As per the announcement if you let your certification expire, “Your certification will be revoked,and you will no longer be entitled to use the certification logo or represent yourself as VMware certified“. Really? You mean everything that was done prior and after taking the exam means nothing?

    Read More “VMware Recertification Policy”

  • VMware Workstation 8.0.4 released

    VMware has just released it’s forth minor update for VMware Workstation 8, bringing it up to 8.0.4. The looks to contain mostly a few bug and security fixes.

    General Issues

    • Linux guests running the Linux kernel version 2.6.34 or later could not be pinged from the host via an IPv6 address.
    • On rare occasions, Linux guests would suddenly fail to Autofit or enter Unity.
    • Unity mode would exit if the title bar of an application contained certain non UTF-8 encoded extended ASCII characters.
    • On Windows hosts, the VMware Workstation user interface sometimes became unresponsive when minimized from full-screen mode if the suggestion balloon was being displayed.
    • On Windows hosts, the user interface sometimes became unresponsive if the application was rendered on an extended display that was abruptly disconnected.

    Read More “VMware Workstation 8.0.4 released”

  • VMware Horizon View 5.3 has been announced

    Horizon View 5.2 is receiving an update to 5.3! Doesn’t sound like much, but in that tiny dot number increase VMware has in fact brought a number improvements and features to Horizon View.

    In a nut shell, some features Horizon View 5.3 brings is the ability to connect to a virtual desktop from any HTML5 capable web browser (yes, even Chromebook!), ability to bring full workstation class user experience with 3D graphics, deploy Windows Server 2008 as a desktop, as well as completely rewritten the Windows client with support for Windows 8.1 and a new iOS7 client too.

    In more detail, Horizon View 5.3 brings…

    Read More “VMware Horizon View 5.3 has been announced”

Leave a Reply

Your email address will not be published. Required fields are marked *

2 Comments

  1. Problem with step 6 above in my case… “Shut down the Windows host machine”
    In my situation I cannot shut down the windows host machine. That is also my vCenter 6.0 server running on Windows.
    I just want to offload SRM 8.2 off this box to its own appliance and then migrate to the VCSA 6.7. Is that possible?