Replication

Replication is a process that supports configurations in which selected tenants and containers are maintained on two or more HCP systems and the objects in those containers are managed across those systems. This cross-system management helps ensure that data is well-protected against the unavailability or catastrophic failure of a system.

A replication topology is a configuration of HCP systems that are related to each other through replication. Typically, the systems in a replication topology are in separate geographic locations and are connected by a high-speed wide area network. This arrangement provides geographically distributed data protection (called geo-protection).

You can read from containers on all systems where those containers are replicated. The replication topology, which is configured at the system level, determines the systems on which you can write to containers.

Replication has several purposes, including:

If a system in a replication topology becomes unavailable (for example, due to network issues), another system in the topology can provide continued data availability.

If a system in a replication topology suffers irreparable damage, another system in the topology can serve as a source for disaster recovery.

If multiple HCP systems are widely separated geographically, each system may be able to provide faster data access for some applications than the other systems can, depending on where the applications are running.

If an object cannot be read from one system in a replication topology (for example, because a node is unavailable), HCP can try to read it from another system in the topology. Whether HCP tries to do this depends on the container configuration.

If a system in a replication topology is unavailable, HTTP requests to that system can be automatically serviced by another system in the topology. Whether HCP tries to do this depends on the container configuration.

© 2015, 2020 Hitachi Vantara LLC. All rights reserved.