Guillaume Outters via rsync wrote:
> On 2020-12-11 12:53, Chris Green wrote :
>
> > […] wrote a trivial[ish] script that copied
> > all the backups to a new destination sequentially (using --link-dest)
> > and then removed the original tree, having checked the new backups
> > were OK of course.
On 2020-12-11 12:53, Chris Green wrote :
[…] wrote a trivial[ish] script that copied
all the backups to a new destination sequentially (using --link-dest)
and then removed the original tree, having checked the new backups
were OK of course.
With the same cause as yours, I once worked out
Paul Slootman via rsync wrote:
> On Thu 10 Dec 2020, Chris Green via rsync wrote:
> >
> > Occasionally, because I've moved things around or because I've done
> > something else that breaks things, the hard links aren't created as
> > they should be and I get a very space consuming backup
On Thu 10 Dec 2020, Chris Green via rsync wrote:
>
> Occasionally, because I've moved things around or because I've done
> something else that breaks things, the hard links aren't created as
> they should be and I get a very space consuming backup increment.
>
> Is there any easy way that one
