# Continuous Restore Continuous Restore is a T4K feature that automatically stages backups to a remote cluster as soon as each new backup is available. Backups from the source cluster are created as snapshots on the target cluster, so in the event of a disaster, applications can be recovered quickly from those pre-staged snapshots. Users can also run regular restore tests to build confidence in their DR plan. The feature is implemented as a cloud-native service designed for multi-cluster and multi-cloud environments. It supports a fabric topology where any application in any Kubernetes cluster can designate any other cluster as a restore site, with no assumptions about network connectivity between clusters. The only requirement is that the backup target is shared and accessible between the source and target clusters. ## In This Section * [Architecture and Concepts](/kubernetes/concepts/continuous-restore/architecture-and-concepts.md) — How Continuous Restore works and the components involved. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.trilio.io/kubernetes/concepts/continuous-restore.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.