Dima P. wrote:Hello Carloton, sorry for the delay.
We reviewed the case and the given information looks correct: whenever you include the entire volume to file level backup scope file masks are going to be ignored. However, I can confirm that path exclusion should work if entire volume selected as a source i.e. you can add volume C to the source items and then add D:\Users\ to exclusion list.
Carloton wrote: However, to clarify, I assume that you meant Volume C and C:\Users?
I am not entirely convinced that path exclusion works even if you select an entire volume as a source. Have you personally tested this and confirmed this fact using the currently available version of Veeam Backup and Replication with Veeam Agent for Windows? I am not 100% sure but I am somewhat certain that we tested path exclusions with the entire volume selected and the exclusions still failed to work (just like file masks).
Now that you have confirmed that including the entire drive letter in a file level backup makes it so that 'Exclude Masks' are ignored, what is the plan to resolve this issue? Is this going to be fixed in a future release of the product? If so, what sort of timeframe are we looking at for that fix?
Yes file path exclusion was tested by our QC team. Please let me how it goes in your environment.
jonom wrote:This sounds almost like the problem I ran into a year or so ago except I was trying to do Volume level backups with exclusions.
I was told the following by support on how to get it working correctly (it is rather counter-intuitive):
To create Volume level backups with directory exclusions and/or file masks select File level backup.
In the Files section select the volumes you want to backup. When you select a volume here the description to the right should change to > volume level backup instead of > file level backup.
Now deselect the folders you want excluded and/or apply exclusions via the Advanced button. The description to the right of the volumes should stay as > volume level backup.
I can confirm the opposite. I just setup a test file level backup, targeting the E:\ drive of a system. Then, under exclude masks I stipulated E:\WindowsImageBackup. After taking the backup and browsing through the backed up files, the directory E:\WindowsImageBackup was still included. How is your QC team testing this that is different from what I am doing?
Users browsing this forum: No registered users and 1 guest