Support

Akeeba Backup for Joomla!

#13533 Obsolete backup with DropBox

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 on Sunday, 21 October 2012 18:00 CDT

michael-rothmann

Description of my issue: Obsolete backup with DropBox
Menu: Administer Backup Files

Backup transferred to DropBox used to work but are now marked as “Obsolete” and no info is included under “Manage & Download”.
The backup is transferred and is present in my DropBox though.
I know I cannot manage files transferred to DropBox but at least I use to get an “OK” and the filename listed.
(Local backup works fine and can be managed in the normal way)

Joomla! version: 2.5.6
PHP version: 5.3.10
MySQL version: 5.1.63-cll
Host: chosting.dk (cloud Linux)
Akeeba Backup version: PRO 3.6.3
Akeeba Backup log file uploaded/attached

Thanks in advance
Best regards,
Michael Rothmann

nicholas
Akeeba Staff
Manager
Can you please run
SHOW CREATE TABLE h2ox_ak_stats
in phpMyAdmin and give me the result here?

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!

michael-rothmann
Note: table prefix was changed to h2oy

SQL result
Host: localhost
Database: h2odk_joomH2O
Generation Time: Sep 14, 2012 at 09:49 AM
Generated by: phpMyAdmin 3.4.10.1 / MySQL 5.1.63-cll
SQL query: SHOW CREATE TABLE h2oy_ak_stats;
Rows: 1
Table Create Table
h2oy_ak_stats
CREATE TABLE `h2oy_ak_stats` (
`id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
`description` varchar(255) NOT NULL,
`comment` longtext,
`backupstart` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`backupend` timestamp NOT NULL DEFAULT '0000-00-00 00:00:00',
`status` enum('run','fail','complete') NOT NULL DEFAULT 'run',
`origin` varchar(30) NOT NULL DEFAULT 'backend',
`type` varchar(30) NOT NULL DEFAULT 'full',
`profile_id` bigint(20) NOT NULL DEFAULT '1',
`archivename` longtext,
`absolute_path` longtext,
`multipart` int(11) NOT NULL DEFAULT '0',
`tag` varchar(255) DEFAULT NULL,
`filesexist` tinyint(3) NOT NULL DEFAULT '1',
`remote_filename` varchar(1000) DEFAULT NULL,
`total_size` bigint(20) NOT NULL DEFAULT '0',
PRIMARY KEY (`id`),
KEY `idx_fullstatus` (`filesexist`,`status`),
KEY `idx_stale` (`status`,`origin`)
) ENGINE=MyISAM AUTO_INCREMENT=18 DEFAULT CHARSET=utf8

BRGDS,
Michael

nicholas
Akeeba Staff
Manager
No, the table looks just fine. I want to see the raw log file. Go to View Log, choose backend, click on Download log file, it downloads a .txt file, put it in a ZIP and attach it to your next post. Make sure you have taken the backup from the site's back-end and the the log level in akeeba backup's config page is set all information and debug

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!

michael-rothmann

Log set to "all info and debug"
Backup taken from backend - local OK
Backup taken from backend - to Dropbox - Obsolete

Log attached

nicholas
Akeeba Staff
Manager
Please go to Akeeba Backup's Configuration page and find the Archiver Engine. Click on "Configure...". Set the Part size for split archives to 20Mb, then retry backing up. Does the backup now appear as "Remote"?

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!

michael-rothmann
Yes it works – I now get “Remote” (and split files in DropBox)
The limitation is not in transfer to DropBox though as backups are transferred fine at 67-117 MB

nicholas
Akeeba Staff
Manager
OK, that's what I thought :) The problem is with the database timeout. When you are transferring a large, single part archive (70Mb) it takes over a minute to do so. MySQL servers usually have a connection wait timeout (the time to keep an idle db connection open) between 1 and 60 seconds with the most common value being 30. Since the transfer takes more than that the db connection closes and when Akeeba Backup tries to write to the database that the backup archive is transferred (and not just obsolete) it can't.

By changing the part size each part's transfer takes less than this timeout. As a result the database is still connected after transferring the last part file and Akeeba Backup can now write to the database the information it needs about the backup being remotely uploaded and all.

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!

michael-rothmann
Sorry but I won’t settle for this solution if not a must!

I have contacted my host and they are willing to go along with my request.
The thing is, that I don’t have a clue what kind of time-out I should ask them to tweak.
Please advise if possible.
Screenshots of possible settings included.

Thanks!

nicholas
Akeeba Staff
Manager
You can't change that. It would require your host to change the MySQL wait_timeout. They are not likely to do that. If you increase that to, say, 120 seconds a script gone wrong can consume all MySQL server resources and screw up all sites on the server. Well, you can always ask them.

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!

michael-rothmann
As I wrote - my host are accommodating :)

They have raised the: interactive_timeout to 120 = no effect though!
Are you telling me they must set: wait_timeout instead? or both?
Any other timeout to tweak to kepp Akeeba happy?
(Please see attachment in prev. post)

Thanks!
Michael

nicholas
Akeeba Staff
Manager
You have to change the wait_timeout instead. At least this is what worked with another client who had the same issue.

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!

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.

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!