Re: [BackupPC-users] RsyncSshArgs fail when separated, work when combined

2019-01-15 Thread Jan Stransky 
My guess is, that the -e parameter needs all ssh parameters included as
a value. That is what the escaped spaces IMHO does. E.g. whole
"/usr/bin/ssh\ -l\ ubuntu\ -C\ -c\ aes256-...@openssh.com" is single
value for -e.

It might be a feature of the rsync_bpc. I am not sure, how this works
with regular rsync. I certainly use very different syntax with normal
rsync :-)

If this is true for clearer config, you are asking for, a new variable
$sshArgs or so might be considered?
Cheers,
Jan

On 1/15/19 10:18 AM, Johan Ehnberg wrote:
> Yes,
> 
> Multiple lines:
> 
> Running: /usr/local/bin/rsync_bpc --bpc-top-dir /var/lib/backuppc 
> --bpc-host-name test.i.molnix.com --bpc-share-name / --bpc-bkup-num 1 
> --bpc-bkup-comp 0 --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1 
> --bpc-bkup-inode0 75573 --bpc-attrib-new --bpc-log-level 1 -e /usr/bin/ssh\ 
> -l\ ubuntu -C -c\ aes256-...@openssh.com --rsync-path=sudo\ /usr/bin/rsync 
> --super --recursive --protect-args --numeric-ids --perms --owner --group -D 
> --times --links --hard-links --delete --delete-excluded --partial 
> --log-format=log:\ %o\ %i\ %B\ %8U,%8G\ %9l\ %f%L --stats --timeout=72000 
> --exclude=/proc test.i.molnix.com:/ /
> incr backup started for directory /
> Xfer PIDs are now 17341
> This is the rsync child about to exec /usr/local/bin/rsync_bpc
> rsync_bpc: -c aes256-...@openssh.com: unknown option
> 
> Combined line, (note also the space escaping around the concerned
> arguments):
> 
> Running: /usr/local/bin/rsync_bpc --bpc-top-dir /var/lib/backuppc 
> --bpc-host-name test.i.molnix.com --bpc-share-name / --bpc-bkup-num 4 
> --bpc-bkup-comp 0 --bpc-bkup-prevnum 3 --bpc-bkup-prevcomp 0 
> --bpc-bkup-inode0 75725 --bpc-attrib-new --bpc-log-level 1 -e /usr/bin/ssh\ 
> -l\ ubuntu\ -C\ -c\ aes256-...@openssh.com --rsync-path=sudo\ /usr/bin/rsync 
> --super --recursive --protect-args --numeric-ids --perms --owner --group -D 
> --times --links --hard-links --delete --delete-excluded --partial 
> --log-format=log:\ %o\ %i\ %B\ %8U,%8G\ %9l\ %f%L --stats --timeout=72000 
> --exclude=/proc test.i.molnix.com:/ /
> incr backup started for directory /
> Xfer PIDs are now 17737
> This is the rsync child about to exec /usr/local/bin/rsync_bpc
> Xfer PIDs are now 17737,17739
> 
> Best regards,
> Johan
> 
> On 1/15/19 10:42 AM, Jan Stransky wrote:
>>
>> In the logs, you can see actual commands issued. Have you compared those?
>>
>> Cheers,
>>
>> Jan
>>
>> On 14/01/2019 10:17, Johan Ehnberg wrote:
>>>
>>> Hello,
>>>
>>> I stumbled upon this weirdness when benchmarking offloadable SSH
>>> ciphers using the rsync transfer method.
>>>
>>> In short, splitting up the RsyncSshArgs I use on multiple lines fails:
>>>
>>> '-e',
>>>
>>> '$sshPath -l ubuntu',
>>>
>>> '-C',
>>>
>>> '-c aes256-...@openssh.com'
>>>
>>>
>>> and combining them on one line works (but may be a fluke):
>>>
>>> '-e',
>>>
>>> '$sshPath -l ubuntu -C -c aes256-...@openssh.com'
>>>
>>>
>>> Errors vary between these:
>>>
>>> No files dumped for share /
>>>
>>> rsync error: syntax or usage error (code 1) at main.c(1572) [client=3.1.2.0]
>>>
>>> The suspect is some escaping problem due to the @ sign since it
>>> indicates an array in Perl. However, escaping it (-c
>>> aes256-gcm\@openssh.com) does not help. I am not into Perl more than
>>> that. Any thoughts?
>>>
>>> Best regards,
>>>
>>> Johan Ehnberg
>>>
>>> -- 
>>> Signature
>>> *Johan Ehnberg*
>>>
>>> Founder, CEO
>>>
>>> Molnix Oy
>>>
>>>
>>> jo...@molnix.com 
>>>
>>> +358 50 320 96 88
>>>
>>> molnix.com 
>>>
>>>
>>> /The contents of this e-mail and its attachments are for the use of
>>> the intended recipient only, and are confidential and may contain
>>> legally privileged information. If you are not the intended recipient
>>> or have otherwise received the e-mail in error, please notify the
>>> sender by replying to this e-mail immediately and then delete it
>>> immediately from your system. Any dissemination, distribution,
>>> copying or use of this communication without prior and explicit
>>> permission of the sender is strictly prohibited./
>>>
>>> /*Please consider the environment - do not print this e-mail unless
>>> you really need to.*/
>>>
>>>
>>>
>>> ___
>>> 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/
> -- 
> Signature
> *Johan Ehnberg*
> 
> Founder, CEO
> 
> Molnix Oy
> 
> 
> jo...@molnix.com 
> 
> +358 50 320 96 88
> 
> molnix.com

