Re: [BackupPC-users] since upgrading to 4.0 I can no longer do full backups

2018-05-15 Thread Craig Barratt via BackupPC-users
I'm glad that it's working now.

For OSX, the default rsync is really old.  On High Sierra 10.13.4, it's
rsync 2.6.9, circa 2006.  I strongly recommend installing a recent version
in, eg, /usr/local/bin.

Craig

On Tue, May 15, 2018 at 6:27 PM, An Ancient BackupPC User <
backu...@thefabfarrows.com> wrote:

>
> Ok so I can report my windows10 machines are completing full backups now
> without any other changes - THANK YOU :)
>
> My mac needs more work based on the way I have the daemon set up.  I will
> report back some time tomorrow, once I have had chance to work on it.
>
> Thanks again, I really appreciate your help and backup pc is the best,
> have used it for ever.
>
> Paul
>
>
> On May 15, 2018 at 4:45:46 PM, Craig Barratt via BackupPC-users (
> backuppc-users@lists.sourceforge.net) wrote:
>
> On your client the rsyncd.conf file should have a setting such as "charset
> = utf-8".  You'll need to make sure rsyncd reloads the rsyncd.conf file
> before retesting.
>
> If it still fails, the next thing to try is to remove --protect-args
> from $Conf{RsyncArgs}.
>
> Craig
>
> On Tue, May 15, 2018 at 1:17 PM, Paul Farrow 
> wrote:
>
>> Ok I updated as you said and now I get this when trying to do a full
>> backup on my mac.
>>
>> This is the rsync child about to exec /usr/bin/rsync_bpc
>> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = >> 0
>> rsync: on remote machine: -slHogDtprc: unknown option
>>
>>
>>
>> On May 15, 2018 at 3:28:04 PM, Craig Barratt via BackupPC-users (
>> backuppc-users@lists.sourceforge.net) wrote:
>>
>> Ok, you are using rsyncd, so $Conf{RsyncSshArgs} doesn't matter.
>>
>> It seems that when you upgraded to 4.0 the config file was not updated
>> (or perhaps these are per-host settings, which don't get updated during an
>> upgrade).  The correct settings should be:
>>
>> $Conf{RsyncFullArgsExtra} = [
>> '--checksum',
>> ];
>>
>> #
>> # Arguments to rsync for backup.  Do not edit the first set unless you
>> # have a good understanding of rsync options.
>> #
>> $Conf{RsyncArgs} = [
>> '--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',
>> ];
>>
>> Craig
>>
>>
>> On Tue, May 15, 2018 at 10:26 AM, An Ancient BackupPC User <
>> backu...@thefabfarrows.com> wrote:
>>
>>> Thanks Craig for such a quick response.
>>>
>>> I upgraded some time ago but have been pretty lazy in posting to the
>>> mailing list about it.
>>>
>>> XferLOG file /somefolder/XferLOG.840.z created 2018-05-15 11:51:27
>>>
>>> Backup prep: type = full, case = 4, inPlace = 0, doDuplicate = 0, 
>>> newBkupNum = 840, newBkupIdx = 45, lastBkupNum = 839, lastBkupIdx = 44 
>>> (FillCycle = , noFillCnt = 20)
>>> Running: /usr/bin/rsync_bpc --bpc-top-dir /somefolder --bpc-host-name 
>>> somehost --bpc-share-name auser --bpc-bkup-num 840 --bpc-bkup-comp 3 
>>> --bpc-bkup-prevnum 839 --bpc-bkup-prevcomp 3 --bpc-bkup-inode0 693052 
>>> --bpc-attrib-new --bpc-log-level 2 --numeric-ids --perms --owner --group -D 
>>> --links --hard-links --times --block-size=2048 --recursive  --timeout=72000 
>>> --password-file=/passwordfile --exclude=Virtual\ Machines/ 
>>> --exclude=.Trash/ --exclude=Downloads/ --exclude=updater/ 
>>> --exclude=Library/ --exclude=Movies/BBC\ iPlayer\ Downloads/ 
>>> --exclude=Microsoft\ User\ Data/ --exclude=AdobeStockPhotos/ 
>>> --exclude=Data.noindex/ --exclude=.nuget/ --exclude=.dnx/ 
>>> --exclude=.Android/ auser@somehost@::auser /
>>> full backup started for directory some directory
>>> Xfer PIDs are now 17304
>>>
>>>
>>> RsyncSshArgs - non existent in config.pl and clients config.
>>> RsyncClientPath - $Conf{RsyncClientPath} = 'rsync';
>>> RsyncBackupPCPath - $Conf{RsyncBackupPCPath} = '/usr/bin/rsync_bpc';
>>> RsyncFullArgsExtra - non existent
>>> RsyncArgsExtra = $Conf{RsyncArgsExtra} = [];
>>> RsyncArgs - $Conf{RsyncArgs} = [
>>>
>>>   '--numeric-ids',
>>>
>>>   '--perms',
>>>
>>>   '--owner',
>>>
>>>   '--group',
>>>
>>>   '-D',
>>>
>>>   '--links',
>>>
>>>   '--hard-links',
>>>
>>>   '--times',
>>>
>>>   '--block-size=2048',
>>>
>>>   '--recursive'
>>>
>>> ];
>>>
>>>
>>> Appreciate your help - thanks
>>>
>>> Paul
>>>
>>> On May 15, 2018 at 1:04:19 PM, Craig Barratt via BackupPC-users (
>>> backuppc-users@lists.sourceforge.net) wrote:
>>>
>>> Please send the first part of the log file with the full rsync command
>>> (feel free to redact confidential arguments, but maintain any special
>>> characters etc).
>>>
>>> Also send this client's settings for $Conf{RsyncSshArgs}, $Conf{Rsy
>>> ncClientPath}, $Conf{RsyncBackupPCPath}, 

