Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1008

February 25th, 2015 10:00

Exception. Failed getting possible datastores .

Hi all,

trying vRPA in my lab and getting an error  "Exception. Failed getting possible datastores ." at step 11.2 of the installer wizard. The datastores attached to hosts are iSCSI LUNs off HP StoreVirtual VSA (P4000). Any help to where I should start looking for clues?

Thanks!

675 Posts

February 26th, 2015 09:00

Just to keep this forum updated on what was the issue in this case.

A single RP4VM cluster can connect to multiple vCenters (up to two vCenters per RP4VM cluster in this 4.2 release). That being said, the vCenter configured during installation must be the vCenter in which the vRPAs are deployed on. If there’s a need to add a 2nd vCenter, this can be done post-installation. In the issue described in this thread, the vRPAs were deployed on a different vCenter then the one configured in Deployment Manager.

Also, when there’s a need to separate the vRPAs load from production VMs load, the vRPAs can be placed on separate ESX cluster on the same vCenter. The only requirement is that ESX housing VMs to be protected has to have connectivity (same or routable subnet) towards the vRPAs.

This would be better clarified in the next documentation revision.

Hope that helps,

Idan

675 Posts

February 25th, 2015 10:00

I would recommend starting with making sure that provided vCenter Credentials entered in Deployment Manager have admin privileges. Also make sure that those datastores are shared across all ESXs in the ESX cluster housing the vRPAs (assuming this isn't installed on a single ESX).

Let me know if that's helpful or you're still getting that error.

Regards,

Idan

8 Posts

February 25th, 2015 11:00

Thank you for reply, Idan.

I'm using domain admin credentials for the vCenter access, I'm able to log in with the same credentials using vCenter client without any issues. The datastores are shared to all nodes in the cluster (only two ESXi hosts there now).

from dm.log:

2015-02-25 11:21:50,687 [ModalContext] (BaseInstallationServerAdapter.java:336) ERROR - Transaction failed. transactionId=75, timeoutInSeconds=120, errorMSG=Exception. Failed getting possible datastores ., errorType=EXCEPTION, value=null

2015-02-25 11:21:50,688 [ModalContext] (BaseDMCommand.java:150) ERROR - GetPossibleDatastoresCommand FAILED

com.emc.dm.exception.InstallationCommExceptionWithUserMSG: Exception. Failed getting possible datastores .

    at com.emc.dm.clients.BaseInstallationServerAdapter.getResultFromTransaction(BaseInstallationServerAdapter.java:337)

    at com.emc.dm.clients.BaseInstallationServerAdapter.getTransactionResult(BaseInstallationServerAdapter.java:280)

    at com.emc.dm.clients.BaseInstallationServerAdapter.getTransactionResult(BaseInstallationServerAdapter.java:213)

    at com.emc.dm.clients.InstallationServerClientImpl.getPossibleDatastores(InstallationServerClientImpl.java:1144)

    at com.emc.dm.commands.concrete.getter.vm.GetPossibleDatastoresCommand.inner(GetPossibleDatastoresCommand.java:44)

    at com.emc.dm.commands.infra.BaseDMCommand.execute(BaseDMCommand.java:39)

    at com.emc.dm.logic.DMLogic.getPossibleDatastores(DMLogic.java:609)

    at com.emc.recoverpoint.deploy.rpi.wizard.SelectDataStorePage$3.run(SelectDataStorePage.java:114)

    at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

2015-02-25 11:21:50,689 [ModalContext] (BaseDMCommand.java:235) DEBUG - Command GetPossibleDatastoresCommand FINISHED with returnValue=[ReturnValue [_isSuccess=false, _message=Exception. Failed getting possible datastores ., _data=null, _throwable=com.emc.dm.exception.InstallationCommExceptionWithUserMSG: Exception. Failed getting possible datastores ., _failureReason=UNKNOWN]]

Thanks again!

8 Posts

February 25th, 2015 18:00

Checked the vCenter logs, vRPAs were able to successfully log in. Pulled the logs from vRPA. The error is: "Failed finding one of the VMs in the VC"...

I had a single VM running in this cluster. Removed it from the inventory so there are no VMs in this cluster at all, re-run the datastore discovery - same error.

2015-02-26 01:54:31,211 [CommandWorker-32] (BaseAction.java:46) ERROR - GetPossibleDatastoresAction Failed.

ActionFailedException(super=com.emc.recoverpoint.connectors.actions.infra.ActionFailedException: Failed finding one of the VMs in the VC: 4237ddbb-9bdf-2e42-be3f-e327632e1230)

Any help figuring out what's going on? Thanks!

./files/home/kos/installationLogs/server.log:

2015-02-26 00:23:11,203 [CommandWorker-32] (BaseAction.java:81) DEBUG - Action started: GetPossibleDatastoresAction BaseAction(vsphereConnection=VsphereConnection(serviceInstance=ServiceInstance:ServiceInstance @ https://10.10.0.5:443/sdk, vcUuid=VcUuid(super=Uuid(uuid=DFA89144-C6CD-474F-80B1-A063143CC662))), uuid=null)

2015-02-26 00:23:11,238 [CommandWorker-32] (BaseAction.java:46) ERROR - GetPossibleDatastoresAction Failed.

ActionFailedException(super=com.emc.recoverpoint.connectors.actions.infra.ActionFailedException: Failed finding one of the VMs in the VC: 4237ddbb-9bdf-2e42-be3f-e327632e1230)

        at com.emc.recoverpoint.connectors.actions.infra.ActionFailedException.createException(ActionFailedException.java:27)

        at com.emc.recoverpoint.connectors.actions.get.GetPossibleDatastoresAction.getPotentialVrpaHost(GetPossibleDatastoresAction.java:77)

        at com.emc.recoverpoint.connectors.actions.get.GetPossibleDatastoresAction.perform(GetPossibleDatastoresAction.java:42)

        at com.emc.recoverpoint.connectors.actions.get.GetPossibleDatastoresAction.perform(GetPossibleDatastoresAction.java:27)

        at com.emc.recoverpoint.connectors.actions.infra.BaseAction.call(BaseAction.java:34)

        at com.kashya.installation.server.commands.vsphere.GetPossibleDatastoresCommand.execute(GetPossibleDatastoresCommand.java:36)

        at com.kashya.installation.server.commands.vsphere.GetPossibleDatastoresCommand.execute(GetPossibleDatastoresCommand.java:24)

        at com.kashya.installation.server.commands.Command.runNormal(Command.java:100)

        at com.kashya.installation.server.commands.Command.run(Command.java:45)

        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

        at java.util.concurrent.FutureTask.run(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

        at com.kashya.installation.server.ThreadPoolFactory$1.run(ThreadPoolFactory.java:42)

        at java.lang.Thread.run(Unknown Source)

2015-02-26 00:23:11,238 [CommandWorker-32] (Command.java:79) ERROR - Command#run() ServerException errorType[EXCEPTION] errorMessage[Exception. Failed getting possible datastores .] failure UID: 38d21b79-28f8-44a8-9a73-114c1fc8e2b9

com.kashya.installation.server.exceptions.CommandFailedException: Exception. Failed getting possible datastores .

        at com.kashya.installation.server.commands.vsphere.GetPossibleDatastoresCommand.execute(GetPossibleDatastoresCommand.java:40)

        at com.kashya.installation.server.commands.vsphere.GetPossibleDatastoresCommand.execute(GetPossibleDatastoresCommand.java:24)

        at com.kashya.installation.server.commands.Command.runNormal(Command.java:100)

        at com.kashya.installation.server.commands.Command.run(Command.java:45)

        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

        at java.util.concurrent.FutureTask.run(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

        at com.kashya.installation.server.ThreadPoolFactory$1.run(ThreadPoolFactory.java:42)

        at java.lang.Thread.run(Unknown Source)

Caused by: ActionFailedException(super=com.emc.recoverpoint.connectors.actions.infra.ActionFailedException: Failed finding one of the VMs in the VC: 4237ddbb-9bdf-2e42-be3f-e327632e1230)

        at com.emc.recoverpoint.connectors.actions.infra.ActionFailedException.createException(ActionFailedException.java:27)

        at com.emc.recoverpoint.connectors.actions.get.GetPossibleDatastoresAction.getPotentialVrpaHost(GetPossibleDatastoresAction.java:77)

        at com.emc.recoverpoint.connectors.actions.get.GetPossibleDatastoresAction.perform(GetPossibleDatastoresAction.java:42)

        at com.emc.recoverpoint.connectors.actions.get.GetPossibleDatastoresAction.perform(GetPossibleDatastoresAction.java:27)

        at com.emc.recoverpoint.connectors.actions.infra.BaseAction.call(BaseAction.java:34)

        at com.kashya.installation.server.commands.vsphere.GetPossibleDatastoresCommand.execute(GetPossibleDatastoresCommand.java:36)

        ... 9 more

675 Posts

February 26th, 2015 04:00

Hi,

Can you confirm that the credentials you're using can indeed browse and write to all datastores (permissions may of changed on a DS level). This is just to rule out any privileges issues.

If all DSs are accessible and writable with the user you are using, please contact me offline (email written below) in order to continue troubleshooting this, we will need logs from RP in addition to the DM logs you've already provided.

Regards,

Idan

idan.kentor@emc.com

675 Posts

February 26th, 2015 05:00

Hi,

Please see my latest reply, this can be a permission issue.

If you have verified and it isn't, please let me know, I would need other logs besides installation server.

Regards,

Idan

No Events found!

Top