Manage a Multiple-CommCell Environment
If you have an environment with multiple CommServe servers, you can manage that environment using a Global Repository Cell (GRC). A GRC is a CommCell system that is configured as a repository to monitor the metadata of jobs from other CommCell systems. The CommCell systems that are monitored are called PodCells.
You can use a Global Repository Cell to complete the following tasks:
- View browse and restore jobs for a PodCell
- Perform cross-machine restores to clients that are local to a Global Repository Cell. Or, if the Global Repository Cell has access to the clients’ backup data, you can create auxiliary copies of the backup data.
- Push configuration data (schedule policies, subclient policies, users and user groups, alerts, and media location) from a Global Repository Cell to PodCells
Global Repository Cell Compared to CommCell Migration
Global Repository Cell
- A Global Repository Cell monitors the metadata of jobs from other CommCell systems (PodCells).
- A Global Repository Cell transfers the metadata on a recurring schedule, and thus synchronizes the metadata.
Caution: A Global Repository Cell is not recommended for the following tasks:
- One time migration. Instead, use CommCell Migration.
- Setting up disaster recovery. Instead, use CommServe LiveSync For High Availability Disaster Recovery.
- Cross CommCell reporting. For metrics and reports purposes, use Enterprise Metrics Reporting Server.
CCM (CommCell Migration)
- CommCell migration is a one-time migration. A CommCell migration can be either temporary, to restore data one time, or permanent, to move a client to a different CommCell system.
- CommCell migration transfers the metadata only one time and does not synchronize the metadata. Thus, after you import data with CommCell migration, jobs that have been pruned in the PodCell may appear as available.
Last modified: 7/16/2019 2:50:04 PM