We are a mainframe shop, and some time ago, when we converted from DMX2 to DMX3 hardware EMC informed us that we would need to convert to Timefinder/Clone since our target devices would be RAID5.
We have recently learned that when performing a Clone1 to R2 that a full push of all tracks will always be invoked … which is not acceptable .. we need to be able to fallback with incremental restores (Clone1 to R2, R2 to R1, R1 to Standard should all be incremental if source site is still intact as in a power outage). EMC is now telling us that we will need to convert to Timefinder/Mirror clone emulation in order to have this capability … and that a full push of all data will be necessary to perform this conversion.
1. Does this sound correct?
2. With Timefinder/Mirror clone emulation can we be IPLed from a Clone1 image and concurrently invoke a restore from Clone1 to R2? (The manual seems to indicate that the volumes will be ‘not ready’ in this situation). If so, will the resulting R2 image be ‘consistent’?
3. Currently with Timefinder/Clone we do not invoke R2 to Clone1 remotely from the source site LPAR but instead invoke this process from an LPAR at the DR site (where the R2 and Clone1 images reside) since execution time is three times longer if invoked ‘over the wire’ from the production DMX3 site (EMC claims it has something to do with passing all of the commands back and forth). Should we expect to experience the same elongated elapsed times for Timefinder/Mirror clone emulation R2 to Clone1 if we try and invoke it from the production DMX3 site?
4. Any other considerations we should be aware of if we convert from Timefinder/Clone to Timefinder/Mirror clone emulation?