snapshot and thawed
-
I ama getting ERROR message for all the DB?? any idea what is this
2005-09-07 14:55:52.17 spid62 Database Northwind: IO is thawed
2005-09-07 14:55:51.53 spid50 Database master: IO is frozen for snapshot
2005-09-07 14:55:52.17 spid50 Database master: IO is thawed
Thanks in advance
Nita
-
Database master: IO is frozen for snapshot
= start of taking a snapshot
Database master: IO is thawed
= taking of snapshot finished. (?)
Is there replication on the server?
-
Is there anything that leads you to believe that these are errors?
I think that they are evidence that snapshots are being started and completed.
-
What type of backup system do you have? I get these messages to and they seem to be a part of the Tivoli backup system.
I am in the process of confirming this.
-
We used to get them on one of our SANs, basically it took a snapshot of the data every evening and issues a freeze whilst it's working followed by a thaw when it's done.
Normally it didn't cause any problems, but occasionally it didn't come back properly and the server had to be rebooted.
-
No We don't use any replication.
This is the Error I got if from ERRORLOG
2005-09-08 15:00:00.42 spid62 Starting up database 'Prod_SRG'.
2005-09-08 15:00:00.46 spid62 Starting up database 'Micro'.
2005-09-08 15:00:00.49 spid62 Starting up database 'Prod_SRG'.
2005-09-08 15:00:01.20 backup Log backed up: Database: Mirco, creation date(time): 2005/08/15(12:44:53), first LSN: 1499:886:1, last LSN: 1499:926:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'D:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\Mirco_tlog_200509071500.TRN'}).
2005-09-08 15:55:51.53 spid62 Database model: IO is frozen for snapshot
2005-09-08 15:55:51.53 spid63 Database msdb: IO is frozen for snapshot
2005-09-08 15:55:51.53 spid64 Database pubs: IO is frozen for snapshot
2005-09-08 15:55:51.53 spid65 Database Northwind: IO is frozen for snapshot
2005-09-08 15:55:51.53 spid66 Database Fiber: IO is frozen for snapshot
2005-09-08 15:55:51.53 spid67 Database Mirco: IO is frozen for snapshot
2005-09-08 15:55:51.53 spid68 Database CA_State: IO is frozen for snapshot
2005-09-08 15:55:51.53 spid69 Database CA_Micro: IO is frozen for snapshot
2005-09-08 15:55:51.53 spid70 Database Prod_SRG: IO is frozen for snapshot
2005-09-08 15:55:51.53 spid55 Database master: IO is frozen for snapshot
2005-09-08 15:55:52.17 spid55 Database master: IO is thawed
2005-09-08 15:55:52.17 spid69 Database CA_Micro: IO is thawed
2005-09-08 15:55:52.17 spid68 Database CA_State: IO is thawed
2005-09-08 15:55:52.17 spid63 Database msdb: IO is thawed
2005-09-08 15:55:52.17 spid67 Database Mirco: IO is thawed
2005-09-08 15:55:52.17 spid66 Database Fiber: IO is thawed
2005-09-08 15:55:52.17 spid64 Database pubs: IO is thawed
2005-09-08 15:55:52.17 spid62 Database model: IO is thawed
2005-09-08 15:55:52.17 spid70 Database Prod_SRG: IO is thawed
2005-09-08 15:55:52.17 spid65 Database Northwind: IO is thawed
2005-09-08 15:55:52.43 backup Database backed up: Database: CA_State, creation date(time): 2005/08/11(11:21:44), pages dumped: 1, first LSN: 466:18111:1, last LSN: 466:18115:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C03853E-147C-47EA-8949-ED5CA3048D05}8'}).
2005-09-08 15:55:52.45 backup Database backed up: Database: CA_Micro, creation date(time): 2005/08/11(11:24:02), pages dumped: 1, first LSN: 1524:4495:1, last LSN: 1524:4497:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C03853E-147C-47EA-8949-ED5CA3048D05}9'}).
2005-09-08 15:55:52.53 backup Database backed up: Database: model, creation date(time): 2000/08/06(01:40:52), pages dumped: 1, first LSN: 4:93:1, last LSN: 4:95:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C03853E-147C-47EA-8949-ED5CA3048D05}2'}).
2005-09-08 15:55:52.61 backup Database backed up: Database: pubs, creation date(time): 2000/08/06(01:40:58), pages dumped: 1, first LSN: 4:384:1, last LSN: 4:386:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C03853E-147C-47EA-8949-ED5CA3048D05}4'}).
2005-09-08 15:55:52.62 backup Database backed up: Database: Fiber, creation date(time): 2005/08/12(10:52:54), pages dumped: 1, first LSN: 107:1555:1, last LSN: 107:1557:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C03853E-147C-47EA-8949-ED5CA3048D05}6'}).
2005-09-08 15:55:52.71 backup Database backed up: Database: Prod_SRG, creation date(time): 2005/08/15(12:47:04), pages dumped: 1, first LSN: 1498:35458:1, last LSN: 1498:35460:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C03853E-147C-47EA-8949-ED5CA3048D05}10'}).
2005-09-08 15:55:52.71 backup Database backed up: Database: master, creation date(time): 2005/08/09(15:33:34), pages dumped: 1, first LSN: 141:284:1, last LSN: 141:286:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C03853E-147C-47EA-8949-ED5CA3048D05}1'}).
2005-09-08 15:55:52.90 backup Database backed up: Database: msdb, creation date(time): 2000/08/06(01:40:56), pages dumped: 1, first LSN: 151:21:1, last LSN: 151:24:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C03853E-147C-47EA-8949-ED5CA3048D05}3'}).
2005-09-08 15:55:52.93 backup Database backed up: Database: Northwind, creation date(time): 2000/08/06(01:41:00), pages dumped: 1, first LSN: 22:330:1, last LSN: 22:332:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C03853E-147C-47EA-8949-ED5CA3048D05}5'}).
2005-09-08 15:55:53.07 backup Database backed up: Database: Mirco, creation date(time): 2005/08/15(12:44:53), pages dumped: 1, first LSN: 1499:926:1, last LSN: 1499:929:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3C03853E-147C-47EA-8949-ED5CA3048D05}7'}).
2005-09-08 14:00:00.42 spid62 Starting up database 'Micro'.
2005-09-08 14:00:00.59 spid62 Starting up database 'Prod_SRG'.
2005-09-08 14:00:00.67 spid62 Starting up database 'Micro'.
2005-09-08 14:00:00.70 spid62 Starting up database 'Prod_SRG'.
-
See my post above for the expanation
-
You might want to contact the folks who installed you backup software. It is probably the work of an 'agent' that was installed as a part of the backup process.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
-
It is caused by SnapManager software from NetApps. Basically the folks who are in charge of your environment's backups and storage devices installed SnapManager to mirror your database files.
- Ye H. Aung, Database Administrator, Nicholas Applegate Capital Management
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply