We got some problems in the datacenter with the virtual vCenter 4.1 server and decided to revert to a physical machine again to run vCenter.
After some good experience with the VMware Datamigration tool I tried to use this option again to migrate the 4.1 vCenter/VUM database + settings to the new host.. but… it’s not supported!
[ERROR] vCenter Server version not supported
[WARNING] vCenter Server does not satisfy migration prerequisite
One of my colleagues was migrating vCenter 4.0 database to vCenter 4.1 by using the Datamigration Tool located at the vCenter Installation CD. After running the Backup.bat script he received the following error:
DB logs: Msg. 3013, Level 16, State 1, Server <name> , Line 1 BACKUP DATABASE is terminating abnormally
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..
For troubleshooting or maintenance purposes it may be necessary to defragment the indexes on your Microsoft SQL database server. This article provides the steps perform a defragmentation of the indexes to increase performance of the database.
Fragmentation of indexes occurs when the logical order of pages is different than the physical order on the disk. In VirtualCenter fragmentation occurs most noticeably due to the statistics collection and consolidation.
When the indexes are excessively fragmented, performance of queries to the VirtualCenter database is slow.
Warning: The VirtualCenter Server service must be shut down prior to performing any kind of database maintenance. For information on stopping the VirtualCenter Server service, see Stopping, starting, or restarting the VirtualCenter Server service (1003895).