Skip to main content

 

Druva Documentation

About NAS share restore

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

Workflow to restore on the source NAS share 

RestoreToSameLocation.png

Workflow to restore on a different NAS share 

RestoreToAlternateLocation.png

Steps to restore a NAS device

Step Operation

Step 1

You initiate a restore operation.

You can select the destination share for the restore of the selected NAS restore point. For example, SMB share for a Windows restore and NFS share for a Linux restore.

Step 2

Phoenix checks if the NAS proxy is running. 

  • If the proxy is running, Phoenix performs the restore operation.
  • If the proxy is not running, Phoenix queues the restore request and performs the restore operation after the NAS proxy starts.

Step 3

Phoenix checks whether the share type of the restore destination is same as the sources and validates the restore request.

Step 4

Phoenix identifies the snapshots to restore.

Step 5

Phoenix starts the restore operation and sequentially downloads the snapshots to the restore destination.

 Note: For more information about restoring a NAS share, see Restore a NAS share.

What you must know about NAS share restore 

This section highlights the important considerations of the NAS share restore:

  • Hot snapshots reside on the Phoenix CloudCache for the period specified in the CloudCache configuration. See Configure Phoenix CloudCacheCloudCache for information on the configuration.
  • If you are a group administrator, you can only restore data to a server that belongs to an administrative group that you manage. Cloud administrators can restore data to shares across administrative groups.
  • You can restore data only to a share that has the same operating system as the source share. 
  • In the event of a network connection failure during restore, the NAS proxy attempts to connect to the Phoenix Cloud. After the network connection is restored, the NAS proxy restarts the restore from the state where it was interrupted. 
  • If you restart or reboot the NAS device during a restore, the restore operation is aborted. 
  • If you choose to restore data to the same location, the existing data at that location is overwritten unless a different restore setting is configured.
  • The snapshot timestamps are displayed according to the server time zone. For example, for servers located in New York and London, the timestamps are displayed according to EST and UTC time zones, respectively.
  • Restores are not supported to mapped drives.
  • For SMB shares:
    • The following file attributes are supported:
      • Content Not indexed.
      • Read-only
    • All the Access Control Lists (ACLs) are restored.
  • For NFS shares,
    • File permissions for file owners, groups, and users are restored.
    • File attributes are not supported.
    • ACL permissions are not supported.
    • The following special permissions for files and folders are not supported:
      • Setgid
      • Sticky bit
      • Setuid
  • Backup and restore can run simultaneously on the same agent.
  • The backup request triggered while a restore is in progress will be queued.
  • Full scan restore will be marked with an  icon.
  • Was this article helpful?