Docs Self-Managed Manage Kubernetes Storage Tiered Storage Data Archiving This is documentation for Self-Managed v23.3. To view the latest available version of the docs, see v24.2. Data Archiving in Kubernetes This feature requires an Enterprise license. To upgrade, contact Redpanda sales. With data archiving, you can enable remote write to back up topics to cloud storage. In the event of a data center failure, data corruption, or cluster migration, you can recover your archived data from the cloud back to your cluster. Data archiving is a use case of Tiered Storage. Redpanda natively supports Tiered Storage with Amazon S3, Google Cloud Storage (GCS), and Microsoft Azure Blob Storage (ABS). Migrating topics from one cloud provider to another is not supported. Prerequisites This feature requires an Enterprise license. To upgrade, contact Redpanda sales. To check if you already have a license key applied to your cluster: rpk cluster license info Configure data archiving Data archiving requires a Tiered Storage configuration. Set up Tiered Storage for the cluster or for specific topics. If you want to read data from cloud storage, enable remote read. When remote read is disabled, data can only be read from local storage. Set retention limits. To recover a topic from cloud storage, use remote recovery. Stop data archiving To cancel archiving jobs, disable remote write. To delete archival data, adjust retention.ms or retention.bytes. 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 Tiered Storage Expand PersistentVolumes