What exactly are you backing up with vCenter Protect? Just the patches? Database?
There is not really any feature within Protect for syncing anything between consoles other than the use of data rollup (which is only for rolling up scan/deployment results to a central console for reporting) or using a distribution server (just for storing patches/definitions/binaries).
It's not really backing up anything. I am wondering that if the primary sitre goes down. How would I set it up so that the outlying sites can fail over to the backup site to get their updates.
I am looking at deploying a distribution server to each outlying site to limit traffic to the primary site.
There isn't anything to failover if the other sites are running a separate instance of Protect that uses a separate database.
If you are using the same database for all these sites I wouldn't recommend it for so many consoles, but make sure to backup the database. That's about all you can do.
Ok, so to setup a distribution server at each location, would I need to install the vCenter Protect console on 1 computer to act as the distribution server?
1 of 1 people found this helpful
Distribution servers with Protect are basically just a shared folder you are using to store patch files and definitions/binaries.
I'd suggest taking a look at the product documentation linked below or the Help section within vCenter Protect when you are initially configuring these.