As the author of Akeeba Backup I have to say that:
In nine years we had a total of four security issues, only one being high priority. Even that one required advanced cryptanalytic skills to exploit. It only applied when an optional feature was enabled. We patched it in ALL versions of our software, even those. It supported for four years. The security ...
Well for starters, Akeeba Backup does not appear to be in the VEL (Vulnerable Extensions List) on the Joomla Extensions Directory.
These people have slagged Akeeba Backup for it insecurity, however:
Have they contacted the developer?
Have they reported it on JED?
Do they have solid evidence? (shared privately for the time being)
Due to the popularity of ...
I am the developer of Akeeba Backup. There are two different CRON scripts supplied with Akeeba Backup Professional.
The recommended method is using the native CRON script which bypasses the web server entirely and runs the backup process essentially as a standalone PHP command line application. But that's not the object of your question.
The legacy backup ...
In akeeba backup component there is an option to exclude the files or folders which you don't want.
Go to the akeeba backup setting Files and Directories Exclusion, exclude the folder which you don't want and then run the backup.
And for more info you can read this: Exclude data from the backup
Here is a video example.
Akeeba Backup is an extension for backup management. It is the industry standard, a JED's TOP Rated and MOST Reviewed extension.
It almost has no interaction with the front-end site. If there were any vulnerability, it would be reported immediately and I am confident that the author would fix it in the shortest possible time.
Artur Stępień's answer in How ...
Sorry to provide just a link as answer, but the only reasonable way I know of is to use https://www.akeebabackup.com/documentation/akeeba-kickstart-documentation.html. Download link is here. The very short version is that you upload the kickstart.php and the backup to the root of the site and then use browser to go to yourdomain.tld/kickstart.php. This ...
Yes you will need to enter the details for the development server database at this step.
By default, Akeeba Kickstart will display the database details from the site it was backed up from... it assumes that you're restoring to the same site that you backed up.
You should upgrade to latest version of Joomla 3.2 or to Joomla 3.3
As per this link Joomla 3.2.1+ , doesn't have this issue.
If you can't upgrade then you need to change Joomla code (I won't recommend this), and the details are mentioned in the above link.
Unfortunately it isn't possible to restore a backup of the database (.sql file) using Akeeba Backups itself. To restore the database, you must import it using PhpMyAdmin or a similar tool. If you do not have access to PhpMyAdmin on your server then an alternative would be using this:
Or a Backup and Restore extension for ...
It should be also possible to move the website with the "classic way"... Meaning, zipping everything in the public_html and getting a mysql dump, using the tools available in your hosting panel.
You may have some issues if the hosting is Godaddy Classic Hosting, which by personal experience, is usually timing out when trying to zip the contents of a Joomla ...
Akeeba backup is used to create backups of your site. You can create backups as ZIP, JPA or JPS files. This means you can make a copy of your site-articles, configurations, database etc and store it in one convenient file.
Akeeba Kickstart is used to **restore** the backup file you created using Akeeba backup. By restore I mean you use the backup file to ...
As @lodder says, the JPA file generated by Akeeba Backup contains everything you need (files and database, including Joomla itself), so all you need to do is upload the JPA file and kickstart.php to your server and visit "http://yourdomain.com/kickstart.php" (if you're using Kickstart pro, you'll have to rename the file to something else first).
But since ...
If you have enough rights on the server, I do it without any downtime and without Akeeba. I use a script like
Make a dump of the mysql joomla database, store the file in a directory which is not readable by apache server (not accessable through user www-data [ubuntu, etc] or http [arch linux,..]):
mysqldump -h hostname -u user --password=password ...
Password protecting the backend using .htpasswd is much better than using (Akeeba's) admintools - it is very efficient, and the beauty is that if an IP tries to login 5 times with a wrong password, then that IP gets blocked by the CSF firewall.
I personally don't believe that having to append a hash at the end of the URL to login to the admin will make the ...
Nicholas (Akeeba developer) already told us what to do in such a case:
I get a blank page or Internal 500 error accessing Akeeba Backup or trying to backup
"If you are receiving a blank page or a fatal error when trying to access Akeeba Backup and/or receive an AJAX error during backup right after upgrading to Akeeba Backup 3.5.x, please note that this is ...
Any data created in Joomla is stored in the database. This means that when taking a backup using Akeeba, you must also take a backup of the database, else, you're only restoring the files, without the content.
The backup file (JPA file) will contain the entire Joomla CMS + any install extensions + the database. Therefore on your new hosting provider, you do ...
I myself too was very disappointed that I had to upload a php file with the backup every time I needed to install from the backup, since that added a few steps in the workflow.
Also the kickstart is just an unzipping tool for the default .jpa archive.
So what I do now a days, is go to the following settings page on Akeeba Backup's admin panel, and set the ...
if you have acces to the backend, try disabling the SEF configurations.
EDIT: then you have an issue with rewrite rules, check with an original .htaccess (cf joomla installation package) after that you can reenable SEF as it should work xampp.
It can be that your backup file is corrupted. I would suggest to try to restore the jpa archive in your local machine using Akeeba extract wizard, to get closer to a conclusion that the file can be restored or it is damaged. If it can not be restored locally, then there is a big chance that your archive is corrupted.
Try to re-backup, but before you do so, ...
You need do this steps:
Upload your .jpa file;
Upload the file kickstart.php from Akeeba site in same directory .jpa file.
Run the file www.yoursite.com/kickstart.php
Follow steps from restore process.
I hope this helps.
There are a couple of approaches. Using @Tom Kuschel suggestion with rsync if you have such privileges is one. But there are others as well.
If the only changes are on the db level, you could simply create the new database, import your data and then connect Joomla to that database.
Connecting Joomla to another database (and remote databases) can work also ...
When we do a site upgrade like this we use a temp folder and Akeeba. Simply create a new folder for for the updated site and install it using Akeeba. Make sure you use a new database so the entire new site is fully functional in the folder. Once you are satisfied that everything works, move the entire current Joomla install into a folder, then move the new ...
it looks like you're dev site is just a subdirectory on the same account so you don't need to ftp the files anywhere. just copy the jpa file from /administrator/components/com_akeeba/backups to /dev and then use kickstart (https://www.akeebabackup.com/products/akeeba-kickstart.html) to install the dev site.
You can read about this warning in Akeeba documentation:
Q203 - Default output directory in use
It is more like a friendly warning or you can say a security warning from the developers (not a functional warning). And it is about a relatively insecure Output Directory location set for akeeba backup files.
If you set the output directory as the default ...
It's a good practice to always have up-to-date backups of your projects/sites. This way, you can always revert back to a previous working state.
If an extension has broken your site, then remove that extension.
You can do it manually by navigating to the directories of your Joomla site, where each extension places its files.
For example in the case of Akeeba,...
If your current site is damaged but you don't want to lose any data, then you've got a long road ahead of you. You really need to provide more detail as to what you want to accomplish.
That said, if you just need to restore the old one and then upgrade it, use Akeeba Kickstart on your server to restore the backup.
Move your live site into a subfolder