Koozali.org: home of the SME Server

Backuppc contrib

duncan

Backuppc contrib
« on: September 30, 2004, 03:23:47 PM »
Backuppc is described as a "high-performance, enterprise-grade system for backing up Linux and WinXX PCs and laptops to a server's disk. BackupPC is highly configurable and easy to install and maintain." - basically it is a superb network to disk backup solution using smb, rsync or tar.

A SME built rpm can be got from  here. The RsyncP rpm is required if you want to use rsync as a backup method.
The package installs the configs, backup locations and web stuff in /opt/backuppc. Prior to the rpm installation - you need to add a user called "backuppc".

To enable do;
/sbin/e-smith/db configuration setprop backuppc  status enabled
/sbin/e-smith/signal-event console-save
reboot

You can browse to http://server-address/backuppc/cgi-bin/BackupPC_Admin.cgi to access the web front end. Username admin has access to everything. I have set this up to use pwauth - so you can use any sme username/password combo to limit access (In the hosts file). On gateway machines - this page will be accessible from the internet albeit behind a username/password combo. You should edit the httpd custom-template and limit access only to your internal networks.

This backup solution is not for the faint hearted. It is highly configurable and very flexible. You will need to get your hands dirty. It is well worth the effort though.

jcoleman

Backuppc contrib
« Reply #1 on: September 30, 2004, 06:30:17 PM »
Bravo Duncan!

Backuppc is a great tool and making it work on the SME Server is an excellent idea.

I will install on a test machine later today and get back with you (and all) with results.

Thanks for the hard work you've been putting in to enhance the SME Server.

-jeff

mbachmann

Backuppc contrib
« Reply #2 on: October 01, 2004, 09:30:58 AM »
Superb. Have not tested yet but i will.

Duncan, the smoke free sig has gone away for what reason?

duncan

Backuppc contrib
« Reply #3 on: October 01, 2004, 11:01:15 AM »
Quote from: "mbachmann"
Superb. Have not tested yet but i will.

Duncan, the smoke free sig has gone away for what reason?


Not sure - Its still in my account. I am at about 6 months now. ;-)

mbachmann

Backuppc contrib
« Reply #4 on: October 01, 2004, 11:16:30 AM »
Aehm, you write one have to create an (user) account called "backuppc" and if so, what's the users first and last name? Like b.ackuppc? Or doesn't it matter?

duncan

Backuppc contrib
« Reply #5 on: October 01, 2004, 11:28:06 AM »
It doesnt matter - Something descriptive perhaps.

Offline percheron

  • *
  • 17
  • +0/-0
Backuppc contrib
« Reply #6 on: October 01, 2004, 01:09:51 PM »
Duncan,
Thanks for doing this work. I would like to try this contrib. After installing on an SME 6.01 server on my local network I am unable to access the cgi script. I can't get past the "You don't have permission to access /backuppc/cgi-bin/BackupPC_Admin.cgi on this server" message when trying to access the script with http://server-address/backuppc/cgi-bin/BackupPC_Admin.cgi.

Looking in the /opt/backuppc/cgi-bin directory I see this file:

-r-sr-xr--    1 backuppc shared       3925 Sep 30 02:55 BackupPC_Admin.cgi

I have a user called backuppc and have set a password. I also followed the rest of your instructions in your post. Any suggestions?

Thanks,
jim

duncan

Backuppc contrib
« Reply #7 on: October 01, 2004, 02:01:25 PM »
Hi Jim, not sure what the problem might be. The cgi-bin permissions are root.root which might be causing a problem.

I have just done a fresh install with no problems on another machine. Perhaps checkout the /var/log/httpd files to see whats going on.

Offline percheron

  • *
  • 17
  • +0/-0
Backuppc contrib
« Reply #8 on: October 01, 2004, 02:32:58 PM »
Duncan,
Thansk for the quick reply. I looked at the error logs but did not see anything peculiar. Here is some more info: on the first install I got the message the backuppc user did not exist and the install was using root. I removed both rpm's and reinstalled them after creating the backuppc user. When I could not get access to the cgi script, I removed the rpm's again, deleted the /opt/backuppc directory and re-installed the rpm's again. I have also used these commands in the process as specified in your post:

/sbin/e-smith/db configuration setprop backuppc status enabled
/sbin/e-smith/signal-event console-save
reboot

I have not done anything related to external access - I am strictly working on the LAN at this point.

Do you think my failure to have created the backuppc user on the first install is causing this problem? If so how can I correct it? What permissions should be set on the backuppc directory and cgi script?

Thanks again,
jim

duncan

Backuppc contrib
« Reply #9 on: October 02, 2004, 02:42:01 AM »
Installing the package without adding the user first does cause problems. However - a simple

rpm -e smeserver-backuppc
add the user
reinstall

Fixes that. If there was an easy way to create the user during the rpm installation - I would add that facility.

You should get challenged with a username/password dialogue when accessing the page. If you log in using your sme admin username/password - you will have access to all machines. If you log in as one of your sme users - you will have access to the machines you have given them access to in the /opt/backuppc/files/conf/hosts file. If you log in as a sme user not set up in the above file - they will see the page - but have access to nothing.

If you dont get the challenge dialogue (some sort of page error) then there is a problem.

Offline percheron

  • *
  • 17
  • +0/-0
Backuppc contrib
« Reply #10 on: October 02, 2004, 02:48:58 AM »
Duncan,
I do not get the user name, password challenge. I simply get the permission denied message. I have removed and re-installed the rpms four times. I did a console-save and reboot in between each install and made sure to delete the /opt/backuppc direcotry on the last two attempts. I only have one test server, the rest are production so I hesitate to try it. The server is fairly stock, just a couple of rpms. It operates in server/gateway mode. I get the same result with Mozilla and IE. I'm not sure what else to try.

Thanks for your reply.
jim

duncan

Backuppc contrib
« Reply #11 on: October 02, 2004, 03:11:51 AM »
I will set up one of my test machines as server/gateway and see how that goes.

Its a long weekend here - and I will be avoiding technology for the most part  :-)

Offline percheron

  • *
  • 17
  • +0/-0
Backuppc contrib
« Reply #12 on: October 02, 2004, 04:21:28 AM »
Duncan,
I will test the install again when you either post a revision or suggest something for me to try. If anyone else has an idea, please chime in.
Thanks again and enjoy your weekend,
jim

monkey

Backuppc contrib
« Reply #13 on: October 02, 2004, 05:28:55 PM »
Duncan,

This looks neat. Thanks for your effort on this!

I will be testing this one out, as I have a number of development PCs on my network with a very fragmented backup system. Backing up to my SME box makes sense.

I will report back my findings for you

Cheers!

Mike

duncan

Backuppc contrib
« Reply #14 on: October 04, 2004, 04:03:41 AM »
I have added a new backuppc version to the contribs directory.

Added -

rsyncd server run from xinetd (will only accept connections from 127.0.0.1 and any defined local networks - password protected, which should be changed)
The backuppc page will now list a 127.0.0.1 machine. This will backup /etc and parts of /home. This should also serve as an example to get you started with networked machines. Edit /etc/rsyncd.conf for additions.

For backing up Win machines - I would suggest using cwrsync from here.

I have only tested this a clean install. I have no idea what a rpm upgrade from the previous version will do.
If you want to add an additional drive for the backups then add some thing like this to /etc/fstab

Code: [Select]
/dev/hdxx        /opt/backuppc/files    ext3    defaults        1 2

mbachmann

Backuppc contrib
« Reply #15 on: October 04, 2004, 10:56:53 AM »
Uh, uh, the config files of this are really not for  faint-hearted chickens from Krautland.

mbachmann

Backuppc contrib
« Reply #16 on: October 07, 2004, 09:39:56 AM »
Code: [Select]
rpm -e smeserver-backuppc the (2.1.0-1 version), installed smeserver-backuppc-2.1.0-2, got:
              ##################################################
