Skip to main content

 

Druva Documentation

About restoring files and folders

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

What you must know about File server restore

Points that you should know about File server restore:

  • Hot snapshots reside on Phoenix CloudCache for a period that you have specified at the time of Configure Phoenix CloudCache.
  • If you are a group administrator, you can only restore data to a server that belongs to a server group that you manage. Cloud administrators can restore data to servers across server groups.
  • You can only restore data to a server that has the same operating system as the source server.
  • In the event of a network connection failure at the time of restore, Phoenix agent attempts to connect to the Phoenix cloud. After the network connection is restored, Phoenix agents restart the restoring from the state where they were interrupted. 
  • If you restart or reboot your servers 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.
  • 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.
  • During an ongoing restore and scheduled backup, if the client machine is restarted then jobs request may not be present to the client machine.
  • For Windows,
    • The following file attributes are supported:
      • Read-only
      • Content Not indexed.
    • All the Access Control Lists (ACL's) are restored.
  • For Linux,
    • 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 is not supported:
      • Setgid
      • Sticky bit
      • Setuid
  • From version 4.6.8 and later, Phoenix can backup and restore empty folders. After the upgrade,  the Windows File server agent where USN journal is enabled:
    • The empty folders created before the last backup and before the client upgrade will not be backed up. Contact Druva Support to backup these empty folders.
    • The empty folders created after the last backup but before the client upgrade will be backed up.

      The Windows File server agent where UNC share is configured for backup, empty folders in the UNC share, created before and after the upgrade will be backed up and restored.

After the Linux File server agent upgrade, the empty folders created before and after the upgrade will be backed up and restored.

  • Backup and Restore can run simultaneously on the same agent.
  • For mixed workloads, you cannot trigger restore for File server and MS-SQL server simultaneously. You need to wait until the restore of a particular workload finishes.
    •  If you trigger a restore request for a File server while another restore is in progress for the File server, the triggered restore request is queued.
    • If you are triggering a restore request for a  File server while the restore is in progress for MS-SQL server, the restore request for the File server will not be triggered and the following error message will be displayed:

  • File server agents earlier than version 4.6.9 cannot run a backup and restore request simultaneously. If a restore request is triggered while a backup is in progress, the following message is displayed:

  • If you select Cancel Backup and Start Restore option, the backup in progress will be canceled and an error PHOENIX247 will be displayed on the Jobs page.The triggered restore request is processed.
  • If you select Start Restore After Backup is Finished option, the triggered restore request will be queued.
  • File server agents earlier than version 4.6.9, the backup request triggered while a restore is in progress will be queued.
  • Full scan restores will be marked  icon.

Restore workflow on the same File server 

Restore workflow on a new File server

Steps to restore File server

Step Operation

Step 1

You or another administrator initiates a restore operation.

You can restore the data at the original location or an alternate location. The alternate location can be the same server and different path or different server and different path.

You can select the destination server where restore can happen for the selected File server restore point. For example, Windows server for Windows restore and Linux server for Linux restore.

Step 2

Phoenix checks if Phoenix agent is running. 

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

Step 3

Phoenix validates the restore destination. 

Step 4

Phoenix checks the free space available at the restore destination.

Step 5

Phoenix identifies the file sets for restore.

Step 6

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

 Note: For more information about restoring file servers, see Restore a File server to the same serverRestore the File server to a different server.