Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re: Curve fitting for rsync snapshot deletion

by Preceptor (Deacon)
on Nov 23, 2013 at 12:51 UTC ( #1064035=note: print w/replies, xml ) Need Help??


in reply to Curve fitting for rsync snapshot deletion

If your objective is to have degrading resolution of snaps as time passes, might I suggest instead - run 3 'sets' of snaps. A '15m' schedule, a 'daily' scheduled, and a 'weekly' schedule.

And then automate the deletions in each with e.g. 'find' - when you're >95% work through each, and purge the '15m' backups more aggressively than the daily/weeklies.

  • Comment on Re: Curve fitting for rsync snapshot deletion

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1064035]
help
Chatterbox?
Corion idly wonders about creating a series of HTTP requests. There seems to be no framework to generate a series of HTTP requests, like "try all these requests"
[Corion]: This is vaguely inspired by that list of "nasty" strings, which I'd like to replace among HTTP parameters, just to see whether the application crashes, but also for easy downloading of a list of URLs etc
[Corion]: Maybe I'll just conoct something using Algorithm::Permute to create an (OO) generator for such requests, or a simple function.

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (9)
As of 2017-01-16 15:36 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Do you watch meteor showers?




    Results (151 votes). Check out past polls.