Following up JungleDisk vs Amanda
Following up to Backing up to Amazon S3 using Amanda (June 28, 2008):
I’ve been having issues with both Amanda+S3 as well as JungleDisk. I’ll outline these here.
JungleDisk Problems
- JungleDisk sometimes destroys all of my data on S3 in the bucket JungleDisk uses and then on the next backup re-uploads all of the data! This is clearly a problem. Luckily I do not have more than a gigabyte of data thats backed up with JungleDisk. If I did this bug (or feature?) would be very expensive.
- JungleDisk doesn’t smartly handle moves. I’d like to be able to move things around on my local filesystem and have JungleDisk notice this and move them. Moving them over WebDAV isn’t feasible.
- JungleDisk scans individual files and doesn’t combine a whole bunch of them into one tarball. This gets very expensive! I wish they’d tar it all up first like Amanda.
Amanda+S3 Problems
- Sometimes the Amanda S3 device module has problems talking to S3. The only fix I’ve found so far is to destroy the bucket, remove it from the tapelist, readd the bucket, reidentify the bucket to Amanda and run amflush. This is clearly not good as it’s just as bad as Jungledisk destroying everything. I haven’t figured out why this happens yet.
Both products are still good and I’ll continue to use them. I’m considering using Amanda on my laptop, however, but this could cause problems in cases where it isn’t connected to the network at backup time.
Try SMEStorage.com - sign up for their OpenS3 beta and use your own amazon keys - much better than both of what you mention
- John
Comment by John Rooken — September 4, 2008 @ 9:52 am
[...] the past I mentioned some Pros and Cons of Jungledisk and Amanda and the one listed “con” for Amanda is that it periodically had issues with my buckets [...]
Pingback by CrudVision - Lisa Seelye » Another Amanda Post — October 7, 2008 @ 12:09 pm