Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 11 Jul 2011 @ 08:53:19 GMT


     
  <Prev Next>   <<First <Prev Next> Last>>  


Subj:   Re: Teradata Disaster Recovery setup
 
From:   Yong Boon

Agreed with Barb,

DR should be planned at the IT architecture level down to the Teradata level, and driven by the Business DR requirements.

1. Which critical applications should have the DR capabilities (hence decide the databases to be recovered during DR, and confine the scope of DR)

2. RTO (Recovery Time Objective) - What's the time the DR site need to be brought up?

3. RPO (Recovery Point Objective) - What's the latest data available in the DR site once brought up.

4. Performance requirement for each critical applications, and ranking.


From the requirement, work with your IT/BI architect to review if your existing IT architecture supports the requirement (from the upstream source system, ETL system like datastage, informatica, and the downstream BI, SAS, data mart.) and decide the RTO and RPO, databases/users (space) requirement for Teradata.

Based on this, determine if your existing Teradata Infrastructure support the DR requirement of the business, and consider with upstream/downstream DR to design your Teradata DR strategy (Dual Active, Data Mover, Tape/Virtual Disk solution) with upstream/downstream, and get the budget from the business.

Also, plan for the DNS/IP hosts, password procedure for the Teradata DR, with upstream/downstream applications. Above all, from the databases/users with DR requirement plan for the DR server capacity (with the assumption if the DR site will be run for a month or two before the main site recovery).

Perform the performance/benchmarking on the Teradata DR with the critical applications/reports, and plan the DR site capacity upgrade accordingly (in bank scenario, there is regulatory report requirements which delay might impose penalty. If the DR site is up, but the report might take longer time to generate and breach the timeline due to the CPU capacity).

Last, and which is missing from most DR plans, is the plan to switch the DR site back to the main site.

DR without testing is as good as No DR.


Hope this help.

YB



     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023