Injecting guest runtime componants

[djmc]

Hi,
Does anyone know if there is a way to force a backup job to inject guest runtime components via VIX first, instead of attempting all the other options?

What are the benefits of using the other option over VIX?

Thanks in advance,
Declan

[david.domask]

Hi Declan,

Sure, you can use the following registry value:

Code: Select all

Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: InverseVssProtocolOrder
Value Type: DWORD (32-Bit) Value
Value Data: 1

0 = Try RPC (admin$ share) first, then failover to VIX. (Default behavior)
1 = Try VIX first, then failover to RPC (admin$ share)

This is documented in this KB article, but it's fairly normal to want to save time/logging by just using the VMware Web Services first (VIX).

RPC vs VIX connection is largely best decided depending on which is most convenient for your environment. VIX goes through the vCenter, so depending on the load/health of the vCenter/vcsa, you may see some slowness or reconnects required, but it shouldn't impact overall unless the vCenter really cannot handle the load/incoming connections. Keep in mind, you will want to follow our guidance on VCSA/vCenter backups and not do snapshot-based backups; backups/snapshots on the vcsa introduces a lot of potential for interruptions to backup/restore operations, and it's best to just follow VMware's guidance and use the native vcsa backup utility and protect that backup with Veeam.

[djmc]

Hi David,
Thanks for getting back to so quickly, its much appreciated.

I'll give the above suggestion a go and see if that improves things much.

Thanks again,
Declan