Hi there, On Thu, 26 Oct 2023, Tobias wrote:
... in another installation, we have backups of no longer existing hosts that cannot be simply deleted. ...
If I understand correctly, and you mean that these cannot be deleted because they are your only copies of the data from those hosts, then that means that they are *not* backups. They're at risk of loss if they're the only copies. It sounds to me like you're trying to fit several quarts into a pint pot, and some of them aren't even of the right beverage. BackupPC is a backup system. If you want an archiving system, don't try to force BackupPC to be that system. That's not what it was designed to be. Your immediate problem seems to be that a full backup is copying a lot of files which shouldn't have been in the backups in the first place. To get around that, you could simply call the problem machine(s) by a different name as far as BackupPC is concerned, set up the exclusions, and start those backups from backup number one. Then BPC won't copy the cruft which you don't need from the previous backup (which as has been explained is how BackupPC V4 works and there's not much that you can do about that). Deduplication and compression will still happen, unless you do something wilful to prevent it. You can delete the old backups in their entirety at your leisure when you have the new ones. Obviously the main problem is that you need more backup storage space. -- 73, Ged. _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
