Data and Xlog file still locked after SQL Server service stops

Last Post 29 Apr 2008 11:17 AM by whale. 1 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
whale
New Member
New Member

--
29 Apr 2008 07:06 AM
Once a week, I drop the three instances on our SQL Server 2000 production machine for a cold backup. I do so using the following script:

net stop "SQLSERVERAGENT"
net stop "SQLAGENT$MIS"
net stop "SQLAGENT$ADP"
net stop "MSSQLSERVER"
net stop "MSSQL$MIS"
net stop "MSSQL$ADP"

Within the last month I have had issues of databases being broken during the cold backup. First of all these instances to appear to go down. The event logs note both the the request and completion of the services stopping. This is done 15 minutes before the backup starts. Once the backup starts there are both data files and xlogs file that are locked and cannot be backed up. But not all of the files, for instance the files for one instance may backup, but not for another.

Can anyone tell me if a session in progress can cause an instance to wait for the session to complete before allowing a shutdown?

whale
New Member
New Member

--
29 Apr 2008 11:17 AM
It's a company policy to complete a full system backup for bare metal recovery. This is best done with the database down.
You are not authorized to post a reply.

Acceptable Use Policy