If you have identical jobs on both the primary copy and the secondary copy, then use the following list to determine the reasons for having considerably higher number of records on the secondary copy as compared to the primary copy.
-
A mount path of the secondary copy is offline.
-
Records are marked bad in the deduplication database configured with the secondary copy.
-
Data aging is not running on the secondary copy.
-
The Distribute data evenly among multiple streams for offline read operations check box is selected on the Storage Policy Properties tab.
-
The Copy first full jobs for new subclients on secondary copy with deduplication enabled before copying other data parameter is not enabled.
-
There is a mismatch between the total capacity and the free space of the disk library that is visible from the CommCell Console and the actual space occupied by the records on the disk.
-
The deduplication block size is different on both the primary copy and the secondary copy.
-
If the Space optimized Auxiliary Copy check box is not selected on the Copy Policy tab of the Storage Policy Copy Properties dialog box. Select the Space optimized Auxiliary Copy check box, and seal the DDB before running the auxiliary copy operation. Sealing the database is required as new reference blocks are written in the new format so that during an auxiliary copy operation the new blocks are identified and copied. This ensures that there is no mismatch between the number of records on the secondary copy and the primary copy.
-
If it is the database type data, then the block alignment is done with uncompressed size on the primary copy whereas during auxiliary copy operation the data is compressed and then deduplicated. To eliminate discrepancy in the number of records between the primary and the secondary copy, seal the DDB on secondary copy and use the same deduplication factor as that of the primary.
For more information about database type data see, Database Data Size Mismatch Between the Primary Copy and the Secondary Copy.
-
In case of the database logs, deduplication happens on the primary copy but not on the secondary copy and the secondary copy contains lesser number of records as compared to the primary copy.
-
Extended retention is set on the secondary copy and therefore data is retained for longer period of time on the secondary copy.
-
Data pruning is lagging on the secondary copy.
-
In case the data is manually pruned from either of the copies, then too there is a discrepancy in the number of records between the primary and the secondary copies.