Critical Alerts for Space in Directory Database Log & Vault Store database Log.

[Stanley_Korivi]

Critical Alerts for Space in Directory Database Log & Vault Store database Log.

We have been getting this alert  for Directory database transaction Log & SQL database transaction log for vault Store"

The Directory database transaction log has used 98% of its allocated space.
	The Directory database contains the Enterprise Vault configuration details and other information. Enterprise Vault cannot function without this database. This problem is most likely to be caused by a failed backup or the database configuration.

I checked with my DBA team & they mentioned that both the databases are set to Autogrowth with unrestricted growth for data & Log. & the drives storing the database & log files have good amount of free space.

I also checked with my backup & they mentioned that backup's have been successfully running & they see no issues. Any idea why these alerts are still popping? I will be upgrading Enterprise Vault tomorrow from 8.0 to 9.0.2 & I wanted to make sure that I have everything backup & healthy. Am i missing anything here  Can some one please advise what else i need to be looking at?

[JesusWept3]

At what point does it autogrow? 90%?

[Stanley_Korivi]

I am checking with my DBA team on what point it triggers autogrowth. Currently it is set to grow by 10% & the initial size is set to 594 MB & drive has about 220 GB of free space left.

[Stanley_Korivi]

Response from DBA team..

There is no specific value or threshold...

if the end of the logical log does reach the start of the logical log then autogrowth is triggered

[Percy_Vere]

I would recommend the databases are backed up as part of an SQL maintenance plan that includes truncation of the transaction logs which should hopefully stop the warnings.

[Liam_Finn1]

It still sounds like there is a limit on the SQL database or log files. Can you get a screen shot of the properties of the database from your SQL admin so we can see the properties. Also what version of SQL are you running?

As per Percy's posting you should truncate your transaction log regularly throughout the day to disk to keep the size down and weekly you should index and compress the databases as good maintenance on SQL

[CFreeX]

I agree, have a look at the links below:

http://www.symantec.com/business/support/index?page=content&id=TECH47828

http://www.symantec.com/business/support/index?page=content&id=TECH74666

[AndrewB · Accepted solution]

i think the bottom line is that the sql logs need to backed up and truncated. i think we've all seen this enough to know that's the solution to the current issue. however, the issue of the files not auto-growing per the setting or the feature not working as expected is something limited to SQL and beyond anything that goes on in EV.