VLSR - Unable to Configure Placeholder Datastore: Available Datastores List Will Not Populate

Products

• VMware Live Recovery

Issue/Introduction

When trying to configure a Placeholder Datastore but the datastore list never populates and you see the following error:

You see the following spinning animation until an eventual timeout:

You see the following error populate once the call eventually times-out:

ERROR
MoRefData: type = Folder, value = group-s4434, serverGuid = xxxxxxx is not part of the request.
Operation ID: xxxxxxxxx

 

Environment

VLSR 8.x
VLSR 9.x

vCenter 7.x
vCenter 8.x

Cause

Large number of datastores presented to the vCenter will cause a timeout if the query extends beyond 30 seconds.

VLSR needs to evaluate all datastores in the vCenter inventory that can be suitable to be configured as Placeholder datastores.

The scan will timeout if there is a large number of datastores it needs to scan.

 

From the SRM vmware-dr.log we see SRM call out from vCenter the 'query.SuiteableDatastoresForFolder' call :

2024-10-09T11:25:16.392-04:00 verbose vmware-dr[01157] [SRM@6876 sub=DrTask opID=xxxxxxxxx-querySuitableDatastoresForFolder] Task 'dr.PlaceholderDatastoreManager.querySuitableDatastoresForFolder3719' completed with result: (dr.PlaceholderDatastoreManager.SuitableDatastoreInfo) [
-->    (dr.PlaceholderDatastoreManager.SuitableDatastoreInfo)

 

From SRM dr.log we see this timeout error:

com.vmware.vim.vmomi.client.exception.ConnectionException: Unable to connect to vCenter Server at https://VC-FQDN:443/sdk. Reason: https://VC-FQDN:443/sdk invocation failed with "java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-2230
[ACTIVE]"

Resolution

On the SRM Appliance, edit the file: 

/opt/vmware/dr-client/lib/h5dr.properties

Increase the following values to higher value (in milliseconds) :

responseTimeout=120000
connectTimeout=120000
socketTimeout=120000

The above setting example was set to 120 seconds (2 minutes)

Whatever value is set above, the SRM appliance will wait to scan all available datastores and mark them suitable for Placeholder Datastore configuration

The idea here is to allow SRM appliance to populate the results before the timeouts above. Results will populate as soon as they are ready.