Database Data Size Mismatch Between the Primary Copy and the Secondary Copy

For database data, after an auxiliary copy operation runs, a mismatch between the size of data on the primary copy and the size of data on the secondary copy might occur.

Symptoms

Secondary copies have a higher number of records than primary copies, even though both the copies have identical jobs.

Causes

This mismatch between the size of data on the primary copy and on the secondary copy occurs because the data block alignment is performed with uncompressed data on the primary copy during backups whereas, during an auxiliary copy operation, the data is compressed and then deduplicated.

Resolution

1. Upgrade the CommServe server to V11 SP18 or a more recent service pack, the MediaAgent and the database client to V11 SP14 or a more recent service pack.
2. On the secondary DDBs, navigate to the C:\Program Files\Commvault\ContentStore\Base> folder, and then run the following command to set the primary block alignment option.

qoperation execscript -sn DDBParam -si set -si "secondary storeID" -si FollowPrimaryBlock -si 1