Docs Self-Managed Manage Tiered Storage Topic Recovery You are viewing the Self-Managed v24.3 beta documentation. We welcome your feedback at the Redpanda Community Slack #beta-feedback channel. To view the latest available version of the docs, see v24.2. Topic Recovery When you create a topic, you can use remote recovery to download the topic data from object storage. This is useful when you need to restore a single topic in Tiered Storage that was accidentally deleted from a cluster. Remote recovery is only safe when no other clusters are writing to the specified bucket or container. You must enable redpanda.remote.read when using remote recovery. If you later disable redpanda.remote.read on the remote recovery topic, previously hydrated (downloaded) data will not be used to serve requests. To create a new topic using remote recovery, in which the recovered topic can read and write in the cloud: rpk topic create <topic_name> -c redpanda.remote.recovery=true -c redpanda.remote.write=true -c redpanda.remote.read=true To create a new topic using remote recovery, while also disabling the redpanda.remote.write property: rpk topic create <topic_name> -c redpanda.remote.recovery=true -c redpanda.remote.write=false -c redpanda.remote.read=true Back to top × Simple online edits For simple changes, such as fixing a typo, you can edit the content directly on GitHub. Edit on GitHub Or, open an issue to let us know about something that you want us to change. Open an issue Contribution guide For extensive content updates, or if you prefer to work locally, read our contribution guide . Was this helpful? thumb_up thumb_down group Ask in the community mail Share your feedback group_add Make a contribution Remote Read Replicas Whole Cluster Restore