Registering replication appliance to vCenter fails with “no element found: line 1, column 0”

Registering replication appliance to vCenter fails with “no element found: line 1, column 0”


Cause: Corrupt ovfenv.xml



Log on to the vR appliance console session and run the below command:

ls -lth /opt/vmware/etc/vami/

If the ovfenv.xml is 0, power down the replication appliance and power (do not perform a guest restart) this back up using the web client (must be powered up on the web client)

If the file still does not regenerate, you will re-deploy the replication appliance.

  1. If powering the vSphere Replication appliance does not resolve the issue, most certainly the appliance has been temporarily removed and re-added in the vCenter Server. There is no solution for restoring the OVF environment in that case. You must re-deploy the vSphere Replication appliance by using an empty database, and configure all replications from scratch.




SRM service crash during upgrade

Log location: c:\ProgramData\VMware\VMware vCenter Site Recovery Manager\Logs\vmware-dr.log


crash backtrace:

2018-01-08T23:02:56.539-07:00 [01952 verbose ‘Recovery’ ctxID=5c5b5384 opID=76706664] No state info for vm ‘protected-vm-96860’
2018-01-08T23:02:56.539-07:00 [01952 verbose ‘Recovery’ ctxID=5c5b5384 opID=76706664] No state info for vm ‘protected-vm-96942’
2018-01-08T23:02:56.539-07:00 [01952 verbose ‘Recovery’ ctxID=5c5b5384 opID=76706664] No state info for vm ‘protected-vm-96962’
2018-01-08T23:02:56.539-07:00 [01952 verbose ‘Recovery’ ctxID=5c5b5384 opID=76706664] No state info for vm ‘protected-vm-96963’
2018-01-08T23:02:56.539-07:00 [01952 verbose ‘Recovery’ ctxID=5c5b5384 opID=76706664] PVM State Tracker: Initializing.
2018-01-08T23:02:56.539-07:00 [01952 verbose ‘Recovery’ ctxID=5c5b5384 opID=76706664] PVM State Tracker: Will NOT initialize VM Info.
2018-01-08T23:02:58.770-07:00 [03132 verbose ‘DatastoreGroupManager’ opID=640e1e2d] Found 9 devices on host ‘host-757’
2018-01-08T23:02:58.770-07:00 [03132 verbose ‘DatastoreGroupManager’ opID=640e1e2d] Found 9 VMFS volumes on host ‘host-757’
2018-01-08T23:02:58.770-07:00 [03132 verbose ‘DatastoreGroupManager’ opID=640e1e2d] Dr::Storage::Match::`anonymous-namespace’::DeviceFetcher::FetchDevices: Fetched devices for host host-757
2018-01-08T23:02:58.786-07:00 [01952 panic ‘Default’ ctxID=5c5b5384 opID=76706664]
–> Panic: FAILURE: “Deserialize failed for data item (persistence id: ##global##_pvmi.protected-vm-106049): std::exception ‘class boost::archive::archive_exception’ “input stream error”” @ d:/build/ob/bora-4535903/srm/src/jobs/jobs.cpp:304
–> Backtrace:
–> [backtrace begin] product: VMware vCenter Site Recovery Manager, version: 6.1.1, build: build-4535903, tag: –
–> backtrace[00] vmacore.dll[0x001BF51A]
–> backtrace[01] vmacore.dll[0x0005D88F]
–> backtrace[02] vmacore.dll[0x0005E9DE]
–> backtrace[03] vmacore.dll[0x001D7A55]
–> backtrace[04] vmacore.dll[0x001D7B4D]
–> backtrace[05] vmacore.dll[0x0004DEFC]
–> backtrace[06] dr-jobs.dll[0x00035DB7]
–> backtrace[07] MSVCR90.dll[0x00074830]
–> backtrace[08] MSVCR90.dll[0x00043B3C]
–> backtrace[09] ntdll.dll[0x0004B681]
–> backtrace[10] dr-jobs.dll[0x0000390C]
–> backtrace[11] dr-jobs.dll[0x00005408]
–> backtrace[12] dr-recovery.dll[0x0016F153]
–> backtrace[13] dr-recovery.dll[0x0016AC81]
–> backtrace[14] dr-recovery.dll[0x002B0488]
–> backtrace[15] dr-recovery.dll[0x002AEF33]
–> backtrace[16] dr-recovery.dll[0x002B4011]
–> backtrace[17] dr-recovery.dll[0x00031A19]
–> backtrace[18] functional.dll[0x00028089]
–> backtrace[19] vmacore.dll[0x00153B8E]
–> backtrace[20] vmacore.dll[0x0015749F]
–> backtrace[21] vmacore.dll[0x001589F1]
–> backtrace[22] vmacore.dll[0x0015A725]
–> backtrace[23] vmacore.dll[0x00066C4B]
–> backtrace[24] vmacore.dll[0x00155DC0]
–> backtrace[25] vmacore.dll[0x001D302B]
–> backtrace[26] MSVCR90.dll[0x00002FDF]
–> backtrace[27] MSVCR90.dll[0x00003080]
–> backtrace[28] kernel32.dll[0x000159CD]
–> backtrace[29] ntdll.dll[0x0002A561]
–> [backtrace end]


Resolution:  Take a backup of the SRM DB and delete the contents of the table: pdj_dataitem and resume the installer.


Delete from pdj_dataitem;



Deploy vsphere replication using webclient

* You must have a vCenter deployed on the environment.
* you must have a compatible version of vR iso/ovf downloaded. (The build of vR used on the environment generally depends on the version of the vCenter, if you are unsure as to which version of vR do download, then read this guide here)



Log into the web client and bring up the Deploy ovf template wizard
Note: If you have trouble with CIP (client integration plugin on vCenter 6.0.x and 5.x), try firefox build 30 and CIP for firefox, Alternatively,  you may deploy this using OVFtool as described on my blog here:)

Mount the ISO and point to the ISO drive\bin\ and select the below files as on the screenshot.

Select the respective Datacenter and cluster

Set in the root password and networking information


Once the appliance has been deployed, Power on the Appliance (using web client only!!) and log in to the VAMI page (https://vr-ip:5480)

Switch to the vR>Configuration tab and correct the below
* Lookup service URL (should this be an external PSC)
* username (if you have a custom username/vsphere domain)
* Password

Click on save and restart, it should prompt for a certificate validation like that of the below. if you do not see the below, Ensure the vCenter FQDN can be resolved from the replication appliance.

If successful, you should see the below.


Log out and log in to the vSphere web-client to load the plugin. In some rare occurrences, you will need to restart the vSphere-client service for this plugin to be pulled up.



If you have vCenter 6.0 U2 and vR 6.1.2, the Plugin will not load if the vCenter does not have access to the internet. Please implement the action plan as described here:

Registering the vR to vCenter might fail with SSL validation errors. This is commonly observed with vCenter 6.0 GA, U1 or if it had been upgraded from this build and the certs were changed at one of these builds. Validate this with task 0 as per the below KB and implement if applicable

External PSC:
Embedded PSC:






















Configuring replication using existing seeds/reverse replication

Before proceeding, Ensure there are no stale replications. The VM name must not be listed in the vCenter server>Monitor>Vsphere replication>(on the source) outgoing,  incoming tab (for the destination)

Configuring replication using existing seeds are rather simple.  Configure replication like you normally would except, you would select the datastore>Folder where the source VM’s virtual disk’s are located.

Configure replication:

Select target site:

Select VR server:

Click on Edit for the VM

Select Datastore>VM folder where the disks are located

for the vR to detect the disk as seed, the Disk name must be identical to that of what is on the source side. you will see the below message when it picks up the seed.  Click on “use existing” to use the seeds

Click on use all seeds

Proceed with the wizard

The status of replication is expected to be “initial full sync” however if you click on the i icon as highlighted below, you will see it doing a checksum.

The replications should resume once the checksum has been compared








Recovering a VM using vSphere replication

Log into the recovery site vCenter webclient>vCenter server>Monitor>vSphere replication>incomeing replication>


Click on the VM that you wish to recover and click on the recover button: 


Should you be performing a planned migration of the VM (with the most recent change, select Synchronise recently change (you will need to authenticate with the source side vCenter) ,. Else, use the latest available data or point in time to recover to a point in time snapshot

in my  scenario, the source site was down and  the VM needs to be recovered on the DR,


Now the VM has been recovered and is running at the DR site