Tried to explain this as a conversation between 2 characters (Mr Green, Mr Blue)
One of the names is inspired by HULK character. The smashing HULK 🙂
Mr Green
My vCenter 6.0 crashed. Unable to connect and is inaccessible.
Mr Blue
vCenter being a centralized management layer, is a single point of failure. In an event of failure it prevents consumption of all the products registered to it
Mr Green
You are right. I have all vCloud Suite 6.0 products (SRM, VR, BDE, VDP, vROPS, vRA, vRAS, vRB, VCM, VIN, VCO, Hyperic) registered to the vCenter and unable to consume them now.
Mr Blue
vCenter is a primary product that should be backed up on regular basis. Scheduled backups can help to restore the vCenter in case of failure/crash
Mr Green
You know, I have successful daily backups of vCenter through VDP. But my vCenter is down so how do I access VDP and restore my backup
Mr Blue
Emergency Restore is a feature in VDP which allows to restore from existing backup even in case vCenter is not accessible
Check this link for steps on how to perform an Emergency Restore
Emergency Restore – VDP 5.5 (Case Study)
Mr Green
That’s Perfect !
I am able to successfully recover my vCenter from backup through Emergency Restore
With the recovered vCenter, all my products are intact now and fully operational.
Thanks a lot Mr Blue ! 🙂
Important points to note
- vCenter referred in this context is a vCSA (vCenter Server Appliance 6.0) with embedded PostgreSQL Database
- This is not a backup/restore of entire environment but only the centralized management layer which is vCenter
- The results holds good for both vCSA with embedded & external Platform Services Controller
- With external PSC both VC & PSC nodes need to be backed up/restored at the same time
- Backup/Restore of vCenter(Windows) with external DB is yet to be tested in my lab
VMware References on Backing up and Restoring vCenter Server