Oct  7 08:59:19 horus e-smith[22600]: backuppc: unrecognized service
Oct  7 08:59:19 horus e-smith[22600]: error: execution of %pre scriptlet from smeserver-backuppc-2.1.0-2 failed, exit status 1
Oct  7 08:59:19 horus e-smith[22600]: error:   install: %pre scriptlet failed (2), skipping smeserver-backuppc-2.1.0-2
...
##################################################

Removed, readded user backuppc, retried with 2.1.0-2, succesful this time, issued
Code: [Select]
/sbin/e-smith/db configuration setprop backuppc status enabled
/sbin/e-smith/signal-event console-save
reboot


Now onto the config-files.

It would be totally great if one can call backuppc from server-manager.

The default 127.0.0.1 backup setting worked just straight away without recursion.

Added remote SME with static IP to the hosts file, noticed the you have to reload the server configuration and got
Reply from server was: ok but then
backup failed (tree connect failed: NT_STATUS_BAD_NETWORK_NAME)
; it seems to think it is an Windows machine. Noticed that there is no config file for remote machine, copied config file from 127.0.0.1. Tried again.

Got fatal error during xfer (inet connect: Connection refused)
2004-10-07 10:05:20 Backup aborted (inet connect: Connection refused)


Then set the
$Conf{RsyncdAuthRequired} = 0;
no go, started to hate this.
Tried
$Conf{RsyncdUserName} = 'goodadminuser';
$Conf{RsyncdPasswd} = 'goodadminpw';

Now it's running.

/sbin/e-smith/user configuration mbachmann delprop faint hearted chicken status

duncan

Backuppc contrib
« Reply #17 on: October 07, 2004, 11:16:44 AM »
Hi,

The rpm might be a little flaky. There are some issues with shutting down the service etc. I am working on it for the next release.

I have edited this bit out - basically going into great detail on how to get your remote machine working - only to find you cheated and edited yours - glad you sorted it out. I will post some example configs in my contribs area later.

Because backuppc runs as user backuppc - the default 127.0.0.1 backup wont backup anything not readable to groups - I have changed this to sudo and tar for the next version - which gets everything.

A work in progress  :-)

mbachmann

Backuppc contrib
« Reply #18 on: October 07, 2004, 11:44:24 AM »
Unfortunately not, i was too hasty, now i got

Can't stat /opt/backuppc/files/pc/192.168.1.100/new: No such file or directory
Backup failed on 192.168.1.100 (inet connect: Connection refused)

Where 192.168.1.100 is the remote machine. Don't understand why backuppc needs to create a directory there.

duncan

Backuppc contrib
« Reply #19 on: October 07, 2004, 12:04:36 PM »
It doesnt.

/opt/backuppc/files/pc/192.168.1.100/new is a temporary directory on your backuppc machine - whilst the backup is running.

Do you have a rsyncd server running on your remote machine (I suspect not). If not - you will need to do rsync/tar over ssh - which is a little tricky. ;-)

mbachmann

Backuppc contrib
« Reply #20 on: October 07, 2004, 12:15:33 PM »
Grmpf, howto daemonize rsync? rsync -0 --daemon?
Found "rsync" in /etc/xinetd.d which reads

# default: off
# description: The rsync server is a good addition to am ftp server, as it \
#   allows crc checksumming etc.
service rsync
{
   disable   = yes
   socket_type     = stream
   wait            = no
   user            = root
   server          = /usr/bin/rsync
   server_args     = --daemon
   log_on_failure  += USERID
}

Should this be rsync.conf? I'm giving up for the moment.

duncan

Backuppc contrib
« Reply #21 on: October 07, 2004, 12:42:25 PM »
pico /etc/rsyncd.conf

Fill it in and save.

mbachmann

Backuppc contrib
« Reply #22 on: October 07, 2004, 01:06:55 PM »
In man pages the easiest things reads like Herculian labours.

Now there is daemonized rsync on the remote machine and the Backup machine is not complaining about a refused connection.

2004-10-07 13:41:19 User admin requested backup of 192.168.1.100 (192.168.1.100)
2004-10-07 13:41:20 Started full backup on 192.168.1.100 (pid=8198, share=home)
2004-10-07 13:41:25 192.168.1.100: Can't stat /opt/backuppc/files/pc/192.168.1.100/new: No such file or directory
2004-10-07 13:41:25 Backup failed on 192.168.1.100 (Unknown module 'home')

It cannot create the directory and there's a glitch with $Conf{RsyncShareName} = ['home','opt'];, regardless if i type ['/home','/opt'];.

The manual says "For $Conf{XferMethod} = rsyncd'' this should be the name of the module to backup (ie: the name from /etc/rsynd.conf)" - i esp. don't get the  statement in parenthesis.

duncan

Backuppc contrib
« Reply #23 on: October 08, 2004, 11:28:14 AM »
Perhaps this Howto might help. It uses tar over ssh as it's transport medium.

Regards Duncan

mbachmann

Backuppc contrib
« Reply #24 on: October 08, 2004, 07:46:38 PM »
Thank you duncan. I'll try it out on monday and report back.

Somehow i am also ambitious to get that rsyncd thing to work without much more asking, so wish me luck.

duncan

Backuppc contrib
« Reply #25 on: October 14, 2004, 03:26:36 AM »
Hi all.

Its been a couple of weeks, just curious if anyone had a go at this and how they went.

Regards Duncan

mbachmann

Backuppc contrib
« Reply #26 on: October 15, 2004, 12:51:50 PM »
I just followed the howto and it worked straight out. But if it is as complicated restoring the data back  i will be lost. Thank you, Duncan.

mbachmann

Backuppc contrib
« Reply #27 on: November 29, 2004, 04:19:20 PM »
Duncan, in the last line of the howto <i>...Create a new config.pl ...</i> you should point out, that the per-PC-config.pl is to be created in /opt/backuppc/files/pc/xxx.xxx.xxx.xxx (=ip-of-computer) directory.

There is a global config.pl in /opt/backuppc/files/conf and a local config.pl which can be easily messed up. This also is not not made very clear in the documentation - for me at least.

Useful commands i've found:
$Conf{Language} = 'de'; (supports de, en, fr, es, nl, it)
$Conf{CompressLevel} = 0; (2 or 3 is a good compromise)
$Conf{TarClientCmd} --one-file-system

Damian

