Recently I upgraded vSphere 4.0 to 4.1. Therefore, I first backed up the vCenter data, configured a new Windows Server 2008 R2 server, and then used install.bat to install vCenter 4.1 with all the data from the old server.
After only a couple of hours, I could not connect to my Virtual Center server anymore. When I tried to login, the following error occured:
vSPhere Client could not connect to “servername”. A connection failure occurred (Unable to connect to the remote server)
I found out that my Virtual Center service was stopped. When I clicked Start, it was started for a few seconds and then stopped again. In the event viewer, I found the following error:
Log Name: Application
Date: 3-9-2010 0:22:51
Event ID: 9002
Task Category: (2)
Computer: vcenter server 1
The transaction log for database ‘VIM_VCDB’ is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
To solve this problem, I did the following:
- Logon locally on the virtual center server
- Open SQL Server Management Studio 2005 Express (this is the management studio for sql express editions. If you haven’t installed it yet, download it from http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796 )
- Expand Databases. Right-click on VIM_VCDB and choose Properties.
- On the left side of the Properties Window, click Options and then choose Recovery Model “Simple”. Click OK to Save
- Right-click VIM_VCDB again, choose Tasks –> Shrink –> Files
- In the Shrink File screen, choose File Type “Log”. Make sure “Release unused space” is checked. Press OK to shrink the current log files
- Start the Virtual Center service from your Windows Services
The transaction logs will now not grow endlessly anymore.