Archives of the TeradataForum
Message Posted: Thu, 11 May 2006 @ 15:34:33 GMT
<-- Anonymously Posted: Thursday, May 11, 2006 11:21 -->
We are looking for some advice from anyone out there who purchased two machines (running v2r5.1.2), comprising of a 'primary' production server and a 'secondary' machine, for use in a disaster situation.
We believed that it was possible to keep the two machines 'in sync' by backing up our data post-load (using Netvault) and restoring to the other machine as the backups finish and the tapes are available. We are happy enough that any tables that are dropped and recreated in batch would be ok in that we would first drop the database from the secondary machine before doing an ARCMAIN COPY to 'refresh' the secondary servers' version of this database.
We do not wish to pursue either (what NCR term) the 'Dual-Load' of both machines for batch nor the 'Dual- Active' option due to various limitations of our setup.
My question is how can we apply daily 'admin' changes (new users/authority changes/tables created,dropped,etc) from the primary production system to the secondary system to keep the two machines' DBCs in sync?
There doesn't appear to be an NCR product to do this but they have hinted that other sites do this themselves.
We thought it might be possible to setup triggers/stored procs to do this and we have some other ideas, but would be very interested in hearing how any other sites facing this situation maintain DBC in this situation, as well as any problems/issues encountered along the way.
Any help would be much appreciated.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|