Re: [BackupPC-users] since upgrading to 4.0 I can no longer do full backups

2018-05-15 Thread An Ancient BackupPC User

Ok so I can report my windows10 machines are completing full backups now 
without any other changes - THANK YOU :)

My mac needs more work based on the way I have the daemon set up.  I will 
report back some time tomorrow, once I have had chance to work on it.

Thanks again, I really appreciate your help and backup pc is the best, have 
used it for ever.

Paul


On May 15, 2018 at 4:45:46 PM, Craig Barratt via BackupPC-users 
(backuppc-users@lists.sourceforge.net) wrote:

On your client the rsyncd.conf file should have a setting such as "charset = 
utf-8".  You'll need to make sure rsyncd reloads the rsyncd.conf file before 
retesting.

If it still fails, the next thing to try is to remove --protect-args from 
$Conf{RsyncArgs}.

Craig

On Tue, May 15, 2018 at 1:17 PM, Paul Farrow  wrote:
Ok I updated as you said and now I get this when trying to do a full backup on 
my mac.

This is the rsync child about to exec /usr/bin/rsync_bpc
bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
rsync: on remote machine: -slHogDtprc: unknown option


On May 15, 2018 at 3:28:04 PM, Craig Barratt via BackupPC-users 
(backuppc-users@lists.sourceforge.net) wrote:

Ok, you are using rsyncd, so $Conf{RsyncSshArgs} doesn't matter.

It seems that when you upgraded to 4.0 the config file was not updated (or 
perhaps these are per-host settings, which don't get updated during an 
upgrade).  The correct settings should be:

$Conf{RsyncFullArgsExtra} = [
            '--checksum',
];

#
# Arguments to rsync for backup.  Do not edit the first set unless you
# have a good understanding of rsync options.
#
$Conf{RsyncArgs} = [
            '--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',
];

Craig


On Tue, May 15, 2018 at 10:26 AM, An Ancient BackupPC User 
 wrote:
Thanks Craig for such a quick response.

I upgraded some time ago but have been pretty lazy in posting to the mailing 
list about it.

XferLOG file /somefolder/XferLOG.840.z created 2018-05-15 11:51:27 
Backup prep: type = full, case = 4, inPlace = 0, doDuplicate = 0, newBkupNum = 
840, newBkupIdx = 45, lastBkupNum = 839, lastBkupIdx = 44 (FillCycle = , 
noFillCnt = 20)
Running: /usr/bin/rsync_bpc --bpc-top-dir /somefolder --bpc-host-name somehost 
--bpc-share-name auser --bpc-bkup-num 840 --bpc-bkup-comp 3 --bpc-bkup-prevnum 
839 --bpc-bkup-prevcomp 3 --bpc-bkup-inode0 693052 --bpc-attrib-new 
--bpc-log-level 2 --numeric-ids --perms --owner --group -D --links --hard-links 
--times --block-size=2048 --recursive  --timeout=72000 
--password-file=/passwordfile --exclude=Virtual\ Machines/ --exclude=.Trash/ 
--exclude=Downloads/ --exclude=updater/ --exclude=Library/ 
--exclude=Movies/BBC\ iPlayer\ Downloads/ --exclude=Microsoft\ User\ Data/ 
--exclude=AdobeStockPhotos/ --exclude=Data.noindex/ --exclude=.nuget/ 
--exclude=.dnx/ --exclude=.Android/ auser@somehost@::auser /
full backup started for directory some directory
Xfer PIDs are now 17304

RsyncSshArgs - non existent in config.pl and clients config.
RsyncClientPath - $Conf{RsyncClientPath} = 'rsync';
RsyncBackupPCPath - $Conf{RsyncBackupPCPath} = '/usr/bin/rsync_bpc';
RsyncFullArgsExtra - non existent
RsyncArgsExtra = $Conf{RsyncArgsExtra} = [];
RsyncArgs - $Conf{RsyncArgs} = [
  '--numeric-ids',
  '--perms',
  '--owner',
  '--group',
  '-D',
  '--links',
  '--hard-links',
  '--times',
  '--block-size=2048',
  '--recursive'
];
 

