juju create-backup should not default to creating backup inside database
Bug #1749300 reported by
Mario Splivalo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Medium
|
Heather Lanigan | ||
Bug Description
Juju, by default, stores backups inside mongod.
This creates issues for customers as there is no standard cleanup procedure for stored backups. Even so, after the backups are (manually) deleted, the mongodb on-disk footprint does not get reduced (LP: #1743986).
By default juju should not store backups in the database at all - in the event of state server crash (when backups are most needed) those backups will be useless anyhow, as state server ceased to exist.
Backups should be downloaded locally as they can be easily restored from there.
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: backup-restore bitesize |
| Changed in juju: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Heather Lanigan (hmlanigan) |
Revision history for this message
| Heather Lanigan (hmlanigan) wrote | #1 |
Revision history for this message
| Heather Lanigan (hmlanigan) wrote | #2 |
| Changed in juju: | |
| milestone: | none → 2.4-beta2 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The current plan to change the default behavior of juju create-backup to download the backup and not keep a copy on the controller.
A new flag will be --keep-copy, which will save a copy of the backup on the controller.
The current --no-download will imply keep-copy is true.