Tom Willmot

Hey ??

So my best guess is that your backup is over 2GB and your on a server running a 32bit version of PHP?

If so it’s a known issue we need to fix: https://github.com/humanmade/backupwordpress/issues/430

If that can’t be the issue (because you’re not on a 32bit version of PHP or the backup is smaller than 2GB then there must be something else going on, if so, would love to debug and fix!

The size of the backup in the list and the site size calculating message aren’t connected, it should just read the size by stating the backup file directly (which is what fails on 32it systems as they can’t stat files larger than 2GB).

No worries Jenny, would love to hear if our plugin works for you as I’ve never come across the long filename issue.

Hey Jenny!

That’s an interesting bug, could you post an example of the errors you are seeing.

I think review was intended to be posted for BackWPup

Instead you’ve reviewed BackUpWordPress (which you might want to give a try as it is better ??

Hey Shaun,

What’s the url for the site you experiencing this issue on?

Best option would be to set your schedules to only store 1 local backup, that way you won’t use up much space.

Sorry you ran into issues restoring, I’d love to know what errors you got when trying to restore the database, could you possibly send a copy of the database export that wasn’t working and I’ll take a look.

Looks like this is an issue with Shopp, not sure why BackUpWordPress would trigger the error as it doesn’t interact with metaboxes at all.

Happy to help out the Shopp dev’s with anything needed to get this resolved though.

I’d love to help you get the issue resolved, could you email me directly at [email protected] and I’ll personally get this fixed.

Hey Ross,

Unfortunately we can’t provide support for premium products here, could you instead use the support mechanism that’s built into the BackUpWordPress plugin and send a message through that?

Backupwordpress catches php errors that occur whilst it’s running a backup, looks like wordfence is throwing a notice, that’s something you’ll want to fix in wordfence.

Hey Reza,

Apologies for the issues you’ve experienced.

I see we have an open support thread with you regarding the issue, it’s currently awaiting a response for yourself. Would love to help you get this resolved asap, feel free to email me directly at [email protected] if the main support channel isn’t working for you.

Hey Dino,

The plugin does a couple of things to avoid people being able to view your backups.

1. The folder name contains a random string of letters and numbers, so it should be unguessable.
2. There is a blank index.html which should ensure that even if directory listing is turned on anyone viewing who manages to view the backups directory would just load the blank index.html file
3. On Apache the directory is protected by a .htaccess which checks for a nonce to ensure that the request to download a backup came from the wp-admin.

The fact that you can’t predict the location of the backups directory means that it’s highly unlikely someone would be able to access your backups, I consider that alone enough security.

I’d definitely accept a Pull Request to add the same .htaccess protection to IIS though.

Your backups are stored on your server in the backupwordpress folder in wp-content.

The wp-cron issue is something outside our control, although the error might not actually be stopping your backups from running, do automatic backups work?

Yep!