Hello Community,

I am facing the following problem.

We are using an archiving (HSM) solution where the archiving application uses the NetApp Fpolicy Engine for mirgation. After migrating files off a NetApp smb share to s3 storage, the NetApp fpolicy engine leaves a stub at the original location. This "stub" is used to recall the file back to the original location when it is accessed. These stubs cause problems when backing up through veeam. During Nas backup (Share and using the NetApp storage integration) the stubs are not backed up, it causes a recall from the archive. (This is not what you want). 

On a Windows Fileserver veeam handles these stubs well. These stubs are called NTFS Reparse points. The stub file has the L (Reparse) and O (Offline) attribute set. When doing a Windows Fileserver backup these reparse points are, by default, skipped. No setting needed. This is the correct way to handle stubs. I assume this is because of the "L" attribute of the reparse point. The NetApp Fpolicy stub is a sparse file that only has the SMB offline bit set (O). Not the (L) attribute. Is there a way to make Veeam filter/ skip files with the (O) offline attribute set? This is not possible through the filter option in the job settings. Here you only have the options filter files by mask and filter objects by path. Not based on file attribute.

I also have a case opened for this.

Hope someone in the community can point me in the right direction.

Regards,

Pieter van de Burg