Loading...
Loading...
Protecting a new virtual machine and trying to deploy a new copy virtual machine at Target side vCenter. When Protecting a new virtual machine, RecoverPoint is unable to create a copy virtual machine and the Consistency Group remains in a Disabled state. The error viewed on Target vCenter when trying to deploy the OVF template is shown as below: "This operation is not allowed in the current state of the datastore" 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 virtual machine on target vCenter, it fails due to Datastore state checks.
Free some space on the Target Datastore to allow the deployment of new virtual machines at target vCenter.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.