Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Exclude List

Created: 23 Jul 2013 • Updated: 18 Sep 2013 | 11 comments
This issue has been solved. See solution.

*** Moved to new discussion from: https://www-secure.symantec.com/connect/forums/excluding-sql-files-file-level-windows-backup ***

I have the following exclusions:

*.ldf

*.mdf

*.ldf

 

However, in my job details i see:

7/22/2013 9:24:34 PM - Warning bpbrm(pid=26816) from client vsdb02: WRN - can't open file: E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\master.mdf (WIN32 32: The process cannot access the file because it is being used by another process. )
7/22/2013 9:24:34 PM - Warning bpbrm(pid=26816) from client vsdb02: WRN - can't open file: E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mastlog.ldf (WIN32 32: The process cannot access the file because it is being used by another process. )
7/22/2013 9:24:34 PM - Warning bpbrm(pid=26816) from client vsdb02: WRN - can't open file: E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\model.mdf (WIN32 32: The process cannot access the file because it is being used by another process. )
 
 
I cant find any of the specified file types when attempting a restore, so i assuming bptm is generating this WRN prior to exclusions being applied via bpbkar.
 
Please advise if my logic is fail. 
Operating Systems:

Comments 11 CommentsJump to latest comment

Marianne's picture

If Exclude List is functioning correctly, there should be no attempt to backup these files.

Please ensure that bpbkar log folder exist on the client.. Copy log file to bpbkar.txt after next backup and post here as File Attachment.

Also post output of this command on the master server:

bpgetconfig -M vsdb02 |findstr Exclude
(command is in ...\netbackup\bin\admincmd)

What is NBU version on this client?
Is it part of a cluster?
There was a bug with certain NBU versions: http://www.symantec.com/docs/TECH144007

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Stumpr2's picture

check the backup images for any SQL db files. You may find some from static/unused small dbs.
If the *.ldf *.mdf *.ndf are not working then try using the absolute path found in results from following:

bplist -C $CLIENT -t 13 -l -PI -s 07/01/2013 -e 07/31/2013 *.ldf

bplist -C $CLIENT -t 13 -l -PI -s 07/01/2013 -e 07/31/2013 *.mdf

bplist -C $CLIENT -t 13 -l -PI -s 07/01/2013 -e 07/31/2013 *.ndf

 

VERITAS "Ain't it the truth"?

VERITAS ain't it the truth?

phoenix24x1's picture

Hey All

FIrst off, thank you for your replies and sorry it took so long to get back.

The bpbkar log and output of bpgetconfig are attached. The client is on 7.5.0.4 and is not clustered. I reviewed the technote but see no references to 7.5.

I may see the problem in the bpbkar:

8:08:31.807 AM: [6776.7240] <16> file_access::V_OpenForRead: ERR - CreateFile() failed: \\?\E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\master.mdf (WIN32 32: The process cannot access the file because it is being used by another process. )

Is the "\\?\E:\...." causing the issue?

AttachmentSize
client_bpbkar.txt 1.62 MB
client_bpgetconfig.txt 719 bytes
phoenix24x1's picture

Stumpr2:

the output from the bplist command is below. I can certainly exclude via the absolute path and will do so if necessary. However I would like to figure out why this is not working in its current config.

-rwx------ root;Admi root;Doma     5242880 Nov 24  2008 E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\distmdl.mdf
-rwx------ root;Admi root;Doma    40304640 Nov 24  2008 E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mssqlsystemresource.mdf
-rwx------ root;Admi root;Doma     5242880 Nov 24  2008 E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\distmdl.mdf
-rwx------ root;Admi root;Doma    40304640 Nov 24  2008 E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mssqlsystemresource.mdf
-rwx------ root;Admi root;Doma     5242880 Nov 24  2008 E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\distmdl.mdf
-rwx------ root;Admi root;Doma    40304640 Nov 24  2008 E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mssqlsystemresource.mdf
-rwx------ root;Admi root;Doma     5242880 Nov 24  2008 E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\distmdl.mdf
-rwx------ root;Admi root;Doma    40304640 Nov 24  2008 E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mssqlsystemresource.mdf
-rwx------ root;Admi root;Doma     5242880 Nov 24  2008 E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\distmdl.mdf
-rwx------ root;Admi root;Doma    40304640 Nov 24  2008 E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mssqlsystemresource.mdf
-rwx------ root;Admi root;Doma     5242880 Nov 24  2008 E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\distmdl.mdf
-rwx------ root;Admi root;Doma    40304640 Nov 24  2008 E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mssqlsystemresource.mdf

