Sorry for reposting this, but simply replying under the "Failback qusting" below was not a good idea I think. Because now this is not a question, this is a failure
Two days ago one of our servers failed and I used "Failover" without problems to start the replicas of a Domain Controller and a File Server on a second ESX.
Today our server (ESX1) was repaired (new mainboard, new RAID controller) and I started a "Failback" for the first VM (PP-VSERVER1, a Domain Controller with 120 GB) and it failed.
It finished the "Calculating original signature..." step but failed in the "Replicating restore point ...." after 7 minutes with error
- Code: Select all
06.10.2017 20:04:11 Error Failed to perform failback Error: Failed to open VDDK disk [[ESX1 - SAS-RAID5] pp-vserver1.polyplan.local/pp-vserver1.polyplan.local.vmdk] ( is read-only mode - [false] )
Logon attempt with parameters [VC/ESX: [PP-ESX1];Port: 902;Login: [root];VMX Spec: [moref=5];Snapshot mor: [5-snapshot-6275];Transports: [nbd];Read Only: [false]] failed because of the following errors:
Failed to process [replicateVddkDiskIncremental].
I opened a support case (#02336918) but because we only have "Basic Support", I guess nobody will work on it before monday. I planed the weekend for failback (the other VM is the fileserver with about 2 TB). Does anyone have an idea what's wrong here?
Looking at the repaired server with the vSphere Client it now tells me that the disk of the VM that didn't failback needs consilidation. I learned from the Veeam KB that the "needs consolidation" is to be expected after a failed failback.
I tried a 2nd failback to a "specified location". That doesn't use the (now probably corrupt) original VM but should simply copy over the whole VM to the specified location. But - after a few minutes I got nearly the same error ..... Failed to process [replicateVddkDiskIncremental].
What is going on here?
There is no vCenter used anymore for more than a year now. Both ESX are standalone.
What I saw is that the failback process choose exactly that VM as proxy that it should failback (I left the proxy to automatic). Maybe it can't proxy itself?