Support

Akeeba Backup for Joomla!

#8895 Recommendations for managing backups of multiple sites

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Friday, 10 June 2011 08:58 CDT

piggybank
Looking for some best practice recommendations (and maybe a paradigm shift in my thinking!)

I've been using Remote to manage the backups of my Client sites (approx. 100 sites). I don't download to my local computer; rather, I use Amazon S3.

With the recent news of Remote no longer being developed (and yes, I do appreciate and accept the logic) I am planning on phasing out my use of Remote.

What I liked about using Remote is that when it ran, I could see my sites backing up and that visual gave me some warm, fuzzy assurance that all was well.

At the moment, I'm thinking that my new set-up should be to: (1) set-up each site to use Native CRON script (professional version), (2) configure Backup to Email on backup completion.

Thoughts?

nicholas
Akeeba Staff
Manager
Here's what I use, albeit on a much lower number of sites.

All of the sites are backing up to Amazon S3 using the native CRON script method. The CRON daemon can optionally send you the output of the command it runs by email. In cPanel, it's as easy as typing in an email in the email box and clicking Submit.

Here's the tricky part: knowing which sites have backed up, which haven't and which backed up with errors. First, we can assume that CRON itself either runs or not. It's a system-wide service, it's been around for decades (yes, it's that old), so the command "not running at all" is not something to worry about. Therefore, we are left with two possibilities:
a. The CRON job runs to successful completion, or
b. The CRON job runs but, for whatever reason, fails
Industrial automation dictates that if there is no error, do not notify the operator (saves the operator from excessive feedback which would make identifying an error condition impossible). Extending that principle to site backup, we would ideally need to be notified by email if and only if a backup fails. That's easy, with mail filters!

Every successful backup prints at the first line something like "Akeeba Backup CLI svn563 (2011-04-16)" and at the last line something like "Backup job finished successfully after approximately 3 minutes". So, we need three rules, in the exact following order (if the first matches, the other should not execute):

1. Successful backup. The message body contains "Akeeba Backup CLI" and "Backup job finished successfully". In this case, trash or move to a folder for safekeeping.
2. Backup with warnings. The message body contains "Akeeba Backup CLI" and "POTENTIAL PROBLEMS DETECTED;". Move it to a mail folder named "Backups with Warnings".
3. Failed backup. The message body does not contain "Backup job finished successfully" and the sender is our CRON daemon (in the case of my site it's something like [email protected]). Move them to a mail folder named "Failed backups"

This way you have your realtime report of backup statuses per domain in a convenient email format. Moreover, instead of having to spot which one of your 100 sites did not email you about backup completion, you only have to spot which one did mail you about a problem. Ta-da! Simple and sweet :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

piggybank
Brilliant...love those Email filters. Thanks for sharing!

nicholas
Akeeba Staff
Manager
You're welcome! Sharing is caring :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!