On 09/13/2015 03:48 PM, Timothy Murphy wrote:> Timothy Murphy wrote: > >> I thought I'd write a 1-page note to myself of the steps I took, >> in preparation for CentOS-8... >> I have a couple of questions that this raises. >> >> 1. Why exactly does backuppc want to ssh to root? >> Is this just a way of running BackupPC as root? >> >> 2. The graphical interface seems to be treated as an extra, >> but what other way is there of accessing BackupPC? >> Is there a CLI approach? >> If so, where is the list of transfer requests kept? > Another small query. > I see that BackupPC starts 6 copies of httpd running, > but so far only 2 have ever been used. > Can this number (6) be changed? >1. It's just the default, it can easily be configured to start rsync through sudo, you need root privileges to backup all files. 2. You can do all operations through CLI, all of it is mentioned in the documentation. http://backuppc.sourceforge.net/faq/BackupPC.html#Step-7:-Talking-to-BackupPC 3. As mentioned earlier, this is just the default apache config. And can be altered through httpd.conf (though I wouldn't mess too much with it, the defaults are normally fine). -kp
kpolberg at olberg.name wrote:>>> 2. The graphical interface seems to be treated as an extra, >>> but what other way is there of accessing BackupPC? >>> Is there a CLI approach? >>> If so, where is the list of transfer requests kept?> 2. You can do all operations through CLI, all of it is mentioned in the > documentation. > http://backuppc.sourceforge.net/faq/BackupPC.html#Step-7:-Talking-to-BackupPCThank you for your response. However, I don't believe this short section gives sufficient information to configure and run BackupPC. Basically, it just gives a way of finding out what is happening while BackupPC is running. (Also it finishes by advising you to use the GUI instead.) For example, what command would you give to tell BackupPC that you want to back up /var/www (to choose a directory at random)?> 3. As mentioned earlier, this is just the default apache config. And can > be altered through httpd.conf (though I wouldn't mess too much with it, > the defaults are normally fine).I don't think that is true. The simplest way to configure BackupPC is to run it with user backuppc, by changing "User apache" to "User backuppc" in /etc/httpd/conf/httpd.conf . -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin
On 09/15/2015 10:58 AM, Timothy Murphy wrote:> kpolberg at olberg.name wrote: > >>>> 2. The graphical interface seems to be treated as an extra, >>>> but what other way is there of accessing BackupPC? >>>> Is there a CLI approach? >>>> If so, where is the list of transfer requests kept? > >> 2. You can do all operations through CLI, all of it is mentioned in the >> documentation. >> http://backuppc.sourceforge.net/faq/BackupPC.html#Step-7:-Talking-to-BackupPC > > Thank you for your response. > However, I don't believe this short section gives sufficient information > to configure and run BackupPC. > Basically, it just gives a way of finding out what is happening > while BackupPC is running. > (Also it finishes by advising you to use the GUI instead.) > > For example, what command would you give to tell BackupPC > that you want to back up /var/www (to choose a directory at random)?That goes in the config file (typically the per-PC one for this kind of setting, since you won't back up the same dirs on all clients). http://backuppc.sourceforge.net/faq/BackupPC.html#Configuration-File The options are described in the following sections, that particular setting is described in the well named section: http://backuppc.sourceforge.net/faq/BackupPC.html#What-to-backup-and-when-to-do-it Really, the backuppc docs are pretty good.