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.
You can use Akeeba backup.
It supports Joomla! 3.4 and later.
Does full backup including database and does make it possible to transfer the whole site to another domain
First thing I would do is use JInput instead of using $_FILES, like so:
$jinput = JFactory::getApplication()->input;
$files = $input->files->get('jform1');
// rest of code here
So rather than becoming some long winded array, it will become much more simplified like so:
[test] => Array
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, ...
While restructuring our company website we had the same experience.
Previously we were using akeeba for backing up our websites. This time
we decided to remove akeeba backup system from our joomla based
We wrote simple phing scripts to build backups and dump them to
protected Amazon S3 service. This improved our backup process and it
With the remote backup you want to switch to breaking the archive up into chunks. You need to experiment with the server set up you have. Basically php and FTP timeout and so you loose all the upload if not finished. start with 100MB and then go up or down if it works or not. I think we got up to 300-500MB on last site we did this to FTP back to an office ...
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
First of all, you don't need to download the latest version of Joomla, because the files you download from your original site already has everything you need.
Akeeba Backup is a better way to move/restore a site, but as you say you don't have full admin access, it's not an option. You'll probably have to get full admin access eventually, but that's not very ...
Is the old website still accessible? If yes, then I think the safest and easiest way to transfer joomla website is to use Akeeba Backup component. You just need to install this component and then create a backup.Once the backup is created then you just need to extract the backup in the new host and run the installation instruction.
You should be able to use the SQL Dump to recreate the database using phpMyAdmin or similar.
You will also need the Joomla files to be able to recreate the Joomla website.
Once the files and the database have been recreated, you will likely need to edit the configuration.php file in the root folder of the website and update the database credentials to the ...
Almost every time there is a blank page on a php application, it denotes a php fatal error somewhere. It's not uncommon, it happens and there can be many reasons for it.
First of all, you have to enable Error Reporting, so Joomla/php will print any errors in your browser. This way you will get an idea of what's ...
There will be a change for that some is missing if you should use a backup.
If you use the pro version of akeebabackup you can set it to run backup at night automatical. there will be less users online, i guess.
Website visitors can be directed to a maintenance page at index.html or index.htm rather than any kickstart.php or index.php file as most hosts are configured to load index.html or index.htm in preference to index.php.
You can ensure this is the case by adding the following directive to your .htaccess file:
DirectoryIndex index.html index.htm index.php
You can try this steps.
Export all content from your actual site with J2XML component. Was free and works fine for this situation.
Install new Jooomla. Be sure was last version.
Import XML genereted from your old site.
You will need create again yours Menus and modules.
But with this steps you are safe ...
You won't find anything like articles, categories and menus in file manager. You should be able to find the Joomla installation folders and files, including all extensions and media/images files.
Actually what you need to do is to download all these files, plus the database of your site.
Assuming the intruder didn't damage anything crucial in your ...
Don't comment just replace 'SET OPTION SQL_BIG_SELECTS=1' with 'SET SQL_BIG_SELECTS=1'. Apparently the syntax changed with mySQL 5.6 or something.
After a little more searching, this error message occurs because your
host has updated to MySQL 5.6. The query SET OPTIONS SQL_BIG_SELECTS=1
fails because the new syntax is SET SQL_BIG_SELECTS=1 (without ...
If the backup is 3 months old then you are going to lose 3 months of data, a "backup" is basically a snapshot of the site at the time it was made, typically weekly backups are a norm because in the worst case you have lost 1 week worth of data. Daily are the best but can be costly in server space to keep enough of them to be "safe".
So YellowWebMonkey goes ...
Use Akeeba Kickstart:
Create new database in cPanel
Upload kickstart.php to where you want to restore site.
Go to URL (http://www.mywebsite.com/kickstart.php) and follow the prompts
Download the jpa archive to your local computer
Extract it with https://www.akeebabackup.com/products/akeeba-extract-wizard.html and use the setting to "Ignore the most errors"
Check if a folder called "AwStats" is there and delete this folder (see for explanation the link by sources.)
Upload the extracted files via FTP to you webserver