Abstract:
ABSTRACT OF THE DISCLOSURE Write order fidelity (WOF) is maintained for totally-active implementations wherein a plurality of access nodes at geographically separated sites can concurrently read and/or write data in a "totally active" fashion on a distributed data system. From the hosts' perspective at diverse geographic locations, a synchronous, cache-coherent view of data is provided. Data transfer is asynchronous. A time ordered data image is created and maintained so operations can be restarted after a partial system failure that causes loss of data not yet asynchronously transferred across the network, but that has been write-acknowledged to the originating host. Time ordered asynchronous data transfer is implemented as a pipeline of changes that reflect contributions from all nodes. WOF also improves network performance and lowers bandwidth consumption. Extensions can provide, in a totally-active context, features such as point-in-time snapshots, time firewalls, on-demand backend storage allocation, synchronous / asynchronous distribution of data, and continuous data protection.
Abstract:
ABSTRACT OF THE DISCLOSURE Write order fidelity (WOF) is maintained for totally-active implementations wherein a plurality of access nodes at geographically separated sites can concurrently read and/or write data in a "totally active" fashion on a distributed data system. From the hosts' perspective at diverse geographic locations, a synchronous, cache-coherent view of data is provided. Data transfer is asynchronous. A time ordered data image is created and maintained so operations can be restarted after a partial system failure that causes loss of data not yet asynchronously transferred across the network, but that has been write-acknowledged to the originating host. Time ordered asynchronous data transfer is implemented as a pipeline of changes that reflect contributions from all nodes. WOF also improves network performance and lowers bandwidth consumption. Extensions can provide, in a totally-active context, features such as point-in-time snapshots, time firewalls, on-demand backend storage allocation, synchronous / asynchronous distribution of data, and continuous data protection.
Abstract:
Network data storage systems and methods allow computers reading and writing data at a plurality of data centers separated by, potentially, large distances to replicate data between sites such that the data is protected from failures, including complete Site failures, while not allowing network latency to significantly impede the performance of read or wπte operations. Continued access to all data is provided even after a single failure of any component of the system or after any complete failure of all equipment regardless of geographic location. Wπte data is replicated synchronously from Active Sites, e g., sites where servers are wπting data to storage resources, to Protection Sites located sufficiently close to Active Sites such that network latency will not significantly impact performance, but sufficiently far apart such that a regional disaster is unlikely to affect both sites. Write data is then asynchronously copied to Active Sites, possibly at distant sites.
Abstract:
Network data storage systems and methods allow computers reading and writing data at a plurality of data centers separated by, potentially, large distances to replicate data between sites such that the data is protected from failures, including complete Site failures, while not allowing network latency to significantly impede the performance of read or write operations. Continued access to all data is provided even after a single failure of any component of the system or after any complete failure of all equipment located at any single geographic region or any failure that isolates access to any single geographic region. Write data is replicated synchronously from Active Sites, e.g., sites where servers are writing data to storage resources, to Protection Sites located sufficiently close to Active Sites such that network latency will not significantly impact performance, but sufficiently far apart such that a regional disaster is unlikely to affect both sites. Write data is then asynchronously copied to other sites, potentially including one or more Active sites, located at greater distances.