#Backup buddy restore update
#Backup buddy restore code

The backup is stored on your site, within the uploads directory, and you have the option to email it, FTP it or send it to an Amazon S3 bucket if you have an Amazon Web Services account. You can back up your entire WordPress site or just the database. In fact, I like BackupBuddy more than any of the other backup solutions I’ve used. I bought a license, downloaded the BackupBuddy plugin, installed it into my WordPress site and took it for a whirl.īackups work. Maybe not.ĭespite the doubts, I decided to give it a try. So, maybe it was the balm for my WordPress anxiety. I read other, glowing, reviews and realised they weren’t reviews at all but simply sales affiliates repackaging the words from the BackupBuddy site. But some of those reviews were pretty old (why don’t people date ALL their blog posts?), and it was clear from other comments that the BackupBuddy people have been putting out revisions on a regular basis.

I read reviews, and found a few more problems. I don’t use GoDaddy I use 1and1, which is mostly smooth as silk but it does have a few quirks when interacting with WordPress. A lot of those problems were host-related in particular, GoDaddy appears to be a nasty piece of work in many ways. I started reading support forum messages and noticed that some people were having problems. Could it be?Īnd then I discovered BackupBuddy.

#Backup buddy restore update

So I ignored the update banner each time I logged in. Even though I had plenty of backups (really, I was over-backed-up using three different systems to get some sense of security), I had yet to find a single tutorial, codex or solution which gave me confidence I could restore my site if disaster struck during the upgrade. x.x updates completely screw up a crucial plug-in before, should I risk this update now? And when WordPress 3.0 was urged upon me – not just a bug fix but a major update! – I decided the wisest course was to ignore it for as long as possible. The banner across the top of the WordPress dashboard saying “WordPress 2.x.x is available. Once I realised the peril of working with WordPress, small things started to terrify me. The trouble isn’t with backing up and reinstating the database or the core files or your own files the trouble comes when you try to restore everything including all the settings for each of your plug-ins, the correct page links, the comments on your blog entries, all the nitty gritty details and linkages which took you for ever to perfect in the first place. But when it comes to restoring all that stuff…well, then you’re heading into the WordPress twilight zone. Oh, there are plenty of options for backing up your system, such as VaultPress and the DB Manager plug-in – some of them back up the database, some your files, and some even back up everything.

#Backup buddy restore code

The way WordPress dumps most of your content and settings into an SQL database (come on – how many of you really understand that database?), then combines that with core code, theme code, plug-in code and your own media and other uploads that makes for a dog’s breakfast when it comes to protecting your site from a meltdown. After moving my website to WordPress, I soon came to realise that while it’s great to work with, it is peculiarly vulnerable to disaster. A huge number of people contribute plug-ins, themes and other bits and bobs which enhance an already powerful core.īut…it’s scary as all get out, too. Not easy, but easy enough, and filled with such endless possibilities.

This open-source blogging platform is a wonder to use.