Re: [BackupPC-users] Backing up the server computer

On Sun, 16 Jul 2017 10:12:39 -0400 Bob Katz wrote: > I appreciate that. Well, if I have to do a bare metal restore I would > use a clone, it's safer, if it's recent. I don't see where it could be safer; the worse you can have are eventual dangling files if the install image

Re: [BackupPC-users] Backing up the server computer

On Sat, 2017-07-15 at 01:16 +0200, B wrote: > On Fri, 14 Jul 2017 18:56:19 -0400 > Paul Fox wrote: > > Just a precision for B.Katz: I also have a script that creates an > _INSTALLED_PKGS.txt file from the usual command (debian), > launched as a pre-backup command

Re: [BackupPC-users] Backing up the server computer

Dear Kenneth Porter On 15.07.2017 10:23, Kenneth Porter wrote: > > Does --one-file-system work with rsyncd (daemonized rsync)? No, at least there is no such parameter documented for rsyncd.conf. You may be able to provide a --one-file-system parameter upon startup, though (untested). With kind

Re: [BackupPC-users] Backing up the server computer

On Sat, 15 Jul 2017 16:20:32 +1000 Adam Goryachev wrote: > Actually, I think you will find that /proc, /dev, /sys, etc are > actually different filesystems, and so will automatically be excluded > by --one-file-system. On 2nd thought, that looks logical from

Re: [BackupPC-users] Backing up the server computer

Adam Goryachev wrote: > > > On 15/7/17 13:00, Paul Fox wrote: > > i didn't say i don't also have some excludes. i exclude /proc and > > /sys. /dev is a separate filesystem. /tmp, believe it or not, i do > > back up, to help with the morning-after regret of having lost a file i > >

Re: [BackupPC-users] Backing up the server computer

Dear Bob Katz On 15.07.2017 00:22, Bob Katz wrote: > > I have root as the user for backuppc for all my other hosts and it > works. And it's also currently set up as root for backing up the server. > I did try "backuppc" as the user before and it failed, maybe for > different reasons. Anyway, I'm

Re: [BackupPC-users] Backing up the server computer

On 7/14/2017 7:45 AM, Bob Katz wrote: But is there a point to running sudo rsync if the object is to use systemctl to run the daemon? Is that for a test or permanent? Yes, I'm confused :-) And systemctl has already been initiated. According to the man page, --foreground should be

Re: [BackupPC-users] Backing up the server computer

On 7/14/2017 11:20 PM, Adam Goryachev wrote: Actually, I think you will find that /proc, /dev, /sys, etc are actually different filesystems, and so will automatically be excluded by --one-file-system. Does --one-file-system work with rsyncd (daemonized rsync)? I thought it only applied when

Re: [BackupPC-users] Backing up the server computer

On 15/7/17 13:00, Paul Fox wrote: B wrote: > On Fri, 14 Jul 2017 18:56:19 -0400 > Paul Fox wrote: > > > i confess i haven't been following this thread in all its gory detail, > > The BackupPC god absolves you (although, it is the BPC v.3x god, so >

Re: [BackupPC-users] Backing up the server computer

B wrote: > On Fri, 14 Jul 2017 18:56:19 -0400 > Paul Fox wrote: > > > i confess i haven't been following this thread in all its gory detail, > > The BackupPC god absolves you (although, it is the BPC v.3x god, so > you'll need to upgrade the confessionnal

Re: [BackupPC-users] Backing up the server computer

On Fri, 14 Jul 2017 18:56:19 -0400 Paul Fox wrote: > i confess i haven't been following this thread in all its gory detail, The BackupPC god absolves you (although, it is the BPC v.3x god, so you'll need to upgrade the confessionnal if you want to also be absolved by

Re: [BackupPC-users] Backing up the server computer

B wrote: > On Fri, 14 Jul 2017 18:22:54 -0400 > Bob Katz wrote: > > > Oh boy I get it!!! I can't believe how stupid I was about that. > > Me too ;-p) > > > Well, doesn't this mean I have to establish a whole bunch of modules > > with a different path for

Re: [BackupPC-users] Backing up the server computer

On Fri, 14 Jul 2017 18:22:54 -0400 Bob Katz wrote: > Oh boy I get it!!! I can't believe how stupid I was about that. Me too ;-p) > Well, doesn't this mean I have to establish a whole bunch of modules > with a different path for each module, in order to back up

