This topic consists of the following sections:
► What does Druva Phoenix back up?
- Druva Phoenix provides support for several file types, out-of-the-box. To see the full list of files that Druva Phoenix backs up, see Default file types for backup.
►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.
►What file systems does Druva Phoenix support?
Druva Phoenix supports file and folder backup of the following file systems:
- On Windows: NTFS and ReFS
- On Linux: EXT3, EXT4, and XFS
Note: Druva Phoenix also supports the backup of files and folders on the non-VSS partitions such as FAT, FAT32, and exFAT.
►Does Druva Phoenix support data deduplication on NTFS and ReFS?
Yes, Druva 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?
Druva Phoenix provides support for several file types, out-of-the-box. To see the full list of files that Druva Phoenix backs up, see Default file types for backup.
►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.
►How do I deploy Druva Phoenix File server?
After you buy a license, you must deploy Phoenix agents for the File server. For more information, see Deploy Druva Phoenix File server agent.
►How do I configure my File servers for backup?
Getting your File servers ready for backup is simple. For more information about how to configure File servers for backup, see Configure Druva Phoenix to back up File servers.
Backup and restore FAQs
►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.
Druva Phoenix restores file data in one of the following ways:
- If file data is not changed after R1: Druva 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: Druva Phoenix restores data and ACLs from R2.
►What will be the effect on backup if we change the IP address of the file server?
There will be no effect on the backup as Druva Phoenix does not use IP address as a unique identifier for backups.
►What type of backups does Druva Phoenix perform on File servers?
The first backup of your servers is a full backup. Thereafter, Druva Phoenix performs an incremental backup of all File servers.
►How do I view the files that were missed or skipped during the backup?
- Download the log folder and open the ‘Phoenix-
-MissedFiles.log’ file to view the list of files that were skipped or missed during the backup operation.
►What does Druva Phoenix exclude from backup?
By default, Druva Phoenix excludes some file types from backup. To see the full list of files that Druva Phoenix excludes, see Default folder exclusions.
►How do I back up or restore my data?
►How does Druva 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, Druva 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 > File Servers.
- In the Registered Servers page, under the Server Name column, click the server name.
- In the server details page, under the Configured Backup Sets section, select the backup set, click more options, and then click Backup Now.
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.
►What are the benefits of enabling smart scan?
Smart Scan applies to backups of SMB and NFS shares that have:
- Files and folders that are infrequently modified
- Archive or log data
When a large number of infrequently modified files and folders are configured for backups in a backup policy, backups can take long because the Phoenix agent scans every file and folder. Enabling Smart Scan for these backup sets can save a lot of time by skipping infrequently modified files and folders.
Note: The smart scan applies to Linux servers, NAS shares and Windows servers (only UNC shares)
►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 Druva 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.
Druva 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, Druva 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.
Download the log folder and open the ‘Phoenix-<JobID>-MissedFiles.log’ file to view the list of files that were skipped or missed during the backup operation.