Unfortunately, we were unable to replicate the issue on our side. We do exclude the old backup-guard folder in wp-content/uploads from backups generated in JetBackup for WordPress.
The only minor issue that we could find is that after upgrading from 1.6 > 2.0, you lose visibility of those previously generated backups:
BEFORE: https://postimg.cc/23dQBj0S
AFTER: https://postimg.cc/gx3mG5YQ
In our tests, the only way we found the backup size could be higher than normal (but not doubled) is if we specifically moved the old backup-guard “uploads” folder to a different folder in the uploads directory. (such as “2023/”)
It’s possible that a directory was excluded which was now included after he updated. However, we verified that excluded paths in Settings will be kept after updating so there shouldn’t be any issues there.
On my server (Windows 2019) the old backup-guard folder in wp-content/uploads got renamed to jetbackup after the plugin update and retained the previous backups.
I have just seen in the last backup logs that the jetbackup folder is not excluded and so the backup has backed up the previous backups as well as itself.
-
This reply was modified 3 years, 3 months ago by
imoperations.