Why not to use backup mapping for that?I want to use the existing good Site2 reps and just continue the backup chains and use the old jobs as I don't have enough storage (or backup window) to run a Full on everything.
Basically you just want to switch VBR1 and VBR2 roles so VBR2 (Site2) becomes primary and VBR1 (Site1) becomes secondary, did I get it right? If so then you can restore Site1-VBR from the configuration DB backup, then edit/recreate job so the replication/backup continues in the reversed direction from Site2 to Site1. Is that what you need?Do I need a 3rd VBR cold server ready, so I can restore the configuration from the dead Site1 VBR server? I then setup new backup jobs for the newly restored Site1 VM's on this server?
I'm not sure that I follow you. You've mentioned that you lost Site1, is that correct? Please describe your scenario - is it 100% lost including ESXi host or just Veeam infrastructure? Sorry for confusion.if I restored the config DB from dead VBR1 into rep-only VBR2, I would lose the replication jobs and have to fire up those rep-vm's manually from esxi?
No, it can't do that out of the box, however you might want to check this topic.Can the Veeam replication engine actually change the IP address of a vcenter appliance 6.0 like it can with Windows VMs??
lando_uk wrote:The configuration DB from the original (toasted) VBR Site1 is stored on Site2 repositories.
I now need to backup the original Site2 VMs and also the newly restored Site1 VMs for on-going protection.
I want to use the existing good Site2 reps and just continue the backup chains and use the old jobs as I don't have enough storage (or backup window) to run a Full on everything.
Do I need a 3rd VBR cold server ready, so I can restore the configuration from the dead Site1 VBR server? I then setup new backup jobs for the newly restored Site1 VM's on this server?
lando_uk wrote:At the moment, my failover processes seems almost one way, especially if we have to import config DB's and have VBR instances that don't know about each other.
From the issue description,I understand that you are would like to change the ip address of the vcenter server appliance,correct me if I am wrong.
Please note that by design ,changing the IP address of the appliance is not supported as of now.
You could refer the below links to the kb articles which discusses the issues that you may encounter in case you change the IP address of the appliance:
https://kb.vmware.com/kb/2130599 > The vCenter Server or PSC services fails to start when the IP address or hostname is changed in vCenter Server or Platform Service Controller (PSC).
http://kb.vmware.com/kb/2124422 > Attempting to change the IP address of the VMware vCenter Server Appliance 6.0 fails with the error: IPv4 configuration for nic0 of this node cannot be edited post deployment
Therefore,in case you have to migrate the VCSA to use a different VLAN,I would recommend to do a fresh install of the appliance.
Users browsing this forum: Majestic-12 [Bot] and 7 guests