Re: [BackupPC-users] first full never completes
On Sat, Sep 3, 2011 at 11:09 AM, Timothy J Massey tmas...@obscorp.comwrote: But would probably be a very good idea. What would be an even better idea would be to grab a spare PC (or a virtual guest) and test it from a completely clean installation. And document the *heck* out of what you do: you *will* be doing it again (and again and again). Well the whole thing is a test system, and I'm not that concerned with figuring out what went wrong vs moving forward, so I guess I'll just wipe and restart with a clean OS. Since I want to use the BackupPC 3.1 package (eventual production system will be on CentOS5), while I'm at it I'll use the Ubuntu version it's designed for, Lucid 10.04, rather than the latest Natty 11.04. Hopefully will eliminate the problems I'm seeing un/re- installing from the package system. I plan to keep the pool folders and of course my long-tweaked config.pl, but will start off from the clean install with as close to defaults as possible with a small static target share to test with, then make the changes a little at a time only after I've got the basics working right. Which as you say I should've done from the start. . . In the meantime there are a few unanswered questions in the thread above if anyone has the information to ontribute more detailed responses I'm sure it will help others googling later on. . . -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Swapping drives for offsite - the whole shebang
Will a BackupPC 3.2 system just work with a conf/log/pool/pc filesystem moved over from 3.1, or is there an upgrade process run on the data? If the latter, I imagine that would make it difficult to move that data back to 3.1? Just thinking of disaster recovery scenarios, maybe building a custom live-cd boot disc to store offsite with the data drive. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Rsynv vs. tar, full vs. incremental
Hi there, On Fri, 2 Sep 2011 Pavel Hofman wrote: I guess the main problem is tar cannot resume after a network glitch, Can you simply tweak the TCP settings in /proc/sys/net/ so that the connection can cope with a ~one-minute break and tar doesn't notice? -- 73, Ged. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
[BackupPC-users] Upgrade BackupPC 2.1.2 to 3.2.1
Hi, In Gentoo BackupPC 3.2.1 has just gone stable and I want to upgrade from 2.1.2, and have some questions. Will 3.2.1 use the same configfiles as 2.1.2 (do I have to rewrite all my configfiles)? Will 3.2.1 use the same filesystem structure as 2.1.2 (can I restor a file backed up with 2.1.2 with 3.2.1)? Are there some gotchas with this upgrade? Regards, -- Dan Johansson, http://www.dmj.nu *** This message is printed on 100% recycled electrons! *** -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Backuppc problem with filenames (Solved)
Hi Jesper, After removing backuppc v3.2.1 and supporting packages and reinstalling the latest versions everything is now working. Thanks for your assistance. Regards, Paul -- Hi Jesper, Thanks again for your response and your test results. This certainly has me baffled. I guess I'll try and re-install backuppc w/version 3.1 and see if that helps. Regards, Paul Hi Paul, Just tested it on one of my BackupPC servers. Now mine is installed on Debian6 x64, and uses the stable backuppc package (3.1.0) from the Debian repositories. Result here: http://public.haggren.com/for_paul/test.png http://public.haggren.com/for_paul/test.png /Jesper On 24-08-2011 21:07, Paul Cain wrote: Hello, This is a follow up post to the original issue. I have done some additonal testing and now it seems that the issue is specifically related to either backuppc or the File::RsyncP module, as these are the two pieces I can not eliminate. I have setup and successfully completed straight rsync file transfer from the winXP box to the Unbuntu (10.04) with no issue. All files transferred with out any changes to the filename. I have scoured the various user forums for any related problems and aside from a few people who had issues relating to European character sets not translating properly (which I have eliminated as a possible solution) there are no issue being reported. It seem sthat I am the only one to create filenames starting with an open parenthesis Is anyone able to test this issue on their system and see if it is indeed common? Regards, Paul -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] first full never completes
On Sat, Sep 3, 2011 at 2:18 AM, hans...@gmail.com wrote: But would probably be a very good idea. What would be an even better idea would be to grab a spare PC (or a virtual guest) and test it from a completely clean installation. And document the *heck* out of what you do: you *will* be doing it again (and again and again). Well the whole thing is a test system, and I'm not that concerned with figuring out what went wrong vs moving forward, so I guess I'll just wipe and restart with a clean OS. Keep in mind that if you get a virtual machine working, you can just keep the copy at the offsite location. I have a Centos image on my windows laptop under vmware player and can connect the disk with a usb-sata adapter cable. Since I want to use the BackupPC 3.1 package (eventual production system will be on CentOS5), while I'm at it I'll use the Ubuntu version it's designed for, Lucid 10.04, rather than the latest Natty 11.04. If you are going to use centos, you might as well use centos in testing, even if you have to do it under vmware. I think the EPEL package was recently updated to 3.2 and I would be able to give better advice with rpm commands. rpm -q --list backuppc # to see where all the files go rpm -q --scripts # view the install scripts rpm -V backuppc # see what has changed since install etc. I'm sure debian/ubuntu has the equivalent or better, but I don't know them. -- Les Mikesell lesmikes...@gmail.com -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] first full never completes
On Sat, Sep 3, 2011 at 7:55 AM, Les Mikesell lesmikes...@gmail.com wrote: On Sat, Sep 3, 2011 at 2:18 AM, hans...@gmail.com wrote: [SNIP] Since I want to use the BackupPC 3.1 package (eventual production system will be on CentOS5), while I'm at it I'll use the Ubuntu version it's designed for, Lucid 10.04, rather than the latest Natty 11.04. If you are going to use centos, you might as well use centos in testing, even if you have to do it under vmware. I think the EPEL package was recently updated to 3.2 and I would be able to give better advice with rpm commands. rpm -q --list backuppc # to see where all the files go rpm -q --scripts # view the install scripts rpm -V backuppc # see what has changed since install etc. I'm sure debian/ubuntu has the equivalent or better, but I don't know them. I just checked and there are builds of 3.2.1 for both EL5 and EL6 but I didn't check if they've made it through to the stable repository. Worst case you can pull them directly from koji[1]. I don't run EL/CentOS/Scientific Linux but I do run Fedora which is more or less equivalent. I used yum to install and the only manual configuration I had to do to get a basic working system was to edit /etc/BackupPC/config.pl to setup the CGI admin user and then setup the password file for apache. That's it. Richard [1] http://koji.fedoraproject.org/koji/buildinfo?buildID=256288 If you don't go through the EL repo then you'll also need to pay attention to the changelog as there are two new perl modules you need to install separately. (perl(Net::FTP::AutoReconnect) and perl(Net::FTP::RetrHandle)). -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] first full never completes
Hi, Les Mikesell wrote on 2011-09-02 16:46:34 -0500 [Re: [BackupPC-users] first full never completes]: On Fri, Sep 2, 2011 at 4:38 PM, hans...@gmail.com wrote: Or is the message link host-name in my log when running _dump -v manually indicate a hardlinkng problem kicking in **after** the pc filesystem's already been created? I think the fact that the link step isn't completing is your real problem, but I still don't know why. If you get that far it should work or tell you why in the logs. just in case this hasn't been cleared up somewhere else in this huge thread: the link host-name message is simply BackupPC_dump's way of telling the BackupPC daemon that BackupPC_link needs to be run for host-name, nothing more. Normally, the daemon starts BackupPC_dump and reads its stdout. If you run BackupPC_dump manually, the message just pops up on your terminal without effect. Just ignore it. Regards, Holger -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] first full never completes
Hi, hans...@gmail.com wrote on 2011-09-03 05:03:30 +0700 [Re: [BackupPC-users] first full never completes]: On Sat, Sep 3, 2011 at 4:38 AM, Les Mikesell lesmikes...@gmail.com wrote: In general, backuppc needs rw permission on everything, and apache (www-data on debian/ubuntu) needs read access to some of it. Sorry to need such hand-holding, I was thinking hand-cuffing. How about *solving* one issue before creating a dozen new ones in the attempt? but if I'm above my TOPDIR and execute chown -R backuppc TOPDIR chgrp -R www-data TOPDIR chmod 644 TOPDIR should that be OK? No. Should I run the start/stop with su backuppc instead? You hopefully won't be able to. Means: no. Regards, Holger -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] first full never completes
Hi, Les Mikesell wrote on 2011-09-03 07:55:29 -0500 [Re: [BackupPC-users] first full never completes]: On Sat, Sep 3, 2011 at 2:18 AM, hans...@gmail.com wrote: Keep in mind that if you get a virtual machine working, [...] and before keeping that in mind, keep in mind to get your system working before raising other issues. Since I want to use the BackupPC 3.1 package (eventual production system will be on CentOS5), while I'm at it I'll use the Ubuntu version it's designed for, Lucid 10.04, rather than the latest Natty 11.04. If you are going to use centos, you might as well use centos in testing, I need to agree with that. You might be hunting down a packaging issue you will never have on the system you are intending to use. On the other hand, you may be missing other packaging issues that you *will* have (not meaning to say there are any bugs in the rpm, just that things can go wrong). So what's the point of testing the installation process if you are going to use a completely different one? I think the EPEL package was recently updated to 3.2 Which may or may not be an advantage. I'm still running BackupPC 2.1.2, and it does exactly what it is supposed to do. The 3.2 package may be better or worse than the 3.1 package. No idea. But, again, you should test what you intend to do later, not something possibly similar. If you plan on using 3.2, then test with that. and I would be able to give better advice with rpm commands. Just as much as I would be able to give better advice with dpkg/apt commands :). I'll get back to that if there is any point. Regards, Holger P.S.: On the bind-mount issue, first of all I agree with the points that have been made on eliminating complexity as long as things are not working for you. Once you know how to *reproducibly* get things running (which *should be* as trivial as installing the package and setting up the necessary configuration, but obviously something is going wrong somewhere), you can move on to the issue of data pool storage. I maintain that bind mounts are absolutely fine to use. They are not the *source* of your problem, though in the process of using them you might have messed something up. They *certainly* will *never* replace soft links, because they don't address the same issue (much like scissors haven't replaced knives). If you ask for my guess, either the package is incorrectly setting things up, or you have somehow messed up your system to a point that the package installation runs incorrectly, or you have incorrectly described what is happening. I can understand that you may be leaving things out that seem unimportant to you. Let's just hope you're right :). -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] first full never completes
Hi, hans...@gmail.com wrote on 2011-09-03 02:10:55 +0700 [Re: [BackupPC-users] first full never completes]: [...] I haven't been able to find in the docs a listing of what the permissions are supposed to be, and as a *nix noob, I may very well have screwed things up in that area messing around. I believe I set everything from TOPDIR down as owned by user backuppc and group www-data. I'd appreciate a pointer to how it's supposed to be, and in the meantime will try a complete uninstall and re-install (moving my conf and pool data elsewhere first) and see how that goes. . . just to try to (finally) give a definite answer to this question: It depends on what policies your BackupPC package has implemented! Personally, I'd find a choice of group www-data ***stupid***, because it gives *any web application* running on the server access to your pool data - possibly including any amount of confidential information. There's a reason for running the BackupPC_admin CGI setuid, and that's precisely avoiding this mistake. The BackupPC CGI interface needs access to the pool, the rest of the web server should *not* be allowed to access it in any way. The Debian packages I know use a private group also name 'backuppc' and permissions g=u,g-w (meaning same as user, but without write permission) and no access for others. Actually, these permissions would allow using a different user for the CGI interface, who can browse the backups but has no write access to the data (though I believe that is not actually done). Concerning anything BackupPC creates itself, if that is not automatically created with correct permissions, you've got a problem anyway. You should *never* need to change permissions or ownership on anything below $TopDir. If you're copying something, copy it correctly. Unless you know *exactly* what you are doing, the permissions (and ownership, and timestamps) are just as much part of the information as the data or the file names. While it's true that you *can* presumably fix things you broke regarding permissions, while you likely *cannot* fix errors in the data, prefer avoiding breaking things in the first place. These points are not specific to BackupPC, they apply as much with any other software's data files. The only thing, I believe, BackupPC will *not* automatically create is $TopDir itself. Again, your package is authoritative on what the permissions should be, and if it gets this wrong, that's a bug. *For sanity checking only*, $TopDir should be writeable for the user BackupPC is running as (i.e. backuppc), readable and searchable for the CGI user (usually also backuppc, but could, in principle, differ) and not accessible for others. Ownership and group may be set up in a number of ways to achieve this, subject to the implementation the package creator has chosen. *Presuming the package creates all needed subdirectories under $TopDir and gives them the correct permissions*, and only then, $TopDir might be left *not* writeable for the BackupPC user, though I'm not sure what the point in this would be. Apparently, but this is only a wild guess, the Ubuntu package chooses the latter option, but incorrectly determines when and how to create the subdirectories (seems to skip this on reinstallation, even though they don't exist or have wrong permissions). If this is true, it is a bug in the Ubuntu package and should be reported to the appropriate BTS. Assuming you still want to proceed with the Ubuntu package, it *might* help to *purge* the package (dpkg --purge backuppc) before re-installing it, but it really depends on *how* the package comes up with the idea that it was previously installed. Again, you probably shouldn't be testing with Ubuntu if you are interested in the CentOS installation procedure. Regards, Holger -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] cannot get backuppc to wol a client
I have worked on this issue in the past for myself. Never really got it
completed. However, your email has me interested again and this is good
weekend to work on this.
So, last night I Googled BackupPC wol got some more info.
This is the article that started me off last January:
http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/backuppc-21/wol-how-it-works-for-me-74879/
This writing was initially a little robust for my needs, however he
brings up some very good ideas.
This article is from Ubunut-fr (France) and needed to be translated by
Google:
http://doc.ubuntu-fr.org/backuppc
It relates to Windows pc's, should that be what you need.
I, personally, am trying to wake and backup Ubuntu machines. I cannot
say if it works with other distros, but I don't see why it would not.
My next step is to move my wake-on-lan scripts over to my BackupPC
machine (the scripts are working on my desktop to wake my test machine.)
I'll continue now my testing and keep you posted as I go.
Robert Wooden
Nashville, TN. USA
Computer Freedom? . . . Linux
On 09/02/2011 01:18 PM, Tim Fletcher wrote:
On Fri, 2011-09-02 at 00:34 -0700, egrimisu wrote:
Hi guys,
backuppc won't wol client pc
NmbLookupFindHostCmd = /etc/backuppc/wakeup.sh 00:1a:4d:8c:0a:78 1 $host
wakeup.sh has 777 rights and contains:
#!/bin/bash
wakeonlan $1
sleep ${2}m
/usr/bin/nmblookup $3
using the dos command wolcmd.exe 001a4d8c0a78 192.168.2.74 255.255.255.0
wakes the pc up.
Sending the WoL packets need root (admin in the windows world)
privileges so you will need to make setup sudo to allow the backuppc
user to run wakeonlan as root or you need to setuid the wakeonlan
binary. (bad idea)
--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] cannot get backuppc to wol a client
On Sat, 2011-09-03 at 16:09 -0500, Robert E. Wooden wrote:
I have worked on this issue in the past for myself. Never really got it
completed. However, your email has me interested again and this is good
weekend to work on this.
I've had it working for a year or so with the following setup:
In the file /etc/sudoers add the following lines:
Cmnd_Alias WOL = /usr/bin/wakeonlan,/usr/sbin/etherwake
backuppc ALL=(root) NOPASSWD:WOL
And change the pingcmd for the hosts to the following line:
$Conf{PingCmd} = '/usr/local/bin/wakeup.sh $host';
I've also attached a slightly edited version of the script I use to fire
off the WoL packets.
--
Tim Fletcher t...@night-shade.org.uk
wakeup.sh
Description: application/shellscript
--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Backing up slash partition
Hi, Arnold Krille wrote on 2011-09-03 01:32:15 +0200 [Re: [BackupPC-users] Backing up slash partition]: On Saturday 03 September 2011 00:57:48 Timothy Murphy wrote: Can one sensibly back up / with BackupPC? the confusing thing about that question is that it is probably not what you want to ask. Yes, you *can* back up your file systems from the root, though you will *need* to exclude some things. No, bare metal recovery is not a feature of BackupPC. The result you get is the same as if you would hard power-off your machine and restart it. Or take out one drive in your raid1 while its running. Well, no. Firstly, you don't get a snapshot, unless you actually back up a snapshot, i.e. your hard power-off will have occurred at different points in time for different parts of your file systems - maybe even spread out across several hours. It will likely be inconsistent. That is usually not that much of a problem (maybe because nobody does it), but you *should* consider whether it is in your case. Secondly, while you do get an image of your system, you need to think about what you would want to do with it. You can't press a button and get a disk as result that you can insert into a replacement machine. At the *very least*, you will need to set up partitioning the target disk, creating the file system(s), and boot loading. All of this is information that is stored on your disk, but outside the file systems. Additionally, your system will be configured for the hardware it was running on. Your replacement may or may not have different requirements. For example, it's very likely that udev will name your network interfaces differently, which can be a major nuisance. Chances are, you will find it easier to reinstall a system from original source media and then restore meaningful data and configuration from your backups. If so, there's not much point in backing up all the binaries (and, say, your WWW proxy's cache). You might say, if I backup everything, it won't turn out that I forgot something. True, but you might also find that it has some merit to be aware which of your data is valuable and which isn't. You should make sure you don't cross mount-points though. Otherwise the backup of localhosts '/' will recurse into itself. How that? Les Mikesell wrote on 2011-09-02 18:36:11 -0500 [Re: [BackupPC-users] Backing up slash partition]: On Fri, Sep 2, 2011 at 5:57 PM, Timothy Murphy gayle...@eircom.net wrote: Can one sensibly back up / with BackupPC? Sure, but if you don't use --one-file-system in the options, be sure to exclude the pseudo mounts like /proc, /sys (and maybe /dev, depending on the version). To elaborate, you *need* to exclude /proc (and possibly /sys), else your backup will probably not complete. In the very least, it will contain large amounts of meaningless data (like your kernel core image). Regardless of the version, backing up /dev seems to be pointless. Unless it is both static (does *anyone* still use a static /dev?) and you *really* plan to recover your machine from the backup. What I'd further recommend excluding is /tmp and /media (or whatever your system automatically mounts removable media to). It's always difficult to anticipate everything that might cause problems. This is the real downside of a backup everything except ... approach. Another point to consider would be database files, which generally don't handle non-snapshot image level backups particularly well. You might need additional steps (like dumping the database from a DumpPreUserCmd) if you have software like databases running. So, my answer to your question is, yes, but I wouldn't recommend it. Regards, Holger -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] cannot get backuppc to wol a client
Well, your development on this is way over my head but, I sure do like
your wakeup script.
In my case, I worked on this last January or so and forgot where I left
off. I am embarrassed to say that I cannot find my notes from then and
so I do not know want other related commands (within BackupPC) that I
may have changed. I am sitting here scratching my head, deciding how to
proceed.
Robert Wooden
Nashville, TN. USA
Computer Freedom? . . . Linux
On 09/03/2011 04:33 PM, Tim Fletcher wrote:
On Sat, 2011-09-03 at 16:09 -0500, Robert E. Wooden wrote:
I have worked on this issue in the past for myself. Never really got it
completed. However, your email has me interested again and this is good
weekend to work on this.
I've had it working for a year or so with the following setup:
In the file /etc/sudoers add the following lines:
Cmnd_Alias WOL = /usr/bin/wakeonlan,/usr/sbin/etherwake
backuppc ALL=(root) NOPASSWD:WOL
And change the pingcmd for the hosts to the following line:
$Conf{PingCmd} = '/usr/local/bin/wakeup.sh $host';
I've also attached a slightly edited version of the script I use to fire
off the WoL packets.
--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] cannot get backuppc to wol a client
Tim, what OS is your BackupPC running on?
Robert Wooden
Nashville, TN. USA
Computer Freedom? . . . Linux
On 09/03/2011 04:33 PM, Tim Fletcher wrote:
On Sat, 2011-09-03 at 16:09 -0500, Robert E. Wooden wrote:
I have worked on this issue in the past for myself. Never really got it
completed. However, your email has me interested again and this is good
weekend to work on this.
I've had it working for a year or so with the following setup:
In the file /etc/sudoers add the following lines:
Cmnd_Alias WOL = /usr/bin/wakeonlan,/usr/sbin/etherwake
backuppc ALL=(root) NOPASSWD:WOL
And change the pingcmd for the hosts to the following line:
$Conf{PingCmd} = '/usr/local/bin/wakeup.sh $host';
I've also attached a slightly edited version of the script I use to fire
off the WoL packets.
--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Upgrade BackupPC 2.1.2 to 3.2.1
Hi,
Dan Johansson wrote on 2011-09-03 11:04:22 +0200 [[BackupPC-users] Upgrade
BackupPC 2.1.2 to 3.2.1]:
In Gentoo BackupPC 3.2.1 has just gone stable and I want to upgrade from
2.1.2, and have some questions.
Will 3.2.1 use the same configfiles as 2.1.2 (do I have to rewrite all my
configfiles)?
yes (no). Though there are some new variables in config.pl, so you might want
or need to merge your local changes into the new config.pl.
Will 3.2.1 use the same filesystem structure as 2.1.2 (can I restor a file
backed up with 2.1.2 with 3.2.1)?
Yes (yes).
Are there some gotchas with this upgrade?
In general, if you've installed a distribution package of BackupPC, it's up to
the package to handle upgrades (you *did* previously install version 2.1.2
from a package, too, right?).
As far as the upstream BackupPC code is concerned, there should be no issues
with the upgrade. For the Gentoo package, I have no idea. In theory, it
*could* introduce problems (like moving the pool location; however, with 3.2.1
you could just set $Conf{TopDir} in config.pl to work around that). If you
want a definite answer, you'll have to ask in a Gentoo forum (or, of course,
read the source ;-).
Regards,
Holger
--
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free Love Thy Logs t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Backing up slash partition
Hi, On Sunday 04 September 2011 00:08:38 Holger Parplies wrote: Arnold Krille wrote on 2011-09-03 01:32:15 +0200 [Re: [BackupPC-users] Backing up slash partition]: On Saturday 03 September 2011 00:57:48 Timothy Murphy wrote: You should make sure you don't cross mount-points though. Otherwise the backup of localhosts '/' will recurse into itself. How that? Backing up / (including /var/lib/backuppc/pc) into /var/lib/backuppc/pc/localhost. Unless you exclude that dir by excludes or -- one-filesystem (given that dir is on another partition) this results in a recursion. Have fun, Arnold signature.asc Description: This is a digitally signed message part. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Linux backups with rsync vs tar
Hi,
Timothy J Massey wrote on 2011-09-02 10:43:37 -0400 [Re: [BackupPC-users] Linux
backups with rsync vs tar]:
charlesboyo backuppc-fo...@backupcentral.com wrote on 08/31/2011 05:53:43
AM:
[...]
Thus I have reason to suspect the rsync overhead as being guilty.
for the record, I've just (finally!) switched from tar to rsync for a data
server, and this significantly increased run times of backups. Incremental
backups are taking about three times as long as they used to (if memory
serves correctly). So, yes, rsync does have a significant overhead. That is
not surprising.
I should add that in my case the server is backing up local file systems (to
an iSCSI disk). The effect should be less significant if client and server are
not the same machine (though it is a quad-core and the disk sets are
independent).
Note that I have disabled hard links,
???
What is that supposed to mean? You removed the rsync -H option?
When you're talking about the pool, disabling hard links sounds rather
troubling ;-).
implemented checksum caching,
increased the block size to 512 KB and enable --whole-file to no avail.
I don't think File::RsyncP supports changing block size (and probably not
--whole-file either).
1. since over 90% of the files change every day and incremental
backups involve transferring the whole file to the BackupPC server,
won't it make better sense to just run a full backup everyday?
There is probably not much difference either way.
[...]
You may find that trading CPU performance for network performance may not
be a good trade in your case.
That is true, but there are other reasons for using rsync rather than tar.
Exactness of backups. tar incrementals don't reflect deleted files, for
instance. Though, in *this* specific case that may not make much difference
(presuming I'm correct in assuming your mbox files are never deleted or
renamed, extracted from tar-/zip-files, etc., or at least that missing such
a change until the next full backup is unproblematic).
The number one question I have is: is this really a problem? If you have
a backup window that allows this, I would not worry about it. If you do
*not*, then rsync might not be for you.
That's exactly the point. In my case, it is *not* a problem, so I prefer more
accurate backups, even if the fulls take all of the night. Thank you for
reminding me to shift the full run to the weekend, which I'll do right now :-).
2) Les' point about the format of the files (one monolithic file for each
mailbox vs. one file per e-mail) is dead on. That allows 99% of the files
to remain untouched once they're backed up *once*. That will *vastly*
reduce the backup times.
... and pool storage requirements, and rsync will handle small files much
better. Sadly enough, there is still enough braindead software around that
doesn't support maildir format, even in the Unix world. Open Source probably
means that I should start hacking the $#@%volution sources ...
2. from Pavel's questions, he observed that BackupPC is unable to
recover from interrupted tar transfer. Such interruptions simply
cannot happen in my case. Should I switch to tar?
Your situation is completely different from his - you're on a local network,
aren't you? You don't need the bandwidth reductions you gain from rsync - tar
should work fine for you.
*But* you should consider whether (incremental) tar backups will be
sufficiently accurate. Since you are transferring almost everything anyway,
you could even run only full tar backups.
For the sake of completeness, I should mention that full backups always
rebuild the entire tree (in BackupPC storage). In the general case, this
can raise storage requirements (for directory entries and duplicates due to
exceeding HardLinkMax), but in your case I wouldn't expect much difference.
However, with tar, backup exactness would benefit.
And in the
unlikely event that the transferred does get interrupted, what
mechanisms do I need to implement to resume/recover from the failure?
To repeat another response: restart the backup...
To extend on that: BackupPC does that automatically at the next wakeup, so you
don't really need to do anything (except from having a reasonable
WakeupSchedule).
3. What is the recommended process for switching from rsync to tar -
Change $Conf{XferMethod} to 'tar' :-). Add/rename the other settings as
needed.
since the format/attributes are reportedly incompatible?
They're only slightly different. The only problem is that when switching
*from tar to rsync* (which you're not doing), rsync will re-transfer
everything, because it appears to have changed from unknown file type to
plain file. The only time this is really important is when you import a
local clone of a remote file system via tar XferMethod, meaning to save you
the bandwidth of the first full rsync. That won't work (without patching the
attrib files ;-). Pooling is just fine, though. And tar doesn't base any
Re: [BackupPC-users] Backing up slash partition
Hi, Arnold Krille wrote on 2011-09-04 01:11:12 +0200 [Re: [BackupPC-users] Backing up slash partition]: On Sunday 04 September 2011 00:08:38 Holger Parplies wrote: Arnold Krille wrote on 2011-09-03 01:32:15 +0200 [Re: [BackupPC-users] Backing up slash partition]: You should make sure you don't cross mount-points though. Otherwise the backup of localhosts '/' will recurse into itself. How that? Backing up / (including /var/lib/backuppc/pc) into /var/lib/backuppc/pc/localhost. Unless you exclude that dir by excludes or -- one-filesystem (given that dir is on another partition) this results in a recursion. that only happens in the unusual case of backing up the BackupPC server itself (where backing up everything from / is a particularly bad idea). And the real problem is not the recursion - excluding /var/lib/backuppc/pc/localhost/new would eliminate that - it's backing up the pool as data into itself. Either you've got the pool, then you don't need a backup of it, or you haven't, then you also haven't got the backup. In a way, that's an implementation of write-only memory, and a practical demonstration why exponential growth isn't sustainable. Hope that helps. Regards, Holger -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] first full never completes
hans...@gmail.com wrote at about 14:18:41 +0700 on Saturday, September 3, 2011: On Sat, Sep 3, 2011 at 11:09 AM, Timothy J Massey tmas...@obscorp.comwrote: But would probably be a very good idea. What would be an even better idea would be to grab a spare PC (or a virtual guest) and test it from a completely clean installation. And document the *heck* out of what you do: you *will* be doing it again (and again and again). Well the whole thing is a test system, and I'm not that concerned with figuring out what went wrong vs moving forward, so I guess I'll just wipe and restart with a clean OS. Since I want to use the BackupPC 3.1 package (eventual production system will be on CentOS5), while I'm at it I'll use the Ubuntu version it's designed for, Lucid 10.04, rather than the latest Natty 11.04. Hopefully will eliminate the problems I'm seeing un/re- installing from the package system. I plan to keep the pool folders and of course my long-tweaked config.pl, but will start off from the clean install with as close to defaults as possible with a small static target share to test with, then make the changes a little at a time only after I've got the basics working right. Which as you say I should've done from the start. . . In the meantime there are a few unanswered questions in the thread above if anyone has the information to ontribute more detailed responses I'm sure it will help others googling later on. . . Just a piece of friendly advice... you seem to have posted dozens of posts in the past 24 hours or so... you keep making multiple, often non-standard or nonsensical changes to a standard configuration... and are asking multiple questions as you dig yourself deeper. Why don't you pursue this in a rational and organized approach? Get the basic system working with no modifications. Verify that it works, play with it, and get comfortable with the default setup and behaviors. Then step-by-step make one change at a time. If the change works as expected, then move on to the next change. If it doesn't then you know the exact source of the problem and can either troubleshoot it yourself (ideal) or ask a specific question to the list. What you are doing now is confusing yourself and probably most of the readers of the list. Pretty soon people will get tired of answering you or will lose track of all the questions and changes you have made meaning that they won't be around to help you when you really need it. Thanks -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] first full never completes
On Sun, Sep 4, 2011 at 10:49 AM, Jeffrey J. Kosowsky backu...@kosowsky.orgwrote: Just a piece of friendly advice... you seem to have posted dozens of posts in the past 24 hours or so... you keep making multiple, often non-standard or nonsensical changes to a standard configuration... and are asking multiple questions as you dig yourself deeper. Thanks very Jeffrey, and to everyone, both for specific answers to my questions and for your valuable general advice and feedback. About my messing things up by my lack of *nix knowledge and making things too complicated, you're completely right and I apologize for wasting your time with my scattered approach to the learning curve. Re packaging issues, I'm not trying to figure them out at all, AFAIC they're a black box that just works - I plan to just observe their results and stick to their policies (I didn't realize BPC permissions could vary from one distro to another). If necessary, I will now be able to just roll back to a virgin state via CloneZilla, rather than un-installing. Re OS choices, I don't have the access, knowledge or desire to do my initial learning/experimentation in the production CentOS CLI environment; for many aspects it's so much easier to work with a distro like Ubuntu at this stage. Once I'm confident I've got the BPC side of things working just right, the CentOS guy can set up the production server however he likes. My ultimate goal is to have a self-contained BackupPC HDD - conf and log physically under TOPDIR - which in the event of a disaster can be mounted to a new host running an arbitrary distro, possibly needing to be created by a staffer even more ignorant of Linux than myself supported by a step-by-step howto. Ideally I'd like to figure out how to create a customized BackupPC LiveCD that could be stored with the drive(s) offsite. These goals also support my doing the learning/configuration work on an alternative distro. But for now, I am starting from scratch with 3.1 on Lucid, working step by step in departing from the defaults, testing and keeping careful notes in case I need to come back here with further issues, so as not to waste you guys' time further. Thanks again for your help. -- Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free Love Thy Logs t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
