Quick question, in my new design and upgrade plan to 4.0. I will have two vCenter servers one in our primary site and one at the DR site using Linked Mode. If my Update Manager server is on a stand alone VM located in my primary site can I use it to also update the ESX hosts in my DR site? Or do I have to have another update manager instance in my DR location?
Moved to Update Manager forum.
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, Virtualization Practice Analyst[/url]
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]
Each VC can have only one VUM registered with it and vice versa. Both VC and VUM should be of same version as well.
So, one instance of VUM can't work with more than one VC. Linked mode VCs don't affect this either.
You'll need VUM in your DR site too, in case you want to update ESX hosts and VMs managed by vCenter in DR site.
the above said is true - you should have one VUM server installed for each of yours linked VCs. The usage here is that you can have one VIClient connected to your liked VCs and to see their combined inventories.
From the VIC you should installed VUM plugin for every VC and only one VUM plugin can be active at a time. It depends on which inventory you are browsing with your VIClient and those VUM plugin will be active. Swithching between VCs inventories the VUM will switch automatically.
You should also setup the first VUM - create baselines, etc. then you can export your baselines and import them to the next VUM instance. Having the things done this way you'll spare one and the same VUM setup