Re: [BackupPC-users] Backing up the server computer

Dear Stefan, you are so kind! This helps a lot. Yes, I'm plodding my way through. You wrote: [Backup-Data-Folder] ## Next, set the path you want backed up. Be sure to use a trailing slash path= / Please don't do that: o a Linux system has virtual file systems

Re: [BackupPC-users] Backing up the server computer

Hi Bob On 14.07.2017 21:32, Bob Katz wrote: ... snip ... > > > 2017/07/14 15:06:17 [3292] connect from localhost (::1) > 2017/07/14 15:06:17 [3292] rsync denied on module Backup-Data-Folder > from localhost (::1) > ... snip ... > >

Re: [BackupPC-users] Backing up the server computer

Still not much progress but I've simplified things. In Fedora, rsync daemon is supposed to be run by systemctl. But I am pretty sure my attempt to create a service for rsync as a daemon has failed somewhere. So I'm debuggin by using the simple command line: sudo rsync ---daemon By the way, rsync

Re: [BackupPC-users] Backing up the server computer

Thanks. Well, first I have to ensure that inetd and no other mechanism I foolishly initiated in my efforts is running. I'm working on that now. But is there a point to running sudo rsync if the object is to use systemctl to run the daemon? Is that for a test or permanent? Yes, I'm

Re: [BackupPC-users] Backing up the server computer

--On Thursday, July 13, 2017 12:03 PM -0400 Bob Katz wrote: There must be a foolproof way of displaying running daemons, finding out the PID and killing it. The PS command that everyone is fond of does not show the daemon is runnning, I don't believe. If ps doesn't see

Re: [BackupPC-users] Backing up the server computer

--On Thursday, July 13, 2017 4:37 PM + Michael Stowe wrote: At this point, I'd recommend sudo rsync --daemon --foreground --verbose So you can actually tell what's happening. According to the man page, --foreground should be --no-detach. That keeps the

Re: [BackupPC-users] Backing up the server computer

On Thu, Jul 13, 2017 at 2:01 PM, Bob Katz wrote: > > > It's a mess and I wish I could back out of it and start from scratch. > Also in the process I tried to create a xinet.d method of initiating > rsync and I fear a conflict. All I did was install xinetd and create > some

Re: [BackupPC-users] Backing up the server computer

This is for Fedora 26. Backuppc is working fine backing up all sorts of client computers But conquering backing up itself seems to be very complex. I set up a service rsyncd using instructions at https://lists.fedorapro ject.org/pipermail/users/2011-November/408706.html This seems to work,

Re: [BackupPC-users] Backing up the server computer

Guys: Since it appears the correct way to launch rsync on fedora is: systemctl start rsyncd How would I do this in verbose mode? I'm hoping the log file will do the job anyway. I think I'll restart the computer to ensure rsync is NOT running and start debugging again. Crossing fingers

Re: [BackupPC-users] Backing up the server computer

On 2017-07-13 10:03, Bob Katz wrote: On 7/12/17 11:08 AM, Les Mikesell wrote: I noticed in your rsyncd.conf that you are running it as user backuppc. That probably will prevent it from accessing ports below 1024 unless it starts as root. Also, you won't be able to back up all of the files

Re: [BackupPC-users] Backing up the server computer

On 7/12/17 11:08 AM, Les Mikesell wrote: I noticed in your rsyncd.conf that you are running it as user backuppc. That probably will prevent it from accessing ports below 1024 unless it starts as root. Also, you won't be able to back up all of the files on the machine. Thanks, Les. You can

Re: [BackupPC-users] Backing up the server computer

--On Wednesday, July 12, 2017 10:57 AM -0400 Bob Katz wrote: I manually run sudo rsync --daemon and there is no "response" in terminal. I take it to mean the daemon launched with no problem. On Fedora and CentOS 7, you should be starting the daemon with systemd, like

Re: [BackupPC-users] Backing up the server computer

On Wed, Jul 12, 2017 at 8:57 AM, Bob Katz wrote: > Hi, guys. To review: > > I'm Trying to back up the server computer using method rsyncd. The > backup fails. > > I'm on Fedora 26. Yes, I know it's in beta. > > Maybe this rsyncd log entry will help: > > 2017/07/12 05:08:52

