Hi Ged,
Thank you for your answer.
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.
Yes, you are right – that's true. But that was just the counterargument
for the last resort solution I'm about to do (in case there will be no
other solution): purging the entire pool and starting all over again.
But let's put that aside. It is not related to the main problem.
The main issue is, that I expected the delete button in the host
overview page to delete that specific backup, which contains data it was
not supposed to back up.
I know there is deduplication, that's why I deleted the recent backups
of _all_ hosts, in case the newly introduced data was used in another
host as well.
Should that not delete that data and clear up that disk space if nothing
links to it anymore?
[...] and start those backups from backup number one
Right now, I can't start any new backups because the pool is 100% full
and the delete function does not free up disk space. That was the point
of my post.
Best regards,
Tobias
_______________________________________________
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/
