Skip to main content

 

Druva Documentation

FAQs on Phoenix for NAS shares

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

Questions

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 separate installers for NAS Proxy on the downloads page. Which installer should I use?

Use the Phoenix Agent installer to install the NAS Proxy.  Since NAS proxy is same as the Phoenix Agent, you can use the agent installer to install the NAS proxy.


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.


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. 


What happens to backups if I restart my NAS device when the backup is in progress?

If you restart or reboot your NAS device when backup is in progress, the backup operation is paused. NAS proxy resumes the backup from where it had paused after the NAS device restarts.


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.


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

The full scan restore point is marked with  icon.


►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 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.

► Please explain the Smart Scan feature if I have enabled the Only scan files created/modified in the last <selected number of>  months option.

To understand the age based scanning feature, consider the following sample:

You want to backup the folder called MAINFOLDER, which has the following hierarchy:

MAINFOLDER
  • fm1.txt
  • fm2.txt
  • SUBMAINFOLDER
    • sf1.txt
    • sf2.txt
    • sf3.txt
    • NEXTSUBFOLDER
      • ns1.txt
      • ns2.txt

MAINFOLDER, SUBMAINFOLDER, NEXTSUBFOLDER are folders, and everything else is a file. 

In the smart scan, you have specified:

And in the main policy you have specified:

With the above sample configuration, there are three possible conditions for smart scan.

Condition 1:

  • MAINFOLDER, SUBMAINFOLDER, NEXTSUBFOLDER, and all the files were created on January 1st, 2017.
  • No files or folders were modified.
  • You configured MAINFOLDER for backup on April 1st

Based on the configuration, the first backup job is triggered on April 3rd, 2017. The first backup is always a full backup, so all the files and folders are scanned, the agent creates a snapshot and saves it on Phoenix Cloud. April 4th onwards, the Phoenix agent smart scans the MAINFOLDER. The checks are:

  • If the MAINFOLDER was modified
  • If fm1.txt, fm2.txt, and SUBMAINFOLDER was modified.

Since no entity under MAINFOLDER was modified, the Phoenix agent skips further scanning until the scheduled full scan is triggered on April 22nd.

Condition 2:

  • MAINFOLDER, SUBMAINFOLDER, NEXTSUBFOLDER, fm1.txt, fm2.txt, sf1.txt, sf2.txt, and sf3.txt were created on January 1st, 2017.
  • Files ns1.txt and ns2.txt were created on March 26th, 2017.
  • You configured MAINFOLDER for backup on April 1st

Based on the configuration, the first backup job is triggered on April 3rd, 2017. The first backup is always a full backup, so all the files and folders are scanned, the agent creates a snapshot and saves it on Phoenix Cloud. Since files ns1.txt and ns2.txt were created on March 26th, 2017, these files have age less than 90 days. April 4th onwards, the Phoenix agent smart scans the MAINFOLDER, and the checks are:

  • If the MAINFOLDER was modified
  • If fm1.txt, fm2.txt were modified
  • If SUBMAINFOLDER was modified
  • If sf1.txt, sf2.txt, sf3.txt were modified
  • If NEXTSUBFOLDER was modified
  • If ns1.txt, ns2.txt were modified

Since files ns1.txt and ns2.txt have age less than 90 days, Phoenix includes the entire MAINFOLDER hierarchy in further smart scans until the age of all the files is more than 90 days.

Condition 3:

  • MAINFOLDER, SUBMAINFOLDER, NEXTSUBFOLDER, and all the files were created on January 1st, 2017.
  • No files or folders were modified until April 15th On April 15th, the file ns2.txt was modified.
  • You configured MAINFOLDER for backup on April 1st.

Based on the configuration, the first backup job is triggered on April 3rd, 2017. The first backup is always a full backup, so all the files and folders are scanned, the agent creates a snapshot and saves it on Phoenix Cloud. April 4th onwards, through April 21st, the Phoenix agent smart scans the MAINFOLDER. The checks are:

  • If the MAINFOLDER was modified.
  • If fm1.txt, fm2.txt, and SUBMAINFOLDER were modified

Since no entity under the smart scan checks was modified for a period of more than 90 days, the Phoenix agent skips further scanning. The updates to file ns2.txt are not detected until the next scheduled full scan.

Since Saturday is specified for a full scan, and a full scan is scheduled every four weeks, the next scheduled full scan is on April 22nd, 2017. April 22nd, 2017 is the last Saturday within the time period of four weeks. Phoenix agent triggers a full scan on Saturday, April 22nd, 2017, and identifies the modification in ns2.txt. It creates a new snapshot with modification in ns2.txt and saves it in the Phoenix cloud. Since there is a change in ns2.txt and therefore in NEXTSUBFOLDER, April 24th, 2017 onwards, entire MAINFOLDER hierarchy is scanned in every smart scan triggered from Monday through FRIDAY every week until the age of all the files is older than 90 days. 

Note: When Phoenix scans folders for modifications during a backup job, it detects a change in the folder if a file is added, modified, or deleted.