Comments
Sort by recent activity
We encountered a similar error today where it appeared as if a Txn log backup was still processing from 4 days ago, even though the job history did not indicate an error. I closed the client and opened it back up and it disappeared.
We are doing backups with VERIFY_ONLY. Is there a fix/patch in place to resolve this issue or do we need to turn off the VERIFY_ONLY option?
(SQL Server 2005 with SP4 32bit Clustered)
Regards.
Paul / comments
We encountered a similar error today where it appeared as if a Txn log backup was still processing from 4 days ago, even though the job history did not indicate an error. I closed the client and ...
6.5.1.9 is the version we are on. Here are the parameters from the job.
WITH ERASEFILES = 3, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 0, INIT, THREADCOUNT = 7, VERIFY / comments
6.5.1.9 is the version we are on. Here are the parameters from the job.
WITH ERASEFILES = 3, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 0, INIT, THREADCOUNT = 7, VERIFY