The fun with SnapManager continues. It's been days now mirroring/reseeding a VLDB (5TB). Yesterday during the mirror, we ran out of space on the log volume snap partition which in turn took all the DBs offline. From what I can tell given the fact that two of my DBs came back suspect, it's not a graceful shutdown.

From SQL Log:

Error: 17207, Severity: 16, State: 1.

FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'E:\SQL_LOG\DBName.ldf'. Diagnose and correct the operating system error, and retry the operation.

File activation failure. The physical file name "E:\SQL_LOG\DBName.ldf" may be incorrect.

The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due to a hardware or environment failure.

Luckily this was to an internal dev/research db and the loss of data is tolerable. As such, I was able to bring the DBs online by detaching and re-attaching just the .mdf files.

This is not the first time we've had issues with snap partitions filling up and DBs going offline. Do to our recent experience, this is a risk we're not willing to tolerate and are moving back to native backups and copy jobs.