Backup fails after update to 1.2.0.rc3

This means that your server kills off the backup process. Let’s try some easy troubleshooting.

First go to the Configuration page and just click on Save & Close at the top. Then click on the Configuration Wizard button and let it run to completion.

If the backup still hangs, you may want to try the following settings in the Configuration page:
* Minimum execution time: 2 seconds
* Maximum execution time: 7 seconds
* Execution time bias: 75%

If this doesn’t work, try:
* Minimum execution time: 5 seconds
* Maximum execution time: 3 seconds (yes, max is less than min, it’s not a typo)
* Execution time bias: 75%

If you still have a problem you may want to go to the Configuration page, find the Archiver Engine row and click on Configure next to it. In the pane which opens below set the Part Size for Split Archives to 10Mb. You may have to try smaller values such as 5Mb or 2Mb depending on your hosting. Some free hosts require even smaller parts: 256Kb or 128Kb. This option will chunk your backup archive in multiple files with extensions .jpa, .j01, .j02 and so on. You will need all of these parts to restore the archive.

Hi nikosdion,
thanks for your answer. On the first page it works with the second option:
* Minimum execution time: 5 seconds
* Maximum execution time: 3 seconds
* Execution time bias: 75%

On the second page it fails always at Backing up database. In the log the last row is always
… Beginning dump of #__options

I need to see the entire log. Can you please post it somewhere publicly (e.g. Dropbox, or your server) and paste me a link to the log file? Thank you in advance!

Marking as resolved since the requested information was not provided with 5 months.