Frequently Asked Questions
Why can’t I just use Docker export or commit for backups?
Docker export and commit commands are designed for image creation and container migration, not enterprise data protection. These methods don’t capture persistent volumes where most application data resides, lack scheduling and retention policies, and provide no encryption or compliance features. True backup solutions protect all container components with automated workflows, version management, and verified recovery capabilities.
How does backing up containers differ from backing up regular files?
Container backups must capture multiple layers including base images, configuration metadata, environment variables, network settings, and mounted volumes as a cohesive unit. File-level backups would need to traverse complex overlay filesystems and understand Docker’s storage drivers, creating massive overhead and potentially corrupting running containers. Image-based approaches through the Docker API are faster, safer, and ensure containers can be restored as functional units.
What happens to my data when a container is deleted?
Container filesystem changes are lost immediately when containers are removed unless you’ve mounted external volumes or committed changes to images beforehand. Ephemeral containers running without volume mounts lose all data written during their lifetime. Bacula’s automated backup captures container state and associated volumes regularly, ensuring data survives container deletion, host failures, or accidental removal.
Can I backup containers while they’re running?
Yes, Bacula creates container commits (similar to snapshots) that capture the current state without stopping or pausing running containers. The backup process reads from these commits through the Docker API while your applications continue operating normally. This approach minimizes disruption and allows backup of production workloads during business hours without downtime.
How do I restore containers to a different Docker host?
Bacula restores containers as portable image archives that can be loaded into any Docker environment through the standard Docker API. You specify the target Docker host during restore, and Bacula transfers the container image, recreates volume data, and optionally starts the container with its original or modified configuration. This flexibility supports disaster recovery, environment migration, and creating test instances from production backups.