Support » Plugin: BackUpWordPress » Zip warning and backup failure

  • Resolved dbooksta

    (@dbooksta)


    WP v4.8.1, BackUpWordPress v3.6.4, PHP v5.6.31

    BackUpWordPress detected issues with your last backup.

    php: ZipArchive::close(): Renaming temporary file failed: No such file or directory, ~/wp-content/plugins/backupwordpress/classes/backup/class-backup-engine-file-zip-archive.php, 46

    No successful backups have been generated in months.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author katmoody

    (@katmoody)

    Hi there –

    These types of errors usually occur when the backup runs into a memory limit or other server limitation. Can you check to see if there are any kinds of issues with either of those by checking with your host?

    Let me know what you find out,
    Kat

    dbooksta

    (@dbooksta)

    This site is on shared hosting at 1and1.com. There are no file size limits. There are, of course, some reasonable memory limits, but I don’t know what they are, and they are not onerous enough to keep other backup plugins from producing backups of the same WP site.

    In this case: Your plugin is getting so far as to generate a 175MB file called “zingUu7O” and then ten seconds later a 159MB file of the form “site-default-2-complete-2017-09-07-18-56-35.zip.DIRe1h”. (Having failed gracelessly, it also leaves a “.backup-default-2-running” file in that “wp-content/backupwordpress-28542540a1-backups” folder.)

    Plugin Author katmoody

    (@katmoody)

    Hey there –
    I know that 1and1 does have a max_execution_time limit, and it could be running into that and then not recognizing that the backup can’t run anymore. Are you able to break your backups into multiple backups? Here’s an article on our site that might be able to help you do that: https://bwp.hmn.md/knowledge-base/splitting-backup-workload-using-excludes-functionality/

    Let me know if you’re able to work around that limit!
    Kat

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.