December 9, 2008 at 6:51 pm
Hi all
I always get the error in Log file viewer which is
Sourcespid400
Message
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.
and the very next message is
Sourcespid400
Message
I/O was resumed on database databasename. No user action is required.
I have like loads of such type of messages in the Error Logs and I dont understand what is going on, moreover we are using litespeed for our backups.
Any info on this messages will be helpful.I tried to google whole day but was not able to find anything except this link http://technet.microsoft.com/en-us/library/bb693937.aspx which tells me nothing.
Thanks to all of you
December 9, 2008 at 9:36 pm
You have issues in your IO subsystem. I'd have the vendor check it out.
December 10, 2008 at 12:24 am
Have you got any other backup tools than litespeed? That looks like the kind of messages that a 'snapshot' backup tool would generate. They work by asking SQL to temporarily freeze the IOs to the database (stop them), then take a copy of the data and log files as they are at that point, and then ask SQL to unfreeze the IOs.
Providing you are using a backup tool that does that, and the intervals between freeze and unfreeze aren't big, there's no problem there. However that doesn't look like something litespeed generates. Litespeed does compressed backups, I don't think it does snapshots.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 10, 2008 at 1:57 pm
Hey Gila Thanks alot for such descriptive reply but as far as I am aware I dont think so we are using and I am having trouble to figure it out.
Thanks
December 11, 2008 at 12:14 am
See if you can match the entries in the log to a job.
Running on a SAN?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 12, 2009 at 6:29 pm
Sorry for the delay, was kinna busy with some upgrades. I dont have no jobs on SAN
March 10, 2009 at 4:43 am
Gila is absolutely correct, this is a backup application attempting to snapshot the server including database files. If it helps, the application is running under an account with sysadmin rights to perform this operation (typically NTAUTHORITY\SYSTEM).
Is this server a virtual machine or being backed up to a virtual machine? I only ask as I've seen these messages pop up when doing that.
You'll need to talk to your sysadmin to determine what backup operations are occurring on this server at the time of messages.
Good luck! 🙂
March 10, 2009 at 5:38 am
We have the same messages when our DBs which are hosted on a SAN are being backed up via a snapshot. In our logs the order of the messages usually are:
3) Backup message
2) I/O Resumes
1) I/O Frozen
They usually appear in this order because the I/O resume and backup message have the same timestamp.
Is there any backup messages around theses I/O messages in the log? They may help identify what is generating these messages as the backup message will have the destination.
BackupExec will also use this method to backup SQL DBs.
Regards,
Phil
February 3, 2015 at 8:45 pm
Hey! try using "Ahsay software" it actually gives backup on Virtual machines. I am working on it from the long time and quite impressed with their work. Just give it a try i am leaving a link with this comment just have a look at the software. http://www.ahsay.com/jsp/en/home/index.jsp?pageContentKey=ahsay_products_overview
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply