- ►How do I deploy Phoenix File server?
After you buy a license, you must deploy Phoenix Agents for the File server. For more information, see Deploy Phoenix File server agent.
►What server operating systems does Druva support for the File server?
Druva supports Windows and Linux operating systems for File servers. For more information about the supported operating systems, see File server support matrix.
Phoenix backs up files and folders on NTFS and ReFS.
Yes, Phoenix supports data deduplication on NTFS and ReFS, however, it does not support back up of the extended attributes, such as encryption and compression.
►What file types, by default, Druva support for the File server?
Phoenix provides support for several file types, out-of-the-box. To see the full list of files that Phoenix backs up, see Default file types for backup.
►What type of backups does Phoenix perform on File servers?
The first backup of your servers is a full backup. Thereafter, Phoenix performs an incremental backup of all File servers.
►How do I configure my File servers for backup?
Getting your File servers ready for backup is simple. To know how to do this, see Initial configuration of your file servers.
►What do I need to know before performing a configuration of my File servers?
Before configuring your File servers, we recommend that you read File server configuration checklist. This checklist should help you perform a configuration that is best-suited for your environment.
►What does Phoenix exclude from backup?
By default, Phoenix excludes some file types from backup. To see the full list of files that Phoenix excludes, see Default folder exclusions.
►How do I back up or restore my data?
►How does Phoenix back up or restore my File server data?
►I want to run a backup job manually. How do I do that?
After you configure your servers, Phoenix performs a backup of your servers according to the backup policy that you set at the time of configuration.
In addition to the scheduled backups, you can start a backup at any time. After these backups complete, the next backup from the File servers follows the schedule defined in the backup policy.
- Log in to the Phoenix Management Console.
- On the menu bar, click All Organizations, and select the required organization from the drop-down list.
- On the menu bar, click Protect > Windows/Linux Servers.
- Click the File Backup Sets tab.
- In the Server Name column, click the server name.
- Click Backup Now.
Note: The Last Backup Time entry for each server on the Backup Overview page follows the time zone of the server. For example, if your servers are located in New York and London, the timestamps will follow the EST and UTC time zones, respectively.
Note: The first Backup Now will always trigger a full backup for File server and MS SQL server. The subsequent Backup Now requests will trigger an incremental backup for File server and Differential Backup for MS-SQL server.
For more information on Differential Backup, see Differential backups.
►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.
►Phoenix Management Console displays a different count of source data scanned than the actual files.
The Job Details page may show a different count of the source data scanned for a backup job than the actual files being backed up as shown in the following screenshots:
Backup Data section on the Dashboard screenshot:
Job Details page screenshot:
In the above screenshots, the Backup Data section on the Dashboard depicts that Phoenix backs up 1.38 TB data although it scans 2092531 files of 1.78 TB source data as shown in the Job Details page screenshot.
Phoenix implements folder walk or USN walk to scan files for backup. In a nested file structure, the count of the scanned files is always greater than the estimated files. For example, to scan 10K files at the ninth folder level, Phoenix scans the nine folders along with the files and folders contained in the folders, and 10k files that result in the scanned count greater than the actual files. In a USN walk scan, the count of scanned files comprises the USN event count for the volume.
The count of the source data scanned also differs if the network disconnects when the data is being uploaded to the cloud. During the next reconnection, the respective data is scanned again and uploaded. This results in an additional count of the data scanned.
Additionally, the count of the source data scanned may differ if you have not excluded the /proc folder from the backup configuration. The /proc folder contains ever-changing files. Because the file creation is dynamic, the Phoenix agent continues to estimate the file content. The sparse file blocks are also a part of the /proc folder, which leads to incorrect estimation statistics. Therefore, ensure that you exclude the /proc folder from the backups.
►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 the 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.