priv.edb has old date, edb.chk claims all is well

[sladd]

NT 4.0 SP6a Exhange 5.5 sp4

2 weeks ago I deleted 30-40 mailboxes. I did not run performance optimizer afterward. My priv.edb has a last modified date of 6 days ago (I've never seen it more than 3 hours behind current time). When I run a eseutil /mk on edb.chk against priv.edb it tells me the last committed log file is edb.log - that is to say the number listed is one higher than the last ebd#####.log in the list).

Sooo, according to edb.chk, all is well. But, Priv.edb modified date is scaring the hell out of me. Last known good backup is 2 months old although I have all edb*.log files. I'm scared to bring the service down to see if everything is indeed ok.

Sure, I'm an idiot for not having more recent backups - not all my fault (in my mind at least) - another story all together.

Can anyone advise if they have ever seen priv.edb not have a current modified date while having edb.chk show that everything has already been committed. It would help me sleep a lot better at night - otherwise I'll continue my disaster recovery plans...

 

[zbnet]

File explorer can have problems reading the correct information off a file that is locked open for writing, which is effectively what the IS service is doing to priv.edb for as long as the service is running. I wouldn't be too concerned about the file properties.

I would be far more concerned that you don't have an up-to-date online backup. If you aren't running regular online backups, how can you be sure that your database isn't corrupt?