Ron - 

We're not really doing a remote copy.  Logically, we mirror 1 half of the 
box to the other half of the same box.  We are asynchronous for most of 
the day and only swap to synchronous mode a few minutes before we're ready 
to do our backups, break the pairs once they are synchronous, and then 
start the backups on the offline mirrors.  Once the backup is complete, we 
re-establish pairs asynchronously and wait for the next cycle.

In the past, we would take full volume backups for DR.  These backups 
would run over a period of several hours while batch was up and running 
leaving us with loads of inconsistencies.  Then we restore these backups 
at DR, do what clean-up we could, and then applications would start their 
recoveries.

With our current method, we achieve very nearly synchronous backup.  I 
won't quibble about 'near zero', but I can say that to date when we 
restore at DR, we've not seen any file problems.  We still have instances 
where applications was running and our flashcopy was taken in the middle 
of their batch cycle, but it's much cleaner than anything we've had before 
and doesn't involve the extra costs of a remote site. 

ddk

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Then why use asynchronous remote copy software and skip just about all of 
the performance hit? 

The ONLY reason for using Synchronous remote copy is when you need zero 
data loss on the remote side, which is not your requirement.

Note that zero data loss with synchronous remote copy does not occur by 
default. Most synchronous remote copy sites only provide "near zero" data
loss, which always makes me wonder what the point of synchronous is in the 
first place.

Ron
**************************************************************************************
This e-mail message and all attachments transmitted with it may contain legally 
privileged and/or confidential information intended solely for the use of the 
addressee(s). If the reader of this message is not the intended recipient, you 
are hereby notified that any reading, dissemination, distribution, copying, 
forwarding or other use of this message or its attachments is strictly 
prohibited. If you have received this message in error, please notify the 
sender immediately and delete this message and all copies and backups thereof.

Thank you.
**************************************************************************************

----------------------------------------------------------------------
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

Reply via email to