I have backup and migrate on a fairly standard Drupal installation. I have set up schedules so the database is backed up daily, weekly, and monthly, and the files (using backup and migrate files) to back up weekly, all to Amazon AWS. I received a notice from my client's hosting provider that they had exceeded their allotted diskspace (20 GB). When I checked their file system, I could see that the backups were being saved to the sites/default/files/private/tmp folder (in addition to backing up correctly to Amazon AWS). I have used backup and migrate (and backup and migrate files) on many websites and never encountered this. The only think I can guess that is different about this particular website, vs other websites, is the fact that due to my client's hosting provider, I was not permitted to secure the file permissions as recommended . Am I correct to guess that a temporary backup is saved locally on the server while it is being uploaded to Amazon AWS, and that normally this temp file should be deleted?

Comments

ronan’s picture

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

You are correct in your assumption. Those tmp files should be deleted once the backup is done.

Occasionally this cleanup does not happen, such as when the script times out or finishes prematurely. When that happens B&M should be trying to delete these once they are more than 6 hours old. This cleanup happens when cron runs. Can you confirm that cron is running regularly on your site?

If that's not the problem, then I'm not sure what the issue is. It's possible that your web server is unable to delete those files for some reason, but that would be unusual since the webserver created them in the first place.

kbrinner’s picture

kbrinner
she/her
Location San Diego
commented
Status: Fixed » Postponed (maintainer needs more info)

The cleanup didn't appear to be happening since there were backup files dating back a week. I checked the logs and it does appear that cron was running every 3 hours for the last two days. I have contacted the hosting provider (who wouldn't let me change the permissions myself) and had them change the permissions, so they are now set as recommended and I don't see this happening any more, so it appears to be fixed.

Thanks for your prompt response and for the great module.

ronan’s picture

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

Glad you got it fixed.

Status: Postponed (maintainer needs more info) » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.