• ResolvedModerator Bet Hannon

    (@bethannon1)


    Some of our sites running v 3.6.5 backup jobs are not deleting the “extra” older backups beyond the number set in the remote destination. These backups are all sending to S3, and set to keep only 3 backups, but 6+ are accumulating.

    Have you seen this before, and if so, what should we do?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support happyAnt

    (@duongcuong96)

    Hi Bet,
    Could you please make sure that all backup files in S3 storage are belong 1 job only, since we already have a warning about backup files tracking in the S3 file deletion section:

    Warning: Files belonging to this job are now tracked. Old backup archives which are untracked will not be automatically deleted.

    Moderator Bet Hannon

    (@bethannon1)

    The hashes keep changing, which leads to untracked backups. Why do the hashes keep changing? Seems like they change with every update of the plugin…

    Yes, the backups from the same jobs are piling up. Sometimes 20 or 30 or more of them.

    Can you point me toward some troubleshooting ideas?

    • This reply was modified 6 years, 3 months ago by Bet Hannon.
    Plugin Support happyAnt

    (@duongcuong96)

    Hi @bethannon1,
    The hash keep changing is normal, each backup file has a unique hash for BackWPUp backup tracking work, I think the issue happens with the S3 destination only. Do you allow remote file deletion on S3 or you block delete permission on S3? Could you please test with other destination like Dropbox or local folder?

    • This reply was modified 6 years, 3 months ago by happyAnt.
    Moderator Bet Hannon

    (@bethannon1)

    Ok. I’ll be watching this issue, but it’s a low priority right now. I’ll close this topic and open a new one if needed in the future. Thanks!

    • This reply was modified 6 years, 3 months ago by Bet Hannon.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘File deletion not occurring in some backups’ is closed to new replies.