SureBackup RPC Server is Unavailable [InvokerTestConnection]

[rreed]

Morning, all. We're getting our feet wet w/ SureBackup recently; have setup a couple test application groups (one a domain controller to test AD recovery, one just a basic web server), a virtual lab (use proxy appliance w/ available valid production IP that pings once the appliance is up, advanced single-host, valid network mapping, one NIC using production gateway as its IP per settings suggestion, no static mapping).

Try to fire of a test job, bombs out w/ the below error at Publishing the VM. My proxy/repository gateway is there and available, it's been running backups and its repositories just fine. Source VM is via backup.

Error: The RPC server is unavailable RPC function call failed. Function name: [InvokerTestConnection]. Target machine: [IP address of proxy/repository gateway here].

[PTide]

Hi,

Have you checked if RPC service ports are opened for vPower?

Thanks

[rreed]

Firewall is disabled on our proxies, if that applies. Do I need to do anything specific to our proxies/gateways in order for SureBackup to work? I can telnet to port 6160 but not 6161 on them, but we're not running vPower NFS (repositories are dedupe devices so no realistic expectations for VM's to run directly from backup). Oh wait, is that needed for SureBackup to work?

[widmerkarl]

Hi,

As far as i know yes. The VMs are registered on the specified Host but the disk file resides in the backup repository. Its nearly the same procedure as in InstantVM recovery, where you boot a VM directly from backup repository (via vPowerNFS) and later migrate this VM to production.

Also make sure that the ESXi host on which you plan to deploy the virtual lab has a VMkernel interface, otherwise the vPower NFS datastore will not mount.

https://helpcenter.veeam.com/backup/vsp ... begin.html

https://helpcenter.veeam.com/backup/vsp ... rvice.html

[PTide]

Oh wait, is that needed for SureBackup to work?

Karl is spot on, vPower NFS is required to publish VM disks from the backup file. So please make sure that you have vPower service running and that ports specified in "Microsoft Windows Server Running vPower NFS Service Connections" section are opened.

repositories are dedupe devices so no realistic expectations for VM's to run directly from backup

Unless the deduplication appliance offers a fast non-deduplicating landing zone for the latest restore points it's recommended to use fast storage.

Thanks

[rreed]

Yep, that got me going to the next error. Duh. Working w/ tweaking the timeouts now, 10 minutes might not be enough to boot from a dedupe device. Many thanks all!