Appreciate your help - thanks

Paul

On May 15, 2018 at 1:04:19 PM, Craig Barratt via BackupPC-users 
(backuppc-users@lists.sourceforge.net) wrote:

Please send the first part of the log file with the full rsync command (feel 
free to redact confidential arguments, but maintain any special characters etc).

Also send this client's settings for $Conf{RsyncSshArgs}, 
$Conf{RsyncClientPath}, $Conf{RsyncBackupPCPath}, $Conf{RsyncFullArgsExtra} and 
$Conf{RsyncArgs}.

Craig

On Tue, May 15, 2018 at 9:26 AM, An Ancient BackupPC User 
 wrote:

Since I upgraded to 4.0 I can no longer do full backups only incremental.  I 
was wondering if any one else has had this issue.

The error I have in the logs is 

This is the rsync child about to exec /usr/bin/rsync_bpc
bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
Unexpected remote arg: changed@changedtoprotecttheinnocent::changed
Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 693052 inode
rsync error: syntax or usage error (code 1) at main.c(1219) [sender=3.0.9.12]
rsync_bpc exited 

Re: [BackupPC-users] since upgrading to 4.0 I can no longer do full backups

2018-05-15 Thread Craig Barratt via BackupPC-users
On your client the rsyncd.conf file should have a setting such as "charset
= utf-8".  You'll need to make sure rsyncd reloads the rsyncd.conf file
before retesting.

If it still fails, the next thing to try is to remove --protect-args
from $Conf{RsyncArgs}.

Craig

On Tue, May 15, 2018 at 1:17 PM, Paul Farrow  wrote:

> Ok I updated as you said and now I get this when trying to do a full
> backup on my mac.
>
> This is the rsync child about to exec /usr/bin/rsync_bpc
> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
> rsync: on remote machine: -slHogDtprc: unknown option
>
>
>
> On May 15, 2018 at 3:28:04 PM, Craig Barratt via BackupPC-users (
> backuppc-users@lists.sourceforge.net) wrote:
>
> Ok, you are using rsyncd, so $Conf{RsyncSshArgs} doesn't matter.
>
> It seems that when you upgraded to 4.0 the config file was not updated (or
> perhaps these are per-host settings, which don't get updated during an
> upgrade).  The correct settings should be:
>
> $Conf{RsyncFullArgsExtra} = [
> '--checksum',
> ];
>
> #
> # Arguments to rsync for backup.  Do not edit the first set unless you
> # have a good understanding of rsync options.
> #
> $Conf{RsyncArgs} = [
> '--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',
> ];
>
> Craig
>
>
> On Tue, May 15, 2018 at 10:26 AM, An Ancient BackupPC User <
> backu...@thefabfarrows.com> wrote:
>
>> Thanks Craig for such a quick response.
>>
>> I upgraded some time ago but have been pretty lazy in posting to the
>> mailing list about it.
>>
>> XferLOG file /somefolder/XferLOG.840.z created 2018-05-15 11:51:27
>>
>> Backup prep: type = full, case = 4, inPlace = 0, doDuplicate = 0, newBkupNum 
>> = 840, newBkupIdx = 45, lastBkupNum = 839, lastBkupIdx = 44 (FillCycle = , 
>> noFillCnt = 20)
>> Running: /usr/bin/rsync_bpc --bpc-top-dir /somefolder --bpc-host-name 
>> somehost --bpc-share-name auser --bpc-bkup-num 840 --bpc-bkup-comp 3 
>> --bpc-bkup-prevnum 839 --bpc-bkup-prevcomp 3 --bpc-bkup-inode0 693052 
>> --bpc-attrib-new --bpc-log-level 2 --numeric-ids --perms --owner --group -D 
>> --links --hard-links --times --block-size=2048 --recursive  --timeout=72000 
>> --password-file=/passwordfile --exclude=Virtual\ Machines/ --exclude=.Trash/ 
>> --exclude=Downloads/ --exclude=updater/ --exclude=Library/ 
>> --exclude=Movies/BBC\ iPlayer\ Downloads/ --exclude=Microsoft\ User\ Data/ 
>> --exclude=AdobeStockPhotos/ --exclude=Data.noindex/ --exclude=.nuget/ 
>> --exclude=.dnx/ --exclude=.Android/ auser@somehost@::auser /
>> full backup started for directory some directory
>> Xfer PIDs are now 17304
>>
>>
>> RsyncSshArgs - non existent in config.pl and clients config.
>> RsyncClientPath - $Conf{RsyncClientPath} = 'rsync';
>> RsyncBackupPCPath - $Conf{RsyncBackupPCPath} = '/usr/bin/rsync_bpc';
>> RsyncFullArgsExtra - non existent
>> RsyncArgsExtra = $Conf{RsyncArgsExtra} = [];
>> RsyncArgs - $Conf{RsyncArgs} = [
>>
>>   '--numeric-ids',
>>
>>   '--perms',
>>
>>   '--owner',
>>
>>   '--group',
>>
>>   '-D',
>>
>>   '--links',
>>
>>   '--hard-links',
>>
>>   '--times',
>>
>>   '--block-size=2048',
>>
>>   '--recursive'
>>
>> ];
>>
>>
>> Appreciate your help - thanks
>>
>> Paul
>>
>> On May 15, 2018 at 1:04:19 PM, Craig Barratt via BackupPC-users (
>> backuppc-users@lists.sourceforge.net) wrote:
>>
>> Please send the first part of the log file with the full rsync command
>> (feel free to redact confidential arguments, but maintain any special
>> characters etc).
>>
>> Also send this client's settings for $Conf{RsyncSshArgs}, $Conf{Rsy
>> ncClientPath}, $Conf{RsyncBackupPCPath}, $Conf{RsyncFullArgsExtra}
>> and $Conf{RsyncArgs}.
>>
>> Craig
>>
>> On Tue, May 15, 2018 at 9:26 AM, An Ancient BackupPC User <
>> backu...@thefabfarrows.com> wrote:
>>
>>>
>>> Since I upgraded to 4.0 I can no longer do full backups only
>>> incremental.  I was wondering if any one else has had this issue.
>>>
>>> The error I have in the logs is
>>>
>>> This is the rsync child about to exec /usr/bin/rsync_bpc
>>> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles 
>>> = 0
>>> Unexpected remote arg: changed@changedtoprotecttheinnocent::changed
>>> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
>>> sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 693052 inode
>>> rsync error: syntax or usage error (code 1) at main.c(1219) 
>>> [sender=3.0.9.12]
>>> rsync_bpc exited with fatal status 1 (256) (rsync error: syntax or usage 
>>> error (code 1) at main.c(1219) [sender=3.0.9.12])
>>> Xfer PIDs 

