OK... but when a replicated VM is registered on the DR host, then it should be done through vCenter, right? Otherwise these VM's will be kind of "rouge", or isn't that a problem at all?
If day to day replication is done by communicating with vCenter, and then someday vCenter is gone, will VBR still know that the replicated VM's on the DR host, registered by it's IP address, are the same as the ones it has replicated through vCenter, so the re-IP settings still work? Do I explain is this in an understandable way?
Would it be better if the DR host is a part of another vCenter, fx. obtained by a Essentials license? In that way the replicated VM's will not be a part of the production vCenter and the DR setup would not be relying on the production vCenter that would be lost in a disaster.
A third solution would be to restore the vCenter server on the secondary site and change it's IP address to an address in the IP range of the secondary site. The secondary site has DC's that are part of the same domain that is running on the primary site, so it would just be a matter of changing the static IP in the DNS and then vCenter would be "up" (since it's referred by it's DNS name).
I have focused a lot on a complete disaster, where the primary site is completely gone for an extended time. However it's important the the replication setup will also work in a situation where the primary site is not completely gone and where the production vCenter might still be available, but we for some reason would like to fail over to the secondary site for some VM's. In this scenario it's important that fail back will work, so the setup must not be a "hack".
I really appreciate the input!