Support

The log excerpt you pasted does not contain enough information to diagnose the problem. Please provide the complete log file.

Go to Akeeba Backup, Manage Backups.

Find the records of the failed backup and click the View Log button in its right-hand column.

Click the Download Log File button towards the top of the page, next to the log file selector drop-down.

This downloads a .txt file. Put that file inside a ZIP file.

• If the ZIP file is under 10 MiB: attach it to your next reply
• If the ZIP file is over 10 MiB: upload it to Dropbox, then paste me a public share link in your next reply

The log file tells me what is going on during backup – including the upload stage, if it's actually reached that step. Let me look at that file so I can give you a much better suggestion about what to do next.

Regarding table exclusions: the regular Database Table Exclusion filter does not support wildcards. If you want to exclude all tables matching a pattern — for example, all tables whose name starts with sv_bookpro3 — you should use the RegEx Database Table Exclusion filter instead. The corresponding regular expression would be /^#__sv_bookpro3/.

All filters in Akeeba Backup — including the RegEx Database Table Filters — are part of the backup profile. There is no separate "linking" step.

You simply need to make sure the correct profile is selected on the Akeeba Backup main page (the control panel) before navigating to any filter page. Whichever profile is active there is the one your filters apply to. So the workflow is:

1. Go to the Akeeba Backup main page.
2. Select the profile you want to configure from the profile selector.
3. Navigate to the RegEx Database Table Filters page. The regex you enter there will be saved as part of that profile.

This has been how backup profiles work since they were introduced — a profile consists of its configuration options and its filters together.

Regarding the Files and Directories Exclusion page: the meaning of each column and the icons in it are explained in our documentation. The same applies: select the correct profile on the main page first, then configure your directory exclusions.

Regarding notification emails: our site has sent them from [email protected] to the email address on your account. From that point, delivery is in the hands of your email provider and mail client, which is outside our control.

The steps below are exact. Please follow them in order.

Step 1 — Select the correct profile

Go to Components > Akeeba Backup. This takes you to the main Akeeba Backup page.

At the top of that page there is a profile selector drop-down. Click it and select the profile you use for your backups ("Profil EXCLUE 2 tables et media/k2 + images" or whichever one you run the backup with). Do not navigate away from this page yet — just select the profile.

Step 2 — Open the RegEx Database Table Filters

Still on the Akeeba Backup main page, click on RegEx Database Table Filters in the left-hand sidebar. Because you selected the profile in Step 1, this page is now showing the filters for that profile.

Step 3 — Add the exclusion

Find the field labelled Exclude tables (not "exclude rows" or any other option — specifically "exclude tables"). Click the Add button next to it and enter:

/^#__sv_bookpro3/

Then click Save.

Step 4 — Confirm

Run the backup again. The tables whose names start with sv_bookpro3 will now be skipped entirely.

Regarding the Files and Directories Exclusion: our documentation has an index. The section you need is titled Files and Directories Exclusion — which you can find directly at https://www.akeeba.com/documentation/akeeba-backup-joomla/exclude-data-from-backup.html#files-and-directories-exclusion. The same rule applies: select the correct profile on the main page first.

We link to the documentation rather than reproducing it here for three reasons. First, copying it into every ticket would make replies very long and hard to follow. Second, it is written by the same people who answer support tickets — we can only explain the same thing in so many ways. Third, and most importantly, the documentation is kept up to date with every release; a ticket reply is not. Anyone reading this ticket in the future — including yourself — will find current, accurate information by following the link, rather than instructions that may no longer reflect how the software works.

Regarding the complete log file from the original stalled backup: we have asked for it twice now and have not received it. We cannot diagnose why the backup is stalling without it. If we do not receive the complete log file in your next reply, we will have no choice but to close this ticket as unsolvable — not because we do not want to help, but because we simply cannot help without the information needed to troubleshoot.