VDP 5.5 Emergency Restore: Could not create restore task

[SayNo2HyperV]

Trying to recover a VM via VDP 5.5 Emergency Restore

Disassociated ESXi from vcenter.  Can connect to ESXi by either DNS or IP.  Selecting datastore with enough disk space.  Using a unique VM name.

Upon creating the restore task I receive:

Restore failed:

Server could not create a restore task at this time.

As configuration changes may take a few minutes to become effective, please try again at a later time.

Hunting around for cause of this issue or which log file contains further information on the problem.

The VDP admin guide has poor documentation on what log file pertains to what or much regarding this new emergency restore feature.

Also.  Is there any documentation on available CLI commands to run on the appliance to find active tasks and such.

Help would be appreciated.  Thanks!

[Incosolutions · Accepted solution]

Hi,

You've already read it? vSphere Data Protection Direct-to-Host Emergency Restore | VMware vSphere Blog - VMware Blogs

[SayNo2HyperV]

Thank you.  I had.  But revisiting, it did get me to realize a DNS inconsistency in my test environment.  The hostname on ESXi 5.5 was "ESXi" however my domain controller had "ESX".  When attempting the restore I used the DNS name registered in the domain so it connected, but it was not the true name used by ESXi thus job failed.  Updated the DNS on my DC and restore job submitted just fine.

Learning about VDP.  Is there a document regarding VDP 5.5 logs and what they relate to? Or common CLI commands?