We have a distribution database on a dedicated distributor server which went into suspect mode. The reason we believe to be that the log file size was limited to 2Gigs when we upgraded it from 2000 to 2008. The upgrade process worked fine and we've been using the server successfully ever since until this morning. The size of the LOG file is 24Gigs despite the size limitation and that is probably because it was like that at the moment when the upgrade was done. Due to some increasingly replication activity probably the db tried to increase the log file even more but failed due to the limitation and started to through errors. At that point we restarted the server but it shows suspect mode after finishes the restart.
We have a backup until the problem started this morning.
What are the options?
Don't just give the hungry man a fish, teach him how to catch it as well.