To choose a location and size of the vCenter server database, perform the following:
- Choose the logging level (this logging level is a vCenter setting and not a database log file setting) carefully so that your vCenter server database will not grow too much and affect the performance in turn.
Use the knowledge base article at http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004795 to change the logging level for vCenter server.
- Consider the vCenter server task and event retention policy, which will increase the size of the vCenter server database.
- Also, choose the performance statistics collection settings carefully, which will also increase the database size and affect your vCenter server database performance.
- If you are deploying vCenter for a large environment, then do not collocate the vCenter database with the vCenter server system. It will help you avoid any possibility of CPU and memory resource contention.
- Preferably, choose a vCenter server database on a VM if does not already exist in the environment. Having a vCenter server database on a virtual platform has many benefits as follows:
- If needed, it can be easily backed up and recreated.
- During planned maintenance, it can be moved to other hosts using vMotion.
- It can be load balanced using vSphere DRS across hosts.
- You can easily protect it by vSphere HA without extra cost and maintenance. Check with your database vendor for details.
- You can take a snapshot of it as well for business continuity and testing.