The former which might help with the latter...
Dave Sherohman via BackupPC-users wrote at about 14:02:09 +0100 on Friday, 
November 18, 2022:
 > Am I understanding correctly that backuppcfs would just provide a more 
 > convenient way to check the ownership of backed-up files instead of 
 > getting a tarball to see their ownership?  Or would it also provide 
 > additional functionality for helping to track down why they have 
 > incorrect ownership?
 > 
 > On 11/16/22 20:56, backu...@kosowsky.org wrote:
 > > 'backuppcfs' is a (read-only) FUSE fileystem that allows you to see
 > > the contents/ownership/perms/dates/Xattrs etc. of any file in your
 > > backup.
 > >
 > > It is great for troubleshooting as well as for partial restores...
 > >
 > > Dave Sherohman via BackupPC-users wrote at about 09:54:27 +0100 on 
 > > Wednesday, November 16, 2022:
 > >   > I've just encountered the same problem from issue #171 on github, "on
 > >   > restore all files owner root"
 > >   > https://github.com/backuppc/backuppc/issues/171
 > >   >
 > >   > My RsyncRestoreArgs are the same as reported there, with the exception
 > >   > that I don't have --ignore-times.  I have done the tar restore check
 > >   > there and confirmed that the files in the tarball show root/root 
 > > ownership.
 > >   >
 > >   > The troubleshooting in the ticket ended with the suggestion "Can you
 > >   > look in the most recent full backup XferLOG file and see what
 > >   > permissions are transferred for that file? You might need to increase
 > >   > the XferLogLevel to 2 or 3 and then do a new full backup to see
 > >   > permissions on unchanged files." which the user in that case did not
 > >   > respond to.  I have attempted that step, but, even with XferLogLevel 
 > > set
 > >   > to 3 (as a per-host override) and doing a full backup of my test host,
 > >   > XferLOG.[backup number] does not contain any individual file
 > >   > names/paths, so I'm not able to check the permissions there.  Latest
 > >   > test XferLOG attached for reference.
 > >   >
 > >   > (I'm actually a little skeptical at this point as to whether
 > >   > XferLogLevel even does anything these days, as there are no obvious
 > >   > differences in the XferLOG files at log level 1 vs. log level 3.)
 > >   >
 > >   > What's my next step, and is there any further documentation on this
 > >   > problem aside from the ticket for #171?
 > >   >
 > >   > My overall setup is a Debian 11 server running debianized BPC 4.4.0-3
 > >   > (the latest version from the stable repo) with a mixed pool of clients 
 > > -
 > >   > mostly Debian, but also some Windows, TrueNAS, OS X, and Centos 
 > > machines.
 > >   > XferLOG file /var/lib/backuppc/pc/koha-dsa/XferLOG.634 created 
 > > 2022-11-16 09:47:03
 > >   > Backup prep: type = full, case = 3, inPlace = 1, doDuplicate = 1, 
 > > newBkupNum = 634, newBkupIdx = 28, lastBkupNum = , lastBkupIdx =  
 > > (FillCycle = 7, noFillCnt = 0)
 > >   > Executing /usr/share/backuppc/bin/BackupPC_backupDuplicate -m -h 
 > > koha-dsa
 > >   > Xfer PIDs are now 3702528
 > >   > Copying backup #633 to #634
 > >   > Xfer PIDs are now 3702528,3702594
 > >   > BackupPC_refCountUpdate: computing totals for host koha-dsa
 > >   > BackupPC_refCountUpdate: host koha-dsa got 0 errors (took 3 secs)
 > >   > BackupPC_refCountUpdate total errors: 0
 > >   > Xfer PIDs are now 3702528
 > >   > BackupPC_backupDuplicate: got 0 errors and 0 file open errors
 > >   > Finished BackupPC_backupDuplicate (running time: 6 sec)
 > >   > Running: /usr/libexec/backuppc-rsync/rsync_bpc --bpc-top-dir 
 > > /var/lib/backuppc --bpc-host-name koha-dsa --bpc-share-name / 
 > > --bpc-bkup-num 634 --bpc-bkup-comp 0 --bpc-bkup-prevnum -1 
 > > --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 569756 --bpc-log-level 3 
 > > --bpc-attrib-new --rsync-path=/usr/bin/nice\ /usr/bin/sudo\ /usr/bin/rsync 
 > > --numeric-ids --perms --owner --group -D --links --hard-links --times 
 > > --block-size=2048 --recursive --delete --timeout=72000 
 > > --exclude=/var/lib/elasticsearch --exclude=/var/lib/mysql --exclude=/proc 
 > > --exclude=/sys --exclude=/var/lib/postgresql 
 > > --exclude=/usr/local/ezproxy/cookies --exclude=/run --exclude=/dev 
 > > --exclude=/tmp --exclude=/var/local/palantir --exclude=/var/local/brick\* 
 > > --exclude=/var/local/arbiter\* --exclude=/var/local/bpc 
 > > --exclude=/var/lib/backuppc --exclude=/var/lib/libvirt/images koha-dsa:/ /
 > >   > full backup started for directory /
 > >   > Xfer PIDs are now 3707471
 > >   > This is the rsync child about to exec 
 > > /usr/libexec/backuppc-rsync/rsync_bpc
 > >   > Xfer PIDs are now 3707471,3707473
 > >   > xferPids 3707471,3707473
 > >   > Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 
 > > filesTotal, 0 sizeTotal, 7 filesNew, 17755669 sizeNew, 17755669 
 > > sizeNewComp, 569757 inode
 > >   > Parsing done: nFilesTotal = 0
 > >   > DoneGen: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 155253 
 > > filesTotal, 35349671498 sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 
 > > 569756 inode
 > >   > Parsing done: nFilesTotal = 155253
 > >   > Xfer PIDs are now
 > >   > full backup 634 complete, 155253 files, 35349671498 bytes, 0 xferErrs 
 > > (0 bad files, 0 bad shares, 0 other)
 > >   > BackupExpire: cntFull = 17, cntIncr = 12, firstFull = 0, firstIncr = 
 > > 12, oldestIncr = 13.5728125, oldestFull = 81.6116550925926
 > >   > Running BackupPC_refCountUpdate -h koha-dsa on koha-dsa
 > >   > Xfer PIDs are now 3711195
 > >   > BackupPC_refCountUpdate: processing host koha-dsa #634 (fsck = 0)
 > >   > BackupPC_refCountUpdate: processing host koha-dsa #634 deltaFile 
 > > /var/lib/backuppc/pc/koha-dsa/634/refCnt/poolCntDelta_0_1_0_3707471 with 
 > > 22 entries
 > >   > BackupPC_refCountUpdate: computing totals for host koha-dsa
 > >   > BackupPC_refCountUpdate: host koha-dsa got 0 errors (took 2 secs)
 > >   > BackupPC_refCountUpdate total errors: 0
 > >   > Xfer PIDs are now
 > >   > Finished BackupPC_refCountUpdate (running time: 2 sec)
 > >   > Xfer PIDs are now
 > >   > _______________________________________________
 > >   > BackupPC-users mailing list
 > >   > BackupPC-users@lists.sourceforge.net
 > >   > List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
 > >   > Wiki:    https://github.com/backuppc/backuppc/wiki
 > >   > Project: https://backuppc.github.io/backuppc/
 > >
 > >
 > > _______________________________________________
 > > BackupPC-users mailing list
 > > BackupPC-users@lists.sourceforge.net
 > > List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
 > > Wiki:    https://github.com/backuppc/backuppc/wiki
 > > Project: https://backuppc.github.io/backuppc/
 > 
 > 
 > _______________________________________________
 > BackupPC-users mailing list
 > BackupPC-users@lists.sourceforge.net
 > List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
 > Wiki:    https://github.com/backuppc/backuppc/wiki
 > Project: https://backuppc.github.io/backuppc/


_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/

Reply via email to