RecoverPoint for Virtual Machines – Unable to create copy VM

Article Number: 503056 Article Version: 3 Article Type: Break Fix



RecoverPoint for Virtual Machines

When Protecting a new VM we were unable to create copy VM and CG remains in Disabled state.

Error viewed on Target Vcenter when trying to deploy OVF template shown as below:

“This operation is not allowed in the current state of the datastore”

error screenshot:


Symptoms found in logs:

DR_RPA/files/home/kos/connectors/logs/connectors.log

2017-08-08 22:23:41,272 [pool-4-thread-1] (CreateNewVMAction.java:227) ERROR – Failed creating new vm: AMRNDHL1038.copy, error msg: The operation is not allowed in the current state of the datastore. (com.vmware.vim25.InvalidDatastoreState)

2017-08-08 22:23:41,281 [pool-4-thread-1] (BaseAction.java:34) ERROR – CreateNewVMAction Failed.

2017-08-08 22:23:41,283 [pool-4-thread-1] (BaseCommand.java:59) ERROR – Command failed: CreateNewVMCommand(ID:2015901748783485597) took: 2161

2017-08-08 22:23:42,236 [pool-5-thread-1] (CommandState.java:80) ERROR – Command Exception:

2017-08-08 22:23:42,523 [pool-6-thread-1] (CommandState.java:80) ERROR – Command Exception:

2017-08-08 22:24:17,283 [pool-4-thread-2] (CreateNewVMAction.java:227) ERROR – Failed creating new vm: AMRNDHL1038.copy,

When trying to deploy the copy VM on DR Vcenter it fails due to Datastore state checks.

Protecting new VM and trying to deploy new copy VM at Target side vCenter.

Free some space on the Target Datastore will allow the deployment of new VMs at target vCenter.

Related:

Leave a Reply