This post is more than 5 years old

1 Rookie

 • 

39 Posts

1232

June 13th, 2008 06:00

Proper way to exclude SQL files from backup

It appears that my file level backups are actually backing up some of the SQL files on my SQL Servers. The reason I say this is, when I do a file level backup of the system, it puts an entry in the SQL transaction log that then screws up my SQL backups. What is the proper way to exclude all SQL files from file level backups? Here is my current MSSQL exclude directive that obviously isn't working:

<< "C:\" >>
+skip: *.ldf *.LDF *.mdf *.MDF *.ndf *.NDF
+aes: *.*
+compressasm: .

<<"C:\i386">>
+skip:.?**

<< "D:\" >>
+skip: *.ldf *.LDF *.mdf *.MDF *.ndf *.NDF
+aes: *.*
+compressasm: .

<< / >>
+skip: *.ldf *.LDF *.mdf *.MDF *.ndf *.NDF
+aes: *.*
+compressasm: .

Thank you!

86 Posts

June 13th, 2008 07:00

With the way directive is currently written unless the log files are in the root of the D drive, they will not be excluded.

Example:

D:\mysqldb.ldf
D:\mysqldb.mdf

Write the directive like this and make it first, meaning it should be the first thing in the directive. <<[space]/[space]>>

<< / >>
+skip: *.ldf
+skip: *.mdf

1 Rookie

 • 

39 Posts

June 13th, 2008 07:00

It's on the D:

86 Posts

June 13th, 2008 07:00

Stupid question but on what drive are the SQL data and log files located?
No Events found!

Top