cancel
Showing results for 
Search instead for 
Did you mean: 

backup sql server

hellomam
Level 2

i got problem below when backup sqlserver with Symantec netbackup 7.1 :

10/7/2013 8:06:56 AM - Warning bpbrm(pid=6544) from client 10.1.6.238: WRN - can't open file: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\distribution.MDF (WIN32 32: The process cannot access the file because it is being used by another process. )
10/7/2013 8:06:56 AM - Warning bpbrm(pid=6544) from client 10.1.6.238: WRN - can't open file: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\EFB.mdf (WIN32 32: The process cannot access the file because it is being used by another process. )
10/7/2013 8:06:56 AM - Warning bpbrm(pid=6544) from client 10.1.6.238: WRN - can't open file: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\EFB_1.ldf (WIN32 32: The process cannot access the file because it is being used by another process. )
10/7/2013 8:06:56 AM - Warning bpbrm(pid=6544) from client 10.1.6.238: WRN - can't open file: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf (WIN32 32: The process cannot access the file because it is being used by another process. )
10/7/2013 8:06:56 AM - Warning bpbrm(pid=6544) from client 10.1.6.238: WRN - can't open file: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf (WIN32 32: The process cannot access the file because it is being used by another process. )
10/7/2013 8:06:56 AM - Warning bpbrm(pid=6544) from client 10.1.6.238: WRN - can't open file: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\model.mdf (WIN32 32: The process cannot access the file because it is being used by another process. )
10/7/2013 8:06:56 AM - Warning bpbrm(pid=6544) from client 10.1.6.238: WRN - can't open file: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\modellog.ldf (WIN32 32: The process cannot access the file because it is being used by another process. )
10/7/2013 8:06:56 AM - Warning bpbrm(pid=6544) from client 10.1.6.238: WRN - can't open file: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf (WIN32 32: The process cannot access the file because it is being used by another process. )
10/7/2013 8:06:56 AM - Warning bpbrm(pid=6544) from client 10.1.6.238: WRN - can't open file: C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\MSDBLog.ldf (WIN32 32: The process cannot access the file because it is being used by another process. )
10/7/2013 8:06:56 AM - Info bpbrm(pid=6544) from client 10.1.6.238: TRV - last message being suppressed aft

Could you give me some advice for issue ?

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You need to exclude SQL data file (*.mdf, *.ldf, etc) from MS-Windows backup.

Use NBU agent to backup SQL databases or else SQL built-in backup tool to backup databases to disk which will be included in MS-Windows backup.

View solution in original post

5 REPLIES 5

huanglao2002
Level 6

Hi 

You should backup sql server by netbackup for sql agent.

If you want to backup database files,you can stop sql server first ,then backup all the data files.

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You need to exclude SQL data file (*.mdf, *.ldf, etc) from MS-Windows backup.

Use NBU agent to backup SQL databases or else SQL built-in backup tool to backup databases to disk which will be included in MS-Windows backup.

Shoeb_Sayyed
Level 3
Partner Accredited
Dude, Files are in use at the time of backup. stop the db before taking backup, or use NBU agent to take SQL backup.

R_Sathish_Kumar
Level 3

Use Netbackup SQL Agent utility to take Microsoft SQL server databases.

Michael_G_Ander
Level 6
Certified

If you do not want use the SQL agent for some reason, set up a maintenance plan in the SQL server to run backup to disk and backup the resulting files with Netbackup.

Cannot recommend it as you get a more complex and probably longer restore/recovery process

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue