instead of using a unix cp, perhaps you could use uvbackup piped through a uvrestore? Slower than a cp, but there will be no corruped files or odd index interactions. I don't know if uvbackup has provisions for re-creating indexes though.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of HENDERSON MIKE, MR Sent: Thursday, May 12, 2005 3:18 PM To: [email protected] Subject: RE: [U2] Unix copying Universe files {Unclassified} Charles, > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Stevenson, Charles > Sent: Friday, 13 May 2005 04:49 > To: [email protected] > Subject: RE: [U2] Unix copying Universe files > > Just to pick nits, if you use Transaction Logging, the txlg > number is in the file header, too. > Subsequent updates of the cloned file can goof up your logs. Now that's interesting. I know how to fix up the Secondary Index pointers (with SET.INDEX) And how to fix up Distributed Files (by ED &PARTFILES& and REBUILD.DF) But how would I fix up the transaction log numbers? Thanks Mike > Is there a similar concern with data replication? > > Distributed files also have pathnames buried in them. > The information contained in this Internet Email message is intended for the addressee only and may contain privileged information, but not necessarily the official views or opinions of the New Zealand Defence Force. If you are not the intended recipient you must not use, disclose, copy or distribute this message or the information in it. If you have received this message in error, please Email or telephone the sender immediately. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
