Bug #4546

Orphaned MySQL backups

Added by Anonymous about 6 years ago. Updated about 4 years ago.

Status:ResolvedStart date:2013-06-14
Priority:NormalDue date:
Assignee:-% Done:


Target version:jessie


Consider the case where there is a database called foo.

Once per day this will be dumped to disk, beneath /var/backups/mysql.

The local backup will be kept for easy restoration, and the backup will also be included in the backup2l dump.

If this database is subsequently removed "mysql --user=root -e 'drop database foo'" the local dump is never removed.

I'd suggest we have a post-backup script that does one of two things:

1. Removes files older than a week. This will ensure that orphaned database dumps are cleaned up shortly.

2. Optionally removes all local dumps. Since they will be present in the backup2l .tar.gz file.

Associated revisions

Revision 9ea525de
Added by Patrick Cherry about 4 years ago

backup: Added orphaned-backup clearing as a pre-backup step.

Closes #4546


#1 Updated by Steve Kemp about 6 years ago

See #551948 for the original report and further details.

#2 Updated by Patrick Cherry about 6 years ago

I'm thinking a replacement to backup2l would be the best solution.

#3 Updated by Patrick Cherry almost 6 years ago

  • Project changed from 221 to Symbiosis

#4 Updated by Patrick Cherry over 4 years ago

  • Target version set to jessie

#5 Updated by Patrick Cherry about 4 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Applied in changeset symbiosis|commit:c35c5ae892e5.

Also available in: Atom PDF