> For the complete documentation index, see [llms.txt](https://docs.hashsphere.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashsphere.com/operations/network-backup-and-restore.md). # Network Backup and Restore Overview of the HashSphere network backup and restore processes HashSphere is resilient by design and avoids single points of failure. HashSphere Managed Service also includes backup and restore to support business continuity. ### Backup Scope For managed service deployments, the following components are backed up on a scheduled basis: * Consensus node state * Mirror node data * Supporting configurations required for service restoration Backup data is encrypted at rest in cloud storage in a customer-selected region. Restore uses the most recent snapshot to provision replacement components and rehydrate state. ### Downtime Considerations Network availability during a restore event depends on several factors, including * The number of nodes affected * Cloud provider availability during the restore event * Whether the restore is for a single node or a full-environment recovery * Transaction volume on the network Planned maintenance windows and recovery objectives are defined in your service agreement. ### Recovery Objectives Recovery objectives such as RPO and RTO targets are defined according to the service contract and deployment architecture. Customers should refer to their service agreement for specific commitments. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hashsphere.com/operations/network-backup-and-restore.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.