Recover broker disks or recover Kafka data
Kafka EBS snapshots are strong infrastructure backups. They recreate broker volumes after an AWS failure. OSO Kafka Backup protects logical topic data and consumer offsets independently of those volumes.
Kafka EBS snapshots and logical backups protect different layers
Amazon EBS snapshots preserve block-volume state. AWS can take crash-consistent snapshots across the volumes attached to one EC2 instance. They fit existing AWS Backup policies and can recreate a failed broker disk without copying every block again.
OSO Kafka Backup reads Kafka records through the client protocol. It stores topic data, configuration, and consumer offset metadata outside the broker volumes. You can restore selected topics to another cluster or stop at a precise timestamp.
The boundary matters for multi-broker recovery. EBS crash consistency covers one instance, not a logical cut across every Kafka broker and consumer group. A volume restore also recreates the whole disk rather than one deleted topic. See the AWS snapshot consistency documentation for the infrastructure guarantee.
| Feature | OSO Kafka Backup | Amazon EBS snapshots |
|---|---|---|
| Protection layer | Kafka records and metadata | Block volumes |
| Primary strength | Logical Kafka recovery | Broker disk recovery |
| Consistency boundary | Selected topics and offsets | Volumes on one EC2 instance |
| Single-topic restore | Yes | No |
| Timestamp-based restore | Millisecond precision | No |
| Consumer group offsets | Preserved | Part of broker disk state |
| Restore to another Kafka cluster | Yes | Requires broker rebuild |
| AWS infrastructure recovery | No | Yes |
| Storage portability | S3, Azure, GCS, filesystem | Amazon EBS |
| Best for | Deletion, corruption, migration | EC2 and volume failure |
Choose the recovery boundary you need
Choose EBS snapshots when your recovery unit is the EC2 instance and its broker disks. They work well for infrastructure rebuilds, account-level backup policies, and fast volume creation inside AWS.
Choose OSO Kafka Backup when your recovery unit is a topic, consumer group, or point in time. Logical backups remain usable when the original brokers or volumes are unavailable. They can also restore into a differently sized cluster.
Many AWS teams use both. EBS snapshots restore the broker infrastructure. A logical backup then provides a clean recovery point for accidental deletion, corrupt writes, or migrations. The Kafka disaster recovery guide maps these layers to common failure modes.
A Kafka-aware snapshot is not a disk snapshot
OSO snapshot mode captures current Kafka high watermarks, then stops after every selected
partition reaches its captured offset. consumer_group_snapshot writes committed group
offsets alongside the backup. These controls create a logical recovery set in portable
storage.
A disk snapshot has a different job. It preserves raw broker files without understanding topics, partitions, or group positions. The configuration reference documents the logical snapshot and offset settings.
Frequently asked questions
Can I use EBS snapshots to back up Kafka?
EBS snapshots can protect broker volumes and help rebuild AWS infrastructure. They do not create a coordinated logical backup across brokers, topics, and consumer groups. Pair them with a Kafka-aware backup when you need topic-level or point-in-time recovery.
Are multi-volume EBS snapshots consistent for Kafka?
AWS creates crash-consistent snapshots across volumes attached to one EC2 instance. A Kafka cluster usually spans several instances, so that guarantee does not create one logical recovery point across the whole cluster.
Can an EBS snapshot restore one deleted Kafka topic?
No. An EBS snapshot restores a block volume, not a selected Kafka topic. OSO Kafka Backup can restore selected topics and stop at a millisecond timestamp before the deletion.
Should I keep EBS snapshots if I use OSO Kafka Backup?
Yes, when broker-volume recovery is part of your AWS plan. EBS snapshots protect infrastructure, while OSO Kafka Backup protects logical Kafka data. Using both covers different failure classes.
Ready to protect your Kafka data?
Take your first backup in minutes with the open source CLI, or talk to us about Enterprise features like encryption, RBAC, and audit logging.