Forum Discussion
Each environment is unique.
You need to determine in your own environment what needs to be backed up and what can be excluded.
Look at the status 1 jobs, generate a report of skipped files and go with this list to the server owner to find out if those can be excluded.
It is common practice to exclude database files for SQL, Exchange and other databases and applications as those should be backed up using agents, not file-level backup.
On a Windows-NT policy, the natural behavior is to not back up Exchange database files. The is no need to name them in an exclude list. I have run a test this morning to confirm this.\
Excerpt from my bpbkar log:
[EseE14::AddExcludes] cachedList:F:\RF2DB1\*.log
[EseE14::AddExcludes] cachedList:F:\RF2DB1\*.chk
[EseE14::AddExcludes] cachedList:F:\RF2DB1\*.jrs
[EseE14::AddExcludes] cachedList:F:\RF2DB1\tmp.edb
[EseE14::AddExcludes] cachedList:E:\RF2DB1\RF2DB1.edb
I think the same is true for SQL Server and SharePoint files, but I have not tested them recently.
- Lowell_Palecek8 years agoLevel 6
Correction and follow-up:
I tested an MS-Windows policy backup on the SQL Server backend server for a SharePoint environment. The .mdf and .ldf database files were not automatically excluded.
I cannot find documentation where we say that Exchange database files are excluded from an MS-Windows backup, but that is demonstrably true. I will initiate a TechNote to document it.
- sdo8 years agoModerator
If you exclude *.[lmn]df on Windows backup clients which contain MS SQL Server instances, then also be sure to include mssqlsystemresource.[lm]df as per:
Related Content
- 10 years ago
- 12 years ago
- 11 years ago