Skip to main content
Druva Documentation

NAS FAQs

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

This FAQs topic contains the following sections: 

Overview

What is the difference between a NAS proxy and Phoenix Agent?

 A NAS proxy is the same as Phoenix Agent; it is the link between the NAS device and the Phoenix server to handle the backup and restore of NAS  shares.  To back up from NAS shares, you must install the NAS proxy on a separate Linux or Windows server and map it to the NAS device. Phoenix supports backup from SMB Shares if the proxy is installed on a Windows server. Similarly, to back up from NFS  Shares, the proxy must be installed on a Linux server.


I do not see NAS Devices tab in the beginning?

You can see the NAS Devices tab after you have added at least one  NAS proxy. Subsequently, you can add NAS device, map NAS proxy, and add NAS shares.


How to differentiate between a smart scan restore point from a full scan restore point?

The full scan restore point is marked with  icon.

Configuration


What if I forget to copy or save the activation token of my NAS proxy? Does Phoenix store old activation tokens?

Phoenix saves the old activation tokens and displays them under Manage > Activation Tokens. You can copy the activation token from the Manage Activation Tokens page.


Is there a limit to how many NAS proxies I can install?

No. You can install any number of NAS proxies. The proxies become functional in backup and restore jobs only when they are mapped to a NAS device and are attached to a backup set.


Can I restore to a share in a different administrative group?

Yes, you can restore data to a share in a different administrative group, provided:

  • The share is in the same organization.
  • You have the access rights to the share on which you want to restore.

How do multiple backup sets contribute to efficient backup performance?

A backup set comprises of a content rule, backup policy, and NAS proxy. You can use different combinations of these components to perform efficient backups and optimize the available bandwidth. For example, you can back up PDF and .txt files using one backup set and configure another backup set to back up .xls and image files. You can also use different policies to back up data at different frequencies. 


Can I copy or duplicate a backup set?

No, you cannot copy a backup set to the same or different share. For a NAS share, you can create multiple backup sets with exactly same configurations (such as content rule, backup policy, and NAS proxy) but with unique names. Across different NAS shares, you can create multiple backup sets with exactly same configurations, provided the proxy is mapped to the NAS device of the share.   


Can I attach the same proxy to multiple backup sets of different NAS devices?

Yes, provided the proxy is mapped to the NAS devices.


►What are the benefits of enabling smart scan?

The smart scan feature is best suited for NAS shares having:

  • Files and folders that do not change for a very long period of time, and
  • Files and folders that are used for archiving data

When you configure such files and folders for backup, the agent scans all folders specified in the policy. Typically, in a NAS share, the number of files and folders configured for backup is very large, and scanning for identifying changes takes a very long time. If a particular folder or certain files are not modified for a very long period of time, enabling smart scan can save a lot of time in incremental backups. If the smart scan feature is enabled, the agent skips scanning files and folders that are not modified for a long period of time. 


►I have enabled smart scan, what ACLs will be restored when I restore data in the middle of a month?

Consider a scenario where the following restore points are created after two backups on the File server:

  • R1 - Created after the first full backup.
  • R2 -Created after subsequent backup with the smart scan.

Phoenix restores file data in one of the following ways:

  • If file data is not changed after R1: Phoenix restores data from R2 and the ACLs are restored from the last full backup, which is R1.
  • If file data is changed after R1: Phoenix restores data and ACLs from R2.

► How does Phoenix treat stub files on a NAS share at the time of a backup?
Phoenix backs up stub files as flat files with the size of zero bytes. However, Phoenix does not read the archived file on the archive destination the stub file refers to, and Phoenix does not backup the offline attributes that specify the archive destination. For example,  if the file foo.txt is converted to a stub file with its contents moved to archive storage, Phoenix will backup foo.txt stub as a flat file with size zero bytes without its content. Phoenix does not read the archived file that is stored on the archive storage.  In addition, Phoenix does not backup the attributes that specify the archive destination where the actual archived content of the foo.txt file is stored.

 

  • Was this article helpful?