Archives of the TeradataForum

Message Posted: Wed, 09 Jul 2003 @ 09:57:49 GMT

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

<-- Anonymously Posted: Tuesday, July 08, 2003 20:42 -->

I have been observed in the Teradata community that since Teradata quite often gets relegated to do the DSS work, managements tend not to spend money on Business Continuity/Disaster Recovery systems and would like to allocate the same money for building BC solutions for OLTP systems, coz if they stop their functioning will stop.

Unlike SQL Server and Oracle and some other Dabatabases, wherein you have Linked Servers, Teradata doesn't have the same capability as of now. Oracle's idea of moving physical disk spaces is a farce as the BC site and Production Site needs to be far away from each other and there is time involved in transporting.

Archiving and Restoring is an option, e.g Cluster Backups - but they work decently only if the configuration is the same. And the BC site usually starts with less systems than Production.

Using ETL tools is an option if they are CLI integrated.

Fast Exports/MLoads using Named Pipes is an option, but with only 15 jobs at a time and having locks most of the time, makes this option ineffective.

What is the best way to have a managed Disaster Recovery Site?

Thanks

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