Restart will be executed now.?!

Where can I download pre 3.1.4 versions ?? They did work for me…

OK, version 3.1.2 allowed me to uncheck the “restart after each job step” option. 3.1.3 allowed me to make a ood backup again. WIll try 3.1.4 now with the restart flagged uncheckek deep down below.

Final observation… version 3.1.2 works flawlessly, after that, trouble starts.

Hi guys, I know this sounds strange and I don’t know if this will help you or not but thought I’d let you know how I fixed this problem on my server.

I’m on WP 4.1 and was having the ‘Database backup done! Restart will be executed now” message. I removed and updated the username and password under BackWPup > Settings > Network and saved and then ran the backup job again and all went well after I had changed and updated the network settings again.

It worked for me, might work for you, then again it might not ??

Good luck.
Jules

I have no username/[assword set there, so that would not solve my problem.

I am new to BackWPup and I also have this problem. I’m running a backup for the first time, and when the file backup is 81% complete, it says “Restart will be executed now” and then hangs. If I abort and retry, I get the same results.

My destinations are Amazon S3 and a local folder:

I went to settings -> network to put in a username/pw, but I’m not sure what username/pw is needed here. The wp-admin login doesn’t help. My WordPress site is not htaccess protected. Do you need the server login with root access to restart apache??? I don’t know why a backup plugin would need such a thing!?

In any case – what is being restarted here? and why??

Hi, as far as I know, it will restart a step in the total backup job that might have timed out on the server. All I can say is: try version 3.1.2, that works fine for me. All after that causes me problems.

I did use an external cron facility to at least make sure my time is synced. Please read https://www.ads-software.com/plugins/backwpup/faq/ about this:

My backup jobs don’t seem to run as scheduled.

BackWPup uses WordPress’ own cron job system (WP Cron) to execute scheduled backup jobs. In order for WordPress to “know” when to execute a job, its “inner clock” needs to be set regularly. That happens whenever someone (including yourself) visits your site. If your site happens to not being visited for a period of time, WordPress’ inner clock gets sort of slow. In that case it takes an extra server-side cron job to regularly call https://your-site.tld/wp-cron.php and tell WordPress what time it is.

Hello
same problem here,

configured to use Dropbox, it’s stuck after archive creation.
It was working correctly before the upload.

Also, I had to add
define(‘ALTERNATE_WP_CRON’, true);
in my wp-config because I had the error “test answer 404”
Not sure if it’s linked…

[INFO] BackWPup version 3.1.4; Un projet de Inpsyde GmbH
[INFO] WordPress version 4.1
[INFO] Blog url : https://www.wm-creations.com/
[INFO]: BackWPup opération: backup; DBDUMP+FILE+WPPLUGIN
[INFO]: BackWPup opération: 0 3 * * 0; Suivante : dim, 18 jan 2015 @ 03:00
[INFO] Opération BackWPup démarrée manuellement
[INFO] version PHP: 5.3.10-1ubuntu3.14 (64bit); cgi-fcgi; Linux
[INFO] Le temps d’exécution maximum d’un script est 60 secondes
[INFO] Le temps de reprise du script est configuré à 60 secondes
[INFO] Version MySQL: 5.5.38-0ubuntu0.12.04.1
[INFO] Web Server: Apache
[INFO] Version curl : 7.22.0; OpenSSL/1.0.1
[INFO] Répertoire temporaire : /var/www/vhosts/wm-creations.com/httpdocs/wp-content/uploads/backwpup-16c90e-temp/
[INFO] Le fichier journal est : /var/www/vhosts/wm-creations.com/httpdocs/wp-content/uploads/backwpup-16c90e-logs/backwpup_log_16c90e_2015-01-16_09-06-07.html
[INFO] Type de sauvegarde : archive
[INFO] Fichier sauvegarde : /var/www/vhosts/wm-creations.com/httpdocs/wp-content/uploads/backwpup-16c90e-temp/backwpup_16c90e_2015-01-16_09-06-07.tar.gz
[16-jan-2015 09:06:07] 1. Tentative de dump de la base de données …
[16-jan-2015 09:06:07] Connexion à la base de données wmcreation sur localhost
[16-jan-2015 09:06:07] Backup database table “wpf78fhyayrh8_commentmeta” with “~339” records
[16-jan-2015 09:06:07] Backup database table “wpf78fhyayrh8_comments” with “~132” records
[16-jan-2015 09:06:07] Backup database table “wpf78fhyayrh8_itsec_lockouts” with “~0” records
[16-jan-2015 09:06:07] Backup database table “wpf78fhyayrh8_itsec_log” with “~27” records
[16-jan-2015 09:06:07] Backup database table “wpf78fhyayrh8_itsec_temp” with “~96” records
[16-jan-2015 09:06:07] Backup database table “wpf78fhyayrh8_links” with “~0” records
[16-jan-2015 09:06:07] Backup database table “wpf78fhyayrh8_options” with “~449” records
[16-jan-2015 09:06:07] Backup database table “wpf78fhyayrh8_postmeta” with “~929” records
[16-jan-2015 09:06:07] Backup database table “wpf78fhyayrh8_posts” with “~1007” records
[16-jan-2015 09:06:08] Backup database table “wpf78fhyayrh8_term_relationships” with “~262” records
[16-jan-2015 09:06:08] Backup database table “wpf78fhyayrh8_term_taxonomy” with “~87” records
[16-jan-2015 09:06:08] Backup database table “wpf78fhyayrh8_terms” with “~87” records
[16-jan-2015 09:06:08] Backup database table “wpf78fhyayrh8_usermeta” with “~70” records
[16-jan-2015 09:06:08] Backup database table “wpf78fhyayrh8_users” with “~2” records
[16-jan-2015 09:06:08] Ajout du dump “wmcreation.sql” avec 4,17 MB a la liste des fichiers à sauvegarder
[16-jan-2015 09:06:08] Sauvegarde de la base de donnée réussie!
[16-jan-2015 09:06:08] 1. Tentative de création de liste des répertoires à sauvegarder …
[16-jan-2015 09:06:08] 391 répertoires à sauvegarder.
[16-jan-2015 09:06:08] 1. Tentative de créer un fichier avec les noms des extensions installées …
[16-jan-2015 09:06:08] Ajout de la liste des fichiers des extensions “WM-Creations.pluginlist.2015-01-16.txt” avec 1,09 kB à la liste des fichiers à sauvegarder.
[16-jan-2015 09:06:08] 1. Tentative de créer un fichier manifeste …
[16-jan-2015 09:06:08] Ajout du fichier manifeste .json avec 4,61 kB à la liste des fichiers de la sauvegarde.
[16-jan-2015 09:06:08] 1. Tentative de création de l’archive…
[16-jan-2015 09:06:08] Compression des fichiers en TarGz. Merci d’être patient, cela peut prendre un certain temps.
[16-jan-2015 09:06:20] Archive de sauvegarde créée.
[16-jan-2015 09:06:20] La taille de l’archive est de 346,41 MB.
[16-jan-2015 09:06:20] 3728 fichiers avec 382,58 MB à sauvegarder
[16-jan-2015 09:06:20] La relance sera faite immédiatement.

Also, if I change it for local folder (instead of Dropbox), it’s stuck in the same place.

And in information tab, self connect has an error 404.
I have multiple sites on the server, only that one has that error, any idea?

Ok, I found the issue.
Hopefully that can help someone:

To enable self connection, and pass the test in BackWPup, you need to enable both IPV4 and IPV6 in you web hosting parameters on the website. (I’m using Plesk)