{
  "id": "durability-ha",
  "title": "Durability and high availability",
  "url": "https://redis.io/docs/latest/operate/rs/7.8/databases/durability-ha/",
  "summary": "Overview of Redis Enterprise durability features such as replication, clustering, and rack-zone awareness.",
  "content": "Redis Enterprise Software comes with several features that make your data more durable and accessible. The following features can help protect your data in cases of failures or outages and help keep your data available when you need it.\n\n## Replication\n\nWhen you [replicate your database](), each database instance (primary shard) is copied to a replica shard. When a primary shard fails, the cluster automatically promotes a replica shard to primary.\n\n## Clustering\n\n[Clustering]() (or sharding) breaks your database into individual instances (shards) and spreads them across several nodes. Clustering lets you add resources to your cluster to scale your database and prevents node failures from causing availability loss.\n\n## Database persistence\n\n[Database persistence]() gives your database durability against process or server failures by saving data to disk at set intervals.\n\n## Active-Active geo-distributed replication\n\n[Active-Active Redis Enterprise databases]() allow reading and writing to the same dataset from multiple clusters in different geographic locations. This increases the durability of your database by reducing the likelihood of data or availability loss. It also reduces data access latency by serving requests from the nearest cluster.\n\n## Rack-zone awareness\n\n[Rack-zone awareness]() maps each node in your Redis Enterprise cluster to a physical rack or logical zone. The cluster uses this information to distribute primary shards and their replica shards in different racks or zones. This ensures data availability if a rack or zone fails.\n\n## Discovery service\n\nThe [discovery service]() provides an IP-based connection management service used when connecting to Redis Enterprise Software databases. It lets your application discover which node hosts the database endpoint. The discovery service API complies with the [Redis Sentinel API](#sentinel-api).\n",
  "tags": ["docs","operate","rs"],
  "last_updated": "2026-04-01T08:10:08-05:00",
  "children": [{"id":"clustering","summary":"Clustering to allow customers to spread the load of a Redis process over multiple cores and the RAM of multiple servers.","title":"Database clustering","url":"https://redis.io/docs/latest/operate/rs/7.8/databases/durability-ha/clustering/"},{"id":"consistency","summary":"Explains the order write operations are communicated from app to proxy to shards for both non-blocking Redis write operations and blocking write operations on replication.","title":"Consistency during replication","url":"https://redis.io/docs/latest/operate/rs/7.8/databases/durability-ha/consistency/"},{"id":"discovery-service","summary":"","title":"Discovery service","url":"https://redis.io/docs/latest/operate/rs/7.8/databases/durability-ha/discovery-service/"},{"id":"replication","summary":"","title":"Database replication","url":"https://redis.io/docs/latest/operate/rs/7.8/databases/durability-ha/replication/"}]
}