最適なインスタンスの可用性とデータ耐久性を実現するには、永続性と高可用性の両方を有効にすることをおすすめします。
永続性と高可用性は、提供する保護の点で重複していますが、互いに補完する異なる強みがあります。HA は、個々のノード障害とゾーン停止に対する最初の防御線と見なすことができます。永続性により、シャード内のすべてのノードで障害が発生し HA で解決できないとき、まれなイベントに対する障害復旧が提供されます。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-04 UTC。"],[],[],null,["# Persistence overview\n\nThis page provides an overview of persistence for Memorystore for Redis Cluster.\n\nMemorystore for Redis Cluster supports two types of persistence:\n\n- [AOF persistence](/memorystore/docs/cluster/about-aof-persistence)\n- [RDB persistence](/memorystore/docs/cluster/about-rdb-persistence)\n\n| **Note:** You can either enable AOF or RDB persistence for your instance, not both.\n\nFor the best instance availability and data durability, we recommend enabling\nboth persistence and [high availability](/memorystore/docs/cluster/ha-and-replicas).\nWhile persistence and high availability overlap in the protection they offer, they have\ndifferent strengths that complement each other. HA can be considered the first\nline of defense against individual node failures and\nzonal outages. Persistence provides disaster recovery for rare events when all\nnodes in a shard fail and HA is unable to help.\n\nChoosing a persistence type\n---------------------------\n\nChoosing between AOF and RDB persistence comes down to a choice between\nperformance and data durability. These tradeoffs are generally true of all\nmanaged Redis services because of the nature of AOF and RDB persistence in OSS\nRedis.\n\nIf your top priority is data durability and preserving the highest percentage of\nwrites sent to your Redis server, we recommend choosing AOF persistence. AOF's\nability to persist data every second (or for every write) offers superior data\ndurability compared to RDB snapshots which save data on an hourly basis.\n\nIf performance is your top priority, we recommend using RDB persistence because\nit usually places lower performance demands on your instance than AOF persistence\ndoes for a similarly sized instance. If you are comfortable with some staleness\nin your data on recovery and you want the performance that RDB persistence provides\nfor a similarly sized instance, then RDB persistence is the better choice for\nyou.\n\nIt is possible to have both high throughput with the durability of AOF\npersistence. To get both you can enable AOF persistence and also choose a high\nshard count. A high shard count provides more vCPUs which improves performance. However, some\nlatency increase is expected for AOF in any configuration."]]