You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(15) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(7) |
Feb
(6) |
Mar
(3) |
Apr
(9) |
May
(5) |
Jun
(11) |
Jul
(40) |
Aug
(15) |
Sep
(3) |
Oct
(2) |
Nov
(1) |
Dec
|
2004 |
Jan
(2) |
Feb
(8) |
Mar
(8) |
Apr
(25) |
May
(10) |
Jun
(11) |
Jul
(5) |
Aug
(9) |
Sep
(2) |
Oct
(7) |
Nov
(7) |
Dec
(6) |
2005 |
Jan
(6) |
Feb
(17) |
Mar
(9) |
Apr
(3) |
May
(4) |
Jun
(11) |
Jul
(42) |
Aug
(33) |
Sep
(13) |
Oct
(14) |
Nov
(19) |
Dec
(7) |
2006 |
Jan
(23) |
Feb
(19) |
Mar
(6) |
Apr
(8) |
May
(1) |
Jun
(12) |
Jul
(50) |
Aug
(16) |
Sep
(4) |
Oct
(18) |
Nov
(15) |
Dec
(10) |
2007 |
Jan
(10) |
Feb
(13) |
Mar
(1) |
Apr
|
May
(1) |
Jun
(1) |
Jul
(5) |
Aug
(7) |
Sep
(25) |
Oct
(58) |
Nov
(15) |
Dec
(4) |
2008 |
Jan
(2) |
Feb
(13) |
Mar
(3) |
Apr
(10) |
May
(1) |
Jun
(4) |
Jul
(4) |
Aug
(23) |
Sep
(21) |
Oct
(7) |
Nov
(3) |
Dec
(12) |
2009 |
Jan
(5) |
Feb
(2) |
Mar
|
Apr
(7) |
May
(6) |
Jun
(25) |
Jul
|
Aug
(2) |
Sep
(2) |
Oct
(3) |
Nov
(2) |
Dec
(2) |
2010 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
(2) |
May
(2) |
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
|
Nov
|
Dec
(3) |
2011 |
Jan
(10) |
Feb
(2) |
Mar
(71) |
Apr
(4) |
May
(8) |
Jun
|
Jul
|
Aug
(4) |
Sep
(3) |
Oct
(1) |
Nov
(5) |
Dec
(1) |
2012 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
(15) |
Jun
(1) |
Jul
|
Aug
(20) |
Sep
|
Oct
|
Nov
(2) |
Dec
|
2013 |
Jan
(3) |
Feb
(5) |
Mar
|
Apr
(4) |
May
(2) |
Jun
(11) |
Jul
(12) |
Aug
|
Sep
(19) |
Oct
(25) |
Nov
(7) |
Dec
(9) |
2014 |
Jan
(6) |
Feb
(2) |
Mar
(7) |
Apr
(5) |
May
(1) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(3) |
Nov
(2) |
Dec
(4) |
2015 |
Jan
(8) |
Feb
(2) |
Mar
(3) |
Apr
(4) |
May
(3) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2016 |
Jan
(16) |
Feb
|
Mar
(1) |
Apr
(1) |
May
(12) |
Jun
(3) |
Jul
|
Aug
(5) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
2017 |
Jan
(2) |
Feb
(6) |
Mar
(68) |
Apr
(18) |
May
(8) |
Jun
(1) |
Jul
|
Aug
(10) |
Sep
(2) |
Oct
(1) |
Nov
(13) |
Dec
(25) |
2018 |
Jan
(18) |
Feb
(2) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(1) |
Oct
(7) |
Nov
|
Dec
|
From: Richard S. <hob...@gm...> - 2020-10-20 14:14:17
|
On Sun, Oct 18, 2020 at 12:01 PM Craig Barratt via BackupPC-devel < bac...@li...> wrote: > Richard, > > Sorry about the delay in following up. rsync-bpc and rsync have very > similar configuration scripts, and we need to find out why one fails but > the other works. Both detect that FALLOC_FL_PUNCH_HOLE is available, but > for some reason in rsync-bpc the reference to that macro fails. > > It would be easiest if I had access to a CentOS6 machine, but I don't. > > Could you send me the following 6 files please (just directly, not to the > list): > > - config.log for rsync-bpc and rsync > - config.h for rsync-bpc and rsync > - output of make for rsync-bpc and rsync > > Craig, If you have a Fedora machine available you can always use mock to build for any current Fedora or CentOS release. :) In either case here's a link to the requested information: https://hobbes1069.fedorapeople.org/rsync/ Thanks, Richard |
From: Craig B. <cba...@us...> - 2020-10-18 17:01:20
|
Richard, Sorry about the delay in following up. rsync-bpc and rsync have very similar configuration scripts, and we need to find out why one fails but the other works. Both detect that FALLOC_FL_PUNCH_HOLE is available, but for some reason in rsync-bpc the reference to that macro fails. It would be easiest if I had access to a CentOS6 machine, but I don't. Could you send me the following 6 files please (just directly, not to the list): - config.log for rsync-bpc and rsync - config.h for rsync-bpc and rsync - output of make for rsync-bpc and rsync Thanks, Craig On Sat, Oct 17, 2020 at 6:15 PM Richard Shaw <hob...@gm...> wrote: > Craig, > > Any more input/advice on this? > > Thanks, > Richard > >> _______________________________________________ > BackupPC-devel mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel > Wiki: https://github.com/backuppc/backuppc/wiki > Project: https://backuppc.github.io/backuppc/ > |
From: Richard S. <hob...@gm...> - 2020-10-18 01:15:11
|
Craig, Any more input/advice on this? Thanks, Richard > |
From: Richard S. <hob...@gm...> - 2020-10-12 20:02:51
|
On Mon, Oct 12, 2020 at 2:16 PM Craig Barratt via BackupPC-devel < bac...@li...> wrote: > What output do you get from: > > egrep FALLOC_FL_ config.h config.log > > # egrep FALLOC_FL_ config.h config.log config.h:/* Define if FALLOC_FL_PUNCH_HOLE is available. */ config.h:#define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.h:/* Define if FALLOC_FL_ZERO_RANGE is available. */ config.h:/* #undef HAVE_FALLOC_FL_ZERO_RANGE */ config.log:configure.sh:7756: checking for FALLOC_FL_PUNCH_HOLE config.log:configure.sh:7785: checking for FALLOC_FL_ZERO_RANGE config.log:conftest.c:161:10: error: #error FALLOC_FL_ZERO_RANGE is missing config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #ifndef FALLOC_FL_ZERO_RANGE config.log:| #error FALLOC_FL_ZERO_RANGE is missing config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:#define HAVE_FALLOC_FL_PUNCH_HOLE 1 > Can you try building vanilla rsync-3.1.3 on that platform? The > configure.ac check for FALLOC_FL_PUNCH_HOLE should be the same as > rsync-bpc-3.1.3. > I downloaded a 3.1.3 SRPM from a previous release (Fedora is on 3.2.3) and it built fine. # egrep FALLOC_FL_ config.h config.log config.h:/* Define if FALLOC_FL_PUNCH_HOLE is available. */ config.h:#define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.h:/* Define if FALLOC_FL_ZERO_RANGE is available. */ config.h:/* #undef HAVE_FALLOC_FL_ZERO_RANGE */ config.log:configure.sh:7771: checking for FALLOC_FL_PUNCH_HOLE config.log:configure.sh:7800: checking for FALLOC_FL_ZERO_RANGE config.log:conftest.c:159:10: error: #error FALLOC_FL_ZERO_RANGE is missing config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #ifndef FALLOC_FL_ZERO_RANGE config.log:| #error FALLOC_FL_ZERO_RANGE is missing config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:| #define HAVE_FALLOC_FL_PUNCH_HOLE 1 config.log:#define HAVE_FALLOC_FL_PUNCH_HOLE 1 Thanks, Richard |
From: Craig B. <cba...@us...> - 2020-10-12 19:16:38
|
What output do you get from: egrep FALLOC_FL_ config.h config.log Can you try building vanilla rsync-3.1.3 on that platform? The configure.ac check for FALLOC_FL_PUNCH_HOLE should be the same as rsync-bpc-3.1.3. Craig On Mon, Oct 12, 2020 at 12:01 PM Richard Shaw <hob...@gm...> wrote: > Clicked send too soon... > > This is with 3.1.3.0, 3.1.2.2 built fine. > > gcc 4.4.7 > > Build log: > > https://download.copr.fedorainfracloud.org/results/hobbes1069/BackupPC/epel-6-x86_64/01705128-rsync-bpc/build.log.gz > >> _______________________________________________ > BackupPC-devel mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel > Wiki: https://github.com/backuppc/backuppc/wiki > Project: https://backuppc.github.io/backuppc/ > |
From: Richard S. <hob...@gm...> - 2020-10-12 19:00:55
|
Clicked send too soon... This is with 3.1.3.0, 3.1.2.2 built fine. gcc 4.4.7 Build log: https://download.copr.fedorainfracloud.org/results/hobbes1069/BackupPC/epel-6-x86_64/01705128-rsync-bpc/build.log.gz > |
From: Richard S. <hob...@gm...> - 2020-10-12 18:58:49
|
All other systems completed (CentOS 7 & 8 and All Fedora releases), but CentOS 6 gave me this: syscall.c: In function 'do_punch_hole': syscall.c:341: error: 'FALLOC_FL_PUNCH_HOLE' undeclared (first use in this function) syscall.c:341: error: (Each undeclared identifier is reported only once syscall.c:341: error: for each function it appears in.) syscall.c:341: error: 'FALLOC_FL_KEEP_SIZE' undeclared (first use in this function) Thanks, Richard |
From: Raoul B. <ra...@bh...> - 2020-09-02 18:19:56
|
So, I am officially lost with additional errors popping up, i.e. > bpc_path_refCountAll: can't read attrib file > /data/backup/backuppc/pc/aaa.bbb.ccc/8240/inode/03/attrib52_75b800923eee9d3484169624f5b691fa Unfortunatly, I have no clue how to clean them up and/or force a true "Full" backup (means to truly check/recreate/retransfer everything). From what I understand right now, I have both bad/non-existing attrib cpool files, as well as a few errors in the actualy data cpool files. Any help would be appreciated, before I will have to fall back to a full re-initialization of my backups (which potentially means transferring 500+ GB of data via painfully slow internet links). Thanks, Raoul On 2020-08-29 07:50, Raoul Bhatia wrote: > Hi, > > another update from my side, for all who might be interested / future > generations ;-) > > I set $Conf{PoolNightlyDigestCheckPercent} = 100 > and ran BackupPC_refCountUpdate -m . > > I get 104 ERRORs with md5sum d41d8cd98f00b204e9800998ecf8427e (= empty > file) instead of the expected digest. All of these files have 0 > length, see https://paste.ubuntu.com/p/RRBSsXvMWV/ > > My observations until now: > > A. The timestamp of these files falls into 1 of 3 dates, see > https://paste.ubuntu.com/p/FcY3gb5q8V/ (sorted via xargs ls -altr) > If I disregard the 2 files from 2017, these files first started to > appear when I upgraded rsync-bpc from 3.0.9.14 to 3.0.9.15 > (I usually initate a test backup right after an upgrade to validate > everything is functioning correctly) > >> /var/log/dpkg.log: 2020-08-12 22:46:22 upgrade rsync-bpc:amd64 >> 3.0.9.14 3.0.9.15 > > > B. I verified that there are no other pool files with the same digest > (so no digest* / digest + extension). > > > C. At least some of these pool files are related to attrib files, i.e. >> BackupPC_attribPrint >> aaa.aaa.aaa/8238/f%2fdata%2fmail%2f/fspool/attrib_f1811600a7b6f6e3f2fcafea644e005b >> BackupPC_attribPrint: cannot read attrib file >> mail.bhatia.eu/8238/f%2fdata%2fmail%2f/fspool/attrib_f1811600a7b6f6e3f2fcafea644e005b >> (f1811600a7b6f6e3f2fcafea644e005b) > > > D. Looking at the source of rsync-bpc, I find: > https://github.com/backuppc/rsync-bpc/blob/3.0.9/backuppc/bpc_poolWrite.c#L348 > and > https://github.com/backuppc/rsync-bpc/commit/3eb30d1b4fe844d0a1409f8a090c518e4d713f40#diff-11e5a98fabcaf3b4938189c693342209 > . Could this play a role here? > > > (I have to admit that I am not (yet?) able to wrap my head around the > pooling, so please excuse any error in my assuptions.) > > --> > 1. To me, this reads in a way that backuppc might (have?) decide(d) to > zero out a file / create an empty pool file? > > 2. Would it make sense to handle this specific case (empty pool file) > in BackupPC_refCountUpdate when checking the pool, i.e. at > https://github.com/backuppc/backuppc/blob/master/bin/BackupPC_refCountUpdate#L821 > > > Any further help to debug this problem would be appreciated! > Raoul > PS. Cross-posting to backuppc-devel mailing list, just in case. > > On 2020-08-27 21:58, Raoul Bhatia wrote: >> Hi Craig, Guillermo, all. >> >> A quick update from my side >> >> I have a (complete?) list of (potentially) broken files as reported by >> BTRFS read errors. >> >> I then validated the md5sum from the (c)pool with a one-liner: >>> for i in $(grep /cpool/ ~/broken_files.txt); do >>> M=$(/usr/share/backuppc/bin/BackupPC_zcat $i | md5sum | cut -d ' ' -f >>> 1); echo -n "$M: "; echo $i | grep --color $M || echo "$f ERR"; done >> --> No error, perhaps I am lucky? :-) >> >> >> This leaves only one file that might be damaged: >> backuppc/pc/abc.def.ghi/1989/refCnt/poolCnt.1.16 ? >> >> I am now experimenting with running >> /usr/share/backuppc/bin/BackupPC_refCountUpdate -m >> (Until now: No error; exit code 0) >> >> >> >> Reading the source I have the following questions: >> >> 1. >> https://github.com/backuppc/backuppc/blob/master/bin/BackupPC_refCountUpdate#L819 >> does "rand(100) < $Conf{PoolNightlyDigestCheckPercent}" >> >> My understanding would be that I won't get a predictable 1% check on >> *each* run. Perhaps on average, with a sufficiently large pool, over >> a longer period of time, this might work out, but for a few runs of >> BackupPC_refCountUpdate not. >> >> --> Perhaps there would be another implementation that gets a more >> predictable result? >> (i.e. create an array of all the files to check, sort them, and then >> take the first $Conf{PoolNightlyDigestCheckPercent} of entries, but at >> least 1?) >> >> >> >> 2. I also seem to have accumulated checksum errors over the past >> years. >> >> --> How do I proceed with these files? If they still exist on the >> source, I'd like to re-sync them to the backup. >> >> >> 3. For backuppc/pc/abc.def.ghi/1989/refCnt/poolCnt.1.16 , I do not >> find a way to re-check only this one, old backup. >> >> --> Would it be a good idea to add an option to add a "-n num" flag to >> BackupPC_refCountUpdate to be able to operate on a particular backup? >> >> >> >> Thanks for your guidance, >> Raoul >> >> On 2020-08-24 20:39, Raoul Bhatia wrote: >>> Hi Craig and Guillermo, >>> >>> On 2020-08-23 19:35, Craig Barratt via BackupPC-users wrote: >>> >>>> $Conf{PoolNightlyDigestCheckPercent} is in percent, so you should >>>> set it to 100 to check all the pool file's MD5 digest against their >>>> file names. >>>> >>>> As Guillermo mentions, to check the pool MD5 digests, you can set >>>> temporarily set $Conf{PoolNightlyDigestCheckPercent} to 100 and >>>> $Conf{PoolSizeNightlyUpdatePeriod} to 1. >>> >>> When reading the documentation, I also came across these options. >>> However, I didn't dare to run backuppc / BackupPC_nightly, because >>> from the documentation: >>> >>> Overnight, when BackupPC_nightly next runs, >>> all the unused pool files will be deleted and >>> this will recover the disk space used by the client's backups. >>> >>> I didn't want to end up with an empty pool... >>> >>>> If you stop BackupPC, to check all the pool digests, run: >>>> >>>>> BackupPC_refCountUpdate -m >>>> If you want to also regenerate all the host reference counts (which >>>> will take a long time), you could run: >>>> >>>>> BackupPC_refCountUpdate -m -F >>> >>> Meanwhile, with the kind help of the btrfs community, I figured out a >>> way to get the damaged files. This process is not finished, yet, >>> however, I have a first list: >>> >>> /mnt/backuppc/pc/abc.def.ghi/1989/refCnt/poolCnt.1.16 >>> /mnt/backuppc/cpool/5c/c8/5cc9373a32e06baaa308a7b341db5ac9 >>> /mnt/backuppc/cpool/b2/62/b3629c46481cb038682aea248c45b89f >>> /mnt/backuppc/cpool/20/c6/21c61013d40e644af734e28459df0a1a >>> /mnt/backuppc/cpool/8a/f8/8af935bc53f7199ed75a5695bfd57f26 >>> >>> FYI: The most recent backup from host abc.def.ghi is 2291, so 1989 is >>> quite far in the past. >>> >>> How should I proceed when I have a list of broken files? >>> Move them out from cpool and hope they will be re-synced by the next >>> (full?) backup? >>> >>> Thanks, >>> Raoul >>> >>>> Craig >>>> >>>> On Sun, Aug 23, 2020 at 6:45 AM Guillermo Rozas >>>> <gui...@gm...> wrote: >>>> >>>> Hi Raoul, >>>> >>>> are you using BackupPC v4? If yes, you can use a modification of the >>>> script I posted here: >>>> https://sourceforge.net/p/backuppc/mailman/message/37032497/ >>>> >>>> In the latest version (4.4.0) you also have the config option >>>> $Conf{PoolNightlyDigestCheckPercent}, which checks the md5 digest of >>>> this fraction of the pool files each night. You can probably set it >>>> to 1 and wait a night for it to run. >>>> >>>> Regards, >>>> Guillermo >>>> >>>> On Sun, Aug 23, 2020 at 5:38 AM Raoul Bhatia <ra...@bh...> >>>> wrote: Hi, >>>> >>>> related to my previous email, it seems that the cause of my issues >>>> was a >>>> file system corruption after a "power cut". >>>> >>>> I managed to recover (most of?) the data and would now like to do a >>>> thorough check of the data. >>>> >>>> Is there any way to "fully verify" the integrity of my backuppc >>>> installation, ideally in a nondestructive way ;-) >>>> >>>> Thanks, >>>> Raoul >>>> >>>> PS. My backuppc process is stopped. >>>> -- >>>> DI (FH) Raoul Bhatia MSc >>>> E-Mail. ra...@bh... >>>> Tel. +43 699 10132530 >> >> >> >> _______________________________________________ >> BackupPC-users mailing list >> Bac...@li... >> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users >> Wiki: https://github.com/backuppc/backuppc/wiki >> Project: https://backuppc.github.io/backuppc/ -- DI (FH) Raoul Bhatia MSc E-Mail. ra...@bh... Tel. +43 699 10132530 |
From: Raoul B. <ra...@bh...> - 2020-08-29 05:50:56
|
Hi, another update from my side, for all who might be interested / future generations ;-) I set $Conf{PoolNightlyDigestCheckPercent} = 100 and ran BackupPC_refCountUpdate -m . I get 104 ERRORs with md5sum d41d8cd98f00b204e9800998ecf8427e (= empty file) instead of the expected digest. All of these files have 0 length, see https://paste.ubuntu.com/p/RRBSsXvMWV/ My observations until now: A. The timestamp of these files falls into 1 of 3 dates, see https://paste.ubuntu.com/p/FcY3gb5q8V/ (sorted via xargs ls -altr) If I disregard the 2 files from 2017, these files first started to appear when I upgraded rsync-bpc from 3.0.9.14 to 3.0.9.15 (I usually initate a test backup right after an upgrade to validate everything is functioning correctly) > /var/log/dpkg.log: 2020-08-12 22:46:22 upgrade rsync-bpc:amd64 3.0.9.14 > 3.0.9.15 B. I verified that there are no other pool files with the same digest (so no digest* / digest + extension). C. At least some of these pool files are related to attrib files, i.e. > BackupPC_attribPrint > aaa.aaa.aaa/8238/f%2fdata%2fmail%2f/fspool/attrib_f1811600a7b6f6e3f2fcafea644e005b > BackupPC_attribPrint: cannot read attrib file > mail.bhatia.eu/8238/f%2fdata%2fmail%2f/fspool/attrib_f1811600a7b6f6e3f2fcafea644e005b > (f1811600a7b6f6e3f2fcafea644e005b) D. Looking at the source of rsync-bpc, I find: https://github.com/backuppc/rsync-bpc/blob/3.0.9/backuppc/bpc_poolWrite.c#L348 and https://github.com/backuppc/rsync-bpc/commit/3eb30d1b4fe844d0a1409f8a090c518e4d713f40#diff-11e5a98fabcaf3b4938189c693342209 . Could this play a role here? (I have to admit that I am not (yet?) able to wrap my head around the pooling, so please excuse any error in my assuptions.) --> 1. To me, this reads in a way that backuppc might (have?) decide(d) to zero out a file / create an empty pool file? 2. Would it make sense to handle this specific case (empty pool file) in BackupPC_refCountUpdate when checking the pool, i.e. at https://github.com/backuppc/backuppc/blob/master/bin/BackupPC_refCountUpdate#L821 Any further help to debug this problem would be appreciated! Raoul PS. Cross-posting to backuppc-devel mailing list, just in case. On 2020-08-27 21:58, Raoul Bhatia wrote: > Hi Craig, Guillermo, all. > > A quick update from my side > > I have a (complete?) list of (potentially) broken files as reported by > BTRFS read errors. > > I then validated the md5sum from the (c)pool with a one-liner: >> for i in $(grep /cpool/ ~/broken_files.txt); do >> M=$(/usr/share/backuppc/bin/BackupPC_zcat $i | md5sum | cut -d ' ' -f >> 1); echo -n "$M: "; echo $i | grep --color $M || echo "$f ERR"; done > --> No error, perhaps I am lucky? :-) > > > This leaves only one file that might be damaged: > backuppc/pc/abc.def.ghi/1989/refCnt/poolCnt.1.16 ? > > I am now experimenting with running > /usr/share/backuppc/bin/BackupPC_refCountUpdate -m > (Until now: No error; exit code 0) > > > > Reading the source I have the following questions: > > 1. > https://github.com/backuppc/backuppc/blob/master/bin/BackupPC_refCountUpdate#L819 > does "rand(100) < $Conf{PoolNightlyDigestCheckPercent}" > > My understanding would be that I won't get a predictable 1% check on > *each* run. Perhaps on average, with a sufficiently large pool, over > a longer period of time, this might work out, but for a few runs of > BackupPC_refCountUpdate not. > > --> Perhaps there would be another implementation that gets a more > predictable result? > (i.e. create an array of all the files to check, sort them, and then > take the first $Conf{PoolNightlyDigestCheckPercent} of entries, but at > least 1?) > > > > 2. I also seem to have accumulated checksum errors over the past years. > > --> How do I proceed with these files? If they still exist on the > source, I'd like to re-sync them to the backup. > > > 3. For backuppc/pc/abc.def.ghi/1989/refCnt/poolCnt.1.16 , I do not > find a way to re-check only this one, old backup. > > --> Would it be a good idea to add an option to add a "-n num" flag to > BackupPC_refCountUpdate to be able to operate on a particular backup? > > > > Thanks for your guidance, > Raoul > > On 2020-08-24 20:39, Raoul Bhatia wrote: >> Hi Craig and Guillermo, >> >> On 2020-08-23 19:35, Craig Barratt via BackupPC-users wrote: >> >>> $Conf{PoolNightlyDigestCheckPercent} is in percent, so you should set >>> it to 100 to check all the pool file's MD5 digest against their file >>> names. >>> >>> As Guillermo mentions, to check the pool MD5 digests, you can set >>> temporarily set $Conf{PoolNightlyDigestCheckPercent} to 100 and >>> $Conf{PoolSizeNightlyUpdatePeriod} to 1. >> >> When reading the documentation, I also came across these options. >> However, I didn't dare to run backuppc / BackupPC_nightly, because >> from the documentation: >> >> Overnight, when BackupPC_nightly next runs, >> all the unused pool files will be deleted and >> this will recover the disk space used by the client's backups. >> >> I didn't want to end up with an empty pool... >> >>> If you stop BackupPC, to check all the pool digests, run: >>> >>>> BackupPC_refCountUpdate -m >>> If you want to also regenerate all the host reference counts (which >>> will take a long time), you could run: >>> >>>> BackupPC_refCountUpdate -m -F >> >> Meanwhile, with the kind help of the btrfs community, I figured out a >> way to get the damaged files. This process is not finished, yet, >> however, I have a first list: >> >> /mnt/backuppc/pc/abc.def.ghi/1989/refCnt/poolCnt.1.16 >> /mnt/backuppc/cpool/5c/c8/5cc9373a32e06baaa308a7b341db5ac9 >> /mnt/backuppc/cpool/b2/62/b3629c46481cb038682aea248c45b89f >> /mnt/backuppc/cpool/20/c6/21c61013d40e644af734e28459df0a1a >> /mnt/backuppc/cpool/8a/f8/8af935bc53f7199ed75a5695bfd57f26 >> >> FYI: The most recent backup from host abc.def.ghi is 2291, so 1989 is >> quite far in the past. >> >> How should I proceed when I have a list of broken files? >> Move them out from cpool and hope they will be re-synced by the next >> (full?) backup? >> >> Thanks, >> Raoul >> >>> Craig >>> >>> On Sun, Aug 23, 2020 at 6:45 AM Guillermo Rozas >>> <gui...@gm...> wrote: >>> >>> Hi Raoul, >>> >>> are you using BackupPC v4? If yes, you can use a modification of the >>> script I posted here: >>> https://sourceforge.net/p/backuppc/mailman/message/37032497/ >>> >>> In the latest version (4.4.0) you also have the config option >>> $Conf{PoolNightlyDigestCheckPercent}, which checks the md5 digest of >>> this fraction of the pool files each night. You can probably set it >>> to 1 and wait a night for it to run. >>> >>> Regards, >>> Guillermo >>> >>> On Sun, Aug 23, 2020 at 5:38 AM Raoul Bhatia <ra...@bh...> wrote: >>> Hi, >>> >>> related to my previous email, it seems that the cause of my issues >>> was a >>> file system corruption after a "power cut". >>> >>> I managed to recover (most of?) the data and would now like to do a >>> thorough check of the data. >>> >>> Is there any way to "fully verify" the integrity of my backuppc >>> installation, ideally in a nondestructive way ;-) >>> >>> Thanks, >>> Raoul >>> >>> PS. My backuppc process is stopped. >>> -- >>> DI (FH) Raoul Bhatia MSc >>> E-Mail. ra...@bh... >>> Tel. +43 699 10132530 > > > > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: https://github.com/backuppc/backuppc/wiki > Project: https://backuppc.github.io/backuppc/ -- DI (FH) Raoul Bhatia MSc E-Mail. ra...@bh... Tel. +43 699 10132530 |
From: Craig B. <cba...@us...> - 2020-06-22 20:24:00
|
BackupPC 4.4.0 <https://github.com/backuppc/backuppc/releases/tag/4.4.0> has been released on Github. This release contains several new features and some bug fixes. New features include: - any full/filled backup can be marked for keeping, which prevents any expiry or deletion - any backup can be annotated with a comment (eg, "prior to upgrade of xyz") - added metrics CGI (thanks to @jooola <https://github.com/jooola>) that replaces RSS and adds Prometheus support - tar XferMethod now supports xattrs and acls - rsync XferMethod now correctly supports xattrs on directories and symlinks - nightly pool scanning now verifies the md5 digests of a configurable fraction of pool files - code runs through perltidy so format is now uniform (thanks to @jooola <https://github.com/jooola>, with help from @shancock9 <https://github.com/shancock9> and @moisseev <https://github.com/moisseev>) New versions of BackupPC::XS (0.62 <https://github.com/backuppc/backuppc-xs/releases/tag/0.62>) and rsync-bpc ( 3.0.9.15 <https://github.com/backuppc/rsync-bpc/releases/tag/3.0.9.15>, 3.1.2.2 <https://github.com/backuppc/rsync-bpc/releases/tag/3.1.2.2> or 3.1.3beta0 <https://github.com/backuppc/rsync-bpc/releases/tag/3.1.3beta1>) are required. Thanks to Jeff Kosowsky for extensive testing and debugging for this release, particularly around xattrs. Enjoy! Craig Here are the more detailed changes: - Merged pull requests #325 <https://github.com/backuppc/backuppc/pull/325>, #326 <https://github.com/backuppc/backuppc/pull/326>, #329 <https://github.com/backuppc/backuppc/pull/329>, #330 <https://github.com/backuppc/backuppc/pull/330>, #334 <https://github.com/backuppc/backuppc/pull/334>, #336 <https://github.com/backuppc/backuppc/pull/336>, #337 <https://github.com/backuppc/backuppc/pull/337>, #338 <https://github.com/backuppc/backuppc/pull/338>, #342 <https://github.com/backuppc/backuppc/pull/342>, #343 <https://github.com/backuppc/backuppc/pull/343>, #344 <https://github.com/backuppc/backuppc/pull/344>, #345 <https://github.com/backuppc/backuppc/pull/345>, #347 <https://github.com/backuppc/backuppc/pull/347>, #348 <https://github.com/backuppc/backuppc/pull/348>, #349 <https://github.com/backuppc/backuppc/pull/349> - Filled/Full backups can now be marked as "keep", which excludes them from any expiry/deletion. Also, a backup-specific comment can be added to any backup to capture any important information about that backup (eg, "pre-upgrade of xyz"). - Added metrics CGI, which adds Prometheus support and replaces RSS, by @joola <https://github.com/joola> (#344 <https://github.com/backuppc/backuppc/pull/344>, #347 <https://github.com/backuppc/backuppc/pull/347>) - Tar XferMethod now supports xattrs and acls; xattrs should be compatible with rsync XferMethod, but acls are not - Sort open directories to top when browsing backup tree - Format code using perltidy, and included in pre-commit flow, by @joola <https://github.com/joola> (#334 <https://github.com/backuppc/backuppc/pull/334>, #337 <https://github.com/backuppc/backuppc/pull/337>, #342 <https://github.com/backuppc/backuppc/pull/342>, #343 <https://github.com/backuppc/backuppc/pull/343>, #345 <https://github.com/backuppc/backuppc/pull/345>). Thanks to @joola <https://github.com/joola> and @shancock9 <https://github.com/shancock9> (perltidy author) for significant effort and support, plus improvements in perltidy, to make this happen. - Added $Conf{PoolNightlyDigestCheckPercent}, which checks the md5 digest of this fraction of the pool files each night. - $Conf{ClientShareName2Path} is saved in backups file and the share to client path mapping is now displayed when you browse a backup so you know the actual client backup path for each share, if different from the share name - configure.pl now checks the per-host config.pl in a V3 upgrade to warn the user if $Conf{RsyncClientCmd} or $Conf{RsyncClientRestoreCmd} are used for that host, so that the new settings $Conf{RsyncSshArgs} and $Conf{RsyncClientPath} can be manually updated. - Fixed host mutex handling for dhcp hosts; shifted initial mutex requests to client programs - Updated webui icon, logo and favicon, by @moisseev <https://github.com/moisseev> (#325 <https://github.com/backuppc/backuppc/pull/325>, #326 <https://github.com/backuppc/backuppc/pull/326>, #329 <https://github.com/backuppc/backuppc/pull/329>, #330 <https://github.com/backuppc/backuppc/pull/330>) - Added $Conf{RsyncRestoreArgsExtra} for host-specific restore settings - Language files are now all use utf8 charsets - Bumped required version of BackupPC::XS to 0.62 and rsync-bpc to 3.0.9.15. - Ping failure message only written to stdout only if verbose - BackupPC_backupDelete removes partial v3 backup in HOST/new; fixes #324 <https://github.com/backuppc/backuppc/issues/324> reported by @thalueng <https://github.com/thalueng> - BackupPC_backupDelete adds -f option to over keep, if set - BackupPC_nightly: change -f to -F when running BackupPC_refCountUpdate during fsck - Better formatting of eval cmd result in cmdSystemOrEvalLong() - Remove zero count entries in per-backup and per-host poolCnt files - Add a fake version parameter to the CSS URL to overcome caching - Fixed ALRM typo in BackupPC_dump, by @rhansen <https://github.com/rhansen> (#348 <https://github.com/backuppc/backuppc/pull/348>) - Fixed command name in error message in BackupPC_archive, by @rhansen <https://github.com/rhansen> (#349 <https://github.com/backuppc/backuppc/pull/349>) - lib/BackupPC/Xfer/Rsync.pm skips adding --iconv option when $conf->{ClientCharset} is utf8 or empty, to avoid a long-standing rsync bug - lib/BackupPC/Xfer/Rsync.pm provides a more informative warning when the client rsync exits with an IO error, and also includes the IO error in the xferErr count - lib/BackupPC/Xfer/Smb.pm recognizes NT_STATUS_LOGON_FAILURE error - Increase text length in config editor fields, by @moisseev <https://github.com/moisseev> (#336 <https://github.com/backuppc/backuppc/pull/336>) - Typo fix in config.pl, by @cure <https://github.com/cure> (#338 <https://github.com/backuppc/backuppc/pull/338>) - Minor documentation updates, removing old SourceForge links |
From: Richard S. <hob...@gm...> - 2020-02-19 15:21:27
|
Update already submitted for Fedora[1] / EL 8[2]. I'm also testing some changes to the SELinux attributes and when I'm happy they're fine I'll update my COPR[3] for EL 7. It's got over 40k downloads so I don't want to create a huge issue if I messed it up :) Thanks, Richard [1] https://bodhi.fedoraproject.org/updates/FEDORA-2020-18c7d01dcf [2] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7536856c92 [3] https://copr.fedorainfracloud.org/coprs/hobbes1069/BackupPC/ |
From: Craig B. <cba...@us...> - 2020-02-19 15:03:36
|
BackupPC 4.3.2 <https://github.com/backuppc/backuppc/releases/tag/4.3.2> has been released on Github. This release has a number of bug fixes and a couple of minor feature additions. The changes since 4.3.1 are listed below. I'd like to thank the folks that contributed to this release, and people who helped debug issues. Enjoy! Craig - Merged pull requests #278 <https://github.com/backuppc/backuppc/pull/278>, #281 <https://github.com/backuppc/backuppc/pull/281>, #289 <https://github.com/backuppc/backuppc/pull/289>, #295 <https://github.com/backuppc/backuppc/pull/295>, #297 <https://github.com/backuppc/backuppc/pull/297>, #307 <https://github.com/backuppc/backuppc/pull/307>, #308 <https://github.com/backuppc/backuppc/pull/308>, #311 <https://github.com/backuppc/backuppc/pull/311>, #312 <https://github.com/backuppc/backuppc/pull/312>, #313 <https://github.com/backuppc/backuppc/pull/313>, #314 <https://github.com/backuppc/backuppc/pull/314>. - Added per-host read/write exclusivity to worker programs, so command-line programs don't collide with backups or other operations; reported by @hamster65 <https://github.com/hamster65> (issue #299 <https://github.com/backuppc/backuppc/issues/299>) - Added $Conf{RsyncIncrArgsExtra} (issue #284 <https://github.com/backuppc/backuppc/issues/284>) - Added $Conf{ClientShareName2Path}, which allows mapping of share names/path to real paths on the client (eg, to backup a snapshot that's in a different directory to the share name path) - Fixed v3 digest calculation in bin/BackupPC_backupDuplicate and bin/BackupPC_migrateV3toV4; reported by @palmtop <https://github.com/palmtop> (issue #291 <https://github.com/backuppc/backuppc/issues/291>) - Improved handling of BackupPC_nightly running for more than 24 hours: drop next queued run, and provide better log messages; reported by @guestisp <https://github.com/guestisp> (issue #303 <https://github.com/backuppc/backuppc/issues/303>) - Improved error checking on $Conf{BackupPCNightlyPeriod}, and update $Info->{NightlyPhase} if it's larger than $Conf{BackupPCNightlyPeriod}; reported by @guestisp <https://github.com/guestisp> (issue #304 <https://github.com/backuppc/backuppc/issues/304>) - Fixed warnings in bin/BackupPC, submitted by @moisseev <https://github.com/moisseev> (#278 <https://github.com/backuppc/backuppc/pull/278>) - Avoid rrd updates using the same time stamp, submitted by @moisseev <https://github.com/moisseev> (#311 <https://github.com/backuppc/backuppc/pull/311>, issue #305 <https://github.com/backuppc/backuppc/issues/305>) - Removed unused counting of renamed files, submitted by @moisseev <https://github.com/moisseev> (#281 <https://github.com/backuppc/backuppc/pull/281>) - Make tar xfer output parsing compatible with FreeBSD tar, submitted by @haarp <https://github.com/haarp> (#289 <https://github.com/backuppc/backuppc/pull/289>) - Fix daemon stdin open to read mode, submitted by @moisseev <https://github.com/moisseev> (#308 <https://github.com/backuppc/backuppc/pull/308>) - Hosts config editor table layout CGI fix, submitted by @steven-de-wit <https://github.com/steven-de-wit> (#297 <https://github.com/backuppc/backuppc/pull/297>) - Fixes to French translation, submitted by @pjoubert- <https://github.com/pjoubert-> (#295 <https://github.com/backuppc/backuppc/pull/295>) - Fixes to Italian translation, submitted by @guestisp <https://github.com/guestisp> (#314 <https://github.com/backuppc/backuppc/pull/314>) - Updated comments for Apache 2.4 config in httpd/src/BackupPC.conf, submitted by @NotAProfessionalDeveloper <https://github.com/NotAProfessionalDeveloper> (#307 <https://github.com/backuppc/backuppc/pull/307>) - Documentation update for SCGI prerequisite, submitted by @guestisp <https://github.com/guestisp> (#312 <https://github.com/backuppc/backuppc/pull/312>) - Documentation update for nginx config, submitted by @guestisp <https://github.com/guestisp> (#313 <https://github.com/backuppc/backuppc/pull/313>) |
From: Craig B. <cba...@us...> - 2019-07-15 01:15:48
|
BackupPC 4.3.1 <https://github.com/backuppc/backuppc/releases/tag/4.3.1> has been released on Github. This release has a number of bug fixes. In addition, rsync-bpc 3.0.9.14 <https://github.com/backuppc/rsync-bpc/releases/tag/3.0.9.14> and rsync-bpc 3.1.2.1 <https://github.com/backuppc/rsync-bpc/releases/tag/3.1.2.1> have been released. Upgrading is recommended. The changes since 4.3.0 are listed below. I'd like to thank the folks that contributed to this release, and people who helped debug issues. Enjoy! Craig #------------------------------------------------------------------------ # Version 4.3.1, 14 Jul 2019 #------------------------------------------------------------------------ - Merged pull request #240 <https://github.com/backuppc/backuppc/pull/240>. - Fixed CGI host summary columns for new Comment value; reported by @karlis-irmejs <https://github.com/karlis-irmejs> (#245 <https://github.com/backuppc/backuppc/issues/245>). - Added support to BackupPC_tarCreate for PAX headers to allow large metadata values to be correctly encoded; reported by @seblu <https://github.com/seblu> (#254 <https://github.com/backuppc/backuppc/issues/254>). - Fixed regexp in BackupPC so that versions like rsync-bpc 3.1.2beta0 are matched. PR submitted by Adrien Ferrand (#240 <https://github.com/backuppc/backuppc/pull/240>). - Added more details to error messages when failing to connect to BackupPC server; reported by @dmak <https://github.com/dmak>(#261 <https://github.com/backuppc/backuppc/issues/261>). - bin/BackupPC Main_Initialize() checks if a BackupPC server is running by trying to connect to it, in addition to existing check that PID exists; reported by @toggoboge <https://github.com/toggoboge> (#264 <https://github.com/backuppc/backuppc/issues/264>). - Fixed utf8 encoded share names in deletion of orphan RsyncShareNames, reported by @Yann79 <https://github.com/Yann79>(#266 <https://github.com/backuppc/backuppc/issues/266>). - Fixed %Conf passing to perl code version of $bpc->cmdSystemOrEval; reported by Jeff Kosowsky. - BackupPC_backupDelete removes files with BPC_FTYPE_DELETED from filled merged backup; reported by Jeff Kosowsky. - added Data::Dumper SortKeys(1) to lib/BackupPC/Storage/Text.pm so that config hash writes have repeatable order; suggested by @kr4ut <https://github.com/kr4ut> (#275 <https://github.com/backuppc/backuppc/issues/275>). - bin/BackupPC_archive: use $bpc->openPCLogFile() instead of manual LOG file rotation - lib/BackupPC/CGI/Archive.pm: create client directory if it doesn't exist |
From: Craig B. <cba...@us...> - 2018-11-26 18:45:22
|
BackupPC 4.3.0 <https://github.com/backuppc/backuppc/releases/tag/4.3.0> has been released on Github. This release has a few new features (eg, checking inode usage on the BackupPC filesystem) and some improvements (eg, html table sorting), in addition to a number of bug fixes. In addition, rsync-bpc 3.0.9.13 <https://github.com/backuppc/rsync-bpc/releases/tag/3.0.9.13> and backuppc-xs 0.58 <https://github.com/backuppc/backuppc-xs/releases/tag/0.58> have been released. Those are very minor updates, and upgrading from rsync-bpc 3.0.9.12 or backuppc-xs 0.57 is not necessary to run BackupPC 4.3.0. The changes since 4.2.1 are listed below. I'd like to thank the folks that contributed to this release, and people who helped debug issues. Enjoy! Craig #------------------------------------------------------------------------ # Version 4.3.0, 25 Nov 2018 #------------------------------------------------------------------------ This release includes a couple of new features (eg, checking inode usage on the BackupPC filesystem) and a few improvements (eg, html table sorting), and several bug fixes: - Merged pull requests #200 <https://github.com/backuppc/backuppc/pull/200>, #208 <https://github.com/backuppc/backuppc/pull/208>, #216 <https://github.com/backuppc/backuppc/pull/216>, #217 <https://github.com/backuppc/backuppc/pull/217>, #229 <https://github.com/backuppc/backuppc/pull/229>, #230 <https://github.com/backuppc/backuppc/pull/230>, #231 <https://github.com/backuppc/backuppc/pull/231>, #232 <https://github.com/backuppc/backuppc/pull/232>, #233 <https://github.com/backuppc/backuppc/pull/233>, #235 <https://github.com/backuppc/backuppc/pull/235>. - Added checking of file system inode usage, with new configuration settings $Conf{DfInodeUsageCmd} and $Conf{DfMaxInodeUsagePct}. - bin/BackupPC_tarExtract: fixes to hardlink handling on incrementals, plus cleanup - bin/BackupPC_backupDuplicate: fixed directory creation for copying v3 backups. - bin/BackupPC_backupDelete: couple of inode-related bug fixes; also do fsck if $Conf{RefCntFsck} != 0. - bin/BackupPC: fixed handling of dhcp hosts, reported by Jean-Marc. - bin/BackupPC: improved version check of rsync_bpc to allow period before "beta", reported by @ktenney <https://github.com/ktenney> in issue #214 <https://github.com/backuppc/backuppc/issues/214>. - Added $Conf{EMailAdminSubject} to allow the admin email subject to be set. - Changed default $Conf{CgiDateFormatMMDD} to 2 (YYYY-MM-DD), submitted by @moisseev <https://github.com/moisseev> (#231 <https://github.com/backuppc/backuppc/pull/231>). - Allow multiple groups in $Conf{CgiAdminUserGroup}, submitted by @moisseev <https://github.com/moisseev> (#235 <https://github.com/backuppc/backuppc/pull/235>). - Improvements to html table sorting, and made more tables sortable, submitted by @brenard <https://github.com/brenard> and @moisseev <https://github.com/moisseev> (issue #199 <https://github.com/backuppc/backuppc/issues/199>, PRs #200 <https://github.com/backuppc/backuppc/pull/200>, #229 <https://github.com/backuppc/backuppc/pull/229>, #230 <https://github.com/backuppc/backuppc/pull/230>, #232 <https://github.com/backuppc/backuppc/pull/232>). - Add action type column to queue status page (#208 <https://github.com/backuppc/backuppc/pull/208>), submitted by @brenard <https://github.com/brenard>. - lib/BackupPC/CGI/Summary.pm: host summary only reports age of completed backups (not partial or active), suggested by Michael Selway. - lib/BackupPC/CGI/HostInfo.pm: show active backup as partial if there is no job running (to handle case of abnormal exit of BackupPC), reported by @8666 <https://github.com/8666> in issue #220 <https://github.com/backuppc/backuppc/issues/220>. - systemd/src/backuppc.service: added ExecReload, submitted by @opoplawski <https://github.com/opoplawski> (#233 <https://github.com/backuppc/backuppc/pull/233>). - lib/BackupPC/Xfer/Rsync.pm: empty $Conf{RsyncdPasswd} is no longer fatal; removed remaining mentions of RsyncdAuthRequired from conf/ config.pl and lib/BackupPC/Config/Meta.pm; reported by @jooola <https://github.com/jooola> in issue #224 <https://github.com/backuppc/backuppc/issues/224>. - bin/BackupPC_dump: moved alarm($Conf{ClientTimeout}) to after all the pre-backup code (including expiry, duplication etc of backups, which could be slow) reported by Michael Selway. - bin/BackupPC_refCntUpdate: added a couple of bpc_progress_state prints to improve status reporting during nightly (-m), reported by Michael Selway. - lib/BackupPC/CGI/RSS.pm: added Disabled value to host info (copied from $Conf{BackupsDisable}); suggested by @danielmotaleite <https://github.com/danielmotaleite> (issue #222 <https://github.com/backuppc/backuppc/issues/222>). - lib/BackupPC/Xfer/Rsync.pm: added checks for a couple of common rsync file error and error exit messages that now increment the xferErrs count. - bin/BackupPC_tarExtract: errors related to a particular file are counted as Xfer errors, rather than considered fatal. - bin/BackupPC_dump: added check that $LogFd is defined before using it. - lib/BackupPC/Lib.pm: replaced exit() with POSIX::_exit() so that object destruction is skipped in the child process. This fixes corruption of the compressed XferLOG file if the exec of $Conf{DumpPostUserCmd} fails. - conf/config.pl: updated project home page to https://backuppc.github.io/backuppc in email message footers. |
From: Craig B. <cba...@us...> - 2018-11-10 02:29:01
|
Richard, The next BackupPC release should hopefully be before the end of November. Craig On Tue, Nov 6, 2018 at 9:12 AM Richard Shaw <hob...@gm...> wrote: > I went ahead and merged the service file update in Fedora but was going to > hold off on doing builds if a new release was getting close. > > Thanks, > Richard > _______________________________________________ > BackupPC-devel mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > |
From: Richard S. <hob...@gm...> - 2018-11-06 17:11:37
|
I went ahead and merged the service file update in Fedora but was going to hold off on doing builds if a new release was getting close. Thanks, Richard |
From: Craig B. <cba...@us...> - 2018-05-12 17:42:24
|
BackupPC 4.2.1 <https://github.com/backuppc/backuppc/releases/tag/4.2.1> has been released on Github. The changes since 4.2.0 <https://github.com/backuppc/backuppc/releases/tag/4.2.0> are listed below. This release allows the new backup delete CGI feature to be disabled for users and/or admins, plus a couple of minor bug fixes. Enjoy! Craig #------------------------------------------------------------------------ # Version 4.2.1, 7 May 2018 #------------------------------------------------------------------------ This release allows the new backup delete CGI feature to be disabled for users and/or admins, plus a couple of minor bug fixes: - Merged pull request #195 <https://github.com/backuppc/backuppc/pull/195>. - Added new config variable $Conf{CgiUserDeleteBackupEnable} that sets whether users and admins can delete backups via the CGI interface. The default value is 0, which means it's disabled for regular users but available for admins. - Fixed delete backup bug in bin/BackupPC_Admin_SCGI reported by Julian Zielke in issue #193 <https://github.com/backuppc/backuppc/issues/193>. - Added check to dirCacheFlush() in bin/BackupPC_tarExtract to skip files that don't have attributes; reported by Tarak Patel. - Removed extraneous duplicate variable assignment in lib/BackupPC/CGI/GeneralInfo.pm, from @moisseev <https://github.com/moisseev> (#195 <https://github.com/backuppc/backuppc/pull/195>). |
From: Craig B. <cba...@us...> - 2018-04-14 23:11:22
|
BackupPC 4.2.0 <https://github.com/backuppc/backuppc/releases/tag/4.2.0> has been released on Github. The changes since 4.1.5 <https://github.com/backuppc/backuppc/releases/tag/4.1.5> are listed below. The biggest change is a new feature in the web interface written by @moisseev that allows prior backups to be deleted. Enjoy! Craig #------------------------------------------------------------------------ # Version 4.2.0, 8 Apr 2018 #------------------------------------------------------------------------ Merged pull requests #160, #190. * Backups can now be deleted via the CGI interface, written by @moisseev (#160). * bin/BackupPC_backupDelete: added -L option that puts output into client LOG file, to support CGI backup deletion. * Added support for a user-editable comment per host, via a new ClientComment config parameter, requested by @andrewmaksymowsky. * bin/BackupPC_tarExtract: Added support for pax headers, which smbclient uses for long file names * bin/BackupPC_backupDelete: make sure directory exists when renaming tree from deleted backup. * lib/BackupPC/Xfer/Smb.pm: ignore empty output lines from smbclient; fixes issue #159. * bin/BackupPC: improved several of the exit error messages. * lib/BackupPC/Xfer/Rsync.pm: added shareName to RsyncArgs* argument substitutions; suggested by Alex Kobel. * conf/BackupPC_stnd.css: removed import url(' https://fonts.googleapis.com/css....' suggested by @MartijnRas in issue #174. |
From: Michael S. <mic...@me...> - 2018-02-03 07:34:18
|
On 2018-02-02 01:20, Marc Gilliatt wrote: > Can I please get an update on my issue, please? > > This is our only source of backing up our servers, we are not backing > up at the current moment because of this issue. > > As mentioned, I upgraded backuppc from 3.3.1 to 4.1.3 from which I > download the tar file from the backuppc website. > > However, when I see what version of backuppc I'm currently running > right now, it's still 3.3.1? > > I'm not sure what I've done wrong? > > ------------------------- This will be somewhat backwards due to top-posting, but I'll start here -- the first thing you've done wrong is persisted in using the developer list, but it is a user issue. You're much more likely to get faster and better responses on the correct list. I've taken the liberty of crossposting this reply to the users list (see above) in the hopes that we can terminate this thread in the developer discussion, where it does not belong. > > FROM: Marc Gilliatt <m.g...@li...> > SENT: 31 January 2018 10:17 > TO: Michael Stowe; Developers discussion > SUBJECT: Re: [BackupPC-devel] SMB Windows share not backing up - > NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* > > I apologize for the multiple emails. > > I am now getting the following message when I go into the GUI.... > > INTERNAL SERVER ERROR > > The server encountered an internal error or misconfiguration and was > unable to complete your request. > > Please contact the server administrator at webmaster@localhost to > inform them of the time this error occurred, and the actions you > performed just before this error. > > More information about this error may be available in the server error > log. > ------------------------- > Apache/2.4.18 (Ubuntu) Server at backuppc01.dsdb.int Port 80 > > Any ideas or suggestions on how to fix this, please? This is our only > source of backing up our servers. > ------------------------- That part about more information available in the server error log is usually a good clue -- what does the server error log say? > FROM: Marc Gilliatt <m.g...@li...> > SENT: 31 January 2018 09:39 > TO: Michael Stowe; Developers discussion > SUBJECT: Re: [BackupPC-devel] SMB Windows share not backing up - > NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* > > I tried to download backuppc-4.1.3 from the backuppc website. > > The upgrade went fine, however, I backuppc.server won't start now? > > In the GUI, I'm getting..... > > ERROR: UNABLE TO CONNECT TO BACKUPPC SERVER > > This CGI script (/backuppc/index.cgi) is unable to connect to the > BackupPC server on backuppc01 port -1. > The error was: unix connect: No such file or directory. > Perhaps the BackupPC server is not running or there is a configuration > error. Please report this to your Sys Admin. > > And when I try to run "service backuppc restart", Im getting..... > > Job for backuppc.service failed because the control process exited > with error code. See "systemctl status backuppc.service" and > "journalctl -xe" for details. > > And when I run "systemctl status backuppc.service", Im getting..... > > backuppc.service - LSB: Launch backuppc server > Loaded: loaded (/etc/init.d/backuppc; bad; vendor preset: enabled) > > Active: failed (Result: exit-code) since Wed 2018-01-31 09:33:33 GMT; > 20s ago > Docs: man:systemd-sysv-generator(8) > Process: 29163 ExecStop=/etc/init.d/backuppc stop (code=exited, > status=0/SUCCESS) > > Process: 29425 ExecStart=/etc/init.d/backuppc start (code=exited, > status=1/FAILURE) > Jan 31 09:33:33 backuppc01 systemd[1]: Starting LSB: Launch backuppc > server... > Jan 31 09:33:33 backuppc01 backuppc[29425]: * Starting backuppc... > > Jan 31 09:33:33 backuppc01 backuppc[29425]: BackupPC cannot be > started because important parameters are missing from config.pl. > > Jan 31 09:33:33 backuppc01 backuppc[29425]: If you just upgraded > BackupPC, please update /etc/backuppc/config.pl. > > Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Control > process exited, code=exited status=1 > > Jan 31 09:33:33 backuppc01 systemd[1]: Failed to start LSB: Launch > backuppc server. > > Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Unit entered > failed state. > > Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Failed with > result 'exit-code'. > > I followed the upgrade instructions correctly. > > I have no working backuppc now...any ideas, please? > ------------------------- I can't speak to which upgrade instructions you followed and whether or not you did so correctly, but this is telling you that you're trying to start a version 4 server with a version 3 config.pl, which probably isn't going to work well. > FROM: Marc Gilliatt <m.g...@li...> > SENT: 31 January 2018 08:37 > TO: Michael Stowe > CC: Developers discussion > SUBJECT: Re: [BackupPC-devel] SMB Windows share not backing up - > NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* > > My distro is Ubuntu 16.04.3 > > I try to upgrade just backuppc, and it's telling me that "backuppc is > already the newest version (3.3.1-2ubuntu3.3)." > > I'm not sure on how I can upgrade backuppc to 3.3.2 or later as you > suggested? > > ------------------------- > > FROM: Michael Stowe <mic...@me...> > SENT: 31 January 2018 07:49 > TO: Marc Gilliatt > CC: Developers discussion > SUBJECT: Re: [BackupPC-devel] SMB Windows share not backing up - > NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* > > On 2018-01-30 02:27, Marc Gilliatt wrote: > >> Sincere apologies for the late reply. >> >> You mention that version 3.3.1 doesn’t work with 4.3 of smbclient. >> >> How do I downgrade the smbclient, please? > > Unfortunately, that highly depends on your distro and/or flavor or how > you've installed samba or smbclient in the first place. For some > distros, it's as simple as specifying the version to the package > manager or using the recommended downgrade path, for others, it can be > much more complicated, requiring building from source or alternative > repositories. > > It might be simpler to upgrade to version 3.3.2 (or later) instead. > > IIRC, the issue is that smbclient changed its reporting, so that > BackupPC has trouble recognizing when the files are actually > successfully retrieved, when in fact they are. |
From: Marc G. <m.g...@li...> - 2018-02-02 09:36:02
|
Can I please get an update on my issue, please? This is our only source of backing up our servers, we are not backing up at the current moment because of this issue. As mentioned, I upgraded backuppc from 3.3.1 to 4.1.3 from which I download the tar file from the backuppc website. However, when I see what version of backuppc I'm currently running right now, it's still 3.3.1? I'm not sure what I've done wrong? ________________________________ From: Marc Gilliatt <m.g...@li...> Sent: 31 January 2018 10:17 To: Michael Stowe; Developers discussion Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* I apologize for the multiple emails. I am now getting the following message when I go into the GUI.... Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at webmaster@localhost to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. ________________________________ Apache/2.4.18 (Ubuntu) Server at backuppc01.dsdb.int Port 80 Any ideas or suggestions on how to fix this, please? This is our only source of backing up our servers. ________________________________ From: Marc Gilliatt <m.g...@li...> Sent: 31 January 2018 09:39 To: Michael Stowe; Developers discussion Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* I tried to download backuppc-4.1.3 from the backuppc website. The upgrade went fine, however, I backuppc.server won't start now? In the GUI, I'm getting..... Error: Unable to connect to BackupPC server This CGI script (/backuppc/index.cgi) is unable to connect to the BackupPC server on backuppc01 port -1. The error was: unix connect: No such file or directory. Perhaps the BackupPC server is not running or there is a configuration error. Please report this to your Sys Admin. And when I try to run "service backuppc restart", Im getting..... Job for backuppc.service failed because the control process exited with error code. See "systemctl status backuppc.service" and "journalctl -xe" for details. And when I run "systemctl status backuppc.service", Im getting..... backuppc.service - LSB: Launch backuppc server Loaded: loaded (/etc/init.d/backuppc; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-01-31 09:33:33 GMT; 20s ago Docs: man:systemd-sysv-generator(8) Process: 29163 ExecStop=/etc/init.d/backuppc stop (code=exited, status=0/SUCCESS) Process: 29425 ExecStart=/etc/init.d/backuppc start (code=exited, status=1/FAILURE) Jan 31 09:33:33 backuppc01 systemd[1]: Starting LSB: Launch backuppc server... Jan 31 09:33:33 backuppc01 backuppc[29425]: * Starting backuppc... Jan 31 09:33:33 backuppc01 backuppc[29425]: BackupPC cannot be started because important parameters are missing from config.pl. Jan 31 09:33:33 backuppc01 backuppc[29425]: If you just upgraded BackupPC, please update /etc/backuppc/config.pl. Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Control process exited, code=exited status=1 Jan 31 09:33:33 backuppc01 systemd[1]: Failed to start LSB: Launch backuppc server. Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Unit entered failed state. Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Failed with result 'exit-code'. I followed the upgrade instructions correctly. I have no working backuppc now...any ideas, please? ________________________________ From: Marc Gilliatt <m.g...@li...> Sent: 31 January 2018 08:37 To: Michael Stowe Cc: Developers discussion Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* My distro is Ubuntu 16.04.3 I try to upgrade just backuppc, and it's telling me that "backuppc is already the newest version (3.3.1-2ubuntu3.3)." I'm not sure on how I can upgrade backuppc to 3.3.2 or later as you suggested? ________________________________ From: Michael Stowe <mic...@me...> Sent: 31 January 2018 07:49 To: Marc Gilliatt Cc: Developers discussion Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* On 2018-01-30 02:27, Marc Gilliatt wrote: Sincere apologies for the late reply. You mention that version 3.3.1 doesn’t work with 4.3 of smbclient. How do I downgrade the smbclient, please? Unfortunately, that highly depends on your distro and/or flavor or how you've installed samba or smbclient in the first place. For some distros, it's as simple as specifying the version to the package manager or using the recommended downgrade path, for others, it can be much more complicated, requiring building from source or alternative repositories. It might be simpler to upgrade to version 3.3.2 (or later) instead. IIRC, the issue is that smbclient changed its reporting, so that BackupPC has trouble recognizing when the files are actually successfully retrieved, when in fact they are. |
From: Marc G. <m.g...@li...> - 2018-01-31 10:17:43
|
I apologize for the multiple emails. I am now getting the following message when I go into the GUI.... Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator at webmaster@localhost to inform them of the time this error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log. ________________________________ Apache/2.4.18 (Ubuntu) Server at backuppc01.dsdb.int Port 80 Any ideas or suggestions on how to fix this, please? This is our only source of backing up our servers. ________________________________ From: Marc Gilliatt <m.g...@li...> Sent: 31 January 2018 09:39 To: Michael Stowe; Developers discussion Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* I tried to download backuppc-4.1.3 from the backuppc website. The upgrade went fine, however, I backuppc.server won't start now? In the GUI, I'm getting..... Error: Unable to connect to BackupPC server This CGI script (/backuppc/index.cgi) is unable to connect to the BackupPC server on backuppc01 port -1. The error was: unix connect: No such file or directory. Perhaps the BackupPC server is not running or there is a configuration error. Please report this to your Sys Admin. And when I try to run "service backuppc restart", Im getting..... Job for backuppc.service failed because the control process exited with error code. See "systemctl status backuppc.service" and "journalctl -xe" for details. And when I run "systemctl status backuppc.service", Im getting..... backuppc.service - LSB: Launch backuppc server Loaded: loaded (/etc/init.d/backuppc; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-01-31 09:33:33 GMT; 20s ago Docs: man:systemd-sysv-generator(8) Process: 29163 ExecStop=/etc/init.d/backuppc stop (code=exited, status=0/SUCCESS) Process: 29425 ExecStart=/etc/init.d/backuppc start (code=exited, status=1/FAILURE) Jan 31 09:33:33 backuppc01 systemd[1]: Starting LSB: Launch backuppc server... Jan 31 09:33:33 backuppc01 backuppc[29425]: * Starting backuppc... Jan 31 09:33:33 backuppc01 backuppc[29425]: BackupPC cannot be started because important parameters are missing from config.pl. Jan 31 09:33:33 backuppc01 backuppc[29425]: If you just upgraded BackupPC, please update /etc/backuppc/config.pl. Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Control process exited, code=exited status=1 Jan 31 09:33:33 backuppc01 systemd[1]: Failed to start LSB: Launch backuppc server. Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Unit entered failed state. Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Failed with result 'exit-code'. I followed the upgrade instructions correctly. I have no working backuppc now...any ideas, please? ________________________________ From: Marc Gilliatt <m.g...@li...> Sent: 31 January 2018 08:37 To: Michael Stowe Cc: Developers discussion Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* My distro is Ubuntu 16.04.3 I try to upgrade just backuppc, and it's telling me that "backuppc is already the newest version (3.3.1-2ubuntu3.3)." I'm not sure on how I can upgrade backuppc to 3.3.2 or later as you suggested? ________________________________ From: Michael Stowe <mic...@me...> Sent: 31 January 2018 07:49 To: Marc Gilliatt Cc: Developers discussion Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* On 2018-01-30 02:27, Marc Gilliatt wrote: Sincere apologies for the late reply. You mention that version 3.3.1 doesn’t work with 4.3 of smbclient. How do I downgrade the smbclient, please? Unfortunately, that highly depends on your distro and/or flavor or how you've installed samba or smbclient in the first place. For some distros, it's as simple as specifying the version to the package manager or using the recommended downgrade path, for others, it can be much more complicated, requiring building from source or alternative repositories. It might be simpler to upgrade to version 3.3.2 (or later) instead. IIRC, the issue is that smbclient changed its reporting, so that BackupPC has trouble recognizing when the files are actually successfully retrieved, when in fact they are. |
From: Marc G. <m.g...@li...> - 2018-01-31 09:55:04
|
I tried to download backuppc-4.1.3 from the backuppc website. The upgrade went fine, however, I backuppc.server won't start now? In the GUI, I'm getting..... Error: Unable to connect to BackupPC server This CGI script (/backuppc/index.cgi) is unable to connect to the BackupPC server on backuppc01 port -1. The error was: unix connect: No such file or directory. Perhaps the BackupPC server is not running or there is a configuration error. Please report this to your Sys Admin. And when I try to run "service backuppc restart", Im getting..... Job for backuppc.service failed because the control process exited with error code. See "systemctl status backuppc.service" and "journalctl -xe" for details. And when I run "systemctl status backuppc.service", Im getting..... backuppc.service - LSB: Launch backuppc server Loaded: loaded (/etc/init.d/backuppc; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-01-31 09:33:33 GMT; 20s ago Docs: man:systemd-sysv-generator(8) Process: 29163 ExecStop=/etc/init.d/backuppc stop (code=exited, status=0/SUCCESS) Process: 29425 ExecStart=/etc/init.d/backuppc start (code=exited, status=1/FAILURE) Jan 31 09:33:33 backuppc01 systemd[1]: Starting LSB: Launch backuppc server... Jan 31 09:33:33 backuppc01 backuppc[29425]: * Starting backuppc... Jan 31 09:33:33 backuppc01 backuppc[29425]: BackupPC cannot be started because important parameters are missing from config.pl. Jan 31 09:33:33 backuppc01 backuppc[29425]: If you just upgraded BackupPC, please update /etc/backuppc/config.pl. Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Control process exited, code=exited status=1 Jan 31 09:33:33 backuppc01 systemd[1]: Failed to start LSB: Launch backuppc server. Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Unit entered failed state. Jan 31 09:33:33 backuppc01 systemd[1]: backuppc.service: Failed with result 'exit-code'. I followed the upgrade instructions correctly. I have no working backuppc now...any ideas, please? ________________________________ From: Marc Gilliatt <m.g...@li...> Sent: 31 January 2018 08:37 To: Michael Stowe Cc: Developers discussion Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* My distro is Ubuntu 16.04.3 I try to upgrade just backuppc, and it's telling me that "backuppc is already the newest version (3.3.1-2ubuntu3.3)." I'm not sure on how I can upgrade backuppc to 3.3.2 or later as you suggested? ________________________________ From: Michael Stowe <mic...@me...> Sent: 31 January 2018 07:49 To: Marc Gilliatt Cc: Developers discussion Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* On 2018-01-30 02:27, Marc Gilliatt wrote: Sincere apologies for the late reply. You mention that version 3.3.1 doesn’t work with 4.3 of smbclient. How do I downgrade the smbclient, please? Unfortunately, that highly depends on your distro and/or flavor or how you've installed samba or smbclient in the first place. For some distros, it's as simple as specifying the version to the package manager or using the recommended downgrade path, for others, it can be much more complicated, requiring building from source or alternative repositories. It might be simpler to upgrade to version 3.3.2 (or later) instead. IIRC, the issue is that smbclient changed its reporting, so that BackupPC has trouble recognizing when the files are actually successfully retrieved, when in fact they are. |
From: Marc G. <m.g...@li...> - 2018-01-31 08:37:44
|
My distro is Ubuntu 16.04.3 I try to upgrade just backuppc, and it's telling me that "backuppc is already the newest version (3.3.1-2ubuntu3.3)." I'm not sure on how I can upgrade backuppc to 3.3.2 or later as you suggested? ________________________________ From: Michael Stowe <mic...@me...> Sent: 31 January 2018 07:49 To: Marc Gilliatt Cc: Developers discussion Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* On 2018-01-30 02:27, Marc Gilliatt wrote: Sincere apologies for the late reply. You mention that version 3.3.1 doesn’t work with 4.3 of smbclient. How do I downgrade the smbclient, please? Unfortunately, that highly depends on your distro and/or flavor or how you've installed samba or smbclient in the first place. For some distros, it's as simple as specifying the version to the package manager or using the recommended downgrade path, for others, it can be much more complicated, requiring building from source or alternative repositories. It might be simpler to upgrade to version 3.3.2 (or later) instead. IIRC, the issue is that smbclient changed its reporting, so that BackupPC has trouble recognizing when the files are actually successfully retrieved, when in fact they are. |
From: Michael S. <mic...@me...> - 2018-01-31 07:49:59
|
On 2018-01-30 02:27, Marc Gilliatt wrote: > Sincere apologies for the late reply. > > You mention that version 3.3.1 doesn’t work with 4.3 of smbclient. > > How do I downgrade the smbclient, please? Unfortunately, that highly depends on your distro and/or flavor or how you've installed samba or smbclient in the first place. For some distros, it's as simple as specifying the version to the package manager or using the recommended downgrade path, for others, it can be much more complicated, requiring building from source or alternative repositories. It might be simpler to upgrade to version 3.3.2 (or later) instead. IIRC, the issue is that smbclient changed its reporting, so that BackupPC has trouble recognizing when the files are actually successfully retrieved, when in fact they are. |
From: Marc G. <m.g...@li...> - 2018-01-30 10:28:11
|
Sincere apologies for the late reply. You mention that version 3.3.1 doesn’t work with 4.3 of smbclient. How do I downgrade the smbclient, please? ________________________________ From: Michael Stowe <mic...@me...> Sent: 18 January 2018 18:10 To: Developers discussion Cc: Craig Barratt Subject: Re: [BackupPC-devel] SMB Windows share not backing up - NT_STATUS_ACCESS_DENIED listing \System Volume Information\SRM\* On Jan 18, 2018, at 12:53 AM, Marc Gilliatt <m.g...@li...<mailto:m.g...@li...>> wrote: Hi Craig, Are there any updates on my issue, please? A quick recap of where we landed: (Craig): version 3.3.1 doesn’t work with 4.3 of smbclient. (Marc): I am running those exact versions What update are you expecting? Unless you downgrade smbclient or upgrade BackupPC, we can only reiterate, yes, you are continuing to encounter a known issue. |