- Veeam Support Knowledge Base
- Hyper-V Backup Job fails after 72 hours "Failed to call RPC function 'HvSetVmBackupStatus'"
Hyper-V Backup Job fails after 72 hours "Failed to call RPC function 'HvSetVmBackupStatus'"
| KB ID: | 3134 |
| Product: | Veeam Backup & Replication |
| Version: | 9.x, 10.x |
| Published: | 2020-03-25 |
| Last Modified: | 2020-08-13 |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
Challenge
Failed to call RPC function 'HvSetVmBackupStatus': Snapshot with id '{snapshot-uuid}' was not found.
In the Task log for the specific VM ( %programdata%\Veeam\Backup\<jobname>\Task.<vmname>.<vm-uuid>.log ) the following error is found:
Error The device is not ready. (Veeam.Backup.Common.CCppComponentException)
Error Failed to read data from the file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\<foldername>\<vmname>\Virtual Hard Disks\<vmname>.vhdx]. (Veeam.Backup.Common.CCppComponentException)
In the Svc.VeeamHvIntegration.log log file found on the Veeam Backup & Replication server ( %programdata%\Veeam\Backup ) the following is found:
WARN|[GC] Removing expired snapshot. Creation time: '<date-stamp>'. JobInfo: 'Locked Job [<jobname>], Backup console [<veeamservername>]'. Is successful snapshot: 'true'. Is completed: 'true'. Life time: '72' hour.
Cause
This limit is intended to prevent issues with performance due to a VM running on a shadow copy for extended periods of time.
Solution
If it is not possible to improve performance, the 'snapshot life time' limit is adjustable with a registry entry on the Veeam Backup & Replication server:
(The Veeam Backup Service on the Veeam Backup & Replication server must be restarted after the key is modified to take immediate effect)
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\
Type: DWORD
Name: hvSnapshotLifeTimeHour
Value (Default): 72
The value may be doubled or set to a value which is sufficient to allow the VM to complete being backed up.
It is inadvisable to set the value any higher than 240 unless absolutely necessary, and should never exceed 596. In most cases a value of 144 (double default) works well.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.