Skip to main content

How can we help you?

Druva Documentation

File Servers restore pre-checks

Overview

Druva runs restore pre-checks for File-Level Restores. 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. 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.

File Servers restore pre-checks

Restore pre-checks Recommendations if the checks fail
Restore to the original server
Original Location
Agent version check  Upgrade agent to the latest version to run pre-checks. 
You can click Proceed to Restore to trigger the restore request or click Cancel to go back to the Restore target screen.
Target connection status check This error can occur if the Hybrid Workloads agent is disconnected from the Druva Cloud. Restart the agent and check for network connectivity. For more information, see PHOENIX17.
Custom Location
Agent version check  Upgrade agent to the latest version to run pre-checks. 
You can click Proceed to Restore to trigger the restore request or click Cancel to go back to the Restore target screen.
Target connection status check This error can occur if the Hybrid Workloads agent is disconnected from the Druva Cloud. Restart the agent and check for network connectivity. For more information, see PHOENIX17.
Write permission check  Fix the write permission issues corresponding to the below errors:
  • Invalid destination path. Provide the absolute destination path. For more information, see PHOENIX390.
  • Drive does not exist for a given input. For more information, see PHOENIX391.
  • Permission is not available at the restore destination. For more information see, PHOENIX392.
  • Environmental issues: <issue>. For more information, see PHOENIX393.
Restore to a different server
Agent version check  Upgrade agent to the latest version to run pre-checks. 
You can click Proceed to Restore to trigger the restore request or click Cancel to go back to the Restore target screen.

Target connection status check

This error can occur if the Hybrid Workloads agent is disconnected from the Druva Cloud. Restart the agent and check for network connectivity. For more information, see PHOENIX17.

Write permission check  Fix the write permission issues corresponding to the below errors:
  • Invalid destination path. Provide the absolute destination path. For more information, see PHOENIX390.
  • Drive does not exist for a given input. For more information, see PHOENIX391.
  • Permission is not available at the restore destination. For more information see, PHOENIX392.
  • Environmental issues: <issue>. For more information, see PHOENIX393.

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. For more information on File Servers restore, see Restore files and folders.