Akeeba Backup for Joomla!

Thursday, 06 April 2017 07:38 CDT

dewittds

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:
Just found out that full backups are failing, database only backups seam to complete fine. I do db backup daily and full at the first of the month. Backups are going to amazon S3. I have the backups made using the Schedule automated backup.

Yesterday I tried to manualy start backup. It ran to around 71% then the percent showing jumped back to 67% and then 74% and got no higher.
Log file attached .

added note: Was just looking at the "manage backups" screen looks like full backups that completed in past show size around 2.6GB, but failed backups 3.16 and larger. and the manual backup yesterday shows 15.81 Gb

Thanks for your help,
David DeWitt

Edited by dewittds on 2017-04-06 07:46 CDT

Thursday, 06 April 2017 08:02 CDT

nicholas

In the last few lines of the log you can see that the problem is that you have another site inside the main site. Namely, inside the testdsd3 directory. You should exclude this directory.

Otherwise, at the very least, please exclude the default backup output directory (testdsd3/administrator/components/com_akeeba/backup).

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!

Thursday, 06 April 2017 10:16 CDT

dewittds

After excluding that test directory. The backup went off with out a hitch. So was the problem a amount of information in the backup or that it saw another copy of Akeebe backup?

Thanks,
David DeWitt

Friday, 07 April 2017 08:00 CDT

nicholas

Yes and no. The amount if information by itself is not a problem. I know of two sites which successfully back up to 64Gb and just a hair sort of 100Gb without a hitch. However, this is not the typical case :) In most cases you have things getting in the way such as physical free space on the storage unit (hard storage limit), filesystem inode count limits (soft storage limit), maximum CPU usage over a period of time, I/O usage restrictions, network interface stability, timeout limits and so on and so forth. If you hit one of these server limits you can't continue running the backup. The more data you try to back up the more likely it is that you hit a limit.

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!

Sunday, 07 May 2017 17:17 CDT

System Task

system

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.

Edited by on 2017-05-07 17:17 CDT

Support