Hi
I have just installed BackupPC. It is great I am using samba and have just
tried rsyncd.
I want to be able to specify a host which is accessed over the internet. I get
"ping too slow" errors.
BackupPC 2.1.2;
$Conf{BlackoutBadPingLimit} = 3;
$Conf{BlackoutGoodCnt} = -7;
Regards
Chris

Les Mikesell writes:
> On Fri, 2006-01-20 at 16:44, Dan Pritts wrote:
> > On Fri, Jan 20, 2006 at 03:53:33PM -0600, Les Mikesell wrote:
> > >
> > > I'd expect to see quite a lot of temp file activity that would
> > > result in changes to unused space on the live system. It would
> >
> > Yeah, you're right - i think of this as all being rsync based
> > but it sort of is and sort of isn't. Files get transferred
> > to the store disk and then get pooled, rather than using
> > rsync --link-dest.
>
> Even a normal rsync transfer of anything with changes builds
> a new copy of the file and replaces the old only when the
> new temp copy is complete. Hmmm... I guess that means the
> partition image scheme needs disk space for a 2nd copy
> of the file at the remote side.
Rsync's --inplace option solves this issue: it doesn't use a
temp file. The restriction this imposes is that no blocks will
be matched earlier in the file, since with --inplace the earlier
blocks might already be changed. Also, --inplace will of course
leave the target in an undefined state if the transfer is
interrupted.
For a partition sync the matching limitation wouldn't be
significant since most matching blocks will be at the same
offset.
The notion of using rsync on the raw device is intriguing,
provided they are offline or are a frozen snapshot.
Craig

Hi Justin,
Because of the line in smb.conf that says
winbind use default domain = yes
your users can log in with just their user names. This works for me,
and I'm surprised it doesn't seem to work for you. Just to be sure,
check that the line is present in smb.conf. It seems to be, since
getent returns your groups and users without the DOMAIN prefix.
To get the e-mail link properly set up, list your users in hosts file
with their plain login name (i.e. without the DOMAIN\ part). Then, set
$Conf{CgiUserUrlCreate} = 'mailto:%s@...';
Of course this assumes that your users can login using their username
without the DOMAIN part.
Cheers.
Muyiwa

Hello Justin,
1. An ADS domain group is fine. You don't need local Linux groups, so
revert to
$Conf{CgiAdminUserGroup} = 'backuppcadmins';
in your config.pl file, but note that you have a space in your own
setting, which shouldn't be there.
2. I was tempted to say that you hadn't included the line:
winbind use default domain = yes
in your smb.conf file. You do have it, and also when you do:
bs-pc115:~# getent group | grep backuppcadmins,
you get the correct response. So, winbind is correctly stripping the
domain information off the beginning of the Active Directory user ID's.
You'll also notice that the usernames returned by your getent command
are all lowercase, and therefore, when you use them on the Linux box
(i.e. Winbind+Apache+PAM), they must be typed in lowercase. In your
case, you must type "administrator", and NOT "Administrator"
3. Your REMOTE_USER environment variable is listed as
*PDXMISSION\Administrator. *My guess is that this is what you're typing
in the login box to access BackupPC's web interface. Again, as I've
said above, you must type "administrator", or "justinb", since he's also
in the backuppcadmins group. Lose the "PDXMISSION".
4. In your config.pl file, the setting
$Conf{CgiAdminUserGroup} = ' backuppcadmins';
has a space in front of the word backuppcadmins. My guess is that
BackupPC is looking for a Linux group called
' backuppcadmins', i.e., with a space (which doesn't exist - what exists
is 'backuppcadmins', without the space :-) )
5. I SUGGEST THAT YOU:
a. Take out the space in front of ' backuppcadmins' in your
$Conf{CgiAdminUserGroup}
b. Restart BackupPC, Apache, and Winbind
c. Login to the CGI interface using just "administrator" or
"justinb", i.e. no "PDXMISSION"
Try this and let me know how you get on.
Cheers,
Muyiwa

On Fri, Jan 20, 2006 at 04:49:50PM -0600, Les Mikesell wrote:
> Even a normal rsync transfer of anything with changes builds
> a new copy of the file and replaces the old only when the
> new temp copy is complete. Hmmm... I guess that means the
> partition image scheme needs disk space for a 2nd copy
> of the file at the remote side.
unless you use this rsync option:
--inplace update the destination files inplace
danno

Hi, all,
I recently reinstalled BackupPC on a new backup server, and it's running
well (backing up over 1 TB of data daily/weekly). That is, except for some
errors for one of the backed up client partitions. Here is an extract of
the XferLOG (things in angle brackets are my own munging; the f<1>/f<2>...
sequence corresponds to <long_path_...>):
[...]
create d 775 3864/112 880 <long_path_below_backed_up_dir>
same 664 3864/112 12
<long_path_below_backed_up_dir>/6304166_1.txt
pool l 777 3864/112 97
<long_path_below_backed_up_dir>/6304166_1.wa
same 664 3864/112 12
<long_path_below_backed_up_dir>/6304229_1.txt
pool l 777 3864/112 97
<long_path_below_backed_up_dir>/6304229_1.wa
same 664 3864/112 12
<long_path_below_backed_up_dir>/6304491_1.txt
pool l 777 3864/112 97
<long_path_below_backed_up_dir>/6304491_1.wa
same 664 3864/112 12
<long_path_below_backed_up_dir>/6304672_1.txt
pool l 777 3864/112 97
<long_path_below_backed_up_dir>/6304672_1.wa
same 664 3864/112 12
<long_path_below_backed_up_dir>/6304847_1.txt
Unable to link
/backup/BackupPC/pc/burdata01lx_home/3/f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6304847_1.txt
to
/backup/BackupPC/pc/burdata01lx_home/new//f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6304847_1.txt
pool l 777 3864/112 97
<long_path_below_backed_up_dir>/6304847_1.wa
same 664 3864/112 12
<long_path_below_backed_up_dir>/6305204_1.txt
Unable to link
/backup/BackupPC/pc/burdata01lx_home/3/f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6305204_1.txt
to
/backup/BackupPC/pc/burdata01lx_home/new//f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6305204_1.txt
pool l 777 3864/112 97
<long_path_below_backed_up_dir>/6305204_1.wa
same 664 3864/112 12
<long_path_below_backed_up_dir>/6305239_1.txt
Unable to link
/backup/BackupPC/pc/burdata01lx_home/3/f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6305239_1.txt
to
/backup/BackupPC/pc/burdata01lx_home/new//f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6305239_1.txt
pool l 777 3864/112 97
<long_path_below_backed_up_dir>/6305239_1.wa
same 664 3864/112 12
<long_path_below_backed_up_dir>/6305623_1.txt
Unable to link
/backup/BackupPC/pc/burdata01lx_home/3/f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6305623_1.txt
to
/backup/BackupPC/pc/burdata01lx_home/new//f%2fhome_snapshot/f<1>/f<2>/f<3>/f<4>/f<5>/f<6>/f<7>/f<8>/f6305623_1.txt
pool l 777 3864/112 97
<long_path_below_backed_up_dir>/6305623_1.wa
[...]
Indeed, those files that were not linked are not in the BackupPC data
directory and aren't available for restore on the CGI interface. It looks
like BackupPC is trying to make a link from the previous full (3) to the
new one. I've verified that the file in the previous full exists. The only
notable thing I see is perhaps an excess of forward slashes, literal in the
"new//" (but this shouldn't really matter...), and a URL-mangled one (%2f).
All the other partitions are backed up without errors, and as you can see,
not all files in the same directory present this error... So I'm stumped.
Has anyone seen this before?
Bernardo Rechea