181–190 of 393 posts
Earlier quoted context omitted.
US Standard isn't replicated across regions.
Hm, you could be right, AWS says: > The US Standard Region automatically routes requests to facilities in Northern Virginia or the Pacific Northwest using network maps. I guess this means that the data is automatically geographically sharded?
Earlier quoted context omitted.
sigh Dropbox should not be used as a backup system. A system that synchronizes live should never get that role, except if they can guarantee that old data is never overwritten, new is always appended. This is not the case with dropbox - I've experienced multiple scary occurrences of old versions going to the nirvana with certain user actions. In certain cases the old data just appears to be gone, in other cases the w…
I use a combination of Dropbox and S3. I have my MacBook and a Linux server linked to my Dropbox account. So changes in my documents are synced to my Linux. My Linux run three cron-jobs. One daily, one weekly and another monthly. The command is. s3cmd sync --delete-removed ~/Dropbox/documents/ s3://backup-daily/ There are buckets for weekly and monthly too. Note: the command is not exactly like that, check the man pa…
Anyone know what the TOS are for this? I couldn't find them on a scan of the announcement. A lot of the consumer-level services refuse any liability for any data loss. Does Amazon do the same for this?
Presumably the standard S3 SLA will apply: http://aws.amazon.com/s3-sla/ Realistically, you'd want to have at least two diverse cloud backup systems - I doubt you'd be happy with Service Credits if your data went missing.
"We will keep your data safe! *
* T&C's apply, if we lose it, you're on your own."
I shouldn't imagine Bank Vaults deal the same way with physical property. Can you get insurance for digital assets the same way you can for physical ones?
Earlier quoted context omitted.
With large volumes the real issue is not the storage but the upload speed. I've done some experiments and with the Comcast link (20Mbps down/whatever up), I got 1 Gb/hour upload rate. So, it'll take 11 full days to upload 256 Gb. Or, more realistically, if you do it overnight (8 hours) - the entire month.
If you don't mind the additional cost, you can physically send Amazon a harddrive: http://aws.amazon.com/importexport/
I'm a long time user of backblaze, and I'm a big fan of the product - it does a great job of always making sure my working documents are backed up, particularly when I'm traveling overseas, and my laptop is more vulnerable to theft or damage. With that said - Backblaze is optimized for working documents - and the default "exclusion" list makes it clear they don't want to be backing up your "wab~,vmc,vhd,vo1,vo2,vsv,v…
I'm looking into supporting Glacier in Arq. It sure is cheap -- $10/month for a terabyte.
Earlier quoted context omitted.
Duplciity supports S3, so I'd watch it for Glacier support: http://duplicity.nongnu.org/
I wonder if Glacier support in Duplicity will be possible without large changes. AFAIK, duplicity also reads some state from the remote end to determine what to backup (Although it also keeps a local cache of this?). To use glacier, the protocol would have to completely write-only.
Earlier quoted context omitted.
In a corporate environment, I wouldn't want to depend on the cloud as my primary backup solution in the first place. I'd be much more comfortable using it as the offsite mirror of an onsite backup. If you're at a point in disaster recovery where you have to restore from your offsite, you (likely) have bigger problems than a 4-hour wait time.
I personally believe that data should never be deleted (or overwritten), but only appended to. Kinda like what redis/datomic does. So, keep live data onsite, along with an onsite (small) backup, and all the old data in Glacier.
I had a quick skim through the marketing stuff and the FAQs and didn't see anywhere that actually details what the backend of this is. I'd be curious if they're actually using tape, older machines, Backblaze pods, etc. I guess if it's the latter, the time to recover could be an artificial barrier to prevent people from getting cute.
agreed, it would be great to know how this is running from a hardware point of view - just out of personal interest :-)
I'm a long time user of backblaze, and I'm a big fan of the product - it does a great job of always making sure my working documents are backed up, particularly when I'm traveling overseas, and my laptop is more vulnerable to theft or damage. With that said - Backblaze is optimized for working documents - and the default "exclusion" list makes it clear they don't want to be backing up your "wab~,vmc,vhd,vo1,vo2,vsv,v…
With large volumes the real issue is not the storage but the upload speed. I've done some experiments and with the Comcast link (20Mbps down/whatever up), I got 1 Gb/hour upload rate. So, it'll take 11 full days to upload 256 Gb. Or, more realistically, if you do it overnight (8 hours) - the entire month.