Fpolicy question regarding Fpolicy Stubs and Veeam integration

314ter

Hello All,

We are using an archiving (HSM) solution where the archiving application uses NetApp Fpolicy. After migrating files off a NetApp smb share to s3 storage, the 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. When using "flat" fileshare backup the stubs are not backed up, it causes a recall from the archive. (This is not what you want). There is no functionality in veeam to skip the stubs. When using the NetApp storage integration in Veeam. (eg. Snapshot). The stubs are then skipped on the basis of an access denied. (Skiping is what you want, not how it is done) The Fpolicy server rejects stub backup/ restore from a Snapshot. [SNAPSHOT_ACCESS_BLOCKED].

We tested this with Ontap release 9.12.1 P4 and 9.13.1 P4. Are there any best-practices to integrate Veeam with NetApp Fpolicy stub backup? NDMP is not an option as it is very basic within veeam.

Thanks in advance.

Pieter van de Burg

Tas

There should be an option in Veeam to skip links or symbolic links. However, the product is performing the way it should; the stub should be resolved, and the data retrieved from archive and backed up. If you skip the links, then you will never backup your archival data. BTW, which HSM are you using?

314ter

Hello Tas,

Thanks for the reply. Unfortunately veeam does not have the functionality to filter/ Skip symbolic links. In case of Fpolicy the stub is a sparse file that has the SMB offline bit set. Veeam is not able to filter/ skip that as well. During backup stubs should be skipped, not trigger a recall from the archive. You do not need/ want to backup archived content. Same with most of the virus scanners, they skip stubs, preventing unwanted recalls. NetApp Fpolicy is not at fault here. As you state NetApp Fpolicy is performing the way it should; when accessed, the stub is resolved, and the data retrieved from archive. Only if there was a way to skip that during a veeam backup 😁 The reason I came here, I was hoping someone encountered this already.

We are using Moonwalk, now Panzura Symphony as an HSM.