Monitor System Recovery after Long Outage | Teradata Business Continuity Manager - Monitoring System Recovery after Long Outage - Teradata Business Continuity Manager

Teradata® Business Continuity Manager User Guide - 1.01.01

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Teradata Business Continuity Manager
Release Number
1.01.01
Published
March 2023
Language
English (United States)
Last Update
2023-03-13
dita:mapPath
qra1653979755546.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2550
lifecycle
previous
Product Category
Analytical Ecosystem

After a prolonged outage, monitor the progress of the system recovery and respond to alerts or interrupted sessions. The IDs assigned to client sessions are used to sequence requests during recovery. If a request on a session ID fails during recovery with an interrupt, it blocks later sessions in the recovery that re-use the same session ID. To avoid these problems, address the issues that appear in the recovery process immediately.

Use the interrupted session screen to monitor issues that appear during recovery. The interrupted sessions are divided into Root causes and Secondary. It is normal for sessions to become interrupted if they wait for other sessions to finish their recovery. These sessions appear as Secondary, and you need not take any action to address them.

If a request repeatedly fails to recover, you can skip the request and make the tables unrecoverable.

  1. Use one of the following methods to monitor a system recovery.
    Method Steps
    Business Continuity Manager UI Select Systems, then select a system for which you want to view the recovery status.
    bcmadmin
    bcmadmin> status;
    OR
    bcmadmin> system recovery status;