Thank you.
Sent from my iPhone
> On May 22, 2021, at 12:39 PM, Radoslaw Skorupka
> wrote:
>
> Two things to consider:
> 1. Distance => delay. For long distances it means synchronous copy is not
> applicable. It can be asynchronous copy or some kind of "fuzzy" copy like
> PPRC-XD or SRDF Ada
Two things to consider:
1. Distance => delay. For long distances it means synchronous copy is
not applicable. It can be asynchronous copy or some kind of "fuzzy" copy
like PPRC-XD or SRDF Adaptive Copy.
2. Bandwidth and I/O rate. The more I/O the higher bandwidth is needed
for replication. Te
Thank you.
Sent from my iPhone
> On May 21, 2021, at 7:39 PM, Mike Schwab wrote:
>
> Async mirroring would be possible. The bad / good thing is your
> source dasd track could be updated several times between passes. What
> the controller does is look at the updated track table, 1 bit per
> t
Async mirroring would be possible. The bad / good thing is your
source dasd track could be updated several times between passes. What
the controller does is look at the updated track table, 1 bit per
track, copies the tracks in order, resetting the bits when read and
acknowledged, then proceeds t
Hello folks,
I am trying to find out what we could consider to be a "safe" maximum
distance for mirroring DASD from one site to another.
We have a situation where site #1 will be thousands (9,000) of miles away
from site #2 (across the ocean.
I realize there would be a great deal of latency involv
