How To Restart The Dba Server Services For Vcenter

Here is a curt "how-to" if you desire to motion your vCenter Server 5.v/6.0 and Update Managing director SQL database to a new SQL database server.

There is a KB article from VMware roofing this topic (KB 7960893 – Moving the VMware vCenter Server 4.x/5.x/6.0.10 SQL database).

In this blogpost I accept added some sidenotes from my experience and y'all can find some screenshots, too.

Preparation:

read KB 7960893
read this weblog post 🙂
install the new windows server (check compatibility matrix offset)
install the advisable SQL server version (take care of the servicepack level,too!)

Migration:

1. Stop Services:

Stop the following services on your "sometime" vCenter Database Server:

VMware Update Manager
VMware VirtualCenter Server
VMware VirtualCenter Management Webservices

2. Export SQL Amanuensis rollup jobs:

vCenter Server offloads some maintenance tasks to the database.

If you lot move your vCenter database to a new server yous have to take care that you recreate these jobs. The easiest mode is to export them from your "erstwhile" server and import them to the new one.

Consign the following jobs (Microsoft SQL Server Management Studio):

SQL_Jobs

To consign them into a .sql file just right click the jobname, select "Script Job as" – "Create to" and "New Query Editor Window":

export_jobs

Correct click the SQLQuery.sql and select "Save SQLQuery.sql" to salvage the file:

save_job

Echo this for every job and call up the binder where y'all salve the .sql files.

3. Perform a database fill-in:

Now you have to fill-in your vCenter Server database and your Update Manager database:

open up your MS SQL Server Management Studio
right click the database yous desire to fill-in
select "Tasks" – "Support…"
select a destination and expect until the backup has successfully finished

4. Copy data to the new DB Server:

Copy the database backup files and the SQL Amanuensis rollup jobs to the new database server…

5. Database restore:

open up the MS SQL Server Management Studio and connect to your new DB Server
right click "Database" and select "Restore Database…"
select "Device" and enter the path to your .bak file
click OK to restore the database
perform these steps for your Update Managing director DB and your vCenter DB

6. Import SQL Agent rollup jobs:

doubleclick the .sql files and execute them
check if all jobs are available (see screenshot Step 2)

seven. Update the vcdb.backdrop file:

connect to your vCenter Server
update the vcdb.properties file with the new SQL server

Y'all can find the vcdb.properties file at the post-obit location:

vCenter Server 5.ten:

Windows 2008 – C:\ProgramData\VMware\VMware VirtualCenter
other Windows versions – C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\

vCenter Server half dozen.x:

C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx

8. Update the ODBC connections:

The last task is to update the ODBC System Information Sources at your vCenter Server:

32bit ODBC: C:\Windows\System32\odbcad32.exe
64bit ODBC: C:\Windows\SysWOW64\odbcad32.exe

select "System DSN"
select the System Data Source (eg. for vCenter)
click "Configure"
change the SQL Server proper noun
follow the wizzard (eg. enter the password to connect to the SQL server)
test the Connection
repeat these steps for both ODBC connections (Update Manager and vCenter Server)

ix. Commencement the Services:

Now it is fourth dimension to start your VMware VirtualCenter Server and VMware Update Manager services.

If you made no mistakes your vCenter should now access the databases on your new MS SQL Server.