|
Works well - but this can miss critical objects such as data areas which are not capured by journalled changes, and files which aren't journalled, but are vital. Best get a few business users to go through the motions on the B machine to see if anything bombs out in normal use. Again, I've seen Lakeview's MIMIX/400 product manages this process very well. Another consideration might be to protect any links between machines by changing authorities to stop developers from also sending objects from the A machine to the B machine - this risks them bypassing any change control steps - e.g. they could send objects from test libs on A to live libs on B. (I was very careful not to call them AS/400 & BS/400.) Anyway, if you are restoring, not transmitting, this won't apply. Fiona
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.