Hi David,
thanks for the feedback. No, files are backed up just once after tiering.
this is what I'm observing:
- I activated the azure file sync without tiering on a directory that is also backed up via Veeam B&R NAS. That worked as expected w/o side effects on the backup side
- once the first sync to azure was finished I activated a date based tiering leaving only on the last two years of files on the windows server
- when I activated tiering, on the subsequent backup 3.5 TB where processed / 3.1 TB read and 2.5 TB transferred. Those 2.5 TB were effectively added to the backup repository. Before tiering the usual pattern was 3.5 TB processed / 3 GB read and / 3 GB transferred. The files weren't actually recalled, in that the integration works, files are passed directly to Veeam B&R.
- on subsequent backups the situation in went back to the pattern I was seeing before the tiering was activated.
Two are the main problems on the recall/transfer of tiered files:
- azure egress fees
- backup repository space consumption, in this case Wasabi, because the same file is now stored twice even if the content is the same
I guess that Veeam B&R NAS treats the stub file as a different/new file and performs a new backup of the file. A complete integration should be aware that the file is the same (same modified date, same file size) and skip it.
thanks for the feedback. No, files are backed up just once after tiering.
this is what I'm observing:
- I activated the azure file sync without tiering on a directory that is also backed up via Veeam B&R NAS. That worked as expected w/o side effects on the backup side
- once the first sync to azure was finished I activated a date based tiering leaving only on the last two years of files on the windows server
- when I activated tiering, on the subsequent backup 3.5 TB where processed / 3.1 TB read and 2.5 TB transferred. Those 2.5 TB were effectively added to the backup repository. Before tiering the usual pattern was 3.5 TB processed / 3 GB read and / 3 GB transferred. The files weren't actually recalled, in that the integration works, files are passed directly to Veeam B&R.
- on subsequent backups the situation in went back to the pattern I was seeing before the tiering was activated.
Two are the main problems on the recall/transfer of tiered files:
- azure egress fees
- backup repository space consumption, in this case Wasabi, because the same file is now stored twice even if the content is the same
I guess that Veeam B&R NAS treats the stub file as a different/new file and performs a new backup of the file. A complete integration should be aware that the file is the same (same modified date, same file size) and skip it.
Statistics: Posted by cristiano.cumer — Jul 17, 2025 3:10 pm
