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