Problem description
On a File Server, the data scan size shown in the Druva Phoenix console may appear larger than the actual folder size displayed on disk.
This difference can be confusing, especially when administrators expect the backup scan size to match the on-disk folder size exactly.
Cause
This typically occurs when the default folder exclusions are removed from the content rule.
By default, Druva Phoenix excludes specific system and snapshot-related folders that are not required for data protection. When these exclusions are removed, Phoenix scans the additional hidden or system-level content, increasing the total data scan size.
Default Excluded Folders
$Recycle.Bin
System Volume Information
.snapshot
If these exclusions are not in place, Phoenix will include the above folders in its scan, along with any similarly named directories such as #recycle or #snapshot.
These folders can contain a large amount of system or hidden data — for example, user recycle bins, volume shadow copies, or file system snapshots — which can cause the “Data Scanned” value in the console to exceed the folder size visible in the OS.
Resolution
To ensure that the data scan size reported in the Phoenix console closely matches the actual data size on disk:
Retain the default exclusions in the content rule.
Ensure the following folders are excluded:
$Recycle.Bin
System Volume Information
.snapshot
Avoid removing or modifying these exclusions unless explicitly required for troubleshooting.
If the exclusions were removed, edit the content rule in the Phoenix console and re-add them.
Expected Behavior
If the default exclusions are removed, Phoenix will scan all system, recycle bin, and snapshot directories. As a result, the “Data Scanned” value in the Druva console can be significantly higher than the actual folder size visible in file properties.
This is expected behavior and does not indicate a backup issue or data duplication.
Best Practice
Always keep the default exclusions for $Recycle.Bin, System Volume Information and .snapshot in the content rules.
Excluding these folders prevents unnecessary scanning of system and snapshot data, reduces backup time, and ensures accurate data scan reporting.