zip file created and is fine, but job still shows as running.

  • mharpen

    (@mharpen)


    8 years, 2 months ago

    I’m on godaddy shared server. when I run a “complete” backup manually it runs forever, even though I can see on the ftp server that the job finished and the zip file is created. I can even download the zip file (using ftp) and open it fine. it’s a 2.4 GB zip file. But if I click your “cancel” link for the running job, it deletes the perfectly good zip file.

    So the zip job is finishing, but apparently your script is getting cut off by godaddy’s 120 second limit, so the .backup-xxx-running file stays there, and since you’re looking for that file, the only option you provide is a “cancel” link, which then goes and deletes a perfectly good backup. Can you please add a “stop” link also, which just deletes the .running file, so I can see a list of backups and download them and take my chances that the backup is good or not? thank you.

    https://wordpress.org/plugins/backupwordpress/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Katrina “Kat” Moody

    (@katmoody)

    8 years, 2 months ago

    This is already listed in our GitHub as something we want to enable at some point. I agree it’s a good idea!

    Kat

    Thread Starter mharpen

    (@mharpen)

    8 years, 2 months ago

    Kat, just for the time being, at least do this…
    When cancel is pressed, do “NOT” delete the backup. Just delete your ” .backup-xxx-running” trigger file that you’re already deleting. But please do not delete the backup, since it may very well be a good backup. Maybe later on you can figure out a better way to determine if the backup job actually finished. Because at least on godaddy shared hosting, it “is” finishing, and the zip file is perfectly good. Just you need to allow your plugin to stop “spinning” and let us click “cancel” without the plugin deleting the backup zip file. Thank you. please consider this. many of us use shared hosting, and if a wp site has 200+MB or so, the 120 minute timeout is killing your script.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘zip file created and is fine, but job still shows as running.’ is closed to new replies.