Re: [BackupPC-users] Upgrade from 3 to 4 or start afresh

2019-01-15 Thread Michael Stowe 

On 2019-01-15 05:34, Paul Littlefield wrote:

Hello,

I look after a 3.3.1-2ubuntu3.3 installation and now all clients do
not backup and have tar_process done, err = 0.

I have been told that version 4 of BackupPC will fix the errors.


I would not expect this, but it's *possible* if you have, say, upgraded 
smbclient and use samba for backups.  You can also downgrade smbclient 
if this is the case.  You can validate this by executing the backup 
command line and reviewing the results.



Should I try to upgrade the Ubuntu v3 apt-get installation or start
afresh with a TAR install of v4?


No, I don't recommend upgrading without at least a rudimentary diagnosis 
of the problem.



There are 6 clients running a mix of Windows 7, Windows 10 and all
using Microsoft Outlook.


Samba can't back up Outlook unless it's shut down, obviously.  Is this 
what you're trying to back up?  What method are you using?



Thanks in advance.

Regards,

Paul
___
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] Upgrade from 3 to 4 or start afresh

2019-01-15 Thread Paul Littlefield 

Hello,

I look after a 3.3.1-2ubuntu3.3 installation and now all clients do not backup 
and have tar_process done, err = 0.

I have been told that version 4 of BackupPC will fix the errors.

Should I try to upgrade the Ubuntu v3 apt-get installation or start afresh with 
a TAR install of v4?

There are 6 clients running a mix of Windows 7, Windows 10 and all using 
Microsoft Outlook.

Thanks in advance.

Regards,

Paul



___
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/

Re: [BackupPC-users] RsyncSshArgs fail when separated, work when combined

2019-01-15 Thread Jan Stransky 
In the logs, you can see actual commands issued. Have you compared those?

Cheers,

Jan

On 14/01/2019 10:17, Johan Ehnberg wrote:
>
> Hello,
>
> I stumbled upon this weirdness when benchmarking offloadable SSH
> ciphers using the rsync transfer method.
>
> In short, splitting up the RsyncSshArgs I use on multiple lines fails:
>
> '-e',
>
> '$sshPath -l ubuntu',
>
> '-C',
>
> '-c aes256-...@openssh.com'
>
>
> and combining them on one line works (but may be a fluke):
>
> '-e',
>
> '$sshPath -l ubuntu -C -c aes256-...@openssh.com'
>
>
> Errors vary between these:
>
> No files dumped for share /
>
> rsync error: syntax or usage error (code 1) at main.c(1572) [client=3.1.2.0]
>
> The suspect is some escaping problem due to the @ sign since it
> indicates an array in Perl. However, escaping it (-c
> aes256-gcm\@openssh.com) does not help. I am not into Perl more than
> that. Any thoughts?
>
> Best regards,
>
> Johan Ehnberg
>
> -- 
> Signature
> *Johan Ehnberg*
>
> Founder, CEO
>
> Molnix Oy
>
>
> jo...@molnix.com 
>
> +358 50 320 96 88
>
> molnix.com 
>
>
> /The contents of this e-mail and its attachments are for the use of
> the intended recipient only, and are confidential and may contain
> legally privileged information. If you are not the intended recipient
> or have otherwise received the e-mail in error, please notify the
> sender by replying to this e-mail immediately and then delete it
> immediately from your system. Any dissemination, distribution, copying
> or use of this communication without prior and explicit permission of
> the sender is strictly prohibited./
>
> /*Please consider the environment - do not print this e-mail unless
> you really need to.*/
>
>
>
> ___
> 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/