Anthony Chavez wrote at about 02:08:39 -0700 on Tuesday, November 2, 2021:
 > On 10/19/21 7:06 PM, Anthony Chavez wrote:
 > > 
 > > On 10/9/21 3:02 PM, Anthony Chavez wrote:
 > >> Hi all,
 > >>
 > >> So I have had to make a slight change to my BackupPC setup and while I 
 > >> am able to access new backups in the web interface, I am now unable to 
 > >> access my older backups.
 > >>
 > >> My old setup was under a FreeNAS Jail, using the FreeBSD pkg of 
 > >> BackupPC with a nullfs mount from the jail to a ZFS dataset housing 
 > >> the backups themselves. It worked great for months.
 > >>
 > >> When upgrading from FreeNAS 11 to TrueNAS 12, my jail refused to 
 > >> upgrade so the option was to either create a new jail or install Linux 
 > >> in a VM and mount the backups directory over NFSv3. I chose the latter 
 > >> (ArchLinux) and because Docker is becoming a thing in my LAN, 
 > >> adferrand/backuppc.
 > >>
 > >> The error message for older backups I am seeing in the web interface 
 > >> is "Error: Directory /data/backuppc/pc/$host/$baknum is empty".
 > >> When trying to access an older backup, BackupPC_ls comes back with, 
 > >> for example: "bpc_attrib_dirRead: can't open 
 > >> /data/backuppc/cpool/72/ca/72ca0cc1bf7a179f8c3cdabc187e3887".

Have you tried BackupPC_zcat on the above pool file?

 > >>
 > >> Permissions check out (uid 126/backuppc, gid 126/backuppc, umask 027) 
 > >> so the only thing I can think of is that I need to re-index or 
 > >> re-build the pool somehow, but I am not familiar enough with BackupPC 
 > >> command line utilities to know what to do at this point.
 > >>
 > >> Any help would be much appreciated.
 > > 
 > > Could anyone help with this please? It's making no sense to me:
 > > 
 > > $ ls -ahln /data/backuppc/pc/$host/$baknum
 > > total 65K
 > > drwxr-x---    8 126      126           10 Aug 29 16:22 .
 > > drwxr-x---  110 126      126          233 Oct 19 15:12 ..
 > > -rwxr-x---    1 126      126            0 Aug 29 16:22 
 > > attrib_5e6a2266a222d07587f687f9df5ac097
 > > -rwxr-x---    1 126      126          695 Aug 29 16:00 backupInfo
 > > drwxr-x---    3 126      126            4 Aug 29 16:01 f%2fetc
 > > drwxr-x---    3 126      126            4 Aug 29 16:14 f%2fhome
 > > drwxr-x---    3 126      126            3 Aug 29 16:18 f%2fsrv
 > > drwxr-x---    4 126      126            4 Aug 29 16:20 f%2fvar
 > > drwxr-x---    2 126      126            3 Aug 29 16:22 f%2fvar%2flib
 > > drwxr-x---    2 126      126           95 Oct  7 14:13 refCnt

What is in the refCnt directory (and subdirectory)?
What is in the f-mangled directories?

What is in the log files under:
- TopDir/log
- TopDir/pc/$host

Are there errors? And if so what are they?

> > $ /usr/local/BackupPC/bin/BackupPC_ls -h $host -n $baknum -s /etc /
 > > /:
 > > bpc_attrib_dirRead: can't open 
 > > /data/backuppc/cpool/72/ca/72ca0cc1bf7a179f8c3cdabc187e3887
 > > bpc_attrib_dirRead: can't open 
 > > /data/backuppc/cpool/68/40/6940aeccff660743da3041191216d260
 >
Again try BackupPC_zcat..
You may also want to try backuppcfs.pl which mounts your backups as a fuse
file system and allows you to browse files to see what if any files
are actually backed up.

 > Is there nobody that can help me with this? Are my backups lost?
 > 
You really need to give us some more troubleshooting info if we are to
have any chance of helping you!

 > I am open to paying for one-on-one assistance with this. I would very 
 > much like to salvage this situation, if at all possible.
 > 
 > 
 > _______________________________________________
 > 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