How can I manage the deduplication database after CommCell migration on the destination CommCell environment?
After CommCell migration, migrated storage policies can no longer be used for local backup operations. Basically, a storage policy should only have data from one CommCell environment.
After CommCell migration, the deduplication database operates in read-only mode on the destination CommCell environment. The migrated deduplicated storage policies on the destination CommCell environment can be used to restore the migrated deduplicated data and to perform auxiliary copy operations. However, new deduplicated backup operations cannot be performed to the migrated storage policies on the destination CommCell environment.
Do we migrate the content indexes during CommCell migration?
No. The content indexes are not migrated by a CommCell migration operation.
Can I use the migrated storage policies for backups of migrated client computer in the Destination CommCell environment?
No. Storage policy should only have data from one CommCell environment. Hence after CommCell migration, migrated storage policies can no longer be used for backup operations. If you want to perform backups of migrated client computers, then you must assign a local storage policy (storage policy created in the destination CommCell environment) to subclients of the migrated client computers.
Can I migrate a client that doesn't have a subclient?
No. The migration doesn't fail, but the client is not captured. The client to be migrated should have atleast one subclient (default subclient or user-defined subclient) created.
How do we age data from migrated storage policies? Is it done from source CommCell environment or from destination CommCell environment?
The software performs data aging in the source CommCell environment based on the retention period. If you migrated a MediaAgent that contains a library that any migrated storage policy uses to the destination CommCell environment, you must enable data aging on migrated library and storage policy manually in the destination CommCell environment.