-
- Expert
- Posts: 121
- Liked: 24 times
- Joined: Sep 30, 2018 9:03 pm
- Contact:
FilesNotToSnapshot - not exlcuding files
hello and thanks,
this is a general question, if i must open a ticket please let me know.
to exclude files, i have been using the registry entry FilesNotToSnapshot and so far has been working.
today, i found that for a given folder, veeam agent included 10.0GB of files that should have been excluded.
i was trying to compile chromium and it creates approx 50,000s of files, many with just a file name without an extension.
i think the issue is the difference between * and *.*
microsoft website examples are *.*.
veeam website examples are * as per https://www.veeam.com/kb3236
i just want to exclude each and every file.
so which way is correct?
c:\ex\* /s
or
c:\ex\*.* /s
or
do i need two rules for every folder.?
thanks so much,
david
this is a general question, if i must open a ticket please let me know.
to exclude files, i have been using the registry entry FilesNotToSnapshot and so far has been working.
today, i found that for a given folder, veeam agent included 10.0GB of files that should have been excluded.
i was trying to compile chromium and it creates approx 50,000s of files, many with just a file name without an extension.
i think the issue is the difference between * and *.*
microsoft website examples are *.*.
veeam website examples are * as per https://www.veeam.com/kb3236
i just want to exclude each and every file.
so which way is correct?
c:\ex\* /s
or
c:\ex\*.* /s
or
do i need two rules for every folder.?
thanks so much,
david
-
- Product Manager
- Posts: 2579
- Liked: 708 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: FilesNotToSnapshot - not exlcuding files
Hi David.
One rule with Microsoft format will be enough(aka path\*.* /s).
Microsoft KB has a "Note" section on top, and last point of it says "Files are deleted from a shadow copy on a best-effort basis. This means that they are not guaranteed to be deleted." which could be the reason why you see Veeam backing up files that are not supposed to.
/Cheers!
One rule with Microsoft format will be enough(aka path\*.* /s).
Microsoft KB has a "Note" section on top, and last point of it says "Files are deleted from a shadow copy on a best-effort basis. This means that they are not guaranteed to be deleted." which could be the reason why you see Veeam backing up files that are not supposed to.
/Cheers!
-
- Expert
- Posts: 121
- Liked: 24 times
- Joined: Sep 30, 2018 9:03 pm
- Contact:
Re: FilesNotToSnapshot - not exlcuding files
thanks for the reply
for an incremental backup, how can i get a list all files that were backed-up?
that would confirm my findings below.
you wrote "One rule with Microsoft format will be enough(aka path\*.* /s)"
i could be wrong, but that advice might not be correct
i am using vbar.11 to control a win.10.21h1 computer running vagent.5 using a entire computer backup option.
i created a test and the results are
using `path\*.* /s` will fail to exclude all files.
using `path\* /s` will succeed to exclude all files in a folder except as noted below.
note: if a file has read-only attribute set, veeam will never exclude that file.
not sure if this is a bug with vss, veeam or what?
i did report this to the forum in the past, but never got a response as i think this should be documented on veeam support website.
so i created the following, ran an incremental backup, did a file restore to view the files and compared the source and the veeam restore point
2 rules in FilesNotToSnapshot
C:\test-single\* /s
C:\test-double\*.* /s
2 folders
C:\test-single\
C:\test-double\
15 files per folder
.ext
file
file.ext
.archive
archive
archive.archive
.readonly
readonly
readonly.readonly
.system
system
system.system
.hidden
hidden
hidden.hidden
for these files, no file attribute was set
.ext
file
file.ext
for these files, the archive attribute was set
.archive
archive
archive.archive
for these files, the readonly attribute was set
.readonly
readonly
readonly.readonly
for these files, the system attribute was set
.system
system
system.system
for these files, the hidden attribute was set
.hidden
hidden
hidden.hidden
for the veeam restore point, here were the files that were backed-up.
C:\VeeamFLR\en07.local\Volume0\test-single using FilesNotToSnapshot rule C:\test-single\* /s
.readonly
readonly
readonly.readonly
C:\VeeamFLR\en07.local\Volume0\test-double using using FilesNotToSnapshot rule C:\test-double\*.* /s
.readonly
arc
file
hidden
readonly
readonly.readonly
system
for an incremental backup, how can i get a list all files that were backed-up?
that would confirm my findings below.
you wrote "One rule with Microsoft format will be enough(aka path\*.* /s)"
i could be wrong, but that advice might not be correct
i am using vbar.11 to control a win.10.21h1 computer running vagent.5 using a entire computer backup option.
i created a test and the results are
using `path\*.* /s` will fail to exclude all files.
using `path\* /s` will succeed to exclude all files in a folder except as noted below.
note: if a file has read-only attribute set, veeam will never exclude that file.
not sure if this is a bug with vss, veeam or what?
i did report this to the forum in the past, but never got a response as i think this should be documented on veeam support website.
so i created the following, ran an incremental backup, did a file restore to view the files and compared the source and the veeam restore point
2 rules in FilesNotToSnapshot
C:\test-single\* /s
C:\test-double\*.* /s
2 folders
C:\test-single\
C:\test-double\
15 files per folder
.ext
file
file.ext
.archive
archive
archive.archive
.readonly
readonly
readonly.readonly
.system
system
system.system
.hidden
hidden
hidden.hidden
for these files, no file attribute was set
.ext
file
file.ext
for these files, the archive attribute was set
.archive
archive
archive.archive
for these files, the readonly attribute was set
.readonly
readonly
readonly.readonly
for these files, the system attribute was set
.system
system
system.system
for these files, the hidden attribute was set
.hidden
hidden
hidden.hidden
for the veeam restore point, here were the files that were backed-up.
C:\VeeamFLR\en07.local\Volume0\test-single using FilesNotToSnapshot rule C:\test-single\* /s
.readonly
readonly
readonly.readonly
C:\VeeamFLR\en07.local\Volume0\test-double using using FilesNotToSnapshot rule C:\test-double\*.* /s
.readonly
arc
file
hidden
readonly
readonly.readonly
system
-
- Product Manager
- Posts: 2579
- Liked: 708 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: FilesNotToSnapshot - not exlcuding files
Results do look valid to me.
* means all files(no matter of naming format), *.* means all files with extensions (more strict filter) and VSS skipped read-only files on both cases.
Case 1 leaves with all files removed from snapshot(even those without extension, aside read-only ones), Case 2 leaves with all files with extension being removed from snapshot as filter was strictly set on *.*
So if you want to exclude files without extensions, "*" filter would be more appropriate.
* means all files(no matter of naming format), *.* means all files with extensions (more strict filter) and VSS skipped read-only files on both cases.
Case 1 leaves with all files removed from snapshot(even those without extension, aside read-only ones), Case 2 leaves with all files with extension being removed from snapshot as filter was strictly set on *.*
So if you want to exclude files without extensions, "*" filter would be more appropriate.
-
- Expert
- Posts: 121
- Liked: 24 times
- Joined: Sep 30, 2018 9:03 pm
- Contact:
Re: FilesNotToSnapshot - not exlcuding files
thanks for taking the time to read my long detailed post
yes we agree that *.* means all files with extensions (more strict filter)".
tho you wrote that "One rule with Microsoft format will be enough(aka path\*.* /s)
your advice conflicts with the veeam documentation example that use path\* /s, not path\*.* /s
for other forum users, i wanted to point out those facts, as i could not find them documented on the veeam support site.
do you know why VSS skips read-only files?
thanks much
yes we agree that *.* means all files with extensions (more strict filter)".
tho you wrote that "One rule with Microsoft format will be enough(aka path\*.* /s)
your advice conflicts with the veeam documentation example that use path\* /s, not path\*.* /s
for other forum users, i wanted to point out those facts, as i could not find them documented on the veeam support site.
do you know why VSS skips read-only files?
thanks much
-
- Expert
- Posts: 121
- Liked: 24 times
- Joined: Sep 30, 2018 9:03 pm
- Contact:
Re: FilesNotToSnapshot - not exlcuding files
please, how can i get a list of files included in an incremental backup.
thanks,
thanks,
-
- Product Manager
- Posts: 2579
- Liked: 708 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: FilesNotToSnapshot - not exlcuding files
There is no native listing, however you can easily get the list of files and folders in the backup by mounting backup for File Level Restore and running:
CMD from C:\VeeamFLR\XXXXXXX <- where your backup will be mounted to
CMD from C:\VeeamFLR\XXXXXXX <- where your backup will be mounted to
Code: Select all
dir /s /b /o:gn >C:\Temp\FilesInBackup.txt
Who is online
Users browsing this forum: vtsybin and 38 guests