Challenge
A job fails with an error message reporting an error “The RPC server is unavailable.” The following error can occur when using Application-Aware Image Processing:[timestamp] <01> Error VSSControl: IsSnapshotInProgress failed. Transaction logs will not be truncated.<…>
[timestamp] <01> Error RPC function call failed. Function name: [IsSnapshotInProgress]. Target machine: [xxx.xx.x.xx].
[timestamp] <01> Error RPC error:The RPC server is unavailable.
[timestamp] <01> Error Code: 1722
Cause
1. The ports that Veeam Backup & Replication is attempting to use are blocked by a firewall.2. The VeeamVSSSupport service is stuck on the Guest OS
3. Antivirus or Antimalware software may attempt to interact with the VeeamVSSSupport service executable.
In rarer cases dynamic port allocation needs to be configured.
Note: If the VM that is failing to be connected to is Windows Server 2003, you need to use the RPC Configuration Tool (RPCCfg.exe) from the Windows Server 2003 Resource Kit to complete the process that is described in this article.
Additional troubleshooting steps can be found in the following Microsoft KB article:
http://social.technet.microsoft.com/wiki/contents/articles/4494.windows-server-troubleshooting-the-rpc-server-is-unavailable.aspx
Solution
──────────────────────────────────────────────────────────Firewall / Ports
──────────────────────────────────────────────────────────
A full list of used ports can be found here: https://helpcenter.veeam.com/docs/backup/vsphere/used_ports.html?ver=95u4
When Veeam Backup & Replication connects to a VM it creates firewall exclusions for the ports and processes it uses. Veeam Backup & Replication however is not able to add firewall exclusions to hardware or third-party software firewalls.
The most common ports that cause this issue when using Application-Aware Image Processing are the Dynamic RPC ports that the temporary guest agents are assigned. These ports are:
•1025 to 5000 (for Microsoft Windows 2003)
•49152 to 65535 (for Microsoft Windows 2008 and newer)
Note: The NIC’s Network Location being set to Public mode will also cause this, as Public mode sets the firewall it’s strictest settings.
──────────────────────────────────────────────────────────
VeeamVSSSupport service cleanup
──────────────────────────────────────────────────────────
When no job is processing the VM connect to it and check the following things:
1. Make sure the VeeamVSSSupport service is no longer present.
•If it is, use the command ‘sc delete VeeamVSSSupport’ to remove the service.
2. Make sure the c:\Windows\VeeamVSSSupport folder is not present.
•If it is, delete the folder. If it fails to delete reboot or resolve the file lock.
──────────────────────────────────────────────────────────
Antivirus/Antimalware
──────────────────────────────────────────────────────────
Please review the full list of Antivirus/Antimalware exclusions listed here: http://www.veeam.com/kb1999
The most common solution is to exclude the C:\Windows\VeeamVSSSupport\ folder from being scanned.
──────────────────────────────────────────────────────────
Dynamic Port Configuration
──────────────────────────────────────────────────────────
To configure dynamic port allocation follow the steps outlined in the following Microsoft KB article.
These changes will need to be made on the server that Veeam Backup & Replication is having trouble connecting to.
http://support.microsoft.com/kb/154596