Rohail2004
Enthusiast
Enthusiast

VC Database Log file

My VC database log file is keep growing every hour, and the limit is 500MB with enable autogrowth ON... it never happened before, but yesterday I had to run the VC databsae clean up script and since then the log file is keep changing... I have been manually shrinking the log file so make sure it does not get full.. Any ideas why?

VC 2.5 update 3, SQL 2005 full.

Thanks,

0 Kudos
9 Replies
Troy_Clavell
Immortal
Immortal

what do you have your logging options set to? We usually leave them at Warning(error and warnings)

0 Kudos
Rohail2004
Enthusiast
Enthusiast

it is set to Info(Normal Logging).

0 Kudos
Troy_Clavell
Immortal
Immortal

reduce it to Warning, that should help

0 Kudos
Rohail2004
Enthusiast
Enthusiast

ok, does it require to reboot VC server? will do it and then wait to see if that helps.. thanks

0 Kudos
Troy_Clavell
Immortal
Immortal

no reboot required

0 Kudos
dickybird
Enthusiast
Enthusiast

In you VC check which level of stats you have set.. this can be done by going to Administration | statisitics.

Level 4 is the most space consuming level and level one is minimum.

Also you need to use the Simple as logging in SQL server instead of Full, the only caveat is with Simple you can only goto Last Full backup in case of issue with DB.

If there are no sapce concern Full is recommended by DBA's but in case of VC if you do not have many updates during the day to day, I would say keeping simple should be ok.

also make sure your Roll Back jobs are setup correctly, in VC2.5 update 4 is has that capability.

0 Kudos
dickybird
Enthusiast
Enthusiast

look at the Level of stats set in the VC by going to Administration | VC management server configuration | Statisitics and see if its Level

Level 1 keeps minimum logs and less space consumption and level 4 is maximum

Also keeping SQL server logs to Full will fill up Disk, Keep it simple only caveat is you can only to resotre to last full backup if you have Simple choosen for Log files.

With VC2.5 update 4, you have roll back jobs taking care of some of the logs

0 Kudos
Rohail2004
Enthusiast
Enthusiast

same thing happening still even after i made those changes which you guys suggested.

0 Kudos
admin
Immortal
Immortal

There are a number of KB articles about this. Did you search the KB? http://kb.vmware.com/

Rick Blythe

Social Media Specialist

VMware Inc.

0 Kudos