Support

Hello Mario,

You can't backup only the front-end. That doesn't make sense. I believe you mean you want to take a backup using the front-end backup feature.

If you use the incremental files method then you are backing up only new files. You are not backing up any database changes. My guess is that this is not what you want. What you most likely want is a full site backup.

1. It depends. Do you want to backup different things on the same site, e.g. have one profile ot backup the entire site and one profile to backup only changed files? If you do, you need multiple backup profiles. If you need to inly backup the same stuff you just need one profile.

2. I am not sure what you want to achieve. Do you want to copy site A to site B and C? You can't do it automatically. You can use a full site backup and DirectFTP but after the "backup" operation you will have to manually run the restoration script on sites B and C

3. You always need an output directory. This is where Akeeba Backup will store its temporary files. Use the default output directory.

4. No idea? It seems that you have not activated the CRON job or you set it to run on a very irregular schedule. Your log file tells me that no backup has ever run.

OK, now I understand what you want. You need to have a clone of Site A on Site B and Site C. You cannot copy just the files. You have to transfer the entire site, including database and all of the files. Anything else might or might not work. If you don't want to follow my advice on points #2 and #3 of my previous reply you'll have to make some tests to see if your solution works. I seriously doubt it will work, but who knows?

You mean that it doesn't work if I copy the root on other roots and db on other db's?

No, it will most likely not work. At the very least you also have to modify your configuration.php. Usually you have to also modify your .htaccess and several configuration options (in files or in the database) for several third party extensions so that the correct site URL and absolute path to the site's root is used. If copying files and a database was the way to do a full site backup Akeeba Backup wouldn't exist at all.

Mario,

you are approaching this in the wrong way :) Akeeba Backup is designed to make backing up, restoring and moving a site between different places very easy. In fact, it was made as a solution to move sites. Backing up and restoring is a degenerate subcase where the source and target server is the same.

So, what do you need to do to survive what happened to you 3 weeks ago? Simple: take automated, frequent backups to an off-site storage location (e.g. Amazon S3 or Dropbox). If your server crashes, just upload the backup archive, kickstart.php and run Kickstart. Akeeba Backup Installer, the restoration script which is included in every backup archive, will reconfigure your configuration.php file for you. Akeeba Backup is a disaster recovery tool. Use it as such :)