It should be more or less as slow as doing the new backup without removing
them, as it's doing essentially the same thing. The difference would be to
do it out of "backup hours" or when the server has more free resources.
On Thu, Oct 19, 2023 at 11:49 AM marki wrote:
> Alright. In any case remov
Alright. In any case removing files from the current backup (because
they don't exist anymore / have been excluded / ...) is painfully slow.
On 2023-10-19 16:04, Guillermo Rozas wrote:
It's not a capacity problem.
It's a performance problem.
Sorry, you implied that the problem was the capacit
>
> It's not a capacity problem.
> It's a performance problem.
>
Sorry, you implied that the problem was the capacity when you said
>> Also in the original example the disk isn't large enough, so we're
>> not
>> even making it to that stage.
But again, that was not the question.
> The question i
It's all V4.
It's not a capacity problem.
It's a performance problem.
And trying to figure out why it is so slow, I tried looking at what it
is actually doing.
Which brought me to what I was initially asking.
I'm not sure where the stuff in 2846 is coming from before being deleted
again (beca
Are you using V3 or V4? According to my understanding, this step
However 2846 seems to be populated with the content from 2845 (including
> the stuff I have excluded).
> It looks like it's first copying all the stuff from 2845 (even the
> excluded path) and then later tries to remove it again from
Sure we have and that's actually what we are doing.
But until that is in place we need a workaround which is excluding stuff. So I
would like to understand why the system behaves this way when I exclude a
directory.
On October 19, 2023 12:37:05 PM GMT+02:00, Paul Leyland
wrote:
>This may soun
This may sound fatuous but I am serious. Have you considered installing
more disk(s)?
Sometimes throwing hardware rather than liveware at a problem is more
cost-effective. The former gets ever cheaper whereas the latter is ever
more expensive.
I doubled the size of my pool over the last year
Hello,
I'm having a hard time here excluding stuff starting with the next
backup.
The problem is the disk containing the pools is not large enough to host
more full backups.
But we don't want to touch our retention policy for now, so we are
trying to exclude some things starting now.
But it
