When a planned or unplanned outage is complete, a DBA can initiate a full system recovery to bring the system back to the active state by re-running all the requests sent in managed sessions. The time to recover depends on factors such as:
- Size of the Teradata system
- Concurrency of the workloads
In a workload with numerous write requests, and with little or no read traffic, the time to recover a system may be longer and may equal the time of the outage. For example, the client workload driving the active system at the full throughput while the recovery system is trying to catch up.
While the system is recovering, Business Continuity Manager recovery log and data file system provide the recovering system extra capacity to sync. The log and data files store incoming write requests at the top of the recovery queue as the recovering system is re-running the requests from the bottom of the queue.