Enterprise Workloads Editions: ✅ Business | ✅ Enterprise | ✅ Elite
Overview
Druva 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 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. |
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 |
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:
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. |
Staging VM pre-restore checks
Restore pre-checks | Recommendations if the checks fail |
Destination VM does not exist | Select another destination VM
The selected staging VM does not exist. Select another staging VM. |
Destination VM is powered off | Power on the destination VM
The staging VM is powered off. Power on the selected staging VM. |
Invalid destination VM credentials | Provide valid staging VM credentials
The credentials provided for the staging VM are invalid. Enter valid credentials for the staging VM. |
VM tools not installed | Install VMware tools
VMware tools are not installed. Install VMware tools on the selected staging VM. |
VM tools not running | Ensure that VMware tools are running
VMware tools are not running on the selected staging VM. Make sure they are running. |
Disk UUID in Advanced VM Configuration settings is either disabled or does not exist | Create or enable Disk UUID
Create or enable disk UUID in Advanced VM Configuration settings for the selected staging VM. For more information, see https://kb.vmware.com/s/article/52815. |
Check if the IP address assigned for the selected staging VM is reachable | Check the IP address
Valid IP address is not assigned to the staging VM. Check if the IP address assigned for the selected staging VM is reachable. |
Staging VM is already in use | Select another staging VM
Release the staging VM
|
Sandbox Recovery pre-restore checks
Restore pre-checks | Recommendations if the checks fail |
Delete malicious files operation is not allowed for proxy with version less than 6.3.1. | Upgrade proxy to version 6.3.2 or above to delete malicious files. |
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.