Updated Jul 15, 2016 (Originally Published Jul 14, 2016)
I am using Akeeba Backup Professional for WordPress.
And, I am using Akeeba Backup Solo Professional for my Laravel web applications.
Akeeba Backup Professional for WordPress
The wonderful thing about WordPress is its infinite availability of plugins. So there shouldn't be a problem finding a long established full featured backup plugin for WordPress, right? Well, for me, the answer is wrong.
Over the years, my dissatisfaction with free and commercial backup plugins has me searching again and again for backup plugins. Backing up the database and uploading it to Amazon's S3 is definitely covered, no trouble finding a plugin for this. The site files, and restoration? Well, that's a different matter.
What I've found over the years is that backing up the WordPress folders and files is trickier than it appears. One reason is that errors emanate from the webhost, not from WordPress (or MySQL). Sometimes errors happen because of differing PHP versions. Sometimes the backup works but the upload to Dropbox or Rackspace or whatever fails. Yeah, there's a lot of cloud storage outfits to keep up with. And, y'know, WordPress users just want plugins "to just work". When it comes to backing up, it's enormously difficult to have it "just work" when there are so many potential externally based points of failure.
Restoring WordPress sites is not fully straight forward. Site URLs are stored in the database where they really shouldn't be in the first place -- confession: this little WordPress twist-and-turn so infuriates me that I refuse to fully understand it! Suffice to say, you have a development site, and now you want to go live on the live URL, you can't just import the database straight up.
I've seen some pretty whacky plugins that "import" and "export" WordPress sites. People who need to move WordPress sites around concocted their own plugins to deal with the WordPress idiosyncracies, and ended up publishing them. My hats off to people who release free open source software. But there's a certain point where I'm not interested in, essentially, reverse engineering peoples' home made solutions to idiosyncracies baked into the core software.
It's no secret that I'm a huge fan of Akeeba Backup for Joomla. I've had the pleasure, and a pleasure it was, interviewing Akeeba's founder many times in the old days of my The Bob Bloom Show (https://southlasallemedia.com/tbbs48). Nicholas has been through it all dealing with all the sordid issues involved backing up Joomla sites. It really does seem so straight forward at first, but it's incredible how un-straight-forward it becomes. I could not fathom doing a Joomla site without Akeeba Backup.
So, when Akeeba Backup for WordPress came out, I was very excited. It took some time transmuting this wonderful Joomla extension into a WordPress plugin. A journey worthy of another podcast! Suffice to say, it was successfuly transmutted.
Now, I cannot fathom doing a WordPress site without Akeeba Backup Pro for WP.
The combination of Rochen.com hosting and Akeeba Backup is, so far, incredible. My Akeeba Backup CRON jobs -- they all upload to AWS S3 -- have 99% success (can never bat 1.000, eh!). Small database files, large full site archive files -- they all work (except for an outlier here-and-there), unattended, in the middle of the night, via CRON jobs.
Restoring an Akeeba backed up WordPress site is straight forward (and GUI based), once you get the hang of it. The WordPress idiosyncracies are handled well.
Akeeba Backup Solo Professional -- for Laravel!
For my Laravel web applications, I want to use a Laravel backup package. I want it Laravel all the way. Except, that, and does this sound familiar? I am unsatisfied with the backup packages. There's just not enough functionality to them.
It's fabulous that people publish free open source software. The backup packages hook in beautifully with Laravel -- and Forge. They use the Symfony console. They upload to S3. There is nothing wrong with the backup packages I tried. I wanted more functions, so, I forked a package. And, then, I deleted it.
What's more valuable? Using a Laravel based backup package, or installing Akeeba Backup "Solo" Pro? This is the standalone version of Akeeba Backup Pro.
Yes, a standalone version of Akeeba Backup.
So I tried it last night. Set up a subdomain on my DigitalOcean-slash-Forge-slash-Envoyer droplet. First time I set up a subdomain -- figured it out. First time I set up a subdomain for LetsEncrypt SSL -- figured it out.
Akeeba Backup Solo Professional works, and works beautifully. The one install backs up, with individual backup jobs, each database, and each set of files. Akeeba Backup sees the droplet's file structure, so I can have one job backup "/home/forge/domainONE.com/storage/images", and another job backup "/home/forge/domainTWO.com/storage/images". With Envoyer's symlinks, this is no moot point. Also, unlike backing up WordPress, I do not want to backup the entire folder structure of my app that resides on the droplet; rather, I only want to backup files that originate from the app's usage. Such as user uploaded images.
Kudos to the Akeeba Team for bringing their mature, full featured backup software to my Laravel web apps!