logging behavior while performing a backup job (host-dependent, apparently)
-
I have two sites: one is mine an the other is my friend’s. The sites are hosted on different servers, with apparently different setups.
I’ve installed the current version of BackWPup Free on both. Both sites are running on WP4.5 currently.
I’ve made the exact same settings for the plugin and the backup jobs. The jobs run via WPcron (accesses through a user), everything is Zipped.
When I run the jobs, the behavior differs:
– my site backs up all in one sitting, with progress bars nicely showing me the progress, and the files appearing at the upload destinations right away;
– my friend’s site shows the back up progress in little steps. After each of the steps, the progress bar shows that the job was completed OK in 0 (zero) seconds.At first I thought that was some strange bug, and the job at my friend’s site failed. But reloading the Jobs page several times would show the progress bars for a few seconds again, with next steps being added to the logs. So I decided to be patient and see what happens.
It took a while for the job to complete (the site is old and full of pictures), but it is finally done and the zip files seem to be ok.We’ve contacted my friend’s hoster and they said that during that period (when the job was running), the site was creating a load of about 95 percent of CPU allocation without any breaks, so it looks like the process wasn’t stopping in the background. Testing also indicates that the job completes OK (and the files are uploaded to backup destinations) if nobody looks at the admin page of my friend’s site.
But the logs still remain incomplete for some time, until you look at them (i mean, the admin page), then it takes them about a minute to be completed.Any idea why there might be such a difference in displaying / logging behavior?
It’s definitely something with the hosting setup, but before we ask the hoster if they would change anything, it would be nice to have some idea about where to look and maybe test (reproduce it) somewhere else.
- The topic ‘logging behavior while performing a backup job (host-dependent, apparently)’ is closed to new replies.