July 27, 2009 at 12:58 pm
In my SQL logs I get the following messages for 'model4IDR'. and 'master4IDR'.
Message
Starting up database 'master4IDR'.
The database 'master4IDR' is marked RESTORING and is in a state that does not allow recovery to be run.
Starting up database 'master4IDR'.
CHECKDB for database 'master4IDR' finished without errors on 2009-07-22 23:02:45.277 (local time). This is an informational message only; no user action is required.
atabase was restored: Database: master4IDR, creation date(time): 2009/07/22(02:28:56), first LSN: 294:368:37, last LSN: 294:392:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'RESTORE_restore_'}). Informational message. No user action required.
Could not start Service Broker for database id: 18. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.
How can I find out what is master4IDR and what these messaged mean and who is doing that and what is doing to my db? Our 4 db all of all tables data got deleted and I am trying to see what happend.Thank you
July 27, 2009 at 1:56 pm
Hi..
Do you have any database with name maste4IDR?
It's a info message displayed after DBCC command run on your database.
If you get this message regularly check if there is any job created for it in maintenance plan or under jobs.
Shree
July 27, 2009 at 2:18 pm
shripati (7/27/2009)
It's a info message displayed after DBCC command run on your database.If you get this message regularly check if there is any job created for it in maintenance plan or under jobs.
Nope, actually it's displaying the date and time of the last known good run of CheckDB. When CheckDB runs and doesn't find any errors, it updates a datetime in the database header page. Each time the database is started (at server startup or when it's brought online), SQL will read that and write into the error log a message saying when checkDB last ran without errors.
This looks like a restore of a database called maste4IDR. That's not a system or standard database, either it's something you or your predecessors set up, or it's something that an app you're running has set up.
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
July 28, 2009 at 6:23 am
No, I don't have maste4IDR set up, I don't see it anywhere and I don't know where it is comming from
July 28, 2009 at 8:15 am
Did you check what GilaMonster said? Is there an application creating these?
Since your backup is using a virtual device and the databases have IDR in them, I'd guess your backup software is going to tape and creating the databases in some sort of IDR (usually,- intelligent disaster recovery) test afterwards.
Edit-
Decided to do a quick google search --- found like 1000 pages mentioning these databases and veritas(symantec) backup exec..
July 29, 2009 at 10:53 am
It is indeed related to Backup Exec. I have seen these on some of our older servers where Backup Exec has been removed.
Beth Richards
Sybase, Oracle and MSSQL DBA
July 26, 2010 at 12:55 am
bethrich (7/29/2009)
It is indeed related to Backup Exec. I have seen these on some of our older servers where Backup Exec has been removed.
Yes.
July 26, 2010 at 2:20 am
Please note: Year-old thread.
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
September 22, 2011 at 11:16 am
Backup Exec indeed. I have a a few SQL servers with Backup Exec on them. The older Backup Exec versions with Intelligent Disaster Recovery use DB's with the IDR suffix.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply