This page is the single place where you can review all your backup history, as well as administer the backup files. Each row represents a backup record and displays a whole lot of information:
Clicking the check box on the leftmost cell of a row selects this backup for an operation to be applied to it. Operations are activated by clicking on the tool bar buttons. In case of an operation allowing a single row to be selected, the topmost selected row is considered as the sole selection.
Displays the description you set when you started the backup. In case of front-end backups (taken without logging in to Akeeba Solo / your site), this contains the default description which was assigned. If your backup has a comment attached to it, an info icon will also appear. Hovering your mouse over the info icon will show you a preview of that comment.
Below the description you will see the backup ID (only
for certain backup types). The backup ID is always part of the
log file's name. So, for example, a back-end backup with
backup ID id1234 will have its actions logged to the log file
akeeba.backend.id1234.log found in the
backup output directory configured for this backup
The date when the backup started. The date is expressed in the server's time zone, as set in the System Configuration page.
The duration of the backup in hours : minutes : seconds format. This information is not available for failed backups!
Indicates the status of the backup and can be one of:
A complete backup whose backup archive is available for download.
A complete backup whose backup archive is either deleted, or was overwritten by another backup record.
If you move your backup output directory's location, all your previous backups will appear as "Obsolete", even though you might have moved these backup files as well. This is not a bug. The application internally stores the absolute path to the backup files. When you move the output directory its absolute path changes, so the application is unable to locate the old backup files.
Indicates a complete backup which has been uploaded to remote storage (e.g. Dropbox, Amazon S3, CloudFiles and so on), but it is no longer stored on your server. You can fetch the backup archive backup to your server any time (as long as you haven't manually removed the file from the remote storage) in order to restore it, clicking the Manage Remote Files link on the right-hand column.
Not all remote storage engines support fetching back backup archives.
A backup attempt which is still running. You should not see any such record, unless a backup attempt started while you were loading this page. In this case, you should not navigate to the main page! Doing so would invalidate the backup and cause it to fail. You have been warned! Another reason to see such an entry is a backup attempt which failed with a PHP fatal error, or which was abruptly interrupted (by the user or a PHP error). In this case, you can safely delete the entry and get rid of the incomplete backup file as well.
A backup record which failed with a catchable error condition.
Indicates the origin of the backup. You have the following possibilities:
Frontend for backups taken with the front-end backup method without logging in to Akeeba Solo / your site or with the alternative CRON script
Backend for backups taken when logged in to Akeeba Solo / your site
JSON API for backups taken with the Remote JSON API
Command Line for backups taken using the native CRON script
Indicates the backup type and can be Full for full site backups (database and files), DB Only for database only backups, Files only for files only backup or Multi DB for multiple databases backup (an archive containing SQL dumps of the main site's database and the defined multiple databases).
Displays the numeric identifier of the backup profile used during the backup. It is possible that since then the profile may have been modified or even deleted!
The total size of the backup archive in Mb. If the files are not available on your server, i.e. the record is marked as "obsolete" or "remote", the size appears inside parentheses to let you know that the files are not available for download.
This will not be accurate if you are using the Process each part immediately option in the data processing engine section of the application's configuration
Displays the name of the backup file, if it is available.
It will also show you the backup download links which allow you to download the backup archive directly to your browser. These links show as "Part 00", "Part 01" and so on. Single-part archives (the default setting on most hosts) will always have only one download link, titled "Part 00". If you have a multi-part archive, you will see as many links as the number of parts generated by the application.
The only supported and guaranteed method of downloading your backup archives error-free is using FTP/SFTP in BINARY transfer mode. Anything else has the potential to CORRUPT your backup archives.
If the file is stored on a remote storage location, e.g. Amazon S3 or a remote FTP server, you will also see a Manage remote stored files link. Clicking on it will allow you to transfer the files back to your server, download them directly from the remote location or remove them from the remote storage. For more information, please read the Manage remotely stored files page.
If your backup archive has a backup ID you will also see the View Log button which takes you to the View Log page, with this backup attempt's log file open.
Clicking on the label on top of each column allows you to sort the backup entries by the contents of that column. By default, the application sorts the records by Start descending, so that the newest backup records will appear on top. Below the header there are three filter boxes. The first one allows you to filter by the backup description. The other two allow you to select a date range so that only backups attempted within this date range will be displayed. You can leave either of these boxes empty to allow an open start or end date respectively.
On the top of the page you can find a tool bar with operations buttons. The Delete button will remove the selected backup record entries along with their backup archives (if applicable), whereas the button will only remove the files (if found on your server). The button will run the integrated extraction feature for the selected archive file. This feature can be used to restore your backup archive on the same server you backed up from or even a different server (live transfer of your site to another host!).
If you are interested in restoring your backup archives on a different server or when the application is inaccessible, you can use Akeeba Kickstart or Akeeba eXtract Wizard to extract the archive and restore it on the server.
Integrated restoration is only supported for Full Site and Files Only backup archives. Trying to use it with any other type of backup files will ultimately result in an error. This feature is available only to Akeeba Solo / Akeeba Backup Professional - the paid version. Users of the Akeeba Backup Core version can follow our video tutorials or Quick Start Guide instructions to easily restore their backups using Kickstart or eXtract Wizard.
Backup description / comment editor
The View / Edit Comment button will open a page showing the description and comment of the currently selected backup row. You can freely edit both the description and the comment on that page and save your changes using the Save & Close button. If you changed your mind, click on the button. The same page will open if you click on a backup record's description (appearing as a link).
You have the option to manage backup archives stored in a remote storage location, for example Amazon S3 or a remote FTP server. You can do that by clicking on the Manage remotely stored files link on the far right hand column of supported backup records in the Manage Backups page. Clicking on that link opens a modal (popup box).
Please note that not all of the following features may appear in the dialog. It depends on the remote storage engine used for the backup record. Most engines support remotely stored file deletion and quite a lot of them support fetching an archive back to your server. Very few of them support downloading a remotely stored file directly to the browser. These are limitations imposed by the remote storage service.
The "Manage Remotely Stored Files" page
Thebutton will automatically download the backup archive from the remote location and store it again on your server. This allows you to easily import backup archives stored on a remote location back to your server's storage so that you can easily restore them on the same or a different site. If you are using S3, please make sure that the user credentials you have supplied have enough privileges for the files to be downloaded (i.e. they don't grant write-only access to the bucket). Also make sure that you have adequate free disk space on your server for the operation to complete.
Thebutton will permanently delete the archives from the remote storage. There is no confirmation. Once you click this button, your remotely stored files will be removed.
Finally, if the remote storage engine supports this feature, there are links under the Download to your desktop header. Clicking on them will instruct your browser to download the respective backup archive's part directly to your PC. Currently, only Amazon S3, CloudFiles, Dropbox and remote FTP support this feature. Do note that the backup archives are transferred directly from the remote storage to your PC. They are not stored on your site's server. If you want to store them on your server, use the button instead.
If none of the above options are available, the application will display an error message. In that case, just close the popup box.
After finishing your remote files administration, please close the modal dialog by clicking on the X button on its top-right corner and reload the Manage Backups page. Until you reload the page the changes you made will not be visible.