RE: chunk transplant

You would need the primary offline for the duration of the copy for this to work. If it was online, transactions could make the instance inconsistent on the backup server and hence not able to be used. We have a client that does an archive on their primary server each night and later in the night uses an automated restore to restore that tape onto their backup server. This is reliable and uses supported processes. They use the secondary server for reporting and development during the day. MW -----Original Message----- From: owner-informix-list@iiug.iiug.org [mailto:owner-informix-list@iiug.iiug.org]On Behalf Of Robert Carts Sent: Wednesday, January 17, 2001 2:09 AM To: informix-list@iiug.org Subject: chunk transplant We have been investigating ways to keep data current on a local and identical backup server. We are aware of IER and HDR. My boss suggested that we keep a mirrored chunk on a cross mounted drive that resides on the backup server. Then in the event of a failure of the primary server, bring the backup server online using the primary servers chunk. I skeptically attempted this and it worked! The conditions are: The schemas, database spaces, chunk size and number of chunks are the same on both servers. The chunks use cooked files. The databases are created in rootdbs and the tables, indexes are created in dedicated chunks. The chunks from the primary server are copied over the backup server chunk files before the backup instance is brought online. We are using 9.2uc3 on solaris 2.7. Question: Under what conditions would this not work (within the conditions above) ? I either need to demonstrate why not to use the technique or make it work reliably? Thanks, Bob Carts