Update Manager DB Best Practices?

[geob]

Is it best practice to give VUM it's own DB instance seperated from the VC DB instance? Is the best practice documented somewhere?

Thanks in advance,

-geob

[vmroyale]

Hello.

How many hosts and vms are we talking about here?

The VMware Infrastructure 3 Documentation contains an Administration Guide and Sizing Estimator.

[geob]

Starting with approx 15 hosts and about 300 VMs, mostly win 2000, and 2003 server.

[vmroyale]

I would definitely create a separate database for a deployment of that size.

[dmn0211]

This is from the Administration Guide Update Manager

"For an Update Manager database to be supported, you must create a database instance and configure it to ensure that all Update Manager database tables are placed in it."

Maybe I am taking this statement "you must create a database instance" to literally but also consider.

"Because the VirtualCenter database size is the single most important factor in determining the performance and scalability of VirtualCenter, you should configure these settings carefully."

The has some pretty good information concerning the VC database. Using the same database for the Update Manager could be detrimental to performance, recovery (Since you may want replicate only your VC database) and scalability.

[vmroyale · Accepted solution]

This is probably what you are looking for: VMware Update Manager Performance and Best Practices

[geob]

That is exactly what I was looking for.

Thanks for the help!

-geob