Closed (won't fix)
Project:
Hostmaster (Aegir)
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
3 Apr 2009 at 16:42 UTC
Updated:
20 Aug 2012 at 06:13 UTC
Jump to comment: Most recent
Comments
Comment #1
anarcat commentedThis depends on #422970: have one task type per site node and of course #422962: Add Hosting Tasks Schedule module.
Comment #2
anarcat commentedThere's a workaround documented here: #683610: Implement automated backups workaround.
Comment #3
mathieu commentedSubscribe.
Comment #4
adrian commentedjust FYI:
in HEAD i added a useful debugging feature to the hosting-task command, in that you can now specify it in the following format :
Where site.com is the alias for the site and backup is the task you want to use.
This will actually run the task in the hosting site and also add the resultant entry to the backups table.
You could also do :
or any other task that doesnt need arguments (migrate and restore , off the top of my head).
Comment #5
adrian commentedso i think the backups should be a separate queue
but i'm trying to determine where to plug in the deleting of old backups, and whether we should be passing the list of backups to delete to the provision task, or just giving it a time and telling it to delete all pre a certain timestamp, and report back about what it removed so we can trim the table.
i think the latter suits our design better.
We should do this for 0.4 if possible.
Comment #6
adrian commentedi added this in the dev-purgebackup branch.
when the --delete_backups_older_than flag is specified for the provision-backup command, provision matches files that are older than the specified time offset, and unlinks them.
it then returns a list of files it removed, and hosting then deletes the backup table entries for eahc of the files.
it's not configurable in the tree right now, as it's hard coded to delete backups older than 1 week.
Comment #7
adrian commentedthis is sort of working in git.
under the dev-purgebackup branch
Comment #8
Bèrto ëd Sèra commentedsubscribe
Comment #9
steven jones commentedHmm...deleting old backups after a certain threshold is a bit heavy handed. What if I want to keep around montly backups for the last year?
Comment #10
mvcThis would also be helpful for #974572: site node garbage collection
Comment #11
steven jones commentedAs there doesn't seem to be much movement in this, I might just implement a simple backup queue as a contrib module. Seems like it would be useful to lots of people, myself included.
Comment #12
steven jones commentedA very simple automated backups module is now available here:
http://drupal.org/project/hosting_backup_queue
Comment #13
Anonymous (not verified) commentedGreat work Steven, and I'm sorry we haven't been around much to give you much help here.
This is a significant contribution and I hope to soon get some time / funding to focus on this and get this whole idea into Aegir proper.
Thanks!
Comment #14
steven jones commentedI've implemented the backup garbage collection here:
http://drupal.org/project/hosting_backup_gc
Comment #15
jackbravo commentedsubscribe
Comment #16
steven jones commentedTagging
Comment #17
steven jones commentedNow that we have these add-on modules, I don't think we need this in Aegir core.