Backups and imports
Backups and imports built for recovery, migration, and environment sync
Protect application data with scheduled backups, off-site storage, and import workflows that make migrations less painful.
Backups are not only for worst-case scenarios. Wodby helps teams protect data, restore service faster, migrate existing applications, and move datasets between environments without building a separate operational process for every case.
Create the backup strategy that fits each application
Different services need different backup rhythms, and teams should be able to handle both scheduled and one-off protection events.
Wodby supports on-demand backups for immediate safety and recurring schedules for ongoing coverage. That gives teams a practical way to protect data before risky changes and to keep regular recovery points available without manual intervention.
Backup creation follows the service definition instead of treating all data the same way. Each supported service exposes backup options for its own data shape, then Wodby runs the backup task and keeps the resulting archive tied to the application, instance, and service that produced it.
- Create an immediate backup before risky upgrades, migrations, or data-changing maintenance.
- Schedule recurring backups for services that need continuous recovery points.
- Restore from the backup history attached to the service that produced the archive.
Store backups off-site for stronger disaster recovery posture
Backups are more useful when they are not tied to the same infrastructure that might fail.
Wodby integrates with external storage providers so backup archives can live outside the runtime environment itself. This supports a cleaner disaster recovery model and gives teams more options for retention, compliance, and longer-term storage.
Standardize backup policies across projects and services
Platform teams often need the same backup expectations to apply across multiple applications.
Shared presets make it easier to roll out backup expectations without configuring every service from scratch. Organization-wide presets can apply consistent storage, retention, and scheduling expectations while still allowing app teams to override settings where the service requires a different policy.
Presets are especially useful when production, staging, and preview environments need different backup behavior. Platform teams can define defaults once, scope them by environment, and reduce the chance that a new app launches without the expected recovery posture.
- Use shared presets to keep service backups consistent across teams.
- Scope backup expectations by environment instead of relying on each project to remember them.
- Allow service-level overrides when one app needs a different schedule, retention period, or storage target.
Import existing applications and datasets with less migration friction
Migration work is easier when the platform can accept archives and URLs directly.
Wodby import workflows help teams move existing applications onto the platform or refresh lower environments with realistic data. Instead of building a one-off migration path for every project, imports become a supported operation inside the platform.
Imports can start from an uploaded archive, a remote URL, or an existing Wodby backup. Database services use database-aware import commands, while file-based services can import into volumes using the workflow defined by the service.
- Upload an archive directly when the data is available on your machine.
- Import from a remote URL when the source archive is already stored elsewhere.
- Use an existing Wodby backup as the source when cloning data between environments.
Recover faster and keep lower environments useful
Restore workflows are valuable both in incidents and during everyday engineering work.
Quick restore options help reduce downtime after accidental deletions, broken changes, or data corruption. The same mechanics also support development workflows by letting teams copy or synchronize datasets into staging and test environments.
- Restore service to a known-good state after data loss or a bad change.
- Refresh staging with newer production-like data for safer validation.
- Troubleshoot production issues in a separate environment with more confidence.
File imports also support two operating modes. A simple files import is useful for straightforward copy operations, while an init-volume import prepares data before the target service starts, giving teams a safer transactional path for services that need data in place at startup.
Environment sync becomes more practical when paired with application environments that can safely receive imported data.
Next step
Treat data protection and migration as part of normal delivery
Use one workflow for scheduled backups, restores, migrations, and environment sync instead of bolting recovery steps onto the side of the platform.