Global Repository Cell (GRC)

Post Migration

What gets Migrated

The following components are available for migration:

Client computers and the Agents installed on the Client can be migrated to another CommCell.
Client Group definitions are migrated but not the associations and the clients associated to the Client group.

Note that the client group definition is migrated. The actual clients within the group are not migrated unless they are selected for migration.
Subclient policies, schedule policies, user groups, media location and alerts associated with the CommCell.
Client configurations such as holidays, operation window, activity control, and schedules can be migrated.
Tape library will be migrated as a deconfigured library.
Metadata records associated with the backup data secured by Data Protection operations from the Agents. This includes the following:
- History information.
- Information about media.
- Storage Policy and Storage Policy Copies associated with the subclients configured in the Client, including storage policies and storage policy copies used in the past, that contain valid data from the Client.

The following components associated with a source CommCell are not migrated:

The data and binaries that are associated with metadata are not migrated.
History information associated with Data Recovery operations and administration jobs.
Firewall related configuration information.
Events associated with jobs generated by Clients that are migrated.
Audit trail information associated with the client
Subclient-based Storage Policy Copy associations.
Any associations related to the configurations i.e., non-data bearing entities associated with a client such as schedule policies, subclient policies etc. They are migrated as configuration templates.
Data Aging Schedules.
Use of existing Global Deduplication Policy for migrated data from a different CommCell.
SRM Data.

The following views are available in SQL after migration. For more information about views, see CommCell Views.

View	Notes
CommCellRetentionInfo	Used storage policies with "Data aging Enabled" value modified to "NO"
CommCellSnapInfo	Mounted snapshots
CommCellStoragePolicy	Storage policies used in backup jobs
CommCellSubClientConfig	Used clients in "uninstalled" status
CommCellUpdateInfo	Information for agents in which jobs run
CommCellBackupInfo	All successful jobs except for those with the ‘xmljoboptions’ column is set to NULL
CommCellBkupSizeInfo	Jobs that are completed or complated with errors
CommCellClientConfig	Clients with successful jobs
CommCellClientFSFilters	Clients with successful jobs
CommCellClientLevelBkpJobSummary	Jobs that are completed or complated with errors
CommCellCompletedBkpJobsInfo	Jobs that are completed or complated with errors
CommCellMediaInfo	Media information that is associated with the used library
CommCellMediaSubClient	Media that is associated with the used subclient
CommCellPrePostCmdInfo	Subclients with successful jobs
CommCellLibraryInfo	Libraries that are used for backup operations

The following must be considered while performing these operation s on migrated data:

Barcodes associated with tapes
Ensure that you check the barcodes associated with the tapes in the CommCell to make sure that there are no duplicate barcodes across all CommCells being migrated.

If you find two tapes that have the same bar code, one of them must be changed.
Migrating mount path
When you migrate a mount path that contains deduplicated data, the Interval (Minutes) between disk space updates parameter is created with a default value in minutes. This value will ascertain the time taken by MediaManager to automatically detect and update the new mount paths for deduplicated data.

This in turn will determine the time to restore the data on the new target MediaAgent.