This feature is available only in Akeeba Backup Professional.
By default, Akeeba Backup automatically includes the whole database of your Joomla!™ installation as well as all the files under your site's root in the backup set. Sometimes you want to include a different database or files you have placed above your site's root for increased security. Akeeba Backup Professional can cope with that need by providing you with handy data inclusion filters.
This feature is available only in Akeeba Backup Professional
Sometimes your site may use more than one databases. Taking a full site backup requires backing up those external databases too. Normally, Akeeba Backup only backs up the tables from your Joomla! database. The solution to this problem is the Akeeba Backup. You can define an unlimited number of additional MySQL, PostgreSQL, Microsoft SQL Server and Windows Azure SQL databases which will get to be backed up (and restored) along with your regular Joomla! database.option of
Please note that you do not need to and, in fact, must not use this feature to add the main database of your site (the one used by Joomla! itself). The main database of your site is backed up automatically. If you ignore this warning and add your main database as an additional database in this page you will cause errors during the restoration of your site.
Moreover, you should not confuse the term "database" with your Joomla!™ tables. It is possible that a single database contains tables for the current Joomla!™ site, tables from a third party script, tables from another Joomla!™ site on the same server (e.g. a subdomain) and so on and so forth. As far as Akeeba Backup is concerned, all of those tables exist in the same database regardless of their prefix. Unless you tell it otherwise, it will backup ALL tables of the database.
Finally note that if you add an empty database (one which has no tables) it will result in backup errors!
The settings on this page are defined per profile . Make sure you have selected the desired profile in the page.
Multiple Databases Definitions
At first, you are presented with a grid view, listing all database definitions. On the left of each entry, there are two icons:
The trashcan. Clicking on this icon will remove the current database definition from the backup set.
Pencil or Add. Both will open the database definition editor: the former to edit the database definition, the latter to create a new one.
Multiple Databases Definitions - The editor
The database definition editor opens as a dialog box inside the multiple databases definitions page. The options you can select for each database are:
Database driver. You can select which database driver Akeeba Backup will use to connect to the database. Your options are:
MySQLi. This is the modern MySQL connection driver. We recommend using it for MySQL, Percona and MariaDB databases.
MySQL. This is the old, obsolete MySQL connection driver for PHP. It has bad performance and has been removed in PHP 7.
PostgreSQL. Connection to a PostgreSQL database.
SQL Server. Connection to a Microsoft SQL Server database. You must be running your site on a Windows server and have the Microsoft-supplied "sqlserver" PHP extension installed.
Windows Azure SQL. The same thing as "SQL Server". Windows Azure SQL databases are, in fact, Microsoft SQL Server databases running in a remote machine. You must be running your site on a Windows server and have the Microsoft-supplied "sqlserver" PHP extension installed.
Database server hostname.
The host of your database server. Usually it's
localhost, but many hosts use something
different. If in doubt, ask your host. Please remember that for
MySQL servers the settings
127.0.0.1 are NOT the same. The first means
"connect using a socket or named pipe" the second means "connect
using TCP/IP networking". If you are on Windows they have a
massive performance difference as well.
Database server port. Leave it blank, unless your host has told you to use a non standard port for connecting to their database server.
Username. The username of the database user needed to connect to the database.
Password. The password of the database user needed to connect to the database.
Database name. The name of the database you are connecting to.
Prefix. The prefix used
in the table name's prefixes. MAJOR
PITFALL: Please do not leave the Prefix field blank
if you intend to use the Database Table Exclusion feature to
exclude tables or table data of this extra database from the
backup. If you don't want to use a real prefix, please use a
"fake" prefix, e.g.
thisIsAFakePrefix_ , to
keep the Database Table Exclusion feature happy and
Some hosts use your account name as a prefix for the database
and username. This is not the same as the
Prefix setting above. That database and username prefix
is actually part of the actual database and username that you need
to fill into this page. For example, you're hosted under the account
foobar and you create a database
mydata and a user
host displays a prefix
foobar_ on the left of the
edit boxes where you entered the database and user names. This means
that your REAL database name is
your real username is
foobar_myuser. This is
especially true for accounts hosted in cPanel and Plesk powered
hosts. It goes without saying that your password does NOT take a
prefix. If in doubt, please contact your host. We can't guess the
right values for you because we are not your host. If you ask your
host to give you the connection information to your database, they
must be able to do so - except for the password which they obviously
cannot see for security reasons.
When you think you have all the connection information ready, click on Prefix. The connection test will tell you if it succeeded or failed.. This will check all settings except the
If your connection works properly, it's time to save your changes by clicking thebutton. The top panel will briefly display a "loading" message and the dialog box will go away. That was it, your extra database definition is now saved.