- Step 0: BACKUP or SNAPSHOT your VC server!
- Stop VirtualCenter service
- Stop VMware Update service
- Stop License Server service
- Stop SQL Express service
- copy the SQL data files to the new SQL 2005 location. Example below:
- on the new SQL 2005 server, start Management Studio and use "attach database" function import the migrated data files. Name the new database VIM_VCDB (or any other name).
- identify or create a SQL user (vmware is recommended, but anything will work) on the SQL 2005 server to have db_owner role for the VIM_VCDB database.
- on the VirtualCenter server, modify the both of the VMware DSNs in "Administrative Tools -> Data Source (ODBC)", see below:
- take defaults for the rest of the steps.
- Edit registry key "HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter\DB\2" with the SQL user name.
- at cmd prompt, run "vpxd -p" from the VirtualCenter folder under "c:\Program Files" (or the equivalent) and supply the password.
- start Licensing Server
- start VMware Update Manager
- start VirtualCenter Service
- test connection and functionality from a VI Client and you are done. if it works with no glitch, pat yourself on the back!
Thursday, December 04, 2008
How to upgrade VMware VirtualCenter 2.5 SQL Express to SQL 2005:
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment