The answer is no. If there is crash on the system, all the requests tracks to be re sync are written to bitmap file or send to PC for request Sync. So, if the system crash, or the disk crash, the PC or the MF bitmap may have the tracks which need to be SYNC.
If the disk return to life, the MFNetDisk will re sync the tracks again. If the disk failed, MFNetDisk will not be able to re sync pending re sync requests. But if the disk crash, the multi volume DSN of group of DSN which must be sync will not be available because one of its disk is not operational. So, part of the DSNs will be recovered and the crashed disk will not and I think that in this case if you do not use sync remote mirroring, you will have to restore the DSN from backup or from loging if exist. So, better if you have the money to use remote mirroring which doing the sync mirroring and multi-volume consistency which may cost some money and of course with delay in the IO performance. If you want to have free product for remote mirroring but in case of DR to be async for few seconds of IO operation, then you can try the free MFNetDisk. At least I can say that if you can not afford remote mirroring, better to use MFNetDIsk. MFNetDIsk can allow to take picture of the disks. You can let in specific time to stop the update for seconds and let MFNetDIsk finish its re sync for all its disk data to this time. Then you can stop the update of the disks to MFNetDisk and in case of crash you have all the disks SYNC to the specific time. On Tue, Dec 13, 2011 at 5:17 PM, Ron Hawkins <[email protected]>wrote: > Are you supporting multi-volume consistency? > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of > > shai hess > > Sent: Monday, December 12, 2011 9:47 PM > > To: [email protected] > > Subject: [IBM-MAIN] Fwd: case from DR in France. > > > > ---------- Forwarded message ---------- > > From: Shai Hess <[email protected]> > > Date: Tue, Dec 13, 2011 at 7:45 AM > > Subject: case from DR in France. > > To: [email protected] > > > > > > ** > > HI, > > > > Two days ago, I receive email with the title "big problem for me ! help > !" > > from customer from France name Will_fashion from France. > > The native host real disks were crashed. > > > > Luckily, the user use the replication MFNetDisk for its MF real disks. > > > > After few emails to me, the native disks were recovered using MFNetDisk > > replication feature which enable the user to mirror the host real disks > > to PC hard disks without and performance reduction in MF nor delay to the > > real disks in the MF. > > > > I just put the last words of the customer after the disks were > recovered. > > > > "thanks a lot for your FREE product and your work (i hope you can earn > > much money with it you deserve) > > I talk about your product in my job soon". > > > > So, if you like to have DR and disks backup always without MF performance > > issue nor real disk performance reduction nor delay, and to pay zero > money > > for this product, it is time to use MFNetDisk replication feature. > > > > Thanks, > > God bless you. > > Shai Hess, MFNetDisk product. > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: GET IBM-MAIN INFO > > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
