We've transitioned to a new documentation portal to serve you better. Access the latest content by clicking here.
If you have taken a standard backup (non-application aware), you can restore:
To know more about the restore workflow, see Nutanix AHV restore workflow.
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 |
|
Linux virtual machine |
|
File-level Restore to NFS share | |
Windows virtual machine |
|
Linux virtual machine (with no root squash) |
|
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.
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.
Note: Currently, restore is supported only to the UNC path. Therefore only CIFS and NFS shares are supported.
Field | Description |
---|---|
UNC Path |
Valid UNC share (network share) path that is reachable from the selected Prism. Valid sharename format:
|
Username |
Valid username of UNC share.
|
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.
|
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.
|
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:
|
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.
Field | Description |
---|---|
UNC Path |
Valid UNC share (network share) path that is reachable from the selected Prism Valid sharename format:
|
Prism |
From the drop-down list, select a Prism that has at least one Backup proxy in the connected state.
|
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.
|
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:
|
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.