Support » Plugin: BackWPup - WordPress Backup Plugin » How does the plugin create the backups? I’m seeing replacing zip files…

  • Resolved ellmann creative

    (@ellmanncreative)


    How does the plugin create its archive? Because I’m seeing a weird behaviour where the plugin creates a .zip file, then creates a new .zip file (named the same) that reaches a little more size than the old one, and then the process repeats.

    Normally I wouldn’t have an issue, but the new host we’re using seems to be imposing write limitations of some sort (or some other limitation), and we’re seeing about 10 MB/s when the .zip is created. This makes a site that’s about 260 MB zipped take about 15 minutes to get backed up (by writing about 8 GB total in order to create a 260 MB archive).

    Is there something we can switch, or reconfigure, to make this go faster?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support BWU support

    (@duongcuong96)

    Hello @ellmanncreative

    Could you try with Tar instead? thank you

    Plugin Support BWU support

    (@duongcuong96)

    since we haven’t heard back from you, I’m going to mark it as resolved.
    In case you’re still having problems, feel free to let us know 😉

    Thread Starter ellmann creative

    (@ellmanncreative)

    I’ll give it a shot sometime this week and report back. I hope that’s OK.

    Thread Starter ellmann creative

    (@ellmanncreative)

    So, it seems tar/tgz behaves better – I suppose it has to do with how the archive creation is handled (direct OS command vs constructing via ZipArchive, I assume?).

    However, there’s a separate issue with the tar/tgz format:

    WARNING: File name "wp-content/plugins/woocommerce/packages/woocommerce-blocks/build/product-add-to-cart--product-button--product-image--product-price--product-rating--product-sale-bad--49d3ecb2.js" is too long to be saved correctly in TarGz archive!

    (same is true for ‘Tar’)

    I’ve actually had issues unpacking tar/tgz archives created by BackWPUp in the past, which is why I generally avoid using it if I can help it. I believe it was a general problem with disk space – there wasn’t enough space to create the archive, but the plugin was never notified; on top of that, I found out “the hard way” when a plugin failed to update (ran into 0 bytes free and never completed) and broke the site, and it turned out that recent backups were broken.

    (no – we left enough space on the disk for backups and adjusted the number of files kept accordingly; the client started uploading images in .tiff format at like 50-70 MB/image though, and we found out when they came back with “boo hoo our site is broken fix plz” a year later)

    Ideas?

    • This reply was modified 6 months, 4 weeks ago by ellmann creative. Reason: Added info on why I stay way from tar/tgz
    Plugin Support BWU support

    (@duongcuong96)

    hi @ellmanncreative

    so I think you can split the big backup job into smaller ones like one for database, themes, and plugin backup, and one for just the backup uploads folder.

    this would make the backup jobs use fewer server resources and avoid being killed by the server.

    Thread Starter ellmann creative

    (@ellmanncreative)

    Except the database, plugins, themes etc. take 1-2s each, and everything else is file backup – I don’t expect splitting that up would help at all.

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