Hot answers tagged backups
Here's my wild stab in the dark: configure your web server to return 304 for every image request, then crowd-source the recovery by posting a list of URLs somewhere and asking on the podcast for all your readers to load each URL and harvest any images that load from their local caches. (This can only work after you restore the HTML pages themselves, ...
Some of us follow you with an RSS reader and don't clear caches. I have blog posts that appear to go back to 2006. No images, from what I can see, but might be better than what you're doing now.
By going to Google Image search and typing site:codinghorror.com you can at least find the thumbnailed versions of all of your images. No, it doesn't necessarily help, but it gives you a starting point for retrieving those thousands of images. It looks like Google stores a larger thumbnail in some cases: Google is on the left, Bing on the right.
Sorry to hear about the blogs. Not going to lecture. But I did find what appears to be your images on Imageshack. Are they really yours or has somebody been keeping a copy of them around. http://profile.imageshack.us/user/codinghorror They seem to have what looks like 456 images that are full size. This might be the best bet for recovering everything. ...
I'd suggest that you: Automatically mirror the entire contents and configuration of your main server to a secondary backup server on a completely separate network in a different data centre. Use RSync, FXP, cPanel voodoo, or whatever method you wish to automate syncing. Use DNS failover switching to automatically route traffic to the backup server should ...
A suggestion for the future: I use Windows Live Writer for blogging and it saves local copies of posts on my machine, in addition to publishing them out to the blog.
Use the Internet Archive's Wayback Machine: http://www.archive.org Note that they only have content from at least six months ago available. Otherwise, you can try using Google's cache by searching for "cache:youroldwebsite.com" or using the "Cached" link on search results.
About five years ago, an early incarnation of an external hard drive on which I was storing all my digital photos failed badly. I made an image of the hard drive using dd and wrote a rudimentary tool to recover anything that looked like a JPEG image. Got most of my photos out of that. So, the question is, can you get a copy of the virtual machine disk image ...
The basic model for this is that a domain name points at an IP address, the server machine at that IP address runs web server software, and your web content is on the hard drive of that server machine. Having a domain expire generally means that "www.mydomain.com" no longer points to the same IP address, but it doesn't automatically cause your content to be ...
Disaster recovery can be a huge task, especially when dealing with multiple servers, sites, and databases. Two key items to take into account with the solution you select are recovery time objectives (RTOs) and recovery point objectives (RPOs). RTO is essentially the expectation of how long it should take until the sites are back up. If you have an RTO of ...
If your images were stored on an external service such as Flickr or a CDN (as mentioned in one of your podcasts), you may still have the image resources there. Some of the images could be found searching on Google Images and click on "Find similar images", maybe there are copies on other sites.
I can tell you that I currently use mysqldump to maintain a backup of my database. I do this because my goal is to keep weekly backups so that in the event someone removes their webpage(s), I can recover it from at most a week ago. The good thing about this is that it is a basic text file so I can import it over to any computer with MySQL, load it up, and ...
I would consider using a WordPress plugin called "WordPress Database Backup (WP-DB-Backup)" which is also listed on the Wordpress Database backup guide. This plugin can backup the database on a schedule and email it to you(assuming its a small database). You can also just back it up locally. You can exclude comment spam and revisions to make the DB smaller ...
Whichever backup solution you go with, realize that backups are worthless if you don't test them. This means, having a restore strategy, and actually simulating a complete recovery. You don't have to kill your production data to do this, but you need to make 100% sure that you can actually recover what you need to using your backups. Also version control ...
Only top voted, non community-wiki answers of a minimum length are eligible