Continuous Access EVA Latency Question

Question:     There used to be a maximum supported latency time when using CA Synchronous, I believe it was 50ms round trip.   Does that limitation still exist or do we now suggest it?s whether the servers/applications can handle the delay?

Answer:      That would be around 20000km or 12427.4 miles distance between the boxes or about one satellite up and down link. However, anything beyond 20ms is probably too much for most applications, meaning users will notice the increase in response time.  Initial copy time will be measured in weeks or months at 20000km and I don?t know how happy (if at all) CommandView will be while trying to manage the 2 EVAs connected to each other? The most recent versions of the HP StorageWorks Continuous Access EVA implementation guide and the HP StorageWorks Replication Solutions Manager release notes are available from he HP Business Support Center as follows:

      http://www.hp.com/support/manuals

1. Under storage, click Storage Software.

2. Under Storage Replication Software, click either HP StorageWorks Continuous Access EVA

Software or HP StorageWorks Replication Solutions Manager Software:

? For the HP StorageWorks Continuous Access EVA implementation guide, click User Guide.

? For the HP StorageWorks Replication Solutions Manager release notes, see the General

reference section.

Continuous Access documents are available from the Continuous Access Documentation page on hp.com.

  • Continuous Access EVA – Americas Pre-Sales Qualification Program link click here
  • Continuous Access EVA – Americas Pre-Sales Qualification Process click here
  • Replication Workload Profiler click here
  • Network Based Data Replication Solution w/ Cisco ONS 15500 Series DWDM Platform click here
  • Networked-Based Remote Storage Replication Solution for C-Series Fibre Channel Switches click here
WordPress Appliance - Powered by TurnKey Linux