cancel
Showing results for 
Search instead for 
Did you mean: 

Space in Directory Database Log problem

Hi all

I've just setup EV 8 SP4 on our network and have started archiving with 5 accounts to test but I keep getting a Critical error on the Status that Space in the Directory Database Log is almost at 100%.

We have the EV agent for Backup Exec 2010 and backup the whole thing on a daily basis so I thought that the logs would be commited after each backup. The log fiel on the SQL server (VaultLog3b.mdf) is 32.5MB and it's initial size is set to 33MB with a max of 2GB.

I don't know if 33MB is ok or if it is expected to be much bigger / smaller than this.
The EV agent in Backup Exec 2010 added some options to the selections list so I just selected all of these for the backup. Have I missed something here maybe.

Anyway, many thanks in advance for any help with this and cheers to all.
1 Solution

Accepted Solutions
Accepted Solution!

i could be wrong , but i

i could be wrong , but i think the initial size is set in the database field? i'll check
and my original username JesusWept was when i was a symantec employee, but the forum admins wouldn't let me keep the username so i had to change it, my imagination was strong that day, so i added a 2 to the end
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post

4 Replies

you can probably just turn

you can probably just turn the monitoring off or set the initial size of the logs to be 100MB (which i believe is the default for all EV databases)

https://www.linkedin.com/in/alex-allen-turl-07370146

Hi JesusWept2 I've increased

Hi JesusWept2

I've increased it to 50MB for now and the alarm has gone. The consultant who installed EV set the initial size to 33MB so I'm going to chase him to see why.

Thanks for the help and what happended to JesusWept1?

I would set it to auto-grow

I would set it to auto-grow 10% that way you just need to keep watch on the disk space and the logs will take care of themselves

Also I would make sure that you have a maintenance plan in place on your SQL server to re-index weekly, truncate the event logs every 15 mins to a separate directory where you can backup the truncated logs and delete them from disk, and weekly do a compression of the logs and databases
Finally do a daily backup to disk of your databases (same time you backup your indexes and vault storage)
Accepted Solution!

i could be wrong , but i

i could be wrong , but i think the initial size is set in the database field? i'll check
and my original username JesusWept was when i was a symantec employee, but the forum admins wouldn't let me keep the username so i had to change it, my imagination was strong that day, so i added a 2 to the end
https://www.linkedin.com/in/alex-allen-turl-07370146

View solution in original post