BackupPC-users

Re: [BackupPC-users] Noted Observations & Complaints Using BackupPC for 5 mon

2010-04-23 08:56:46
Subject: Re: [BackupPC-users] Noted Observations & Complaints Using BackupPC for 5 mon
From: Les Mikesell <lesmikesell AT gmail DOT com>
To: backuppc-users AT lists.sourceforge DOT net
Date: Fri, 23 Apr 2010 07:54:24 -0500
Saturn2888 wrote:
> @Les Mikesell
> That makes sense then why RAID5 is bad for this.
> 
> Now you know my trouble with Samba. Sure, if I can read the files they should 
> be there, but they're not. This is why I stopped using Samba. It's like 
> BackupPC get tired when using Samba and quits when it feels like it because.

Rsync does do a better job on incrementals.  The samba/tar methods simply go by 
the file timestamps so if you move files in ways that preserve old timestamps 
create them by unpacking a zip, etc., they won't be picked up in an incremental 
run - and they don't note deletions.  Rsync/rsyncd compares directories and 
will 
catch these changes.  Samba should have had everything it could read on the 
full 
runs, though.

> I had the original volume / on /dev/md1 and /boot on /dev/md0. I dd'd 
> /dev/md1 to /dev/sda1 then copied the files for /boot from a mounted /dev/md0 
> using cp. I reinstalled GRUB2 and got the machine to boot. From there I 
> started the machine, all my files were intact and things appeared to work yet 
> I noticed my graphs had large unfilling holes in them and my compressed pool 
> information is not there.

The device name doesn't matter - it is the mount point - and if you only have 
one drive I guess it hasn't changed.   You'd be better off with the backuppc 
volume on a separate drive so the head never has to seek anywhere else - it is 
busy enough anyway.   But, it has to be mounted or symlinked into the point 
where it is now, and it has to be the top of the tree containing both the 
pool/cpool and pc directories, probably /var/lib/backuppc if you installed from 
a distribution packaged version.


> @Tyler J. Wagner
> I tried using Rsync on a Linux box, and it gave me some error about not being 
> able to read 4 bytes. I'm assuming the user BackupPC is not configured to 
> login as root on the machine I'm trying to backup.

Yes that is nearly always an ssh problem.  After the keys are set up correctly, 
you need to log in once manually as a test and to answer the one-time prompt 
about connecting to a new machine.  You don't need to do a keygen on the remote 
machines and it can be configured to permit root ssh with keys even when you 
can't log in with a password - but others have posted ways to connect as 
another 
user and run sudo as part of the command.

> What do you use for backing up localhost? I have Rsyncd setup, but I can use 
> some other method like Rsync if needed. I remember the default being tar, but 
> I remember hearing many times Rsync being a superior method of backup.

You can connect to localhost with ssh just like anything else but there is some 
unnecessary overhead.   If you don't, you need to change the commands from the 
defaults because there will be one less level of shell parsing.

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com


------------------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

<Prev in Thread] Current Thread [Next in Thread>