Troubleshooting problems with Akeeba backup
Akeeba Backup support has been integrated into Watchful to provide a reliable backup service for your websites.
If your site has a problem performing backups with Akeeba of the following errors may be displayed:
- Invalid JSON data or error with remote backups
- Invalid Body data
- Access Denied
- Cannot step backup
Most of these problems and any other issue can be addressed using one of the solutions below:
1. Ensure site is connected to Watchful
The first step is to make sure that the site is properly connected to Watchful. A site that is properly connected to Watchful will show a green check mark in the Connection column in your Watchful Dashboard.
2. Ensure Offline Mode is disabled in Joomla
Ensure that the site in question is online (i.e. offline mode is disabled) in the Joomla Global Configuration.
3. Match HTTP or HTTPS
Ensure that the URL of your website matches what is entered in the site details in Watchful, including wether or not you are using HTTP or HTTPS.
4. Enable Frontend Backup
In order for Watchful to be able to control backups, you need to enable Frontend Back in the Akeeba Backup Options. Full details on this can be found elsewhere on the Knowledge Base.
5. Verify the Akeeba Secret Word
In order for Watchful to be able to control backups, the Akeeba Secret word (which can be found/modified in the must match in the Akeeba Backup Options and in the Watchful Site Details). Full details on this can be found elsewhere on the Knowledge Base.
6. Ensure the Akeeba Secret Word only contains alphanumeric characters.
This is the official recommendation found in the Akeeba Backup Documentation.
7. Make sure the site backup works normally from the website backend.
Confirm that backups performed from the backend of your site are working normally. If the backup is failing from the website backend, it will also fail when performed remotely from Watchful.
8. Make sure your site has enough disk space for your backups.
One of the most common problems users experience when troubleshooting issues with Akeeba Backup is disk space. This is especially true for large web sites.
So if you are having backup problems, be sure that your server or hosting account has enough available disk space to complete your backup. We recommend that you have at least twice as much free space as required for your backup.
8. Ensure the output directory has the correct permissions
The output directory is used to write files during the backup process and the path to this directory can be fund in the configuration details for the Akeeba profile you are using.
Ensure that the Akeeba output directory has the appropriate permissions to allow writing, usually CHMOD 0755.
9. Delete any akeeba_json files.
When remote Akeeba backups are triggered from Watchful or the frontend of your site, a file called akeeba_json is created in the following location:
akeeba_json is used as a flag that prevents additional remote backups from starting and is normally deleted when the remote backup process is complete.
A failed backup can sometimes leave akeeba_json in place, thus preventing new backups from starting. These files can be safely deleted if no backup processes are running.
10. Optimize your Akeeba Backup profile using the Configuration Wizard.
Akeeba Backup includes a Configuration Wizard that will optimize the settings in your Akeeba Backup profile to the server on which your site is installed. Run the Configuration Wizard and see if the modified profile resolves the backup problem (see details from the developer documentation).
11. Use split archives when uploading to remote storage.
If you are uploading your backups to remote storage locations like Amazon S3, CloudFiles, or a private FTP server, it is important to limit the size of the files being transferred. One way to do this is to split Akeeba Backups into smaller parts and upload each part as they are ready.
The following screenshot shows the relevant options for a uploading Akeeba Backups to CloudFiles (the options are identical for all of the remote storage services). Try reducing the part size in 50% steps until the backups from Watchful complete normally.
12. Use the database for temporary data storage
In some cases, using the database (and not the file system) produces more reliable backups. To enable this feature, visit the Akeeba Backup configuration page and select the "Use database for temporary data storage" option in the first section of that page.
13. Update any SEO tools for Joomla
Joomla users with the outdated versions of following extensions have reported errors performing remote Akeeba backups:
- SEF Advance
In addition, these sites also experience problems triggering Akeeba backups directly (i.e. not via the Watchful dashboard, but by accessing the CLI directly).
The problem is caused by a flaw in these URL management extensions that corrupt the backup requests (and any other JSON requests, full details are here).
sh404SEF is fully compatible with the Akeeba Backup CLI. No further action is required.
AceSEF can be configured for use with the Akeeba Backup CLI.
- Upgrade to the AceSEF version 2.5.2 or greater Disable the following variables to by adding them to the Disable Variable list. This is found in
AceSEF > Configuration > URL > Global variables > disable-SEF variables
ArtioSEF, SEF Advance
The Akeeba Backup CLI is not compatible with ArtioSEF or SEF Advance. You will need to disable the plugins associated with these extensions.
You may replace their functionality by installing a compatible SEF manager like sh404SEF.
- Configuring remote backups for Joomla
- Configuring remote backups for WordPress
- How do I generate reports for my clients?
- How do I use the Site Audit?
- How do I use the Watchful REST API?
- How often does Watchful monitor my web sites?
- How to backup a site in Watchful
- How to create a Watchful App
- How to make plugins and extension updates compatible with Watchful
- Installing the Watchful client