After CommCell Migration, the merged mount paths are disabled for write operations to prevent new data being written onto them. These mount paths are used for restore purposes only. New mount paths should be created for future backup operations.
By default, pruning is disabled on the migrated mount paths. However in case of permanent CommCell Migration, you can configure pruning on migrated mount paths by enabling read/write access on them. See Data Aging of Migrated Mount Paths for step-by-step instructions.
For information about data aging of the deduplicated data present in the migrated mount paths, see Data Aging for Deduplication.
@kszaf I want to make sure I am understanding the issue correctly. Are you saying that you moved mount paths and that you are seeing a size disparity between what shows on the new mount path and what should be there?
After CommCell Migration, the merged mount paths are disabled for write operations to prevent new data being written onto them. These mount paths are used for restore purposes only. New mount paths should be created for future backup operations.
By default, pruning is disabled on the migrated mount paths. However in case of permanent CommCell Migration, you can configure pruning on migrated mount paths by enabling read/write access on them. See Data Aging of Migrated Mount Paths for step-by-step instructions.
For information about data aging of the deduplicated data present in the migrated mount paths, see Data Aging for Deduplication.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.