Backuppc contrib
« Reply #28 on: January 19, 2005, 10:03:11 PM »
I have backuppc running great on SME 6.0 but am told by the restore page that I don't have the Archive::Zip package installed and cannot therefore offer ZIP files for restore. I contacted the backuppc maillist and was told where to get the CPAN stuff for this but it complains during install about missing Archive::Zlib. They said I need that too but installing that fails when gcc isn't found on SME :-(

Can't remember where I eventually grabbed the backuppc rpm from does anyone have experience of this ? Great package by the way  ;-)

Damian

Damian

Backuppc contrib
« Reply #29 on: January 20, 2005, 03:22:28 PM »
Just checked the contents of the contrib backuppc rpm and this doesn't contain these elements either. That probably means that anyone who installed this on SME can't restore to ZIP. Is this true ?

Damian

mbachmann

Backuppc contrib
« Reply #30 on: January 20, 2005, 04:17:38 PM »
I will check and report back with zip's and rar's - i have no zip's/rar's backed up, so i have to wait until tommorrow.

Offline askelon

  • ***
  • 59
  • +0/-0
Backuppc contrib
« Reply #31 on: January 21, 2005, 07:13:46 AM »
I have a slightly OT question in regards to this..  Ive installed it all fine on my server and have it backing up my docs/outlook from my workstation for test purposes.  This *seems* to be working.  Now does it get put on an automatic schedule?  Im thinking this would be a very good way to setup a backup system for one of my clients running SME.  They have about 15 notebooks that come in and out all day long so it would be ideal if the backup could poll their comp and backup as soon as it gets reconnected or at the standard designated time.  

From here Im thinking I'll use backup to workstation to then backup everything to DVD.

duncan

Backuppc contrib
« Reply #32 on: January 21, 2005, 09:20:16 AM »
Not OT at all.

This is one of the main features of backuppc - any machine that has x amount of successive ping replys will be backed up out of hours (servers, always on machines). A machine (like a notebook) will fail when it is away - so backuppc will back it up when it becomes available. It can deal with a partial backup (machine removed half way thru) and will even email the owner if a certain time period has passed without a backup. All of these time periods are configurable.

Regards Duncan

mbachmann

Backuppc contrib
« Reply #33 on: January 21, 2005, 10:36:46 AM »
@duncan, would you please go back a page and look at damians question? Maybe you can help him with perl-extension Archive::zip for backuppc from cpan.

Alright damian, i see what you mean. Restoring zip'/rar is possible but you cannot download the file(s) as a zip-Archive - therefore you need Perl-Erweiterung/extension Archive::Zip

But tar-archive dl is another working option and tar is not a problem for most packers. So why must it be zip?

duncan

Backuppc contrib
« Reply #34 on: January 21, 2005, 11:44:52 AM »
Quote from: "mbachmann"
@duncan, would you please go back a page and look at damians question? Maybe you can help him with perl-extension Archive::zip for backuppc from cpan.


I am guessing he needs to install the "dev tools" for gcc.

Damian

Backuppc contrib
« Reply #35 on: January 22, 2005, 12:54:35 AM »
I'm apparently watching this topic but am not getting the "someone's posted" emails. Odd.

Yes, tar is an option. I'd like to enable all functionality on SME so that I can can convince more people to take it up. Saying that this function would work on SuSE/RH but not on SME puts people off a bit  :-(

Hey Duncan,
Quote
I am guessing he needs to install the "dev tools" for gcc

I'm guessing he needs to install gcc too  :-D

Also without a working Compress::Zlib we don't get any storage compression :-(

Damian

duncan

Backuppc contrib
« Reply #36 on: January 22, 2005, 03:53:05 AM »
Ok,

I remember that Jespers antivirus script installs a few things you need. Take a look here and you may find what you need without resorting to cpan.

Let us know how you go. I seem to remember an issue where I would download 0 byte files.

Regards Duncan

Damian

Backuppc contrib
« Reply #37 on: January 23, 2005, 12:34:29 AM »
:-D   Fabulous

All now working. Needed perl-Archive-Zip-1.12-1.noarch.rpm and perl-Compress-Zlib-1.33-1.i386.rpm.

Brilliant job and many thanks!!!

Damian

Offline soprom

  • *
  • 589
  • +0/-0
    • www.logiciel-libre.org
BackupPC - 127.0.0.1 Ok, others fail
« Reply #38 on: March 01, 2005, 03:51:24 AM »
I'm recieving this error:
Got fatal error during xfer (Unable to read 4 bytes)
because the connexion was reset by peer... what ever that means.

I'm no guru, so could can someone give me a hint as to were to start looking for clues?

The same config.pl used for 127.0.0.1 (built-in) is modified with the next IP to backup (eg: 192.168.240.15)

Code: [Select]
$Conf{XferMethod} = 'rsync';
$Conf{RsyncShareName} = ['/etc/e-smith', '/home/e-smith'];
$Conf{BackupFilesExclude} = ['/opt','/tmp'];    
#
# Path to rsync executable on the client
#
$Conf{RsyncClientPath} = '/usr/bin/rsync';
$Conf{RsyncClientCmd} = '$sshPath -q -x -l root $host $rsyncPath $argList+';
$Conf{RsyncClientRestoreCmd} = '$sshPath -q -x -l root $host $rsyncPath $argList+';

$Conf{RsyncdAuthRequired} = 0;
$Conf{RsyncUserName} = 'root';
$Conf{RsyncPasswd} = 'xxxxxxx';
$Conf{ClientNameAlias} = '192.168.50.15';
$Conf{Language} = 'fr';
$Conf{CompressLevel} = 3;



Code: [Select]
2005-02-28 22:00:58 full backup started for directory /etc/e-smith
2005-02-28 22:00:59 Got fatal error during xfer (Unable to read 4 bytes)
2005-02-28 22:01:04 Backup aborted (Unable to read 4 bytes)


Thanks,
Sophie
Sophie from Montréal

Damian

Backuppc contrib
« Reply #39 on: March 01, 2005, 07:53:14 AM »
That sometimes happens when ssh can't connect to the target machine. As the user "backuppc" on your backuppc machine, can you run "ssh root@192.168.50.15 w" succesfully ? This tests the ssh part only.
If not, get this working first.
Damian

duncan

Backuppc contrib
« Reply #40 on: March 01, 2005, 07:54:25 AM »
Sophie,

Do you have 192.168.240.15 in the hosts file?

I have seen this before. From what I remember - it usually occurs due to a mismatch in the backup method being used between the client and the server (tar, rsync, rsyncd and smb).

If you are doing rsync over ssh (the preferred way) - then you need to share ssh public keys between the server and client.

Regards Duncan

duncan

Backuppc contrib
« Reply #41 on: March 01, 2005, 07:56:50 AM »
Quote from: "Damian"
That sometimes happens when ssh can't connect to the target machine. As the user "backuppc" on your backuppc machine, can you run "ssh root@192.168.50.15 w" succesfully ? This tests the ssh part only.
If not, get this working first.
Damian


And that too  :-)

Damian

Backuppc contrib
« Reply #42 on: March 01, 2005, 08:01:09 AM »
Hi Duncan,
What are doing providing support at this time of night ?  Ozzy government outlawed sleep ? ;-)
Damian

duncan

Backuppc contrib
« Reply #43 on: March 01, 2005, 08:09:10 AM »
Quote from: "Damian"
Hi Duncan,
What are doing providing support at this time of night ?  Ozzy government outlawed sleep ? ;-)
Damian


Its 3.00 pm - Nearly :pint: time.

Damian

Backuppc contrib
« Reply #44 on: March 01, 2005, 08:12:27 AM »
Sorry - forgot you're ahead (not behind). On chat now.
Damian

Offline soprom

  • *
  • 589
  • +0/-0
    • www.logiciel-libre.org
Maybe hardware problem
« Reply #45 on: March 02, 2005, 03:33:36 AM »
The problem seems to be caused by a faulty NIC... I replaced it and I'll see tomorrow. Thanks for your feedback.

Sophie
Sophie from Montréal

Offline soprom

  • *
  • 589
  • +0/-0
    • www.logiciel-libre.org
Still not working
« Reply #46 on: March 04, 2005, 01:10:06 AM »
I'm testing backuppc on two sites and I have the same problems on both sites. I can connect ssh to the other pc. When I issue the same command as backuppc
Code: [Select]
/usr/bin/ssh -q -x -l root@192.168.10.16 /usr/bin/rsync --server --sender --numeric-ids --perms --owner --group --devices --links --times --block-size=2048 --recursive --ignore-times . /etc/e-smith/
Nothing happend and the cursor comes right back.
/var/log/messages doesn't report about this.

help !
Sophie from Montréal

Offline soprom

  • *
  • 589
  • +0/-0
    • www.logiciel-libre.org
user backuppc
« Reply #47 on: March 04, 2005, 01:53:45 AM »
The user backuppc can connect via ssh to the target server and the logs report this:

Got fatal error during xfer (No files dumped for share /etc/e-smith

The server running backuppc is on a different subnet. Could this be a problem?
Sophie from Montréal

Damian

Backuppc contrib
« Reply #48 on: March 04, 2005, 01:23:14 PM »
Is rsync available on the remote server at /usr/bin ?
The subnet is irrelevant - we back up lots of clients via the internet and they're all on different subnets.
Any more hints in the remote server messages file ?
Damian

tkt

Backuppc contrib
« Reply #49 on: June 09, 2005, 03:03:53 AM »
Hi,

I have just installed backuppc-2.1.1.  Does anyone has a sample configuration for this software?  I could not even access the web interface of backuppc although I installed the cgi files during installation.  Any suggestion is welcomed.

Thanks.


tkt

Offline soprom

  • *
  • 589
  • +0/-0
    • www.logiciel-libre.org
Backuppc contrib
« Reply #50 on: June 09, 2005, 03:32:57 AM »
I finally discovered that user backuppc is not allowed to connect to the other sme box. Using user root is working fine.
Sophie from Montréal

tkt

Backuppc contrib
« Reply #51 on: June 10, 2005, 03:17:21 AM »
Hi,

I used cp linux-backuppc /etc/init.d/backuppc to copy to init.d, but it prompted

[root@kevin init.d]# service backuppc restart
Shutting down BackupPC:                          [FAILED]
Starting BackupPC: Couldn't open /data/BackupPC/conf/config.pl: Permission denied
BackupPC::Lib->new failed                        [FAILED]

when I try to start the service.  I checked the mod for config.pl and it showed as read only for owner, group and others.  I changed it to rwx for all, but still couldn't start backuppc.  Anyone can help with this?

Thanks.


tkt

duncan

Backuppc contrib
« Reply #52 on: June 10, 2005, 03:21:10 AM »
Was this an upgrade from the original rpm or a fresh installation.

tkt

Backuppc contrib
« Reply #53 on: June 10, 2005, 03:36:17 AM »
Hi Duncan,

It's a fresh installation.

cgi-bin directory        /var/www/cgi-bin/BackupPC
data directory           /data/BackupPC
html directory           /var/www/html/BackupPC
install directory        /usr/local/BackupPC
image directory          /usr/local/apache/htdocs/BackupPC
URL for image directory  /BackupPC

Apache version 2.0.49-4
Perl version 5.8.3-18
Mod_perl version 1.99_12-2.1

I'm using Fedora Core 2 installed as server.

Thanks.


tkt

duncan

Backuppc contrib
« Reply #54 on: June 10, 2005, 03:42:28 AM »
I can help with my rpm installed on a flavour of SME - however if your on Fedora core it might pay to visit the Backuppc mailing lists.

Regards Duncan

tkt

Backuppc contrib
« Reply #55 on: June 10, 2005, 05:06:31 AM »
Hi,

SOS.  Anyone is using Fedora Core 2 as BackupPC server?  A bit discouraged after trying with the configuration in the documentation coz the configuration didn't work on my Fedora Core 2.  Any help is welcomed.

Thanks.

tkt

Offline soprom

  • *
  • 589
  • +0/-0
    • www.logiciel-libre.org
Backuppc contrib
« Reply #56 on: June 12, 2005, 07:54:53 AM »
Is there a way to deal with dynamic remote hosts?
The file /root/.ssh/known_hosts saves the IP address of the remote hosts. Can this be omitted ?
Sophie from Montréal

duncan

Backuppc contrib
« Reply #57 on: June 12, 2005, 08:13:58 AM »
Quote from: "soprom"
Is there a way to deal with dynamic remote hosts?
The file /root/.ssh/known_hosts saves the IP address of the remote hosts. Can this be omitted ?


Just checking mine - looks like you can use names as well IP addresses.

Offline soprom

  • *
  • 589
  • +0/-0
    • www.logiciel-libre.org
Backuppc contrib
« Reply #58 on: June 12, 2005, 08:59:17 AM »
Can you confirm that ssh requires (based on know_hosts file) that the remote hosts has to have a fixed IP ?

If I set .ssh/config with
Code: [Select]
StrictHostKeyChecking yes
do you think I'm messing around?

The key to transfer to the remote host is the one for root or for backuppc ?
Sophie from Montréal

Damian

Backuppc contrib
« Reply #59 on: June 12, 2005, 07:11:15 PM »
Hi Sophie,
I back up 4 remote SME servers over ADSL with dynamic IPs and I don't have "StrictHostKeyChecking yes" for them and it works fine.
If you run backuppc as the user "backuppc" (the normal way) then you have to add the backuppc user public key to the remote server's ~root/.ssh/authorized_keys2 file. That way you get access to all the remote file systems ('cos you're root there from backuppc here).
Can you run "su - backuppc" on your backup server (as root) ? If not you need to set up backuppc as a standard user so that the ssh keys are available.
If you need hep wit that let me know.
Damian

tkt

Backuppc contrib
« Reply #60 on: June 13, 2005, 02:24:22 AM »
Hi,

My backuppc in Fedora Core 2 can be started already.  However, I don't really understand some field in config.pl.  Those fields are as below:

$Conf{UmaskMode}=027  ##isn't that mean no permission to owner, read permission to group and all permission to others?

$Conf{DfPath}='/bin/df'  ##what is this path for?  is it default for all?

$Conf{DfCmd}='$dfPath $topDir'  ##what is this field for?  

Thanks.

tkt

Backuppc contrib
« Reply #61 on: June 13, 2005, 05:11:06 AM »
Hi,

I would like to use rsync as transport method for backuppc.  Should I include this in the configuration?

$Conf{RsyncClientCmd} = '$sshPath -q -x -l root $kevin $/usr/bin/rsync $argList+' ;

The host to be backup is kevin.  Another question.  Let say I wanna backup folder /usr, which parameter should I include this path for the backup to backuppc server?

Thanks.


tkt

tkt

Backuppc contrib
« Reply #62 on: June 13, 2005, 05:45:19 AM »
Hi,

I specify the path in RsyncShareName, but backuppc still didn't backup folders in the path to backuppc server.  The configuration is here.  Please correct if there is anything wrong.  I would like to use backuppc running on user Niceman.sy to backup /usr folder from host kevin.sy using rsync.  The host is using linux also.  If the code I pasted is too lengthy, I would also appreciate if someone could just point out which are the necessary path for me to edit in order to run the backup, and leave other parameters unchanged.


$Conf{ServerHost} = 'Niceman.sy';
$Conf{ServerPort} = -1;
$Conf{MyPath} = '/bin';
$Conf{UmaskMode} = 027;
$Conf{WakeupSchedule} = [1..23];
$Conf{MaxBackups} = 4;
$Conf{MaxUserBackups} = 4;
$Conf{MaxPendingCmds} = 10;
$Conf{MaxBackupPCNightlyJobs} = 2;
$Conf{MaxOldLogFiles} = 14;
$Conf{DfPath} = '/bin/df';
$Conf{DfCmd} = '$dfPath $topDir';
$Conf{SplitPath} = '/usr/bin/split';
$Conf{ParPath}   = '/usr/bin/par2';
$Conf{CatPath}   = '/bin/cat';
$Conf{GzipPath}  = '/bin/gzip';
$Conf{Bzip2Path} = '/usr/bin/bzip2';
$Conf{DfMaxUsagePct} = 95;
$Conf{TrashCleanSleepSec} = 300;
$Conf{DHCPAddressRanges} = [];
$Conf{BackupPCUser} = 'root';
$Conf{CgiDir}       = '/var/www/cgi-bin/BackupPC';
$Conf{InstallDir}   = '/usr/local/BackupPC';
$Conf{BackupPCUserVerify} = 1;
$Conf{HardLinkMax} = 31999;
$Conf{SmbShareName} = 'C$';
$Conf{SmbSharePasswd} = '';
$Conf{TarShareName} = '/';
$Conf{FullPeriod} = 6.97;
$Conf{IncrPeriod} = 0.97;
$Conf{FullKeepCnt} = 1;
$Conf{FullKeepCntMin} = 1;
$Conf{FullAgeMax}     = 90;
$Conf{IncrKeepCnt} = 6;
$Conf{IncrKeepCntMin} = 1;
$Conf{IncrAgeMax}     = 30;
$Conf{PartialAgeMax} = 3;
$Conf{IncrFill} = 0;
$Conf{RestoreInfoKeepCnt} = 10;
$Conf{ArchiveInfoKeepCnt} = 10;

$Conf{BackupFilesOnly} = undef;
$Conf{BackupFilesExclude} = undef;


$Conf{BlackoutBadPingLimit} = 3;
$Conf{BlackoutGoodCnt}      = 7;
$Conf{BlackoutPeriods} = [
    {
   hourBegin =>  7.0,
   hourEnd   => 19.5,
   weekDays  => [1, 2, 3, 4, 5],
    },
];
$Conf{XferMethod} = 'rsync';
$Conf{XferLogLevel} = 1;
$Conf{SmbClientPath} = '/usr/bin/smbclient';
$Conf{SmbClientFullCmd} = '$smbClientPath \\\\$host\\$shareName'
       . ' $I_option -U $userName -E -N -d 1'
            . ' -c tarmode\\ full -Tc$X_option - $fileList';
$Conf{SmbClientIncrCmd} = '$smbClientPath \\\\$host\\$shareName'
       . ' $I_option -U $userName -E -N -d 1'
       . ' -c tarmode\\ full -TcN$X_option $timeStampFile - $fileList';
$Conf{SmbClientRestoreCmd} = '$smbClientPath \\\\$host\\$shareName'
            . ' $I_option -U $userName -E -N -d 1'
            . ' -c tarmode\\ full -Tx -';
$Conf{TarClientCmd} = '$sshPath -q -x -n -l root $host'
                    . ' $tarPath -c -v -f - -C $shareName+'
                    . ' --totals';
$Conf{TarFullArgs} = '$fileList+';
$Conf{TarClientRestoreCmd} = '$sshPath -q -x -l root $host'
         . ' $tarPath -x -p --numeric-owner --same-owner'
         . ' -v -f - -C $shareName+';

$Conf{TarClientPath} = '/bin/gtar';
$Conf{RsyncClientPath} = '/usr/bin/rsync';
$Conf{RsyncClientCmd} = '$sshPath -q -x -l root $kevin $/usr/bin/rsync $argList+' ;
$Conf{RsyncClientRestoreCmd} = '$sshPath -q -x -l root $host $rsyncPath $argList+';
$Conf{RsyncClientRestoreCmd} = '$sshPath -q -x -l root $kevin $/usr/bin/rsync $argList+';


$Conf{RsyncShareName} = '/';


$Conf{RsyncdClientPort} = 873;

#
# Rsync daemon user name on client, for $Conf{XferMethod} = "rsyncd".
# The user name and password are stored on the client in whatever file
# the "secrets file" parameter in rsyncd.conf points to
# (eg: /etc/rsyncd.secrets).
#
$Conf{RsyncdUserName} = '';

#
# Rsync daemon user name on client, for $Conf{XferMethod} = "rsyncd".
# The user name and password are stored on the client in whatever file
# the "secrets file" parameter in rsyncd.conf points to
# (eg: /etc/rsyncd.secrets).
#
$Conf{RsyncdPasswd} = '';

#
# Whether authentication is mandatory when connecting to the client's
# rsyncd.  By default this is on, ensuring that BackupPC will refuse to
# connect to an rsyncd on the client that is not password protected.
# Turn off at your own risk.
#
$Conf{RsyncdAuthRequired} = 1;

#
# When rsync checksum caching is enabled (by adding the
# --checksum-seed=32761 option to $Conf{RsyncArgs}), the cached
# checksums can be occaisonally verified to make sure the file
# contents matches the cached checksums.  This is to avoid the
# risk that disk problems might cause the pool file contents to
# get corrupted, but the cached checksums would make BackupPC
# think that the file still matches the client.
#
# This setting is the probability (0 means never and 1 means always)
# that a file will be rechecked.  Setting it to 0 means the checksums
# will not be rechecked (unless there is a phase 0 failure).  Setting
# it to 1 (ie: 100%) means all files will be checked, but that is
# not a desirable setting since you are better off simply turning
# caching off (ie: remove the --checksum-seed option).
#  
# The default of 0.01 means 1% (on average) of the files during a full
# backup will have their cached checksum re-checked.
#  
# This setting has no effect unless checksum caching is turned on.
#  
$Conf{RsyncCsumCacheVerifyProb} = 0.01;

#
# Arguments to rsync for backup.  Do not edit the first set unless you
# have a thorough understanding of how File::RsyncP works.
#
# Examples of additional arguments that should work are --exclude/--include,
# eg:
#
#     $Conf{RsyncArgs} = [
#           # original arguments here
#           '-v',
#           '--exclude', '/proc',
#           '--exclude', '*.tmp',
#     ];
#
$Conf{RsyncArgs} = [
       #
       # Do not edit these!
       #
            '--numeric-ids',
            '--perms',
            '--owner',
            '--group',
            '--devices',
            '--links',
            '--times',
            '--block-size=2048',
            '--recursive',

       #
       # If you are using a patched client rsync that supports the
       # --checksum-seed option (see http://backuppc.sourceforge.net),
       # then uncomment this to enabled rsync checksum cachcing
       #
       #'--checksum-seed=32761',

       #
       # Add additional arguments here
       #
];

#
# Arguments to rsync for restore.  Do not edit the first set unless you
# have a thorough understanding of how File::RsyncP works.
#
# If you want to disable direct restores using rsync (eg: is the module
# is read-only), you should set $Conf{RsyncRestoreArgs} to undef and
# the corresponding CGI restore option will be removed.
#
$Conf{RsyncRestoreArgs} = [
       #
       # Do not edit these!
       #
       '--numeric-ids',
       '--perms',
       '--owner',
       '--group',
       '--devices',
       '--links',
       '--times',
       '--block-size=2048',
       '--relative',
       '--ignore-times',
       '--recursive',

       #
       # If you are using a patched client rsync that supports the
       # --checksum-seed option (see http://backuppc.sourceforge.net),
       # then uncomment this to enabled rsync checksum cachcing
       #
       #'--checksum-seed=32761',

       #
       # Add additional arguments here
       #
];

#
# Archive Destination
#
# The Destination of the archive
# e.g. /tmp for file archive or /dev/nst0 for device archive
#
$Conf{ArchiveDest} = '/tmp';

#
# Archive Compression type
#
# The valid values are:
#
#   - 'none':  No Compression
#
#   - 'gzip':  Medium Compression. Recommended.
#
#   - 'bzip2': High Compression but takes longer.
#
$Conf{ArchiveComp} = 'gzip';

#
# Archive Parity Files
#
# The amount of Parity data to generate, as a percentage
# of the archive size.
# Uses the commandline par2 (par2cmdline) available from
# http://parchive.sourceforge.net
#
# Only useful for file dumps.
#
# Set to 0 to disable this feature.
#
$Conf{ArchivePar} = 0;

#
# Archive Size Split
#
# Only for file archives. Splits the output into
# the specified size * 1,000,000.
# e.g. to split into 650,000,000 bytes, specify 650 below.
#
# If the value is 0, or if $Conf{ArchiveDest} is an existing file or
# device (e.g. a streaming tape drive), this feature is disabled.
#
$Conf{ArchiveSplit} = 0;

#
# Archive Command
#
# This is the command that is called to actually run the archive process
# for each host.  The following variables are substituted at run-time:
#
#   $Installdir    The installation directory of BackupPC
#   $tarCreatePath The path to BackupPC_tarCreate
#   $splitpath     The path to the split program
#   $parpath       The path to the par2 program
#   $host          The host to archive
#   $backupnumber  The backup number of the host to archive
#   $compression   The path to the compression program
#   $compext       The extension assigned to the compression type
#   $splitsize     The number of bytes to split archives into
#   $archiveloc    The location to put the archive
#   $parfile       The amount of parity data to create (percentage)
#
$Conf{ArchiveClientCmd} = '$Installdir/bin/BackupPC_archiveHost'
   . ' $tarCreatePath $splitpath $parpath $host $backupnumber'
   . ' $compression $compext $splitsize $archiveloc $parfile *';

#
# Full path for ssh. Security caution: normal users should not
# allowed to write to this file or directory.
#
$Conf{SshPath} = '/usr/bin/ssh';

#
# Full path for nmblookup. Security caution: normal users should not
# allowed to write to this file or directory.
#
# nmblookup is from the Samba distribution. nmblookup is used to get the
# netbios name, necessary for DHCP hosts.
#
$Conf{NmbLookupPath} = '/usr/bin/nmblookup';

#
# NmbLookup command.  Given an IP address, does an nmblookup on that
# IP address.  The following variables are substituted at run-time:
#
#   $nmbLookupPath      path to nmblookup ($Conf{NmbLookupPath})
#   $host               IP address
#
# This command is only used for DHCP hosts: given an IP address, this
# command should try to find its NetBios name.
#
$Conf{NmbLookupCmd} = '$nmbLookupPath -A $host';

#
# NmbLookup command.  Given a netbios name, finds that host by doing
# a NetBios lookup.  Several variables are substituted at run-time:
#
#   $nmbLookupPath      path to nmblookup ($Conf{NmbLookupPath})
#   $host               NetBios name
#
# In some cases you might need to change the broadcast address, for
# example if nmblookup uses 192.168.255.255 by default and you find
# that doesn't work, try 192.168.1.255 (or your equivalent class C
# address) using the -B option:
#
#    $Conf{NmbLookupFindHostCmd} = '$nmbLookupPath -B 192.168.1.255 $host';
#
# If you use a WINS server and your machines don't respond to
# multicast NetBios requests you can use this (replace 1.2.3.4
# with the IP address of your WINS server):
#
#    $Conf{NmbLookupFindHostCmd} = '$nmbLookupPath -R -U 1.2.3.4 $host';
#
# This is preferred over multicast since it minimizes network traffic.
#
# Experiment manually for your site to see what form of nmblookup command
# works.
#
$Conf{NmbLookupFindHostCmd} = '$nmbLookupPath $host';

#
# For fixed IP address hosts, BackupPC_dump can also verify the netbios
# name to ensure it matches the host name.  An error is generated if
# they do not match.  Typically this flag is off.  But if you are going
# to transition a bunch of machines from fixed host addresses to DHCP,
# setting this flag is a great way to verify that the machines have
# their netbios name set correctly before turning on DCHP.
#
$Conf{FixedIPNetBiosNameCheck} = 0;

#
# Full path to the ping command.  Security caution: normal users
# should not be allowed to write to this file or directory.
#
# If you want to disable ping checking, set this to some program
# that exits with 0 status, eg:
#
#     $Conf{PingPath} = '/bin/echo';
#
$Conf{PingPath} = '/bin/ping';

#
# Ping command.  The following variables are substituted at run-time:
#
#   $pingPath      path to ping ($Conf{PingPath})
#   $host          host name
#
# Wade Brown reports that on solaris 2.6 and 2.7 ping -s returns the wrong
# exit status (0 even on failure).  Replace with "ping $host 1", which
# gets the correct exit status but we don't get the round-trip time.
#
$Conf{PingCmd} = '$pingPath -c 1 -w 3 $host';

#
# Path to init.d script and command to use that script to start the
# server from the CGI interface.  The following variables are substituted
# at run-time:
#
#   $sshPath           path to ssh ($Conf{SshPath})
#   $serverHost        same as $Conf{ServerHost}
#   $serverInitdPath   path to init.d script ($Conf{ServerInitdPath})
#
# Example:
#
# $Conf{ServerInitdPath}     = '/etc/init.d/backuppc';
# $Conf{ServerInitdStartCmd} = '$sshPath -q -x -l root $serverHost'
#                            . ' $serverInitdPath start'
#                            . ' < /dev/null >& /dev/null';
#
$Conf{ServerInitdPath} = '';
$Conf{ServerInitdStartCmd} = '';

#
# Compression level to use on files.  0 means no compression.  Compression
# levels can be from 1 (least cpu time, slightly worse compression) to
# 9 (most cpu time, slightly better compression).  The recommended value
# is 3.  Changing to 5, for example, will take maybe 20% more cpu time
# and will get another 2-3% additional compression. See the zlib
# documentation for more information about compression levels.
#
# Changing compression on or off after backups have already been done
# will require both compressed and uncompressed pool files to be stored.
# This will increase the pool storage requirements, at least until all
# the old backups expire and are deleted.
#
# It is ok to change the compression value (from one non-zero value to
# another non-zero value) after dumps are already done.  Since BackupPC
# matches pool files by comparing the uncompressed versions, it will still
# correctly match new incoming files against existing pool files.  The
# new compression level will take effect only for new files that are
# newly compressed and added to the pool.
#
# If compression was off and you are enabling compression for the first
# time you can use the BackupPC_compressPool utility to compress the
# pool.  This avoids having the pool grow to accommodate both compressed
# and uncompressed backups.  See the documentation for more information.
#
# Note: compression needs the Compress::Zlib perl library.  If the
# Compress::Zlib library can't be found then $Conf{CompressLevel} is
# forced to 0 (compression off).
#
$Conf{CompressLevel} = 0;

#
# Maximum round-trip ping time in milliseconds.  This threshold is set
# to avoid backing up PCs that are remotely connected through WAN or
# dialup connections.  The output from ping -s (assuming it is supported
# on your system) is used to check the round-trip packet time.  On your
# local LAN round-trip times should be much less than 20msec.  On most
# WAN or dialup connections the round-trip time will be typically more
# than 20msec.  Tune if necessary.
#
$Conf{PingMaxMsec} = 20;

#
# Timeout in seconds when listening for the transport program's
# (smbclient, tar etc) stdout. If no output is received during this
# time, then it is assumed that something has wedged during a backup,
# and the backup is terminated.
#
# Note that stdout buffering combined with huge files being backed up
# could cause longish delays in the output from smbclient that
# BackupPC_dump sees, so in rare cases you might want to increase
# this value.
#
# Despite the name, this parameter sets the timeout for all transport
# methods (tar, smb etc).
#
$Conf{ClientTimeout} = 7200;

#
# Maximum number of log files we keep around in each PC's directory
# (ie: pc/$host).  These files are aged monthly.  A setting of 12
# means there will be at most the files LOG, LOG.0, LOG.1, ... LOG.11
# in the pc/$host directory (ie: about a years worth).  (Except this
# month's LOG, these files will have a .z extension if compression
# is on).
#
# If you decrease this number after BackupPC has been running for a
# while you will have to manually remove the older log files.
#
$Conf{MaxOldPerPCLogFiles} = 12;

#
# Optional commands to run before and after dumps and restores.
# Stdout from these commands will be written to the Xfer (or Restore)
# log file.  One example of using these commands would be to
# shut down and restart a database server, or to dump a database
# to files for backup.  Example:
#
#    $Conf{DumpPreUserCmd} = '$sshPath -q -x -l root $host /usr/bin/dumpMysql';
#
# The following variable substitutions are made at run time for
# $Conf{DumpPreUserCmd} and $Conf{DumpPostUserCmd}:
#
#        $type         type of dump (incr or full)
#        $xferOK       1 if the dump succeeded, 0 if it didn't
#        $client       client name being backed up
#        $host         host name (could be different from client name if
#                                 $Conf{ClientNameAlias} is set)
#        $hostIP       IP address of host
#        $user         user name from the hosts file
#        $moreUsers    list of additional users from the hosts file
#        $share        the first share name
#        $shares       list of all the share names
#        $XferMethod   value of $Conf{XferMethod} (eg: tar, rsync, smb)
#        $sshPath      value of $Conf{SshPath},
#        $cmdType      set to DumpPreUserCmd or DumpPostUserCmd
#
# The following variable substitutions are made at run time for
# $Conf{RestorePreUserCmd} and $Conf{RestorePostUserCmd}:
#
#        $client       client name being backed up
#        $xferOK       1 if the restore succeeded, 0 if it didn't
#        $host         host name (could be different from client name if
#                                 $Conf{ClientNameAlias} is set)
#        $hostIP       IP address of host
#        $user         user name from the hosts file
#        $moreUsers    list of additional users from the hosts file
#        $share        the first share name
#        $XferMethod   value of $Conf{XferMethod} (eg: tar, rsync, smb)
#        $sshPath      value of $Conf{SshPath},
#        $type         set to "restore"
#        $bkupSrcHost  host name of the restore source
#        $bkupSrcShare share name of the restore source
#        $bkupSrcNum   backup number of the restore source
#        $pathHdrSrc   common starting path of restore source
#        $pathHdrDest  common starting path of destination
#        $fileList     list of files being restored
#        $cmdType      set to RestorePreUserCmd or RestorePostUserCmd
#
# The following variable substitutions are made at run time for
# $Conf{ArchivePreUserCmd} and $Conf{ArchivePostUserCmd}:
#
#        $client       client name being backed up
#        $xferOK       1 if the archive succeeded, 0 if it didn't
#        $host         Name of the archive host
#        $user         user name from the hosts file
#        $share        the first share name
#        $XferMethod   value of $Conf{XferMethod} (eg: tar, rsync, smb)
#        $HostList     list of hosts being archived
#        $BackupList   list of backup numbers for the hosts being archived
#        $archiveloc   location where the archive is sent to
#        $parfile      amount of parity data being generated (percentage)
#        $compression  compression program being used (eg: cat, gzip, bzip2)
#        $compext      extension used for compression type (eg: raw, gz, bz2)
#        $splitsize    size of the files that the archive creates
#        $sshPath      value of $Conf{SshPath},
#        $type         set to "archive"
#        $cmdType      set to ArchivePreUserCmd or ArchivePostUserCmd
#
$Conf{DumpPreUserCmd}     = undef;
$Conf{DumpPostUserCmd}    = undef;
$Conf{RestorePreUserCmd}  = undef;
$Conf{RestorePostUserCmd} = undef;
$Conf{ArchivePreUserCmd}  = undef;
$Conf{ArchivePostUserCmd} = undef;

#
# Override the client's host name.  This allows multiple clients
# to all refer to the same physical host.  This should only be
# set in the per-PC config file and is only used by BackupPC at
# the last moment prior to generating the command used to backup
# that machine (ie: the value of $Conf{ClientNameAlias} is invisible
# everywhere else in BackupPC).  The setting can be a host name or
# IP address, eg:
#
#         $Conf{ClientNameAlias} = 'realHostName';
#         $Conf{ClientNameAlias} = '192.1.1.15';
#
# will cause the relevant smb/tar/rsync backup/restore commands to be
# directed to realHostName, not the client name.
#
# Note: this setting doesn't work for hosts with DHCP set to 1.
#
$Conf{ClientNameAlias} = undef;

#
# Advanced option for asking BackupPC to load additional perl modules.
# Can be a list (array ref) of module names to load at startup.
#
$Conf{PerlModuleLoad}     = undef;

###########################################################################
# Email reminders, status and messages
# (can be overridden in the per-PC config.pl)
###########################################################################
#
# Full path to the sendmail command.  Security caution: normal users
# should not allowed to write to this file or directory.
#
$Conf{SendmailPath} = '/usr/sbin/sendmail';

#
# Minimum period between consecutive emails to a single user.
# This tries to keep annoying email to users to a reasonable
# level.  Email checks are done nightly, so this number is effectively
# rounded up (ie: 2.5 means a user will never receive email more
# than once every 3 days).
#
$Conf{EMailNotifyMinDays} = 2.5;

#
# Name to use as the "from" name for email.  Depending upon your mail
# handler this is either a plain name (eg: "admin") or a fully-qualified
# name (eg: "admin@mydomain.com").
#
$Conf{EMailFromUserName} = 'root';

#
# Destination address to an administrative user who will receive a
# nightly email with warnings and errors.  If there are no warnings
# or errors then no email will be sent.  Depending upon your mail
# handler this is either a plain name (eg: "admin") or a fully-qualified
# name (eg: "admin@mydomain.com").
#
$Conf{EMailAdminUserName} = 'root';

#
# Destination domain name for email sent to users.  By default
# this is empty, meaning email is sent to plain, unqualified
# addresses.  Otherwise, set it to the destintation domain, eg:
#
#    $Cong{EMailUserDestDomain} = '@mydomain.com';
#
# With this setting user email will be set to 'user@mydomain.com'.
#
$Conf{EMailUserDestDomain} = '';

#
# This subject and message is sent to a user if their PC has never been
# backed up.
#
# These values are language-dependent.  The default versions can be
# found in the language file (eg: lib/BackupPC/Lang/en.pm).  If you
# need to change the message, copy it here and edit it, eg:
#
#   $Conf{EMailNoBackupEverMesg} = <<'EOF';
#   To: $user$domain
#   cc:
#   Subject: $subj
#  
#   Dear $userName,
#  
#   This is a site-specific email message.
#   EOF
#
$Conf{EMailNoBackupEverSubj} = undef;
$Conf{EMailNoBackupEverMesg} = undef;

#
# How old the most recent backup has to be before notifying user.
# When there have been no backups in this number of days the user
# is sent an email.
#
$Conf{EMailNotifyOldBackupDays} = 7.0;

#
# This subject and message is sent to a user if their PC has not recently
# been backed up (ie: more than $Conf{EMailNotifyOldBackupDays} days ago).
#
# These values are language-dependent.  The default versions can be
# found in the language file (eg: lib/BackupPC/Lang/en.pm).  If you
# need to change the message, copy it here and edit it, eg:
#
#   $Conf{EMailNoBackupRecentMesg} = <<'EOF';
#   To: $user$domain
#   cc:
#   Subject: $subj
#  
#   Dear $userName,
#  
#   This is a site-specific email message.
#   EOF
#
$Conf{EMailNoBackupRecentSubj} = undef;
$Conf{EMailNoBackupRecentMesg} = undef;

#
# How old the most recent backup of Outlook files has to be before
# notifying user.
#
$Conf{EMailNotifyOldOutlookDays} = 5.0;

#
# This subject and message is sent to a user if their Outlook files have
# not recently been backed up (ie: more than $Conf{EMailNotifyOldOutlookDays}
# days ago).
#
# These values are language-dependent.  The default versions can be
# found in the language file (eg: lib/BackupPC/Lang/en.pm).  If you
# need to change the message, copy it here and edit it, eg:
#
#   $Conf{EMailOutlookBackupMesg} = <<'EOF';
#   To: $user$domain
#   cc:
#   Subject: $subj
#  
#   Dear $userName,
#  
#   This is a site-specific email message.
#   EOF
#
$Conf{EMailOutlookBackupSubj} = undef;
$Conf{EMailOutlookBackupMesg} = undef;

###########################################################################
# CGI user interface configuration settings
# (can be overridden in the per-PC config.pl)
###########################################################################
#
# Normal users can only access information specific to their host.
# They can start/stop/browse/restore backups.
#
# Administrative users have full access to all hosts, plus overall
# status and log information.
#
# The administrative users are the union of the unix/linux group
# $Conf{CgiAdminUserGroup} and the manual list of users, separated
# by spaces, in $Conf{CgiAdminUsers}. If you don't want a group or
# manual list of users set the corresponding configuration setting
# to undef or an empty string.
#
# If you want every user to have admin privileges (careful!), set
# $Conf{CgiAdminUsers} = '*'.
#
# Examples:
#    $Conf{CgiAdminUserGroup} = 'admin';
#    $Conf{CgiAdminUsers}     = 'craig celia';
#    --> administrative users are the union of group admin, plus
#      craig and celia.
#
#    $Conf{CgiAdminUserGroup} = '';
#    $Conf{CgiAdminUsers}     = 'craig celia';
#    --> administrative users are only craig and celia'.
#
$Conf{CgiAdminUserGroup} = '';
$Conf{CgiAdminUsers}     = '';

#
# URL of the BackupPC_Admin CGI script.  Used for email messages.
#
$Conf{CgiURL} = 'http://Niceman.shinyang/cgi-bin/BackupPC/BackupPC_Admin';

#  
# Language to use.  See lib/BackupPC/Lang for the list of supported
# languages, which include English (en), French (fr), Spanish (es),
# German (de), Italian (it) and Dutch (nl).
#
# Currently the Language setting applies to the CGI interface and email
# messages sent to users.  Log files and other text are still in English.
#
$Conf{Language} = 'en';

#
# User names that are rendered by the CGI interface can be turned
# into links into their home page or other information about the
# user.  To set this up you need to create two sprintf() strings,
# that each contain a single '%s' that will be replaced by the user
# name.  The default is a mailto: link.
#
# $Conf{CgiUserHomePageCheck} should be an absolute file path that
# is used to check (via "-f") that the user has a valid home page.
# Set this to undef or an empty string to turn off this check.
#
# $Conf{CgiUserUrlCreate} should be a full URL that points to the
# user's home page.  Set this to undef or an empty string to turn
# off generation of URLs for user names.
#
# Example:
#    $Conf{CgiUserHomePageCheck} = '/var/www/html/users/%s.html';
#    $Conf{CgiUserUrlCreate}     = 'http://myhost/users/%s.html';
#    --> if /var/www/html/users/craig.html exists, then 'craig' will
#      be rendered as a link to http://myhost/users/craig.html.
#
$Conf{CgiUserHomePageCheck} = '';
$Conf{CgiUserUrlCreate}     = 'mailto:%s';

#
# Date display format for CGI interface.  True for US-style dates (MM/DD)
# and zero for international dates (DD/MM).
#
$Conf{CgiDateFormatMMDD} = 1;

#
# If set, the complete list of hosts appears in the left navigation
# bar pull-down for administrators.  Otherwise, just the hosts for which
# the user is listed in the host file (as either the user or in moreUsers)
# are displayed.
#
$Conf{CgiNavBarAdminAllHosts} = 1;

#
# Enable/disable the search box in the navigation bar.
#
$Conf{CgiSearchBoxEnable} = 1;

#
# Additional navigation bar links.  These appear for both regular users
# and administrators.  This is a list of hashes giving the link (URL)
# and the text (name) for the link.  Specifying lname instead of name
# uses the language specific string (ie: $Lang->{lname}) instead of
# just literally displaying name.
#
$Conf{CgiNavBarLinks} = [
    {
        link  => "?action=view&type=docs",
        lname => "Documentation",    # actually displays $Lang->{Documentation}
    },
    {
        link  => "http://backuppc.sourceforge.net/faq",
        name  => "FAQ",              # displays literal "FAQ"
    },
    {
        link  => "http://backuppc.sourceforge.net",
        name  => "SourceForge",      # displays literal "SourceForge"
    },
];

#
# Hilight colors based on status that are used in the PC summary page.
#
$Conf{CgiStatusHilightColor} = {
    Reason_backup_failed           => '#ffcccc',
    Reason_backup_done             => '#ccffcc',
    Reason_no_ping                 => '#ffff99',
    Reason_backup_canceled_by_user => '#ff9900',
    Status_backup_in_progress      => '#66cc99',
};

#
# Additional CGI header text.
#
$Conf{CgiHeaders} = '<meta http-equiv="pragma" content="no-cache">';

#
# Directory where images are stored.  This directory should be below
# Apache's DocumentRoot.  This value isn't used by BackupPC but is
# used by configure.pl when you upgrade BackupPC.
#
# Example:
#     $Conf{CgiImageDir} = '/usr/local/apache/htdocs/BackupPC';
#
$Conf{CgiImageDir} = '/usr/local/apache/htdocs/BackupPC';

#
# Additional mappings of file name extenions to Content-Type for
# individual file restore.  See $Ext2ContentType in BackupPC_Admin
# for the default setting.  You can add additional settings here,
# or override any default settings.  Example:
#
#     $Conf{CgiExt2ContentType} = {
#                 'pl'  => 'text/plain',
#          };
#
$Conf{CgiExt2ContentType} = { };

#
# URL (without the leading http://host) for BackupPC's image directory.
# The CGI script uses this value to serve up image files.
#
# Example:
#     $Conf{CgiImageDirURL} = '/BackupPC';
#
$Conf{CgiImageDirURL} = '/BackupPC';

#
# CSS stylesheet for the CGI interface.  It is stored in the
# $Conf{CgiImageDir} directory and accessed via the
# $Conf{CgiImageDirURL} URL.
#
$Conf{CgiCSSFile} = 'BackupPC_stnd.css';

Damian

Backuppc contrib
« Reply #63 on: June 13, 2005, 09:55:24 AM »
tkt,
These are valid questions but this in't the backuppc forum. Please ask them at the backuppc mailling list at https://lists.sourceforge.net/lists/listinfo/backuppc-users.
Craig, Les, Carl and others will be happy to answer your questions there.
And yes, it is a busy and knowlegable list  :-D

tkt

Backuppc contrib
« Reply #64 on: June 14, 2005, 03:35:31 AM »
Hi,

I clicked on the link, but it displayed that the mailing list is not available.  I managed to bring up the GUI of backuppc and set up rsyncd as transport protocol.  however, there is error during backup.  wondering if anyone know of other forum which I could post the question to.  It prompted "Finish EOL:  The connection has been reset" during backup.

Thanks.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Backuppc contrib
« Reply #65 on: February 20, 2006, 04:41:56 PM »
Quote from: "duncan"
I can help with my rpm installed on a flavour of SME


Duncan, could you please post your src.rpm file and/or spec file, so that someone else can make contributions to the package? For instance, I'd like to look at what's involved to get it installed smoothly on SME7.

Thanks

Offline RvLardin

  • ****
  • 82
  • +0/-0
    • http://sme.firewall-services.com
Backuppc on SME7 ?
« Reply #66 on: February 22, 2006, 06:30:08 PM »
If anyone dare to to do it, I'll be the happiest man.

If it can help, I'm ok to encourage by an odd contribution, at least 400 € (about 475 US$).
I'm not sure that everybody here agree with this form of contribution and I'm in advance sorry if it's offending anyone.

RV.
----
"Those who are willing to lose some of their essential liberties in favour of security deserve neither and will lose both."
- Thomas Jefferson .

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: Backuppc on SME7 ?
« Reply #67 on: February 23, 2006, 02:41:55 AM »
Quote from: "RvLardin"

If it can help, I'm ok to encourage by an odd contribution, at least 400 € (about 475 US$).
I'm not sure that everybody here agree with this form of contribution and I'm in advance sorry if it's offending anyone.


I'd suggest that you open a bug report in "SME Server Future" as a New Feature Request, suggesting a backuppc addition. You might mention your "encouragement" there as well.

Offline Daniel B.

  • *
  • 1,700
  • +0/-0
    • Firewall Services, la sécurité des réseaux
Backuppc contrib
« Reply #68 on: March 29, 2006, 01:16:20 PM »
Hello. I'm looking for a backup solution on SME 7rc1. I've already tried several and backuppc looks interesting. I install the 2.1.0-3 version that I've found at http://mirror.contribs.org/smeserver/contribs/dthomas/smeserver/6.x/Beta/Backuppc/
(not sure it's the last version)
It seems to work quite well on SME 7 even if it's for SME 6.
I'd like to have a panel in the server manager for the configuration. Don't know if someone already worked (or still working) on it so, if you have any information...I'd like to help developing it.
ps: don't blame me if you see monstrous faults, I don't speak good english.
C'est la fin du monde !!! :lol: