Re: [BackupPC-users] Backup problems with /home directory
On Mon, Apr 15, 2024 at 9:10 PM John Cusick wrote: > > I've searched multiple sites and everything I've tried just isn't working. > > I'm using rsyncd > > The systems I'm testing are both Fedora 39, one server and one laptop. > > I'm using the BackupPC on the server: > BackupPC-XS-0.62-13.fc39.x86_64 > BackupPC-4.4.0-10.fc39.x86_64 > > I named the backup user "backuppc" which has passwordless ssh login on both > the server and laptop client. > > the sudoers file has the following entry: ... Are you sure you understand the difference between the rsync and rsyncd methods?Rsyncd expects a standalone rsync daemon listening on the client and backs up 'shares' in the rsyncd.conf setup. The rsync method connects over ssh to the client and either needs to connect as root on the client or have a more convoluted sudo configuration to have permission to read everything. -- Les Mikesell lesmikes...@gmail.com ___ 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] Backup problems with /home directory
I've searched multiple sites and everything I've tried just isn't working. I'm using rsyncd The systems I'm testing are both Fedora 39, one server and one laptop. I'm using the BackupPC on the server: BackupPC-XS-0.62-13.fc39.x86_64 BackupPC-4.4.0-10.fc39.x86_64 I named the backup user "backuppc" which has passwordless ssh login on both the server and laptop client. the sudoers file has the following entry: # setup for backuppc to run rsync backuppc ALL= NOPASSWD:/usr/bin/rsync The rsyncd.conf and rsyncd.secrets files are setup correctly as far as I can tell since both the "/usr/local" and "/etc" directories are backed up with no problems (that I worry about :) I'm backing up 4 directories, /etc, /usr/local, /home/john, and /home/backuppc No matter what I've tried so far, even though the "/etc" and "/user/local" directories are successfully backed up, everytime backuppc tries to backup either user directory in the /home directory I get the following error: rsync: [sender] change_dir "/" (in backuppc) failed: Permission denied (13) On the client system I can sudo to the backuppc user and, as a test I ran "sudo rsync /home/john/testfile.txt /home/backuppc/" and it succeeds with no errors. The file was copied to the backuppc home directory. But it always fails when being run from the BackupPC server with the "Permission denied (13)" error. I'm stumped and any help would be appreciated. Regards, John C. ___ 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/
Re: [BackupPC-users] Problems cropping up with backups
On Mon, Apr 15, 2024 at 8:30 AM G.W. Haywood wrote: > Hi there, > > On Mon, 15 Apr 2024, Brad Alexander wrote: > > > I am having a bit of a problem with my backuppc install that just cropped > > up recently. > > > > Most of my network runs the latest version of FreeBSD 14.0-RELEASE, and > it > > has been running on FreeBSD for years. > > Noted. [1] > > > So my backuppc server is in a FreeBSD jail on dedicated jails server > > (i-5 7500, 32 GB RAM), with backing storage that is NFS mounted from > > from my TrueNAS host. > > Noted. [2] > > > I am backing up a total of 8 jails, 3 hardware servers, my desktop, my > > laptop, all running FreeBSD 14.0. I am also backing up my wife's desktop, > > which is running linux. I'm using rsync. Everything has been backing up > > properly, then one day about 2 weeks ago, backups on my laptop quit > > working. I started receiving the error message > > > > backup failed (rsync error: error in rsync protocol data stream...) > > > > R bpc_read: read past EOF; readSize = 1024, posn = 356352, fileSize = 0, > bufferSize = 8388608 > > R bpc_read: read past EOF; readSize = 17408, posn = 0, fileSize = 0, > bufferSize = 8388608 > > ... > > [ skipped some lines ] > > ... > > R bpc_poolWrite_updateMatches: can't open candidate file > > ... > > Since it is only occurring on these two hosts, but none of the other 14, > > can someone explain what is going on here? > > Are you running the server from UPS? Because to me that looks like > filesystem damage. If I'm right it could be a lost write at a power > failure or something, or maybe it could be that a storage medium is on > the way out. I'd want to know ASAP. To start with, can you run fsck > or something like that on the TrueNAS host? > > [1] I note that this has been working for years, but all the same I > feel the need to say that in my experience NFS has been truly awful > for this kind of thing. Performance, reliability, everything. > > [2] NAS hosts have a habit of getting compromised, however from all > you've said I have to assume that you're on top of that. But it might > be worth considering the possibility. I wouldn't touch them with a > ten metre pole. Putting TrueNAS and NFS in the same system seem to me > like asking for it but I guess I have to keep coming back to [1]. :/ > > Can't really fault you for putting BackupPC in a jail, but I'd be more > concerned about things attacking BackupPC than I would that the backup > server might attack the rest of the network. My personal take on it > is to run separate hardware for the backup server. > Hi G.W., The NAS (as well as the two jail servers) are on UPS. And TrueNAS generally does not lose writes, as the underlying filesystem is ZFS, which is copy-on-write, plus checksums every block on read and write. The last scrub of the zpool (checking checksums against saved ones, was completed Apr 7: scan: scrub repaired 0B in 16:34:41 with 0 errors on Sun Apr 7 16:34:43 2024 However, I am running another one currently, just to be sure. Also came back with zero errors: scan: scrub repaired 0B in 09:24:41 with 0 errors on Mon Apr 15 20:34:02 2024 As for the other notes: [1] My previous configuration was I had the jail running on the NAS and the dataset mounted via nullfs mount to the jail. The strange thing is that it is only with these two particular hosts. All of the other systems being backed up are working fine, both jails and hardware. And initially, the desktop was backing up, only the laptop stopped working. Once I disabled the laptop, the desktop stopped. Now I have both disabled, and everything else is still working. [2] The NAS is only reachable from the internal network. I do watch network security closely. Having said that, I don't understand what you meant about putting TrueNAS and NFS on the same system. TrueNAS is a FreeBSD-based appliance for network attached storage, and where else would you run NFS from, if the data lives on the NAS box... And the reason that I have backuppc in a jail is that TrueNAS is an appliance, and thus installing software (like backuppc) on the TrueNAS OS is contraindicated. In addition, I have seen over the years, dating back to 2005, of people successfully running backuppc over NFS, plus my ZFS pool says things are okay, so I'm at a loss... Ceers, --b ___ 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/
Re: [BackupPC-users] Problems cropping up with backups
Hi there, On Mon, 15 Apr 2024, Brad Alexander wrote: I am having a bit of a problem with my backuppc install that just cropped up recently. Most of my network runs the latest version of FreeBSD 14.0-RELEASE, and it has been running on FreeBSD for years. Noted. [1] So my backuppc server is in a FreeBSD jail on dedicated jails server (i-5 7500, 32 GB RAM), with backing storage that is NFS mounted from from my TrueNAS host. Noted. [2] I am backing up a total of 8 jails, 3 hardware servers, my desktop, my laptop, all running FreeBSD 14.0. I am also backing up my wife's desktop, which is running linux. I'm using rsync. Everything has been backing up properly, then one day about 2 weeks ago, backups on my laptop quit working. I started receiving the error message backup failed (rsync error: error in rsync protocol data stream...) R bpc_read: read past EOF; readSize = 1024, posn = 356352, fileSize = 0, bufferSize = 8388608 R bpc_read: read past EOF; readSize = 17408, posn = 0, fileSize = 0, bufferSize = 8388608 ... [ skipped some lines ] ... R bpc_poolWrite_updateMatches: can't open candidate file ... Since it is only occurring on these two hosts, but none of the other 14, can someone explain what is going on here? Are you running the server from UPS? Because to me that looks like filesystem damage. If I'm right it could be a lost write at a power failure or something, or maybe it could be that a storage medium is on the way out. I'd want to know ASAP. To start with, can you run fsck or something like that on the TrueNAS host? [1] I note that this has been working for years, but all the same I feel the need to say that in my experience NFS has been truly awful for this kind of thing. Performance, reliability, everything. [2] NAS hosts have a habit of getting compromised, however from all you've said I have to assume that you're on top of that. But it might be worth considering the possibility. I wouldn't touch them with a ten metre pole. Putting TrueNAS and NFS in the same system seem to me like asking for it but I guess I have to keep coming back to [1]. :/ Can't really fault you for putting BackupPC in a jail, but I'd be more concerned about things attacking BackupPC than I would that the backup server might attack the rest of the network. My personal take on it is to run separate hardware for the backup server. -- 73, Ged. ___ 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/
