Restoring a centrally managed collector

Follow these steps to restore a centrally managed collector.

About this task

A centrally managed collector stores its configuration data on the central manager; restore data is not required.

Procedure

  1. Use an ISO that is appropriate for your appliance.
    For example, to restore a collector, use a collector ISO; for an aggregator, use an aggregator ISO.
  2. Register the newly built collector with central manager (licenses are pooled from central manager).
  3. Make sure that your newly built appliance is at an equal or later version than the source appliance from which the backup was taken. If the appliance is at an earlier version, then apply the required GPU, bundle, and sniffer patches to bring the appliance to the same patch level as it was when the last backup was taken.
    For example, if the source appliance is a version 11.4 Guardium system that was patched with bundle 11.0p450 and sniffer patch 11.0p4020 and the new appliance was built from ISO 11.3, choose one of the following options:
    • Install 11.4 GPU. Then, apply appliance bundle version 11.0p450 or later and sniffer patch version 11.0p4020 or later.

      Or,

    • Install GPU version 11.5 or later.
  4. Use the restore backup CLI command to restore the data backup.
    This step might be optional if the environment includes an aggregator and data from the collector also exists on the aggregator. (You do not need to restore the configuration backup because the definitions are pooled from the central manager.)
    For more information, see Before you restore your Guardium system.
  5. Use the store system shared secretCLI command to set the shared secret to enable communication with central manager. The shared secret encrypts communication of the appliance with central manager.
  6. Optional: Restore archive files for missing days, as needed. This step is not required if you are not restoring data backup.