Our Differential backups will succeed one night and then fail the next. We suspect it is either related to the following logs

Every day at 7:19 we get this sequence of events in the log for each database we have in SQL Server

I/O is frozen on database DATABASENAME No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.

I/O was resumed on database DATABASENAME No user action is required.

Database backed up. Database: DATABASENAME, creation date(time): 2010/11/04(23:28:04), pages dumped: 841, first LSN: 35:483:37, last LSN: 35:499:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{F8C10393-542B-4491-8135-BE0545F42EBE}22'}). This is an informational message only. No user action is required.


that related to our online backup software Mozy.

Any ideas?

  • Please not the backups that are failing are scheduled in SQL Server Maintenance Plan and failing with the error – cpgascho Nov 23 '10 at 19:23

We've seen this before with Mozy when it runs on a scheduled basis, it resets the archive bit and then SQL Server can't recognize the last full backup and the differentials fail. Assuming at this point if you use the Mozy agent it will work for you.

| improve this answer | |
  • Tony's response below seems to bear merit although it states its an exchange bug, perhaps it spans across into their SQL backup product as well. – NateReid Nov 25 '10 at 15:15

This is known error for MozyPro. Their technical support is still working on it to fix this issue. As you can see from this below post:


| improve this answer | |

I've seen this message when the Symantec tape backup product is used to backup SQL Server databases.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.