Odd things have been happening w/ the backup manager lately.
I get an error email every time the backup manager runs (see below), even though upon checking in my server directory, the backups are being created and are unzippable.
The Backups tab in MW has stopped showing me the backups. I can only see them by manually checking the server directory, since each backup is now in its own unique 10-digit folder (rather than just a single zip).
My rule of only keeping 6 backups as per the settings has stopped working. The directory with the backup subfolders keeps growing unless I manually delete older backups.
I've set up an Amazon S3 connection with the required details. However the backups are never sent to S3. The selected bucket doesn't contain any of the backups since its creation. They still only go to the local server directory. Do I have to change the path under "settings" to reflect the S3 destination, too? Is there a way of testing that the S3 location is accessible to the Backup Manager?
Odd things have been happening w/ the backup manager lately.
I get an error email every time the backup manager runs (see below), even though upon checking in my server directory, the backups are being created and are unzippable. View attachment 11676
The Backups tab in MW has stopped showing me the backups. I can only see them by manually checking the server directory, since each backup is now in its own unique 10-digit folder (rather than just a single zip).
My rule of only keeping 6 backups as per the settings has stopped working. The directory with the backup subfolders keeps growing unless I manually delete older backups.
I've set up an Amazon S3 connection with the required details. However the backups are never sent to S3. The selected bucket doesn't contain any of the backups since its creation. They still only go to the local server directory. Do I have to change the path under "settings" to reflect the S3 destination, too? Is there a way of testing that the S3 location is accessible to the Backup Manager?
Was there a resolution to this problem that can be documented here?
I am having the same error message, but on a new install.
I haven't been able to perform a successful backup yet.
Thanks in advance.
It was an issue I managed to resolve with my web host and most likely down to blocked IP addresses. It was quite tedious and involved some trial and error incl. temporarily disabling the firewall.
Odd things have been happening w/ the backup manager lately.
I get an error email every time the backup manager runs (see below), even though upon checking in my server directory, the backups are being created and are unzippable. View attachment 11676
The Backups tab in MW has stopped showing me the backups. I can only see them by manually checking the server directory, since each backup is now in its own unique 10-digit folder (rather than just a single zip).
My rule of only keeping 6 backups as per the settings has stopped working. The directory with the backup subfolders keeps growing unless I manually delete older backups.
I've set up an Amazon S3 connection with the required details. However the backups are never sent to S3. The selected bucket doesn't contain any of the backups since its creation. They still only go to the local server directory. Do I have to change the path under "settings" to reflect the S3 destination, too? Is there a way of testing that the S3 location is accessible to the Backup Manager?
@Raydar - Maybe the problem is the hosting as well? Because I am sure the backup manager works just fine generally, we have quite a few installs that use it.
