From: Craig B. <cr...@at...> - 2002-11-27 21:40:13
|
> In order to run the CGI interface on a different server than the > backuppc daemon is running on, does one need to install backuppc > on both machines? "CGI interface" has two parts: the apache web server, and any web browser. Obvisouly the web browser can run on any machine. I assume you are referring to where apache runs. Apache can run on a different machine than the BackupPC server. The CGI script, BackupPC_Admin, needs access to BackupPC::Lib, and also BackupPC_zipCreate and BackupPC_tarCreate for restore. You will also need to make sure perl on the apache machine has Compress::Zlib and Archive::Zip. Rather than manually copying these files it would be easiest to either: - install BackupPC on the second machine (best choice), or - mount the file system where BackupPC is installed (eg: /usr/local/BackupPC) on the other machine. Obviously BackupPC doesn't run the daemon on the second machine; just the installed files are there. BackupPC_Admin on the apache machine needs access to the entire BackupPC data directory. So you will need to mount that file system (eg: /data/BackupPC) on the apache machine. If the path to the data directory (eg: /data/BackupPC) is different on the two machines (because of where you mount the file systems) then you must install a copy of BackupPC on the apache machine (first option above), rather than mount the installed directory, since BackupPC::Lib (in lib/BackupPC/Lib.pm) includes the location of the data directory. To keep things simple you should mount the data directory so the paths on each machine are the same. Finally, you will need to edit config.pl to set $Conf{ServerHost}, $Conf{ServerPort} and $Conf{ServerMesgSecret} so that BackupPC_Admin knows how to contact the BackupPC server. Craig |
From: Craig B. <cr...@at...> - 2002-11-27 23:35:46
|
> 1. Install BackupPC on my publicly available web server. > 2. NFS mount the backuppc data dir in the exact same spot as it is on > the backup server. > > Now it would read the same conf, pc , log, etc ... directories as the > backup server....... would that alone solve this problem? Yes. > Of course I would change the port from -1 to some available TCP port > and add the secret key, then restart the daemon on the backup server. Yes. You don't have to restart the daemon: a kill -1, or "/etc/init.d/backuppc reload" (or simply waiting) works too. BackupPC is meant to detect if the TCP port config has changed (eg: port number, on/off etc) and recreate the socket if necessary. You should consider the security risk associated with the NFS mount on your "publicly available web server". If that machine is compromised then all you backup data is visible... Thanks for the feedback! I get very little time to work on it, but things are moving forward. I'm hoping to checkin initial Rsync support to CVS sometime soon... Craig |
From: David C. <dcr...@me...> - 2002-11-27 22:47:03
|
Ok, that helps a lot. To save you some time, hopefully you can answer most of these with a simple yes or no: I already installed the whole package on the backup server and have been using it for three day's, I am only doing this because my backup server is on a private network, and I would like limited access to the server via cgi interface from outside my network from time to time. It sounds like this would be easiest: 1. Install BackupPC on my publicly available web server. 2. NFS mount the backuppc data dir in the exact same spot as it is on the backup server. Now it would read the same conf, pc , log, etc ... directories as the backup server....... would that alone solve this problem? Of course I would change the port from -1 to some available TCP port and add the secret key, then restart the daemon on the backup server. I would also like to mention that the experience I have with the program so far as been exceptional. It was very easy to install and setup of the backup configurations was also simple. I use a commercial product, by Arkeia (formally Knox software), at work and was very impressed with there remote gui configuration and administration, restoration of machines. Unfortunately, when looking for solution for my home/business network, I was disappointed to find that while they do have a free ware version, it only supports two clients and must be installed on a linux server. I had difficulty finding an open source or even inexpensive commercial backup solution that had the features I was looking for, especially the remote gui with easy single file restoration options. You are to be commended on your work thus far. It also appears, from scanning your list archives, that anything that would be on my wish list is, already being worked on, the DB back end would be nice, especially with availability to store all config options so they could easily be setup from the cgi interface. Nice of you to give up your time to benefit the rest of us. Nice work. David Craig Barratt wrote: >>In order to run the CGI interface on a different server than the >>backuppc daemon is running on, does one need to install backuppc >>on both machines? >> >> > >"CGI interface" has two parts: the apache web server, and any web >browser. Obvisouly the web browser can run on any machine. I assume >you are referring to where apache runs. > >Apache can run on a different machine than the BackupPC server. >The CGI script, BackupPC_Admin, needs access to BackupPC::Lib, >and also BackupPC_zipCreate and BackupPC_tarCreate for restore. >You will also need to make sure perl on the apache machine has >Compress::Zlib and Archive::Zip. > >Rather than manually copying these files it would be easiest >to either: > > - install BackupPC on the second machine (best choice), or > > - mount the file system where BackupPC is installed (eg: /usr/local/BackupPC) > on the other machine. > >Obviously BackupPC doesn't run the daemon on the second machine; just >the installed files are there. > >BackupPC_Admin on the apache machine needs access to the entire >BackupPC data directory. So you will need to mount that file >system (eg: /data/BackupPC) on the apache machine. > >If the path to the data directory (eg: /data/BackupPC) is different >on the two machines (because of where you mount the file systems) >then you must install a copy of BackupPC on the apache machine (first >option above), rather than mount the installed directory, since >BackupPC::Lib (in lib/BackupPC/Lib.pm) includes the location of >the data directory. To keep things simple you should mount the >data directory so the paths on each machine are the same. > >Finally, you will need to edit config.pl to set $Conf{ServerHost}, >$Conf{ServerPort} and $Conf{ServerMesgSecret} so that BackupPC_Admin >knows how to contact the BackupPC server. > >Craig > > > |
From: Toby J. <to...@to...> - 2002-11-27 23:23:20
|
Craig, just a thought, you may want to include a few options to the install program: "everything", "cgi only", and "server only". Lib.pm and the other helper files would be installed regardless, but only what's necessary for one or the other in a split setup for the last two. |