Jaime, I'm glad the issue is resolved.
I don't think your tone was that snippy or rude, although not answering my specific debugging questions and replying with "SMB worked almost 100% when we used backuppc 3.3.1, so I’m not sure why it should be so difficult." is borderline. Helping someone debug an issue is like playing "20 questions" over email. If each round-trip is lossy then the chances of figuring out the issue go way down. I did ask you about the smb config settings. Your reply didn't answer my question and repeated that it worked fine in 3.3.1, so something is wrong. So that caused my debugging effort to stall 6 days ago. The process works best when people stick to the facts with concrete, precise observations and data, and not clutter things with opinions that might be wrong or be irrelevant. Perhaps my question about the smb settings did indeed cause you to look at them and figure out the problem, or Holger's or Michael's followups triggered you to do so, which is good. As you know, we've exchanged a couple of emails about the "256 exit error" off-list. You sent me a log file - thanks. I replied that it looks clean and doesn't show the error, and I asked you to send me any other log file that actually shows the error. That was almost 24 hours ago. Craig On Tue, Oct 30, 2018 at 10:44 AM Jaime Fenton <jaime.fen...@animallogic.ca> wrote: > Thanks for the follow up on this thread. > > The issue is resolved. > > I had put some items in the global config that had affected some singular > configs. Once I corrected the global config and rolled all configs back to > the global, it started working (for the most part, but there's a thread > about my 256 exit error). > > Thanks for everyones help on this. > > Cheers, > Jaime > > -----Original Message----- > From: Michael Stowe [mailto:michael.st...@member.mensa.org] > Sent: Tuesday, October 30, 2018 10:28 AM > To: General list for user discussion, questions and support < > backuppc-users@lists.sourceforge.net> > Cc: Jaime Fenton <jaime.fen...@animallogic.ca>; Craig Barratt < > cbarr...@users.sourceforge.net> > Subject: Re: [BackupPC-users] Weird backup commands > > On 2018-10-30 08:04, Holger Parplies wrote: > > Hi, > > > > Jaime Fenton wrote on 2018-10-24 16:17:24 +0000 [Re: [BackupPC-users] > > Weird backup commands]: > >> Also, my apologies if my tone came across as snippy or rude [...] > >> I???m just frustrated with the issues I???m having [...] > > > > well ... > > > >> [...] > >> If I thought samba was not going to work, then I would dump it. > > > > Believe it or not, Samba *can* never work properly, presuming you want > > both incremental and exact backups. As Craig pointed out, Samba *can* > > never give you the in-/exclude options rsync does. If you're fine with > > all of that, then go ahead. The only benefit Samba gives you is > > presumably the ease of setup, and you're apparently not getting much > > out of that, because it doesn't "just work". You're going to have to > > put in some work one way or the other. > > There > > is simply no way around that. > > Let me amplify this: samba can also easily miss incremental files whose > timestamp is not as expected, something rsync is not subject to. > There's a set of issues surrounding open and locked files, which I won't > attempt to cover in detail here, except to point out that it's suited to a > use case where the files you care about are expected to be static during > the backup period. > > >> [...] > >> Out of curiosity, has anyone else had a problem with samba 4.7.1? I > >> did see one mention in a forum somewhere that there issues were > >> resolved with samba 4.7.3. Thoughts? > > Between 4.7.1 and 4.7.3 of Samba, there were a number of server changes > around vulnerabilities, particularly using the SMB1 protocol. smbclient > (the only relevant portion) is largely unchanged. So, my main thoughts > are: > 1) No, this isn't relevant > 2) Reading the release notes is a good way to find out if a minor version > change would be important or not > > > It seems highly unlikely that one Samba version changes the command > > line BackupPC passes to it. Much more likely is an issue with your > > BackupPC configuration. That is why Craig asked: > > > >> [...] > >> What are your settings for $Conf{SmbClientFullCmd}, > >> $Conf{SmbShareName}, $Conf{BackupFilesOnly} and > >> $Conf{BackupFilesExclude} on the two machines? > > > > So, my thought is: answer the question. Without that information, the > > only help we can give you is, "there's probably something wrong with > > your configuration". > > > > I might add that each of these settings individually might be global > > or host specific. How do you manipulate the settings? Do you edit the > > config file or use the web interface? > > > >> [...] > >> ??? Good example: Running: /usr/bin/smbclient > >> \\\\computername.domainname\\C\$<file:///\\computername.domainname\C\ > >> $> -U AL\\backuppc -E -d 1 -c tarmode\ full -TcN /data/backuppc/pc/ > >> computername.domainname /timeStamp.level0 - Users\\username\\AppData > >> Users\\ username \\Documents<file:///\\Documents> Users\\ username > >> \\Downloads<file:///\\Downloads> Users\\ username > >> \\My\<file:///\\My\> Documents Users\\ username > >> \\Desktop<file:///\\Desktop> > >> > >> ??? Error example: Running: /usr/bin/smbclient \\\\ > >> computername.domainname \\C\$<file:///\\C\$> -U AL\\backuppc -E -d 1 > >> -c tarmode\ full -Tc - Users\\\*\\AppData\\\* > >> Users\\\*\\Documents\\\* > >> Users\\\*\\Downloads\\\* Users\\\*\\Desktop\\\* Users\\\*\\My\ > >> Documents\\\* > > > > This seems to be badly mangled by both your MUA as well as yourself - > > I'm guessing the spaces around "computername.domainname" as well as > > "username" > > are probably not there (they're not escaped, so they would separate > > arguments, basically meaning the good example command would be > > nonsense, even with the file tags removed). > > In any case, the confusion Windoze path separators introduce is a pain. > > I'm > > not sure this is better with rsync, but it probably is - at least you > > *should > > be* able to consistently use "/", which doesn't need escaping. Oh, and > > you can use both in- and excludes with rsync. You can't with Samba. > > You know that, right? > > > > My reaction, at least, is, I'm not taking a closer look at any of > > that, because it's bogus, confusing, and irrelevant. We need the > > configuration details. > > > > Hope that helps. > > > > Also, my apologies if my tone came across as snippy or rude, I'm just > > frustrated with questions (and followups) that prevent the possibility > > of meaningful help. > > > > Regards, > > Holger > > > > > > _______________________________________________ > > BackupPC-users mailing list > > BackupPC-users@lists.sourceforge.net > > List: > https://u2182357.ct.sendgrid.net/wf/click?upn=rBK8reUlX8Sxr7Iz1fV-2F7azDepoKsO2pWuEqaZQXziclOk1C3J1HK5ryLm0UkwauF8WGAbPQPulkw6jGlj-2BNdMKzyS4-2BY7RcC51XaueEjwE-3D_2m721kandkcBOiWGNKtykmhkC2Nr07T0YxkYtTXRcaNlt5gMd1ZyWoo3HSTJa-2BwMHwpydK-2BukuFYBvKRfoxry3TVvllqLROQddqhTe1yucARl45kXOdCPeEipL8v0Typ-2FwXbNX1kHUZB4LFSUBhI1MCUop50YR-2FJi8OceMWC8wpxzf7VG4lTuXygZv8spcZ9yIOvoG2yJ2OyCk47-2BPhhx0BuykHhs80LYwl7-2FsojLAo-3D > > Wiki: > https://u2182357.ct.sendgrid.net/wf/click?upn=YahQ8tVjTExAt0gOS-2Bui2Mixv9MMU5sk9-2B870pGjW1AnKM7ab4hD66FpxtTa0zRK_2m721kandkcBOiWGNKtykmhkC2Nr07T0YxkYtTXRcaNlt5gMd1ZyWoo3HSTJa-2BwMHwpydK-2BukuFYBvKRfoxry1iDK6l7Ec5XGJfqD-2F9GxriYAL0M6B2O0GxkXl1ykeLGs6PqVvVBOgCYr-2FCHwtwJYNg3f4SPMVki2Ns4lAH-2FS6NlruHWepTHQE-2B0uyERlG-2FvWGTR3uog3gLrClyrqKeN8gPFE7kxIJRY0RnxBza6GGk-3D > > Project: > > https://u2182357.ct.sendgrid.net/wf/click?upn=YahQ8tVjTExAt0gOS-2Bui2N > > o4X-2FoaUvRonuUjUtJd4Qaeqdswo1k-2Bm1Ez13Mv9mt3_2m721kandkcBOiWGNKtykmh > > kC2Nr07T0YxkYtTXRcaNlt5gMd1ZyWoo3HSTJa-2BwMHwpydK-2BukuFYBvKRfoxry090v > > HpajZ1amlq3rPQocmBKf-2FlgSPhl2r1Y2PI9Ky4J2ujZO29QO-2FNYFGFxJMxLtesVMCY > > A-2B3Dc-2BOAH2DmMktSLRE8rOCib5Rkq7-2BbelnAU7UPZqjbZBc1-2F11YJBUZt-2Bh- > > 2F5a8rVm6g1u3urcjPBYNk-3D > -- > Jaime Fenton > Support Engineer > > T: +1 604 398 4800 (main) > D: +1 604 398 4813 (direct) > E: jaime.fen...@animallogic.ca > > 840 Cambie Street > Vancouver, BC V6B 2P6 > CANADA > > > [LinkedIn] <https://www.linkedin.com/company/animal-logic> [Facebook] > <https://www.facebook.com/Animal-Logic-129284263808191/> [Twitter] < > https://twitter.com/AnimalLogic> [Instagram] < > https://www.instagram.com/animallogicstudios/> > > [Animal Logic]<http://www.animallogic.com> > > www.animallogic.com<http://www.animallogic.com> > > CONFIDENTIALITY AND PRIVILEGE NOTICE > This email is intended only to be read or used by the addressee. It is > confidential and may contain privileged information. If you are not the > intended recipient, any use, distribution, disclosure or copying of this > email is strictly prohibited. Confidentiality and legal privilege attached > to this communication are not waived or lost by reason of the mistaken > delivery to you. If you have received this email in error, please delete it > and notify us immediately by telephone or email. >
_______________________________________________ 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/
