I'm not asking you to test it on a test database (and besides, getting a test DB into SUSPECT is not trivial). You have a suspect database. Please try and take a tail log backup (no_truncate, not no_recovery) and, if it fails, please post the error.
I mean, this is now a 3-month old problem, with unknown cause (because of missing errorlog files), so we have ZERO information as to the cause, and hence it's just about impossible to say anything at this point
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass