The following sections explain the requirements that are mandatory for the Global Repository Cell setup to work effectively.
CommServe
The PodCell and the destination CommCell systems must have the same version of the CommServe software installed.
For more information, see CommServe Installation.
MediaAgent
If you want to restore data from any imported client, at least one MediaAgent must be installed on the destination CommCell system. For more information, see MediaAgent Installation. For more information about restoring data from an imported client, refer to Restore Data from imported clients.
SQL Server Version
Global Repository Cell uses database dump files. For restoring dump files, the Global Repository Cell must be the same version or a more recent version of Microsoft SQL Server as the PodCell is on. The specific requirements for the SQL Server versions are as follows:
-
If push-back is enabled, both the PodCell and the Global Repository Cell must be on the same version of SQL Server.
-
If push-back is not enabled, the Global Repository Cell can be on a more recent version than the PodCell is on. However, we recommend that both the Global Repository Cell and the PodCell are on the same version of SQL Server.
-
The PodCell cannot be on a more recent version of SQL Server than the Global Repository Cell is on. The PodCell must be on the same version or on an earlier version of SQL Server.
User Permissions
The CommCell user who uses the CommCell Registration Wizard must have the following permissions:
-
Alert Management
-
Administrative Management
For more information, see User Security Permissions and Permitted Actions.
Firewall
If the PodCell and the destination CommCell systems are separated by a firewall, you must create the pseudo client for the PodCell in the Global Repository Cell.
Adding a pseudo client for the Global Repository Cell is similar to installing any client in the CommCell system. For the Global Repository Cell, in addition to installing another client, you must register the PodCell as a client.
To set up the connection route between the destination CommCell system and the PodCell, see Firewall for instructions.
The following table displays the ports required for GRC operations:
|
Operation |
Source |
Destination |
Connection Initiation |
Port(s) |
Protocol |
|---|---|---|---|---|---|
|
CommCell registration |
GRC CommServe |
PodCell CommServe |
GRC CommServe |
8401, 8400 |
TCP |
|
Setup GRC monitoring schedule |
GRC CommServe |
PodCell CommServe |
Two-way |
8401, Random port |
TCP |
|
Import job |
GRC CommServe |
PodCell CommServe |
GRC CommServe |
Random port, 8400 |
TCP |
|
Export job |
PodCell CommServe |
GRC CommServe |
PodCell CommServe |
Random port, 8400 |
TCP |
Guidelines for Scaling the Global Repository Cell Setup
You can register multiple CommCell systems in a destination CommCell system. You can also import clients from multiple CommCell systems into a single destination CommCell system.
Consider the following guidelines when you import clients from multiple PodCells into a Global Repository Cell system. For comprehensive information about the following requirements, see
System Requirement for CommServe.
-
Do not configure more PodCells than a Global Repository Cell can monitor effectively.
-
If a PodCell has more backup data, then the export and import operations might take more time. Increase the schedule frequency of export and import operations so that incremental exports and imports have less data to process.