Global Repository Cell (GRC) - Getting Started

Before you begin

Refer to the Global Repository Cell (GRC) – Prerequisites.

About the Task

Use the following process to guide you through the set up a GRC :
  1. Registering a PodCell
  2. Setting up Metadata Collection
  3. Testing the Export or Import of GRC Metadata
  4. Preparing a GRC for Restores

Registering a PodCell

The source CommCell is the CommCell from which the clients are imported to the destination CommCell. The Source CommCell will be referred to as PodCell in this documentation.

  1. Log on to the CommCell Console of the destination CommCell.
  2. From the CommCell Console, click Tools and then click Register CommCell.
    The CommCell Registration dialog box is displayed.
  3. Click Add CommCell.
  4. In the User Name box and Password box, type the PodCell credentials.

    The user must have similar Administrative Management capabilities configured at the CommCell levels on both the source CommCell and the destination CommCell.

  5. In the CommCell Host Name, choose the appropriate method based on your security policy:
    • If the PodCell CommServe is not behind a firewall, type the hostname of the PodCell in the CommCell Host Name box.
    • If the PodCell CommServe is behind a firewall, select the Select CommServe client located across a firewall check box and then select the pseudo client name from the list.

      If the pseudo client for the PodCell is not created in the destination CommCell, then create the pseudo client. To set up the connection route between the destination and PodCell, see Firewall for instructions.

  6. Click OK.
  7. Click OK to close the message box.

           You can view the registered PodCell from the following areas:

  • CommCell Registration Window
    A list of registered CommCells is displayed in the CommCell Registration Window (Commserve node | All Tasks | CommCell Registration).
  • CommCell Console
    In the Destination CommCell, the PodCell CommServe is available as an uninstalled client under <Client Computers>.

    In the PodCell, the destination CommServe is available as an uninstalled client under <Client Computers>.

Setting Up Metadata Collection

To collect metadata, import clients from the PodCell to the destination CommCell by using the Setup Monitoring wizard.

Before you begin

Ensure that the PodCell was registered successfully.

  1. From the CommCell Browser, right-click the <Source CommServe>, point to All Tasks | CommCell Registration.
  2. Right click the registered CommCell and then click Setup Monitoring.
  3. On the Monitor Entities page, select the appropriate clients, agents, backup sets, or subclients of the PodCell, and click Next.

    These podcell entities (clients, agents, backup sets, or subclients) are imported to the destination CommServe for monitoring. For more information about the entities that are not imported, go to Frequently Asked Questions.

  4. On the Specify Destination Client Group page, choose whether to associate the imported clients to a client group
    • If you select the Use the following client group option, default, a new client group is created in the destination CommCell for the imported clients

      Select this option if you want to associate all the imported clients to a client group in the destination CommCell. Select the client group name from the Client group drop-down. You can edit the new client group name.

  5. Click Next.
  6. On the Prefixes for Imported Entities page, select one of the following options:
    Option Description
    Do not prefix imported entities Select this option if you do not want to add a prefix to the names of imported entities
    Use following suffix if local entity of same name already exists If the name of the imported entity is same as any entity in the destination CommCell, type the suffix in the box.
    Always add the following prefix to imported entities Select this option if you want to add a prefix to the names of all the imported entities. Type the prefix in the Prefix box.

     You can add prefixes to storage policies, copies, libraries, and devices, except clients.

  7. Click Next.
  8. In the Specify MediaAgents that have read access to the mount paths and edit access paths if needed page do the following:
    1. Select the MediaAgent from the Destination MediaAgent list.

      You can select the MediaAgent after the import using the Remote CommCell Properties dialog box. Selecting a MediaAgent is mandatory for a successful restore operation.

    2. To change the imported mount path location, click Edit Location. Specify the access path. Click OK.

      If the libraries were created in Simpana version 8.0, then select the MediaAgent for the library without editing the path. Mount paths are converted to shared after the import operation, after which you may edit the path.

    3. For the Select MediaAgent for Index Restore drop-down list, select a MediaAgent from the list. Click Next.

      The drop-down box displays only MediaAgents that have at least one library configured to it. If you don’t see the MediaAgents in the drop-down list, then continue with the other steps. Selecting a MediaAgent is mandatory for a successful restore operation. You can select it after the first import using the Remote CommCell Properties dialog box.

  9. On the Export Options page, select one of the following options for the first import.
    • Perform Complete Export

      Imports entire metadata for the selected entities from the PodCell.

    • Export Data From Last

      Imports the recent metadata of the selected entities from the PodCell. You can specify the number of months and days for which the data is required.

      The first import of the data will be performed as per the selected option. All subsequent imports will be incremental.

  10. Click Next.
  11. Optional:To push the destination CommCell entities to the PodCell, select the Push Back Configuration check box. Select the appropriate entities.

    Alerts, subclient policies, schedule policies, and media location information that are created at the destination CommCell are sent to the PodCell. For more information about the entities that are not imported, go to Frequently Asked Questions.

  12. Click Next.
  13. On the Configure Schedule Pattern page, set up the schedule for the monitoring job
    1. In the Schedule Name box, type a name for the schedule
    2. Click one of the following: Daily, Weekly, Monthly, or Yearly.
    3. In the Start Time box specify the schedule start time.
    4. In the Every box, select the number of days for which you want to repeat the job.
    5. If you want to add any exceptions, click Exceptions button. Click to define weekday occurrences or days of the month which you want to exclude from the schedule.
    6. If you want to repeat the schedule, select the Repeat Every check box. Select the values for hr(s), min(s), and until.
    7. Click Finish.
  14. The CommCell Registration dialog box is displayed. If you want to verify the settings for the remote CommCell, you can right-click the registered CommCell and then click CommCell Properties.

     For more information about Remote CommCell Properties, see Remote CommCell Properties

