Anyone any ideas on this?
The vCenter Server Appliance has got it's self in a loop. it's not booting. Am I able to just get one of the replicated VM's up on another ESXi server as all the files look up to date on the remote storage store?
You can do this manually if there's no way to recover the VM using the GUI.
Firstly, you should stop replication using the command line method: https://kb.vmware.com/kb/2106946
In the past I've just used the existing set of replica files, and it worked ok:
See here from my lab:
-rw------- 1 root root 8684 Oct 5 06:56 hbrcfg.GID-51f7e490-895a-43d2-b303-c67521e17c18.411.nvram.822
-rw------- 1 root root 2951 Oct 5 06:56 hbrcfg.GID-51f7e490-895a-43d2-b303-c67521e17c18.411.vmx.821
-rw------- 1 root root 12288 Oct 5 06:56 hbrdisk.RDID-9cc2fe60-1b54-44b7-b08c-789873f8d16f.416.96532343697320-delta.vmdk
-rw------- 1 root root 371 Oct 5 06:56 hbrdisk.RDID-9cc2fe60-1b54-44b7-b08c-789873f8d16f.416.96532343697320.vmdk
-rw------- 1 root root 2700 Oct 5 06:56 hbrgrp.GID-51f7e490-895a-43d2-b303-c67521e17c18.txt
-rw------- 1 root root 4294967296 Oct 5 06:56 linux-01-flat.vmdk
-rw------- 1 root root 494 Oct 5 06:56 linux-01.vmdk
I think you could rename hbrcfg.GID-51f7e490-895a-43d2-b303-c67521e17c18.411.nvram.822 to linux-01.nvram, and do the same with the vmx
Then register the VM in the inventory using the vmx.
Alternatively, you could create a new VM with the same name/configuration. During the VM creation wizard, select to use an existing virtual disk, and choose your replica VMDKs.
This worked really well - thank you.