Re: [BackupPC-users] since upgrading to 4.0 I can no longer do full backups

2018-05-15 Thread An Ancient BackupPC User
Ok I updated as you said and now I get this when trying to do a full backup on 
my mac.

This is the rsync child about to exec /usr/bin/rsync_bpc
bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
rsync: on remote machine: -slHogDtprc: unknown option


On May 15, 2018 at 4:13:52 PM, Paul Farrow (p...@thefabfarrows.com) wrote:

Ok I updated as you said and now I get this when trying to do a full backup on 
my mac.

This is the rsync child about to exec /usr/bin/rsync_bpc
bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
rsync: on remote machine: -slHogDtprc: unknown option


On May 15, 2018 at 3:28:04 PM, Craig Barratt via BackupPC-users 
(backuppc-users@lists.sourceforge.net) wrote:

Ok, you are using rsyncd, so $Conf{RsyncSshArgs} doesn't matter.

It seems that when you upgraded to 4.0 the config file was not updated (or 
perhaps these are per-host settings, which don't get updated during an 
upgrade).  The correct settings should be:

$Conf{RsyncFullArgsExtra} = [
            '--checksum',
];

#
# Arguments to rsync for backup.  Do not edit the first set unless you
# have a good understanding of rsync options.
#
$Conf{RsyncArgs} = [
            '--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',
];

Craig


On Tue, May 15, 2018 at 10:26 AM, An Ancient BackupPC User 
 wrote:
Thanks Craig for such a quick response.

I upgraded some time ago but have been pretty lazy in posting to the mailing 
list about it.

XferLOG file /somefolder/XferLOG.840.z created 2018-05-15 11:51:27 
Backup prep: type = full, case = 4, inPlace = 0, doDuplicate = 0, newBkupNum = 
840, newBkupIdx = 45, lastBkupNum = 839, lastBkupIdx = 44 (FillCycle = , 
noFillCnt = 20)
Running: /usr/bin/rsync_bpc --bpc-top-dir /somefolder --bpc-host-name somehost 
--bpc-share-name auser --bpc-bkup-num 840 --bpc-bkup-comp 3 --bpc-bkup-prevnum 
839 --bpc-bkup-prevcomp 3 --bpc-bkup-inode0 693052 --bpc-attrib-new 
--bpc-log-level 2 --numeric-ids --perms --owner --group -D --links --hard-links 
--times --block-size=2048 --recursive  --timeout=72000 
--password-file=/passwordfile --exclude=Virtual\ Machines/ --exclude=.Trash/ 
--exclude=Downloads/ --exclude=updater/ --exclude=Library/ 
--exclude=Movies/BBC\ iPlayer\ Downloads/ --exclude=Microsoft\ User\ Data/ 
--exclude=AdobeStockPhotos/ --exclude=Data.noindex/ --exclude=.nuget/ 
--exclude=.dnx/ --exclude=.Android/ auser@somehost@::auser /
full backup started for directory some directory
Xfer PIDs are now 17304

