Best Practice for NetApp CIFS share backup

[myRCvmforum]

Hi,

We have a NetApp FAS2700 that has a CIFS share. This CIFS is also snapmirrrored to a secondary NetApp FAS2700 at another building within the same campus but the CIFS copy is disabled/not active. Both NetApp is configured such that if the primary FAS2700 goes down, the CIFS share can be "switched over" quickly to the secondary NetApp FAS2700 using the same IP address (so we don't have to change anything on the client side).

My question is: what's the best way to backup the CIFS share? Should I configure the backup job to use the NAS Filer option or the File Share option? My concern/confusion is that if I configure the job as NAS Filer and select the primary NetApp, then the CIFS share, if it goes down and we switch to the secondary NetApp, the job will fail because it can't access the primary NetApp anymore. If I go the File Share option, I can add the IP address of the SVM + CIFS share (e.g. \\192.168.1.1\share) and the job will continue to work even if the primary NetApp is gone as the secondary NetApp will take over the SVM IP of 192.168.1.1. However, I am not sure if Veeam can still use the snapshots to do the back up in this mode (because now it's accessing the CIFS share not the filer)?

[ybarrap2003]

Hi @myRCvmforum, I would recommend using the NAS filer option so you do not have to manually add all the shares. In your case it is a unique situation and you would probably have to use the ip address share name. It there a reason you are not using DNS? Since you are currently performing a snapmirror to the other cluster. The only way to backup the share is by doing a SnapMirror DR test (https://docs.netapp.com/us-en/ontap/dat ... est-volume). This is a NetApp procedure. Once the primary is done we do not backup from the secondary. You can also mount a Veeam NAS share instant file share recovery if this is a temporary outage. I would recommend doing some DR testing to make sure it works.