Skip to main content

How can we help you?

Druva Documentation

VMware restore pre-checks

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

 

Overview

Druva Phoenix runs a few checks before restoring a full VM or performing file-level restores (FLR). These checks look for issues that can cause your restore job to fail before the restore has even started. You must fix any identified issues before restoring your data.

Druva Phoenix runs restore pre-checks for Full VM restores and File-Level Restores. The following sections describe the restore pre-checks for each type of restore and remedial actions you must take in case of pre-check failures.

Full VM pre-restore checks

Restore pre-checks Recommendations if the checks fail
Restore to original location
Original VM does not exist

Restore to an alternate location

The original VM does not exist at the original location. Restore the full VM to an alternate location.

Original datastore does not exist

Restore to an alternate location

The original datastore does not exist at the original location. Restore the full VM to an alternate location.

Insufficient free disk space on the original datastore

Restore to an alternate location and select an alternate datastore

The original datastore is either low on free disk space or has no free disk space. Restore the full VM to an alternate datastore with sufficient free disk space at an alternate location.

Restore to alternate location
VM with the same name exists

Choose a different VM name

The specified alternate location already has a VM with the same name as the entered VM name. Enter a different VM name.

After fixing any identified issues, you can click rerun pre-checks to rerun the checks and initiate the restore once all checks have succeeded. Though you can skip the pre-checks and proceed with the restore, we recommend running the pre-checks and running the restore only after all checks have succeeded.

File Level Restore (FLR) pre-restore checks

Restore pre-checks Recommendations if the checks fail
Restore to virtual machine
Destination VM does not exist

Select another destination VM

The selected destination VM does not exist. Select another destination VM.

Destination VM is powered off

Power on the destination VM

The selected destination VM is powered off. Power on the destination VM. For more information, see Powering on an ESX/ESXi host's VMs.

Invalid destination VM credentials

Provide valid destination VM credentials

The credentials supplied for the destination VM are invalid. Enter valid credentials for the destination VM. 

Invalid location within the destination VM

Provide a valid location within the destination VM.

The entered location within the destination VM is invalid. Enter a valid location in the destination VM.

Credentials have insufficient privileges over the destination VM location

Provide a destination VM location over which the credentials have valid permissions

The credentials supplied for the destination VM do not have write permissions over the destination VM location. Enter a location over which the credentials have write permissions.

Restore to CIFS share  
Invalid UNC share details received

Enter correct share details

Either the entered UNC share path does not exist, or has been entered in an incorrect format. Enter the UNC share path in the format //IP/share_name or //Hostname/share_name.
UNC Share not Reachable

Enter reachable UNC share details

The specified UNC share could not be reached because of an incorrect or inaccessible IP address. Enter a UNC share that is reachable from vCenter.

UNC Share Invalid Credential

Enter valid credentials for UNC share details

You could run into this error during the following scenarios:

  • The entered credentials are invalid.
  • The share hasn't been shared, or the share has been shared, but the logged-in user does not have permissions over the share.
  • The share does not exist.
  • The share has been renamed and the renamed folder share has not been shared.

Ensure that the credentials are valid, the share exists, and has been shared and the logged-in user has permissions over the share

Credentials have insufficient privileges over the UNC Location

Provide a UNC location over which the credentials have valid permissions

The credentials supplied for the specified UNC share do not have read-write permissions over the UNC share location. Enter a location over which the credentials have read-write permissions.

After fixing any identified issues, you can click rerun pre-checks to rerun the checks and initiate the restore once all checks have succeeded. Though you can skip the pre-checks and proceed with the restore, we recommend running the pre-checks and running the restore only after all checks have succeeded.

  • Was this article helpful?