Skip to main content
Restore Nutanix AHV virtual machine data
Updated over a week ago

If you have taken a standard backup (non-application aware), you can restore:

  • Full virtual machine: Restores the entire virtual machine. For more information, see Restore full virtual machine.

  • Data Restore: Restores vDisks, files and folders. For more information, see Restore vDisks and Restore files and folders.

To know more about the restore workflow, see Nutanix AHV restore workflow.

Prerequisites

Restore files and folders

Druva provides you with the capability to restore files to CIFS/NFS.

The following ACL parameters are restored along with the files:

Source virtual machine

ACL parameters restored

File-level Restore to CIFS share

Windows virtual machine

  • File modification time

  • Last access time

Linux virtual machine

  • File modification time

  • Last access time

File-level Restore to NFS share

Windows virtual machine

  • File modification time

  • Last access time

Linux virtual machine (with no root squash)

  • File Modification time

  • Last access time

  • User id

  • Group id

  • File permission

Considerations

  • If the Hybrid Workloads agent restarts during the browse operation, the browse operation fails.

  • If the Hybrid Workloads agent restarts during the restore job, the job is retried.

  • The target restore location should have enough space to store the restored files.

Procedure

  1. Log in to the Management Console.

  2. Select your Organization if Organizations are enabled .

  3. On the menu bar, click Protect > Nutanix AHV.

  4. On the Prism page, click Prism and then select the VM whose files need to be restored. Alternatively, select the Prism Element or Prism Central from the Prism dropdown menu on the left.

  5. In the left pane, under the selected Prism Element or Prism Central, click Configured VMs.

  6. Select the VM that needs to be restored, and then click Restore.

    configured_vms.png
  7. In the Restore Type section, select Files & Folders.

  8. Click Files & Folders and select the file or folder you want to restore. File-level restore eliminates the need to perform time-consuming disk restores when you want to restore file(s) and folder(s).

  9. Click the dropdown next to the date and time stamp, and select the recovery point that you want to restore from. Click Browse Selected Recovery point, to browse the files and folders from the above selected recovery point.
    ​
    If the prism associated with the configured virtual machine is unavailable, you can select another prism as the location where your files and folders will be restored.

    If the alternate prism is unavailable, it will be automatically disabled once discovery fails.


    πŸ“ Note: If an alternate Prism is not already registered, ensure to register one to facilitate file-level restoration to an alternative location.



    πŸ“ Note
    ​ You view the actual volume names and drive letters when the volume is mounted. This helps you quickly identify and find the directory. If the Hybrid Workloads agent is unable to read the volume name or drive letter, it will assign a custom name to all such volumes, for example, volume1, volume2, and so on. For more information, see Support Matrix.


  10. Select the files and folders to be restored and click Restore.


    πŸ“ Note
    ​ A single click of expanding a particular folder will load a total of 1024 files/folders. If there are more than 1024 files/folders, then the Load More option will be visible to display the next set of results in that folder.


  11. On the File Restore page, you can choose one of the following restore targets.


    πŸ“ Note
    ​ Currently, restore is supported only to the UNC path. Therefore only CIFS and NFS shares are supported.


    file_restore.png
  • Restore to CIFS share: Restores the files and folders to a specific network share.
    ​

    • UNC Path:

      Valid UNC share (network share) path that is reachable from the selected Prism.

      Valid sharename format:

      • \\<hostname> or<Ip address>\<Sharename>

      • //<hostname> or<Ip address>/<Sharename>

    • Username:

      Valid username of UNC share.


      πŸ“ Note
      ​ You can specify domain name in the username of the UNC share in the "domain@username" or domain\username format.


    • Password: Valid password for UNC share.

    • Prism:

      From the drop-down list, select a Prism that has at least one Backup proxy in the connected state.


      πŸ“ Note
      ​ A Backup proxy pool with at least one Backup proxy with version 6.3.0-227659 or later is listed. If there are no proxies with version 6.3.0-227659 or later in the pool, then the pool is not listed for that Prism.


    • Backup Proxy Pool: From the drop-down list, select a Backup proxy pool. It is recommended that you select a Backup proxy pool with backup proxies that are locally connected to the destination hypervisor for restore.

    • If original file(s) exist

      • Always overwrite:

        The files with the same name will always be overwritten at the destination regardless of the file version or date. By default, this option is always selected.


        πŸ“ Note
        ​ During a file-level restore, if a file or folder is already present at the destination location and you select the overwrite option, the new file/folder is successfully restored. Also, the existing file/folder is not overwritten but renamed with the suffix .orig.


      • Always skip: The files with the same name will not be restored to the destination.

      • Overwrite if original is older:

        The files with the same name will be overwritten only if the existing file’s modification time is older.


        πŸ“ Note
        ​ During a file-level restore, if a file or folder is already present at the destination location and you select the overwrite option, the new file/folder is successfully restored. Also, the existing file/folder is not overwritten but renamed with the suffix .orig.


    • Restore and move original to .orig: If the file being restored already exists at the destination, the version being restored will be saved with the same filename. While the existing file will be renamed to filename.ext.orig.

    • Preserve original directory structure:

      You can preserve the entire source location directory structure, that is, tree path while restoring a file.

      The following are the examples of original directory structure when:

      • Preserve original directory structure option is checked:
        If you are restoring folder β€œD” from the source location Volume1/A/B/C/D to <UNC_path>, then
        The restored file structure will be <UNC_path>/Volume1/A/B/C/D.

      • Preserve original directory structure option is unchecked:
        If you are restoring folder β€œD” from the source location Volume1/A/B/C/D to <UNC_path>, then
        The restored file structure will be <UNC_path>/D.


      πŸ“ Note
      ​ Suppose you browse and select two files in different folders with the same names to restore. In that case, only one file with that name will be restored if the Preserve upward directory structure option in the Restore Target window is unchecked. Also, the following message is displayed that shows the files that are not restored.
      ​Files/folders/<volume_name>/<file_name> with the same name will not be restored.


  • Restore to NFS share: Restores the files and folders to a specific network share.


    πŸ“ Note
    ​ Make sure the Backup proxy is allowed to mount the NFS share.



    πŸ“ Note
    ​ The Backup proxy mounts the NFS share using the root user. By default, NFS shares change the root user to the nfsnobody user, an unprivileged user account. In this way, all root-created files are owned by nfsnobody. The nfsnobody user does not have sufficient privileges to change the file attributes, making restoring file attributes impossible. Therefore, if you want to restore the file attributes such as mtime, owner, permissions, and so on, then map the root user to an appropriate user on the target NFS share.


    • UNC Path:

      Valid UNC share (network share) path that is reachable from the selected Prism

      Valid sharename format:

      • \\<hostname> or<Ip address>\<Sharename>

      • //<hostname> or<Ip address>/<Sharename>

    • Prism:

      From the drop-down list, select a Prism that has at least one Backup proxy in the connected state.


      πŸ“ Note
      ​ A Backup proxy pool with at least one Backup proxy with version 6.3.0-227659 or later is listed. If there are no proxies with version 6.3.0-227659 or later in the pool, then the pool is not listed for that Prism.


    • Backup Proxy Pool:From the drop-down list, select a Backup proxy pool. It is recommended that you select a Backup proxy pool with backup proxies that are locally connected to the destination hypervisor for restore.
      ​

    • If original file(s) exist:

      • Always overwrite: The files with the same name will always be overwritten at the destination regardless of the file version or date. By default, this option is always selected.

      • Always skip: The files with the same name will not be restored to the destination.

      • Overwrite if original is older:

        The files with the same name will be overwritten only if the existing file’s modification time is older.


        πŸ“ Note
        ​ During a file-level restore, if a file or folder is already present at the destination location and you select the overwrite option, the new file/folder is successfully restored. Also, the existing file/folder is not overwritten but renamed with the suffix .orig.


    • Restore and move original to .orig: If the file being restored already exists at the destination, the version being restored will be saved with the same filename. While the existing file will be renamed to filename.ext.orig.

    • Preserve original directory structure:

      You can preserve the entire source location directory structure, that is, tree path while restoring a file.

      The following are the examples of original directory structure when:

      • Preserve original directory structure option is checked:
        If you are restoring folder β€œD” from the source location Volume1/A/B/C/D to <UNC_path>, then the restored file structure will be <UNC_path>/Volume1/A/B/C/D.

      • Preserve original directory structure option is unchecked:
        If you are restoring folder β€œD” from the source location Volume1/A/B/C/D to <UNC_path>, then the restored file structure will be <UNC_path>/D.
        ​


      πŸ“ Note
      ​ Suppose you browse and select two files in different folders with the same names to restore. In that case, only one file with that name will be restored if the Preserve upward directory structure option in the Restore Target window is unchecked. Also, the following message is displayed that shows the files that are not restored.
      ​Files/folders/<volume_name>/<file_name> with the same name will not be restored


Click Finish. After clicking Finish, Druva initiates restore pre-checks. These checks look for issues that can cause your restore job to fail, for example, UNC share not reachable. Druva does not initiate a restore job if the restore pre-checks identify any issues. You must fix any identified issues before restoring your data. For more information, see Restore pre-checks.
​

precheck.png

πŸ“ Note
​ If all the pre-checks are successful, the restore job is triggered automatically after 5 seconds or when you click Proceed to restore. You can click Proceed to restore even before pre-checks are finished. In this case, pre-checks are ignored, but the job may fail.
If some pre-checks fail, it is recommended to fix the identified issues before clicking Proceed to restore. However, you can still click Proceed to restore, even if some pre-checks have failed.

Did this answer your question?