Some days, this messages show, and other days, it doesn't. This on-again, off-again functionality varies even when I do nothing (change no configuration, add no modules, etc.) in between backups. That is to say, one day it will work just fine, and another day, I will get the error message "Could not run backup because the file could not be saved to the destination" regardless of how many manual backups I attempt. Notably, this seems to primarily occur with manual backups.

Comments

Shai’s picture

Shai commented

Hi @DC_Marc and all,

I'm having the same problem, but only with backups to Amazon S3. Are your backups to Amazon?

Shai Gluskin

dc_marc’s picture

dc_marc commented

Our backups are to Amazon, yes.

ronan’s picture

ronan commented
Status: Active » Postponed (maintainer needs more info)

The S3 library I'm using triggers php errors which may be getting saved to your apache log if they're not displaying on the screen. Can you look for errors next time this happens?

ronan’s picture

ronan commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Is this still an issue? If so please reopen.