It is an inherited system, and I've traditionally been an operational DBA more than a programmer, having come from an infrastructure background.

Unfortunately, I don't have any historical data. That...

Wow guys, I can't thank you enough. The 2nd link from Steve is exactly what I was hoping for.

I'll throw in my vote for redgate SQL backup or litespeed as well. I have several DBs of aroun 7TB which all compress to well under 1 TB each...

I did take a full backup, no issues. no errors in any logs.

I was unable to move the DB to simple recovery mode. I was able to restart SQL without a huge recovery. This is very good, as last time...

Atul DBA (12/4/2009)

---

Did you try to kill the Backup process id manually? Kill the backup process ID forcefully and then run the full backup. Changing the database from Full to...

According to SQL, nothing is blocking it.

Over 693K seconds.

I'm planning on changing to simple recovery mode, then back to full, then running a full backup unless someone can tell me a good reason not to.

Since I...

Now at 562K seconds. Log file is not growing significantly at this time.

Anyone?

The log file isn't too large-- it just didn't free any space inside it since the log backup didn't occur. It is growing because of the amount of data...

Ugh.

So here is the final response from MS. Not terribly helpful.

I verified the logs and could not find the Root cause of this issue.

Have my Technical lead reviewed those...

dbcc loginfo(<db name>) now results in 604 vlfs, growth is set to 5000MB. We did run a dbcc checkdb and got the following:

CHECKDB found 0 allocation errors and 0...

Sorry for the confusion... it is at least partiall my fault.

When the recovery had been running for 20+ hours, I kicked off a restore of a recent backup so that...

2.1 billion transactions rolled forward. 34 rolled back.

It finally finished around noon. I have had a few hours sleep now, and will be taking a fresh look at...

May have found the culprit. Will post more once I can think clearly, as I'm going on 22 hours here, but it looks like one of the 3 data...