Support

I am trying to perform a backup, triggered manually in the Joomla admin interface and with no post-processing enabled. (Context: I am attempting to create a development copy of the production website in order to upgrade from Joomla 2.5.28 to 3.7.) During the Backing up files portion of the process, I get a message on screen saying the backup has been suspended, with the following information:

BACKUP HALTED AND WILL RESUME AUTOMATICALLY
The backup operation has been halted because an error was detected. However, Akeeba Backup will attempt to resume the backup. If you do not want to resume the backup please click the Cancel button below.

The backup will resume in	2 seconds	
 Cancel    Resume

For your information, the last error message was:

Cannot save factory state in db storage, storage key backend.id43

Shortly after this message is displayed, the screen goes back to the Initialising backup process stage and seems to remain there indefinitely.

I have attached the log file.

I have read the troubleshooting article here and followed these steps:

1. I am not on Windows. The site is hosted on a Linux server.
2. I have disabled uploading to remote locations (no post-processing).
3. I have run the configuration wizard.
4. The PHP memory limit is set to 128MB.
5. I have clicked Save on the Configuration page.
6. There are 6.5GB of free space on the server. I believe this should be enough given I have excluded from the backup the directories with large files (documents and images in particular), though I am not sure how to tell for certain. Note that my first backup attempt (before excluding these directories) resulted in the server becoming full up and the website ceasing to work correctly. Deleting the backup from Akeeba Backup corrected this problem and since then I have not seen large amounts of disk space being used as part of the backup process.
7. I'm running on a VPS which I have full control over, so no one is clearing out any temporary directories.
8. I am using the JPA archive format.
9. I lowered the maximum execution time to 5s (from 30s, configured by the wizard) and reran the backup process. The same thing happened (error message displayed on screen was "Cannot save factory state in db storage, storage key backend.id44").

AWESOME troubleshooting! :-D

Let's go to Configuration, in the Basic Configuration section at the top, and flip the value of the "Use database storage for temporary data" checkbox. If it is checked, uncheck it, if it is unchecked, check it. That changes the way the temporary data is stored. That may be what it was trying to do when it stopped.

If that doesn't fix the problem, please reinstall your Akeeba Backup 4.7.4 twice, back to back, without doing anything in between. Do not uninstall, that will cause you to lose all your settings and possibly your stored backup archives. There is a possibility that you have a damaged installation of Backup, this would fix it.

Dale,

Thanks very much for the swift response! I should have been more optimistic — your documentation suggested a minimum waiting time of 12 hours for support, so I went ahead and uninstalled and reinstalled before seeing your response. So while the bad news is that you're right, I've lost some settings and some (not very important) historical logs/backup records, the good news is that it is now working!

FWIW, I had previously upgraded from version 3 of AkeebaBackup, perhaps that is what led to the issue.

Thanks

Michael

We try to do better than 12 hours but it depends on the type of problem and time zones and a host of factors.

The most important thing is that it's working!

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.