How to recover if the HVR Hub fails?

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #8804
    Simon Faas
    Keymaster

    Depending on the type of failure and/or whether the hub database/machine is part of a cluster (e.g. Oracle RAC) the following actions need to be performed:

    When the hub database is a clustered database (e.g. Oracle RAC) the hub will fail over to another node and HVR should recover automatically. This requires that HVR is set-up properly for cluster fail-over, but this is described elsewhere. An error message will written to the log file which will then be reported by an HVRMaint email as well.

    If the hub comes back without any loss of data in either in the database (HVR Catalog tables) or inside the $HVR_CONFIG directory, HVR will recover automatically. An error message will written to the log file which will then be reported by an HVRMaint email as well.

    If the hub database is lost, manual steps are necessary to recover:

    • (Re)Create a hub database.
    • Re-load the channel definitions & location configuration from a backed-up XML catalog document using hvrcatalogimport / HVRGUI’s Catalog Import.
    • Run HVR Initialize for “Scripts and Jobs” only to recreate the replication jobs
    • Start the replication jobs

    If the $HVR_CONFIG/router directory is lost, HVR will not be able to recover automatically. Manual steps are necessary:

    • Run HVR Initialize to recreate all replication objects
    • Perform an Online Refresh to re-sync source and target database.
    • After the refresh has completed successfully the replication jobs can be started.

    If the complete hub machine is lost a new machine needs to be create / chosen to run the hub installation. The following steps are necessary:

    • Follow the installation steps to install the HVR binaries etc.
    • (Re)Create a hub database.
    • Re-load the channel definitions & location configuration from a backed-up XML catalog document using hvrcatalogimport / HVRGUI’s Catalog Import.
    • Run HVR Initialize to recreate all replication objects
    • Perform an Online Refresh to re-sync source and target database.
    • After the refresh has completed successfully the replication jobs can be started.

    In some situations (when DBMS log files are still available) an alternative to the Online Refresh is to use a HVR Initialize with a capture rewind to a time before the incident. This may result in some overlap in the changes that are replicated. Adding Integrate /Resilience to the channel can be used to overcome this.

    #22116
    Sachin Khanna
    Participant

    Not working for me!

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.

© 2020 HVR

Test drive Contact us