check-circle-line exclamation-circle-line close-line

VMware vRealize Orchestrator Plug-In for vSphere Replication 8.2 Release Notes

VMware vRealize Orchestrator Plug-In for vSphere Replication 8.2  | 09 MAY 2019 | Build 13431631  | Download

VMware vRealize Orchestrator 7.6 Appliance | APR 11 2019 | Build  13020602 | Release Notes

VMware vSphere Replication 8.2 | 9 MAY 2019 | Build 13480246 | Release Notes

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

The vRealize Orchestrator Plug-In for vSphere Replication 8.2 аdds a Replication Details group of workflows that allow you to retrieve information about the status or configuration details of replications. You can use the results of the workflows as parameters in other workflows. 

  • Check Replication Status – returns the status of a selected replication as a string, for example OK, Error or RPO Violation.
  • Get Replication Configuration - returns the following properties of a selected replication:
    • mpitDays – the number of days to store a replication instance
    • mpitInstances - the number of replication instances to keep within a day
    • isMpitEnabled – indicates with true or false if MPIT is enabled
    • isNetworkCompression - indicates with true or false if network compression is enabled
    • isQuiescingEnabled - indicates with true or false if quiescing is enabled
    • RPO – the number of minutes set as a limit for the latest available replication instance
    • status – the status of the replication, such as OK, Error or RPO Violation.
    • testRecoveryState – returns the status of a replication to the cloud where you must run a test recovery before you run a clean up, such as Complete, testError or cleanupError.
  • Get Replication List – returns a list of replicated VMs for a selected direction of replication. You must select the source vCenter Server and the direction of the replications that you want to retrieve to complete the workflow.

The vRealize Orchestrator Plug-In for vSphere Replication 8.2 аdds workflows in the Configure Replication and Remote Site Management groups of workflows:

  • Reconfigure Replication - assists you to change the settings of a replication, including reconfiguring a replication on new virtual hard disks and pointing it to an existing replica disk at the disaster recovery site as a seed.
  • Log in to a vCenter Server site - performs a login to a selected remote vCenter Server site for replications within a single vCenter Server instance.

Introduction to the VMware vRealize Orchestrator Plug-In for vSphere Replication 8.2

The VMware vRealize Orchestrator Plug-In for vSphere Replication allows VMware administrators to simplify the management of their vSphere Replication infrastructure by leveraging the robust workflow automation platform of vRealize Orchestrator. The vRealize Orchestrator Plug-In for vSphere Replication extends automation capabilities for certain vSphere Replication operations by including them in vRealize Orchestrator workflows.
The plug-in also delivers pre-built out-of-the-box building blocks and complete workflows that cover certain existing vSphere Replication actions.

The vRealize Orchestrator Plug-In for vSphere Replication 8.2 release runs with VMware vRealize Orchestrator 7.6.

You can download the vRealize Orchestrator Plug-In for vSphere Replication 8.2 from the download page.

For information about creating workflows by using vRealize Orchestrator, see the vRealize Orchestrator documentation.

For more information on the supported workflows, see the Featured Workflows section.

For more information on the compatibility between the VMware vRealize Orchestrator Plug-In for vSphere Replication and vRealize Orchestrator Appliance, see the compatibility matrix

Installation

The Orchestrator Plug-In for vSphere Replication software requires vRealize Orchestrator 7.6, and vSphere Replication 8.2. For information on installing vRealize Orchestrator, see the vRealize Orchestrator documentation. For information on installing vSphere Replication 8.2, see Install vSphere Replication in the VMware Site Recovery documentation.

The Orchestrator Plug-In for vSphere Replication software is distributed as Orchestrator application file. Install and configure the plug-in by using the Orchestrator configuration interface.

After you install the Orchestrator Plug-In for vSphere Replication, the plug-in automatically discovers the vSphere Replication instances on all vCenter Servers that are currently registered.

After you install the Orchestrator Plug-In for vSphere Replication, you find the vSphere Replication 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 > vSphere Replication folder.

Before you can run vSphere Replication workflows, which interact with remote sites, you must register the remote site, by running the corresponding workflow from Library > vSphere Replication > Remote Site Management > Register VC Site. Even if you want to configure replication to the same site, you must register it by selecting self pair in the Site field. Then, you must log in to the remote site by running the Login to VC Site​ workflow. You must run this workflow only once per vRealize Orchestrator user.

Note: vRealize Orchestrator communicates with the vSphere Replication appliance over port 8043.

Featured Workflows

The vRealize Orchestrator plug-in provides out-of-the-box workflows to help customers automate vSphere Replication operations. Below are some of the implemented workflows.

  • Remote Site Management workflows:
    1. Log in to a vCenter Server site
  • Configure Replication workflows:
    1. Reconfigure Replication
  • Pause Replication workflows
  • Resume Replication workflows
  • Reverse Replication workflows
  • Stop Replication workflows
  • Planned Migration workflows
  • Replication Details Workflows
    1. Check Replication Status
    2. Get Replication Configuration
    3. Get Replication List

Resolved Issues

  • The destination path of replicated disks contains null, instead of the remote datastore name

    The API call to retrieve the destination path of a replicated disk returns null datastore. (VcToVcSourceGroup) replication.getReplicationData().getVmDisks()[0].getDestinationPath() returns '[null] disk_name.vmdk'

    This issue is resolved in this release.

Known Issues

The known issues are grouped as follows.

General
  • You might see an error in the vSphere Replication inventory of the vRealize Orchestrator after replacing a vSphere Replication management server certificate at the local site of a pair

    If for some reason you change the certificate of the vSphere Replication management server at the local site of a replication pair, you might not be able to see the pair in the vSphere Replication inventory of the vRealize Orchestrator. You see an error similar to:
    Unable to execute 'fetchRelation' for type : Site : com.vmware.vim.vmomi.client.exception.SslException: com.vmware.vim.vmomi.core.exception.CertificateValidationException: Server certificate chain is not trusted and thumbprint doesn't match

    Stale certificates in the vRealize Orchestrator inventory cause the issue.

    Workaround:

    1. Restart the vRealize Orchestrator server:
      1. Launch a console to the virtual machine on which the vRealize Orchestrator server is installed.
      2. Log in to the console as root.
      3. Run the command service vco-server restart to restart the vRealize Orchestrator server.
    2. Restart the Orchestrator client. Wait for the validation to complete. You can monitor validation progress at this url pattern: https://{your vRealize Orchestrator server address}:8283/vco-controlcenter/config/#/control-app/validate
    3. In case the vSphere Replication management server is in a pair with another vSphere Replication management server, you must reconnect the pair.
    4. In the vRealize Orchestrator inventory, unregister the old server entries and register the new ones.

Known Issues from Previous Releases

To view a list of previous known issues, click here.