August 24, 2009 at 12:19 pm
Hi,
I have Installed an instance of SQL Server 2005 a month ago and we are not using that instance for any application right now, just the instance is there with system databases.
I have noticed the below messages in the error log and I did not understand what exactly happend on that particaulr time. It says No user action required but I would like to know what this message about.
2009-08-08 00:00:25.17 spid13s This instance of SQL Server has been using a process ID of 1552 since 7/7/2009 9:46:52 AM (local) 7/7/2009 4:46:52 PM (UTC). This is an informational message only; no user action is required.
2009-08-08 21:51:00.62 spid51 I/O is frozen on database msdb. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2009-08-08 21:51:00.63 spid53 I/O is frozen on database model. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2009-08-08 21:51:00.63 spid54 I/O is frozen on database master. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2009-08-08 21:51:01.79 spid51 I/O was resumed on database msdb. No user action is required.
2009-08-08 21:51:01.79 spid53 I/O was resumed on database model. No user action is required.
2009-08-08 21:51:01.79 spid54 I/O was resumed on database master. No user action is required.
2009-08-08 21:51:01.90 Backup Database backed up. Database: master, creation date(time): 2009/07/07(09:46:50), pages dumped: 1, first LSN: 195:280:50, last LSN: 195:312:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'BE_SQLAgent-master__a4985483_5e85_4510_b49e_2d85eabe3f1b_'}). This is an informational message only. No user action is required.
2009-08-08 21:51:01.94 Backup Database backed up. Database: msdb, creation date(time): 2005/10/14(01:54:05), pages dumped: 1, first LSN: 71:288:57, last LSN: 71:320:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'BE_SQLAgent-msdb__232c8450_0c2c_4952_bca2_a3ab38f2a088_'}). This is an informational message only. No user action is required.
2009-08-08 21:51:01.94 Backup Database backed up. Database: model, creation date(time): 2003/04/08(09:13:36), pages dumped: 1, first LSN: 16:80:37, last LSN: 16:104:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'BE_SQLAgent-model__530b9d37_fb54_4456_a016_c9c8bca37780_'}). This is an informational message only. No user action is required.
2009-08-09 00:00:06.37 spid15s This instance of SQL Server has been using a process ID of 1552 since 7/7/2009 9:46:52 AM (local) 7/7/2009 4:46:52 PM (UTC). This is an informational message only; no user action is required.
August 24, 2009 at 12:37 pm
looks like one of the third party tape backup tools that take a hot backup of SQL databases by temporarily 'freezing' the files and taking a snapshot of them.
I would still take your own native backups of the system databases.
---------------------------------------------------------------------
June 20, 2012 at 12:36 am
Hi there,
Thought it would be easier to reply to this thread instead of creating a new one.
I have a question regarding these snapshots. As far as I know it should not be noticeable to the end user (working on the application) that the IO is frozen correct? If they experience hangs during these snapshots then something must be wrong? When reviewing the logs it shows that the snapshots take up to 7 minutes.
Could fragmentation be the reason, or anything else I'm missing?
Thanks
June 21, 2012 at 10:55 pm
refer this link to see if it helps you.
June 22, 2012 at 12:12 am
Thanks for the reply.
But I have read this and it's not related.
I think this may be file fragmentation as both drives (log and db) sits at about 99% and this has only started being a problem a few weeks ago. I will be performing some maintenance this weekend.
Regards
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply