The free forums are no longer in use. It remains available as read-only archive.

1:18 am

October 6, 2012

Hi Ovidiu,
Not certain this is a bug, but it certainly is for me… and I suspect, others.
If my assertion here is incorrect, please enlighten me.
Amazon s3 allows us to set expiration limits on objects within buckets e.g. backup Tar’s etc.
But, at least as far as I can tell, NOT folders within buckets nor objects within folders.
When I setup XCloner with a specified “Upload Directory” in XCLoner amazon cron tab page and had a coresponding folder called “backups” in s3…
I was able to backup to that folder OK, but could not set an expiration for objects within it (nor the folder object itself).
When I left the “Upload Directory” input box empty, XCloner (I think) created a nameless folder and uploaded to that. Thus leaving me again unable to set an expiration in s3.
I would have thought XCloner should NOT create a folder if the input box is empty. If, of course, it is XCloner and not the s3 system creating such folders.
I should point out that:
1. I am ONLY using the external version – 3.1
2. I have tested manually using the “execute cron” link.
3. I have also tested with auto server side cronjob.
4. For the external setup I have successfully moved the cloner.config.php to a folder above the site root – with a couple of little hacks to admin.cloner.php and cloner.cron.php.
… But have tested without such hacks… same results.
I hope I have expressed the issue clearly.
Cheers,
Chris
8:13 am
September 26, 2010

8:15 am
September 26, 2010

From amazon description http://aws.amazon.co…..iration/ , you can add an expiration to the folder itself, so all files inside it will be deleted when the expiration rule is meet…
8:52 am

October 6, 2012

Thanks for getting back Ovidiu,
Yep, I saw the article “Amazon S3 announces Object Expiration”.
But I cannot make it work for me.
When I had a folder called “backups”
I tried “backups/backup_”
I tried “backups/*.tar”
I tried “backups/tar”
Suggestions for alternatives welcome 🙂
So, I rearranged everything and made buckets for backups e.g. [nhd.live.joomla.bak]
That’s when the nameless folders were created by XCloner.
Also, deleting the contents of a folder is not really the solution. I need to expire, for example, backups older than 32 days… whether in a bucket or folder.
I may have a range of folders “backups”, “images” etc. But I can’t dynamically time-stamp folder names on the fly.
How do I post screen captures?
— I will try this…
http://newhomedesign.com.au/cwm_pics/aws_s3_nameless_folder_example_001.jpg
http://newhomedesign.com.au/cwm_pics/aws_s3_nameless_folder_contents_002.jpg
Chris
9:15 am
September 26, 2010

9:32 am

October 6, 2012

11:59 pm

October 6, 2012

Hi Ovidiu,
Yes, backups/ worked for s3 expiration.. at least items in the folder are indicating they will expire. I think it’s safe to assume that will happen 🙂
I feel a bit stupid for not seeing the /… but we live and learn.
Just one more point relevant to this subject.
— from a standalone install…
When I initiate the manual cron, a new tab opens, but it remains blank. I have noticed when initiated from Joomla or WP, there is a rolling page of actions taken… to finally announce completion. I am using FireFox 15.0.1
— Is that a config thing that I have missed?
Thanks for your patience.
Chris
1 Guest(s)