Re: [BackupPC-users] Backing up the server computer

On 2017-07-12 08:57, Bob Katz wrote: Hi, guys. To review: I'm Trying to back up the server computer using method rsyncd. The backup fails. I'm on Fedora 26. Yes, I know it's in beta. Maybe this rsyncd log entry will help: 2017/07/12 05:08:52 [13623] rsyncd version 3.1.2 starting, listening

Re: [BackupPC-users] Backing up the server computer

Hi, guys. To review: I'm Trying to back up the server computer using method rsyncd. The backup fails. I'm on Fedora 26. Yes, I know it's in beta. Maybe this rsyncd log entry will help: 2017/07/12 05:08:52 [13623] rsyncd version 3.1.2 starting, listening on port 873 2017/07/12 05:08:52 [13623]

Re: [BackupPC-users] Backing up the server computer

It's still a struggle, and I thank everyone who has tried to help. Here's what I've done so far. I've succeeded in getting this command to work: [bobkatz@localhost etc]$ rsync localhost.localdomain:: Backup-Data-Folder "Backup-Data-Folder" is the rsync task (module) named in rsyncd.conf

Re: [BackupPC-users] Backing up the server computer

Am 05.07.2017 um 17:26 schrieb Bob Katz: > Dear Les and group: > > > So it seems the daemon is not running on the port? This ps command > seems to say the daemon is running: > > > [bobkatz@localhost Documents]$ ps x | grep rsync > 17690 pts/1S+ 0:00 grep --color=auto rsync The output

Re: [BackupPC-users] Backing up the server computer

On 06/07/17 05:46, Kenneth Porter wrote: --On Wednesday, July 05, 2017 12:26 PM -0400 Bob Katz wrote: rsync: failed to connect to localhost.localdomain (::1): Connection refused (111) Is rsyncd listening on the IPv6 interface? Or only the IPv4 interface? The error

Re: [BackupPC-users] Backing up the server computer

--On Wednesday, July 05, 2017 12:26 PM -0400 Bob Katz wrote: rsync: failed to connect to localhost.localdomain (::1): Connection refused (111) Is rsyncd listening on the IPv6 interface? Or only the IPv4 interface? The error message says that rsync is attempting to

Re: [BackupPC-users] Backing up the server computer

On Wed, Jul 5, 2017 at 10:26 AM, Bob Katz wrote: > Dear Les and group: > > The rsync command you gave me for testing makes rsync think it's > pushing a file, not connecting with the remote server. > > Here's a different test command I worked out, just to see if rsync can >

Re: [BackupPC-users] Backing up the server computer

Dear Les and group: The rsync command you gave me for testing makes rsync think it's pushing a file, not connecting with the remote server. Here's a different test command I worked out, just to see if rsync can communicate with the daemon on its own computer. There is an rsync task mentioned in

Re: [BackupPC-users] Backing up the server computer

On Mon, Jul 3, 2017 at 7:58 PM, Bob Katz wrote: > Thanks, Ken. localhost.localdomain is definitely the 127... address we > would expect > > ps command tells me that the daemon is running > > I haven't run lsof but I do know the daemon is running > > So I'm still

Re: [BackupPC-users] Backing up the server computer

Thanks, Ken. localhost.localdomain is definitely the 127... address we would expect ps command tells me that the daemon is running I haven't run lsof but I do know the daemon is running So I'm still stuck :-( Best, Bob On 7/3/17 5:47 PM, Kenneth Porter wrote: On 7/3/2017

Re: [BackupPC-users] Backing up the server computer

On 7/3/2017 1:16 PM, Bob Katz wrote: But I get this error. I suppose I'm doing something fundamentally not permitted (can't use rsync daemon to connect to the same computer???): rsync_bpc: failed to connect to localhost.localdomain (::1): Connection refused (111) rsync_bpc: failed to connect to

[BackupPC-users] Backing up the server computer

Hi guys. All of my hosts are connected by rsyncd so I decided to try backing up the server computer via rsyncd. It's "localhost.localdomain" of course. I am not using any secrets file, I've always just connected as root. Secrets is not mentioned in rsyncd.conf, and there are no keys used: But I