RsyncSshArgs - non existent in config.pl and clients config.
RsyncClientPath - $Conf{RsyncClientPath} = 'rsync';
RsyncBackupPCPath - $Conf{RsyncBackupPCPath} = '/usr/bin/rsync_bpc';
RsyncFullArgsExtra - non existent
RsyncArgsExtra = $Conf{RsyncArgsExtra} = [];
RsyncArgs - $Conf{RsyncArgs} = [
  '--numeric-ids',
  '--perms',
  '--owner',
  '--group',
  '-D',
  '--links',
  '--hard-links',
  '--times',
  '--block-size=2048',
  '--recursive'
];
 

Appreciate your help - thanks

Paul

On May 15, 2018 at 1:04:19 PM, Craig Barratt via BackupPC-users 
(backuppc-users@lists.sourceforge.net) wrote:

Please send the first part of the log file with the full rsync command (feel 
free to redact confidential arguments, but maintain any special characters etc).

Also send this client's settings for $Conf{RsyncSshArgs}, 
$Conf{RsyncClientPath}, $Conf{RsyncBackupPCPath}, $Conf{RsyncFullArgsExtra} and 
$Conf{RsyncArgs}.

Craig

On Tue, May 15, 2018 at 9:26 AM, An Ancient BackupPC User 
 wrote:

Since I upgraded to 4.0 I can no longer do full backups only incremental.  I 
was wondering if any one else has had this issue.

The error I have in the logs is 

This is the rsync child about to exec /usr/bin/rsync_bpc
bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
Unexpected remote arg: changed@changedtoprotecttheinnocent::changed
Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 693052 inode
rsync error: syntax or usage error (code 1) at main.c(1219) [sender=3.0.9.12]
rsync_bpc exited with fatal status 1 (256) (rsync error: syntax or usage error 
(code 1) at main.c(1219) [sender=3.0.9.12])
Xfer PIDs are now 
Got fatal error during xfer (No files dumped for share changed)
Backup aborted (No files dumped for share changed)
BackupFailCleanup: nFilesTotal = 0, type = full, BackupCase = 4, inPlace = 0, 
lastBkupNum = 839
Removing empty backup #839
Incrementals appear to work fine.

Thank you in advance

Paul




Re: [BackupPC-users] since upgrading to 4.0 I can no longer do full backups

2018-05-15 Thread Craig Barratt via BackupPC-users
Ok, you are using rsyncd, so $Conf{RsyncSshArgs} doesn't matter.

It seems that when you upgraded to 4.0 the config file was not updated (or
perhaps these are per-host settings, which don't get updated during an
upgrade).  The correct settings should be:

$Conf{RsyncFullArgsExtra} = [
'--checksum',
];

#
# Arguments to rsync for backup.  Do not edit the first set unless you
# have a good understanding of rsync options.
#
$Conf{RsyncArgs} = [
'--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',
];

Craig


On Tue, May 15, 2018 at 10:26 AM, An Ancient BackupPC User <
backu...@thefabfarrows.com> wrote:

> Thanks Craig for such a quick response.
>
> I upgraded some time ago but have been pretty lazy in posting to the
> mailing list about it.
>
> XferLOG file /somefolder/XferLOG.840.z created 2018-05-15 11:51:27
>
> Backup prep: type = full, case = 4, inPlace = 0, doDuplicate = 0, newBkupNum 
> = 840, newBkupIdx = 45, lastBkupNum = 839, lastBkupIdx = 44 (FillCycle = , 
> noFillCnt = 20)
> Running: /usr/bin/rsync_bpc --bpc-top-dir /somefolder --bpc-host-name 
> somehost --bpc-share-name auser --bpc-bkup-num 840 --bpc-bkup-comp 3 
> --bpc-bkup-prevnum 839 --bpc-bkup-prevcomp 3 --bpc-bkup-inode0 693052 
> --bpc-attrib-new --bpc-log-level 2 --numeric-ids --perms --owner --group -D 
> --links --hard-links --times --block-size=2048 --recursive  --timeout=72000 
> --password-file=/passwordfile --exclude=Virtual\ Machines/ --exclude=.Trash/ 
> --exclude=Downloads/ --exclude=updater/ --exclude=Library/ 
> --exclude=Movies/BBC\ iPlayer\ Downloads/ --exclude=Microsoft\ User\ Data/ 
> --exclude=AdobeStockPhotos/ --exclude=Data.noindex/ --exclude=.nuget/ 
> --exclude=.dnx/ --exclude=.Android/ auser@somehost@::auser /
> full backup started for directory some directory
> Xfer PIDs are now 17304
>
>
> RsyncSshArgs - non existent in config.pl and clients config.
> RsyncClientPath - $Conf{RsyncClientPath} = 'rsync';
> RsyncBackupPCPath - $Conf{RsyncBackupPCPath} = '/usr/bin/rsync_bpc';
> RsyncFullArgsExtra - non existent
> RsyncArgsExtra = $Conf{RsyncArgsExtra} = [];
> RsyncArgs - $Conf{RsyncArgs} = [
>
>   '--numeric-ids',
>
>   '--perms',
>
>   '--owner',
>
>   '--group',
>
>   '-D',
>
>   '--links',
>
>   '--hard-links',
>
>   '--times',
>
>   '--block-size=2048',
>
>   '--recursive'
>
> ];
>
>
> Appreciate your help - thanks
>
> Paul
>
> On May 15, 2018 at 1:04:19 PM, Craig Barratt via BackupPC-users (
> backuppc-users@lists.sourceforge.net) wrote:
>
> Please send the first part of the log file with the full rsync command
> (feel free to redact confidential arguments, but maintain any special
> characters etc).
>
> Also send this client's settings for $Conf{RsyncSshArgs}, $Conf{
> RsyncClientPath}, $Conf{RsyncBackupPCPath}, $Conf{RsyncFullArgsExtra}
> and $Conf{RsyncArgs}.
>
> Craig
>
> On Tue, May 15, 2018 at 9:26 AM, An Ancient BackupPC User <
> backu...@thefabfarrows.com> wrote:
>
>>
>> Since I upgraded to 4.0 I can no longer do full backups only
>> incremental.  I was wondering if any one else has had this issue.
>>
>> The error I have in the logs is
>>
>> This is the rsync child about to exec /usr/bin/rsync_bpc
>> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = >> 0
>> Unexpected remote arg: changed@changedtoprotecttheinnocent::changed
>> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
>> sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 693052 inode
>> rsync error: syntax or usage error (code 1) at main.c(1219) [sender=3.0.9.12]
>> rsync_bpc exited with fatal status 1 (256) (rsync error: syntax or usage 
>> error (code 1) at main.c(1219) [sender=3.0.9.12])
>> Xfer PIDs are now
>> Got fatal error during xfer (No files dumped for share changed)
>> Backup aborted (No files dumped for share changed)
>> BackupFailCleanup: nFilesTotal = 0, type = full, BackupCase = 4, inPlace = 
>> 0, lastBkupNum = 839
>> Removing empty backup #839
>>
>> Incrementals appear to work fine.
>>
>> Thank you in advance
>>
>> Paul
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> 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] since upgrading to 4.0 I can no longer do full backups

2018-05-15 Thread An Ancient BackupPC User
Thanks Craig for such a quick response.

I upgraded some time ago but have been pretty lazy in posting to the mailing 
list about it.

XferLOG file /somefolder/XferLOG.840.z created 2018-05-15 11:51:27 

Backup prep: type = full, case = 4, inPlace = 0, doDuplicate = 0, newBkupNum = 
840, newBkupIdx = 45, lastBkupNum = 839, lastBkupIdx = 44 (FillCycle = , 
noFillCnt = 20)
Running: /usr/bin/rsync_bpc --bpc-top-dir /somefolder --bpc-host-name somehost 
--bpc-share-name auser --bpc-bkup-num 840 --bpc-bkup-comp 3 --bpc-bkup-prevnum 
839 --bpc-bkup-prevcomp 3 --bpc-bkup-inode0 693052 --bpc-attrib-new 
--bpc-log-level 2 --numeric-ids --perms --owner --group -D --links --hard-links 
--times --block-size=2048 --recursive  --timeout=72000 
--password-file=/passwordfile --exclude=Virtual\ Machines/ --exclude=.Trash/ 
--exclude=Downloads/ --exclude=updater/ --exclude=Library/ 
--exclude=Movies/BBC\ iPlayer\ Downloads/ --exclude=Microsoft\ User\ Data/ 
--exclude=AdobeStockPhotos/ --exclude=Data.noindex/ --exclude=.nuget/ 
--exclude=.dnx/ --exclude=.Android/ auser@somehost@::auser /
full backup started for directory some directory
Xfer PIDs are now 17304

RsyncSshArgs - non existent in config.pl and clients config.
RsyncClientPath - $Conf{RsyncClientPath} = 'rsync';
RsyncBackupPCPath - $Conf{RsyncBackupPCPath} = '/usr/bin/rsync_bpc';
RsyncFullArgsExtra - non existent
RsyncArgsExtra = $Conf{RsyncArgsExtra} = [];
RsyncArgs - $Conf{RsyncArgs} = [
  '--numeric-ids',
  '--perms',
  '--owner',
  '--group',
  '-D',
  '--links',
  '--hard-links',
  '--times',
  '--block-size=2048',
  '--recursive'
];
 

