Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Wed, 29 Dec 2004 @ 13:42:04 GMT


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


Subj:   Fallback, Journaling or Both
 
From:   Coffing Christopher L

A-Team

So I'm minding my own business supporting a 36-node 24 TB system (having the time of my life I might add!) and my management team comes to me about adding a layer or two of data protection for the warehouse.

Like any large system we are loading almost 24x7 with a 4 hour backup window. We maintain an Archive area on the production system that stores all of our source data (as is, with no transformation) so we can recover quickly if we loose production tables and we do not have a good backup for oooohh let's say 3-months (yeah I know, #@%! happens!)

So after a few incidents where we got bit by Murphy's law, the management team has gotten a little pressure to decrease any additional data lose incidents. So they come to me.

Currently we do not have Fallback or Permanent Journals on any of the tables. Permspace is not an issue, we have plenty to work with...

Oh right, my question....

In an effort to maintain performance, minimize administrative overhead and maximize data protection do we want to add fallback to our production tables and also use Journaling?

I realize there are different uses for both approaches. I am most interested in the real-world gotcha's that you have experienced and how you are using these features.


Please share your findings.

Chris Coffing
Air Force Knowledge Services (AFKS)
Lead DBA Operations & Support
Teradata Certified Master



     
  <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: 27 Dec 2016