VSS Snapshot Creation Delay on Server with DFSR Enabled
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Oops! Something went wrong.
Please, try again later.
Article Applicability
The issue described in this article affects earlier versions of Veeam Agent for Microsoft Windows (VAW), however, the solution provided will only work with VAW 6.1.2 and higher.
Challenge
When backing up a server with the DFS feature enabled, the VSS snapshot creation step in the Veeam Agent for Microsoft Windows (VAW) backup job can take several hours or even days to complete.
Cause
During the VSS preparation phase, Veeam Agent for Microsoft Windows (VAW) prepares VSS writers for a snapshot. When interacting with the DFS VSS writer, VAW can get into a recursion while checking the files within the scope of the DFS writer; this recursion can significantly affect performance. The more files located on the volume with DFS, the longer it takes to finish the preparation steps. The issue is most notably observed on volumes with more than a million files.
Solution
To exclude the DFS writer from the preparation phase, add the following registry key to the server where Veeam Agent for Microsoft Windows is installed:
Note: This registry value requires at minimum Veeam Agent for Microsoft Windows 6.1.2.134.
Key Location: HKLM\SOFTWARE\Veeam\Veeam Endpoint Backup\
Value Name: VSSExcludeDFSWriter
Value Type: DWORD (32-Bit) Value
Value Data: 1
Set registry value using PowerShell:
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.