CommCell Migration

Basic Advanced Troubleshooting 

The following section provides information on some of the troubleshooting scenarios related to CommCell Migration:

Merge Failure

During CommCell Migration
  • Ensure that compatible drives are available in the destination CommCell to restore the migrated backup data.
  • The source and destination CommCells should be accessing the same version of CommServe(s).
  • Make sure that you have the same SQL Server version in the source and destination CommServe. For example, if you have SQL 2008 R2 version in the source, you need to have the same version in the destination as well.
  • If the SRM Server is installed in Source CommServe, make sure to install the SRM Server on destination CommServe too while performing CommCell Migration. This is because an SRM Analytics Policy is required to be associated with the migrated SRM components and there is one SRM Analytics Policy per CommCell.

Migration Failure

CommCell Migration Fails when the CommServe and SQL server exist in two different computers SQL Server requires the dumps that are to be backed up/restored on a local folder in a local drive. A local staging area (For example: C:\SomeDir) needs to be created on the SQL server for which the Commserve also needs to have access to (in order to push/pull dumps to/from it).

When the CommServe and SQL server are in two different computers, create the following registry keys in CommServe to let it access the shared location in SQL server and successfully allow the CommCell migration.

Enabling auxiliary copy on migrated storage policies

After CommCell Migration Auxiliary copy job will only copy the new backups and not the merged jobs. By default auxiliary copy on migrated storage policies is disabled. You may enable the Auxiliary copy operations on migrated storage policies using the following registry key.