Problem with excessive edb*.log files

[Guest]

One of my servers is having its drive space eaten up by EDB log files. So far
there are 172 of the, going from edb00003.log up to edb000AC.log. I noticed
edb00001.log and edb00002.log are not there. The earliest have time stamps of
10 months ago.

The users don't find any problem with active directory, and any new users or
computers I create get put into Active Dir. just fine. If these log files are
suppossed to hold the updates until they are processed into the Active Dir.,
why are my updates going in and these files not being deleted?
Could there be a problem with edb.chk?

 

[Chris Malone]

I dont know what build you're on (I hope you're still not on w2k RTM)
but if you are have a look at:
http://support.microsoft.com/kb/272425/EN-US/

There is also a problem with many edb.log files being created if you
use Veritas 8.6 to back up the system state. The only other thing that
comes to mind is that someone found a way to disable circular logging
for AD , but I doubt this.

chris

 

[Guest]

We are on SP4, and we are using Veritas BackupExec 8.6 to backup the system
state. Should we use NTBackup to backup the system state to a file, and then
have Veritas backup that file?
Or just move to Veritas 10?

 

[Chris Malone]

Veritas v.10 shouldnt have that bug. You should also be safe with
ntbackup since the problem was only evident in RTM/sp1.

chris

 

[Guest]

NTbackup would be Ok except for the fact it doesn't have software
compression, which will effectively half the tape space for us.