Replication benefits

Content Platform Tenant Management Help

Version
9.7.x
File Size
4269 KB
Audience
anonymous
Part Number
MK-95HCPH002-19

Replication has several purposes:

  • 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 enterprise has several satellite offices, an HCP system at a central facility can consolidate data from the HCP systems at those outlying locations.
  • 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. HCP tries to do this only if:
    • The namespace that contains the object is being replicated.
    • The namespace has the read-from-remote-system feature enabled.
    • The object has already been replicated. Users can check object metadata to determine whether an object has been replicated.
  • If a system in a replication topology is unavailable, requests to that system that come through the REST, S3 compatible API can be automatically serviced by another system in the topology without the client needing to modify the target URL. The other system can service a request only if:
    • The namespace named in the URL is replicated on the other system
    • The namespace named in the URL is configured to accept requests redirected from other HCP systems
    • The HCP systems involved use DNS for system addressing