Hi Jan,
I think this is correct, but there are other experts who might chime in to
correct me.
1. Migration will not result in compression of existing backups. It just
allows V4 to consume the V3 pool.
2. After compression is turned on, newly backed up files will be
compressed. Existing backups
3. Sorry, I think of the machines being backed up as clients, but BackupPC
does call them hosts. rsync supports compressed transfers but that's not
the scheme used for storage by BackupPC.
4. You may be thinking of the tasks that check for unreferenced files and
recalculate the total pool size,
Hi,
I have few questions related to compression
Currently, I have BackupPC 3 installed on Intel NUC with 4 core pentium,
and since the compression significantly decreased backup speeds, I have
turned it off. I am about to switch to v4, so it might be worth to
reconsider, since the increments are
Hi Robert,
1-2) This is what I would expect, I am currious if there is a way to
gradually compress the files; not all at once.
3) By the host, I meant host being backed up. And I am sure, it is not
used for the compression, unless compress option of rsync is used. But I
guess, this is
3. Yes, there is certainly some confusion in client/host or host/server
naming schemes :-) Actually, I could imagine that the rsync compression
could be a reason for writing the custom perl version, which BackupPC
use: You just don't uncompress and store the already compressed file...
But I doubt
