Support

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? No
Have I searched the forum before posting? No
Have I read the documentation before posting (which pages?)? No
Joomla! version: (1.5.23)
PHP version: (5.2.17)
MySQL version: (5.0.51a)
Host: (Dreamhost VPS)
Akeeba Backup version: (3.3.2)

EXTREMELY IMPORTANT: Please attach your Akeeba Backup log file in order for us to help you with any backup or restoration issue.

Description of my issue:
Upon doing a backup I'm receiving a lot of AEDumpNative error warnings, I really need these database tables and was wondering if there were a way to back them up.

Example [110806 12:25:10] AEDumpNative :: Table akb_ak_profiles has a prefix of #__. This would cause restoration errors; table skipped.
[110806 12:25:10] AEDumpNative :: Table akb_ak_stats has a prefix of #__. This would cause restoration errors; table skipped.
[110806 12:25:10] AEDumpNative :: Table akb_banner has a prefix of #__. This would cause restoration errors; table skipped.
[110806 12:25:10] AEDumpNative :: Table akb_bannerclient has a prefix of #__. This would cause restoration errors; table skipped.
[110806 12:25:10] AEDumpNative :: Table akb_bannertrack has a prefix of #__. This would cause restoration errors; table skipped.
[110806 12:25:10] AEDumpNative :: Table akb_categories has a prefix of #__. This would cause restoration errors; table skipped.
[110806 12:25:10] AEDumpNative :: Table akb_components has a prefix of #__. This would cause restoration errors; table skipped.
[110806 12:25:10] AEDumpNative :: Table akb_contact_details has a prefix of #__. This would cause restoration errors; table skipped.
[110806 12:25:10] AEDumpNative :: Table akb_content has a prefix of #__. This would cause restoration errors; table skipped.

Any help would be great and thanks for providing a great product.

Thanks for taking a look at this, the only thing that I can say maybe the culprit of this abnormal naming of the tables would be a app we use for uploading products into VirtueMart. The component is called CSVI VirtueMart and during the last update it made some DB changes. Before this was done Akeeba was running fine as we just moved the site to a new server with the existing Akeeba free version and it worked fine.

I was prompted to go pro when I noticed the DB tables were not getting backed up..

Thanks for looking into this and let me know what you think would be the best process/adjustment going forward to ensure all db tables are getting backed up.

Wade