Testing the Export or Import of GRC Metadata

The GRC metadata import and export schedule is, by default, configured to run only once a day at a certain time. However, you can test it manually before the regular schedule kicks off by running the monitoring job.
  1. From the destination CommCell Browser, right-click the CommServe node, and click View |, Schedules.

    The Schedule Name column displays the schedule name. The Type column displays CCM Merge.

  2. Right-click the schedule and then click Run Immediately.

    When the monitoring job is run, a CommCell Import job is initiated at the destination CommCell. The CommCell Import job sends a request to the remote CommServe to start the Export. On completion of the Export job, the data import begins at the destination CommCell. After the scheduled job completes successfully, the imported clients can be viewed from the CommCell Browser of the destination CommServe under Client Computers as "uninstalled" clients.

Preparing a GRC for Restores

Before you begin, check that you meet the following requirements to restore data from the imported clients

  • Ensure that you have configured at least one MediaAgent in the destination CommCell.
  • Check whether the new libraries exist, and if these libraries that contain data are accessible from the destination CommCell.

You can use the following methods to access the backup data from the various storage media:

Tapes

If the backup data of any imported client is available on tape, you can remove the tape from the tape library in the PodCell and then insert it into a free slot in any compatible tape library in the destination CommCell.

For more information, see  Tape Libraries - Getting Started.

Data in a Disk Library

If the backup data is available in a disk library, the data in a disk library can be restored if you associate the library with a MediaAgent on the destination CommServe. When you perform Library Mapping, you must select a MediaAgent that has access to the library and then specify the location on a destination MediaAgent where data is available.

  • If the disk library is available in a network location

    Select a MediaAgent on the destination CommCell that has access to the UNC path of the network location and specify the UNC path.

  • If the backup data on the disk library is replicated to a local MediaAgent on the destination

    Select the MediaAgent and specify the location where the mount path is replicated.

  • If you want to create two instances of the MediaAgent software on a single host

    The client name of each instance must be different.

    For example, You can create two instances MA1 and MA2 on a single host. The single host is located in the remote site. MA1 will be the MediaAgent in thesource CommCell and MA2 is the MediaAgent in the destination CommCell. Because both MediaAgents are on a single host, they can access the same mount path on the host. You can backup data to the library on the MA1 from the PodCell. When you set up monitoring, you must select MA2 from the Destination MediaAgent list for the library associated with MA1.

Related Topics

Library Mapping

Restoring Data from Imported Clients

Library Mapping

In the following figure, the Library Mapping tab includes details for all libraries and mount paths.

If any new libraries are available in a PodCell, but are not listed on the Library Mapping tab, you can click Reload Library to refresh the list. For successful restore operations, Simpana can access only those libraries that have a MediaAgent or an associated mount path.
 

  • Mag-4 is accessible on this CommCell through the common-ccm2 MediaAgent, using the UNC path (and the credentials).
  • Cloud-Library is a cloud library that is accessible through the common-ccm2 MediaAgent.
  • mag5 is a library that has not been mapped yet, and therefore not accessible on this CommCell.

    To change or assign a MediaAgent, click the appropriate Destination MediaAgent and select the MediaAgent from the drop-down list. One of the choices is Not Accessible

Restoring Data from Imported Clients

  1. Configure a GRC for restores.
  2. Complete a restore operation. For information about restore operations, see Browse and Restore.