CommCell Migration - FAQ
How can I manage the deduplication database after CommCell Migration on the Destination CommCell?
After CommCell migration, migrated storage policies can no longer be used for local backups. Basically, a storage policy should only have data from one CommCell.
After CommCell migration, the deduplication database operates in read-only mode on the destination CommCell. The migrated deduplicated storage policies on the destination CommCell can be used to restore the migrated deduplicated data and to perform Auxiliary Copy jobs. However, new deduplicated backup jobs cannot be performed to the migrated storage policies on the destination CommCell.
Do we migrate the content indexes during CommCell migration?
No. The content indexes are not migrated by a CommCell migration.
Can I Use the Migrated Storage Policies for Backups of Migrated Clients in the Destination CommCell?
No. Storage Policy should only have data from one CommCell. Hence after CommCell migration, migrated storage policies can no longer be used for backups. If you want to perform backups of migrated clients, then you must assign a local storage policy (storage policy created in the destination CommCell) to subclients of the migrated clients.
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.
Last modified: 2/19/2018 6:02:00 AM