Re: [BackupPC-users] Using SMBv2/Disabled SMBv1 on Windows Hosts, Not Backing Up

James, Sven Bunge submitted a pull request to add the -m option to $Conf{SmbClientFullCmd}. His patch uses "-mSMB3". I haven't applied the PR since I don't know about backward compatibility with old versions of smbclient. Can you test his change?

Re: [BackupPC-users] Using SMBv2/Disabled SMBv1 on Windows Hosts, Not Backing Up

On 6/12/2017 1:39 AM, James Arnold wrote: As per title really, following current affairs I've disabled SMBv1 on about everything running Windows. After that, none of my Windows servers back up any more. I've updated Linux itself, added 'min protocol = SMB2' into smb.conf, even tried putting '-m

Re: [BackupPC-users] Late to the Game: Upgrading from Version 3.x on Fedora 25

On 05/29/2017 09:24 PM, Tim Evans wrote: Today's update: The full backup ran for just a few minutes over 24 hours and was killed by BackupPC; log says: 2017-05-29 15:34:24 Backup failed on pelican (BackupPC_tarExtract exited with fail status 256) 2017-05-29 15:34:27 Started full backup on p

[BackupPC-users] Using SMBv2/Disabled SMBv1 on Windows Hosts, Not Backing Up

Hello all - long-time reader first-time poster sorta thing! As per title really, following current affairs I've disabled SMBv1 on about everything running Windows. After that, none of my Windows servers back up any more. I've updated Linux itself, added 'min protocol = SMB2' into smb.conf, even tr