Support

You need to purchase a subscription to Akeeba Backup for WordPress and another one for Akeeba Backup for Joomla. Purchase one, wait until it's active, then go ahead and purchase the second one; you will get an automatic 50% discount. This means that you are paying a total of 75 Euros for the first year and 45 Euros every year for renewal, as long as you renew it before it expires. An email is sent to you a month, and again two weeks, before the subscription's expiration to remind you. Note that the prices I quoted apply only for the self-service checkout and do not include any sales tax, if applicable.

You can use Akeeba Backup Professional on as many sites as you want; there is no restriction on the number of sites, domains, or servers.

You can set up backup profiles in Akeeba Backup to automatically upload the backup archive file(s) to Amazon S3 — or a number of different remote storage providers.

You can automate your backups in many different ways:

• Using regular CRON jobs, with the included CLI script (recommended) on WordPress and Joomla 3.
• Using regular CRON jobs, with WP-CLI on WordPress or the built-in Joomla CLI application on Joomla 4.
• Using URL-only CRON jobs, accessed from the same or a different server, or third party service.
• Using WordPress' built-in WP-CRON (not recommended, unless you are triggering WP-CRON every minute with an external CRON job).
• Using Joomla's built-in Scheduled Tasks feature (not recommended, unless you are triggering the Scheduled Tasks runner every minute with an external CRON job).
• Using a third party service, such as Watchful.net or BackupMonkey.io. These services typically work for both Joomla and WordPress sites; please consult their marketing material, as we are not affiliated with them in any way. Also note that these services charge you on top of what you pay to us. We only recommend using a third party service if setting up CRON jobs, either command-line or URL-only, is not possible on your server. Seeing that you have your own servers I don't think you'll need to even consider that option, but I thought it's worth mentioning it for completeness' sake.

You can even have different backup profiles. For example, you could be running a more limited backup of only critical database tables and files every hour or few hours with one profile, and a full backup at the end of the day.

You can also set up backup retention rules, including an age-based rule where you can tell Akeeba Backup to, for example, keep the last 30 days of backups (rolling) and always the backups taken on the 1st day of every month. For simple retention policies it is simpler than setting up lifecycle policies on the Amazon S3 bucket.

Feel free to ask any more questions you may have. I'm here to help!