We have a SQL 2000 backend server going out of production and I need to move the VCenter 2.0.2 database to a different server, SQL 2005. Has anyone performed this? Any issues to be aware of?
Thanks for your time.
One or two additional things to keep in mind: VC 2.0.x does not allow you to use the SQL Native ODBC driver, limiting you from using certain SQL 2005 clustering options. Check with your DBA whether this might be a problem.
Also, the default authentication mechanisms in SQL 2005 may be too restrictive. You will need a SQL-based login; Integrated Authentication is only supported if VC runs on the same server as SQL.
I moved a our DB and had no problems.
I've done this to my client last month and had no problems. Make sure you plan it out correctly and always BACKUP.
Look at this instruction for details instructions:
Hope this helps!
Azn2kew
Thanks very much for the info.
One or two additional things to keep in mind: VC 2.0.x does not allow you to use the SQL Native ODBC driver, limiting you from using certain SQL 2005 clustering options. Check with your DBA whether this might be a problem.
Also, the default authentication mechanisms in SQL 2005 may be too restrictive. You will need a SQL-based login; Integrated Authentication is only supported if VC runs on the same server as SQL.
I have followed the steps in this guide, but unfortunately now VMware VirtualCenter Server service will not start. I have rebooted the server as well, but still will not start.
Any ideas?
look at the windows event logs... This application should report.
This can happen when the service can't communicate with the DB. Make sure you have the login ID and password right for both SQL and the service.
Actually, the VC logs are kept in C:\Windows\Temp\vpx in VC 2.0.x. Be sure to grab the one with the latest timestamp - the latest one is not necessarily the one with the highest number.
Whatever error you're encountering should be towards the end of the log file.