.

Teradata Disaster Recovery

Teradata Business Continuity—recovery solutions to mitigate catastrophic events.

The unexpected loss of a Teradata system could mean more than just lost revenues; business reputation, decreased customer retention, lost business intelligence, reduced employee morale, productivity issues, and legal entanglements are very real possibilities.

The default Teradata DR Option, ordering a replacement system when a disaster occurs, has a Recovery Time Objective (RTO) of 6-8 weeks for full data recovery and access. Teradata also offers a full range of disaster recovery solution, from low cost (RTO of Days) to high availability for planned and unplanned downtime (RTO of Hours). What’s the potential ROI and business impact if you lose critical data? Is that a risk you’re willing to take?

Three Steps to Determine Your Best Disaster Recovery Solution

  1. Quantify business impact of losing access to business-critical data on a Teradata system.
  2. Determine how long—weeks, days, hours—you can operate without your critical data. This number, known as recovery time objective (RTO), is the primary consideration for selecting the best option.
  3. Contact your Teradata representative to understand your Teradata recovery options and determine the right disaster recovery solution for your organization.

Teradata Disaster Recovery Solutions

The business function impact determines the RTO and which of the three (3) non-overlapping Teradata Recovery Options is right for you. Each option is available with a variety of potential solutions. The option you select is based on your understanding of the potential business impact and the level of risk you find acceptable.

Option 1: Post-Disaster (RTO of Weeks)

Our default disaster recovery option consists of ordering a replacement system after a disaster occurs. We recommend disaster recovery planning to expedite the process and ensure all data will be recovered.

Option 2: Shared Resources (RTO of Days)

Shared Resources includes using Teradata resources at the Teradata Recovery Center, or using customer resources to recover on an in-house disaster recovery system. For customers performing their own DR we recommend an In-house DR Consulting engagement to ensure Teradata recovery steps are identified, planned, and tested.

Option 3: Dual Systems (RTO of Hours)

Dual Systems require a second production system with the same critical data on both systems. This option is appropriate for organizations with a requirement for high availability, with secondary emphasis on performance continuity and recoverability. Teradata Cloud uses data synchronization to meet customer requirements.

Business Function Impact Recovery Time
Objective
Teradata Recovery
Options
Solutions Advantages
IMPORTANT
“Supports” the business
Weeks Post-Disaster (1) DR Planning Leverage forward
SIGNIFICANT
“Controls” the business
Days Shared Resources (2) Teradata Recovery Center In-house DR Cost/best practices RTO/control
CRITICAL
“Runs” the business
Hours/Minutes
(Availability)
Dual Systems (3) Two production systems
Teradata Cloud
RTO/data
Data/users

 

Industry-standard Teradata Recovery Center

The Teradata Recovery Center provides an enterprise-class recovery system that matches production release levels and is ready for data restoration. The recovery system may include any Teradata certified release levels, as well as any customer specific hardening or encryption. Customer focus is on data and user access to restore business critical functions, while a Teradata Recovery Specialist assists with all required tasks to ensure the recovery system matches the production environment prior to user access. An annual test will validate the recovery process.

Teradata DR Options based on recovery time objective (RTO)

  WEEKS DAYS HOURS
Benefits of Teradata DR Post-Disaster   Dual Systems
Recovery time objective (RTO) based on business impact 6-8 Weeks 48-72 Hours 7-10 Days Hours
Access to recovery system when needed No YES YES YES
Recovery system matches production release levels N/A YES YES YES, with exceptions
Process during a disaster event Order new system Declare disaster Declare disaster Ready to use
Recovery location and recovery system provided No YES YES YES
Recovery system pre-event preparation No YES-BUILD service YES-BUILD service YES
All Teradata recovery services and best practices included No YES YES YES
Method of data recovery Data restoration Data restoration Data restoration Data synchronization
Data restoration data capacity No All critical data Sample data All data
Recovery system ready when needed No 24 hours SLA 48 hours SLA YES
Network and network device required No YES YES YES
Annual testing No YES No YES
Availability capability No No No YES
Requires special software and services No No No YES

 

Teradata Business Continuity Solution in the Cloud

Teradata is championing business continuity solutions (BCS) in the Cloud. Teradata BCS implementations for the cloud address three specific areas for on-premises production systems: Data Protection, Recoverability, and Availability.

  • Data Protection may use data replication over a network for a secondary copy of critical data.
  • Recoverability for disaster recovery capability in the event of a catastrophic event.
  • Availability will use the Teradata Cloud with data synchronization to a second system for planned and unplanned downtime.

For additional information contact Mike Mota, Senior Business Continuity Partner.

Contact Us

Have a question or want additional information on Teradata Disaster Recovery Solutions?

Email Us