command at the arc controller and when the remote controller 16 may accept the write data the arc controller may determine if this delay exceeds a delay threshold the delay may be determined by tracking the resources that are available for example remote controller 16 may be able to accept the write data when the arc controller 20 tracks the resources that are available at the remote controller 16 versus the resources being used for writes that are in progress the resources available may be established as part of the initialization process for the communications between remote controller 16 and arc controller 20 resources are consumed by writes that are in progress from point 58 when arc buffers the write data and until the arc controller receives acknowledgement that the write has completed at the remote controller 16 alternatively the delay may be determined by the delays experienced as the result of preceding accesses in one embodiment the arc controller 20 may use the threshold timer 28 to determine whether consecutive multiple write commands each have a delay over a delay threshold 24 and whether the cumulative delay is beyond a threshold period 26 in case of a disruption of communication between primary arc controller 20 and remote controller 16 prolonged periods of increased latency may be detected in one embodiment to avoid delay or disruption of service to host applications the arc controller 20 may suppress release of the data from the arc buffer 22 to the remote controller 16 the primary controller 12 may not write the data to the primary storage 14 until the arc.