SureBackup: Error: Mount with leaseId already activated

Increase Timeouts

The timeouts can be configured by creating the following registry values on the Mount Server. Increase the timeouts to 2x or 3x their default value. Needing to increase the timeouts further may indicate that performance needs to be investigated instead.

MountLeaseTimeOut

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\SureBackup
Value Name: MountLeaseTimeOut
Value Type: DWORD (32-Bit) Value
Default Value Data(Dec): 600

The value is measured in seconds.

remotingTimeout

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Value Name: remotingTimeout
Value Type: DWORD (32-Bit) Value
Default Value Data(Dec): 900

The value is measured in seconds.

Improve Performance

Impact of Deduplicating Storage

The most common cause of this error is slow read performance from the backup repository. Which often correlates with the use of deduplicating storage as a back-end for Surebackup. If you must verify backups from deduplicating storage, increasing the above timeouts to several hours may be necessary, especially if there are any large (multi-TB) VM disks. Optimize storage devices for random read I/O of large blocks (typically 256 KB – 512KB with default settings or 4 MB for backups on deduplicating storage; your use case may vary). A simple benchmark is described in KB2014.

Performance of deduplicating appliances can also be improved by adding them as Deduplicating Appliance instead of via SMB (CIFS) or NFS.

Additional Performance Considerations

• If verifying offsite backups, ensure the virtual lab and vPower NFS server are on the same site as the repository.
• Depending on the underlying infrastructure, significant performance differences can exist between having the Mount Server assigned to a VM or from a physical machine. For example, try using a VM on the same ESXi host as the virtual lab.
• Heavily fragmented full backup files can reduce restore performance. Schedule compact operations to minimize fragmentation.
• Where applicable, test the throughput of the network connections between the repository and Mount Server and between the Mount Server and the ESXi host.
• Investigate CPU and memory usage of the repository and vPower servers.