is the distribution cleanup job enabled\succeeding?

I'm torn here because I don't want to drop you in the proverbial.

the CORRECT way to fix this would be to stop the instance, restart in single user mode...

recovery mode is full now but you said yourself you set it to simple to do the reindex. Set it to simple for any length of time and log shipping...

is the same [problem as post

http://www.sqlservercentral.com/Forums/Topic525511-265-1.aspx#bm525717

because it looks like they are. Its confusing to multi-post.

Find out whats happened to the G:\sqldata directory and your both issues (suspect databases and backup...

by putting the database into simple mode you have broken the log chain. there are now missing lsns (they were truncated from the tran log) so you will not be...

jeez, how to make something as simple as backing up databases complicated.

If you have suspect databases that will cause job to fail.

Are you using SQLLitespeed or not, unfortunately these store...

yes please post SP usp_waitforprocess, and the full script in step 2. this is unusual logic if all you want to do is backup the databases .

meanwhile try commenting out...

check the errorlog to see if it gives any clues as to why they are in suspect mode, perhaps the database files are missing?

if they are marked suspect/offline just use...

why is job starting at step 2 and what does step 1 do?

no messages about incorrect lsn's or an earlier log being required?

any errors from the restore job in scenario 1?

did anyone take any manual tran log backups during those 10 hours in scenario 1? (check the errorlog)

Mike Hunsaker (6/27/2008)

---

We had a consultant come in and help us establish best practices for managing our database environment. Don't laugh... here's the suggestion he gave us for disk...

no way of answering that without knowing the types of queries run against the table.

as ExpenseRequestLineItem is a foreign key good chance it is used in joins so an index...

sorry, are you trying to backup to a different server than SQL is running on?

is SQL running under the system account or a domain account?

this is weird. Did the DBA leave under a cloud because he may have left you a leaving present and possibly hacked the sysdatabases table. Or maybe he saw this...