Marianne's picture

The TN that I've mentioned is for NBU 7.1

This does not seem right : bpbkar first lists the files and only then add it to Exclude List:

8:08:31.838 AM: [6776.7240] <4> dos_backup::tfs_scannext: INF - detected renamed/new file:<E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\templog.ldf>, forcing backup
8:08:31.838 AM: [6776.7240] <16> file_access::V_OpenForRead: ERR - CreateFile() failed: \\?\E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\templog.ldf (WIN32 32: The process cannot access the file because it is being used by another process. )
8:08:31.838 AM: [6776.7240] <2> tar_base::V_vTarMsgW: WRN - can't open file: E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\templog.ldf (WIN32 32: The process cannot access the file because it is being used by another process. )
8:08:31.838 AM: [6776.7240] <4> dos_backup::V_AddToExcludeAfterList: INF - file will be skipped during cleanup processing:<E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\templog.ldf>

 

I am running NBU 7.5.0.4 on my laptop and do not have the same issue.
Everything that appears in my Exclude List is skipped - no error in Activity Monitor or in bpbkar. 

All I can suggest is to go with Bob's suggestion: try using the absolute path in Exclude List.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Will Restore's picture

Incremental schedule running but many files "renamed/new" (not just .mdf .ldf)

8:07:45.776 AM: [6776.7240] <4> dos_backup::tfs_scannext: INF - detected renamed/new file:<C:\Program Files\Symantec\Symantec Endpoint Protection\12.1.2015.2015.105\Bin\service.dat>, forcing backup
8:07:45.776 AM: [6776.7240] <16> file_access::V_OpenForRead: ERR - CreateFile() failed: \\?\C:\Program Files\Symantec\Symantec Endpoint Protection\12.1.2015.2015.105\Bin\service.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
8:07:45.776 AM: [6776.7240] <2> tar_base::V_vTarMsgW: WRN - can't open file: C:\Program Files\Symantec\Symantec Endpoint Protection\12.1.2015.2015.105\Bin\service.dat (WIN32 32: The process cannot access the file because it is being used by another process. )
8:07:45.776 AM: [6776.7240] <4> dos_backup::V_AddToExcludeAfterList: INF - file will be skipped during cleanup processing:<C:\Program Files\Symantec\Symantec Endpoint Protection\12.1.2015.2015.105\Bin\service.dat>

 

Run Full backup from same Windows-SQL-OS policy then retry the Incremental.

Will Restore -- where there is a Will there is a way

phoenix24x1's picture

Ill raise a case with support and get their input.

 

Thanks All!

phoenix24x1's picture

higher priority issues have delayed investigation/resolution.

Ill provide an update when possible. 

Mark_Solutions's picture

I see that you have two exclude lists for this client.

The first is set as all policies / schedules and contains:

Exclude = *.bak
Exclude = *.ldf
Exclude = *.mdf
Exclude = *.ndf
Exclude = C:\Program Files\Symantec\Symantec Endpoint Protection\*
Exclude = C:\Program Files\Veritas\NetBackup\bin\*.lock
Exclude = C:\Program Files\Veritas\NetBackup\bin\bprd.d\*.lock
Exclude = C:\Program Files\Veritas\NetBackup\bin\bpsched.d\*.lock
Exclude = C:\Program Files\Veritas\NetBackupDB\data\*
Exclude = C:\Program Files\Veritas\Volmgr\misc\*
Exclude = C:\ProgramData\Symantec\Symantec Endpoint Protection\*
Exclude = C:\WINDOWS\system32\NtmsData\NTMSDATA
Exclude = E:\Prosolv Database

The second is set for the policy Windows-SQL-OS and contains:

Exclude = F:\
Exclude = O:\
Exclude = S:\
OTM_Exclude = 0
VSP_Exclude =
Case_Sensitive_Exclude_List = NO
 

So *.ldf, *.mdf etc. will only excluded for policies not named Windows-SQL-OS.

When you run Windows-SQL-OS it will not exclude them - they need to be copied to the exclude list for that policy too if they are to be used

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

SOLUTION
phoenix24x1's picture

I see how you describe and it makes sense, I was incorrect on how NB executes the exclusions.

 

I have modified the exclusions and will let you know.

phoenix24x1's picture

Thanks Mark! That was the ticket