Appreciate your help - thanks

Paul
On May 15, 2018 at 1:04:19 PM, Craig Barratt via BackupPC-users 
(backuppc-users@lists.sourceforge.net) wrote:

Please send the first part of the log file with the full rsync command (feel 
free to redact confidential arguments, but maintain any special characters etc).

Also send this client's settings for $Conf{RsyncSshArgs}, 
$Conf{RsyncClientPath}, $Conf{RsyncBackupPCPath}, $Conf{RsyncFullArgsExtra} and 
$Conf{RsyncArgs}.

Craig

On Tue, May 15, 2018 at 9:26 AM, An Ancient BackupPC User 
 wrote:

Since I upgraded to 4.0 I can no longer do full backups only incremental.  I 
was wondering if any one else has had this issue.

The error I have in the logs is 

This is the rsync child about to exec /usr/bin/rsync_bpc
bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
Unexpected remote arg: changed@changedtoprotecttheinnocent::changed
Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 693052 inode
rsync error: syntax or usage error (code 1) at main.c(1219) [sender=3.0.9.12]
rsync_bpc exited with fatal status 1 (256) (rsync error: syntax or usage error 
(code 1) at main.c(1219) [sender=3.0.9.12])
Xfer PIDs are now   
Got fatal error during xfer (No files dumped for share changed)
Backup aborted (No files dumped for share changed)
BackupFailCleanup: nFilesTotal = 0, type = full, BackupCase = 4, inPlace = 0, 
lastBkupNum = 839
Removing empty backup #839
Incrementals appear to work fine.

Thank you in advance

Paul



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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/


--  
Check out the vibrant tech community on one of the world's most  
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___  
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/  
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] since upgrading to 4.0 I can no longer do full backups

2018-05-15 Thread Craig Barratt via BackupPC-users
Please send the first part of the log file with the full rsync command
(feel free to redact confidential arguments, but maintain any special
characters etc).

Also send this client's settings for
$Conf{RsyncSshArgs}, $Conf{RsyncClientPath}, $Conf{RsyncBackupPCPath},
$Conf{RsyncFullArgsExtra}
and $Conf{RsyncArgs}.

Craig

On Tue, May 15, 2018 at 9:26 AM, An Ancient BackupPC User <
backu...@thefabfarrows.com> wrote:

>
> Since I upgraded to 4.0 I can no longer do full backups only incremental.
> I was wondering if any one else has had this issue.
>
> The error I have in the logs is
>
> This is the rsync child about to exec /usr/bin/rsync_bpc
> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
> Unexpected remote arg: changed@changedtoprotecttheinnocent::changed
> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
> sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 693052 inode
> rsync error: syntax or usage error (code 1) at main.c(1219) [sender=3.0.9.12]
> rsync_bpc exited with fatal status 1 (256) (rsync error: syntax or usage 
> error (code 1) at main.c(1219) [sender=3.0.9.12])
> Xfer PIDs are now
> Got fatal error during xfer (No files dumped for share changed)
> Backup aborted (No files dumped for share changed)
> BackupFailCleanup: nFilesTotal = 0, type = full, BackupCase = 4, inPlace = 0, 
> lastBkupNum = 839
> Removing empty backup #839
>
> Incrementals appear to work fine.
>
> Thank you in advance
>
> Paul
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] since upgrading to 4.0 I can no longer do full backups

2018-05-15 Thread An Ancient BackupPC User

Since I upgraded to 4.0 I can no longer do full backups only incremental.  I 
was wondering if any one else has had this issue.

The error I have in the logs is 

This is the rsync child about to exec /usr/bin/rsync_bpc
bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
Unexpected remote arg: changed@changedtoprotecttheinnocent::changed
Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 693052 inode
rsync error: syntax or usage error (code 1) at main.c(1219) [sender=3.0.9.12]
rsync_bpc exited with fatal status 1 (256) (rsync error: syntax or usage error 
(code 1) at main.c(1219) [sender=3.0.9.12])
Xfer PIDs are now  
Got fatal error during xfer (No files dumped for share changed)
Backup aborted (No files dumped for share changed)
BackupFailCleanup: nFilesTotal = 0, type = full, BackupCase = 4, inPlace = 0, 
lastBkupNum = 839
Removing empty backup #839
Incrementals appear to work fine.

Thank you in advance

Paul


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] how can I identify in which backup a certain file is?

2018-05-15 Thread Robert Trevellyan
Perhaps scouring the XferLOG for lines marked 'new' would help?

Robert Trevellyan

On Tue, May 15, 2018 at 1:54 AM, Michael Schumacher <
michael.schumac...@pamas.de> wrote:

