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 this is the case :-)

4. I guess so... It does not seem to be a place to do the compression
then...

Jan

Dne 12.01.2019 v 17:14 Robert Trevellyan napsal(a):
> 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, which can both be split over
> multiple nightly runs.
>
> Robert Trevellyan
>
>
> On Sat, Jan 12, 2019 at 11:04 AM Jan Stransky
> <jan.stransky.c...@gmail.com <mailto:jan.stransky.c...@gmail.com>> wrote:
>
>     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 uncompressed and compressed again on
>     the server side. The think is that Pentium N3700 is not very
>     efficient worker, however i7, which is backed up is different
>     story....
>
>     4) I think there is an option how big percentage of files is being
>     checked or so; what about this one?
>
>     Cheers,
>
>     Jan
>
>     Dne 12.01.2019 v 14:55 Robert Trevellyan napsal(a):
>>     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 will remain as they were.
>>
>>     3. Host resources are always used for compression, either because
>>     BackupPC is doing the work, or because the filesystem does it
>>     natively. My BackupPC pools are on ZFS with LZ4 compression
>>     enabled and BackupPC compression disabled.
>>
>>     4. The closest thing would be using rsync with --ignore-times for
>>     full backups, which isn't quite the same thing, or having the
>>     filesystem do it (e.g. ZFS scrub).
>>
>>     Robert Trevellyan
>>
>>
>>     On Sat, Jan 12, 2019 at 7:51 AM Jan Stransky
>>     <jan.stransky.c...@gmail.com
>>     <mailto:jan.stransky.c...@gmail.com>> wrote:
>>
>>         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 not big, big data are
>>         already in
>>         the pool and v4 handles files differently.
>>
>>         1) If I start the migration with compression on, when would
>>         it happen?
>>         Would whole pool be compressed at once?
>>
>>         2) If the pool is uncompressed, and I turned it on, when will be
>>         uncompressed files compressed? On full backup, or never unless ti
>>         changes on the host?
>>
>>         3) Is there way to compress the files using the host resources?
>>
>>         4) Is integrity of the compressed file checked any time?
>>
>>         Best  regards,
>>
>>         Jan
>>
>>
>>
>>         _______________________________________________
>>         BackupPC-users mailing list
>>         BackupPC-users@lists.sourceforge.net
>>         <mailto:BackupPC-users@lists.sourceforge.net>
>>         List:   
>>         https://lists.sourceforge.net/lists/listinfo/backuppc-users
>>         Wiki:    http://backuppc.wiki.sourceforge.net
>>         Project: http://backuppc.sourceforge.net/
>>
>>
>>
>>     _______________________________________________
>>     BackupPC-users mailing list
>>     BackupPC-users@lists.sourceforge.net 
>> <mailto:BackupPC-users@lists.sourceforge.net>
>>     List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
>>     Wiki:    http://backuppc.wiki.sourceforge.net
>>     Project: http://backuppc.sourceforge.net/
>     _______________________________________________
>     BackupPC-users mailing list
>     BackupPC-users@lists.sourceforge.net
>     <mailto:BackupPC-users@lists.sourceforge.net>
>     List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
>     Wiki:    http://backuppc.wiki.sourceforge.net
>     Project: http://backuppc.sourceforge.net/
>
>
>
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:    http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Reply via email to