Mandatory information about my setup:
Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: (2.5.4)
PHP version: (5.2.17)
MySQL version: (5.0.90)
Host: (dedicated cloud Apache/2.2.3 (CentOS) with plesk)
Akeeba Backup version: (3.5.1 pro)
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:
Hello,
First of all I must say that I'm not sure if this problem is caused by akeeba backup, but it is the most resourse intensive task it's made on the server, so I took a look at the logs and I saw the error, so maybe you can can give me the solution.
The problem I see in the server is that the databases get broken in time. I have 4 or 5 akeeba backup cron tasks on the server for some big databases about 50 mb. The backups are uploaded to Dropbox.
The poroblems I see in the server is that the tables get Overheaded and in some cases all the system crashes and I see in all my domains could not connect to mysql...
I've set up a cron task that repairs the databases every 30 minutes [mysqlcheck -Aaos -uUSER -pPASS] but this problem was not happening before. Ok my server is very busy in this dates, but, I did not made a lot of changes to the software, only updating plesk and joomlas... I think that this should not be happening...
As I told before I'm not sure if the database degradation is cause by akeeba backup but, I saw the eror on logs so I would like to know if this could be the reason MySQL is breaking.
Sorry for any inconveninece
Best regards
Xavier Pallicer
http://www.cloudhotelier.com
Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: (2.5.4)
PHP version: (5.2.17)
MySQL version: (5.0.90)
Host: (dedicated cloud Apache/2.2.3 (CentOS) with plesk)
Akeeba Backup version: (3.5.1 pro)
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:
Hello,
First of all I must say that I'm not sure if this problem is caused by akeeba backup, but it is the most resourse intensive task it's made on the server, so I took a look at the logs and I saw the error, so maybe you can can give me the solution.
The problem I see in the server is that the databases get broken in time. I have 4 or 5 akeeba backup cron tasks on the server for some big databases about 50 mb. The backups are uploaded to Dropbox.
The poroblems I see in the server is that the tables get Overheaded and in some cases all the system crashes and I see in all my domains could not connect to mysql...
I've set up a cron task that repairs the databases every 30 minutes [mysqlcheck -Aaos -uUSER -pPASS] but this problem was not happening before. Ok my server is very busy in this dates, but, I did not made a lot of changes to the software, only updating plesk and joomlas... I think that this should not be happening...
As I told before I'm not sure if the database degradation is cause by akeeba backup but, I saw the eror on logs so I would like to know if this could be the reason MySQL is breaking.
Sorry for any inconveninece
Best regards
Xavier Pallicer
http://www.cloudhotelier.com
