VMware

VMware Disaster Recovery Service Release Notes

14 April 2014

What's in the Release Notes

The release notes cover the following topics:

About the VMware Disaster Recovery Service

Disaster Recovery is a new Recovery-as-a-Service (RaaS) offering to protect virtual workloads managed by VMware vSphere that are either deployed in a private cloud or data center by replicating those workloads into a cloud.

The VMware Disaster Recovery Service consists of the following VMware products and services:

NOTE These release notes provide information for vSphere Replication 5.6 Disaster Recovery to Cloud and vCloud Air - Disaster Recovery.

vCloud Air Supported Browsers

VMware Disaster Recovery Service Known Issues

vSphere Replication Disaster Recovery to Cloud

Exception 'Placeholder vApp creation failed' appears when you try to configure a replication to a virtual data center
When an org virtual data center is enabled for replications, but disabled in vCloud Director, replication configurations to this virtual data center fail because the placeholder vApp cannot be created. The following error message is displayed in the Recent Tasks pane of the vSphere Web Client: VRM Server runtime error. Please check the documentation for any troubleshooting information. The detailed exception is: 'Placeholder vApp creation failed'.
vSphere Replication does not filter virtual data centers by their enablement status in vCloud Director, and disabled virtual data centers appear in the Configure Replication wizard, so you can select them. However, virtual data centers that are disabled in vCloud Director cannot be used for creating vApps, so they cannot be used as replication targets.
Workaround: None. The org virtual data center must be enabled in vCloud Director to allow replications to cloud.

vSphere Replication actions in vSphere Web Client are not available after upgrade
If you upgrade from vCenter Server version 5.1.x to version 5.5, and if you log in to the updated vSphere Web Client before you upgrade the vSphere Replication appliance to version 5.6, after the upgrade of the appliance replication actions through the vSphere Replication plug-in are not available.
Workaround:
Restart the vSphere Web Client.

  • If vCenter Server runs on Windows, restart the VMware vSphere Web Client service.
  • If vCenter Server runs on Linux, establish an SSH connection to the vCenter Server system, log in as the root user, and run the following command: service vsphere-client restart.

Replication status turns into Error if you add or remove disks on the source virtual machine during test recovery
Adding or removing disks to a replication source virtual machine during test recovery is not supported.
Workaround: None.

You are unable to complete any operations on a replication to the cloud
If the placeholder vApp of a configured replication to the cloud is removed, no operations can be completed on the replicaiton and it will eventually go into Error state.
Workaround: Stop the replication that indicates Error state and configure a new replication for the same source VM.

You can pair only one source site to a target cloud organization
If multiple on-premise sites are paired to the same cloud organization, some or all replications might enter the 'Not Active' state.
Workaround: None. You cannot pair multiple source sites to a single cloud organization.

vSphere Replication to Cloud REST API is showing virtual data centers that are already deleted
If a cloud administrator enables a virtual data center (VDC) for replication and right after that deletes the newly enabled VDC for replication, REST calls to GET https://my.cloud/api/org/{my.org.id}/enabledForReplicationVdcs will show as output the already deleted VDC.
Workaround: None. The vSphere Replication Cloud Service is not monitoring the deletions of virtual data centers, cloud organizations, and placeholder vApps on the target site.

Replications to cloud indicate Error state and you cannot reconfigure them
vSphere Replication to Cloud is unable to reconfigure replications that failed during initial configuration. This problem occurs because replication details are missing from the cloud provider site.
Workaround: Stop the replication by using the vSphere Replication UI in the vSphere Web Client, and try to configure a new replication to cloud.

A certificate validation error appears when you try to reconfigure, pause, sync, resume, or stop an outgoing replication
If you change the certificate of the vSphere Replication appliance on the target site, and, on the source site, you try to reconfigure, pause, sync, resume, or stop an outgoing replication, instead of triggering the corresponding task, vSphere Replication displays an error message that the certificate on the target site cannot be verified.
Workaround:

  1. Click Refresh in the vSphere Web Client and wait for the refresh operation to complete.
  2. Try to reconfigure, pause, sync, resume, or stop an outgoing replication again.

vSphere Replication target sites are not visible in the vSphere Web Client after upgrading the vSphere Replication appliance
After upgrading vSphere Replication from 5.5 to 5.6, replication target sites are no longer visible in the vSphere Web Client user interface.
Workaround: Clear the browser cache and log in to the vSphere Web Client interface again.

The replication configuration task fails and you cannot create another replication for the same source virtual machine
If you complete the Configure Replication wizard while the vSphere Replication service is not running, the following error message is displayed:
VRM Server runtime error. Please check the documentation for any troubleshooting information.
The detailed exception is: 'External service 'vSphereReplication' failed to respond in the specified timeout (10 SECONDS)'.

No replication is created on the Outgoing Replications page for that VM, but if you attempt to configure another replication for this VM, the runtime exception details read Unable to create replication group on secondary site.
If the vSphere Replication service stops during initial configuration, a placeholder vApp might be created on the target site before the initial configuration task fails. The placeholder vApp on the target site does not allow creating a new replicaiton for the same source virtual machine.
Workaround:

  1. Delete the placeholder vApp from the target site by using the vCloud Air portal.
  2. Stop the replication on the source site.
  3. Try configuring another replication for the virtual machine

A BadRequestException notification error occurs when you assign replication seeds
When you configure a replication from a vCenter Server 5.1 to the cloud for a single or multiple VMs and you select to assign replication seeds, a balloon error message appears in the lower right corner of the vSphere Web Client on Target Location and Replication Seed page of the wizards. The error message reads com.vmware.vise.search.transport.BadRequestException:....
Workaround: You can ignore this error message because it does not affect the functionality of vSphere Replication.

