VMware vRealize Orchestrator Plug-In for vSphere Replication 8.2.1  | 29 OCT 2020 | Build 16773455 | Download

VMware vRealize Orchestrator 8.2 Appliance | 06 October 2020 | Build 16995073 | Release Notes

VMware vSphere Replication 8.2.1 | 29 OCT 2020 | Build 17079075 | 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 VMware vRealize Orchestrator Plug-In for vSphere Replication 8.2.1 provides bug fixes and security fixes.

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

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.1 release runs with VMware vRealize Orchestrator 8.2.

You can download the vRealize Orchestrator Plug-In for vSphere Replication 8.2.1 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 8.2, and vSphere Replication 8.2.x. For information on installing vRealize Orchestrator, see the vRealize Orchestrator documentation. For information on installing vSphere Replication 8.2.x, 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.

Note: The vRealize Orchestrator user, which is used to register the vCenter Server sites in vRealize Orchestrator must have the privilege Sessions.ValidateSession and the VRM Administrator role (or all the privileges of the VRM Administor role). The user must have the privileges on all vCenter Server instances in the vRealize Orchestrator inventory, otherwise the vRealize Orchestrator Plug-in for vSphere Replication does not populate the vSphere Replication inventory objects in vRealize Orchestrator.

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

  • NEW Login to VC Site Workflow fails with an error

    When you try to run the Login to VC Site workflow in vRealize Orchestrator, you receive the following error:

    No connection config found for remote site

    Workaround: This issue is resolved in vRealize Orchestrator Plug-In for vSphere Replication 8.2.1.

Known Issues

The known issues are grouped as follows.

General
  • Reconfigure Replication workflow fails with an error

    When you try to run the Reconfigure Replication workflow in vRealize Orchestrator 8.0.1, you receive the following error:

    Login attempt failed

    Workaround: Deselect and select the replication again.

  • Replication values do not load in Reconfigure Replication workflow

    When you try to run the Reconfigure Replication workflow in vRealize Orchestrator 8.0, the replication values do not load.

    Workaround: Upgrade vRealize Orchestrator 8.0 to vRealize Orchestrator 8.0.1.

  • 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.
  • The vSphere Replication site is not shown in the inventory view when a new vCenter instance has been added to vRealize Orchestrator.

    Workaround: Restart the vRealize Orchestrator Server service.

  • Executing any of the unregister workflows from Library > vSphere Replication > Remote Site Management does not terminate the already established connection to the target site.

    Workaround: Restart the vRealize Orchestrator Server service.

  • When registering vCloud Air as a Standalone Org or a Remote Cloud Site and "Ignore certificate warnings" is set to "No", the following warnings appear:
    1) Untrusted certificate, with certificate info:
    Validity : [From : Apr 23, 2013 To : Apr 27, 2016]
    Organizational Unit :
    Public key : RSA
    Fingerprint (MD5) : 80 C1 77 2F 78 16 01 EB 9A 4B 88 E5 A3 E3 C0 29
    Organization : VMware, Inc.
    Common Name (6 characters min) : *.vchs.vmware.com
    Country : US
    Serial Number : 1B C3 C0 84
    Alternative names :
    [2, [2]*.vchs.vmware.com]
    [2, [2]vchs.vmware.com]

    2) Wrong site - saying that the certificate is issued to *.vchs.vmware.com

    Workaround: Verify that the fingerprint is the same as the above, the validity is correct and continue with importing the certificate despite the warnings.

check-circle-line exclamation-circle-line close-line
Scroll to top icon