59510: Acronis Backup 12.5 Advanced: how to configure NetApp SAN storage

use Google Translate

Applies to: 

Last update: 30-08-2017

This article describes how to configure NetApp SAN storage connection in Acronis Backup 12 Advanced Beta.

(!) Important: the backed up VM should not be running on an existing VMware snapshot, or otherwise the backup from SAN snapshot performance may be severly degraded.

NetApp SAN storage configuration

Your NetApp SAN storage should meet these requirements:

  1. NetApp Data ONTAP version is 8.1, 8.2, 8.3 or 9.0+
  2. NetApp is running in cDOT mode. 7-mode mode is not supported.
  3. NetApp storage is connected to vSphere ESXi host as an NFS or iSCSI datastore.
  4. Access to NFS shares from Windows NFSv3 clients must be enabled on particular Storage Virtual Machine (SVM) on NetApp device via the following command as described in item #1 in NetApp Best Practices document:
    • vserver nfs modify -vserver [svm_name] -v3-ms-dos-client enable
  5. Snapshot directory is set to Visible:

Acronis Agent for VMware (Windows) machine configuration

You need to perform these steps on the machine where Acronis Agent for VMware (Windows) is or will be installed.

NFS Client role configuration

Windows NFS Client role must be enabled on the machine which has Acronis Backup Agent for VMware (Windows) installed.

NFS client installation

How to install NFS client on Windows Server 2008R2:

How to install NFS client on Windows Server 2012:

Configuration of AnonymousUID and AnonymousGID

  1. On the machine where Acronis Agent for VMware (Windows) is installed, open Windows Registry: Start -> Search -> type regedit.exe and press Enter.
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default
  3. Create a new DWORD named AnonymousUID and set its value to 0.
  4. Create a new DWORD named AnonymousGID and set its value to 0.
  5. Reboot the machine.

For detailed information, please refer to NFS Best Practice and Implementation Guide.


After configuring NFS client, reboot the machine.

Without reboot, backup from SAN snapshot fails with the error "You do not have access rights to this file".

iSCSI initiator configuration

1. Microsoft iSCSI Initiator is installed natively on Windows Server 2012, Windows Server 2008 R2, and Windows Server 2008. On these operating systems, no installation steps are required. For details, see this article.

2. In some systems, Microsoft iSCSI  Initiator Service may be disabled. Set the Startup type to Automatic or Manual.

3. The iSCSI LUN where the ESXi host datastore is located is connected to machine with Acronis Backup Agent for VMware (Windows) installed. See the example from the following topic in Acronis Backup 12 documentation.

4. In the iSCSI LUN settings, disable Space Reservation:

Otherwise, snapshot creation fails with "Operation with partition terminated. Failed to invoke NatApp API method 'clone-create'. Error code: 22. Error reason: Clone operation failed to start: Volume is full or Volume crosed autodelte threshold."

Acronis Backup 12 Advanced configuration

Backup target configuration

  1. Note the hostname or IP address of the storage, which you can check in VMware vSphere Web Client:
  2. In Acronis management console, navigate to Settings -> SAN storage.
  3. Click Add NetApp Storage.
  4. Specify details of your SAN storage and define which Agent for VMware (Windows) will be given direct access to this storage:

You can specify either an existing user, or a new one. To create a new user, open NetApp OnCommand System Manager, navigate to Configuration -> Security -> Users and create a new user.

Note (!) that the specified user must be a local administrator on corresponding NetApp Storage Virtual Machine (SVM) rather than entire NetApp system management administrator.

VM binding configuration

Make sure the protected VM is backed up by proper Agent for VMware which is configured to work with NetApp storage.

  1. In Acronis management console, select the VM in the Devices list.
  2. Go to the Overview tab.
  3. Check the VM Binding section.