August 5, 2008 at 6:23 am
I have an installation of SQL Server 2005 Standard Edition running in production. I have noticed that there are entries in the logs once a month that indicate that some of the system databases, master, msdb, model, ReportServer and ReportServerTempDB, are being backed up. The strange thing is that I do not have jobs that correspond to these backup times. I queried the msdb.sysjobs table, but nothing appears there to give me any hints. I also cannot find any backup files on the server. The entry in the log is:
Database backed up. Database: master, creation date(time): 2008/06/15(10:51:44), pages dumped: 1, first LSN: 202:424:37, last LSN: 203:32:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{3663CF62-6EB8-4D96-8266-DBF74F115802}1'}). This is an informational message only. No user action is required.
Wondering if there is some auto setting that is causing this to happen. I have my own backups scheduled for these databases, but is bothering me that these are showing up in the log and I don't know why.
August 5, 2008 at 8:32 am
I think I just figured out what is happening. There is a LiveState backup happening at the time of the log entries that backs up the entire drive where the database files reside. I think they are causing it to lock temporarily.
August 11, 2008 at 9:21 pm
Watch out for apps backing up their own databases. They may be useful for places that don't have a DBA to look after things properly but otherwise get in the way. I had one recently with Symantec Antivirus Reporting server - it was trying to backup its database to a folder that didn't exist.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
August 11, 2008 at 9:52 pm
Scott has good advice, but I don't see a lock. A database backup can occur without interrupting activity.
August 12, 2008 at 5:09 am
Thanks for the advice. I will continue monitoring and do additional troubleshooting if it starts causing issues in the database.
August 17, 2008 at 2:52 pm
Scott Duncan (8/11/2008)
Watch out for apps backing up their own databases. They may be useful for places that don't have a DBA to look after things properly but otherwise get in the way. I had one recently with Symantec Antivirus Reporting server - it was trying to backup its database to a folder that didn't exist.
:laugh: yes been caught with this one too. Kept seeing failed backup ops in the log. Managed to login to Symantec reporter web interface and found a settings page which had backup enabled to a default folder which didnt exist on the sql server (i think it assumes that the sql instance and web services are the same host)
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply