Archives of the TeradataForum

Message Posted: Mon, 18 Aug 2003 @ 15:59:28 GMT

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

Dave,

AFAIK, V2R5 is compatible with V2R4 archive data files. I have to say, that I've only tried this with individual table archives (i.e. archive from V2R4 production server, copy to V2R5 DR server), so can't really comment on database level archive/restores. Also, this was using COPY, and not a RESTORE operation to recover data, so Teradata will have created new table ID's, etc - unlikely, but there may be issues with RESTORE that I'm not aware of. I'd would be very surprised though if table archives were okay, but database level arc's weren't. Then again.......

There are definitely issues however with journals - V2R5 cannot read/process R4 permanent journal archives, and I understand that it would be a 3 month Teradata dev window to integrate this functionality to R5. (In addition, we've found that R5 can't process journals written by another R5 system, but that's another story...... ;-) )

As you point out, you can't downgrade the new systems to R4 - the R5 upgrade is a one-way path as it builds and utilises a new file system that is not backwardly compatible. Not great, and this introduces a whole load of new risks that need to be considered for migration, but the file system reconfig is essential for R5 functionality. Bit of a trade-off there, I guess.

God Luck,

Cheers,

Mark

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