Majic Projects
Majic Ansible Roles
Go to the previous open issue
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
icon_project.png Majic Ansible Roles / Closed Enhancement MAR-198 Automatically purge stale backup metadata files
Go to the next issue (open or closed)
Go to the next open issue
There are no more issues in that direction.
This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Enhancement
  • Category
    User interface
  • Targetted for
    8.0.0
  • Status
    Closed
  • Progress
  • Priority
    Normal
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    1 hour
  • Time spent
    1 hour, 20 minutes
    Click here to see time logged against this issue
Issue details
  • Resolution
    RESOLVED
Attachments (0)
There is nothing attached to this issue
Duplicate issues (0)
This issue does not have any duplicates
Description

The backup_client role implements backups using duply/duplicty. Each backup involves not only the data itself, but also a lot of metadata that accompany such backups. Over time these metadata files tend to occupy quite a bit of space on both the backup server and the backup client without providing any value (since the will start to fall outside of the designated backup retention policies).

It would be useful to automatically get rid of any excess fails accumulated during backup, thus reducing disk usage, and making the system run more smoothly in general.

The following should be done:

  • Update the backup_client role.
    • Add running purge --force at the end of backup process. This should purge the metadata files which are past the retention policy preserve times.
    • Run the pre/bkp/post/purge (with --force) stages in sequence in order to ensure that each step is executed successfully.
  • Update role reference documentation.
  • Update usage instructions.
  • Update release notes.
Todos (0 / 0)
There are no comments