Loading...
Loading...
A SureBackup job displays the error: Error: Mount with leaseId 'xxx-xxx-xxx-xxx-xxx-xxx' already activated.
Surebackup will fail with this message if certain operations time out. Veeam Backup & Replication implements timeouts for most operations to protect against hangs. However, even when no process is hung, timeouts may occur due to significant performance problems or an unusual use case. Typically, this error occurs due to the slow performance of the vPower NFS datastore. Possible causes of the slow performance: Slow repository read performance, especially due to deduplication storage "rehydrating" deduped/compressed backup data. Slow network link between host and vPower server due to congestion, setting of 100Mb/s on a NIC, or other infrastructure issues. Poor performance of the vPower NFS server.
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\SureBackupValue Name: MountLeaseTimeOutValue Type: DWORD (32-Bit) ValueDefault Value Data(Dec): 600 The value is measured in seconds. remotingTimeout Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and ReplicationValue Name: remotingTimeoutValue Type: DWORD (32-Bit) ValueDefault Value Data(Dec): 900 The value is measured in seconds.
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.