vSphere Replication client version differs from the product version
The version of the vSphere Replication plug-in that appears on the Client Plug-ins page under Administration might differ depending on the version of the vSphere Web Client in use and will differ from the vSphere Replication product version that is visible under Manage > vSphere Replication > About.
The format of the client version is 5.6.0.55 for vSphere Client version 5.5, and 5.6.0.51 for vSphere Client version 5.1.
Workaround: You can ignore this issue, because vSphere Replicaiton is working as expected and no functionality is impacted.

Replication status turns into Error if you add or remove disks on the source virtual machine during test recovery
Adding or removing disks to a replication source virtual machine during test recovery is not supported.
Workaround: None.

Changes of vRAM, vCPU, or number of NICs on the source VM are not reflected in the placeholder VM on the cloud provider site
If you change the vRAM, vCPU, or the number of NICs on a replication source VM, the changes that you apply are not updated in the replicated placeholder VM.
Workaround: Run a test recovery, a planned migration, or a disaster recovery operation to update the placeholder VM on the target site with the changes in vRAM or vCPU.
NOTE: NICs that are added to a replication source VM are not reflected in the placeholder VM, even after a recovery or a migration operation.
NICs that are deleted from a replication source VM are not reflected in the placeholder VM, but are automatically removed from the target during a recovery operation.

Replication configuration fails with exception 'Placeholder vApp creation failed'
You cannot enable replications for virtual machines that have a CD/DVD device that is marked as Datastore ISO File and is in Connected or Not connected state.
Workaround: Edit the virtual machine configuration and mark the CD/DVD device as Client Device. Do not select the Connected check box.

Replications are no longer functional after you deploy vSphere Replication 5.6 on more than one vCenter Server
When you deploy the vSphere Replication 5.6 on a given vCenter Server, and configure one or more replications, you must verify that no other vCenter Server is setup with the same vCHS Cloud credentials.
Enabling vSphere Replication for Disaster Recovery to Cloud on multiple vCenter Server instances and using the same vCHS Cloud credentials when configuring replications on these distinct vCenter Server instances causes inconsistencies in the corresponding cloud organization on the vCHS server. As a result of this inconsistency, replications to the cloud on some vCenter Server instances might stop functioning, while replications on other vCenter Server instances might continue working as expected.
Workaround:

  1. Select a vCenter Server as the only legitimate instance that should be configured for disaster recoveries to cloud.
  2. Unconfigure all pairings to the cloud on the other vCenter Servers, even if cloud replications work properly.
  3. Restart the vSphere Replication appliance that runs on the legitimate vCenter Server.

NOTE: If you need to setup more than one vCenter Server with vSphere Replication for Disaster Recovery to Cloud, you must acquire multiple vCloud Air - Disaster Recovery subscriptions, one for each vCenter Server.

Exception Invalid datastore format '<Datastore Name>' appears when vSphere Replication runs a sync task
If you rename a datastore on which replication source virtual machines are running, replication sync operations for these virtual machines fail with error VRM Server runtime error. Please check the documentation for any troubleshooting information. The detailed exception is: 'Invalid datastore format '<Datastore Name>'
Workaround: Pause and resume the replications that use source virtual machines from the renamed datastore.

Concurrent replication configurations for more than 50 VMs might fail with error Placeholder vAPP creation error
If you configure more than 50 virtual machines at a time for replication to cloud, their initial configuration might fail with error Placeholder vAPP creation error.
Workaround: None. Do not configure replications for more than 50 virtual machines at a time.

Concurrent export of 100+ VMs through vCloud Connector ODT method causes some of the export tasks to remain stuck at 0%
If you trigger an export of more than 100 virtual machines concurrently from the vCloud Connector UI to and ODT node, some of the export tasks remain at 0% and never get completed.
Workaround: None. Avoid exporting more than 100 virtual machines concurrently.

vCloud Air - Disaster Recovery

VM operations, such as Power on and Snapshot are available for VM placeholders in the Virtual Machine tab
When you log into vCloud Air - Disaster Recovery and select the Virtual Machines tab, VM operations are enabled for the disaster recovery placeholder VMs. However, standard VM operations are not applicable to placeholder VMs and, if you select them, the operations will fail.
Workaround: Navigate to the Virtual Machines tab for the virtual data center enabled for disaster recovery by selecting:
From vCloud Air Dashboard > the virtual data center enabled for disaster recovery > Virtual Machines tab > the placeholder VM > right-click and select an available operation from the menu.

Clouds that are enabled for disaster recovery are shown as Shared clouds in "All Cloud Regions"
If you have clouds that are enabled for disaster recovery in multiple regions, when you browse through the vCloud Air Portal "All cloud Regions", Disaster Recovery clouds are listed as "Shared clouds".
Workaround: None.

The ownership of virtual machines that vSphere Replication creates in the cloud appears as "System" in the vCloud Air portal
In the vCloud Air portal, under the Virtual Machine tab, the ownership of replicated virtual machines is shown as System rather than VPC Administrator.
Workaround: None. You can ignore this visualization problem as it does not affect the replication.

Virtual machine operations, such as Power on and Snapshot, are enabled for Disaster Recovery placeholders in the global Virtual Machine tab .
If you attempt to perform operations from the global Virtual Machines on these placeholder virtual machines, the operations will fail.
Workaround: Do not perform operations on the placeholder virtual machines in the global Virtual Machines tab. Perform these operations by selecting the virtual data center enabled for Disaster Recovery, and then the Virtual Machines tab.