We recently started seeing SQLVDI and MSSQLSERVER errors poping up on a number of our machines. Shortly after event 3197 (I/O is frozen on database x), we start seeing SQLVDI 1 errors (signal abort) and MSSQLSERVER 3041 errors, failure to complete the command BACKUP DATABASE. We run our backups once daily, and looking at our DB backups, they restore fine and are not corrupt. But batches of these errors are happening throughout the day, with no logs of our maintenance plans attempting to run at those times. Even stranger, we are seeing these errors occouring on machines that do not have SQL Server 2012 installed. Any ideas as to what might be causing these errors? or if they can be passed off as nuisance errors?
Asked
Active
Viewed 2,245 times
2
-
It's some kind of snapshot, a VM snapshot, tape backup software or similar. – Tara Kizer Sep 13 '16 at 19:47
-
A VM snapshot would cause the databases to lock their IO? – Alex Sep 13 '16 at 20:02
-
1Alex, yes it will. It has to quiesce the database files since they are open. It should happen very fast, but it will freeze I/O. It's why VM snapshots are not viable if your RPO is pretty low. – Tara Kizer Sep 13 '16 at 20:04
-
BACKUP .. with SNAPSHOT will FREEZE the I/O for the database and report to the VDI consumer that the database I/O is frozen. – Kin Shah Sep 13 '16 at 20:19
1 Answers
2
There's an external backup running via VSS (Volumne Shadow Copy Service), might be a VM snapshot, SAN snapshot or similar. It freezes I/O briefly to quiesce it since the files are open.
Reach out to your Windows admin for what's going on during that timeframe.
See this related post.
Tara Kizer
- 5,956
- 1
- 15
- 28