1. Register an Amazon AWS S3 account - https://aws-portal.amazon.com/gp/aws/developer/registration/... 2. Download my S3 backup script (or anyone's S3 Backup script) - http://github.com/leftnode/S3-Backup 3. Set up a cron to push hourly/daily/whatever tar's of your vhost's directory to S3. Spend, like, $10 a month. Thats 30gb of storage, 30gb up and 30gb down. Now, I know that may not be a lot, but I doubt codinghorr…
There's also tarsnap, run by HN's very own cperciva.
Coding Horror and blogs.stackoverflow.com experience "100% Data Loss"
71–80 of 175 posts
Re: Coding Horror and blogs.stackoverflow.com experience "100% Data Loss"
#72I've backups of my silly blog antirez.com, this guy ran a business out of his blog and don't have external backups. The data is small, it is easy to transfer. It's almost unbelievable to me.
Re: Coding Horror and blogs.stackoverflow.com experience "100% Data Loss"
#73Earlier quoted context omitted.
"Coding Horror experienced 100% data loss at our hosting provider, CrystalTech. I have some backups and I'll try to get it up and running ASAP!"
Read his newer tweets - his backups were just copies on the same server; they are gone as well, and now he's resorting to using internet caches to restore his content.
Re: Coding Horror and blogs.stackoverflow.com experience "100% Data Loss"
#74Oh The Irony This is really bad news for any service, but seriously... codinghorror.com (shakes head) Rule 16. If you fail in epic proportions, it may just become a winning failure.
Re: Coding Horror and blogs.stackoverflow.com experience "100% Data Loss"
#751. Register an Amazon AWS S3 account - https://aws-portal.amazon.com/gp/aws/developer/registration/... 2. Download my S3 backup script (or anyone's S3 Backup script) - http://github.com/leftnode/S3-Backup 3. Set up a cron to push hourly/daily/whatever tar's of your vhost's directory to S3. Spend, like, $10 a month. Thats 30gb of storage, 30gb up and 30gb down. Now, I know that may not be a lot, but I doubt codinghorr…
Re: Coding Horror and blogs.stackoverflow.com experience "100% Data Loss"
#76Earlier quoted context omitted.
Well, he did make sure to tell us to shut up, stop what we're doing and make a back-up. Because he knows things, you see: http://74.125.93.132/search?q=cache:2HHNAk2SB6EJ:www.codingh...
The site says he has a backup, right? So it sounds like he ... does have a backup.
Re: Coding Horror and blogs.stackoverflow.com experience "100% Data Loss"
#77To be fair, Atwood thought his hosting provider (CrystalTech) was backing up his system. As it turns out, their entire VM backup solution failed silently, so everyone thought the backups were being made. If anything, I'd say this is a sign not to work with CrystalTech.
If anything, I'd say this is a sign not to work with CrystalTech. After a mistake like this, it may be a sign that they will never mess up again.
Re: Coding Horror and blogs.stackoverflow.com experience "100% Data Loss"
#78Earlier quoted context omitted.
Yes, but I'm not sure if your comment is targeted at CrystalTech or codinghorror? You can't outsource liability. If YOU are not testing YOUR backups. YOU fail.
It's a blog. How much time and money is worth spending on this? (I backup my Slicehost account with their official service. If they die and my backup dies with it, that's fine; I don't have the time or money to do anything better.)
Re: Coding Horror and blogs.stackoverflow.com experience "100% Data Loss"
#79I've backups of my silly blog antirez.com, this guy ran a business out of his blog and don't have external backups. The data is small, it is easy to transfer. It's almost unbelievable to me.
Did he? I thought Jeff had some "real job" in addition to blogging and Stack Overflow. I honestly doubt an occasionally-updated programming blog was putting the food on his table.
I guess I can not link to the blog post...
Re: Coding Horror and blogs.stackoverflow.com experience "100% Data Loss"
#80Oh The Irony This is really bad news for any service, but seriously... codinghorror.com (shakes head) Rule 16. If you fail in epic proportions, it may just become a winning failure.
System administration is not "coding".