John Ticic wrote:
--- snip ---
In my case ,I run a // sysplex on 2 distant sites
I have protected my environment against hardware failure by PPRCing
(synchronous) the entire siteA DASD bay on siteB bay .
If a plane strikes ( forget the laser beam :-) ) one of my bay,i am OK,i
still have my site B with proper data because device end comes back only
once secondary is written .
--- snip ---
A disaster rarely happens in an instant, most likely it is spread out over
some finite time.
It could be that one of your DASD boxes has failed in site A, but others in
site A are still working. PPRC (I'm only talking about native PPRC) for the
working DASD will continue to transfer the data to site B.
Is this what you really want?
That's why proper planning is important in DR scenario.
Sometimes it is necessary to put all the data on one DASD controller,
however not always. You can also use HDS boxes, which has a feature to
"coordinate" PPRC consistency across boxes.
You can divide your data (depend on application(s)) across controllers
to have consistent copy, even in rolling disaster scenario.
You can use GDPS, asynchronous copy, ....
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
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
