Support

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 I Searched all
Joomla! version: 3.1.5
PHP version: 5.4.19
MySQL version: 5.1.69-cll-lve
Host: awn-archeologie.nl
Akeeba Backup version: 3.8.2 (2013-09-30)

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:
two questions.
1. In the log several times the same warning is present.
Can i get do something against it?
PHP WARNING on line 122 in file <root>/administrator/components/com_akeeba/akeeba/drivers/mysql.php: mysql_close(): 41 is not a valid MySQL-Link resource

2. A backup stopped at 16:47:11 I do not know the reason. When i tried again to backup, it worked succesfully. What can i do to prevend the backups to end unsuccesfull?
In the attachment you see the unsuccesfull first backup run.

Thanks in advance

Can you please try again attaching the backup log? You will probably need to zip the log to keep it under the file size restrictions.

I wil try again to attach the log

It looks like you have multiple sites that you are backing up in a single archive. The way you are doing this would make restoring a single site very difficult. Did you mean to backup multiple sites, or did you intend to back up only one?

I know my site has 10 subsites. Called /00 resp /01 etc
I plan to restore all 11 sites on my localhost when neccessary. And copy to the server only the corrupted subsite. I am aware that the database prefixes of subsites cannot be changed during Akeeba restore in my case. I tested the restore to localhost, it worked fine.

Making 11 seperate backups takes more time for me to logon and start the backup, so i was happy with 1 job backing up 11 sites.

You are right, the backup is easy, the restore to your localhost is fairly easy. The hard part is if you blow up subsite #5 during an upgrade and you want to restore just that one site. It can be done, but there are steps involved that would be outside the comfort level of many of our users. You may wish to consider setting up the individual backup jobs as CRON jobs and let them go off in the middle of the night while you are sound asleep. :-)

It looks like you need to reduce the size of your backup parts just a little bit. The first three parts were uploaded fine, but the fourth looks like it timed out. You are right on the edge with that part size.

Okay i will try to settup individual jobs. I will try to make CRON jobs on my server. But each backup has to exclude a lot of database prefixes. I have not yet found a way to exclude several hundreds of tables from each backup.

Thnaks for your second advice as well:
Where can I lower the size op my backup parts a little??

Would we make you manually exclude all those tables? :-)

Under Exclude Database Tables, at the top, click the Exclude non-code tables button. That will exclude all the tables from the other sites. Now, be careful if you have a forum or gallery or something like that which does not use the standard Joomla! table prefix because those tables would be excluded too.

Under Configuration, Advanced Configuration, Archiver Engine, make the Part size for split archives a little smaller.

Thanks a lot.
I did find the "exclude non-code table" button

And found the size filed as well.

I'm glad you found it even with my typo!