>
>
> RT> Not sure if this is helpful, but if you browse to a specific
> RT> folder for a host, you can then click a link to view that folder's
> history.
>
> thanks Robert, I was aware of that feature, but it only allows a per
> directory browsing. With a typical Windows directory structure, it is
> impossible to identify the one hidden directory that causes the
> trouble.
>
> What I have in mind is either a listing what files are actually new or
> some kind of display that would only show that part of the directory
> structure that was actually modified in a given backup.
>
>
>  best regards
> ---
> Michael Schumacher
> PAMAS Partikelmess- und Analysesysteme GmbH
> Dieselstr.10, D-71277 Rutesheim
> Tel +49-7152-99630
> Fax +49-7152-996333
> Geschäftsführer: Gerhard Schreck
> Handelsregister B Stuttgart HRB 252024
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Out of inodes, how to recover?

2018-05-15 Thread Carl W. Soderstrom
On 05/15 02:14 , Tapio Lehtonen wrote:
> Question: The host is already out of inodes on backuppc partition, can it
> still remove old backups now obsolete since lower FullKeepCnt? And old files
> are removed and inodes made available? I assume this happens during nightly
> cleanup runs, so I have to wait until next day to find  out.


It is possible to run BackupPC_nightly by hand. Here's the help for it:

backuppc@archivist-2:~$ /usr/share/backuppc/bin/BackupPC_nightly --help
/usr/share/backuppc/bin/BackupPC_nightly version [unknown] calling
Getopt::Std::getopts (version 1.07 [paranoid]),
running under Perl version 5.18.2.

Usage: BackupPC_nightly [-OPTIONS [-MORE_OPTIONS]] [--] [PROGRAM_ARG1 ...]

The following single-character options are accepted:
Boolean (without arguments): -m

Options may be merged together.  -- stops processing of options.
  [Now continuing due to backward compatibility and excessive paranoia.
   See 'perldoc Getopt::Std' about $Getopt::Std::STANDARD_HELP_VERSION.]
usage: /usr/share/backuppc/bin/BackupPC_nightly [-m] poolRangeStart poolRangeEnd


and here's an example usage (from memory, so this may be wrong):
/usr/share/backuppc/bin/BackupPC_nightly 0 255


-- 
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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] Out of inodes, how to recover?

2018-05-15 Thread Tapio Lehtonen
Backing up a single desktop computer, BackupPC host ran out of inodes at 
15 million inodes used. Reading old messages from this list I was 
surprised to learn BackupPC uses only one (or two?) inodes per backed up 
file, no matter how  many hard links are used. I am thus at a loss to 
explain how come 15 million inodes is not enough for backing up this 
single desktop computer.


But to recover from this situation, I plan to reduce the number of full 
backups to keep, that is set $Conf{FullKeepCnt} to something lower.


Question: The host is already out of inodes on backuppc partition, can 
it still remove old backups now obsolete since lower FullKeepCnt? And 
old files are removed and inodes made available? I assume this happens 
during nightly cleanup runs, so I have to wait until next day to find  out.


From what I learned from reading discussions, copying the pool to 
larger disk with more inodes is not feasible. Also it seems to me 
converting the current ext4 filesystem to some other filesystem that 
does not have a hard limit for inodes is iffy. So it is time to start 
planning a new backuppc host and use lower bytes-per-inode or use a 
filesystem with dynamic inodes.


--
Tapio Lehtonen
OSK Satatuuli
<>--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] winexe for Centos 7.5

2018-05-15 Thread Pete Geenhuizen



On 05/15/2018 06:34 AM, Pete Geenhuizen wrote:


On 05/15/2018 05:37 AM, Daniel Berteaud wrote:


I just rebuilt it, it's in my fws-testing repo 
(http://repo.firewall-services.com/centos-testing/7/x86_64/winexe-1.2-3.beta0.mstowe.gitc2fcdf.el7.fws.x86_64.rpm). 
Could you give it a try ?





It installs but  seg faults

# winexe --interactive=0 -A /usr/local/etc/compaq.auth //compaq 'cmd 
/c dir'

Segmentation fault

The above command works flawlessly on previous version.

Oops sorry all if the previous message got waylaid due to it being 
marked as spam, my filter got it wrong and I failed to remove it.


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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] [SPAM] winexe for Centos 7.5

2018-05-15 Thread Pete Geenhuizen


On 05/15/2018 05:37 AM, Daniel Berteaud wrote:


I just rebuilt it, it's in my fws-testing repo 
(http://repo.firewall-services.com/centos-testing/7/x86_64/winexe-1.2-3.beta0.mstowe.gitc2fcdf.el7.fws.x86_64.rpm). 
Could you give it a try ?





It installs but  seg faults

# winexe --interactive=0 -A /usr/local/etc/compaq.auth //compaq 'cmd /c dir'
Segmentation fault

The above command works flawlessly on previous version.

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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/