Synchronous replication not dropped to asynchronous replication to have VTVs consistency in the camp
A customer of mine want to avoid that the job synchronous replication is dropped to asynchronous replication.
This because they prefer to stop the write activity in the primary site instead of to don't have the exact copy of the VTVs in the campus site.
We have explored some solutions but the only one that seems to be right is to cancel job before that the replication is dropped from synch to asynch.
What happens if I set the value of MIH 35 minutes?
What happens when the value is reached? Only IOS071I Missing Channel and Device End message or the job fails??
What happens if I set the value of MIH 35 minutes?
What happens when the value is reached? Only IOS071I Missing Channel and Device End message or the job fails??
0