Loading...
Loading...
Instant VM recovery of a VMware VM fails after at least 30 minutes with the error: Failed to publish VM
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, mainly due to deduplication storage "rehydrating" deduped/compressed backup data. Slow network link between host and vPower NFS server due to congestion, setting of 100Mb/s on NIC, or other infrastructure issues. Poor performance of the vPower NFS server.
Increase Timeouts Increase the timeouts below to several times the default value. Although you can increase the timeouts beyond these limits, it is usually better to investigate performance first if you are performing a test or low-priority restore. In an emergency, increase the timeouts as high as necessary, or create a Severity 1 case with Veeam Support for assistance in finding a workaround. All values are created on the Veeam Backup Server. Some may not exist already and must be created. All values are in decimal. Make sure no jobs, restores, or other tasks are running, then restart the Veeam Backup Service to apply these changes. RemotingTimeout Controls general timeout between all services. Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and ReplicationValue Name: RemotingTimeoutValue Type: DWORD (32-Bit) ValueValue Data Default: 900 (seconds)Value Data Suggested: 7200
User Guide: Overview of vPower NFS Service Configuring vPower server The remotingTimeout setting affects all processes and services communicating with the Veeam Backup Service. Communication failures will sometimes be retried, so an operation may not fail until this timeout has occurred multiple times. Consider that, from a networking and vSphere configuration perspective, there is little difference between vPower and any other NFS datastore. VMware Technical Paper: Best Practices for Running vSphere on NFS Storage
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.