Disable Automatic Recovery| Teradata Business Continuity Manager - Temporarily Disabling Automatic Recovery - Teradata Business Continuity Manager

Teradata® Business Continuity Manager Monitoring and Management Guide
Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Product
Teradata Business Continuity Manager
Release Number
1.xx, 2.xx
Published
January 2024
ft:locale
en-US
ft:lastEdition
2024-02-06
dita:mapPath
wmz1639626084071.ditamap
dita:ditavalPath
ft:empty
dita:id
wmz1639626084071
Product Category
Analytical Ecosystem
When a system or a large number of objects are interrupted, it may become a strain on Business Continuity Manager and managed system resources. To allow adequate time to analyze and correct any issues on the Teradata systems, temporarily disable automatic recovery. When the issues are resolved, re-enable automatic recovery.
  1. At bcmadmin, run the following command: 
    CONFIG LIST KEY RECOVERYINTERVAL;
    Business Continuity Manager returns the sequencer system information, including the default recovery interval of 300 seconds and a custom recovery interval if applicable. For example:
    Sequencer System Defaults
-------------------------

RecoveryInterval: 300

Sequencer User Set Values
-------------------------

RecoveryInterval: 600

    In this example, Business Continuity Manager is using a custom recovery interval of 600 seconds.

    When you initiate recovery, Business Continuity Manager sets the custom recovery interval back to the default.

  2. If you are using a custom recovery interval, make a note of the value so you can reset the value after recovery.
  3. At bcmadmin, run the following command to disable automatic recovery:
    CONFIG UPDATE SEQUENCER RecoveryInterval 0 REASON 'Disabled Automatic Recovery for incident _______';
  4. At bcmadmin, run the following command to confirm a recovery is not in progress:
    SYSTEM RECOVERY STATUS;
  5. At bcmadmin, run the following command to make sure no objects on the system are being restored:
    STATUS;
  6. At bcmadmin, run the following command to determine the cause of the mass interrupt event, then fix the errors:
    SESSION LIST INTERRUPTED;
    If you cannot fix the issues, contact Teradata Services for assistance before proceeding with the recovery.
  7. At bcmadmin, run the following command to start recovery for the specified system:
    SYSTEM RECOVER <systemId>;
  8. At bcmadmin, run the following command periodically to check recovery status:
    SYSTEM RECOVERY STATUS;
    When recovery is complete, Business Continuity Manager returns the status recovery not in progress.
  9. At bcmadmin, run the following command after recovery is complete to check for new interrupts:
    SESSION LIST INTERRUPTED;
  10. Do one of the following:
    Recovery Status Action
    No new interrupts
    1. At bcmadmin, run one of the following commands to restore automatic recovery:
      • If you are using a custom recovery interval: 
        CONFIG UPDATE SEQUENCER RECOVERYINTERVAL <recovery interval>;

        This restores automatic recovery to the custom recovery interval specified.

      • If you are using the default recovery interval: 
        CONFIG RESET SEQUENCER SEQUENCER RECOVERYINTERVAL;

        This restores automatic recovery to the default recovery interval of 300 seconds.
    New errors
    1. Fix the issues, then repeat the recovery process.
      If you cannot fix the issues, contact Teradata Services for assistance before proceeding with another recovery attempt.