[Resolved] suggestion for use with cloudfront / s3
Can you clarify what you mean by ‘prefix’? You can already use ‘subfolders’, e.g. s3://mybucket/blah/blah/blah.
prefix to the name of zipped file
so we can then set several rules in S3 to delete files 123 after 60 days , delete 124 after 90 days etc, so we can automate deletion
so the prefix to the uploaded file name could be sequential starting from whatever we set is as
hope that clarifies
The existing file name already contains the backup date, which is a monotonically increasing and unique identifier, so this doesn’t seem to add anything new … ?
unfortunately this would not work as prefix as it would require some extensive rejig of S3 to setup auto deletion based on a prefix such as date, this is how the first part of file shows on S3
so the prefix at the moment is backup, the S3 rule would empty bucket based on a prefix of backup , but if the prefix was
then the rule could be set to delete with prefix 123 after say 60 days.
then the same with 124, 125 etc
I’m still not getting you. Why is entering 123_ as a prefix easy, but entering backup_2013-04-17 requires an extensive rejig?
because it works on set number of days not dates, also it means the person has to sit down and calculate dates rather than just enter delete 123 after 60 days.
because speaking to amazon they said they are not prepared to change the rules system as it does not require the expense on a current system which works OK, they said it not me, I am a user not a tech person
What is the “rules system” you’re referring to? Perhaps that’s why I don’t understand you… you haven’t explained it. Is there some system on S3 of allowing you to delete files that begin with numbers, but no other files???
To clarify more, earlier you said:
“then the rule could be set to delete with prefix 123 after say 60 days.”
What is so special about “prefix 123”? Where does the 123 come from? You said above that the system you’re proposing means nothing has to be calculated. But if you’re sitting down to calculate nothing, then where did you come up with the number 123 from?
As you can tell, I am not really on the ball here with what you’re proposing.
yes or a prefix that the filename has
this has a little info on it
123 could be xxx it was an example prefix that came to mind
we could use funny_backup
the first part before the _ (underscore is a prefix) and numbering sequentially is the easiest way as then you can apply “rules” in S3 on amazon to delete number 1 backup in 60 days, number 2 backup in 90 days and so on you can setup 1000 rules, this would mean you could setup a years deletion rules and have your plugin update each month with a sequential number prefix, the whole thing can do its stuff whilst we get on with doing other things 🙂
Earlier you said that entering ‘backup_2013-04-17’ as a prefix is not possible. I’ve read that link, and I see nowhere where it says that prefixes can only be numbers and cannot include something like ‘backup_2013-04-17’.
If I’m understanding you rightly, then you want to set up UpdraftPlus and Amazon S3 to delete a backup after 123 days.
You want to do this via specifying 123_ as a prefix in S3 that will be automatically deleted.
It still seems to me that you can do this already by looking at a calendar, and seeing that 123 days time from now is 2013-04-17, and then entering backup_2013-04-17.
To me, “123 days” seems no more or less complicated a concept to handle in one’s mind as “17th April 2013”.
If today is 23rd April, and you’re thinking in months, then you can just set up rules for backup_2013-07-23, backup_2013-10-23, backup_2014-01-23.
I’m not being awkward, by the way. The change you’re proposing would involve a tonne of work.
not really it means i have to work out when every 30 days is on the backup, check all the dates, then enter the 12 rules for the year, when it would be much easier with simple sequential numbering
123 means nothing, nada, nowt, jumbo, it was an example number !
Well, you could think in terms of months instead of being strict about precisely 30 days.
But anyway, I think I’d be more likely to want to code a method that implements what you’re trying to achieve in a way that works across all backup methods (Google Drive, FTP, Dropbox), etc. i.e. I’d want something that can be configured inside UpdraftPlus itself, and becomes available to all users, not just those with Amazon S3 and some S3 skills. I’ll chew it over and add this to the list. Thanks for the feedback.
- The topic ‘[Resolved] suggestion for use with cloudfront / s3’ is closed to new replies.