NetApp NAS Integration SVM vs. Cluster

[MatzeB]

Hi,

We often use NetApp systems as file servers and therefore the “NAS Filer” integration in Veeam.
There are two options for adding the NetApp storage system under Storage Infrastructure.
- The whole cluster - this makes sense if all workloads/SVMs on the NetApp system are relevant for Veeam.
- A single SVM (Storage Virtual Machine) - this makes sense if, for example, I have a very large NetApp system with e.g. 30 SVMs and only want to back up one or two SVMs, e.g. the NAS data with Veeam.

I usually recommend individual SVMs for security reasons (deleting snapshots) or because of the reduced “rescan scope” for Veeam. But there is a configuration overhead with dedicated mgmt ip, user etc.

However, it has already happened to me twice that we had added the entire NetApp cluster to Veeam and wanted to do so. However, the customer had several SVMs for file services in different domains.
If I now add the NAS filer in Veeam, I only have the entire cluster (DEMO5 in the example) to choose from and can only store one user account here. Actually, I would like to define the user account per SVM because these could be in different domains.
For me it looks more like a UI topic, because i can only choose the "top element" which is the cluster.

Can you please clarify this?



Regards
Matze

[Andreas Neufert]

It makes sense then to add individual SVMs or use a NetApp internal account that spans all SVMs with the file backup rights.

[MatzeB]

Yes right, in most cases i makes sense. But i think it would be really easy to reslove this with a adjusted UI.

When you create the NAS Backup job in a later step veeam "resolves/shows" all SVMs on the cluster. I think this could be easily done in this step before where you add a system as enterprise NAS. With separate SVMs at this level you could assign seperate user for backup.

Matze

[Dima P.]

Hi Matze,

Noted as a possible improvement for the next versions. Thank you for the feedback!