The current snapmirror will finish and then pick up again when the next scheduled transfer is supposed to happen.<div><br></div><div>i.e.: mirror takes from 2pm-310pm (maybe due to a slow wan). If the schedule is for every hour, then the 3pm will be skipped</div>

<div>and it will resume at 4pm</div><div><br></div><div>You can always look to silverpeak or riverbed to help speed up transfers over a WAN.</div><div><br clear="all">--tmac<br>         Tim McCarthy<br>     Principal Consultant<br>

<br>  RedHat Certified Engineer<br>   804006984323821 (RHEL4)<br>   805007643429572 (RHEL5)<br>
<br><br><div class="gmail_quote">On Wed, Mar 23, 2011 at 12:48 PM, Timothy Hollingworth <span dir="ltr">&lt;<a href="mailto:thollingsworth@eplus.com">thollingsworth@eplus.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

So if a source/destination pair is doing a snapmirror update and the current update is not complete before a new update is requested, what is the behavior? Does it queue the second snapmirror update and just update it when the first completes?<br>


<br>
I understand the behavior when updates are done by the scheduler on the array itself as per snapmirror.conf. In this case it queues the updates but only to a maximum of three.<br>
<br>
&quot;If an update is in progress when another is scheduled to<br>
occur, SnapMirror starts another transfer as soon as the<br>
transfer is complete. However, if three updates pass while<br>
the current transfer is in progress, SnapMirror does only<br>
one more update; it does not go back and run updates<br>
that have been made obsolete by those scheduled later.&quot;<br>
<br>
But I&#39;m not talking updates initiated by the scheduler on the array itself.<br>
<br>
I&#39;m really asking about something like SME performing a backup and requesting an update. The snapmirror update here is functionally equivalent to issuing a snapmirror update command manually. Suppose the mirror does not complete before the next backup and subsequent update request is made (or snapmirror update command issued manually). What if the rate of data change exceeds the ability of network to complete the mirror or if the WAN link to the DR site is just too darn slow? Do the updates queue on the destination and snapshots build up on the source indefinitely? Or do manual or snapmanager initiated updates follow the &quot;queue to three and then give up&quot; rule above?<br>


<br>
Anyone know?<br>
<br>
<br>
Timothy L. Hollingworth<br>
Sr. Network Engineer<br>
ePlus Technology, inc. <br>
511 Davis Drive<br>
Suite 350<br>
Morrisville, NC 27560<br>
<a href="tel:678.462.6698">678.462.6698</a> (Direct/Cell)<br>
<a href="mailto:thollingworth@eplus.com">thollingworth@eplus.com</a><br>
 <br>
<a href="http://www.eplus.com" target="_blank">www.eplus.com</a><br>
<br>
 <br>
The information contained in this electronic transmission and any attachments hereto may be considered proprietary and confidential.  Unauthorized distribution of this material to anyone other than the addressed is prohibited.  Any disclosure, distribution or use of this transmission for any reason other than their intended purpose is prohibited.<br>


<br>
</blockquote></div><br></div>