VMware export wizard will timeout getting metadata from a large environment (4044598)

Steps to reproduce: 

1. Protect an agent and take a snapshots
2. Start the export wizard to vCenter
3. Enter vCenter hostname and credentials
4. Select the VM configuration and finish the wizard to start the export.

Expected result: Export wizard completes and export start sending data.

Actual result: Export wizard will timeout

ERROR 2020-08-12T15:08:48 [279] - Replay.Core.Client.ExportSchedulerManagementCoreClient ()Timeout executing [POST https://localhost:8006/apprecovery/api/core/export/schedule/vsphere/info] after 01:00:00.0040335Microsoft.Http.HttpStageProcessingException depth 0: GetResponse timed out (0x80131501) ---> System.TimeoutException depth 1: GetResponse timed out (0x80131505) ---> System.Net.WebException depth 2 (0x80131509) ---> System.Net.WebException depth 3: The operation has timed out (0x80131509)

ERROR 2020-08-19T08:34:02 [334] - Replay.Common.Implementation.Virtualization.VSphereApi.PbmConnection (RequestUri=https://localhost:8006/apprecovery/api/core/export/schedule/esx/capabilities?agentId=&recoveryPointId=ClientAddress=127.0.0.1:53160 Service=Replay.Core.Management.Export.ExportSchedulerManagement Method=GetEsxCapabilities)Failed to obtain storage profiles for https:///pbm/. This could happen if a user lacks of required privileges System.Web.Services.Protocols.SoapException depth 0 (0x80131501)

The current logic performs a query to request a list of properties we need from vCenter to continue the export. One of this items is the list of VM's to compare and make sure we don't create a VM with the name of a already created VM.

Rapid Recovery will wait until it gets all this information from vCenter. A large vCenter environemnt (+20K VM's) can take a long time to provide this information and eventually the wizard will timeout. 

Solution#1: Export directly to an ESXi host instead of exporting to vCenter

Solution#2:  Increase the following Core timeout settings via registry editor

Note: You may need to increase it to one hour 01:00:00 or more depending on your environment.

Solution#3: Limit the account to only allow access to a certain amount of hosts

1. Create a VMware user with limited permissions to perform agentless backups with Rapid Recovery KB4043046
2. Give permissions to the user at a vCenter level
3. On the cluster/datacenter that Rapid Recovery will not perform backups, set user permissions to "No access"

4. Restart the RapidRecovery Core service following steps in KB4034348