Avamar: Restore UI backup size differs to the backend report for the same client
Summary: Why does the Avamar restore UI backup size show a different value to the backend report value for the same client?
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
The Avamar Administrator Restore interface shows a backup size which is different to the backend report for the same client.
The Avamar Administrator restore UI shows the backup size to be 11.2 GB.
If we run a backend report on the same client, we get a different value - 8.5 GB.
The Avamar Administrator restore UI shows the backup size to be 11.2 GB.
If we run a backend report on the same client, we get a different value - 8.5 GB.
Cause
These reports calculate different things. We should not expect them to match.
The 11.2GB backup size shown in the Avamar restore interface is also recorded in the backup log.
2014-10-24 10:01:53 avtar Info <5156>: Backup #354 timestamp 2014-10-24 10:03:26, 7,744 files, 776 folders, 11.24 GB (4 files, 218.3 KB, 0.00% new)
11.2 GB is the amount of data which is being scanned during a single backup on the client.
This value measures data on the source file system before any deduplication occurs.
The backend report calculates the amount of space consumed by the deduplicated data on Avamar.
The value does not consider additional space overhead consumed by parity stripes for RAIN systems.
The backend report also calculates the space consumed by the deduplicated data for ALL the client backups which are retained on the server, not just a single backup.
The 11.2GB backup size shown in the Avamar restore interface is also recorded in the backup log.
2014-10-24 10:01:53 avtar Info <5156>: Backup #354 timestamp 2014-10-24 10:03:26, 7,744 files, 776 folders, 11.24 GB (4 files, 218.3 KB, 0.00% new)
11.2 GB is the amount of data which is being scanned during a single backup on the client.
This value measures data on the source file system before any deduplication occurs.
The backend report calculates the amount of space consumed by the deduplicated data on Avamar.
The value does not consider additional space overhead consumed by parity stripes for RAIN systems.
The backend report also calculates the space consumed by the deduplicated data for ALL the client backups which are retained on the server, not just a single backup.
Resolution
The behavior is expected.
Affected Products
AvamarProducts
AvamarArticle Properties
Article Number: 000038550
Article Type: Solution
Last Modified: 06 Feb 2025
Version: 5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.