VMware vRealize Orchestrator Plug-In for Site Recovery Manager 6.5 Release Notes

VMware vRealize Orchestrator Plug-In for Site Recovery Manager 6.5 | 22 NOV 2016 | Build 4654257 | Download

VMware vRealize Orchestrator 7.2 Appliance | 22 NOV 2016 | Build 4629837 | Release Notes

VMware Site Recovery Manager 6.5 | 15 NOV 2016 | Build 4613745 | Release Notes

Last updated: 20 DEC 2016

Check frequently for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

Introduction to the VMware vRealize Orchestrator Plug-In for Site Recovery Manager 6.5

With the VMware vRealize Orchestrator plug-in for Site Recovery Manager, Site Recovery Manager administrators can simplify the management of their Site Recovery Manager infrastructure by extending the robust workflow automation platform of Orchestrator. You build these workflows by using the drag-and-drop capability of the workflow editor in the Orchestrator client. Orchestrator uses the plug-in to access the functionality of Site Recovery Manager and the Site Recovery Manager API. The included pre-built workflows simplify the process of creating custom workflows.

What's New in the VMware vRealize Orchestrator Plug-In for Site Recovery Manager 6.5

The VMware vRealize Orchestrator plug-in for Site Recovery Manager 6.5 can work with vRealize Orchestrator configured with LDAP authentication. The Orchestrator plug-in introduces 18 new actions and workflows available through vRealize Orchestrator. The new workflows expand the Site Recovery Manager orchestration capabilities that you can leverage, for protection and recovery of virtual machines, through vRealize Orchestrator.

The Orchestrator plug-in provides the following new workflows:

  • Remove Local Sites
  • Add Test Network Mapping
  • Get Test Network Mappings
  • Remove Test Network Mappings
  • Remove Folder Mapping
  • Remove Network Mapping
  • Remove Resource Mapping
  • Remove Protection Group
  • Remove Replicated VM from vSphere Replication Protection Group
  • Unprotect Virtual Machines
  • Add Test Network Mapping to Recovery Plan
  • Create Recovery Plan
  • Delete Recovery Plan
  • Initiate Planned Migration Recovery Plan
  • Remove Protection Group from Recovery Plan
  • Remove Test Network Mapping from Recovery Plan
  • Wait Task End
  • Discover Replicated Devices

Installation and Upgrade

The Orchestrator plug-in for Site Recovery Manager software is distributed as an Orchestrator application file.

You must install and configure vRealize Orchestrator before you install the Orchestrator plug-in for Site Recovery Manager, see the Installing and Configuring VMware vRealize Orchestrator 7.2 documentation.

For information about how to install the Orchestrator plug-in for Site Recovery Manager on VMware vRealize Orchestrator 7.2, see the Install a New Plug-In topic in the VMware vRealize Orchestrator 7.2 documentation.

After you install the Orchestrator plug-in for Site Recovery Manager, you must configure the connection between the vRealize Orchestrator instance and the vCenter Server instance on your Site Recovery Manager site. For information about how to configure the connection with your vCenter Server, see the VMware vRealize Orchestrator 7.2 documentation.

After you install the Orchestrator plug-in for Site Recovery Manager, you can find the Site Recovery Manager workflows in the vSphere Web Client:

  1. Go to vRealize Orchestrator > Workflows view in the vSphere Web Client.
  2. Expand the hierarchy to navigate to the vRO Servers > vco_server > Library > SRM folder.

Before you can run the Site Recovery Manager workflows, you must configure the plug-in to work with your Site Recovery Manager by selecting Library > SRM > Configuration and running the following workflows:

  1. Run the Configure Local Sites workflow.
  2. Run the Configure Remote Site workflow.
  3. Run the Login Remote Site workflow.

You must run the Login Remote Site workflow once per Orchestrator Client session to log in to Site Recovery Manager on the remote site. The Orchestrator automatically logs out of Site Recovery Manager when you log out of the Orchestrator client.

You can upgrade your Orchestrator plug-in for Site Recovery Manager 6.1.1 or 6.1.1a by uninstalling your 6.1.1 or 6.1.1a plug-in and installing the 6.5 version.

For information about how to uninstall your Site Recovery Manager plug-in, see the Uninstall a Plug-In topic in the Installing and Configuring VMware Realize Orchestrator documentation and the following knowledge base article : http://kb.vmware.com/kb/2064575 , Uninstalling a plug-in from VMware vRealize Orchestrator 5.5.x, 6.0.x, and 7.x.

Example Workflows

The Orchestrator plug-in for Site Recovery Manager includes example workflows in Library > SRM > SRM Samples that demonstrate how you can automate Site Recovery Manager operations by using Orchestrator, such as:

  • Create VM and Protect It:
    1. Creates a virtual machine
    2. Adds the virtual machine to an existing protection group
  • Create ABR Group, Protect Existing VMs, Add to Recovery Plan:
    1. Creates an array-based protection group
    2. Protects the virtual machines in a given datastore by adding that datastore to the protection group
    3. Adds the new protection group to an existing recovery plan

Limitations

If the protection site is not available, you cannot perform the following actions by using vRealize Orchestrator workflows, but you can use the Site Recovery Manager user interface instead:

  • Create a recovery plan or change VM recovery settings;
  • Add or remove a test network mapping to a recovery plan;
  • Add or remove a protection group to an existing recovery plan.

Known Issues

New No Site Recovery Manager sites are displayed in the vRealize Orchestrator inventory if the user does not have privileges on all of the sites in an N:1 shared recovery site configuration

You can have more than one Site Recovery Manager instance installed against a certain vCenter Server instance. If you run the Configure Local Sites workflow with a user that does not have privileges on all Site Recovery Manager instances, no Site Recovery Manager sites are displayed in the vRealize Orchestrator inventory. The Site Recovery Manager sites that the user has privileges on are also not displayed.

Workaround: Run the Configure Local Sites workflow with a user that has privileges on all Site Recovery Manager instances.

New No Site Recovery Manager sites are displayed in the vRealize Orchestrator inventory if a single Site Recovery Manager site in an N:1 shared recovery site configuration is down

You can have more than one Site Recovery Manager instance installed against a certain vCenter Server instance. If a single Site Recovery Manager instance is down, no Site Recovery Manager sites associated with that vCenter Server are displayed in the vRealize Orchestrator inventory.

Workaround: None.

Running Configure Remote Site workflow fails for a Site Recovery Manager instance that is paired after it has been added to vRealize Orchestrator

If you add an unpaired Site Recovery Manager to a vRealize Orchestrator inventory and then pair it, running the execution of Configure Remote Site workflow fails.

Workaround: Restart the vRealize Orchestrator server.

Running the Configure Local Sites, Remove Local Sites, or Configure Remote Site workflow makes the existing sessions to the remote sites invalid

Running the Configure Local Sites, Remove Local Sites, or Configure Remote Site workflow makes the established sessions between the local sites and their remote sites invalid.

Workaround: Log in to the remote sites again.

An error occurs if you call the Server.findAllForType(string type, string query) method

You cannot find an object by using only the type name. The following error occurs if you pass only the type argument to the Server.findAllForType(string type, string query) method : Unable to execute 'fetchAll' for type : … : 'java.lang.NullPointerException'.

Workaround:
You must pass the optional query argument if you call the Server.findAllForType(string type, string query) method.
For example: x = Server.findAllForType(type, "");.