Re: [BackupPC-users] DHCP backups - only once possible

[Craig Barratt via BackupPC-users]

Jean-Marc,

Thanks for the additional information.  Yes, it's a bug.  Here's a patch
that should fix it.

Craig

--- bin/BackupPC 2018-10-22 19:03:33.327873033 -0700
+++ bin/BackupPC 2018-10-26 09:18:50.178239319 -0700
@@ -1803,7 +1803,7 @@
 if ( defined($Status->{$host}{backoffTime})
   && $Status->{$host}{backoffTime} < time );
 return 1 if ( $BgQueueOn{$host} || $UserQueueOn{$host} );
-if ( $Hosts->{$host}{dhcp} ) {
+if ( defined($Hosts->{$host}) && $Hosts->{$host}{dhcp} ) {
 $Status->{$host}{dhcpCheckCnt}++;
 if ( $RunNightlyWhenIdle ) {
 #


On Fri, Oct 26, 2018 at 1:17 AM Jean-Marc  wrote:

> Hello Craig,
>
> Thanks for your help.
>
> Le 26/10/2018 à 07:05, Craig Barratt via BackupPC-users a écrit :
> > Does "nmblookup HOSTNAME" return the correct IP address for that
> > host?  See comments for the $Conf{NmbLookupFindHostCmd} option for
> > arguments you might need to add.
> My clients are in another subnet. I can't ping "name" nor nmblook "name"
> or nmblookup -B "broadcast"
> >
> > If so, then its IP address should be discovered correctly without the
> > dhcp flag.  (In almost all cases it's not necessary to use the dhcp
> flag.)
> >
> I'm afraid i'm in this special case, i need to use dhcp discovery loop.
>
> btw, dhcp flag works as intended, but only in the first wake up loop
> after service start.
>
> Like i said earlier, i suspect a sort of corruption of $host array by
> dhcp datas.
>
> Something like this :
>
> 1st QueueAllPC after service start :
>
> {
>
>  $host loop is clean and run only with non-dhcp flags clients,
> adding tasks to @BGQueue;
>
>   $dhcp loop run and adds BackupPC_dump -d (ip address) to @BGQueue;
>
>  something fills $host with dhcp flagged clients ?
>
> }
>
>
> Others QueueAllPC :
>
> {
>
>  $host loop is perhaps corrupted and adds _all_ clients, including
> dhcp ones, adding tasks BackupPC_dump (ip address) to @BGQueue;
>
>   $dhcp loop run and adds BackupPC_dump -d (ip address) to @BGQueue,
> but create duplicates jobs of $host loop who are canceled later in
> @BGQueue processing loop;
>
>}
>
>
> I mostly understand perl code, but i need to dump $host array to log
> between the two loops and dont know how to print full $host array to LOG
> (or elsewhere) to be sure there is a bug. (will try print
> join("\n",$host),"\n";   monday)
>
> I think it's essential to note that dhcp backup is ok if QueueAllPC
> loops are switched ($dhcp loop first, then $host loop), except if there
> is an ip address in machines list who's part of dhcp range. (problem
> inverted, jobs in the first loop deny duplicates in the second loop)
>
> I suspect a bug in dhcp stuff.
>
> Thanks
>
> JM
>
>
>
> ___
> 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 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] DHCP backups - only once possible

[Craig Barratt via BackupPC-users]

JM,

Does "nmblookup HOSTNAME" return the correct IP address for that host?  See
comments for the $Conf{NmbLookupFindHostCmd} option for arguments you might
need to add.

If so, then its IP address should be discovered correctly without the dhcp
flag.  (In almost all cases it's not necessary to use the dhcp flag.)

Craig

On Thu, Oct 25, 2018 at 8:29 AM Jean-Marc  wrote:

> Hi,
>
> After digging and debugging, it seems to exist a tricky bug.
>
> I changed the *QueueAllPC* , basically switching the 2 loops.
>
> *foreach my $dhcp (...) { ... } *first, then
>
> *foreach my $host (...) { ... } *after
>
> dhcp backups works fine now, but can't use fixed ip if in the dhcp range.
> (i prefer this behavior)
>
> (just use netbios name with dhcp parameter = 1 is fine)
>
> I guess that first wake up (wrongly ?) fill an array ($host ?) with dhcp
> range ip and deny other runs to complete succesfully (debug needed between
> the 2 loops ? what's in $host ? Wich sub fill $host array after/during
> first backup ?)
>
> Thanks for help
>
> ___
> 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 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] Weird backup commands

[Craig Barratt via BackupPC-users]

Jaime,

The first example is an incremental backup (the -N option to smbclient
tarmode), and the second is a full.

What are your settings for
$Conf{SmbClientFullCmd}, $Conf{SmbShareName}, $Conf{BackupFilesOnly} and
$Conf{BackupFilesExclude} on the two machines?

Also, have you consider running rsync instead?  While it requires a
client-side installation, its performance is higher and the include/exclude
logic is clearer and more flexible.

Craig

On Tue, Oct 23, 2018 at 4:32 PM Jaime Fenton 
wrote:

> Hi there,
>
>
>
> With Craig Barratt’s help, I’ve discovered that some of my backups are
> adding in a wildcard instead of the users name as part of the string:
>
>
>
> · Good example: Running: /usr/bin/smbclient
> computername.domainname\\C\$ -U AL\\backuppc -E -d 1 -c tarmode\ full
> -TcN /data/backuppc/pc/ computername.domainname /timeStamp.level0 -
> Users\\username\\AppData Users\\ username \\Documents Users\\ username
> \\Downloads Users\\ username \\My\ Documents Users\\ username \\Desktop
>
> · Error example: Running: /usr/bin/smbclient 
> computername.domainname \\C\$ -U AL\\backuppc -E -d 1 -c tarmode\ full
> -Tc - Users\\\*\\AppData\\\* Users\\\*\\Documents\\\*
> Users\\\*\\Downloads\\\* Users\\\*\\Desktop\\\* Users\\\*\\My\ Documents\\\*
>
>
>
> This does not appear to be ALL the problems I’m facing with backups not
> working, but it’s certainly the major issue that’s preventing me from
> moving forward. Has anyone else see this behaviour?
>
>
>
> Thanks,
>
> Jaime
> --
> Jaime Fenton
> Support Engineer
>
> T: +1 604 398 4800 (main)
> D: +1 604 398 4813 (direct)
> E: jaime.fen...@animallogic.ca
>
> 840 Cambie Street
> Vancouver, BC V6B 2P6
> CANADA
>
>
>   [image: LinkedIn]   [image:
> Facebook]   [image:
> Twitter]   [image: Instagram]
> 
>
> [image: Animal Logic] 
>
> www.animallogic.com
>
> *CONFIDENTIALITY AND PRIVILEGE NOTICE*
> This email is intended only to be read or used by the addressee. It is
> confidential and may contain privileged information. If you are not the
> intended recipient, any use, distribution, disclosure or copying of this
> email is strictly prohibited. Confidentiality and legal privilege attached
> to this communication are not waived or lost by reason of the mistaken
> delivery to you. If you have received this email in error, please delete it
> and notify us immediately by telephone or email.
> ___
> 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 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] v4 migration experiences

[Craig Barratt via BackupPC-users]

Michael,

Thanks for the feedback.

On (1) I pushed a change

so that the Xfer timeout is started after backup expiry, duplication and
refcounting.

On (2), perhaps it should ignore a partial or active backup (which will
have the most recent timestamp), and report just the most recent incr or
full (ie, completed) backup?  I pasted a diff that should do the trick if
you want to try it out (warning - untested).

On (3), I pushed a change

so that the status reporting is more accurate.

Craig

--- lib/BackupPC/CGI/Summary.pm 2018-03-10 16:38:37.195549979 -0800
+++ lib/BackupPC/CGI/Summary.pm 2018-10-22 20:52:50.573850716 -0700
@@ -27,7 +27,7 @@
 #
 #
 #
-# Version 4.2.0, released 18 Feb 2018.
+# Version 4.2.2, released 21 Oct 2018.
 #
 # See http://backuppc.sourceforge.net.
 #
@@ -70,7 +70,7 @@
 $fullDur  = $Backups[$i]{endTime} -
$Backups[$i]{startTime};
 }
 $fullSizeTot += $Backups[$i]{size} / (1024 * 1024);
-} else {
+} elsif ( $Backups[$i]{type} eq "incr" ) {
 $incrCnt++;
 if ( $incrAge < 0 || $Backups[$i]{startTime} > $incrAge ) {
 $incrAge = $Backups[$i]{startTime};


On Thu, Aug 30, 2018 at 3:22 AM Michael Selway  wrote:

> Hi,
> I've recently upgraded from BackupPC v3.3.1 to v4.2.1 on a CentOS 7
> machine using hobbes1069's excellent COPR v4 package.  While the
> experience is fresh in my mind, I have some observations to share.
>
> 1) It has taken around 4 weeks for the v4 system to complete the first
> round of backups - the great bulk of that time is spent in v3->v4
> copying during the first v4 backup.  Right at the end of some of these
> first v4 backups, the backup is flagged as having failed.  The host LOG
> file says (for example):
>2018-08-08 08:10:32 Got fatal error during xfer (total size is
> 466869877613  speedup is 23.88)
>
> The XferLOG says:
>Got fatal error during xfer (total size is 466869877613  speedup is
> 23.88)
>Backup aborted by user signal
>
> As far as I know, this is a bogus report and the backup was actually
> fine.  A subsequent backup starts from this Partial backup and completes
> successfully, running (of course) much faster than the first "failed"
> backup.  My guess is that the failure is caused by a ClientTimeout alarm
> signal 72000 seconds after the backup starts, which arrives during the
> v3->v4 copy.  The LOG file reports this:
>2018-08-01 22:56:17 Aborting backup up after signal ALRM
>
> Thankfully it doesn't abort - it continues with the entire
> copy/backup/refcount/... process.
>
> 2) Backups which are still running or which have failed show up on the
> Host Summary web page with a recent Last Backup (days) value.  This
> makes it look (to me) like the backup has completed successfully.  I
> often use Host Summary sorted on the Last Backup column to see if any
> filesystems are lacking recent backups, and that doesn't work now
> because failed and still-running backups appear to be safely completed.
> I think this is a change from v3.
>
> 3) I noticed that when BackupPC_nightly was running
> "BackupPC_refCountUpdate -m", the BackupPC status web page said "v3
> cpool scan - cntUpdate nn/nn".  This makes it look like the v3 cpool
> scan is still running - I think the reported status is incorrect during
> this phase of the nightly process.
>
> Overall v4 is so much faster than v3 and just as brilliantly conceived
> and implemented - huge thank-you to Craig and anyone else involved for a
> fantastic piece of software.
>
> Michael.
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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 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] Accidently Deleted Host in Gui

[Craig Barratt via BackupPC-users]

Stuart,

Yes, great point - deleting the host and re-adding it many days later it
will likely result in unused pool files being deleted during that period.

You can confirm that hypothesis by looking in the storage for tree for that
host ($TOPDIR/pc/HOST) and below the numbered directories (one for each
backup) you should see an attrib file, like this:

/data/BackupPC/pc//3/attrib_69c04f2b39174a2a33d18eea03311735


Take that md5 digest (the 32 hex digits after "attrib_") and see if that
pool file exists, either by looking for
$TOPDIR/cpool/68/c0/69c04f2b39174a2a33d18eea03311735 (you have to "and" the
first two bytes with 0xfe to get the two directory names), or use this
command:

BackupPC_zcat 69c04f2b39174a2a33d18eea03311735 | wc

If that's missing, you should probably delete $TOPDIR/pc/HOST/* and start
over on that host...

Craig

On Mon, Oct 22, 2018 at 7:41 PM Stuart Rothrock  wrote:

> Thank you Craig - I am running version 4.2.1 and perl 4:5.26.2
>
> The list of backups does appear - 1-full and 5-incrementals. The dropdown
> (html select list) is populated with the 6 backups but when I choose any of
> them from the dropdown, the tree is missing other than "Contents of /" and
> below that is "The directory / is empty".
>
> It looks like I don't need to click the "GO" since a change in the
> selected backup fires an event to display that result at the top directory
> level. Sorry for any confusion.
>
> With further reading and thought, it may be important to mention that the
> full backup was 45 days in age. The host was deleted from the config for a
> month before adding it back. I am a newb to the BackupPC internals so
> excuse my terminology. Is it possible the grim reaper axed metadata or
> files that were only referenced by this host?
>
> Thanks
> Stuart
>
> On Mon, Oct 22, 2018 at 10:03 PM Craig Barratt via BackupPC-users <
> backuppc-users@lists.sourceforge.net> wrote:
>
>> Deleting the host from the gui should only remove the entry from the
>> hosts file, so adding it back should make things work again.  I just tried
>> that on a test setup, and it worked for me.  I should ask what BackupPC
>> version you are running?
>>
>> Does the list of backups GUI appear when you browse to that host?  You
>> say the "previous backups can be selected".  After you select a particular
>> backup, does the directory tree on the left look correct?
>>
>> When you refer to clicking "Go", are you referring to the directory
>> navigation text box just above the backup directory navigation tree?  If
>> so, what path did you enter (I presume "/")?
>>
>> Craig
>>
>>
>>
>> On Mon, Oct 22, 2018 at 2:00 PM Stuart Rothrock 
>> wrote:
>>
>>> I accidently deleted a host so I added it back. No files were manually
>>> deleted but I am unable to browse the previous backups. They can be
>>> selected and after clicking "Go", it says "The directory / is empty". What
>>> do I need to do to be able to browse/restore files for this host? Thanks
>>> ___
>>> 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 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 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] Backup failure due to two specific files

[Craig Barratt via BackupPC-users]

Sorry about the delay in replying.

It appears you have two pairs of identical pool files. In particular, these
two pool files appear to be the same:

/var/lib/backuppc/cpool/fc/86/fd871fd27933f41039f22c4201419c29
/var/lib/backuppc/cpool/fc/86/fd871fd27933f41039f22c4201419c2901


and these two as well:

/var/lib/backuppc/cpool/d0/6c/d06dc5183aa3095ce36e1334235bd76d
/var/lib/backuppc/cpool/d0/6c/d06dc5183aa3095ce36e1334235bd76d01


Can you confirm with cmp that those two pairs are identical (if they are
still around)?

Obviously this shouldn't happen.  For some reason the first file wasn't
matched when a backup of the same file was being done, so a new pool file
was written.  The only time this normally could happen is if you really
have different files with the same md5 digest, which is extraordinarily
unlikely, unless you construct known examples (which I did to test that
part of BackupPC).  That's what the "01" extension is for - you can have an
arbitrary number of different md5 collisions and that's how they are named
in the pool.  But they should all be unique files.

That said, the backup should work fine - yes, you will see ominous "Botch -
got multiple pool file matches" warning messages that multiple pool files
match, which sounds concerning, but the first matching file is used and all
that will happen is the error count for the transfer is incremented.

Craig

On Fri, Sep 7, 2018 at 10:46 AM Patel, Tarak (SSC/SPC) <
tarak.pa...@canada.ca> wrote:

> Hi all,
>
> I configured a backup via ssh on my remote host which requires a hop. The
> config is as follows:
>
> $Conf{TarClientCmd} = '$sshPath -q -x -n -l root oem1 env LC_ALL=C ssh -q
> -x -n -l root $host "env LC_ALL=C $tarPath --exclude=\'*lost+found*\'
> --exclude=\'*ASM1_ora_548653_20180820220003763166143795*\'
> --exclude=\'*ora_468842_201808201844508*\' -c -v -f - -C $shareName+
> --totals"';
> $Conf{XferMethod} = 'tar';
> $Conf{TarShareName} = [
>   '/etc',
>   '/home',
>   '/usr/local/bin',
>   '/opt/oracle'
> ];
> $Conf{ClientNameAlias} = [
>   'repo1'
> ];
> $Conf{PingCmd} = '/usr/bin/ssh -q -x -n -l root oem1 $pingPath -c 1 $host';
> $Conf{XferLogLevel} = 9;
> $Conf{TarIncrArgs} = '--newer=\'$incrDate+ $fileList+\'';
> $Conf{ClientCharset} = 'UTF-8';
> $Conf{ClientCharsetLegacy} = 'UTF-8';
>
> After debugging backup failure issue I was able to narrow down two files
> which seems to have caused the problem and ended up excluding them. With
> XferLogLevel set to 9 and some additional print statements in
> BackupPC_tarExtract I was able to capture output below (please ignore line
> with TKP entry since those are my print statements):
>
> tarExtract: splitPath: returning dir =
> 'f%2fopt%2foracle%2fgrid12%2frdbms/faudit', fileName =
> '+ASM1_ora_548653_20180820220003763166143795.aud', attrib =
> 'f%2fopt%2foracle%2fgrid12%2frdbms/faudit/attrib' from path =
> '/audit/+ASM1_ora_548653_20180820220003763166143795.aud'
> tarExtract: bpc_attribCache_loadPath: path =
> /audit/+ASM1_ora_548653_20180820220003763166143795.aud -> dir =
> f%2fopt%2foracle%2fgrid12%2frdbms/faudit, fileName =
> +ASM1_ora_548653_20180820220003763166143795.aud, attribPath =
> f%2fopt%2foracle%2fgrid12%2frdbms/faudit/attrib
>
> tarExtract: dirCacheNewDir: populating dir = /audit with
> +ASM1_ora_548653_20180820220003763166143795.aud
>
>
> tarExtract: Got file
> './audit/+ASM1_ora_548653_20180820220003763166143795.aud', mode 0640, size
> 1960, type 0
> tarExtract: dirCacheNewFile: path =
> audit/+ASM1_ora_548653_20180820220003763166143795.aud: dir = /audit, file =
> +ASM1_ora_548653_20180820220003763166143795.aud
> tarExtract: tarRead 1960
> tarExtract: TKP processClose BPC_FTYPE_FILE...
> tarExtract: TKP Errors: 1 --> poolWite errs 1 --> 1, 745, 1splitPath:
> returning dir = 'f%2fopt%2foracle%2fgrid12%2frdbms/faudit', fileName =
> '+ASM1_ora_548653_20180820220003763166143795.aud', attrib =
> 'f%2fopt%2foracle%2fgrid12%2frdbms/faudit/attrib' from path =
> 'audit/+ASM1_ora_548653_20180820220003763166143795.aud'
> tarExtract: bpc_attribCache_loadPath: path =
> audit/+ASM1_ora_548653_20180820220003763166143795.aud -> dir =
> f%2fopt%2foracle%2fgrid12%2frdbms/faudit, fileName =
> +ASM1_ora_548653_20180820220003763166143795.aud, attribPath =
> f%2fopt%2foracle%2fgrid12%2frdbms/faudit/attrib
> tarExtract: bpc_poolWrite_write: digest is fd871fd27933f41039f22c4201419c29
> tarExtract: Candidate matching file
> /var/lib/backuppc/cpool/fc/86/fd871fd27933f41039f22c4201419c29
> tarExtract: Candidate matching file
> /var/lib/backuppc/cpool/fc/86/fd871fd27933f41039f22c4201419c2901
> tarExtract:
> bpc_fileZIO_open(/var/lib/backuppc/cpool/fc/86/fd871fd27933f41039f22c4201419c2901,
> 0, 3) -> 3
> tarExtract: match[0] now set to
> /var/lib/backuppc/cpool/fc/86/fd871fd27933f41039f22c4201419c2901
> tarExtract:
> bpc_fileZIO_open(/var/lib/backuppc/cpool/fc/86/fd871fd27933f41039f22c4201419c29,
> 0, 3) -> 5
> tarExtract: match[1] now set to
> 

Re: [BackupPC-users] Upgrading BPC from v3.3 to v4.1

[Craig Barratt via BackupPC-users]

I just pushed the change
<https://github.com/backuppc/backuppc/commit/11e025b8df164634617bbff920bf2410638acfca>
I mentioned in (1).  I confirmed that in perl 5.28, version() gives the
error you mentioned due to the trailing period (while perl 5.22 does not).

Craig

On Mon, Oct 22, 2018 at 10:08 AM Craig Barratt <
cbarr...@users.sourceforge.net> wrote:

> What are the versions of rsync_bpc and perl are you running?
> Specifically, what's the output from
>
> rsync_bpc --version
>
> perl -v
>
>
> I assume rsync_bpc is 3.1.2.beta0.  For some reason the "version" package
> complains about a trailing ".", perhaps in only newer versions of perl (on
> perl 5.22.1 it works fine).
>
> Here are two options:
>
> 1) change this line
>
> $version = $1 if ( $output =~
> /rsync_bpc\s+version\s+([\d.]+)(beta\d+)?\s+protocol/ );
>
> to
>
> $version = $1 if ( $output =~
> /rsync_bpc\s+version\s+([\d.]+?)(\.beta\d+)?\s+protocol/ );
>
>
> 2) installing rsync_bpc 3.0.9 instead.  The latest release is here
> <https://github.com/backuppc/rsync-bpc/releases/tag/3.0.9.12>.
>
> Craig
>
> On Mon, Oct 22, 2018 at 5:10 AM Sorin Srbu  wrote:
>
>> Hi all,
>>
>> Finally found time to upgrade an old BackupPC install from v3.3.1 to the
>> latest v4.
>>
>> I read up on the prerequisites, gotchas' etc and installed
>> BackupPC-XS-0.57,
>> rsync-bpc 0.01 and version 0.9924 using cpan.
>> I've never used cpan before, but I didn't get any errors here. Installs
>> should be fine.
>> After that, I continued with installing the latest BPC 4.2.1 and it went
>> w/o
>> a hitch.
>>
>> The end remarks after BPC-installation mentioned restarting httpd so I did
>> that.
>> I also restarted the backuppc daemon for good measure
>>
>> And this is where the problem started, I got this:
>> "Starting BackupPC: Invalid version format (trailing decimal) at
>> /usr/share/BackupPC/bin/BackupPC line 125"
>>
>> The lines in /usr/share/BackupPC/bin/BackupPC is about this:
>>
>> $version = $1 if ( $output =~
>> /rsync_bpc\s+version\s+([\d.]+)(beta\d+)?\s+protocol/ );
>> if ( $version eq "unknown" || version->parse($1) <
>> version->parse($PackageVersion->{rsync_bpc}) ) {
>> print(STDERR "BackupPC: rsync_bpc at $Conf{RsyncBackupPCPath}
>> needs
>> to be upgraded (got version $1; need >= $PackageVersion->{rsync_bpc});
>> exiting in 30s\n");
>> sleep(30);
>> exit(1);
>> }
>>
>>
>> I've no idea how to proceed. I can't find any information pertinent to the
>> error message.
>> Is version too old? Too new? Something else?
>>
>> Any help appreciated!
>> Thanks.
>>
>>
>> --
>> BW,
>> Sorin
>> ---
>> # Sorin Srbu, Sysadmin
>> # Uppsala University
>> # Dept of Medicinal Chemistry
>> # Div of Org Pharm Chem
>> # Box 574
>> # SE-75123 Uppsala
>> # Sweden
>> #
>> # Phone: +46 (0)18-4714482
>> # Visit: BMC, Husargatan 3, B5:404b
>> # Web: https://www.ilk.uu.se/
>> ---
>> # O<  ASCII ribbon campaign - Against html E-mail
>> # http://tinyurl.com/ascii-ribbon-campaign
>> #
>> # This message was not sent from an iProduct!
>> #
>> # Please consider the environment before printing this email.
>> # Join the campaign at http://thinkBeforePrinting.org
>> #
>> # MotD follows:
>> The Internet? Is that thing still around? -Homer Simpson.
>>
>>
>> --
>> BW,
>> Sorin
>> ---
>> # Sorin Srbu, Sysadmin
>> # Uppsala University
>> # Dept of Medicinal Chemistry
>> # Div of Org Pharm Chem
>> # Box 574
>> # SE-75123 Uppsala
>> # Sweden
>> #
>> # Phone: +46 (0)18-4714482
>> # Visit: BMC, Husargatan 3, B5:404b
>> # Web: https://www.ilk.uu.se/
>> ---
>> # O<  ASCII ribbon campaign - Against html E-mail
>> # http://tinyurl.com/ascii-ribbon-campaign
>> #
>> # This message was not sent from an iProduct!
>> #
>> # Please consider the environment before printing this email.
>> # Join the campaign at http://thinkBeforePrinting.org
>> #
>> # MotD follows:
>> Alimony is like buying oats for a dead horse.
>>
>> ___
>> 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 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] Accidently Deleted Host in Gui

[Craig Barratt via BackupPC-users]

Deleting the host from the gui should only remove the entry from the hosts
file, so adding it back should make things work again.  I just tried that
on a test setup, and it worked for me.  I should ask what BackupPC version
you are running?

Does the list of backups GUI appear when you browse to that host?  You say
the "previous backups can be selected".  After you select a particular
backup, does the directory tree on the left look correct?

When you refer to clicking "Go", are you referring to the directory
navigation text box just above the backup directory navigation tree?  If
so, what path did you enter (I presume "/")?

Craig



On Mon, Oct 22, 2018 at 2:00 PM Stuart Rothrock  wrote:

> I accidently deleted a host so I added it back. No files were manually
> deleted but I am unable to browse the previous backups. They can be
> selected and after clicking "Go", it says "The directory / is empty". What
> do I need to do to be able to browse/restore files for this host? Thanks
> ___
> 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 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] deleted backups then host and pc folder yet data remains in pool

[Craig Barratt via BackupPC-users]

What is your setting for $Conf{BackupPCNightlyPeriod}?  The default is 1,
but if it's set to something larger then it will take that number of
days/nights for the entire pool to be traversed.

It does appear that some of the files are getting deleted - yesterday
afternoon it deleted 242189 files (although the total size wasn't very
large), and 2149846 remain.  That could be reasonable after 6 days with
$Conf{BackupPCNightlyPeriod} set to 16.

Craig

On Mon, Oct 22, 2018 at 1:21 PM Mike Hughes  wrote:

> A host was created to duplicate the cpool from another BackupPC server. It
> was set to skip compression and successfully filled the uncompressed pool
> with ~300GB of data. On the advice of others, I decided to use rsync in a
> cronjob instead, so my intent was to delete this host and its data.
>
> First I went into the host's backup summary and clicked "Delete" for each
> of the four backups that were listed. Then I followed the documentation
> under "Other installation topics - Removing a client" where it said to:
> "remove its entry in the conf/hosts file, and then delete the
> /var/lib/BackupPC//pc/$host directory."
>
> The data still resides in the uncompressed pool - this is six days after I
> performed the above actions:
>
> * Uncompressed pool:
>   o Pool is 306.65GiB comprising 2149846 files and 16512 directories (as
> of 10/21 13:06),
>   o Pool hashing gives 0 repeated files with longest chain 0,
>   o Nightly cleanup removed 242189 files of size 0.94GiB (around 10/21
> 13:06),
> * Compressed pool:
>   o Pool is 141.48GiB comprising 1570628 files and 16512 directories (as
> of 10/21 13:06),
>   o Pool hashing gives 0 repeated files with longest chain 0,
>   o Nightly cleanup removed 4949 files of size 26.05GiB (around 10/21
> 13:06),
> * Pool file system was recently at 46% (10/22 08:00), today's max is 46%
> (10/21 13:00) and yesterday's max was 46%.
>
> I'm concerned I may have created a race-condition when I asked the system
> to delete the individual backups then removed the client and pc folders
> before it could complete. This was the only host set to not use compression
> and I believe the full 306GB in pool is solely for this host. Is it safe to
> delete the contents of pool?
>
>
> ___
> 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 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] Upgrading BPC from v3.3 to v4.1

[Craig Barratt via BackupPC-users]

What are the versions of rsync_bpc and perl are you running?  Specifically,
what's the output from

rsync_bpc --version

perl -v


I assume rsync_bpc is 3.1.2.beta0.  For some reason the "version" package
complains about a trailing ".", perhaps in only newer versions of perl (on
perl 5.22.1 it works fine).

Here are two options:

1) change this line

$version = $1 if ( $output =~
/rsync_bpc\s+version\s+([\d.]+)(beta\d+)?\s+protocol/ );

to

$version = $1 if ( $output =~
/rsync_bpc\s+version\s+([\d.]+?)(\.beta\d+)?\s+protocol/ );


2) installing rsync_bpc 3.0.9 instead.  The latest release is here
.

Craig

On Mon, Oct 22, 2018 at 5:10 AM Sorin Srbu  wrote:

> Hi all,
>
> Finally found time to upgrade an old BackupPC install from v3.3.1 to the
> latest v4.
>
> I read up on the prerequisites, gotchas' etc and installed
> BackupPC-XS-0.57,
> rsync-bpc 0.01 and version 0.9924 using cpan.
> I've never used cpan before, but I didn't get any errors here. Installs
> should be fine.
> After that, I continued with installing the latest BPC 4.2.1 and it went
> w/o
> a hitch.
>
> The end remarks after BPC-installation mentioned restarting httpd so I did
> that.
> I also restarted the backuppc daemon for good measure
>
> And this is where the problem started, I got this:
> "Starting BackupPC: Invalid version format (trailing decimal) at
> /usr/share/BackupPC/bin/BackupPC line 125"
>
> The lines in /usr/share/BackupPC/bin/BackupPC is about this:
>
> $version = $1 if ( $output =~
> /rsync_bpc\s+version\s+([\d.]+)(beta\d+)?\s+protocol/ );
> if ( $version eq "unknown" || version->parse($1) <
> version->parse($PackageVersion->{rsync_bpc}) ) {
> print(STDERR "BackupPC: rsync_bpc at $Conf{RsyncBackupPCPath} needs
> to be upgraded (got version $1; need >= $PackageVersion->{rsync_bpc});
> exiting in 30s\n");
> sleep(30);
> exit(1);
> }
>
>
> I've no idea how to proceed. I can't find any information pertinent to the
> error message.
> Is version too old? Too new? Something else?
>
> Any help appreciated!
> Thanks.
>
>
> --
> BW,
> Sorin
> ---
> # Sorin Srbu, Sysadmin
> # Uppsala University
> # Dept of Medicinal Chemistry
> # Div of Org Pharm Chem
> # Box 574
> # SE-75123 Uppsala
> # Sweden
> #
> # Phone: +46 (0)18-4714482
> # Visit: BMC, Husargatan 3, B5:404b
> # Web: https://www.ilk.uu.se/
> ---
> # O<  ASCII ribbon campaign - Against html E-mail
> # http://tinyurl.com/ascii-ribbon-campaign
> #
> # This message was not sent from an iProduct!
> #
> # Please consider the environment before printing this email.
> # Join the campaign at http://thinkBeforePrinting.org
> #
> # MotD follows:
> The Internet? Is that thing still around? -Homer Simpson.
>
>
> --
> BW,
> Sorin
> ---
> # Sorin Srbu, Sysadmin
> # Uppsala University
> # Dept of Medicinal Chemistry
> # Div of Org Pharm Chem
> # Box 574
> # SE-75123 Uppsala
> # Sweden
> #
> # Phone: +46 (0)18-4714482
> # Visit: BMC, Husargatan 3, B5:404b
> # Web: https://www.ilk.uu.se/
> ---
> # O<  ASCII ribbon campaign - Against html E-mail
> # http://tinyurl.com/ascii-ribbon-campaign
> #
> # This message was not sent from an iProduct!
> #
> # Please consider the environment before printing this email.
> # Join the campaign at http://thinkBeforePrinting.org
> #
> # MotD follows:
> Alimony is like buying oats for a dead horse.
>
> ___
> 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 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] Archive incremental backup

[Craig Barratt via BackupPC-users]

Mtime won't be a reliable indication of what's in an incremental backup.
First, other meta data might have changed (eg, rsync checks all file meta
data including permissions, size etc) that would cause the file to be
transferred during the incremental.  You could look at the XferLOG file to
parse which files were transferred.  Another consideration is that creating
a subset of a tar archive of a backup stored in BackupPC might not
accurately capture hardlinks.

The high-level question is what are you trying to do?  Offsite archives of
BackupPC's backups?  As has been discussed in other threads, using rsync or
a parallel BackupPC instance could accomplish what you want.

Craig

On Fri, Oct 12, 2018 at 8:27 AM Patel, Tarak (SSC/SPC) <
tarak.pa...@canada.ca> wrote:

> Hello,
>
> Archive of incremental backups (only delta) has not been discussed in a
> long time. One of the proposed option was to create a tarball of
> pc/host/BackupNum however this requires some gymnastics to correctly
> interpret the paths. Has anyone come up with an elegant solution to this
> problem? I had successfully modified BackupPC_tarCreate to only write files
> based on mtime of file and a timedelta. By adding 'next if($hdr->{mtime} <
> $TimeDelta);' in TarWriteFile function.  The TimeDelta is simply the time
> stamp of last full.
>
> If there was a way to know which file is new in an incremental backup,
> then we can use remaining code as is.
>
> Any thoughts?
>
> Thanks,
> Tarak
>
> --
>
> Tarak Patel
>
> Chef d'équipe, Integration HPC, Solution de calcul E-Science
> Service partagé Canada / Gouvernment du Canada
> tarak.pa...@canada.ca
> 1-514-421-7299
>
> Team Lead, HPC Integration, E-Science Computing Solution
> Shared Services Canada, Government of Canada
> tarak.pa...@canada.ca
> 1-514-421-7299
>
>
>
>
> ___
> 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 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] Errors returned

[Craig Barratt via BackupPC-users]

What version of smbclient are you running?

Can you email me an XferLOG file that gives an error (hopefully something
not too big)?  Feel free to redact host names etc.

Craig


On Thu, Oct 18, 2018 at 2:30 PM Jaime Fenton 
wrote:

> Hi all,
>
>
>
> I thought I had my issues fixed, I’d got successfully backups on my
> computers that were erroring out on my 4.2.1 backuppc server. However,
> after migrating the rest of my machines, they are now erroring out with
> “Got fatal error during xfer (Non-zero exit status from smbclient)”. All
> these machines are windows 7 machines that backup perfectly fine on a 3.3.1
> backuppc server. I’m really at a loss as what next steps to take because
> everything looks to be correct.
>
>
>
> Things to note:
>
>
>
> · Files are backing up but not all of them are
>
> · I do have some errors (some permission wise, some locked files,
> etc) which make sense and I’ve put exceptions to avoid those
>
>
>
> Any advice would be appreciated
>
>
>
> Jaime
> --
> Jaime Fenton
> Support Engineer
>
> T: +1 604 398 4800 (main)
> D: +1 604 398 4813 (direct)
> E: jaime.fen...@animallogic.ca
>
> 840 Cambie Street
> Vancouver, BC V6B 2P6
> CANADA
>
>
>   [image: LinkedIn]   [image:
> Facebook]   [image:
> Twitter]   [image: Instagram]
> 
>
> [image: Animal Logic] 
>
> www.animallogic.com
>
> *CONFIDENTIALITY AND PRIVILEGE NOTICE*
> This email is intended only to be read or used by the addressee. It is
> confidential and may contain privileged information. If you are not the
> intended recipient, any use, distribution, disclosure or copying of this
> email is strictly prohibited. Confidentiality and legal privilege attached
> to this communication are not waived or lost by reason of the mistaken
> delivery to you. If you have received this email in error, please delete it
> and notify us immediately by telephone or email.
> ___
> 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 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] fatal error during xfer (tar:632)

[Craig Barratt via BackupPC-users]

>
> Here you go... it could be the net shutdown command failing perhaps?


My initial reaction was yes, but a bad exit status from DumpPostUserCmd
will only cause the backup to be considered bad
if $Conf{UserCmdCheckStatus} is non-zero.  If it were, there should be an
error message saying so.  Can you check the value
of $Conf{UserCmdCheckStatus}?  Also, are there any error messages in the
client's LOG file?

I'd recommend temporarily removing $Conf{DumpPostUserCmd}, and also
reducing the smbclient debug level ("-d 5") to 1 ("-d 1")
in $Conf{SmbClientFullCmd} and $Conf{SmbClientIncrCmd}.

Craig

On Fri, Oct 19, 2018 at 2:16 AM Paul Littlefield  wrote:

> On 18/10/2018 16:56, Craig Barratt wrote:
> > It seems the XferLOG file is very short.  Can you just send the whole
> thing please?
>
> Here you go... it could be the net shutdown command failing perhaps?
>
>
> Running: /usr/bin/smbclient 192.168.0.101\\BackupPC-Test -U XX -E
> -d 5 -c tarmode\ full -Tc -
> full backup started for share BackupPC-Test
> Xfer PIDs are now 2075,2074
> INFO: Current debug levels:
>all: 5
>tdb: 5
>printdrivers: 5
>lanman: 5
>smb: 5
>rpc_parse: 5
>rpc_srv: 5
>rpc_cli: 5
>passdb: 5
>sam: 5
>auth: 5
>winbind: 5
>vfs: 5
>idmap: 5
>quota: 5
>acls: 5
>locking: 5
>msdfs: 5
>dmapi: 5
>registry: 5
>scavenger: 5
>dns: 5
>ldb: 5
>tevent: 5
> tar:1667 DUMP:t->to_process= 1
> tar:1668 DUMP:t->mode.operation= TAR_CREATE
> tar:1669 DUMP:t->mode.selection= TAR_INCLUDE
> tar:1670 DUMP:t->mode.blocksize= 20
> tar:1671 DUMP:t->mode.hidden   = 1
> tar:1672 DUMP:t->mode.system   = 1
> tar:1673 DUMP:t->mode.incremental  = 0
> tar:1674 DUMP:t->mode.reset= 0
> tar:1675 DUMP:t->mode.dry  = 0
> tar:1676 DUMP:t->mode.verbose  = 0
> tar:1677 DUMP:t->total_size= 0
> tar:1678 DUMP:t->tar_path  = -
> tar:1679 DUMP:t->path_list_size= 0
> tar:1685 DUMP:t->path_list @ (nil) (0 elem)
> lp_load_ex: refreshing parameters
> Initialising global parameters
> rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
> INFO: Current debug levels:
>all: 5
>tdb: 5
>printdrivers: 5
>lanman: 5
>smb: 5
>rpc_parse: 5
>rpc_srv: 5
>rpc_cli: 5
>passdb: 5
>sam: 5
>auth: 5
>winbind: 5
>vfs: 5
>idmap: 5
>quota: 5
>acls: 5
>locking: 5
>msdfs: 5
>dmapi: 5
>registry: 5
>scavenger: 5
>dns: 5
>ldb: 5
>tevent: 5
> Processing section "[global]"
> doing parameter workgroup = XX
> doing parameter server string = Samba Server %v
> doing parameter netbios name = SERVER1
> doing parameter map to guest = Bad User
> doing parameter passdb backend = smbpasswd
> doing parameter username map = /etc/samba/smbusers
> doing parameter log file = /var/log/samba/log.%m
> doing parameter max log size = 50
> doing parameter name resolve order = wins lmhosts bcast host
> doing parameter time server = Yes
> doing parameter load printers = No
> doing parameter printcap name = /etc/printcap
> doing parameter printing = bsd
> doing parameter preferred master = Yes
> doing parameter domain master = No
> doing parameter dns proxy = No
> doing parameter wins support = Yes
> doing parameter idmap config * : backend = tdb
> doing parameter hosts allow = 172.20.0., 192.168.2., 192.168.1.,
> 192.168.0., 127.
> pm_process() returned Yes
> added interface eno1 ip=192.168.0.1 bcast=192.168.0.255
> netmask=255.255.255.0
> Netbios name list:-
> my_netbios_names[0]="SERVER1"
> Client started (version 4.3.11-Ubuntu).
> Connecting to 192.168.0.101 at port 445
> Socket options:
> SO_KEEPALIVE = 0
> SO_REUSEADDR = 0
> SO_BROADCAST = 0
> TCP_NODELAY = 1
> TCP_KEEPCNT = 9
> TCP_KEEPIDLE = 7200
> TCP_KEEPINTVL = 75
> IPTOS_LOWDELAY = 0
> IPTOS_THROUGHPUT = 0
> SO_REUSEPORT = 0
> SO_SNDBUF = 87040
> SO_RCVBUF = 372480
> SO_SNDLOWAT = 1
> SO_RCVLOWAT = 1
> SO_SNDTIMEO = 0
> SO_RCVTIMEO = 0
> TCP_QUICKACK = 1
> TCP_DEFER_ACCEPT = 0
>   session request ok
> Doing spnego session setup (blob length=277)
> got OID=1.3.6.1.4.1.311.2.2.30
> got OID=1.3.6.1.4.1.311.2.2.10
> got principal=
> GENSEC backend 'gssapi_spnego' registered
> GENSEC backend 'gssapi_krb5' registered
> GENSEC backend 'gssapi_krb5_sasl' registered
> GENSE

Re: [BackupPC-users] fatal error during xfer (tar:632)

[Craig Barratt via BackupPC-users]

It seems the XferLOG file is very short.  Can you just send the whole thing
please?

It appears just one 63 byte file gets transferred. Is Test.txt the only
file in the BackupPC-Test share?

BackupPC 3.3.1 with smb transfers checks for either of these two strings:
"tar_process done, err = 0" and "Total bytes received: 63" to confirm that
the transfer ended normally. Both of those are present.  So I'm not sure
why it thinks there is a fatal error.  Hopefully there's a clue somewhere
in the XferLOG file.

Looking at the code, any of these strings will be taken as a backup failure
(and if so, the XferLOG file should have a message: "This backup will fail
because:...")

} elsif ( /^code 0 listing /
|| /^\s*code 0 opening /
|| /^\s*abandoning restore/i
|| /^\s*Error: Looping in FIND_NEXT/i
|| /^\s*SUCCESS - 0/i
|| /^\s*Call timed out: server did not respond/i
|| /^\s*tree connect failed: ERRDOS - ERRnoaccess
\(Access denied\.\)/
|| /^\s*tree connect failed: NT_STATUS_BAD_NETWORK_NAME/
|| /^\s*NT_STATUS_INSUFF_SERVER_RESOURCES listing /

Craig

On Thu, Oct 18, 2018 at 6:14 AM Paul Littlefield  wrote:

> On 18/10/2018 14:13, Paul Littlefield wrote:
> > Ah, logged in and this is the samba smbclient command line...
>
> and this is the end of the XferLOG file...
>
>
> Domain=[PC] OS=[Windows 7 Home Premium 7601 Service Pack 1]
> Server=[Windows 7 Home Premium 6.1]
>   session setup ok
>   tconx ok
> tar:316  tarmode is now full, system, hidden, noreset, quiet
> tar:702  tar_process do_list with mask: \\*
> tar:899  +++ \Test.txt
> tar:712  Total bytes received: 63
> tar:632  tar_process done, err = 0
>pool 644   0/0  63 Test.txt
> tarExtract: Done: 0 errors, 1 filesExist, 63 sizeExist, 63 sizeExistComp,
> 1 filesTotal, 63 sizeTotal
> Got fatal error during xfer (tar:632  tar_process done, err = 0)
> Backup aborted (tar:632  tar_process done, err = 0)
>
> --
>
> Paul Littlefield
>
___
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] rsync_bpc: write failed on "/path/dump.sql": Quota exceeded (122)

[Craig Barratt via BackupPC-users]

Please Google your os type + "quota".  Here's a tutorial for Ubuntu / Debian
.

Craig

On Sat, Oct 13, 2018 at 3:41 AM Oliver Lippert 
wrote:

> Hey there,
>
> I used to run BackupPC for a while now and since some time I get errors in
> the backups for big files (10GB to 50GB).
>
>
>
> […]
>
> rsync_bpc: write failed on "/path/dump.sql": Quota exceeded (122)
>
> […]
> rsync_bpc: failed to open "/path/mysql/ibdata1", continuing: Quota
> exceeded (122)
>
> […]
>
> rsync error: error in file IO (code 11) at receiver.c(391)
> [receiver=3.0.9.12]
>
>
>
> I searched in the WEB how to figure out which quota I have to configure,
> but I did not found someone else having this problem.
>
>
>
> I do run the BackupPC in a docker container on an Synology DS918+. There
> is enough diskspace available.
>
>
>
> I appreciate any informations / links.
>
>
>
> --
>
> Regards,
>   Oliver Lippert – Lipperts WEB
>
>
> ___
> 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 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] fatal error during xfer (tar:632)

[Craig Barratt via BackupPC-users]

Paul,

Sorry, I really misinterpreted the error message ("tar_process done, err =
0") you sent.  It's from smbclient, not tar.

What version of smbclient are you running?  What is the smbclient command
line (near the top of the XferLOG file)?  What are the settings
for $Conf{SmbClientFullCmd} and $Conf{SmbClientIncrCmd}?  Do both
incremental and full backups fail with the same error?

Craig

On Fri, Oct 12, 2018 at 5:46 AM Holger Parplies  wrote:

> Hi,
>
> Paul Littlefield wrote on 2018-10-12 12:22:48 + [Re: [BackupPC-users]
> fatal error during xfer (tar:632)]:
> > On 11/10/2018 23:44, Craig Barratt wrote:
> > >[...]
> > >What version of tar are you using?  Can you run gnu tar instead (that's
> the default under cygwin)?
> > >[...]
> >
> > $ apt-cache policy tar
> > tar:
> >   Installed: 1.28-2.1ubuntu0.1
> >   Candidate: 1.28-2.1ubuntu0.1
> >   Version table:
> >  *** 1.28-2.1ubuntu0.1 500
> > 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main
> amd64 Packages
> > 500 http://security.ubuntu.com/ubuntu xenial-security/main
> amd64 Packages
> > 100 /var/lib/dpkg/status
> >  1.28-2.1 500
> > 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
> Packages
>
> you're running Ubuntu on the Windoze host? Amazing ...
>
> Regards,
> Holger
>
>
> ___
> 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 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] syncing local and cloud backups

[Craig Barratt via BackupPC-users]

I'd recommend just using rsync if you want to make a remote copy of the
cpool, pc and conf directories, to a place that BackupPC doesn't back up.

Craig

On Thu, Oct 11, 2018 at 10:22 AM Mike Hughes  wrote:

> Hi BackupPC users,
>
> Similar questions have come up a few times but I have not found anything
> relating to running multiple pools. Here's our setup:
> - On-prem dev servers backed up locally to BackupPC (4.x)
> - Prod servers backed up in the cloud to a separate BackupPC (4.x) instance
>
> I'd like to provide disaster recovery options by syncing the dedup'd pools
> from on-prem to cloud and vice-versa but this would create an infinite
> loop. Is it possible to place the off-site data into a separate cpool which
> I could exclude from the sync? It would also be nice to be able to extract
> files from the synced pool individually without having to pull down the
> whole cpool and reproducing the entire BackupPC server.
>
> How do others manage on-prem and off-site backup synchronization?
> Thanks,
> Mike
>
>
> ___
> 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 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] fatal error during xfer (tar:632)

[Craig Barratt via BackupPC-users]

Paul,

BackupPC looks at the status / summary messages from tar to determine if
the transfer completed successfully.  That means it depends on the type and
version of tar you are using.

It's reporting that the last output line from tar was "632  tar_process
done, err = 0".  I don't think that's a standard message from gnu tar.

What version of tar are you using?  Can you run gnu tar instead (that's the
default under cygwin)?

Craig

On Thu, Oct 11, 2018 at 6:51 AM Paul Littlefield  wrote:

> Hello List,
>
> I am getting this error during backup from a Windows 7 Professional PC...
>
> 2018-10-08 20:31:03 Got fatal error during xfer (tar:632  tar_process
> done, err = 0)
> 2018-10-08 20:31:08 Backup aborted (tar:632  tar_process done, err = 0)
>
> ...is anything wrong?
>
> Thanks,
>
> Paul
>
> Ubuntu Linux 16.04.05 LTS
> Kernel 4.4.0-43-generic x86_64
> BackupPC 3.3.1-2ubuntu3.3
> PERL 5.22.1
>
>
>
> ___
> 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 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] Rsync issue

[Craig Barratt via BackupPC-users]

Matt,

I'm happy to take a look at the logs.  The "io timeout after 72035 seconds"
suggests something has stalled, and we'd like to find out what is going on
just before that.

Yes, the first step will be to increase the XferLogLevel to see what is
happening before things stall.  Maybe try 5?  Also, you could add "-vv" to
the RsyncArgs to increase the client's rsync verbosity.  It probably makes
sense to reduce the ClientTimeout so you don't have to wait for ~20 hours
each run.  It would be good to know if the stall is repeatable (ie, same
place in the transfer each time).

However, since the XferLOG file writes are buffered, it's quite likely
we'll miss the most recent debug output when the processes get killed after
the io timeout.  So it might be better to run BackupPC_dump from the
command-line with the -v option, which writes all the log output to stderr
in addition to the XferLOG file.  First disable automatic backups on that
host, to make sure none start when you are running a backup manually.  Then
run BackupPC_dump from the command-line as the backuppc user.  Either do it
from a terminal with a large scroll-back capability (eg, 2k+ lines that you
can cut-and-paste), or use "script" or something similar that captures all
the output.

Please send to me directly.

Thanks,
Craig

On Thu, Oct 4, 2018 at 7:31 AM Bedynek, Matthew J. 
wrote:

> All,
>
>
>
> Am using BackupPC 4.2.1 on a Redhat 7.5 host to backup a rather large
> repository of data.  I believe things worked OK with tar but after we
> changed the file system we switched back to Rsync.  I think we have plenty
> of others which roughly equal in size but backup fine.  Not sure if there
> is something specific about this path that causes issue.
>
>
>
> I have worked with Craig in the past to troubleshoot and provide data.  I
> suspect he or someone will ask I turn up logging and repeat.  I can provide
> the logs on request -- just not here since would be very large.
>
>
>
> It seems our environment is good for testing / finding issues since some
> of them are large in size and number of files.
>
>
>
> Thanks and take care!
>
>
>
> (..list of files..)
>
> [receiver] io timeout after 72035 seconds -- exiting
>
> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
> sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 233977 inode
>
> rsync error: timeout in data send/receive (code 30) at io.c(140) 
> [receiver=3.0.9.12]
>
> rsync_bpc: connection unexpectedly closed (39 bytes received so far) 
> [generator]
>
> DoneGen: 0 errors, 14204 filesExist, 809628 sizeExist, 809628 sizeExistComp, 
> 131190 filesTotal, 2915859542718 sizeTotal, 0 filesNew, 0 sizeNew, 0 
> sizeNewComp, 305814 inode
>
> rsync error: error in rsync protocol data stream (code 12) at io.c(629) 
> [generator=3.0.9.12]
>
> rsync_bpc exited with fatal status 12 (3072) (rsync error: error in rsync 
> protocol data stream (code 12) at io.c(629) [generator=3.0.9.12])
>
> Xfer PIDs are now
>
> Got fatal error during xfer (rsync error: error in rsync protocol data stream 
> (code 12) at io.c(629) [generator=3.0.9.12])
>
> Backup aborted (rsync error: error in rsync protocol data stream (code 12) at 
> io.c(629) [generator=3.0.9.12])
>
> BackupFailCleanup: nFilesTotal = 131190, type = full, BackupCase = 1, inPlace 
> = 1, lastBkupNum =
>
> Keeping non-empty backup #0 (/backups/BackupPC/pc/cncs5to9-8-repo/0)
>
> Running BackupPC_refCountUpdate -h cncs5to9-8-repo -f on cncs5to9-8-repo
>
> Xfer PIDs are now 12182
>
> BackupPC_refCountUpdate: cncs5to9-8-repo #0 inodeLast set to 305812 (was 1)
>
> BackupPC_refCountUpdate: host cncs5to9-8-repo got 0 errors (took 141 secs)
>
> Xfer PIDs are now
>
> Finished BackupPC_refCountUpdate (running time: 142 sec)
>
>
>
>
>
> Thanks,
>
>
>
> Matt
>
>
> ___
> 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 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] turn off PoolV3Enabled

[Craig Barratt via BackupPC-users]

Ideally you should turn it off after all V3 pool files have either been
migrated to the V4 pool (because a new V4 backup matched the old pool file)
or have been deleted (because no backups refer to them).

You can tell this from the status message:

Pool is X+YGiB comprising...


X is the V4 pool size, and Y is the V3 pool size.

It's ok to turn it off before the V3 pool size is zero.  Old V3 backups
will still be complete and accurate.  The only downside is that newly
backed up files could get duplicated: there could be a new copy created in
the V4 pool while an old one is still in the V3 pool.  So the potential
storage duplication/waste is the size of V3 pool when you disable the V3
pool.   Eventually the V3 pool usage should go to zero as the remaining V3
backups expire.

Craig

On Thu, Sep 20, 2018 at 9:31 PM Mark Maciolek  wrote:

> hi,
>
> BackupPC working great with version 4.2.1, on the servers that I did an
> upgrade from version 3.3.x to 4.2.1 when can the PoolV3Enabled box be
> unchecked?
>
> We only retain backups for 90 days so I should be able to turn it off
> after that or do I have to leave it enabled forever?
>
> Mark
>
>
> ___
> 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 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 4.2.1 apparently in an infinite loop.

[Craig Barratt]

Since there's nothing of interest in the XferLOG file, I'd recommend
running BackupPC_dump from the command-line with the -v option.  That
should copy all log messages to stdout so you should see them in real
time.  First make sure there are no backups running on HOST (where HOST is
kestrel or localhost or whatever client you want to run) and then run this
as the BackupPC user:

su backuppc

BackupPC_dump -v -f HOST


If that doesn't show much useful information, the next step is re-run after
increasing the XferLogLevel (eg, to 5) and adding "-vv" or "-vvv" to
$Conf{RsyncArgs} (which increases the logging level from the remote
(client) rsync).

Craig

On Thu, Sep 20, 2018 at 10:10 PM G.W. Haywood via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:

> Hi there,
>
> Thanks for your reply.
>
> On Thu, 20 Sep 2018, Craig Barratt wrote:
>
> > First, this error message looks like just a bug in the message text: it
> > shouldn't be concatenating those paths:
> >
> > > RmTreeQuietInner:
> > >
> /mnt/3TLV/backuppc/pc/kestrel/268//var/lib/backuppc/pc/kestrel/268/X
> > > isn't a directory (while removing
> > > /var/lib/backuppc/pc/kestrel/268/X/f.cache)
>
> That's good news, so I guess it doesn't hurt anything and it can be
> left with you to fix in due course.
>
> > Back to the original issue: the most likely reason backups are
> > taking longer that you expect is that your excludes are not correct.
>
> That's not the case here.
>
> > Are you sure you are excluding /proc and any other sparse
> > potentially large files (eg, /var/log/wtmp)?
>
> Yes I am.  For the vast majority of machines (including the one for
> which rsync_bpc which was in an infinite loop), I'm only backing up
> /etc/ and /home/.  Perhaps the share names don't make it obvious, but
> bear in mind that I've been backing up most of these machines using
> BackupPC V3 for nearly a decade.
>
> As you probably saw I've killed the errant rsync_bpc process (the one
> which had so far taken ten days to do an eight minute job) so the best
> I can offer at the moment is to say it looks like manually running a
> BackupPC_backupDelete job caused rsync_bpc to loop on the next backup.
>
> > For the backup that is taking a lot longer than expected, you should
> > look at its current XferLOG file.
>
> The backup which ran after I killed the one which was spinning took
> four hours 20 minutes to complete and it was a full backup.  The one
> which is running now was started 24 hours later.  It's still running
> after 19 hours and the XferLOG contains two bytes:
>
> tornado:/mnt/3TLV/backuppc/pc/localhost# >>> ls -l XferLOG.738.z
> -rw-r- 1 backuppc backuppc 2 Sep 19 20:00 XferLOG.738.z
> tornado:/mnt/3TLV/backuppc/pc/localhost# >>> hexdump XferLOG.738.z
> 000 5e78
> 002
>
> Now this has your attention, would you offer your thoughts on my use
> of BackupPC_backupDelete in the way that I used it?  Specifically, as
> a tool to remove unwanted parts of all backups for a given host?  It
> seems to me to be a long felt want.  In one particular case here, the
> unwanted directory was backed up because a directory whose name began
> with a dot also had a space in it. :(
>
> --
>
> 73,
> Ged.
>
>
> ___
> 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 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 4.2.1 apparently in an infinite loop.

[Craig Barratt via BackupPC-users]

First, this error message looks like just a bug in the message text: it
shouldn't be concatenating those paths:

RmTreeQuietInner:
> /mnt/3TLV/backuppc/pc/kestrel/268//var/lib/backuppc/pc/kestrel/268/X
> isn't a directory (while removing
> /var/lib/backuppc/pc/kestrel/268/X/f.cache)


Back to the original issue: the most likely reason backups are taking
longer that you expect is that your excludes are not correct.  Are you sure
you are excluding /proc and any other sparse potentially large files (eg,
/var/log/wtmp)?

For the backup that is taking a lot longer than expected, you should look
at its current XferLOG file.  It won't be complete (the most recent portion
won't be yet written to disk), but using BackupPC_zcat should allow you see
what it is has been doing at least up until recently.  If you really want
to see what it happening in real time, you could run strace on rsync_bpc as
Michael suggested, or an easier option would be to run BackupPC_dump from
the command line with the -v option.  That should write all output to
stdout.  Hopefully that shows what unexpected things are being backed up.

Craig



On Thu, Sep 20, 2018 at 12:11 AM Michael Stowe <
michael.st...@member.mensa.org> wrote:

> On 2018-09-19 03:52, G.W. Haywood via BackupPC-users wrote:
> > Hello again all,
> >
> > On Tue, 18 Sep 2018, Michael Stowe wrote:
> >> On Mon, 17 Sep 2018, G.W. Haywood wrote:
> >>
> >>> I suspect that this is a fault in BackupPC_backupDelete ...
> >>> RmTreeQuietInner seems to be seeing some sort of bowdlerization
> >>> ...
> >>> RmTreeQuietInner:
> >>>
> /mnt/3TLV/backuppc/pc/kestrel/268//var/lib/backuppc/pc/kestrel/268/X
> >>> isn't a directory (while removing
> >>> /var/lib/backuppc/pc/kestrel/268/X/f.cache)
> >>> ...
> >>
> >> What is indicating to you that a directory path is built incorrectly?
> >
> > The part that says:
> >
> > RmTreeQuietInner:
> > /mnt/3TLV/backuppc/pc/kestrel/268//var/lib/backuppc/pc/kestrel/268/X
> > isn't a directory (while removing
> > /var/lib/backuppc/pc/kestrel/268/X/f.cache)
> >
> > BackupPC has somehow concatenated the mount path and the symlink path
> > and come up with balderdash.  I've started on tracking it down by
> > means of log statements, but what with all these alligators time has
> > been a bit short.
>
> This is curious, as it would potentially represent a problem for anybody
> whose repository is sym-linked.  It's possible that the delete process
> is leaving unexpected debris, and this is reponsible for the unexpected
> space that BackupPC is consuming.
>
> We've all got alligators; if nobody gets to it first, I'll pursue this.
>
> >> Does it make sense to focus on rsync first?
> >
> > Well it's rsync_bpc not rsync, and I have no idea, but vide infra.
>
> Fair enough -- though presumably it's rsync_bpc on one side and rsync on
> the other.  If you've already killed the process and it doesn't get
> stuck again, it may not be much to worry about.  If it hangs again, it's
> probably worth tracing both sides to see what it's up to.
>
> >>> Is [the correct way to reduce the storage used by V4] documented?
> >
> > I guess I'll just leave this hanging and hope for the hive to come up
> > with something.
> >
> > On Tue, 18 Sep 2018, Guillermo Rozas wrote:
> >> On Mon, 17 Sep 2018, G.W. Haywood wrote:
> >>
> > ... BackupPC appears to think that it has now used 5TB of a 3TB
> > disc and the claimed usage is growing. ...
> >>>
> >>> ... and growing. ...
> >>
> >> Regarding this point: have you tried reducing the parameter
> >> PoolSizeNightlyUpdatePeriod? ... forcing it to check the size in a
> >> single night ... for a couple of days solved it.
> >
> > Oh, dammit, thank you!  I remember seeing that when I trawled through
> > the new configuration options and then forgot all about it.  I set it
> > to 1 last night, before the nightly backup run, then stopped BackupPC,
> > killed the ten-day-old rsync_bpc, restarted BackupPC and hit the sack.
> > This morning normality seems to be restored, at least the crazy usage
> > figures have disappeared and the V4 pool size looks sane again:
> >
> > 8<--
> > Pool is 940.29+987.81GiB comprising 1757074+1459146 files and
> > 16512+4369 directories (as of 2018-09-19 01:29),
> > Pool hashing gives 1678+1909 repeated files with longest chain 7+4,
> > Nightly cleanup removed 6436+10275 files of size 135.04+0.26GiB
> > (around 2018-09-19 01:29),
> > Pool file system was recently at 75% (2018-09-19 08:49), today's max
> > is 80% (2018-09-19 01:00) and yesterday's max was 80%.
> > 8<--
> >
> > There were log messages for over 17,000 missing pool files but I'm
> > guessing that this is probably the result of my manually running
> > BackupPC_backupDelete.  I haven't had a chance to investigate that
> > but I will do later.
> >
> > Thanks again!
>
>
> 

Re: [BackupPC-users] Problem trying to restore to remote host

[Craig Barratt via BackupPC-users]

Steve,

What version of BackupPC are you using?

It looks like you are trying to restore /Users/dickk/Desktop and
/User/dickk/Documents to another share (/Shared Items/Net Programs) and
path (/Ministry/DickK_Restore/).

The "Trimming /dickk from filesList" looks correct; it's the common path in
the files you want to restore, so it gets stripped from the file list, and
added to the rsync_bpc arguments.  Yes, rsync_bpc is expecting to chdir to
/dickk (below host dickk, share /Users), and we need to figure out why it
can't do that.

Does this directory exist: /mnt/stage/BackupPC/pc/dickk/1069/fUsers/fdickk?

Craig

On Wednesday, September 19, 2018, Steve Palm  wrote:

> Can anyone help me determine what the problem is here?  Trying to restore
> from a backup onto a different host. The original backup was for computer
> 'dickk' and trying to restore it to 'xserve1':
>
> I inserted blank lines for readability, but everything looks OK except for
> the
>
> Trimming /dickk from filesList
>
> Wrote source file list to
> /mnt/stage/BackupPC/pc/xserve1/.rsyncFilesFrom23795: /Desktop /Documents
>
> Running: /usr/local/bin/rsync_bpc --bpc-top-dir /mnt/stage/BackupPC
> --bpc-host-name dickk --bpc-share-name /Users/ --bpc-bkup-num 1069
> --bpc-bkup-comp 1 --bpc-bkup-merge 1069/1/3 --bpc-attrib-new
> --bpc-log-level 1 -e /usr/bin/ssh\ -T\ -q\ -x\ -l\ backuppc
> --rsync-path=nice\ -n\ 15\ sudo\ /usr/local/bin/rsync --recursive --super
> --numeric-ids --perms --owner --group -D --times --links --hard-links
> --delete --partial --log-file-format=log:\ %o\ %i\ %B\ %8U,%8G\ %9l\ %f%L
> --stats --protect-args
> --files-from=/mnt/stage/BackupPC/pc/xserve1/.rsyncFilesFrom23795 /dickk
> xserve1.sga.org:/Shared\ Items/Net\ Programs/Ministry/DickK_Restore/
>
> This is the rsync child about to exec /usr/local/bin/rsync_bpc
>
> rsync_bpc: change_dir "/dickk" failed: No such file or directory (2)
>
> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal,
> 0 sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 0 inode
>
> rsync error: errors selecting input/output files, dirs (code 3) at
> flist.c(2022) [sender=3.0.9.12]
>
> rsync_bpc exited with fatal status 3 (768) (rsync error: errors selecting
> input/output files, dirs (code 3) at flist.c(2022) [sender=3.0.9.12])
>
> restore failed: rsync error: errors selecting input/output files, dirs
> (code 3) at flist.c(2022) [sender=3.0.9.12]
>
> I don't understand the failure to change_dir to "/dickk" ?  The pc dir
> does exist on the stage volume '/mnt/stage/BackupPC/pc/dickk/'.
>
> The RestoreInfo file in the destination pc directory has:
>
> %RestoreReq = (
>   'fileList' => [
> '/dickk/Desktop',
> '/dickk/Documents'
>   ],
>   'shareDest' => '/Shared Items/Net Programs',
>   'pathHdrDest' => '/Ministry/DickK_Restore/',
>   'num' => '1069',
>   'reqTime' => 1537371681,
>   'shareSrc' => '/Users/',
>   'pathHdrSrc' => '/dickk',
>   'hostDest' => 'xserve1',
>   'hostSrc' => 'dickk',
>   'user' => 'admin'
> );
>
> Can anyone help me find out what is going on?  Thanks!
>
> Steve
>
>
>
> ___
> 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 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] Troubleshooting assistance for Bad Transfer

[Craig Barratt via BackupPC-users]

Either use the CGI interface to display the XferLOG file, or use
BackupPC_zcat from the command line.

Craig

On Tue, Aug 28, 2018 at 9:25 PM Jaime Fenton 
wrote:

> Hi there,
>
>
>
> On advice from craigbarrett, I’m posting this query here.
>
>
>
> https://github.com/backuppc/backuppc/issues/218
>
>
>
> I’ve gone to the XferLog file and it’s gibberish. Is there a way to
> compile that file or advice on troubleshooting that file that can give me
> some insight as to why my backups are having fatal errors?
>
>
>
> Thanks in advance,
>
> Jaime
> --
> Jaime Fenton
> Support Engineer
>
> T: +1 604 398 4800 (main)
> D: +1 604 398 4813 (direct)
> E: jaime.fen...@animallogic.ca
>
> 840 Cambie Street
> Vancouver, BC V6B 2P6
> CANADA
>
>
>   [image: LinkedIn]   [image:
> Facebook]   [image:
> Twitter]   [image: Instagram]
> 
>
> [image: Animal Logic] 
>
> www.animallogic.com
>
> *CONFIDENTIALITY AND PRIVILEGE NOTICE*
> This email is intended only to be read or used by the addressee. It is
> confidential and may contain privileged information. If you are not the
> intended recipient, any use, distribution, disclosure or copying of this
> email is strictly prohibited. Confidentiality and legal privilege attached
> to this communication are not waived or lost by reason of the mistaken
> delivery to you. If you have received this email in error, please delete it
> and notify us immediately by telephone or email.
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Got fatal error during xfer (No files dumped for share E)

[Craig Barratt via BackupPC-users]

What versions of BackupPC and smbclient are you using?

Craig

On Mon, Aug 20, 2018 at 10:16 PM jose marquez  wrote:

> Hello, I recently was given a Dell Precision T1500 and decided to finally
> make a backup server. I wanted to backup my storage drive (Drive letter E)
> offsite automatically from my main computer which runs Windows 7. So I
> found out about BackupPC and set it up according to this source:
> https://www.howtoforge.com/linux_backuppc and was able to start a backup.
> I had personal errands to take care of so I left the backup to run and came
> back to this in the XferLOG:
>
> This snippet is from the top of the log:
>
>
> Contents of file /var/lib/backuppc/pc/blunt-pc/XferLOG.0.z, modified
> 2018-08-20 17:22:14
>
> Running: /usr/bin/smbclient blunt-pc\\E -I 192.168.1.3 -U Blunt -E -d 1 
> -c tarmode\ full -Tc -
> full backup started for share E
> Xfer PIDs are now 6250,6249
> WARNING: The "syslog" option is deprecated
> Domain=[BLUNT-PC] OS=[Windows 7 Ultimate 7601 Service Pack 1] Server=[Windows 
> 7 Ultimate 6.1]
> tar:316  tarmode is now full, system, hidden, noreset, quiet
>
> This snippet is from the bottom of the log:
>
> create   644   0/0  6440353792 pagefile.sys
> tarExtract: �6���Y��<�H���}�  �c��j�P���
> tarExtract: d���l�)�> = �C��&�
> tarExtract: �U���{�+ �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/9: 
> checksum error at
> tarExtract: Can't open 
> /var/lib/backuppc/pc/blunt-pc/new/fE/f�6���Y��<�H���}�  �c��j�P���%0a
> d���l�)�> = �C��&�%0d�U���{�+ 
> �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/f9 for empty output  
> create 0   0/0   0 �6���Y��<�H���}�  �c��j�P���
> tarExtract: d���l�)�> = �C��&�
> tarExtract: �U���{�+ �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/9
> tarExtract: �1! . � d�,���e�  �yi�Z���H��r�Y�C��z 
> ��7�1�~� �  < �e��
> tarExtract: ���
> tarExtract: 7 � M �m���D�BJ � �   
> tarExtract:  ] � /_: checksum error at
> tarExtract: Unable to open 
> /var/lib/backuppc/pc/blunt-pc/new/fE/f�6���Y��<�H���}�  �c��j�P���%0a
> d���l�)�> = �C��&�%0d�U���{�+ 
> �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/attrib for writingBotch, no 
> matches on /var/lib/backuppc/pc/blunt-pc/new/fE/f�6���Y��<�H���}�  
> �c��j�P���%0ad���l�)�> = �C��&�%0d�U���{�+ 
> �|��.�#���M���L��j�M�}���v���f��o�H�p���H��}/attrib 
> (715fadf75232a925b6f7e60587a51417)Can't open 
> /var/lib/backuppc/pc/blunt-pc/new/fE/f�1! . � d�,���e�  
> �yi�Z���H��r�Y�C��z ��7�1�~� �  < �e��%0a���%0d7 � M 
> �m���D�BJ � �     %0a ] � /f_ for empty output  create 0  
>  0/0   0 �1! . � d�,���e�  
> �yi�Z���H��r�Y�C��z ��7�1�~� �  < �e��
> tarExtract: ���
> tarExtract: 7 � M �m���D�BJ � �   
> tarExtract:  ] � /_
> tarExtract: � ���8�3 * �
> tarExtract: Z�2  ? �P�   L   t�� ��� 5 n $ vn���c�bN 
> � �
> tarExtract:���n��� � r �I���6�/  � v �k�{�"�,; � /a: checksum 
> error at
> NT_STATUS_ACCESS_DENIED listing \System Volume Information\*
> tar:712  Total bytes received: 131331187102
> tarExtract: Unable to open /var/lib/backuppc/pc/blunt-pc/new/fE/f�1! . � 
> d�,���e�  �yi�Z���H��r�Y�C��z ��7�1�~� �  < 
> �e��%0a���%0d7 � M �m���D�BJ � �     %0a ] � /attrib for 
> writingBotch, no matches on /var/lib/backuppc/pc/blunt-pc/new/fE/f�1! . � 
> d�,���e�  �yi�Z���H��r�Y�C��z ��7�1�~� �  < 
> �e��%0a���%0d7 � M �m���D�BJ � �     %0a ] � /attrib 
> (e4894caf9ef0d79e617cfceb23934040)Can't open 
> /var/lib/backuppc/pc/blunt-pc/new/fE/f� ���8�3 * �%0dZ�2  ? �P� 
>   L   t�� ��� 5 n $ vn���c�bN � � %0d   ���n��� � r 
> �I���6�/f  � v �k�{�"�,; � /fa for empty output  create 0   
> 0/0   0 � ���8�3 * �
> tarExtract: Z�2  ? �P�   L   t�� ��� 5 n $ vn���c�bN 
> � �
> tarExtract:���n��� � r �I���6�/  � v �k�{�"�,; � /a
> tarExtract:  � �Y�S��s � B m��_  ~ V ��� � D e   
> u��A� �[  ( �AI� �� n� � ���<�c l
> tarExtract:  We�'�< 7 ���B�/�: checksum error at
> tarExtract: Unable to open /var/lib/backuppc/pc/blunt-pc/new/fE/f� ���8�3 * 
> �%0dZ�2  ? �P�   L   t�� ��� 5 n $ vn���c�bN � � %0d  
>  ���n��� � r �I���6�/f  � v �k�{�"�,; � /attrib for writingBotch, 
> no matches on /var/lib/backuppc/pc/blunt-pc/new/fE/f� ���8�3 * 
> �%0dZ�2  ? �P�   L   t�� ��� 5 n $ vn���c�bN � � %0d  
>  ���n��� � r �I���6�/f  � v �k�{�"�,; � /attrib 
> (583fc6779d9ccc4b6731ef590de7624f)Unable to open 
> /var/lib/backuppc/pc/blunt-pc/new/fE/f� ���8�3 * �%0dZ�2  ? �P� 
>   L   t�� ��� 5 n $ vn���c�bN � � %0d   ���n��� � r 
> �I���6�/attrib for 

Re: [BackupPC-users] installation help

[Craig Barratt via BackupPC-users]

Unfortunately the package support for BackupPC 4.x isn't very
comprehensive, but there are quite a few available.  I appreciate the work
people do keeping various packages up to date (I don't support any
myself).  For example, see this issue
<https://github.com/backuppc/backuppc/issues/127> for RHEL/CentOS rpms.

If you decide to install manually, I would recommend downloading the latest
releases, rather than using git head (which is usually in a working state,
but might not be).  Look in the release page for each project to download
the latest tarballs.  That will allow you to skip the first few steps.
But, yes, you still need a working compiler environment to build rsync-bpc
and backuppc-xs.

Craig

On Wed, Aug 8, 2018 at 11:34 AM Mike Hughes  wrote:

> LOL! I do not want to build everything from source! I’m just following the
> documentation as I’ve been able to find it. You suggested a script which
> installs on Debian-based systems so I’m trying to follow those steps on
> CentOS.
>
> I’ve been running V 3.3.1 from EPEL for a couple years and am ready to
> move to 4.x. If there is a way to install it without building it from
> scratch I am all ears! I must have missed the memo!
>
>
>
> *From:* Craig Barratt via BackupPC-users <
> backuppc-users@lists.sourceforge.net>
> *Sent:* Wednesday, August 8, 2018 13:26
> *To:* General list for user discussion, questions and support <
> backuppc-users@lists.sourceforge.net>
> *Cc:* Craig Barratt 
> *Subject:* Re: [BackupPC-users] installation help
>
>
>
> Mike,
>
>
>
> First, I would strongly recommend using the rsync-bpc 3.0.9 branch.  The
> head is based on rsync 3.1.2 but it hasn't seen as much testing and hasn't
> been released.  You should do a "git checkout 3.0.9" before running
> ./configure, eg:
>
>
>
> git clone https://github.com/backuppc/rsync-bpc.git
>
> cd rsync-bpc
>
> git checkout 3.0.9
>
> ./configure
>
> make
>
>
>
> Second, why do you actually want to build everything from source?
>
>
>
> I don't have access to a Centos 7 box to test building.  However, I
> suspect you'll need to install a libacl-devel package (or similar) to get
> the C headers etc.  Many linux libraries have two packages - the runtime
> library, and another (generally with "devel" in the name) for compiling and
> linking code.
>
>
>
> Craig
>
>
>
> On Wed, Aug 8, 2018 at 10:19 AM Mike Hughes  wrote:
>
> Thanks for the reply. I’m building on CentOS7 so the example is partly
> useful but there are several changes. Here are some basic steps in case
> someone else attempts this:
>
> yum install git build-essential perl-devel perl-CPAN perl-CGI gcc httpd
> mod_ssl glusterfs-client
>
> cpan [accept all defaults]
>
> install Test::More
>
> quit
>
> reboot (might not be necessary)
>
> git clone https://github.com/backuppc/backuppc.git
>
> git clone https://github.com/backuppc/backuppc-xs.git
>
> git clone https://github.com/backuppc/rsync-bpc.git
>
> cd backuppc-xs/
>
> perl Makefile.PL
>
> make
>
> make test
>
> make install
>
>
>
> cd ../rsync-bpc
>
> ./configure
>
> make
>
>
>
> …and this is where it fails with:
>
> lib/sysacls.c:2761:2: error: #error No ACL functions defined for this
> platform!
>
> #error No ACL functions defined for this platform!
>
>   ^
>
> make: *** [lib/sysacls.o] Error 1
>
>
>
> I’m not sure if this is helpful but acl’s (Access Control Lists) are
> supported on this system:
>
>
>
> [Cent-7:root@hostname rsync-bpc]# yum install acl
>
> Package acl-2.2.51-14.el7.x86_64 already installed and latest version
>
> Nothing to do
>
>
>
> [Cent-7:root@hostname rsync-bpc]# cat
> /boot/config-3.10.0-862.9.1.el7.x86_64 | grep _ACL
>
> CONFIG_EXT4_FS_POSIX_ACL=y
>
> CONFIG_XFS_POSIX_ACL=y
>
> CONFIG_BTRFS_FS_POSIX_ACL=y
>
> CONFIG_FS_POSIX_ACL=y
>
> CONFIG_GENERIC_ACL=y
>
> CONFIG_TMPFS_POSIX_ACL=y
>
> CONFIG_NFS_V3_ACL=y
>
> CONFIG_NFSD_V2_ACL=y
>
> CONFIG_NFSD_V3_ACL=y
>
> CONFIG_NFS_ACL_SUPPORT=m
>
> CONFIG_CEPH_FS_POSIX_ACL=y
>
> CONFIG_CIFS_ACL=y
>
>
>
> Am I making a mistake in installing the current version? Perhaps I’d have
> better results installing the version identified in the Debian-based script?
>
> Thank you!
>
> *From:* Craig Barratt via BackupPC-users <
> backuppc-users@lists.sourceforge.net>
> *Sent:* Wednesday, August 8, 2018 00:37
> *To:* backuppc-users@lists.sourceforge.net
> *Cc:* Craig Barratt 
> *Subject:* Re: [BackupPC-users] installation help
>
>
>
> Mike,
>
>
>
> You have to bui

Re: [BackupPC-users] installation help

[Craig Barratt via BackupPC-users]

Mike,

First, I would strongly recommend using the rsync-bpc 3.0.9 branch.  The
head is based on rsync 3.1.2 but it hasn't seen as much testing and hasn't
been released.  You should do a "git checkout 3.0.9" before running
./configure, eg:

git clone https://github.com/backuppc/rsync-bpc.git
cd rsync-bpc
git checkout 3.0.9
./configure
make


Second, why do you actually want to build everything from source?

I don't have access to a Centos 7 box to test building.  However, I suspect
you'll need to install a libacl-devel package (or similar) to get the C
headers etc.  Many linux libraries have two packages - the runtime library,
and another (generally with "devel" in the name) for compiling and linking
code.

Craig

On Wed, Aug 8, 2018 at 10:19 AM Mike Hughes  wrote:

> Thanks for the reply. I’m building on CentOS7 so the example is partly
> useful but there are several changes. Here are some basic steps in case
> someone else attempts this:
>
> yum install git build-essential perl-devel perl-CPAN perl-CGI gcc httpd
> mod_ssl glusterfs-client
>
> cpan [accept all defaults]
>
> install Test::More
>
> quit
>
> reboot (might not be necessary)
>
> git clone https://github.com/backuppc/backuppc.git
>
> git clone https://github.com/backuppc/backuppc-xs.git
>
> git clone https://github.com/backuppc/rsync-bpc.git
>
> cd backuppc-xs/
>
> perl Makefile.PL
>
> make
>
> make test
>
> make install
>
>
>
> cd ../rsync-bpc
>
> ./configure
>
> make
>
>
>
> …and this is where it fails with:
>
> lib/sysacls.c:2761:2: error: #error No ACL functions defined for this
> platform!
>
> #error No ACL functions defined for this platform!
>
>   ^
>
> make: *** [lib/sysacls.o] Error 1
>
>
>
> I’m not sure if this is helpful but acl’s (Access Control Lists) are
> supported on this system:
>
>
>
> [Cent-7:root@hostname rsync-bpc]# yum install acl
>
> Package acl-2.2.51-14.el7.x86_64 already installed and latest version
>
> Nothing to do
>
>
>
> [Cent-7:root@hostname rsync-bpc]# cat
> /boot/config-3.10.0-862.9.1.el7.x86_64 | grep _ACL
>
> CONFIG_EXT4_FS_POSIX_ACL=y
>
> CONFIG_XFS_POSIX_ACL=y
>
> CONFIG_BTRFS_FS_POSIX_ACL=y
>
> CONFIG_FS_POSIX_ACL=y
>
> CONFIG_GENERIC_ACL=y
>
> CONFIG_TMPFS_POSIX_ACL=y
>
> CONFIG_NFS_V3_ACL=y
>
> CONFIG_NFSD_V2_ACL=y
>
> CONFIG_NFSD_V3_ACL=y
>
> CONFIG_NFS_ACL_SUPPORT=m
>
> CONFIG_CEPH_FS_POSIX_ACL=y
>
> CONFIG_CIFS_ACL=y
>
>
>
> Am I making a mistake in installing the current version? Perhaps I’d have
> better results installing the version identified in the Debian-based script?
>
> Thank you!
>
> *From:* Craig Barratt via BackupPC-users <
> backuppc-users@lists.sourceforge.net>
> *Sent:* Wednesday, August 8, 2018 00:37
> *To:* backuppc-users@lists.sourceforge.net
> *Cc:* Craig Barratt 
> *Subject:* Re: [BackupPC-users] installation help
>
>
>
> Mike,
>
>
>
> You have to build and install backuppc-xs first.  Also, makeDist needs a
> --version argument.
>
>
>
> The wiki has an example script
> <https://github.com/backuppc/backuppc/wiki/Installing-BackupPC-4-from-git-on-Ubuntu-Xenial-16.04-LTS>
> for building from git.
>
>
> Craig
>
>
>
> On Tue, Aug 7, 2018 at 10:26 PM Mike Hughes  wrote:
>
> I am new to git-based installations and need some help. I cloned the three
> projects and I cd into the backuppc folder to run perl configure.pl and
> it replies with:
>
> [Cent-7:root@hostname backuppc]# perl configure.pl
>
> You need to run makeDist first to create a tarball release that includes an
>
> updated configure.pl.  After you unpack the tarball, run configure.pl from
>
> there.
>
>
>
> Not sure why I’d need to generate a tarball but when I run makeDist I get:
>
> [Cent-7:root@ hostname backuppc]# perl makeDist
>
> Can't locate BackupPC/XS.pm in @INC (@INC contains: ./lib
> /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
> /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at
> lib/BackupPC/Lib.pm line 51.
>
> BEGIN failed--compilation aborted at lib/BackupPC/Lib.pm line 51.
>
> Compilation failed in require at makeDist line 59.
>
> BEGIN failed--compilation aborted at makeDist line 59.
>
>
>
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> Lis

Re: [BackupPC-users] installation help

[Craig Barratt via BackupPC-users]

Mike,

You have to build and install backuppc-xs first.  Also, makeDist needs a
--version argument.

The wiki has an example script

for building from git.

Craig

On Tue, Aug 7, 2018 at 10:26 PM Mike Hughes  wrote:

> I am new to git-based installations and need some help. I cloned the three
> projects and I cd into the backuppc folder to run perl configure.pl and
> it replies with:
>
> [Cent-7:root@hostname backuppc]# perl configure.pl
>
> You need to run makeDist first to create a tarball release that includes an
>
> updated configure.pl.  After you unpack the tarball, run configure.pl from
>
> there.
>
>
>
> Not sure why I’d need to generate a tarball but when I run makeDist I get:
>
> [Cent-7:root@ hostname backuppc]# perl makeDist
>
> Can't locate BackupPC/XS.pm in @INC (@INC contains: ./lib
> /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
> /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at
> lib/BackupPC/Lib.pm line 51.
>
> BEGIN failed--compilation aborted at lib/BackupPC/Lib.pm line 51.
>
> Compilation failed in require at makeDist line 59.
>
> BEGIN failed--compilation aborted at makeDist line 59.
>
>
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Tricks for Win 10 SMB Backup?

[Craig Barratt via BackupPC-users]

What is the value of $Conf{SmbClientFullCmd} and what is the smb command
that is being run (see the XferLOG file)?

Craig

On Sun, Jul 29, 2018 at 12:22 PM Tim Evans  wrote:

> Unable to connect to a new Windows 10 client via SMB for backup.
> Command-line testing with 'smbclient' works ok:
>
> $ smbclient -L new-pelican -Ubackup%xxx
>
> Sharename Type Comment
> -  ---
> ADMIN$ Disk Remote Admin
> C Disk
> C$ Disk Default share
> E Disk
> E$ Disk Default share
> IPC$ IPC Remote IPC
> Users Disk
> SMB1 disabled -- no workgroup available
>
> Note the last line of the output above ("SMB1 disabled...").
>
> I can login with 'smbclient' and interactively display files in the
> shares.  BackupPC, however, won't connect.
>
> 2018-07-27 15:07:03 Backup failed on new-pelican (No files dumped for
> share C$)
>
> Googling the SMB1 reference leads to suggestions to add the following to
> smb.conf:
>
> client min protocol = SMB2
> client max protocol = SMB3
>
> I added this and restarted Samba. This doesn't resolve the issue.  Other
> suggestions?
>
> Thanks.
> --
> Tim Evans   |5 Chestnut Court
> 443-394-3864|Owings Mills, MD 21117
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] cpool directory twice as big as reported and missing pool files reported by BackupPC_refCountUpdate

[Craig Barratt via BackupPC-users]

Cody,

There were some bugs in earlier versions of 4.x that could cause missing
pool files.  But they have been fixed for some time.

How did you determine the cpool directory size (eg, du -sh)?

At any point did you run backups with compression off?

Here's how to find which backup is referencing a particular digest:

   - pick an md5 digrest (32 hex characters) that got an error
   - take the first 2 hex digits and and it with 0xfe (ie, round down to
   the next even number, eg: 0x77 -> 0x76; 0xaf -> 0xae).  Call those two
   digits XY
   - run BackupPC_poolCntPrint TOPDIR/pc/*/*/refCnt/poolCnt.1.XY | less
   - use less to search for the hex digest (ie, type "/" then paste the 32
   digit digest, then hit return)
   - then search upwards to find the file name (ie, type "?Pool Ref", then
   hit return
   - based on the file name, you can find out the host name and backup
   number

To find which directory / file in the specific backup references that
digest, you would need to use BackupPC_ls -R -h HOST -n BackupNUM -s Share
/ | egrep HexDigest

Craig

On Thu, Jul 5, 2018 at 7:32 PM Cody Jackson  wrote:

> Hi all,
>
> BackupPC reports that my pool is about 800GB, but my cpool directory is
> 1.6TB.
>
> When I try running BackupPC_refCountUpdate, I get about 350 errors
> similar to:
>
> BackupPC_refCountUpdate: missing pool file [md5 hash] count 1
>
> Questions:
>
> * Are these issues related?
> * How can I find out which computers have references to these hashes
> that are missing?
> * Why is my pool so big?
>
> For the pool size, I did recently change the compress level (going from
> 3 to 7), but the older backups should have fallen off the radar by now
> and been removed.
>
> Cheers,
>
> -C
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Xfer errors

[Craig Barratt via BackupPC-users]

Pete,

Can you send me more lines from the XferLOG file for a full backup?
Ideally the entire log file, or otherwise several hundred lines before and
after the errors.

Craig

On Fri, Jun 29, 2018 at 4:53 AM Pete Geenhuizen  wrote:

> I'm running BackupPC 4.2.1 on CentOS 7.5 using rsync and it's running
> just fine with one seemingly minor problem.
>
> I recently upgraded a host from CentOS 6.9 to CentOS 7.5 and forced a
> level 0 backup, and since then I see the following errors.
>
> cannot delete non-empty directory: bin
> could not make way for new symlink: bin
> cannot delete non-empty directory: lib
> could not make way for new symlink: lib
> cannot delete non-empty directory: lib64
> could not make way for new symlink: lib64
> cannot delete non-empty directory: sbin
> could not make way for new symlink: sbin
> cannot delete non-empty directory: var/lock
> could not make way for new symlink: var/lock
> cannot delete non-empty directory: var/run
> could not make way for new symlink: var/run
>
> Although these errors don't seem to affect the backups and seem to be
> benign I'd like to deal with them.
>
> Any ideas on how to best eliminate these error?
>
> Thanks
>
> Pete
>
> --
> Unencumbered by the thought process.
>   -- Click and Clack the Tappet brothers
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Old data in Windows backups

[Craig Barratt via BackupPC-users]

Let's start with your 4.1.5 BackupPC.

Does your $Conf{RsyncArgs} include the --delete option?  If not, add it.
If so, I'd be curious to see a portion of the XferLOG file for a full
backup of a directory where old files remain.

Craig

On Fri, Jul 20, 2018 at 2:04 AM B Consultants 
wrote:

> Hello,
>
> We use Bpc (V4.1.5 and V3) to backup Linuxes and Windows boxes. All
> backups are made through rsync, even on our few Windows boxes.
> Everything is okay as far as data backups are concerned.
>
> When browsing the Windows backups through Bpc web interface, we found
> that they still show and contains *very old* data that have been deleted
> from the relevant computers several months ago. This holds true for full
> and incremental backups, as far as our (limited) checks have shown, for
> all our Windows machines and for BPC 4 and 3.
>
> This seems weird (especially wrt EU's GDPR). Did we make some mistake
> while configuring the backups ?
>
> Tia,
> --
> B Consultants - Sécurité informatique - www.ba-consultants.fr
> Tel. : +33 (0) 563 277 241 - Fax : +33 (0) 567 737 829
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] File Size/Count Reuse Summary

[Craig Barratt via BackupPC-users]

The screenshot you sent doesn't show the message "0 files in pool".  What
status information are you referring to?

Craig

On Thu, Jun 28, 2018 at 1:05 PM Kbtest Testar  wrote:

> Hi...
>
> I dont understand  , it says it 0 files in the pool but I have been
> running several backups so it should be files in the pool. is it somthing
> that is wrong?
>
> Version 4.2.1 using Rsync for backups of Linux hosts.
>
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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 4.2.1 perl issue

[Craig Barratt via BackupPC-users]

Mark,

It looks like your setting for $Conf{CgiImageDirURL} is wrong.  Your html
has hrefs like this:

href="/var/www/htdocs/BackupPC/image/favicon.ico


$Conf{CgiImageDirURL} should be set to the URL (eg: "/BackupPC/image"), not
the absolute file system path.

Craig

On Wed, Jun 13, 2018 at 5:27 AM, Mark Maciolek  wrote:

> hi,
>   Partially fixed. I put the correct BackupPC_Admin in place and the page
> loads, now just have to figure out why every image is 404.
>
> Mark
> > hi,
> >
> > First line:
> > #!/bin/perl
> > #=
> -*-perl-*-w
> > #
> >
> > selinux is in permissive mode
> >
> > manually run:
> >
> >
> > Content-Type: text/html; charset=utf-8
> >
> > 
> > 
> > BackupPC Server Status
> >  > href="/var/www/htdocs/BackupPC/image/BackupPC_stnd.css" title="CSSFile">
> >  > type="image/x-icon">
> > 
> > 
> >  > onLoad="document.getElementById('NavMenu').style.height=document.body.
> scrollHeight">
> >
> > 
> >  Â Â Â Â Â Â Â  
> >  Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â   > href="https://backuppc.github.io/backuppc/;> > src="/var/www/htdocs/BackupPC/image/logo.gif">
> >  Â Â Â Â Â Â Â  
> > 
> > Hosts
> > 
> >  Â Â Â  
> >  Â Â Â   > type="submit" value="Go" name="ignore">
> >  Â Â Â  
> > Server
> > Status
> > Host Summary
> > Documentation
> > https://github.com/backuppc/backuppc/wiki;>Wiki
> > https://backuppc.github.io/backuppc;>Homepage
> > 
> >  
> > 
> >  Â Â Â  BackupPC Server Status
> >
> >
> > 
> >  Â Â Â  Currently Running Jobs
> >
> > 
> > 
> >  Host 
> >  Â Â Â   Type 
> >  Â Â Â   User 
> >  Â Â Â   Start Time 
> >  Â Â Â   Command 
> >  Â Â Â   PID 
> >  Â Â Â   Xfer PID 
> >  Â Â Â   Status 
> >  Â Â Â   Count 
> >  Â Â Â  
> >
> > 
> >
> > 
> >
> >
> >  Â Â Â  Failures that need attention
> >
> > 
> > 
> >  Host 
> >  Â Â Â   Type 
> >  Â Â Â   User 
> >  Â Â Â   Last Try 
> >  Â Â Â   Details 
> >  Â Â Â   Error Time 
> >  Â Â Â   Last error (other than no ping) 
> >
> > 
> >
> > 
> >
> > apache is running as backuppc user.
> >
> > Mark
> >
> >
> > On 6/12/2018 10:25 PM, Craig Barratt via BackupPC-users wrote:
> >> Some random questions:
> >>
> >> What's the very first line of BackupPC_Admin?
> >>
> >> Could this be some sort of selinux issue?
> >>
> >> What happens when you manually run BackupPC_Admin (as the backuppc
> >> user)?  What user is apache running as?
> >>
> >> Craig
> >>
> >> On Tue, Jun 12, 2018 at 7:17 PM, mlm  >> <mailto:m...@sr.unh.edu>> wrote:
> >>
> >>
> >>
> >> On 6/12/2018 8:10 PM, Holger Parplies wrote:
> >>
> >> Hi,
> >>
> >> mlm wrote on 2018-06-12 17:20:06 -0400 [[BackupPC-users]
> >> backuppc 4.2.1 perl issue]:
> >>
> >> [...]
> >> New system running Scientific Linux 7.5, installed 4.2.1
> >> from tar file
> >>
> >> Global symbol "%In" requires explicit package name at
> >> /usr/share/BackupPC/sbin/BackupPC_Admin line 90.
> >> [...]
> >> Bareword "BackupPC::CGI::Lib::NewRequest" not allowed
> >> while "strict subs" in use at
> >> /usr/share/BackupPC/sbin/BackupPC_Admin line 56.
> >> [...]
> >> Any suggestions on troubleshooting further?
> >>
> >> what do the first few non-comment lines of your BackupPC_Admin
> >> look like
> >> (about 12, but I don't have 4.2.1 here right now, so that
> >> might have changed;
> >> up to the first "my" variable declaration)? It would seem that
> >> the
> >> BackupPC::CGI::Lib module is not correctly imported. Is the
> >> path in the
> >> "use lib" pragma correct for your installation? What are the
> >> permissions on
> >> the library file and its parent directories?
> >>
> >

Re: [BackupPC-users] backuppc 4.2.1 perl issue

[Craig Barratt via BackupPC-users]

Some random questions:

What's the very first line of BackupPC_Admin?

Could this be some sort of selinux issue?

What happens when you manually run BackupPC_Admin (as the backuppc user)?
What user is apache running as?

Craig

On Tue, Jun 12, 2018 at 7:17 PM, mlm  wrote:

>
>
> On 6/12/2018 8:10 PM, Holger Parplies wrote:
>
>> Hi,
>>
>> mlm wrote on 2018-06-12 17:20:06 -0400 [[BackupPC-users] backuppc 4.2.1
>> perl issue]:
>>
>>> [...]
>>> New system running Scientific Linux 7.5, installed 4.2.1 from tar file
>>>
>>> Global symbol "%In" requires explicit package name at
>>> /usr/share/BackupPC/sbin/BackupPC_Admin line 90.
>>> [...]
>>> Bareword "BackupPC::CGI::Lib::NewRequest" not allowed while "strict
>>> subs" in use at /usr/share/BackupPC/sbin/BackupPC_Admin line 56.
>>> [...]
>>> Any suggestions on troubleshooting further?
>>>
>> what do the first few non-comment lines of your BackupPC_Admin look like
>> (about 12, but I don't have 4.2.1 here right now, so that might have
>> changed;
>> up to the first "my" variable declaration)? It would seem that the
>> BackupPC::CGI::Lib module is not correctly imported. Is the path in the
>> "use lib" pragma correct for your installation? What are the permissions
>> on
>> the library file and its parent directories?
>>
>> What Perl version are you running ('perl -v')?
>>
>> Regards,
>> Holger
>>
>> hi
> from BackupPC_Admin:
>
> use strict;
> no  utf8;
> use CGI;
> use CGI::Carp qw(fatalsToBrowser);
> use lib "/usr/local/BackupPC/lib";
>
> use BackupPC::Lib;
> use BackupPC::CGI::Lib qw(:all);
>
> BackupPC::CGI::Lib::NewRequest;
>
> my %ActionDispatch = (
> "deleteBackup"   => "DeleteBackup",
>
> folders all owned by backupc:
> s -al /usr/local/BackupPC/lib/BackupPC/
> total 108
> drwxr-xr-x. 8 backuppc backuppc   160 Jun 12 21:40 .
> drwxr-xr-x. 4 backuppc backuppc33 Jun 12 16:09 ..
> drwxr-xr-x. 2 backuppc backuppc  4096 Jun 12 21:40 CGI
> drwxr-xr-x. 2 backuppc backuppc21 Jun 12 21:40 Config
> -r--r--r--. 1 backuppc backuppc 13638 Jun 12 21:40 DirOps.pm
> drwxr-xr-x. 2 backuppc backuppc   181 Jun 12 21:40 Lang
> -r--r--r--. 1 backuppc backuppc 38786 Jun 12 21:40 Lib.pm
> drwxr-xr-x. 2 backuppc backuppc21 Jun 12 21:40 Storage
> -r--r--r--. 1 backuppc backuppc  3014 Jun 12 21:40 Storage.pm
> -r--r--r--. 1 backuppc backuppc 36631 Jun 12 21:40 View.pm
> drwxr-xr-x. 2 backuppc backuppc   101 Jun 12 21:40 Xfer
> -r--r--r--. 1 backuppc backuppc  5002 Jun 12 21:40 Xfer.pm
> drwxr-xr-x. 2 backuppc backuppc27 Jun 12 21:40 Zip
>
>
> This is perl 5, version 16, subversion 3 (v5.16.3) built for
> x86_64-linux-thread-multi
> (with 33 registered patches, see perl -V for more detail)
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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 hangs on certain files.

[Craig Barratt via BackupPC-users]

Brent,

First you should tell us which versions of rsync, BackupPC and rsync-bpc
you are using.  If they are old, you should upgrade and try again.

Assuming you are using relatively recent versions (ie, at least 4.1.x), you
should run the restore with a high level of debug logging.  Specifically:

   - set $Conf{XferLogLevel} to 8
   - increase the rsync logging by adding -vvv to $Conf{RsyncRestoreArgs}
   - run a restore of that file, and send me the RestoreLOG file (don't
   post to the list)
   - then change the logging back, or else your next backup will generate a
   huge log file.

Craig

On Wed, May 30, 2018 at 7:15 AM, Brent Clark 
wrote:

> Good day Guys
>
> I am sitting with a very weird situation, and I am hoping someone can help.
>
> I needed to restore some files on an Ubuntu machine. Whats weird is,
> certain files just sit there and do not complete.
>
> e.g.
>
> lsof -ad3-999 -c rsync
>
> rsync   7372 root7u   REG  252,7  37486592 3174459
> /REMOVED/download/cougar/.COU-IMMPRO.pdf.NYSypa
>
> I went to the directory and selected one file to be stored, and as said
> rsync / backuppc just sit there.
>
> The above is a 38M pdf. And in this case always this file, thats a problem.
>
> If I select all the others files for the download directory, then there is
> no problem with the restore .
>
> I have been doing strace on rsync and backuppc_restore. It just sits
> there. I.e. Nothing happening / happens.
>
> I was thinking it was Ubuntus apparmour that was stopping the renaming
> '.COU-IMMPRO.pdf.NYSypa' to the correct name.
>
> I would like to say, backups is no problem, its just restore.
>
> If anyone can assist, it would be gratefully appreciated.
>
> Kind Regards
>
> Brent Clark
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] getaddrinfo is not a valid Socket macro after Update to version 4.0.0

[Craig Barratt via BackupPC-users]

Diane,

That problem is related to the old version of perl and Socket you are
running.

This was fixed in BackupPC version 4.1.1 last year (it detects which
version of Socket you are using, and defaults to old interface if
necessary).  I strongly recommend upgrading to the most recent version of
BackupPC (4.2.1), or the prior version (4.1.5).

Craig

On Wed, May 23, 2018 at 10:20 AM, Diane Leon  wrote:

> Hi,
>
> I am using BackupPC software for more that 4 years for my job and I never
> had problem but last week I had the bad idea to update the software to
> version 4.0.0 and now I have a problem running backups.
>
> I got the following error:
>
>  active1: getaddrinfo is not a valid Socket macro at
> /usr/share/BackupPC/lib/BackupPC/Lib.pm line 1412
>
> I have found an email with the same problem from 2017, I have the same
> perl version and socket, I have installed cpan and run install Socket but
> didn't help.
>
> Do you have another suggestion to resolve the problem? Do I have to
> install a new version of Perl?, I think I can install a new version in
> different directory but how BackupPC will point to it.
>
> ​
> root@sv02 usr]# perl -v
>
> This is perl, v5.10.1 (*) built for x86_64-linux-thread-multi
>
> Copyright 1987-2009, Larry Wall
>
> Perl may be copied only under the terms of either the Artistic License or
> the
> GNU General Public License, which may be found in the Perl 5 source kit.
>
> Complete documentation for Perl, including FAQ lists, should be found on
> this system using "man perl" or "perldoc perl".  If you have access to the
> Internet, point your browser at http://www.perl.org/, the Perl Home Page.
>
> [root@sv02 usr]# perl -e 'use Socket; print $Socket::VERSION . "\n"'
> 1.82
>
> Old Ticket with the error
> https://sourceforge.net/p/backuppc/mailman/message/35753460/
>
> ​I am using Centos 6.5
>
> Thanks for your help
>
> Diane Leon
> Senior Systems Administrator
> di...@tbi.ca
> (403) 702-3294
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Incremental backups succeed, full backups fail.

[Craig Barratt via BackupPC-users]

Please email me the entire XferLOG file (or the first ~100 lines if it's
too big).

Please also tell me your settings for
$Conf{XferMethod}, $Conf{RsyncArgs}, $Conf{RsyncFullArgsExtra},
$Conf{RsyncClientPath}, $Conf{RsyncSshArgs},
and $Conf{RsyncArgsExtra}.  What is your client's rsync version?

Craig

On Thu, May 17, 2018 at 5:54 AM, Micha Kersloot  wrote:

> Hi,
>
> I'm using BackupPC for several years now (upgraded to 4.1.5, but the
> problem existed before), but lately full backups of 2 servers started to
> fail. We are using rsync over ssh for all backups. Mainly Linux servers and
> some Windows server where we installed Cygwin sshd and rsync to facilitate
> the backup. We run little scripts to create a disk shadow before we start
> the backup and clear it when the backup is finished. I've moved one of the
> client servers to another BackupPC server and the backup runs without any
> problems on that server. I can use the second failing server to try to
> debug why the backup fails.
>
> So far I've upgraded the server from 3.xxx to 4.1.5, but that didn't
> change anything.
> Incremental backups always succeed.
> I've created a new 'server' in backuppc to have a clean starting point,
> but that full backup also never succeeded.
> I've changed the XferLogLevel to 7 to see if it shows anything, but the
> only error I can find is:
>   rsync_bpc: connection unexpectedly closed (5560630 bytes received so
> far) [receiver]
>   rsync error: error in rsync protocol data stream (code 12) at io.c(629)
> [receiver=3.0.9.12]
>   rsync_bpc: connection unexpectedly closed (342 bytes received so far)
> [generator]
>
> How can I debug this further to find the real problem?
>
> Any help is appreciated.
>
> Kind regards,
> Micha Kersloot
>
> *Chat with us via Telegram *
> 
>
> 
> www.kovoks.nl | www.mailcasa.eu | Follow @kovoks
>  on Twitter
> *E* mi...@kovoks.nl 
> *T* +31 (0)345 - 53 29 27 <+31%20(0)345%20-%2053%2029%2027>
> *A* Belle van Zuylenlaan 1-5  | 4105 JX
> Culemborg | The Netherlands 
>
> KvK 1104
>
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] how can I identify in which backup a certain file is?

[Craig Barratt via BackupPC-users]

BackupPC_zcat.

Craig

On Wed, May 16, 2018 at 10:30 PM, Michael Schumacher <
michael.schumac...@pamas.de> wrote:

> Thanks Robert,
>
> this is not very comfortable, but it works.
>
> I assume that there is no interest to have such a function integrated
> into BackupPC.
>
> Btw., what program uncompresses the XferLOG.*.z files? Neither gzip,
> zcat, unzip or any other tested tool works?
>
> Michael
>
> Tuesday, May 15, 2018, 4:26:16 PM, you wrote:
>
> RT> Perhaps scouring the XferLOG for lines marked 'new' would help?
>
> RT> Robert Trevellyan
>
> RT> On Tue, May 15, 2018 at 1:54 AM, Michael Schumacher
> RT>  wrote:
>
>
>
>  RT>> Not sure if this is helpful, but if you browse to a specific
>  RT>> folder for a host, you can then click a link to view that folder's
> history.
>
> RT>  thanks Robert, I was aware of that feature, but it only allows a per
> RT>  directory browsing. With a typical Windows directory structure, it is
> RT>  impossible to identify the one hidden directory that causes the
> RT>  trouble.
>
> RT>  What I have in mind is either a listing what files are actually new or
> RT>  some kind of display that would only show that part of the directory
> RT>  structure that was actually modified in a given backup.
>
>
> RT>   best regards
> RT>  ---
> RT>  Michael Schumacher
>
>
> RT>
> RT> 
> --
> RT>  Check out the vibrant tech community on one of the world's most
> RT>  engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> RT>  ___
> RT>  BackupPC-users mailing list
> RT> BackupPC-users@lists.sourceforge.net
> RT>  List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> RT>  Wiki:http://backuppc.wiki.sourceforge.net
> RT>  Project: http://backuppc.sourceforge.net/
>
>
>
>
>
>  best regards
> ---
> Michael Schumacher
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] since upgrading to 4.0 I can no longer do full backups

[Craig Barratt via BackupPC-users]

I'm glad that it's working now.

For OSX, the default rsync is really old.  On High Sierra 10.13.4, it's
rsync 2.6.9, circa 2006.  I strongly recommend installing a recent version
in, eg, /usr/local/bin.

Craig

On Tue, May 15, 2018 at 6:27 PM, An Ancient BackupPC User <
backu...@thefabfarrows.com> wrote:

>
> Ok so I can report my windows10 machines are completing full backups now
> without any other changes - THANK YOU :)
>
> My mac needs more work based on the way I have the daemon set up.  I will
> report back some time tomorrow, once I have had chance to work on it.
>
> Thanks again, I really appreciate your help and backup pc is the best,
> have used it for ever.
>
> Paul
>
>
> On May 15, 2018 at 4:45:46 PM, Craig Barratt via BackupPC-users (
> backuppc-users@lists.sourceforge.net) wrote:
>
> On your client the rsyncd.conf file should have a setting such as "charset
> = utf-8".  You'll need to make sure rsyncd reloads the rsyncd.conf file
> before retesting.
>
> If it still fails, the next thing to try is to remove --protect-args
> from $Conf{RsyncArgs}.
>
> Craig
>
> On Tue, May 15, 2018 at 1:17 PM, Paul Farrow <p...@thefabfarrows.com>
> wrote:
>
>> Ok I updated as you said and now I get this when trying to do a full
>> backup on my mac.
>>
>> This is the rsync child about to exec /usr/bin/rsync_bpc
>> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = >> 0
>> rsync: on remote machine: -slHogDtprc: unknown option
>>
>>
>>
>> On May 15, 2018 at 3:28:04 PM, Craig Barratt via BackupPC-users (
>> backuppc-users@lists.sourceforge.net) wrote:
>>
>> Ok, you are using rsyncd, so $Conf{RsyncSshArgs} doesn't matter.
>>
>> It seems that when you upgraded to 4.0 the config file was not updated
>> (or perhaps these are per-host settings, which don't get updated during an
>> upgrade).  The correct settings should be:
>>
>> $Conf{RsyncFullArgsExtra} = [
>> '--checksum',
>> ];
>>
>> #
>> # Arguments to rsync for backup.  Do not edit the first set unless you
>> # have a good understanding of rsync options.
>> #
>> $Conf{RsyncArgs} = [
>> '--super',
>> '--recursive',
>> '--protect-args',
>> '--numeric-ids',
>> '--perms',
>> '--owner',
>> '--group',
>> '-D',
>> '--times',
>> '--links',
>> '--hard-links',
>> '--delete',
>> '--delete-excluded',
>> '--partial',
>> '--log-format=log: %o %i %B %8U,%8G %9l %f%L',
>> '--stats',
>> ];
>>
>> Craig
>>
>>
>> On Tue, May 15, 2018 at 10:26 AM, An Ancient BackupPC User <
>> backu...@thefabfarrows.com> wrote:
>>
>>> Thanks Craig for such a quick response.
>>>
>>> I upgraded some time ago but have been pretty lazy in posting to the
>>> mailing list about it.
>>>
>>> XferLOG file /somefolder/XferLOG.840.z created 2018-05-15 11:51:27
>>>
>>> Backup prep: type = full, case = 4, inPlace = 0, doDuplicate = 0, 
>>> newBkupNum = 840, newBkupIdx = 45, lastBkupNum = 839, lastBkupIdx = 44 
>>> (FillCycle = , noFillCnt = 20)
>>> Running: /usr/bin/rsync_bpc --bpc-top-dir /somefolder --bpc-host-name 
>>> somehost --bpc-share-name auser --bpc-bkup-num 840 --bpc-bkup-comp 3 
>>> --bpc-bkup-prevnum 839 --bpc-bkup-prevcomp 3 --bpc-bkup-inode0 693052 
>>> --bpc-attrib-new --bpc-log-level 2 --numeric-ids --perms --owner --group -D 
>>> --links --hard-links --times --block-size=2048 --recursive  --timeout=72000 
>>> --password-file=/passwordfile --exclude=Virtual\ Machines/ 
>>> --exclude=.Trash/ --exclude=Downloads/ --exclude=updater/ 
>>> --exclude=Library/ --exclude=Movies/BBC\ iPlayer\ Downloads/ 
>>> --exclude=Microsoft\ User\ Data/ --exclude=AdobeStockPhotos/ 
>>> --exclude=Data.noindex/ --exclude=.nuget/ --exclude=.dnx/ 
>>> --exclude=.Android/ auser@somehost@::auser /
>>> full backup started for directory some directory
>>> Xfer PIDs are now 17304
>>>
>>>
>>> RsyncSshArgs - non existent in config.pl and clients config.
>>> RsyncClientPath - $Conf{RsyncClientPath} = 'rsync';
>>> RsyncBackupPCPath - $Conf{RsyncBackupPCPath} = '/usr/bin/rsync_bpc';
>>> RsyncFullArgsExtra - non existent
>>> RsyncArgsExtra = $Conf{RsyncArgsExtra} = [];
>>> RsyncArgs - $Conf{RsyncArgs} = [
>>

Re: [BackupPC-users] since upgrading to 4.0 I can no longer do full backups

[Craig Barratt via BackupPC-users]

On your client the rsyncd.conf file should have a setting such as "charset
= utf-8".  You'll need to make sure rsyncd reloads the rsyncd.conf file
before retesting.

If it still fails, the next thing to try is to remove --protect-args
from $Conf{RsyncArgs}.

Craig

On Tue, May 15, 2018 at 1:17 PM, Paul Farrow <p...@thefabfarrows.com> wrote:

> Ok I updated as you said and now I get this when trying to do a full
> backup on my mac.
>
> This is the rsync child about to exec /usr/bin/rsync_bpc
> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
> rsync: on remote machine: -slHogDtprc: unknown option
>
>
>
> On May 15, 2018 at 3:28:04 PM, Craig Barratt via BackupPC-users (
> backuppc-users@lists.sourceforge.net) wrote:
>
> Ok, you are using rsyncd, so $Conf{RsyncSshArgs} doesn't matter.
>
> It seems that when you upgraded to 4.0 the config file was not updated (or
> perhaps these are per-host settings, which don't get updated during an
> upgrade).  The correct settings should be:
>
> $Conf{RsyncFullArgsExtra} = [
> '--checksum',
> ];
>
> #
> # Arguments to rsync for backup.  Do not edit the first set unless you
> # have a good understanding of rsync options.
> #
> $Conf{RsyncArgs} = [
> '--super',
> '--recursive',
> '--protect-args',
> '--numeric-ids',
> '--perms',
> '--owner',
> '--group',
> '-D',
> '--times',
> '--links',
> '--hard-links',
> '--delete',
> '--delete-excluded',
> '--partial',
> '--log-format=log: %o %i %B %8U,%8G %9l %f%L',
> '--stats',
> ];
>
> Craig
>
>
> On Tue, May 15, 2018 at 10:26 AM, An Ancient BackupPC User <
> backu...@thefabfarrows.com> wrote:
>
>> Thanks Craig for such a quick response.
>>
>> I upgraded some time ago but have been pretty lazy in posting to the
>> mailing list about it.
>>
>> XferLOG file /somefolder/XferLOG.840.z created 2018-05-15 11:51:27
>>
>> Backup prep: type = full, case = 4, inPlace = 0, doDuplicate = 0, newBkupNum 
>> = 840, newBkupIdx = 45, lastBkupNum = 839, lastBkupIdx = 44 (FillCycle = , 
>> noFillCnt = 20)
>> Running: /usr/bin/rsync_bpc --bpc-top-dir /somefolder --bpc-host-name 
>> somehost --bpc-share-name auser --bpc-bkup-num 840 --bpc-bkup-comp 3 
>> --bpc-bkup-prevnum 839 --bpc-bkup-prevcomp 3 --bpc-bkup-inode0 693052 
>> --bpc-attrib-new --bpc-log-level 2 --numeric-ids --perms --owner --group -D 
>> --links --hard-links --times --block-size=2048 --recursive  --timeout=72000 
>> --password-file=/passwordfile --exclude=Virtual\ Machines/ --exclude=.Trash/ 
>> --exclude=Downloads/ --exclude=updater/ --exclude=Library/ 
>> --exclude=Movies/BBC\ iPlayer\ Downloads/ --exclude=Microsoft\ User\ Data/ 
>> --exclude=AdobeStockPhotos/ --exclude=Data.noindex/ --exclude=.nuget/ 
>> --exclude=.dnx/ --exclude=.Android/ auser@somehost@::auser /
>> full backup started for directory some directory
>> Xfer PIDs are now 17304
>>
>>
>> RsyncSshArgs - non existent in config.pl and clients config.
>> RsyncClientPath - $Conf{RsyncClientPath} = 'rsync';
>> RsyncBackupPCPath - $Conf{RsyncBackupPCPath} = '/usr/bin/rsync_bpc';
>> RsyncFullArgsExtra - non existent
>> RsyncArgsExtra = $Conf{RsyncArgsExtra} = [];
>> RsyncArgs - $Conf{RsyncArgs} = [
>>
>>   '--numeric-ids',
>>
>>   '--perms',
>>
>>   '--owner',
>>
>>   '--group',
>>
>>   '-D',
>>
>>   '--links',
>>
>>   '--hard-links',
>>
>>   '--times',
>>
>>   '--block-size=2048',
>>
>>   '--recursive'
>>
>> ];
>>
>>
>> Appreciate your help - thanks
>>
>> Paul
>>
>> On May 15, 2018 at 1:04:19 PM, Craig Barratt via BackupPC-users (
>> backuppc-users@lists.sourceforge.net) wrote:
>>
>> Please send the first part of the log file with the full rsync command
>> (feel free to redact confidential arguments, but maintain any special
>> characters etc).
>>
>> Also send this client's settings for $Conf{RsyncSshArgs}, $Conf{Rsy
>> ncClientPath}, $Conf{RsyncBackupPCPath}, $Conf{RsyncFullArgsExtra}
>> and $Conf{RsyncArgs}.
>>
>> Craig
>>
>> On Tue, May 15, 2018 at 9:26 AM, An Ancient BackupPC User <
>> backu...@thefabfarrows.com> wrote:
>>
>>>
>>> Since I upgraded to 4.0 I can no longer do full backups only
>>> incremental.  I was wondering if any one else has had this

Re: [BackupPC-users] since upgrading to 4.0 I can no longer do full backups

[Craig Barratt via BackupPC-users]

Ok, you are using rsyncd, so $Conf{RsyncSshArgs} doesn't matter.

It seems that when you upgraded to 4.0 the config file was not updated (or
perhaps these are per-host settings, which don't get updated during an
upgrade).  The correct settings should be:

$Conf{RsyncFullArgsExtra} = [
'--checksum',
];

#
# Arguments to rsync for backup.  Do not edit the first set unless you
# have a good understanding of rsync options.
#
$Conf{RsyncArgs} = [
'--super',
'--recursive',
'--protect-args',
'--numeric-ids',
'--perms',
'--owner',
'--group',
'-D',
'--times',
'--links',
'--hard-links',
'--delete',
'--delete-excluded',
'--partial',
'--log-format=log: %o %i %B %8U,%8G %9l %f%L',
'--stats',
];

Craig


On Tue, May 15, 2018 at 10:26 AM, An Ancient BackupPC User <
backu...@thefabfarrows.com> wrote:

> Thanks Craig for such a quick response.
>
> I upgraded some time ago but have been pretty lazy in posting to the
> mailing list about it.
>
> XferLOG file /somefolder/XferLOG.840.z created 2018-05-15 11:51:27
>
> Backup prep: type = full, case = 4, inPlace = 0, doDuplicate = 0, newBkupNum 
> = 840, newBkupIdx = 45, lastBkupNum = 839, lastBkupIdx = 44 (FillCycle = , 
> noFillCnt = 20)
> Running: /usr/bin/rsync_bpc --bpc-top-dir /somefolder --bpc-host-name 
> somehost --bpc-share-name auser --bpc-bkup-num 840 --bpc-bkup-comp 3 
> --bpc-bkup-prevnum 839 --bpc-bkup-prevcomp 3 --bpc-bkup-inode0 693052 
> --bpc-attrib-new --bpc-log-level 2 --numeric-ids --perms --owner --group -D 
> --links --hard-links --times --block-size=2048 --recursive  --timeout=72000 
> --password-file=/passwordfile --exclude=Virtual\ Machines/ --exclude=.Trash/ 
> --exclude=Downloads/ --exclude=updater/ --exclude=Library/ 
> --exclude=Movies/BBC\ iPlayer\ Downloads/ --exclude=Microsoft\ User\ Data/ 
> --exclude=AdobeStockPhotos/ --exclude=Data.noindex/ --exclude=.nuget/ 
> --exclude=.dnx/ --exclude=.Android/ auser@somehost@::auser /
> full backup started for directory some directory
> Xfer PIDs are now 17304
>
>
> RsyncSshArgs - non existent in config.pl and clients config.
> RsyncClientPath - $Conf{RsyncClientPath} = 'rsync';
> RsyncBackupPCPath - $Conf{RsyncBackupPCPath} = '/usr/bin/rsync_bpc';
> RsyncFullArgsExtra - non existent
> RsyncArgsExtra = $Conf{RsyncArgsExtra} = [];
> RsyncArgs - $Conf{RsyncArgs} = [
>
>   '--numeric-ids',
>
>   '--perms',
>
>   '--owner',
>
>   '--group',
>
>   '-D',
>
>   '--links',
>
>   '--hard-links',
>
>   '--times',
>
>   '--block-size=2048',
>
>   '--recursive'
>
> ];
>
>
> Appreciate your help - thanks
>
> Paul
>
> On May 15, 2018 at 1:04:19 PM, Craig Barratt via BackupPC-users (
> backuppc-users@lists.sourceforge.net) wrote:
>
> Please send the first part of the log file with the full rsync command
> (feel free to redact confidential arguments, but maintain any special
> characters etc).
>
> Also send this client's settings for $Conf{RsyncSshArgs}, $Conf{
> RsyncClientPath}, $Conf{RsyncBackupPCPath}, $Conf{RsyncFullArgsExtra}
> and $Conf{RsyncArgs}.
>
> Craig
>
> On Tue, May 15, 2018 at 9:26 AM, An Ancient BackupPC User <
> backu...@thefabfarrows.com> wrote:
>
>>
>> Since I upgraded to 4.0 I can no longer do full backups only
>> incremental.  I was wondering if any one else has had this issue.
>>
>> The error I have in the logs is
>>
>> This is the rsync child about to exec /usr/bin/rsync_bpc
>> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = >> 0
>> Unexpected remote arg: changed@changedtoprotecttheinnocent::changed
>> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
>> sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 693052 inode
>> rsync error: syntax or usage error (code 1) at main.c(1219) [sender=3.0.9.12]
>> rsync_bpc exited with fatal status 1 (256) (rsync error: syntax or usage 
>> error (code 1) at main.c(1219) [sender=3.0.9.12])
>> Xfer PIDs are now
>> Got fatal error during xfer (No files dumped for share changed)
>> Backup aborted (No files dumped for share changed)
>> BackupFailCleanup: nFilesTotal = 0, type = full, BackupCase = 4, inPlace = 
>> 0, lastBkupNum = 839
>> Removing empty backup #839
>>
>> Incrementals appear to work fine.
>>
>> Thank you in advance
>>
>> Paul
>>
>>
>>
>> 
>> -

Re: [BackupPC-users] since upgrading to 4.0 I can no longer do full backups

[Craig Barratt via BackupPC-users]

Please send the first part of the log file with the full rsync command
(feel free to redact confidential arguments, but maintain any special
characters etc).

Also send this client's settings for
$Conf{RsyncSshArgs}, $Conf{RsyncClientPath}, $Conf{RsyncBackupPCPath},
$Conf{RsyncFullArgsExtra}
and $Conf{RsyncArgs}.

Craig

On Tue, May 15, 2018 at 9:26 AM, An Ancient BackupPC User <
backu...@thefabfarrows.com> wrote:

>
> Since I upgraded to 4.0 I can no longer do full backups only incremental.
> I was wondering if any one else has had this issue.
>
> The error I have in the logs is
>
> This is the rsync child about to exec /usr/bin/rsync_bpc
> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
> Unexpected remote arg: changed@changedtoprotecttheinnocent::changed
> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
> sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 693052 inode
> rsync error: syntax or usage error (code 1) at main.c(1219) [sender=3.0.9.12]
> rsync_bpc exited with fatal status 1 (256) (rsync error: syntax or usage 
> error (code 1) at main.c(1219) [sender=3.0.9.12])
> Xfer PIDs are now
> Got fatal error during xfer (No files dumped for share changed)
> Backup aborted (No files dumped for share changed)
> BackupFailCleanup: nFilesTotal = 0, type = full, BackupCase = 4, inPlace = 0, 
> lastBkupNum = 839
> Removing empty backup #839
>
> Incrementals appear to work fine.
>
> Thank you in advance
>
> Paul
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] BackupPC 4.2.1 released

[Craig Barratt via BackupPC-users]

BackupPC 4.2.1  has
been released on Github.

The changes since 4.2.0
 are listed
below.  This release allows the new backup delete CGI feature to be
disabled for users and/or admins, plus a couple of minor bug fixes.

Enjoy!

Craig

#
# Version 4.2.1, 7 May 2018
#

This release allows the new backup delete CGI feature to be disabled for
users and/or admins, plus a couple of minor bug fixes:

   - Merged pull request #195
   .
   - Added new config variable $Conf{CgiUserDeleteBackupEnable} that sets
   whether users and admins can delete backups via the CGI interface. The
   default value is 0, which means it's disabled for regular users but
   available for admins.
   - Fixed delete backup bug in bin/BackupPC_Admin_SCGI reported by Julian
   Zielke in issue #193 .
   - Added check to dirCacheFlush() in bin/BackupPC_tarExtract to skip
   files that don't have attributes; reported by Tarak Patel.
   - Removed extraneous duplicate variable assignment in
   lib/BackupPC/CGI/GeneralInfo.pm, from @moisseev
    (#195
   ).
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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 4.2.0 released

[Craig Barratt via BackupPC-users]

As usual, Holger makes some very good points.  I just pushed some additional
changes
<https://github.com/backuppc/backuppc/commit/953a5cb976a76ca3175c984cd84e9bbe070ee241>
so that CgiUserDeleteBackupEnable can be set to a negative value to disable
the backup delete feature for everyone, including admins.

Craig

On Thu, May 3, 2018 at 3:48 PM, Holger Parplies <wb...@parplies.de> wrote:

> Hi,
>
> Steve Palm wrote on 2018-05-03 09:55:38 -0500 [Re: [BackupPC-users]
> BackupPC 4.2.0 released]:
> > I think that would cover it here, as you said, if you give someone Admin
> > rights, then they can alter any other settings. Only a
> > compile-build-install-time option to totally remove it would eliminate
> this
> > possibility.
>
> well, not really. If you can change the host settings, you can probably
> change
> backup expiry to keep only one or two backups, change the data set to only
> include /tmp, for example, and then manually force one or two backups. It's
> not as fast and easy as a "maliciously delete all backups" button, but if
> we're talking about security, it doesn't have to be easy, just possible.
> With root access to the BackupPC server, it's just a matter of 'rm -r',
> really. If you give someone 'Admin' capabilities (for whatever definition
> may be applicable), he can administratively break things. There is really
> no way to tell a computer to let someone only do constructive things.
> 'gzip /etc/passwd' is a good thing, right? ;-)
>
> For the 'home use' type scenario (as in "backup *PC*"), where people "own"
> machines they backup and restore as they like, there may be some merit in
> allowing them to delete backups on their own.
>
> For the 'office' type scenario (as in "*Backup* pc"), I would expect an IT
> department (or some member(s) of it) to be responsible for backups, and
> *nobody* else to have any access to them. The access control mechanism in
> BackupPC is just not fine-grained enough - if you can see any data within a
> backup, you can see all of it. In this scenario, you probably won't ever
> manually delete backups, and if you do, you'll do it through shell access
> to the BackupPC server from the command line. So you'll have a gratuitious
> "shoot myself in the foot" button in the web interface, nothing more.
>
> There will always be people who use BackupPC somewhere in between those
> scenarios, so yes, why not give them the option of deleting backups through
> the web interface?
>
> > It is a great feature to have, especially with some restrictions on
> > availability. Thanks!
> >
> > > On Apr 21, 2018, at 7:43 PM, Craig Barratt via BackupPC-users <
> backuppc-users@lists.sourceforge.net> wrote:
> > >
> > > I just pushed some changes [...] that add a new config variable
> > > CgiUserDeleteBackupEnable (default off) which sets whether users can
> > > delete backups via the CGI interface.
>
> I agree that this makes sense (both the option and the default).
>
> > >  Admins always have the delete feature enabled.
>
> Absurdly, I'd suggest to always *dis*able the feature for admins. Well, no,
> that doesn't make much sense, either. But it's so easy - even for admins -
> to press the wrong button (just imagine an unresponsive browser or X
> server)
> and then answer the confirmation dialog the wrong way. If a site has the
> policy (or maybe even legal requirement) "we *never* manually delete
> backups",
> they should be able to prevent this from happening accidentally (or
> maliciously, if you prefer).
>
> In fact, it's possible to disable direct restores, which can do great harm,
> so I'd argue it should be possible to disable backup deletion, too.
>
> Disclaimer: no, I haven't looked at the new version or its web interface,
> so
> reality might be less problematic than the theory sounds. But even if it's
> hard to shoot yourself in the foot, someone will manage ;-).
>
> > > On Fri, Apr 20, 2018 at 11:05 AM, Craig Barratt <
> cbarr...@users.sourceforge.net <mailto:cbarr...@users.sourceforge.net>>
> wrote:
> > > [...]
> > > How about I add a configuration setting that has three values -
> completely
> > > off, admin only, or any user?  The default setting could be admin only.
>
> I would prefer that implementation. Personally, I'd make the default
> setting
> "completely off", though I trust people really *wanting* that setting could
> easily enough change it, if the default were different. In a way, the
> default
> setting seems to be a recommendation. Is manually deleting backups that are
> no longer needed something the average BackupPC admin 

Re: [BackupPC-users] about installation of backuppc 4.2.0 on CentOS 7

[Craig Barratt via BackupPC-users]

Luigi,

It looks like the CGI script is running correctly, but the static web data
(CSS, images etc) are not being loaded.

Inspect the page source.  The first few lines should include things like
this:







On the BackupPC side, the path to those files in the html is specified
by $Conf{CgiImageDirURL} (in the example above it is set to '/BackupPC').
The files (like logo.gif, BackupPC_stnd.css) should be stored in the
path $Conf{CgiImageDir} (eg, /var/www/html/BackupPC but that depends on
your install).

So this URL should get you the BackupPC logo:

http://HOSTNAME/BackupPC/logo.gif


You should confirm that the apache configuration (eg, DocumentRoot)
correctly maps regular html requests so that these are correctly served
from the $Conf{CgiImageDir} directory.  Check your permissions too.

Craig

On Wed, May 2, 2018 at 6:03 AM, Luigi Augello 
wrote:

> Hello
> I installed BackupPC-4.2.0 on a Centos 7 server, I followed the
> instructions step by step several times and every timei have the GUI
> attached. Any suggestion?
>
> thanks
> Luigi
> --
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] tarExtract: Can't use an undefined value as a HASH

[Craig Barratt via BackupPC-users]

I make this change
<https://github.com/backuppc/backuppc/commit/c7ee020aadc23eee64850d5f0fc59df79c35ba04>
which likely fixes the issue.  But it would still be helpful to get the
more detailed XferLOG details so I can confirm what went wrong.

Craig

On Fri, Apr 27, 2018 at 10:37 AM, Patel, Tarak (SSC/SPC) <
tarak.pa...@canada.ca> wrote:

> Hi Craig,
>
>
>
> I will collect logs with XferLogLevel set to 5 of a failure and keep you
> posted.
>
>
>
> Thanks,
>
>
> Tarak
>
>
>
> *From:* Craig Barratt via BackupPC-users [mailto:backuppc-users@lists.
> sourceforge.net]
> *Sent:* 27 April, 2018 00:15
> *To:* General list for user discussion, questions and support <
> backuppc-users@lists.sourceforge.net>
> *Cc:* Craig Barratt <cbarr...@users.sourceforge.net>
> *Subject:* Re: [BackupPC-users] tarExtract: Can't use an undefined value
> as a HASH
>
>
>
> Can you increase the log level (XferLogLevel) to, eg, 5 and send me either
> the whole log file, or at a minimum the last few hundred lines up to and
> including the error?  Just send it directly to me, and not to the list, or
> we could use Google drive or dropbox etc.
>
> Thanks,
> Craig
>
>
>
> On Thu, Apr 26, 2018 at 8:39 AM, Patel, Tarak (SSC/SPC) <
> tarak.pa...@canada.ca> wrote:
>
> Hi all,
>
>
>
> I’ve been testing BackupPC (Version 4.2.0 ) for 2-3 weeks now and I’m
> seeing ‘tarExtract: Can't use an undefined value as a HASH’ error every so
> often. In order to ensure a consistent backup I use one of the snapshots
> from the filesystem of interest. Below is an ‘partial’ log from one such
> failure:
>
>
>
> cmdExecOrEval: about to exec /usr/local/openssh-7.5p1/bin/ssh -o
> NoneSwitch=yes -o NoneEnabled=yes -q -x -n -l root  env LC_ALL=C
> /bin/tar --one-file-system --ignore-failed-read -c -v -f - -C 
> /.snapshots/@GMT-\`date --date=yesterday \'+%Y.%m.%d\'\`-06\* --totals .
>
>
>
> tarExtract: Can't use an undefined value as a HASH reference at
> /usr/local/BackupPC/bin/BackupPC_tarExtract line 1078.
>
> BackupPC_tarExtract exited with fail status 512
>
> readOutput: sysread returns 0 and got EOF
>
> Tar exited with error 65280 () status
>
> Xfer PIDs are now
>
> xferPids
>
> Got fatal error during xfer (BackupPC_tarExtract exited with fail status
> 512)
>
> cmdSystemOrEval: about to system /bin/ping -c 1 homeprotox.science.gc.ca
>
> cmdSystemOrEval: about to system /bin/ping -c 1 homeprotox.science.gc.ca
>
> CheckHostAlive: ran '/bin/ping -c 1 homeprotox.science.gc.ca'; returning
> 0.599
>
> Backup aborted (BackupPC_tarExtract exited with fail status 512)
>
> __bpc_progress_state__ fail cleanup
>
> BackupFailCleanup: nFilesTotal = 11521, type = full, BackupCase = 6,
> inPlace = 1, lastBkupNum =
>
> BackupFailCleanup: inPlace with some new files... no cleanup and marking
> partial
>
>
>
>
>
> Any insight is greatly appreciated.
>
>
>
> Thank you,
>
>
>
> Tarak
>
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] tarExtract: Can't use an undefined value as a HASH

[Craig Barratt via BackupPC-users]

Can you increase the log level (XferLogLevel) to, eg, 5 and send me either
the whole log file, or at a minimum the last few hundred lines up to and
including the error?  Just send it directly to me, and not to the list, or
we could use Google drive or dropbox etc.

Thanks,
Craig

On Thu, Apr 26, 2018 at 8:39 AM, Patel, Tarak (SSC/SPC) <
tarak.pa...@canada.ca> wrote:

> Hi all,
>
> I’ve been testing BackupPC (Version 4.2.0 ) for 2-3 weeks now and I’m
> seeing ‘tarExtract: Can't use an undefined value as a HASH’ error every so
> often. In order to ensure a consistent backup I use one of the snapshots
> from the filesystem of interest. Below is an ‘partial’ log from one such
> failure:
>
> cmdExecOrEval: about to exec /usr/local/openssh-7.5p1/bin/ssh -o
> NoneSwitch=yes -o NoneEnabled=yes -q -x -n -l root  env LC_ALL=C
> /bin/tar --one-file-system --ignore-failed-read -c -v -f - -C
> /.snapshots/@GMT-\`date --date=yesterday \'+%Y.%m.%d\'\`-06\*
> --totals .
>
> tarExtract: Can't use an undefined value as a HASH reference at
> /usr/local/BackupPC/bin/BackupPC_tarExtract line 1078.
> BackupPC_tarExtract exited with fail status 512
> readOutput: sysread returns 0 and got EOF
> Tar exited with error 65280 () status
> Xfer PIDs are now
> xferPids
> Got fatal error during xfer (BackupPC_tarExtract exited with fail status
> 512)
> cmdSystemOrEval: about to system /bin/ping -c 1 homeprotox.science.gc.ca
> cmdSystemOrEval: about to system /bin/ping -c 1 homeprotox.science.gc.ca
> CheckHostAlive: ran '/bin/ping -c 1 homeprotox.science.gc.ca'; returning
> 0.599
> Backup aborted (BackupPC_tarExtract exited with fail status 512)
> __bpc_progress_state__ fail cleanup
> BackupFailCleanup: nFilesTotal = 11521, type = full, BackupCase = 6,
> inPlace = 1, lastBkupNum =
> BackupFailCleanup: inPlace with some new files... no cleanup and marking
> partial
>
>
> Any insight is greatly appreciated.
>
> Thank you,
>
> Tarak
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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 4.2.0 released

[Craig Barratt via BackupPC-users]

This is a very good point.

How about I add a configuration setting that has three values - completely
off, admin only, or any user?  The default setting could be admin only.

However, if it's turned off, any admin could change that setting back to
admin only.

Craig

On Monday, April 16, 2018, Steve Palm <n9...@n9yty.com> wrote:

>
> On Apr 16, 2018, at 7:47 AM, Ghislain Adnet <gad...@aqueos.com> wrote:
> > Le 15/04/2018 à 01:10, Craig Barratt via BackupPC-users a écrit :
> >> BackupPC 4.2.0 <https://github.com/backuppc/backuppc/releases/tag/4.2.0>
> has been released on Github.
> >> The changes since4.1.5 <https://github.com/backuppc/
> backuppc/releases/tag/4.1.5>are listed below.  The biggest change is a
> new feature in the web interface written by @moisseev that allows prior
> backups to be deleted.
> >
> > ohhh this is a very bad idea... Having a way to remove backup in the web
> interface  sounds cool but when a bad apple employee comes and destroy all
> the backups because he is angry this is a real issue. Same if account is
> comprimised
>  .
>  .
>  .
> >  is there a way to remove the feature so its not even loaded in the code
> (not just limited by the login/pass used) ?
>
>  I didn't see where it was even configurable by user/login/etc...  If it
> is, please post, and also a global "shutoff" would be great. Maybe a
> compile/install option to not even include it as requested above, although
> for our use case I don't think we need to go that far, hope I'm not ever
> proven wrong on that. :)
>
>  Thanks!
>  Steve
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Cryptic logs

[Craig Barratt via BackupPC-users]

It's probably benign (sorry I can't be very definitive).  Just to be safe,
you could browse the backup tree to make sure those files are stored
correctly.

This is pretty old code; you should consider upgrading to 4.x.

Craig

On Sat, Apr 14, 2018 at 3:00 PM, B  wrote:

> Hi list,
>
> The digest gives 1 error for a machine, but it's logs show several
> cryptic lines I don't understand very much, such as:
>
> …
> Xfer PIDs are now 10411,10498
> [ skipped 6075 lines ]
> Unexpected call
> BackupPC::Xfer::RsyncFileIO->unlink(usr/lib/python2.7/dist-
> packages/xlwt/BIFFRecords.py)
> Unexpected call
> BackupPC::Xfer::RsyncFileIO->unlink(usr/lib/python2.7/dist-
> packages/xlwt/Bitmap.py)
> Unexpected call
> BackupPC::Xfer::RsyncFileIO->unlink(usr/lib/python2.7/dist-
> packages/xlwt/Cell.py)
> Unexpected call
> BackupPC::Xfer::RsyncFileIO->unlink(usr/lib/python2.7/dist-
> packages/xlwt/Column.py)
> …
> [~a good dozen of such lines]
>
>
> What does it really mean ?
>
> Is it something I should fear ?
>
> Jean-Yves
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] BackupPC 4.2.0 released

[Craig Barratt via BackupPC-users]

BackupPC 4.2.0  has
been released on Github.

The changes since 4.1.5
 are listed
below.  The biggest change is a new feature in the web interface
written by @moisseev
that allows prior backups to be deleted.

Enjoy!

Craig

#
# Version 4.2.0, 8 Apr 2018
#

Merged pull requests #160, #190.

* Backups can now be deleted via the CGI interface, written by @moisseev
  (#160).

* bin/BackupPC_backupDelete: added -L option that puts output into client
  LOG file, to support CGI backup deletion.

* Added support for a user-editable comment per host, via a new
ClientComment
  config parameter, requested by @andrewmaksymowsky.

* bin/BackupPC_tarExtract: Added support for pax headers, which smbclient
  uses for long file names

* bin/BackupPC_backupDelete: make sure directory exists when renaming tree
  from deleted backup.

* lib/BackupPC/Xfer/Smb.pm: ignore empty output lines from smbclient;
  fixes issue #159.

* bin/BackupPC: improved several of the exit error messages.

* lib/BackupPC/Xfer/Rsync.pm: added shareName to RsyncArgs* argument
  substitutions; suggested by Alex Kobel.

* conf/BackupPC_stnd.css: removed import url('
https://fonts.googleapis.com/css'
  suggested by @MartijnRas in issue #174.
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Delete files from Backups

[Craig Barratt via BackupPC-users]

4.x includes BackupPC_backupDelete, which is the reliable way to delete
entire backups, or portions of backups.  Since 4.x maintains reference
counts instead of using hardlinks, BackupPC_backupDelete has to be careful
to update the reference counts after deleting something.

Here's the usage:

usage: BackupPC_backupDelete -h host -n num [-p] [-l] [-L] [-r] [-s
shareName [dirs...]]
  Options:
 -h host host name
 -n num  backup number to delete
 -s shareNamedon't delete the backup; delete just this share
 (or only dirs below this share if specified)
 -p  don't print progress information
 -L  log output to host's LOG file (instead of stdout)
 -l  don't remove XferLOG files
 -r  do a ref count update (default: none)
  If a shareName is specified, just that share (or share/dirs) are deleted.
  The backup itself is not deleted, nor is the log file removed.


In 3.x, it's relatively easy and safe to delete portions of backups.  The
BackupPC_deleteFile.pl mentioned by GW Haywood isn't built into 3.x, but is
worth checking out.

Craig

On Fri, Mar 30, 2018 at 5:26 AM, G.W. Haywood via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:

> Hi there,
>
> On Fri, 30 Mar 2018, Stefan Schumacher wrote:
>
> ... Are there any other, better ways I should consider when
>> sanitizing my backups? ...
>>
>
> #!/usr/bin/perl
> #= -*-perl-*-
> #
> # BackupPC_deleteFile.pl: Delete one or more files/directories from
> # a range of hosts, backups, and shares
> #
> # DESCRIPTION
> #   See below for detailed description of what it does and how it works
> #
> # AUTHOR
> #   Jeff Kosowsky
> # [...]
>
> --
>
> 73,
> Ged.
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Can't switch users to BackupPC in terminal?

[Craig Barratt via BackupPC-users]

Marc,

What is in the XferLOG file for the failed backup?

Craig

On Tue, Mar 13, 2018 at 2:58 PM, Robert Trevellyan <
robert.trevell...@gmail.com> wrote:

> That's actually a slightly different error (io.c(1556) instead of
> io.c(629)). It's possible that browsing the source code of io.c would offer
> a clue, but it's a pretty generic error, so it's probably time to enable
> verbose logging on both ends and do some proper debugging. I'd do that by
> running rsync at the command-line.
>
> Robert Trevellyan
>
> On Tue, Mar 13, 2018 at 11:13 AM, Marc Gilliatt 
> wrote:
>
>> I've set the timeout on my backuppc server to 604800 which is one week.
>> One of my clients has just completed its first full backup. However, my
>> other clients are still receiving the same rysnc error as before...
>>
>>
>> 2018-03-13 15:11:29 Got fatal error during xfer (rsync error: error in rsync 
>> protocol data stream (code 12) at io.c(1556) [generator=3.0.9.11])
>> 2018-03-13 15:11:34 Backup aborted (rsync error: error in rsync protocol 
>> data stream (code 12) at io.c(1556) [generator=3.0.9.11])
>>
>>
>> --
>> *From:* Robert Trevellyan 
>> *Sent:* 13 March 2018 14:44:54
>> *To:* General list for user discussion, questions and support
>> *Subject:* Re: [BackupPC-users] Can't switch users to BackupPC in
>> terminal?
>>
>> I'd say its worth a try.
>>
>> Robert Trevellyan
>>
>> On Tue, Mar 13, 2018 at 10:30 AM, Marc Gilliatt 
>> wrote:
>>
>> So I should set my ConnectTimeout on my backuppc server then?
>> --
>> *From:* Robert Trevellyan 
>> *Sent:* 13 March 2018 14:25:30
>>
>> *To:* General list for user discussion, questions and support
>> *Subject:* Re: [BackupPC-users] Can't switch users to BackupPC in
>> terminal?
>>
>> According to the man pages, the ConnectTimeout and ServerAlive settings
>> only apply to ssh_config, i.e. the BPC end, whereas the other settings only
>> apply to sshd_config, i.e. the host you are trying to backup.
>>
>> Robert Trevellyan
>>
>> On Tue, Mar 13, 2018 at 10:12 AM, Marc Gilliatt 
>> wrote:
>>
>> Thank you for the quick response.
>>
>>
>> Do I have to increase the SSH timeout on my backuppc server or my client
>> or both?
>>
>>
>> I've checked the SSH timeout on my backuppc server, its commented out,
>> should I uncomment it and set it?
>>
>>
>>
>> --
>> *From:* Robert Trevellyan 
>> *Sent:* 13 March 2018 14:00:17
>> *To:* General list for user discussion, questions and support
>> *Subject:* Re: [BackupPC-users] Can't switch users to BackupPC in
>> terminal?
>>
>> Maybe the client has its own firewall?
>>
>> The BPC timeout setting is ClientTimeout on the Backup Settings page. For
>> SSH you would have to delve into /etc/ssh_config and /etc/sshd_config.
>> Look for ConnectionTimeout, ClientAliveInterval, ClientAliveCountMax and
>> ServerAliveInterval. More details via man ssh_config and man sshd_config.
>>
>>
>> Robert Trevellyan
>>
>> On Tue, Mar 13, 2018 at 9:51 AM, Marc Gilliatt 
>> wrote:
>>
>> Our servers our on our internal LAN, so I don't think it's our firewall.
>> I used BackupPC v3 in the past, and I upgraded to BackupPC v4. I had issues
>> with the upgrade and I had to completely build my backuppc server again.
>> However, I had no issue with BackupPC v3, I never received that rsync error
>> before until now. When I go into each of my client's page in the GUI, it
>> says its been successfully pinged.
>>
>>
>> I'm not sure on how to find out about the timeout and setting it greater,
>> or the SSH connection time sorry?
>> --
>> *From:* Robert Trevellyan 
>> *Sent:* 12 March 2018 21:38:11
>> *To:* General list for user discussion, questions and support
>> *Subject:* Re: [BackupPC-users] Can't switch users to BackupPC in
>> terminal?
>>
>> Perhaps the client's firewall is blocking pings.
>>
>> And what do you have set for timeout - is it 600 seconds? Or perhaps the
>> SSH connection is timing out.
>>
>> Robert Trevellyan
>>
>> On Mon, Mar 12, 2018 at 12:46 PM, Marc Gilliatt 
>> wrote:
>>
>> I believe I solved my issue of the hostname, I had to use the IP address
>> for some reason, I cant use the FQDN.
>>
>>
>> Also, when I try to run a backup it fails after about 10 minutes, I'm
>> receiving the following message...
>>
>>
>> 2018-03-12 16:39:08 Got fatal error during xfer (rsync error: error in rsync 
>> protocol data stream (code 12) at io.c(629) [generator=3.0.9.11])
>> 2018-03-12 16:39:14 Backup aborted (rsync error: error in rsync protocol 
>> data stream (code 12) at io.c(629) [generator=3.0.9.11])
>>
>>  I'm not sure on what that error means?
>>
>> --
>> *From:* Stefan Peter 
>> *Sent:* 12 March 

Re: [BackupPC-users] bpc_read error messages

[Craig Barratt via BackupPC-users]

No, those are recently added warnings as part of a fix for the case where
the pool file is actually smaller than the file size in the attributes.

In your case, the file size from the attributes is 18446744073709551613 (64
bit unsigned -3).  I'm not sure how it got that way (possibly some
corruption of the attribute file for that directory?), but the log message
should mean it will get repaired during that backup.

Craig

On Tuesday, January 30, 2018, infos+backu...@ba-cst.net <
infos+backu...@ba-cst.net> wrote:

> Hello,
>
> We are using BPC 4, should be with latest release of every component.
>
> Not sure if this could mean troubles or some bug, so...
>
> While looking at a full XferLog, we found several "read past EOF" error
> messages, with a huge fileSize (always the same for each error). Here
> are two of those (with very short context in case it's useful) :
>
> same  recv .d..t.. rwxr-xr-x 0, 0 4096 usr/portage/dev-php/pecl-http
> G bpc_read: read past EOF; readSize = 262500, posn = 0, fileSize =
> 18446744073709551613, bufferSize = 8388608
> G bpc_read: read past EOF; readSize = 34398, posn = 262500, fileSize =
> 18446744073709551613, bufferSize = 8388608
> new   recv >f.st.. rw-r--r-- 0, 0 3070
> usr/portage/dev-php/pecl-http/Manifest
>
> Are those errors troubles in the making ? They seem to have appeared
> after a storage disk upgrade with offline rsync between old and new BPC
> data repository.
>
> Tia,
> -- B Consultants
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] bpc_read error messages

[Craig Barratt via BackupPC-users]

No, those are recently added warnings as part of a fix for the case where
the pool file is actually smaller than the file size in the attributes.

In your case, the file size from the attributes is 18446744073709551613 (64
bit unsigned -3).  I'm not sure how it got that way (possibly some
corruption of the attribute file for that directory?), but the log message
should mean it will get repaired during that backup.

Craig

On Tuesday, January 30, 2018, infos+backu...@ba-cst.net <
infos+backu...@ba-cst.net> wrote:

> Hello,
>
> We are using BPC 4, should be with latest release of every component.
>
> Not sure if this could mean troubles or some bug, so...
>
> While looking at a full XferLog, we found several "read past EOF" error
> messages, with a huge fileSize (always the same for each error). Here
> are two of those (with very short context in case it's useful) :
>
> same  recv .d..t.. rwxr-xr-x 0, 0 4096 usr/portage/dev-php/pecl-http
> G bpc_read: read past EOF; readSize = 262500, posn = 0, fileSize =
> 18446744073709551613, bufferSize = 8388608
> G bpc_read: read past EOF; readSize = 34398, posn = 262500, fileSize =
> 18446744073709551613, bufferSize = 8388608
> new   recv >f.st.. rw-r--r-- 0, 0 3070
> usr/portage/dev-php/pecl-http/Manifest
>
> Are those errors troubles in the making ? They seem to have appeared
> after a storage disk upgrade with offline rsync between old and new BPC
> data repository.
>
> Tia,
> -- B Consultants
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Serious error: last backup ... directory doesn't exist!!!

[Craig Barratt via BackupPC-users]

Torsten,

Thanks for the additional info, but I can't explain the behavior your are
seeing.  Sending to the user-list to see if others have suggestions.

BackupPC seems to be unable to create directories and files below
/vol/bpc4/BackupPC.  The "No space left on device" errno seems inconsistent
with the output of df.

Although it won't address any of your problems, I pushed a fix
<https://github.com/backuppc/backuppc/commit/265431fff889bca2624541b05cdfbbaeae7a0039>
for the error caused by the failure to open a directory.

Craig

On Sat, Feb 3, 2018 at 3:56 AM, <f...@igh.de> wrote:

> Dear Craig,
>
> On Fri, Feb 02, 2018 at 09:19:02AM -0800, Craig Barratt via BackupPC-users
> wrote:
> > Here are a few things to check:
> >
> >- can you manually create files and directories below
> /vol/bpc4/BackupPC
> >as the backuppc user (eg, "su backuppc; cd /vol/bpc4/BackupPC; mkdir
> foo;
> >rmdir foo; touch foobar; rm foobar")
>
> yes, works as expected.
>
> >- is the file system mounted readonly?
>
> no, mount says:
> ... /vol/bpc4 type ext4 (rw,noatime,data=ordered)
>
> >- has the backuppc user lost permissions?
>
> in what sense? All BackupPC processes run as user backuppc; all files
> and directories /vol/bpc4/BackupPC and below are owned by
> backuppc:backuppc.
>
>
> df says
> Filesystem Size  Used Avail Use% Mounted on
> /dev/mapper/data-bpc4  1.6T  955G  535G  65% /vol/bpc4
>
> The file system lives on a mirror raid, which seems to be ok:
>
> md127 : active raid1 sdb1[1] sdc1[0]
>   2930266432 blocks [2/2] [UU]
>
> There are no SMART errors logged on the disks (even after SMART test).
>
> I have copied several GB to the file system and removed them again -
> no errors.
>
> I have launched a forced fsck. It succeeded without any errors:
> Durchgang 1: Inodes, Blöcke und Größen werden geprüft
> Durchgang 2: Verzeichnisstruktur wird geprüft
> Durchgang 3: Verzeichnisverknüpfungen werden geprüft
> Durchgang 4: Referenzzähler werden überprüft
> Durchgang 5: Zusammengefasste Gruppeninformation wird geprüft
> /dev/data/bpc4: 104312919/104505344 Dateien (0.0% nicht
> zusammenhängend), 256909
> 738/417993728 Blöcke
>
>
> I went through the logs. There are more error messages from a backup
> which was presented as "running" in the summary. Rather strange sound
> the messages "IO error encountered" and "No space left on device "
> (please see below). I cannot figure out the origin of these messages.
>
> ...
> G bpc_fileReadAll: can't open
> /vol/bpc4/BackupPC/cpool/20/9a/219b13a5a32e6cd66ab3cf139bd8d35c (from
> alternatives/pg_config)
> file has vanished: "alternatives/pg_config"
> ...
>
> ...
> IO error encountered -- skipping file deletion
> G bpc_attrib_dirRead: can't open
> /vol/bpc4/BackupPC/cpool/26/24/27243e59e0d4404f14ddc7ebb0202ce6
> G bpc_attribCache_loadPath:
> bpc_attrib_dirRead(/vol/bpc4/BackupPC/pc/zuse/169, fetc/fapache2/attrib)
> returned -1
> ...
>
> ...
> R bpc_attrib_dirRead: can't open
> /vol/bpc4/BackupPC/cpool/1e/aa/1eab8cca5e477b6fe2530e955cca3978
> R bpc_attribCache_loadPath:
> bpc_attrib_dirRead(/vol/bpc4/BackupPC/pc/zuse/169,
> fetc/fcups/fssl/attrib) returned -1
> [ skipped 6 lines ]
> ...
>
>
> ...
> R
> R
> bpc_sysCall_checkFileMatch(.cpan/build/DateTime-Locale-1.
> 05-GcMGii/pm_to_blib):
> file doesn't exist
> ...
>
> ...
> R bpc_poolWrite_write: can't open/create
> /vol/bpc4/BackupPC/cpool/18801.736.0 for writingIOdone: pool
> .cpan/build/DateTime-Locale-1.05-GcMGii/blib/lib/DateTime/
> Locale/.en_NR.pod.00
> ...
>
> ...
> R
> bpc_poolWrite_unmarkPendingDelete(/vol/bpc4/BackupPC/cpool/50/02/
> 50032f7b52be451f6a6c396067253906)
> failed; errno = 2
> R Couldn't unmark candidate matching file
> /vol/bpc4/BackupPC/cpool/50/02/50032f7b52be451f6a6c396067253906
> (skipped; errno = 2)
> ...
>
>
> The following is very strange:
> ...
> rsync_bpc: recv_generator: mkdir
> "/.cpan/build/Dist-CheckConflicts-0.11-RNgNPa/t/lib" failed: No space
> left on device (28)
> ...
>
> dumpe2fs says:
>
> ...
> Inode count:  104505344
> Block count:  417993728
> Reserved block count: 20899686
> Free blocks:  243883988
> Free inodes:  97119479
> ...
>
>
>
> Best regards
>
>
> Torsten Finke
>
>
>
>
> > It does look like the failure to update the filesystem exposes a bug
> which
> > I'll fix, but this is secondary to your main issue:
> >
> > Can't use an undefined value as an ARRAY refere

Re: [BackupPC-users] Serious error: last backup ... directory doesn't exist!!!

[Craig Barratt via BackupPC-users]

Other things to check include:

   - is the file system full? (df) - you did say it was only 65% full, so
   that should be ok
   - have you run out of inodes? (df -i)

If you can't directly see some problem with the file system the next step
is to stop backuppc, unmount the file system and run fsck.

Craig


On Fri, Feb 2, 2018 at 9:19 AM, Craig Barratt <
cbarr...@users.sourceforge.net> wrote:

> Here are a few things to check:
>
>- can you manually create files and directories below
>/vol/bpc4/BackupPC as the backuppc user (eg, "su backuppc; cd
>/vol/bpc4/BackupPC; mkdir foo; rmdir foo; touch foobar; rm foobar")
>- is the file system mounted readonly?
>- has the backuppc user lost permissions?
>
> It does look like the failure to update the filesystem exposes a bug which
> I'll fix, but this is secondary to your main issue:
>
> Can't use an undefined value as an ARRAY reference at
> /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380
>
>
> Craig
>
> On Fri, Feb 2, 2018 at 5:56 AM, <f...@igh.de> wrote:
>
>> Dear BackupPC Users,
>>
>>
>> I am running BackupPC-4.1.3 for several months without problems
>> (really a great piece of software).
>>
>> About a week ago a strange type of error occured and keeps staying,
>> which I cannot understand. The error messages are like this ("fs" is
>> the name of one of my systems to be backed up; I did some linebreaks
>> to increase readability):
>>
>>
>> 2018-01-28 23:43:34 Can't create /vol/bpc4/BackupPC/pc/fs/149/refCnt
>> 2018-01-29 02:09:34 Serious error: last backup
>>   /vol/bpc4/BackupPC/pc/fs/149 directory doesn't exist!!!  Need to
>>   remove back to last filled backup
>> 2018-01-29 02:09:34 Deleting backup 147
>> 2018-01-29 02:09:35 BackupPC_backupDelete: removing #147
>> 2018-01-29 02:09:35 BackupPC_backupDelete: No prior backup for merge
>> 2018-01-29 02:09:52 BackupPC_refCountUpdate: doing fsck on fs #149
>>   since /vol/bpc4/BackupPC/pc/fs/149/refCnt doesn't exist
>> 2018-01-29 02:09:52 Can't use an undefined value as an ARRAY reference
>>   at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380.
>> 2018-01-29 02:09:52 BackupPC_backupDelete: got 1 errors
>> 2018-01-29 02:09:52 Finished BackupPC_backupDelete, status = 256
>>   (running time: 18 sec)
>> 2018-01-29 02:09:52 Deleting backup 148
>> 2018-01-29 02:09:52 BackupPC_backupDelete: removing #148
>> 2018-01-29 02:09:52 BackupPC_backupDelete: No prior backup for merge
>> 2018-01-29 02:09:55 BackupPC_refCountUpdate: doing fsck on fs #149
>>   since /vol/bpc4/BackupPC/pc/fs/149/refCnt doesn't exist
>> 2018-01-29 02:09:55 Can't use an undefined value as an ARRAY reference
>>   at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380.
>> 2018-01-29 02:09:55 BackupPC_backupDelete: got 1 errors
>> 2018-01-29 02:09:55 Finished BackupPC_backupDelete, status = 256
>>   (running time: 3 sec)
>> 2018-01-29 02:09:55 Deleting backup 149
>> 2018-01-29 02:09:56 BackupPC_backupDelete: removing #149
>> 2018-01-29 02:09:56 BackupPC_backupDelete: No prior backup for merge
>> 2018-01-29 02:38:20 BackupPC_refCountUpdate: host fs got 0 errors
>>   (took 1704 secs)
>> 2018-01-29 02:38:20 Finished BackupPC_backupDelete, status = 0
>>   (running time: 1705 sec)
>> 2018-01-29 03:16:29 dump failed: unable to open/create
>>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
>> 2018-01-29 03:55:15 dump failed: unable to open/create
>>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
>> 2018-01-29 04:15:15 dump failed: unable to open/create
>>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
>> 2018-01-29 23:43:54 dump failed: unable to open/create
>>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
>> 2018-01-30 01:24:02 dump failed: unable to open/create
>>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
>> 2018-01-30 02:36:01 dump failed: unable to open/create
>>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
>> 2018-01-30 03:42:01 dump failed: unable to open/create
>>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
>> 2018-01-30 04:12:01 dump failed: unable to open/create
>>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
>> 2018-01-30 23:57:53 Copying backup #146 to #147
>>
>> 2018-01-31 01:05:38 Can't mkpath
>>   /vol/bpc4/BackupPC/pc/fs/147/./fsysbak/f.../fLocked/f00
>> 2018-01-31 01:05:38 Can't copy
>>   ./fsysbak/f.../fLocked/f00/attrib_dc793dc4650baa1a8cc3b69d211573c1
>>   to /vol/bpc4/BackupPC/pc/fs/147/./fsysbak/f.../fLocked/f00/attr
>> ib_dc793dc4650baa1a8cc3b69d211573c1
>> ...
>>
>> The last pair of messages is then repeated for th

Re: [BackupPC-users] Serious error: last backup ... directory doesn't exist!!!

[Craig Barratt via BackupPC-users]

Here are a few things to check:

   - can you manually create files and directories below /vol/bpc4/BackupPC
   as the backuppc user (eg, "su backuppc; cd /vol/bpc4/BackupPC; mkdir foo;
   rmdir foo; touch foobar; rm foobar")
   - is the file system mounted readonly?
   - has the backuppc user lost permissions?

It does look like the failure to update the filesystem exposes a bug which
I'll fix, but this is secondary to your main issue:

Can't use an undefined value as an ARRAY reference at
/vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380


Craig

On Fri, Feb 2, 2018 at 5:56 AM,  wrote:

> Dear BackupPC Users,
>
>
> I am running BackupPC-4.1.3 for several months without problems
> (really a great piece of software).
>
> About a week ago a strange type of error occured and keeps staying,
> which I cannot understand. The error messages are like this ("fs" is
> the name of one of my systems to be backed up; I did some linebreaks
> to increase readability):
>
>
> 2018-01-28 23:43:34 Can't create /vol/bpc4/BackupPC/pc/fs/149/refCnt
> 2018-01-29 02:09:34 Serious error: last backup
>   /vol/bpc4/BackupPC/pc/fs/149 directory doesn't exist!!!  Need to
>   remove back to last filled backup
> 2018-01-29 02:09:34 Deleting backup 147
> 2018-01-29 02:09:35 BackupPC_backupDelete: removing #147
> 2018-01-29 02:09:35 BackupPC_backupDelete: No prior backup for merge
> 2018-01-29 02:09:52 BackupPC_refCountUpdate: doing fsck on fs #149
>   since /vol/bpc4/BackupPC/pc/fs/149/refCnt doesn't exist
> 2018-01-29 02:09:52 Can't use an undefined value as an ARRAY reference
>   at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380.
> 2018-01-29 02:09:52 BackupPC_backupDelete: got 1 errors
> 2018-01-29 02:09:52 Finished BackupPC_backupDelete, status = 256
>   (running time: 18 sec)
> 2018-01-29 02:09:52 Deleting backup 148
> 2018-01-29 02:09:52 BackupPC_backupDelete: removing #148
> 2018-01-29 02:09:52 BackupPC_backupDelete: No prior backup for merge
> 2018-01-29 02:09:55 BackupPC_refCountUpdate: doing fsck on fs #149
>   since /vol/bpc4/BackupPC/pc/fs/149/refCnt doesn't exist
> 2018-01-29 02:09:55 Can't use an undefined value as an ARRAY reference
>   at /vol/opt/BackupPC-4.1.3/bin/BackupPC_refCountUpdate line 380.
> 2018-01-29 02:09:55 BackupPC_backupDelete: got 1 errors
> 2018-01-29 02:09:55 Finished BackupPC_backupDelete, status = 256
>   (running time: 3 sec)
> 2018-01-29 02:09:55 Deleting backup 149
> 2018-01-29 02:09:56 BackupPC_backupDelete: removing #149
> 2018-01-29 02:09:56 BackupPC_backupDelete: No prior backup for merge
> 2018-01-29 02:38:20 BackupPC_refCountUpdate: host fs got 0 errors
>   (took 1704 secs)
> 2018-01-29 02:38:20 Finished BackupPC_backupDelete, status = 0
>   (running time: 1705 sec)
> 2018-01-29 03:16:29 dump failed: unable to open/create
>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
> 2018-01-29 03:55:15 dump failed: unable to open/create
>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
> 2018-01-29 04:15:15 dump failed: unable to open/create
>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
> 2018-01-29 23:43:54 dump failed: unable to open/create
>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
> 2018-01-30 01:24:02 dump failed: unable to open/create
>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
> 2018-01-30 02:36:01 dump failed: unable to open/create
>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
> 2018-01-30 03:42:01 dump failed: unable to open/create
>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
> 2018-01-30 04:12:01 dump failed: unable to open/create
>   /vol/bpc4/BackupPC/pc/fs/XferLOG.147.z
> 2018-01-30 23:57:53 Copying backup #146 to #147
>
> 2018-01-31 01:05:38 Can't mkpath
>   /vol/bpc4/BackupPC/pc/fs/147/./fsysbak/f.../fLocked/f00
> 2018-01-31 01:05:38 Can't copy
>   ./fsysbak/f.../fLocked/f00/attrib_dc793dc4650baa1a8cc3b69d211573c1
>   to /vol/bpc4/BackupPC/pc/fs/147/./fsysbak/f.../fLocked/f00/attrib_
> dc793dc4650baa1a8cc3b69d211573c1
> ...
>
> The last pair of messages is then repeated for thousands of files.
>
>
> It seems, that there is an error concerning the sequence.
>
> I had checked for several default reasons:
> - No files or directories have been manipulated manually
> - BackupPC is almost the only task running on my backup server (there
>   should be no side effects from other services; no user is normally
>   working on that machine)
> - the file system has about 1.6 TB at a usage of 65% (this rate was
>   never exceeded)
> - the system had no crash (uptime is 217 days, since setup of
>   BackupPC).
> - /vol/bpc4 is a mount point of an ext4 file system (normally very
> reliable)
> - Kernel 4.1.39, OpenSuSE 42.1 - not really outdated
>
>
>
>
> Any advice to repair this error is highly appretiated.
>
>
> Best regards
>
>
> Torsten Finke
>
>
>
> --
> 
> Torsten Finke
> f...@igh.de
>
> Ingenieurgemeinschaft IgH
> Gesellschaft für Ingenieurleistungen mbH
> Heinz-Bäcker-Str. 34
> D-45356 Essen
>
> 

Re: [BackupPC-users] No files dumped for share for localhost

[Craig Barratt via BackupPC-users]

Please remove the -q option.  Try adding -v (or even -vv) to the ssh args.

What happens if you run some other command, eg, /bin/date?  What happens if
you run some path that doesn't exist, eg, /bin/foobar.

Examples:

/usr/bin/ssh -v -x -l backuppc localhost /bin/date
/usr/bin/ssh -v -x -l backuppc localhost /bin/foobar


Craig


On Mon, Jan 29, 2018 at 10:14 PM, RAKOTONDRAINIBE Harimino Lalatiana <
mimino...@gmail.com> wrote:

> Hi Alexander, Graig
>
> I installed the backuppc4 and p5-BackupPC-XS via ports. And I reinstalled
> the rsync-bpc via ports.
>
> Anyway their still no output for the command below and yes it exit
> immediately:
>
> backuppc@backup:/ % /usr/bin/ssh -q -x -l backuppc localhost
> /usr/local/bin/rsync --server --sender -svvlHogDtpre.iLsf
>
> Regards,
>
> Hari
>
>
> 2018-01-29 22:05 GMT+03:00 Alexander Moisseev via BackupPC-users <
> backuppc-users@lists.sourceforge.net>:
>
>> On 1/29/2018 2:53 PM, RAKOTONDRAINIBE Harimino Lalatiana wrote:
>>
>>> The backuppc is installed in freebsd 11.1
>>> All hosts seems to be backuppc well except the localhost.
>>> I did like it was said in the forum so  I build rsync-bpc 3.0.9 from
>>> current git .
>>>
>>
>> BTW, You could use ports:
>>
>> net/rsync-bpc
>> sysutils/backuppc4
>> sysutils/p5-BackupPC-XS
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> 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/
>>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] No files dumped for share for localhost

[Craig Barratt via BackupPC-users]

What happens when you run this command as the backuppc user?

su backuppc
/usr/bin/ssh -q -x -l backuppc localhost /usr/local/bin/rsync --server
--sender -svvlHogDtpre.iLsf


Is there any output?  Does it exit immediately?

Craig

On Mon, Jan 29, 2018 at 3:53 AM, RAKOTONDRAINIBE Harimino Lalatiana <
mimino...@gmail.com> wrote:

> Hi everyone,
>
> After an issues with backuppc v3 , I upgraded to v4.1.4.
>
> The backuppc is installed in freebsd 11.1
>
> All hosts seems to be backuppc well except the localhost.
>
> I did like it was said in the forum so  I build rsync-bpc 3.0.9 from
> current git .
>
> In addition to that I run :
>
> /usr/bin/ssh -q -x -l backuppc localhost /usr/local/bin/rsync
>
> Which don't give any output.
>
> I also run the dump manually and the out is :
>
> backuppc@backup:/ % /usr/local/bin/BackupPC_dump -v -i localhost
> Backup type: type = incr, needs_full = 1, needs_incr = 1, lastFullTime =
> 1512601200, opts{f} = , opts{i} = 1, opts{F} =
> cmdSystemOrEval: about to system /sbin/ping -c 1 localhost
> cmdSystemOrEval: about to system /sbin/ping -c 1 localhost
> CheckHostAlive: ran '/sbin/ping -c 1 localhost'; returning 0.020
> XferLOG file /var/db/BackupPC/pc/localhost/XferLOG.153 created 2018-01-29
> 14:47:18
> Backup prep: type = incr, case = 6, inPlace = 1, doDuplicate = 0,
> newBkupNum = 153, newBkupIdx = 3, lastBkupNum = , lastBkupIdx =  (FillCycle
> = 0, noFillCnt = 0)
> __bpc_progress_state__ backup share "/"
> Running: /home/backuppc/rsyns-git/rsync-bpc/rsync_bpc --bpc-top-dir
> /var/db/BackupPC --bpc-host-name localhost --bpc-share-name /
> --bpc-bkup-num 153 --bpc-bkup-comp 0 --bpc-bkup-prevnum -1
> --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 530710 --bpc-attrib-new
> --bpc-log-level 5 -e /usr/bin/ssh\ -q\ -x\ -l\ backuppc
> --rsync-path=/usr/local/bin/rsync --super --recursive --protect-args
> --numeric-ids --perms --owner --group -D --times --links --hard-links
> --delete --delete-excluded --partial --log-format=log:\ %o\ %i\ %B\
> %8U,%8G\ %9l\ %f%L --stats -vv --timeout=72000 --exclude=/dev
> --exclude=/media --exclude=/mnt --exclude=/nonexistent --exclude=/proc
> --exclude=/sys --exclude=/tmp --exclude=/usr/src/sys --exclude=/var/run
> --exclude=/var/tmp --exclude=/var/db/BackupPC localhost:/ /
> incr backup started for directory /
> started incr dump, share=/
> Xfer PIDs are now 39051
> xferPids 39051
> This is the rsync child about to exec /home/backuppc/rsyns-git/
> rsync-bpc/rsync_bpc
> cmdExecOrEval: about to exec /home/backuppc/rsyns-git/rsync-bpc/rsync_bpc
> --bpc-top-dir /var/db/BackupPC --bpc-host-name localhost --bpc-share-name /
> --bpc-bkup-num 153 --bpc-bkup-comp 0 --bpc-bkup-prevnum -1
> --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 530710 --bpc-attrib-new
> --bpc-log-level 5 -e /usr/bin/ssh\ -q\ -x\ -l\ backuppc
> --rsync-path=/usr/local/bin/rsync --super --recursive --protect-args
> --numeric-ids --perms --owner --group -D --times --links --hard-links
> --delete --delete-excluded --partial --log-format=log:\ %o\ %i\ %B\
> %8U,%8G\ %9l\ %f%L --stats -vv --timeout=72000 --exclude=/dev
> --exclude=/media --exclude=/mnt --exclude=/nonexistent --exclude=/proc
> --exclude=/sys --exclude=/tmp --exclude=/usr/src/sys --exclude=/var/run
> --exclude=/var/tmp --exclude=/var/db/BackupPC localhost:/ /
> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles
> = 0
> opening connection using: /usr/bin/ssh -q -x -l backuppc localhost
> /usr/local/bin/rsync --server --sender -svvlHogDtpre.iLsf
> protected args: --timeout=72000 --numeric-ids . /
> rsync_bpc: connection unexpectedly closed (0 bytes received so far)
> [Receiver]
> bpc_sysCall_cleanup: doneInit = 1
> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal,
> 0 sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 530710 inode
> Parsing done: nFilesTotal = 0
> rsync error: error in rsync protocol data stream (code 12) at io.c(629)
> [Receiver=3.0.9.11]
> rsync_bpc exited with fatal status 12 (3072) (rsync error: error in rsync
> protocol data stream (code 12) at io.c(629) [Receiver=3.0.9.11])
> Xfer PIDs are now
> xferPids
> __bpc_progress_state__ post-cmd
> Executing DumpPostUserCmd: /var/db/BackupPC/mailadmin.sh 0 localhost
> cmdSystemOrEval: about to system /var/db/BackupPC/mailadmin.sh 0 localhost
> send-mail: Cannot open smtp.irenala.edu.mg:25
> Got fatal error during xfer (rsync error: error in rsync protocol data
> stream (code 12) at io.c(629) [Receiver=3.0.9.11])
> cmdSystemOrEval: about to system /sbin/ping -c 1 localhost
> cmdSystemOrEval: about to system /sbin/ping -c 1 localhost
> CheckHostAlive: ran '/sbin/ping -c 1 localhost'; returning 0.070
> Backup aborted (rsync error: error in rsync protocol data stream (code 12)
> at io.c(629) [Receiver=3.0.9.11])
> __bpc_progress_state__ fail cleanup
> BackupFailCleanup: nFilesTotal = 0, type = incr, BackupCase = 6, inPlace =
> 1, lastBkupNum =
> BackupFailCleanup: inPlace with no new files... no cleanup
> __bpc_progress_state__ 

Re: [BackupPC-users] backup failing with "No files dumped for share /"

[Craig Barratt via BackupPC-users]

Joel,

Thanks for confirming.  Those errors shouldn't appear on the next full
backup.

I just released rsync-bpc-3.0.9.12 with that fix.

Craig

On Wed, Jan 24, 2018 at 3:16 AM, Joel Uckelman <uckel...@nomic.net> wrote:

> Thus spake Craig Barratt via BackupPC-users:
> > Joel,
> >
> > It's hard to tell from the log.  However, one thing worth trying is to
> > build rsync-bpc 3.0.9 from current git, since there was a bug I fixed
> last
> > week that could be related to this:
> >
> > mkdir somewhere
> > cd somewhere
> > git clone https://github.com/backuppc/rsync-bpc
> > cd rsync-bpc
> > git checkout 3.0.9
> >
> > ./configure
> >
> > make
> >
> > Then set $Conf{RsyncBackupPCPath} to the new rysnc_bpc executable (ie:
> > /path/to/somewhere/rsync-bpc/rsync_bpc) and try running the backup
> again.
> >
> > If that still fails, the next steps are to increase XferLogLevel (eg, to
> 5
> > or 6), and add -vv to RsyncArgsExtra and send the log file.
> >
> > Craig
> >
>
> I had a complete successful backup with the patched rsync-bpc. I get
> a bunch of these (~50) in the log now:
>
> G bpc_read: read past EOF; readSize = 262101, posn = 43, fileSize = 43,
> bufferSize = 8388608
> G bpc_read: read past EOF; readSize = 262144, posn = 262144, fileSize =
> 43, bufferSize = 8388608
> G bpc_read: read past EOF; readSize = 262144, posn = 524288, fileSize =
> 43, bufferSize = 8388608
>
> But the backup appears to have been successful. Thanks!
>
> --
> J.
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] backup failing with "No files dumped for share /"

[Craig Barratt via BackupPC-users]

Hari,

This doesn't look related to the original thread.  For some reason
rsync_bpc's connection to the client is closed before any files get
transferred.

What happens when you run this comment as the backuppc user:

/usr/bin/ssh -q -x -l backuppc localhost /usr/local/bin/rsync

Craig

On Fri, Jan 26, 2018 at 5:01 AM, RAKOTONDRAINIBE Harimino Lalatiana <
mimino...@gmail.com> wrote:

> Hi everyone,
>
> I encounter the same issue now when I backup my localhost. I had a problem
> after an OS upgrade and after some change and an upgrade in 4.1.4, the
> issue has been resolved for all the hosts except for my localhost.
>
> I already tried all that was said earlier in the forum by  building
> rsync-bpc with the current git and increasing the xferlog
>
> The error in xferlog :
>
> This is the rsync child about to exec 
> /home/backuppc/rsyns-git/rsync-bpc/rsync_bpc
> bpc_attrib_backwardCompat: WriteOldStyleAttribFile = 0, KeepOldAttribFiles = 0
> opening connection using: /usr/bin/ssh -q -x -l backuppc localhost 
> /usr/local/bin/rsync --server --sender -svvlHogDtpre.iLsf
> protected args: --timeout=72000 --numeric-ids . /
> rsync_bpc: connection unexpectedly closed (0 bytes received so far) [Receiver]
> bpc_sysCall_cleanup: doneInit = 1
> Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 
> sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 530710 inode
> Parsing done: nFilesTotal = 0
> rsync error: error in rsync protocol data stream (code 12) at io.c(629) 
> [Receiver=3.0.9.11]
> rsync_bpc exited with fatal status 12 (3072) (rsync error: error in rsync 
> protocol data stream (code 12) at io.c(629) [Receiver=3.0.9.11])
> Xfer PIDs are now
> Executing DumpPostUserCmd: /var/db/BackupPC/mailadmin.sh 0 localhost
> Got fatal error during xfer (rsync error: error in rsync protocol data stream 
> (code 12) at io.c(629) [Receiver=3.0.9.11])
> Backup aborted (rsync error: error in rsync protocol data stream (code 12) at 
> io.c(629) [Receiver=3.0.9.11])
> BackupFailCleanup: nFilesTotal = 0, type = incr, BackupCase = 6, inPlace = 1, 
> lastBkupNum =
> BackupFailCleanup: inPlace with no new files... no cleanup
> Running BackupPC_refCountUpdate -h localhost -f on localhost
> Xfer PIDs are now 17115
> BackupPC_refCountUpdate: host localhost #153: gotFsck = 1, gotDelta = , 
> gotPoolCnt = 1, gotNoPoolCntOk =
> BackupPC_refCountUpdate: processing host localhost #153 (fsck = 1)
> BackupPC_refCountUpdate: processing host localhost #153 deltaFile 
> /var/db/BackupPC/pc/localhost/153/refCnt/poolCntDelta_0_0_0_17115 with 510160 
> entries
> BackupPC_refCountUpdate: computing totals for host localhost
> BackupPC_refCountUpdate: host localhost got 0 errors (took 5 secs)
> BackupPC_refCountUpdate total errors: 0
> Xfer PIDs are now
> Finished BackupPC_refCountUpdate (running time: 5 sec)
> Xfer PIDs are now
>
> As I understand it's a problem with rsync-bpc but I didn't find any solution 
> to resolve it.
>
> Thank you,
>
> Hari
>
>
>
>
> 2018-01-24 14:16 GMT+03:00 Joel Uckelman <uckel...@nomic.net>:
>
>> Thus spake Craig Barratt via BackupPC-users:
>> > Joel,
>> >
>> > It's hard to tell from the log.  However, one thing worth trying is to
>> > build rsync-bpc 3.0.9 from current git, since there was a bug I fixed
>> last
>> > week that could be related to this:
>> >
>> > mkdir somewhere
>> > cd somewhere
>> > git clone https://github.com/backuppc/rsync-bpc
>> > cd rsync-bpc
>> > git checkout 3.0.9
>> >
>> > ./configure
>> >
>> > make
>> >
>> > Then set $Conf{RsyncBackupPCPath} to the new rysnc_bpc executable (ie:
>> > /path/to/somewhere/rsync-bpc/rsync_bpc) and try running the backup
>> again.
>> >
>> > If that still fails, the next steps are to increase XferLogLevel (eg,
>> to 5
>> > or 6), and add -vv to RsyncArgsExtra and send the log file.
>> >
>> > Craig
>> >
>>
>> I had a complete successful backup with the patched rsync-bpc. I get
>> a bunch of these (~50) in the log now:
>>
>> G bpc_read: read past EOF; readSize = 262101, posn = 43, fileSize = 43,
>> bufferSize = 8388608
>> G bpc_read: read past EOF; readSize = 262144, posn = 262144, fileSize =
>> 43, bufferSize = 8388608
>> G bpc_read: read past EOF; readSize = 262144, posn = 524288, fileSize =
>> 43, bufferSize = 8388608
>>
>> But the backup appears to have been successful. Thanks!
>>
>> --
>> J.
>>
>> 
>> --
>> Check out the vibra

Re: [BackupPC-users] UPDATE: BackupPC_tarExtract exited with fail status 256

[Craig Barratt via BackupPC-users]

Tim,

Can you send a failing XferLOG, or at least the interesting parts (eg,
first and last ~100 lines) if it is too big)?

Last week I pushed a commit

that supports the pax format headers from smbclient for long pathnames.
That might be worth trying.

Craig

On Sun, Dec 17, 2017 at 6:02 AM, Tim Evans  wrote:

> On 12/03/2017 12:32 PM, Tim Evans wrote:
>
>> We visited this topic this past summer:
>>
>> https://sourceforge.net/p/backuppc/mailman/message/35912961/
>>
>> Now that 4.1.4 is out, I can report the problem's still here. Server's OS
>> has been updated to Fedora 27, with Samba version
>> samba-common-4.7.3-0.fc27.noarch.
>>
>> Behavior is as reported previously:  full SMB backups (Win7 client) never
>> complete; after approximately 24 hours, the server detects the failure,
>> kills it, and starts over.  New instance sometimes completes, but not
>> always. In the latter case, it's killed and restarted.
>>
>
> And to update this, 4.1.5 does not seem to have resolved this problem. Two
> consecutive full backups have failed with the same error and behavior.
> Third one started overnight.
>
> --
> Tim Evans   |   5 Chestnut Court
> |   Owings Mills, MD 21117
> |   443-394-3864
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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 3.3.0 does not traverse all hosts

[Craig Barratt via BackupPC-users]

The behavior shouldn't have changed.

Here are some things to check:

   - the BackupPC server LOG file - any messages for hosts that you expect
   should start?
   - the host LOG file for a host that doesn't start
   - have blackouts changed in some way?
   - if you manually start a backup on one of the "skipped" hosts, does it
   run (eg, perhaps ping returns different output now)?
   - you can manually run a backup on a "skipped" host (su backuppc;
   BackupPC_dump -v HOST) ; the -v option gives more output on what BackupPC
   is doing for that host, including why it might skip the host)

Craig

On Thu, Jan 11, 2018 at 11:41 PM, Adam Pribyl  wrote:

> I am using BackupPC for many years, after update from 3.2.1 (Debian 7) to
> 3.3.0 (Debian 8) the backuppc does not traverse all hosts during the night
> the same way as the previous version does i.e. I have a hosts that are not
> backed up for up to 3 days.
>
> I thoroughly merged the backuppc config files (there were no significant
> changes). I do have:
>
> $Conf{BackupPCNightlyPeriod} = 1;
> $Conf{WakeupSchedule} = [  1,  2,  3,  4,  5,  6 ];
> $Conf{MaxBackups} = 4;
> $Conf{IncrPeriod} = '0.97';
>
> but the backups are started only at 01:00 roughly 20 of more than 60
> hosts. Sometimes something is started a 02:00 but the rest of the pool is
> not backuped up that day, even thou the backuppc wakes up at 03:00-06:00
> with all the previous jobs finished, but it does not continue with the rest
> of the pool. I have now every host backed up only once every 3 days,
> instead every day.
>
> Host  ↓User #Full Full Age (days) Full Size (GB) Speed (MB/s) #Incr Incr
> Age (days) Last Backup (days) State #Xfer errs Last attempt bbbspr
>12  5.1 0.890.2212  0.2 0.2 idle3
>  idle
> ccc spr 12  15.14.820.4912  2.3 2.3
>  idle3   idle
> ddd spr 12  14.20.170.1912  1.3 1.3
>  idle1   idle
>
>
> Is there any known change in the behavior?
>
>
> Thanks
>
> Adam Pribyl
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] backup failing with "No files dumped for share /"

[Craig Barratt via BackupPC-users]

Joel,

It's hard to tell from the log.  However, one thing worth trying is to
build rsync-bpc 3.0.9 from current git, since there was a bug I fixed last
week that could be related to this:

mkdir somewhere
cd somewhere
git clone https://github.com/backuppc/rsync-bpc
cd rsync-bpc
git checkout 3.0.9

./configure

make

Then set $Conf{RsyncBackupPCPath} to the new rysnc_bpc executable (ie:
/path/to/somewhere/rsync-bpc/rsync_bpc) and try running the backup again.

If that still fails, the next steps are to increase XferLogLevel (eg, to 5
or 6), and add -vv to RsyncArgsExtra and send the log file.

Craig




On Sun, Jan 21, 2018 at 2:28 PM, Joel Uckelman  wrote:

> Thus spake Michael Stowe:
> > >
> > > Can anyone suggest what's causing the backup to fail or how I could
> > > further troubleshoot?
> >
> > Certainly.
> >
> > First, to further troubleshoot:  check the logs for rsync on the other
> > side (the system that is being backed up) which may include more
> > information on the fatal errors.
>
> Where would I find logs for rsync on the target system? I see nothing
> which looks relevant in /var/log there.
>
> To be clear, the target system is not running rsyncd. The XferMethod in
> use is "rsync", which I understood was using rsync over ssh.
>
> > Second, suggestions on what's causing the backup to fail:  you haven't
> > specified how the backups are structured, but it certainly looks like
> > rsync backing up files either directly from or mounted from a Windows
> > system.  Some of the non-fatal errors are indicating that you are (for
> > some reason) backing up Internet Explorer cache files.  While a bit
> > silly, this isn't itself a problem, but it strongly implies possible
> > indiscretion with regards to attempting to back up forbidden files
> > (e.g., open or protected without shadow copies) or those whose filenames
> > can't be handled by rsync.
>
> Those files are from a backup of the last Windows system the owner of
> the laptop used, some years prior. The target system is Fedora 26, not
> Windows.
>
> Those Windows files were backed up successfully by BackupPC 3, from the
> user's previous laptop. Unfortunately, I upgraded to 4.1.5 in the same
> week when the user got a new lapop, so I never had a chance to see how
> the old BackupPC version behaved with the new laptop.
>
> --
> J.
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Bug in rsync_bpc --sparse?

[Craig Barratt via BackupPC-users]

Alex,

I pushed some changes
<https://github.com/backuppc/rsync-bpc/commit/54286d87e05c98d68a24a8f8dbd4b9d494b788f9>
to rsync-bpc (and 3.0.9 here
<https://github.com/backuppc/rsync-bpc/commit/f07e4be5d31ed0b6d26b1c860dcd5b5bc4565534>)
a few weeks ago that exit with an error if --sparse is specified.

Craig

On Fri, Dec 15, 2017 at 2:31 AM, Alexander Kobel <a-ko...@a-kobel.de> wrote:

> Hi Craig,
>
> thanks for your swift reply.
>
> On 2017-12-15 05:17, Craig Barratt via BackupPC-users wrote:
>
>> Unfortunately sparse files are not supported by rsync_bpc, and there are
>> no plans to do so.
>>
>
> Okay. Not a big impact for BackupPC's files, anyway - I just thought it's
> safe and no harm, but proven wrong...
>
> I should make it a fatal error if that option is specified.
>>
>
> Yes, that would be great to avoid future mistakes.
>
> I believe a full backup (without --sparse of course) should update the
>> files to their correct state.
>>
>
> Okay. For me to understand: the MD5 hashes are generated on the server
> side, correct? So a file that was transferred incorrectly will not be
> stored under the hash of the original file? And the full backup does not
> just skip based on size, times and names, but on the actual hash of the
> file? In that situation I see why running a full backup should resolve
> everything.
>
>
> May I ask you to crank out a short comment on point d) as well? If it's
> complicated, don't. But I found earlier questions on how to decompress an
> entire pool on the mailing list to employ ZFS' or Btrfs' compression, and
> while it's officially unsupported to convert the pool, I might try if (and
> only if) my assumptions are correct on what would need to be done.
>
>> d) On my *actual* server, I used compression. This incident taught
>> me to verify some of the files manually, and to perhaps migrate to
>> filesystem compression (which I had planned anyway) to keep things
>> as simple as possible.
>>d.1) BackupPC_zcat for verifying/decompressing has a remarkable
>> overhead for a well-grown set of small files (even when pointed
>> directly to the pool files). From what I can tell, Adler's pigz [2]
>> implementation supports headerless zlib files and is *way* faster.
>> Also, all my tests show that files compress to output with the
>> expected hashes encoded in the filename. However, I remembered that
>> BackupPC's compression flushes in between, apparently much like
>> pigz. Are BackupPC's compressed files *fully* in default zlib
>> format, or do I need to expect trouble with large files in corner
>> cases?
>>d.2) Conceptually, what is needed to convert an entire v4 pool to
>> uncompressed storage? Is it just
>> - decompression of all files from cpool/??/?? to pool/??/??
>> (identical names, because hashes are computed on the decompressed
>> data)
>> - move poolCnt files from cpool/?? to pool/??
>> - replace compression level in pc/$host/backups and
>> pc/$host/nnn/backupInfo
>>or do any refCnt files need to be touched as well?
>>
>
>
> Thanks a lot,
> Alex
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Share exclude lists among different servers

[Craig Barratt via BackupPC-users]

Alex,

I added shareName substitution for RsyncArgs* in commit 0b6dee6

.

Craig

On Wed, Nov 29, 2017 at 3:34 AM, Alexander Kobel  wrote:

> Dear all,
>
> is there a good/clean/recommended way of sharing exclude lists between
> servers by decoupling them from the main config.pl file?  I have a couple
> of servers whose configs differ just a bit, but enough that synchronizing
> changes becomes slightly annoying.  Also, I'm sure that many people have
> put quite a bit of effort to write sensible default exclude lists, and
> sharing/distributing such lists would be easier if they are decoupled from
> the rest of the configuration.
>
> On a related note (perhaps more appropriate for -devel):
> $Conf{RsyncArgsExtra} pretty much allows me to do what I need:
>
> $Conf{RsyncArgsExtra} = [
> '--exclude-from=$confDir/pc/$host.exclude',
> ];
>
> Unfortunately, there is no variable substitution for $shareName, unlike in
> the tar and SMB client commands.  Is there a specific reason why it is not
> allowed for RsyncArgs?
>
>
> Thanks,
> Alex
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] backuppc3.3.2.2 won't work after an OS upgrade

[Craig Barratt via BackupPC-users]

The bind() is trying to create a socket in $Conf{RunDir}.  It's likely that
directory doesn't exist, or isn't writeable by BackupPC.  Try something
like this as root (replace /var/run/BackupPC with whatever your
$Conf{RunDir} is set to):

mkdir /var/run/BackupPC
chown backuppc /var/run/BackupPC

chmod 755 /var/run/BackupPC


This is something that /usr/local/etc/rc.d/backuppc should do.  Also, I'll
improve that error message.

Craig

On Wed, Jan 17, 2018 at 11:30 PM, RAKOTONDRAINIBE Harimino Lalatiana <
mimino...@gmail.com> wrote:

> Hello,
>
> Thank you for your answer,
>
> When I run the command the output is :
> backuppc@backup:/ % /usr/local/bin/BackupPC -d&
> [1] 79359
>
>
> In addition to that, the output of the log file is :
> 2018-01-18 10:17:52 Reading hosts file
> 2018-01-18 10:17:52 Deleted host  trashClean  from backup list
> 2018-01-18 10:17:52 unix bind() failed: Permission denied
> [1]  + Done  /usr/local/bin/BackupPC -d
>
>
> Regards,
> Hari
>
> 2018-01-18 10:16 GMT+03:00 Craig Barratt via BackupPC-users <
> backuppc-users@lists.sourceforge.net>:
>
>> Those warnings are all benign and can be ignored.
>>
>> Back to your original email.  After first confirming that BackupPC isn't
>> running, what happens when you directly start BackupPC as the BackupPC
>> user, eg:
>>
>> su backuppc
>> /usr/local/bin/BackupPC -d &
>>
>>
>> Do you get any errors?  Is there anything written to the BackupPC server
>> LOG file?
>>
>> Craig
>>
>> On Wed, Jan 17, 2018 at 11:09 PM, RAKOTONDRAINIBE Harimino Lalatiana <
>> mimino...@gmail.com> wrote:
>>
>>> Hi everyone,
>>>
>>> Doesn't anyone have any idea of the issue ?
>>>
>>> I continue debugging hoping that someone can help me and when I try to
>>> run int manually , the result can be seen below :
>>>
>>> backuppc@backup:/ % /usr/local/bin/perl -w /usr/local/bin/BackupPC -d
>>> Statement unlikely to be reached at /usr/local/lib/BackupPC/Lib.pm line
>>> 1172.
>>> (Maybe you meant system() when you said exec()?)
>>> Statement unlikely to be reached at /usr/local/lib/BackupPC/Lib.pm line
>>> 1236.
>>> (Maybe you meant system() when you said exec()?)
>>> Statement unlikely to be reached at /usr/local/bin/BackupPC line 607.
>>> (Maybe you meant system() when you said exec()?)
>>> Statement unlikely to be reached at /usr/local/bin/BackupPC line 779.
>>> (Maybe you meant system() when you said exec()?)
>>> Use of uninitialized value $topDir in string eq at
>>> /usr/local/lib/BackupPC/Lib.pm line 70.
>>> Use of uninitialized value $installDir in string eq at
>>> /usr/local/lib/BackupPC/Lib.pm line 71.
>>> Use of uninitialized value $confDir in string eq at
>>> /usr/local/lib/BackupPC/Lib.pm line 79.
>>> Use of uninitialized value $host in string ne at
>>> /usr/local/lib/BackupPC/Lib.pm line 348.
>>> Use of uninitialized value $Conf{"SmbClientPath"} in string eq at
>>> /usr/local/bin/BackupPC line 284.
>>> Use of uninitialized value $Conf{"NmbLookupPath"} in string eq at
>>> /usr/local/bin/BackupPC line 284.
>>> Filehandle STDIN reopened as STDIN only for output at
>>> /usr/local/bin/BackupPC line 326.
>>>
>>> So now I am not sure if it's a socket problem or the because of the
>>> errors above .
>>>
>>> Regards,
>>>
>>> 2018-01-09 14:50 GMT+03:00 RAKOTONDRAINIBE Harimino Lalatiana <
>>> mimino...@gmail.com>:
>>>
>>>> Hi everyone,
>>>>
>>>> After an upgrade of freebsd from 11.0 to 11.1, my backupc service won't
>>>> work .
>>>> The version of backuppc I use is backuppc 3.3.2.2
>>>> When I run from service management, it shows  :
>>>>
>>>> root@backup:~ # service -v backuppc start
>>>> backuppc is located in /usr/local/etc/rc.d
>>>> Starting backuppc.
>>>> term: Undefined variable.
>>>>
>>>> And when I check in the backup log it says :
>>>>
>>>> Reading hosts file
>>>> unix bind() failed: Address already in use
>>>>
>>>> I already try to reboot my server, uninstall and reinstall backup and
>>>> upgrade to backupc 4, also downgrade to see if it's a compatility issues
>>>> but nothing seems to work.
>>>>
>>>> I also didn't find anything in others forum .
>>>>
>>>> So i

Re: [BackupPC-users] backuppc3.3.2.2 won't work after an OS upgrade

[Craig Barratt via BackupPC-users]

Those warnings are all benign and can be ignored.

Back to your original email.  After first confirming that BackupPC isn't
running, what happens when you directly start BackupPC as the BackupPC
user, eg:

su backuppc
/usr/local/bin/BackupPC -d &


Do you get any errors?  Is there anything written to the BackupPC server
LOG file?

Craig

On Wed, Jan 17, 2018 at 11:09 PM, RAKOTONDRAINIBE Harimino Lalatiana <
mimino...@gmail.com> wrote:

> Hi everyone,
>
> Doesn't anyone have any idea of the issue ?
>
> I continue debugging hoping that someone can help me and when I try to run
> int manually , the result can be seen below :
>
> backuppc@backup:/ % /usr/local/bin/perl -w /usr/local/bin/BackupPC -d
> Statement unlikely to be reached at /usr/local/lib/BackupPC/Lib.pm line
> 1172.
> (Maybe you meant system() when you said exec()?)
> Statement unlikely to be reached at /usr/local/lib/BackupPC/Lib.pm line
> 1236.
> (Maybe you meant system() when you said exec()?)
> Statement unlikely to be reached at /usr/local/bin/BackupPC line 607.
> (Maybe you meant system() when you said exec()?)
> Statement unlikely to be reached at /usr/local/bin/BackupPC line 779.
> (Maybe you meant system() when you said exec()?)
> Use of uninitialized value $topDir in string eq at
> /usr/local/lib/BackupPC/Lib.pm line 70.
> Use of uninitialized value $installDir in string eq at
> /usr/local/lib/BackupPC/Lib.pm line 71.
> Use of uninitialized value $confDir in string eq at
> /usr/local/lib/BackupPC/Lib.pm line 79.
> Use of uninitialized value $host in string ne at
> /usr/local/lib/BackupPC/Lib.pm line 348.
> Use of uninitialized value $Conf{"SmbClientPath"} in string eq at
> /usr/local/bin/BackupPC line 284.
> Use of uninitialized value $Conf{"NmbLookupPath"} in string eq at
> /usr/local/bin/BackupPC line 284.
> Filehandle STDIN reopened as STDIN only for output at
> /usr/local/bin/BackupPC line 326.
>
> So now I am not sure if it's a socket problem or the because of the errors
> above .
>
> Regards,
>
> 2018-01-09 14:50 GMT+03:00 RAKOTONDRAINIBE Harimino Lalatiana <
> mimino...@gmail.com>:
>
>> Hi everyone,
>>
>> After an upgrade of freebsd from 11.0 to 11.1, my backupc service won't
>> work .
>> The version of backuppc I use is backuppc 3.3.2.2
>> When I run from service management, it shows  :
>>
>> root@backup:~ # service -v backuppc start
>> backuppc is located in /usr/local/etc/rc.d
>> Starting backuppc.
>> term: Undefined variable.
>>
>> And when I check in the backup log it says :
>>
>> Reading hosts file
>> unix bind() failed: Address already in use
>>
>> I already try to reboot my server, uninstall and reinstall backup and
>> upgrade to backupc 4, also downgrade to see if it's a compatility issues
>> but nothing seems to work.
>>
>> I also didn't find anything in others forum .
>>
>> So is someone had already see this issues and can anyone have an idea of
>> what is going wrong ?
>>
>> Thank you,
>>
>> Regards
>>
>> Hari
>>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Backup fails after upgrade to v4

[Craig Barratt via BackupPC-users]

Just a follow up for the list.  This was a bug in rsync_bpc which has
been fixed
in github
<https://github.com/backuppc/rsync-bpc/commit/361ddcd90bb2c3e233bbcd688028c0a5ff81115f>
.

Thanks to Aleks for the debugging help!

Craig

On Wed, Jan 10, 2018 at 2:53 PM, Craig Barratt <
cbarr...@users.sourceforge.net> wrote:

> [989735.607370] rsync_bpc[17687]: segfault at 7fe6e2e1c128 ip 
> 7fe6e421bdf0 sp 7ffe37536078 error 4 in 
> libc-2.24.so[7fe6e40f+195000]
>>
>> That's not good.  I'd really like to get a stack trace or more
> information about where the segfault occurs.
>
> Can you build rsync_bpc from source, and add
>
> -fsanitize=address
>
>
> to CFLAGS and LDFLAGS in the Makefile (after you run configure, but before
> you run make)?
>
> It would also be helpful to get more debug output in the XferLOG file.
> Please set $Conf{XferLogLevel} to 7 before your next run, and send me
> (directly, not on the list) the XferLOG file.  If it is too big just send
> me the first and last ~100 lines.
>
> Thanks,
> Craig
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Backup fails after upgrade to v4

[Craig Barratt via BackupPC-users]

>
> [989735.607370] rsync_bpc[17687]: segfault at 7fe6e2e1c128 ip 
> 7fe6e421bdf0 sp 7ffe37536078 error 4 in 
> libc-2.24.so[7fe6e40f+195000]
>
> That's not good.  I'd really like to get a stack trace or more information
about where the segfault occurs.

Can you build rsync_bpc from source, and add

-fsanitize=address


to CFLAGS and LDFLAGS in the Makefile (after you run configure, but before
you run make)?

It would also be helpful to get more debug output in the XferLOG file.
Please set $Conf{XferLogLevel} to 7 before your next run, and send me
(directly, not on the list) the XferLOG file.  If it is too big just send
me the first and last ~100 lines.

Thanks,
Craig
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] V4 will not backup some directories

[Craig Barratt via BackupPC-users]

The default for a fresh install in V4 includes --one-file-system in
$Conf{RsyncArgs} (for a V3->V4 upgrade, that option is not added or removed
from the V3 settings).

Trying removing the --one-file-system argument if you want it to behave
like the default V3.

Craig

On Mon, Jan 8, 2018 at 5:21 AM, Müfit Eribol  wrote:

> I have problem with another client as well.
>
> If I specify /opt/qwerty-5.0.a in BackupFilesOnly , it doesn't copy any
> file. It comes up with empty directory.
>
> But, if I specify just /opt in BackupFilesOnl, then BackupPC copies all as
> expected.
>
> Anything wrong with using dash/dot in the directory name? Is it a sign of
> a design change in V4?
>
> By the way, I am using rsync method.
>
> Regards,
>
> Mufit
>
>
>
> On 8.01.2018 09:42, Müfit Eribol wrote:
>
>> After using V3 for years, I installed a fresh V4 and defined the same
>> directory structure for backup.
>>
>> All clients working OK except one which is a QNAP box. V4 connects
>> without any error. It even backups /etc folder. But, for a reason unknown
>> to me, it doesn't backup:
>>
>> /share/xyz which is symlinked to /share/MD0_DATA/xyz
>>
>> The only difference of this folder is that MD0_DATA is the raid data
>> volume. I have already tried /share/xyz and /share/MD0_DATA/xyz with no
>> avail.
>>
>> Any advice and suggestions will be greatly appreciated.
>>
>> Mufit
>>
>>
>> --
>>
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> 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/
>>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Direct restore broken with BackupPC 4.1.x and SMB3?

[Craig Barratt via BackupPC-users]

This is a cross-post of the github issue
 you created 2 days ago.
I responded there.

Craig

On Thu, Dec 21, 2017 at 2:28 PM, Jens Potthast <
jens.potth...@innovation.uni-bremen.de> wrote:

> Hello list!
> After many hours of tests and research, I need your help.
>
> Here is a short-as-possible report of what is happening and what I've done
> already.
> Actually, I have three problems, but let's try to get the first one fixed
> first for a start.
>
> Why read any further?
> =
> If my environment is similar to your environment, you should test a direct
> restore operation on your hosts, just to be sure to have a valid
> backup-system in case of emergency. (Ok, restore to zip/tar does work :-))
>
> My environment
> ==
> Backup-Server: BackupPC 4.1.5 running on Debian 8.10 with smbclient 4.2.14
> Host: Windows Server 2012 R2
>
> The situation
> =
> Backing up is no problem*, but doing a direct restore is impossible.
>
> What happens?
> =
> Using the (default) configuration for smb restore:
>  $Conf{SmbClientRestoreCmd} = '$smbClientPath $host\\$shareName
> $I_option -U $userName -E -d 1 -c tarmode\\ full -mSMB3 -Tx -';
> The operation stops with:
>  > tar:316  tarmode is now full, system, hidden, noreset, quiet
>  > tar:1596 Can't mkdir test: NT_STATUS_OBJECT_NAME_COLLISION
>
> What I've done and checked so far
> =
> * As BackupPC user, I can connect to the windows host in an interactive
> smbclient-session.
> * While in smbclient-session: I'm able to create directories and put files
> on the host.
> * While in smbclient-session: Trying to create a directory, that already
> exists, I get the same error as above, what seems legit, since the
> directory
> exists.
> * Swapped my smb.conf with the vanilla smb.conf
> * Extracting files with BackupPC_tarCreate locally does work.
> * Piping BackupPC_tarCreate-command to smbclient-command manually and
> change
> path options: if the new path does not exists, it is successfully created,
> but then instantly stops with the error as seen above (since BackupPC tries
> to create the path as soon as it tries to put the actual file in the new
> directory).
> * Checked permissions for backuppc-smb-user on windows domain/filesystem.
> Although this was not likely, since smbclient-sessions do work.
> * Checked another environment: BackupPC 4.1.x on Debian 9.2 and Windows
> Server 2012 R2 as host on a different subnet - same error occurs. This
> system is only a couple of weeks old and does not serve any other purpose.
> This is, why I think that other users are affected, too.
>
> Possible solution
> =
> Let BackupPC continue to work, if creation of a directory fails *just
> because* it already exists. Alternatively do not try to create a directory,
> if it already exists. (If smbclient is responsible for breaking the
> operation, please guide me to someone to contact.)
>
>
> *Since my setup has undergone some heavy migration work (moved from
> BackupPC
> 3.x to 4.x, moved my pool from v3 to v4), I have two other points to check
> that might be something only existing for my setup:
> - Filenames get chopped off after 97-99 characters. It's visible on the
> web-frontend, if you navigate to a file in a backup.
> - Some directories do net get backed up (yes, I checked permissions)
>
>
> Any input is really appreciated!
>
> Regards,
> Jens
>
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] File System containing backup was too full

[Craig Barratt via BackupPC-users]

This log message:

2017-12-19 01:00:00 24hr disk usage: 68% max, 68% recent, 0 skipped hosts


correctly shows the disk usage, and also says that no hosts were skipped.

Is there any chance you are running two different BackupPCs, and the 2nd
one is on a different system that is in fact 96% full?

Do you see messages like this in the LOG files:

Disk too full (96%); skipped 7 hosts

Craig

On Tue, Dec 19, 2017 at 5:05 AM, Adrien Coestesquis 
wrote:

> after installation i changed the topdir setting in the config.pl
> $Conf{TopDir} = '/backup/backuppc';
> then i had to copy the entire /var/lib/backuppc arborescence to this new
> dir in order to make it work
>
> i have no var partition and all is clean :
>
> root@bak1:/etc/backuppc# df -h
> Filesystem Size  Used Avail Use% Mounted on
> /dev/md0p1 543G  6.4G  509G   2% /
> udev10M 0   10M   0% /dev
> tmpfs  1.6G   16M  1.5G   1% /run
> tmpfs  3.8G 0  3.8G   0% /dev/shm
> tmpfs  5.0M 0  5.0M   0% /run/lock
> tmpfs  3.8G 0  3.8G   0% /sys/fs/cgroup
> /dev/sda1   15T  9.4T  4.4T  69% /backup
>
>
> 2017-12-19 13:43 GMT+01:00 Stefan Peter :
>
>> Dear Adrien Coestesquis
>> On 19.12.2017 13:10, Adrien Coestesquis wrote:
>> > i don't think so, the BPC arborescence is somewhere else
>>
>> And BackupPC knows this for real? If I remember correctly, you can
>> deviate from /var/lib/backuppc only if you install directly from the
>> sources. If you use an upstream package, you can not.
>>
>> Could it be that your /var partition is at 95%?
>>
>>
>> With kind regards
>>
>> Stefan Peter
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> 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/
>>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Trouble with restore

[Craig Barratt via BackupPC-users]

It looks like this issue was opened on github
 a couple of days ago.  I
responded there with some suggestions.

Craig

On Wed, Dec 13, 2017 at 10:50 AM, Holger Parplies  wrote:

> Hi,
>
> let's start over.
>
> Jens Potthast wrote on 2017-12-13 14:01:46 +0100 [[BackupPC-users] Trouble
> with restore]:
> > [...]
> > I needed to restore a couple of files
> > recently. The last time, I had to restore some files was years ago. At
> that
> > time it was no problem. Right now, restore fails:
> >
> > Running: /usr/bin/smbclient server\\sharename -U backuppcuser -E -d
> 1 -c
> > tarmode\ full -mSMB3 -Tx -
> > Running: /usr/local/BackupPC/bin/BackupPC_tarCreate -h hostname -n 1886
> -s
> > sharename -t -r /Path\ to\ file -p /Path\ to\ file/filename.txt
>
> you've got an error in your arguments, or you've misquoted from your log
> file
> (or your version of BackupPC is broken). That may or may not be related,
> but
> it's something to check. You are apparently using the web interface for a
> direct restore to the client system.
>
> a) Personally, I wouldn't do that, but you may have good reasons.
> b) You are possibly filling in some incorrect values into the web form. The
>arguments to BackupPC_tarCreate are directing it to
>- remove "/Path to file" from the paths in the backup and
>- add"/Path to file/filename.txt" in front of all paths.
>Is that what you want? The "filename.txt" seems misplaced, and it will
>likely be difficult to create a directory of that name on the target
>system if there happens to be a file of that name present, which might
>explain your error (or not).
>Also, there are no file name arguments, which should cause
>BackupPC_tarCreate to terminate with an error message. Strange.
>Note: the '-r' and '-p' arguments wouldn't be created if the two paths
>were equal (at least the code says so).
>
> > [...]
> > tarCreate: Done: 1 files, 237695 bytes, 0 dirs, 0 specials, 0 errors
>
> That sounds as if it had worked ...
>
> > tar:1596 Can't mkdir Path to filename: NT_STATUS_OBJECT_NAME_COLLISION
>
> ... and that doesn't mention "filename.txt".
>
> What's in the RestoreInfo.xxx file for the restore attempt?
>
> Regards,
> Holger
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Problems with BackupPC - RSync

[Craig Barratt via BackupPC-users]

There could be a lot of reasons for this.  Start by looking for errors in
the server log file, and the XferLOG.bad.z file in the client's backup
directory.

Craig

On Thu, Dec 14, 2017 at 8:10 AM, Jeffrey West via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:

> All,
>
>
>
> I have been using rsync to backup my windows workstations.  I have some
> machines that are not backing up, even though I can manually rsync with
> their machine from the BackupPC server.  BackupPC tries to backup, but
> doesn’t even save a partial backup if it gets disconnected.   Is there some
> way to change this?
>
>
>
>
>
> Jeff West
> Systems Engineer
> Riptide Software
> Office 321-296-7724 ext 216 <(321)%20296-7724>
> Direct 407-542-7697 <(407)%20542-7697>
> Cell407-925-7030 <(407)%20925-7030>
> www.riptidesoftware.com
>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Where's the full backup the incrementals need?

[Craig Barratt via BackupPC-users]

In 4.x the incrementals are stored as deltas relative to the next (future)
backup.  So your unfilled backups #4 depends on #5, #5 depends on #6, and
#6 depends on the filled (full) backup #7.

Craig

On Wed, Dec 13, 2017 at 1:16 PM, Jamie Burchell  wrote:

> Hey
>
>
>
> Am I dreaming or did I read in the documentation that an incremental
> relies on a full backup staying around to support it?
>
>
>
> I’ve let BackupPC run for a month or so and logged in to the web interface
> today expecting to see one more full backup than I have configured, but
> that doesn’t seem to be the case?
>
>
>
> Backup#
>
> Type
>
> Filled
>
> Level
>
> Start Date
>
> Duration/mins
>
> Age/days
>
> 4 
>
> incr
>
> no
>
> 1
>
> 11/14 21:00
>
> 0.2
>
> 29.0
>
> 5 
>
> incr
>
> no
>
> 1
>
> 11/15 21:01
>
> 0.9
>
> 28.0
>
> 6 
>
> incr
>
> no
>
> 1
>
> 11/17 02:01
>
> 0.4
>
> 26.8
>
> 7 
>
> full
>
> yes
>
> 0
>
> 11/18 02:03
>
> 0.4
>
> 25.8
>
> 8 
>
> incr
>
> no
>
> 1
>
> 11/19 02:01
>
> 0.3
>
> 24.8
>
>
>
> According to the table, the oldest four incremental backups have no
> “parent” full backup. Is that to be expected?
>
>
>
> Cheers
>
> Jamie
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Bug in rsync_bpc --sparse?

[Craig Barratt via BackupPC-users]

Unfortunately sparse files are not supported by rsync_bpc, and there are no
plans to do so.

I should make it a fatal error if that option is specified.

I believe a full backup (without --sparse of course) should update the
files to their correct state.

Craig

On Thu, Dec 14, 2017 at 4:59 AM, Alexander Kobel  wrote:

> Dear all,
>
> some while ago I started to include '--sparse' in RsyncArgs.  Now, I
> realized that some files from my backups are corrupted - namely, some of
> those after the configuration change.
>
> I tried to find the problem and realized that, apparently, --sparse is
> indeed the culprit.  I have a file attached which shows the problem, tested
> on Arch Linux' most recent backuppc package, which contains BackupPC-4.1.5,
> BackupPC-XS 0.57 and rsync_bpc 3.0.9.10.  The build script can be seen at
> [1], but it's pretty much as vanilla as it gets. Rsync on the client side
> is again from Arch's official repo, version 3.1.2, protocol 31.  In fact,
> the client is the same machine in this case, but connection is done via ssh
> nevertheless, to simulate the same conditions.
> FWIW, I disabled compression for the test.  Otherwise, the configuration
> of the live server is essentially vanilla except for some excludes.
>
> The original file in this test is core.db, with md5sum 9bde...  Without
> --sparse, the file is stored correctly in $topDir/pool/09/de/9bde
> With --sparse, however, this file does not appear.  Via the webinterface,
> I recovered the file core.db--sparse, with md5sum 7a9e..., and it turned
> out that this is indeed stored in the corresponding pool folder.
>
> So I get:
>
> % md5sum core*
> 9bde60210cc9a3d57fd6aa69d2a964d3  core.db
> 7a9e44d8fcc02d98a2a28d8d9069f448  core.db--sparse
> 9bde60210cc9a3d57fd6aa69d2a964d3  core.db_no--sparse
>
> % diff <(hexdump core.db) <(hexdump core.db--sparse)
> 3584c3584
> < 000dff0 489e 25a7 d831 8731 6ca0 46a3 5dd7 00ee
> ---
> > 000dff0 489e 25a7 d831 8731 6ca0 46a3 5dd7 90ee
> 8072c8072
> < 001f870 5d5a 4a81  0008
> ---
> > 001f870 5d5a 4a81  ad08
>
> Test files straight out of /dev/urandom are unaffected, which was the
> crucial hint that led me to --sparse in the first place - they have no
> sparsity at all.  However, I even found some highly compressed data (e.g.,
> JPEGs) that are affected.
>
>
> So, couple of questions.
>
> a) Can someone confirm (preferably not on a live host and not with real
> data, of course)?
>
> b) Is --sparse plainly not supported by rsync_bpc? If so, should it be
> disabled?
>
> c) Is there any way to reliably list, verify and, if possible, retransfer
> files that have been transferred within the past n days (where n is,
> obviously, today minus date of introduction of --sparse in my args) without
> retransfering *everything*?  (I'm not sure whether any files, especially of
> full runs, have been skipped entirely due or, in other words, whether the
> rolling hashes of rsync have been correct or not.)
>
>
> And finally, somewhat unrelated:
>
> d) On my *actual* server, I used compression. This incident taught me to
> verify some of the files manually, and to perhaps migrate to filesystem
> compression (which I had planned anyway) to keep things as simple as
> possible.
>   d.1) BackupPC_zcat for verifying/decompressing has a remarkable overhead
> for a well-grown set of small files (even when pointed directly to the pool
> files). From what I can tell, Adler's pigz [2] implementation supports
> headerless zlib files and is *way* faster. Also, all my tests show that
> files compress to output with the expected hashes encoded in the filename.
> However, I remembered that BackupPC's compression flushes in between,
> apparently much like pigz. Are BackupPC's compressed files *fully* in
> default zlib format, or do I need to expect trouble with large files in
> corner cases?
>   d.2) Conceptually, what is needed to convert an entire v4 pool to
> uncompressed storage? Is it just
>- decompression of all files from cpool/??/?? to pool/??/?? (identical
> names, because hashes are computed on the decompressed data)
>- move poolCnt files from cpool/?? to pool/??
>- replace compression level in pc/$host/backups and
> pc/$host/nnn/backupInfo
>   or do any refCnt files need to be touched as well?
>
>
> [1] https://git.archlinux.org/svntogit/community.git/tree/trunk/
> PKGBUILD?h=packages/backuppc
> [2] https://zlib.net/pigz/
>
>
> Best,
> Alex
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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 4.1.5 released (plus new versions of backuppc-xs and rsync-bpc)

[Craig Barratt via BackupPC-users]

There were a couple of bugs in rsync-bpc-3.0.9.9 that are fixed in a newly
released rsync-bpc-3.0.9.11
<https://github.com/backuppc/rsync-bpc/releases/tag/3.0.9.11>.

If you have installed rsync-bpc-3.0.9.9 or rsync-bpc-3.0.9.10, please
upgrade to rsync-bpc-3.0.9.11.

Craig

On Sun, Dec 3, 2017 at 8:28 PM, Craig Barratt <
cbarr...@users.sourceforge.net> wrote:

> BackupPC 4.1.5 <https://github.com/backuppc/backuppc/releases/tag/4.1.5> has
> been released on Github.
>
> New versions of BackupPC-XS 0.57
> <https://github.com/backuppc/backuppc-xs/releases/tag/0.57> and
> rsync-bpc 3.0.9.9
> <https://github.com/backuppc/rsync-bpc/releases/tag/3.0.9.9> have also
> been released.  BackupPC 4.1.5 requires BackupPC-XS 0.57.
>
> The cumulative changes including 4.1.4
> <https://github.com/backuppc/backuppc/releases/tag/4.1.4> (released last
> week but not announced) are listed below.  Upgrading is strongly
> recommended.
>
> Thanks to the multiple contributions and debugging help.
>
> Enjoy!
>
> Craig
>
> #
> # Version 4.1.5, 3 Dec 2017
> #
>
> * Changed required BackupPC::XS version from 0.56 to 0.57.
>
> * bin/BackupPC_dump now updates inodeLast for share being backed up.
>
> * bin/BackupPC_refCountUpdate: inodeLast is checked and updated during
> fsck;
>   needs BackupPC::XS 0.57.
>
> #
> # Version 4.1.4, 25 Nov 2017
> #
>
> Merged pull requests #99, #121, #125, #131, #133, #134, #137, #148, #149,
> #150
>   #151, #152, #153, #155, #157, #167
>
> * lib/BackupPC/Xfer/Smb.pm: made pipeSMB non-blocking to avoid a
>   reported deadlock when BackupPC's select() returns ok for reading,
>   but there are no bytes to read from the client tar's log/stdout
>   output.  Parallel change to lib/BackupPC/Xfer/Tar.pm in 4.1.3.
>
> * bin/BackupPC_tarCreate and bin/BackupPC_zipCreate: untaint the host name
>   so they work with setuid under CGI; fixes empty tar or zip files
>   downloaded via CGI interface (fixes issue #156)
>
> * bin/BackupPC: fixed BackupPC::XS min version checking and error message,
>   from @moisseev (#152)
>
> * bin/BackupPC: added more detailed startup information (perl and BackupPC
>   version) to log, from @moisseev (#157)
>
> * bin/BackupPC_rrdUpdate: fixed empty pools hiding from @moisseev (#167)
>
> * lib/BackupPC/Xfer/Smb.pm: now ignores additional debug messages from
>   smbclient, and flags lines in the XferLOG it doesn't recognize.
>
> * lib/BackupPC/CGI/Browse.pm: default display now has the last, rather
>   than first, share opened.
>
> * Replaced submit with button so that Enter doesn't activate the Delete
>   button.  Fixes issue #161, reported by Philippe-M.
>
> * removed commented-out settings for some ftp args (eg, port#) in
>   lib/BackupPC/Xfer/Ftp.pm; reported by Adam W.
>
> * bin/BackupPC_backupDelete: only print delta counts if LogLevel is >= 5
>
> * bin/BackupPC_tarExtract: fix existing file size count and size
>
> * lib/BackupPC/CGI/EditConfig.pm: fixed masking of subheadings in
>   config editor.
>
> * config/config.pl: added -mSMB3 to $Conf{SmbClientIncrCmd} and
>   $Conf{SmbClientRestoreCmd}, from @SvenBunge (#99)
>
> * lib/BackupPC/Xfer/Rsync.pm: improved cleanup of orphan rsyncTmp files
>
> * In bin/BackupPC_dump, added "share" to __bpc_progress_state__ message so
>   it is 'backup share "$shareName"'.  Patch #150 by @guestisp (issue #143)
>
> * added share name to log message in lib/BackupPC/CGI/Restore.pm for tar
>   and zip restore.
>
> * makeDist: fixed exit code from @moisseev (#153)
>
> * Added Travis CI configuration from @moisseev (#155) and enabled travis
>
> * Replaced "Homepage" with "Github" in config.pl and configure.pl from
>   @moisseev (#121)
>
> * Spelling fixes, mainly in comments from @ka7 (#125).
>
> * Fixed comment in config.pl (zh_CH -> zh_CN) from @patch (#131)
>
> * Fixed German translations from @mainboarder (#133, #134)
>
> * Fixed minor comment typo in config.pl from @pbe-axelor (#137)
>
> * Fixed comments in systemd/README from @schuetzm (#138)
>
> * Fixed Italian translations from @guestisp (#148, #149; issue #142)
>
> * Fixed incorrect hash key in German translations from @moisseev (#151)
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] BackupPC 4.1.5 released (plus new versions of backuppc-xs and rsync-bpc)

[Craig Barratt via BackupPC-users]

BackupPC 4.1.5  has
been released on Github.

New versions of BackupPC-XS 0.57
 and
rsync-bpc 3.0.9.9
 have also been
released.  BackupPC 4.1.5 requires BackupPC-XS 0.57.

The cumulative changes including 4.1.4
 (released last
week but not announced) are listed below.  Upgrading is strongly
recommended.

Thanks to the multiple contributions and debugging help.

Enjoy!

Craig

#
# Version 4.1.5, 3 Dec 2017
#

* Changed required BackupPC::XS version from 0.56 to 0.57.

* bin/BackupPC_dump now updates inodeLast for share being backed up.

* bin/BackupPC_refCountUpdate: inodeLast is checked and updated during fsck;
  needs BackupPC::XS 0.57.

#
# Version 4.1.4, 25 Nov 2017
#

Merged pull requests #99, #121, #125, #131, #133, #134, #137, #148, #149,
#150
  #151, #152, #153, #155, #157, #167

* lib/BackupPC/Xfer/Smb.pm: made pipeSMB non-blocking to avoid a
  reported deadlock when BackupPC's select() returns ok for reading,
  but there are no bytes to read from the client tar's log/stdout
  output.  Parallel change to lib/BackupPC/Xfer/Tar.pm in 4.1.3.

* bin/BackupPC_tarCreate and bin/BackupPC_zipCreate: untaint the host name
  so they work with setuid under CGI; fixes empty tar or zip files
  downloaded via CGI interface (fixes issue #156)

* bin/BackupPC: fixed BackupPC::XS min version checking and error message,
  from @moisseev (#152)

* bin/BackupPC: added more detailed startup information (perl and BackupPC
  version) to log, from @moisseev (#157)

* bin/BackupPC_rrdUpdate: fixed empty pools hiding from @moisseev (#167)

* lib/BackupPC/Xfer/Smb.pm: now ignores additional debug messages from
  smbclient, and flags lines in the XferLOG it doesn't recognize.

* lib/BackupPC/CGI/Browse.pm: default display now has the last, rather
  than first, share opened.

* Replaced submit with button so that Enter doesn't activate the Delete
  button.  Fixes issue #161, reported by Philippe-M.

* removed commented-out settings for some ftp args (eg, port#) in
  lib/BackupPC/Xfer/Ftp.pm; reported by Adam W.

* bin/BackupPC_backupDelete: only print delta counts if LogLevel is >= 5

* bin/BackupPC_tarExtract: fix existing file size count and size

* lib/BackupPC/CGI/EditConfig.pm: fixed masking of subheadings in
  config editor.

* config/config.pl: added -mSMB3 to $Conf{SmbClientIncrCmd} and
  $Conf{SmbClientRestoreCmd}, from @SvenBunge (#99)

* lib/BackupPC/Xfer/Rsync.pm: improved cleanup of orphan rsyncTmp files

* In bin/BackupPC_dump, added "share" to __bpc_progress_state__ message so
  it is 'backup share "$shareName"'.  Patch #150 by @guestisp (issue #143)

* added share name to log message in lib/BackupPC/CGI/Restore.pm for tar
  and zip restore.

* makeDist: fixed exit code from @moisseev (#153)

* Added Travis CI configuration from @moisseev (#155) and enabled travis

* Replaced "Homepage" with "Github" in config.pl and configure.pl from
  @moisseev (#121)

* Spelling fixes, mainly in comments from @ka7 (#125).

* Fixed comment in config.pl (zh_CH -> zh_CN) from @patch (#131)

* Fixed German translations from @mainboarder (#133, #134)

* Fixed minor comment typo in config.pl from @pbe-axelor (#137)

* Fixed comments in systemd/README from @schuetzm (#138)

* Fixed Italian translations from @guestisp (#148, #149; issue #142)

* Fixed incorrect hash key in German translations from @moisseev (#151)
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Unable to read config.pl after BackupPC update

[Craig Barratt]

Jamie,

The new config file looks fine to me: it doesn't have any syntax errors,
and the values seem to be unchanged from the previous version.

To confirm, does it still work correctly if you swap back in the old config
file?  Was BackupPC also upgraded?

Craig

On Mon, Nov 27, 2017 at 3:11 AM, Jamie Burchell  wrote:

> Hi
>
>
>
> I’m using BackupPC from “hobbes1069-BackupPC.repo” and notice that it
> updated over the weekend, creating a config.pl.rpmnew.
>
>
>
> I did a diff between my config.pl and config.pl.rpmnew and merged/updated
> mine. Now unfortunately I can’t get BackupPC to run without the “unable to
> read config.pl or language strings” error. The web interface was mostly a
> whitepage with an empty small select box at the top. I checked the file
> permissions on the config.pl and all looks good.
>
>
>
> I’ve attached the old working config and the new config with merged
> changes and would be most grateful if someone could point out what’s wrong!
>
>
>
> Cheers
>
> Jamie
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Don't expand first backed up directory by default?

[Craig Barratt via BackupPC-users]

Jamie,

Unfortunately it's not easy to have none open, since the browse code
assumes you have selected a particular share.

How about this: by default it opens the last one, rather than the first?
That way all the other shares will appear first.

It's a very simple change if you want to try it.  Here's a diff (just
replace the 0 index with -1):

Craig

--- a/lib/BackupPC/CGI/Browse.pm
+++ b/lib/BackupPC/CGI/Browse.pm
@@ -84,7 +84,7 @@ sub action
 if ( $dir eq "" || $dir eq "." || $dir eq ".." ) {
  $attr = $view->dirAttrib($num, "", "");
  if ( keys(%$attr) > 0 ) {
- $share = (sort(keys(%$attr)))[0];
+ $share = (sort(keys(%$attr)))[-1];
  $dir   = '/';
  } else {
 ErrorExit(eval("qq{$Lang->{Directory___EscHTML}}"));


On Fri, Nov 24, 2017 at 10:07 AM, Jamie Burchell  wrote:

> Hey
>
> Is it possible to configure BackupPC 4 not to expand the first directory
> when viewing a backup?
>
> I'm currently backing up 3 directories from Linux webservers:
>
> /etc
> /var/lib/mysqlbackup
> /var/www
>
> Unfortunately, as the first directory contains many files, it's not
> immediately obvious that there are other (arguably more likely to be
> restored) root directories available to chose from. The other two get a bit
> lost and it's necessary to scroll to see them.
>
> Ideally, all directories would be collapsed so it's obvious what is
> available from the backup and the user can drill-down in to it.
>
> I appreciate this might not be for everybody, so perhaps a configuration
> parameter for it would be better?
>
> Thanks
> Jamie
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Problem BackupPC 4 report double files count and size

[Craig Barratt via BackupPC-users]

This was fixed in this commit

on
July 30.  Will be included in 4.1.4, to be released soon (hopefully).

Craig

On Fri, Nov 24, 2017 at 11:38 AM, Stéphane Bourque <
stephane.bour...@croesus.com> wrote:

> Hello,
>
> We have a problem with BackupPC 4. Every time we launch a Full backup,
> BackupPC report double the amount of files and double size.
>
> Here's a XferLog you can see that it's backing-up only 4 files but report
> show 8 filesExist. The total file size is also double of the real size.
> Can someone help us fix that problem?
> We are using SentOS7
>
> Many thanks.
> Stephane
>
> File /data/BackupPC/pc/pc350/XferLOG.26.z
>
> Contents of file /data/BackupPC/pc/pc350/XferLOG.26.z, modified
> 2017-11-24 13:46:56
>
> XferLOG file /data/BackupPC/pc/pc350/XferLOG.26.z created 2017-11-24 13:42:51
> Backup prep: type = full, case = 4, inPlace = 0, doDuplicate = 0, newBkupNum 
> = 26, newBkupIdx = 12, lastBkupNum = 25, lastBkupIdx = 11 (FillCycle = 3, 
> noFillCnt = 1)
> Running: /usr/bin/smbclient pc350\\s-backup -U backup -m SMB3 -E -d 1 -c 
> tarmode\ full -TcrX - \*\\OutputFiles \*\\Debug OutputFiles Debug 
> \*\\ThirdParties ThirdParties \*\\bin bin \*\\obj obj
> full backup started for share s-backup
> Xfer PIDs are now 4165,4164
> Kinit for backup@SAMBA to access pc350 failed: Cannot find KDC for requested 
> realm
> Domain=[CROESUS] OS=[] Server=[]
> tar:316  tarmode is now full, system, hidden, noreset, quiet
> tarExtract: /usr/local/BackupPC/bin/BackupPC_tarExtract: got Full = 1
> tarExtract: /usr/local/BackupPC/bin/BackupPC_tarExtract starting... 
> (XferLogLevel = 1)
>   same 644   0/0   4 test.txt
>   same 644   0/0   5 test3.txt
>   same 644   0/0   5 test4.txt
> tar:712  Total bytes received: 3599695886
>   same 644   0/0  3599695872 Windows10-Pro-Fr-1703.iso
>   delete   644   0/0   5 test2.txt
> tarExtract: Done: 0 errors,* 8 filesExist*, 7199391772 <(719)%20939-1772> 
> sizeExist, 6912464346 sizeExistComp, 8 filesTotal, 7199391772 
> <(719)%20939-1772> sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 30 
> inodeLast
> Xfer PIDs are now
> Removing unfilled backup 14
> Xfer PIDs are now 4184
> BackupPC_backupDelete: removing #14
> BackupPC_backupDelete: No prior backup for merge
> Xfer PIDs are now 4185,4184
> BackupPC_refCountUpdate: host pc350 got 0 errors (took 0 secs)
> Xfer PIDs are now 4184
> Xfer PIDs are now
> Finished BackupPC_backupDelete, status = 0 (running time: 0 sec)
> Xfer PIDs are now
> Running BackupPC_refCountUpdate -h pc350 on pc350
> Xfer PIDs are now 4186
> BackupPC_refCountUpdate: doing fsck on pc350 #26 (full) since $ConfRefCntFsck 
> == 1
> BackupPC_refCountUpdate: host pc350 got 0 errors (took 0 secs)
> Xfer PIDs are now
> Finished BackupPC_refCountUpdate (running time: 0 sec)
>
> Xfer PIDs are now
>
>
> *Stéphane Bourque*
> Conseiller bureautique
>
> 600, boulevard Armand-Frappier, bureau 200
> Laval QC  H7V 4B4
>
> T  450-662-6101, poste 132
>
> [image: Croesus] 
>
> [image: Facebook] 
>[image: Twitter]    [image: LinkedIn]
>    [image: Youtube]
> 
>
> _
>
> *Avis *: Ce message ne vise uniquement que son destinataire et peut
> contenir de l’information confidentielle.  Son utilisation/divulgation
> non-autorisée est interdite.  Si reçu par erreur, veuillez en aviser
> l’expéditeur et supprimer ce message et toute pièce jointe de votre système.
>
> *Notice*:  This  message  is  intended  to  its  recipient  only  and
>  may  contain  privileged  information.   Unauthorized  use/disclosure is
>  prohibited.If  received  by  error,  please  notify the  sender  and
>  delete this message and any attachments from your system.
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:

Re: [BackupPC-users] rsync error buffer overflow

[Craig Barratt via BackupPC-users]

BackupPC 3.x uses older versions of the rsync protocol, which requires the
entire file list to be stored in memory.

BackupPC 4.x uses pretty up-to-date versions of rsync, which no longer
requires the full file list to be stored.

So it's likely that BackupPC 4.x will have a better chance of running
successfully than 3.x.

Craig

On Fri, Nov 24, 2017 at 4:29 AM, G.W. Haywood via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:

> Hi there,
>
> On Fri, 24 Nov 2017, Jose Barriga wrote:
>
> Im trying to backup a very large number of files and trees and trees
>> of directories.  How can i solved???
>>
>
> You either need to add memory to the machine or modify the way that
> you use rsync/rsyncd so that it uses less memory to do the transfers.
>
> --
>
> 73,
> Ged.
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Execute bash script after each share on backup server

[Craig Barratt via BackupPC-users]

>
> But why Error 256 when it's 1? And the last Line the scripts outputs is:


Perl shifts the exit status left by 8 bits, so the reported exit status is
256 times your program's exit status.

2017-11-23 16:18:08 Output from DumpPreShareCmd: ERROR: Index * on ***
> corrupted or locked!


I'm not sure why that output has a later timestamp (~8 minutes later) than
the exit message.  I presume that's a different (later) run.

backup canceled by user (DumpPreShareCmd returned error status 0)


When a backup is canceled by the user, the error text is whatever was last
in the log.  It might not be a real error.

Craig



On Thu, Nov 23, 2017 at 7:24 AM, Julian Zielke <
jzie...@next-level-integration.com> wrote:

> Hi,
>
> I've implemented some error checking in this script and it either exit
> with 0 (ok) or 1 (fail).
>
> The UserCmdCheckStatus has been activated and the Logfile of BackuPPC says:
>
> 2017-11-23 16:10:30 DumpPreShareCmd returned error status 256... exiting
>
> But why Error 256 when it's 1? And the last Line the scripts outputs is:
>
> 2017-11-23 16:18:08 Output from DumpPreShareCmd: ERROR: Index * on ***
> corrupted or locked!
>
> However on the host summary it says:
>
> backup canceled by user (DumpPreShareCmd returned error status 0)
>
> This doesn't make sense to me either, since it wasn't 0 but 1.
>
> Anybody who can help me solving this problem?
>
> - Julian
>
> -Ursprüngliche Nachricht-
> Von: Julian Zielke
> Gesendet: Montag, 13. November 2017 08:55
> An: 'General list for user discussion, questions and support' <
> backuppc-users@lists.sourceforge.net>
> Betreff: AW: [BackupPC-users] Execute bash script after each share on
> backup server
>
> Ok, Fi finally fixed it.
>
> First of all I for shure know the difference between sh and bash. I just
> tried out different combinations, though my script doesn't make use of and
> bash-only syntax.
>
> However: The PATH-Variable is not available when I execute I, so I added
> an export command at the beginning, resulting in my script working right.
>
> The cleaner way would be to use absolute paths to the separate binaries,
> so I'll use /usr/bin/which  to invoke them properly.
> Thanks anyway for your help. I'm glad the tool is so well supported by the
> community, although being free and opensource.
>
>
> - Julian
>
> -Ursprüngliche Nachricht-
> Von: Julian Zielke
> Gesendet: Montag, 13. November 2017 08:34
> An: General list for user discussion, questions and support <
> backuppc-users@lists.sourceforge.net>
> Betreff: AW: [BackupPC-users] Execute bash script after each share on
> backup server
>
> Hi,
>
> sorry for the confusion. I've tried with both arguments just for debugging
> purposes.
>
> My script used the basename-command, which isn't available during
> execution so I changed that.
> Now I get:
>
> Executing DumpPostShareCmd: /bin/bash -c "/etc/BackupPC/notify.sh *arg1*
> *arg2*"
> server01: -c: line 0: unexpected EOF while looking for matching `"'
> server01: -c: line 1: syntax error: unexpected end of file
>
> The command is:
> /bin/bash -c "/etc/BackupPC/notify.sh $host $share $type $xferOK"
>
> So what's unexpected here? I have to quote the scrit arguments, otherwise
> bash doesn't recognize them.
>
> - Julian
>
> -Ursprüngliche Nachricht-
> Von: Holger Parplies [mailto:wb...@parplies.de]
> Gesendet: Freitag, 10. November 2017 19:46
> An: General list for user discussion, questions and support <
> backuppc-users@lists.sourceforge.net>
> Betreff: Re: [BackupPC-users] Execute bash script after each share on
> backup server
>
> Hi,
>
> Les Mikesell wrote on 2017-11-10 11:13:23 -0600 [Re: [BackupPC-users]
> Execute bash script after each share on backup server]:
> > On Fri, Nov 10, 2017 at 10:11 AM, Julian Zielke
> >  wrote:
> > > I???ve written a script which should be run after each processed
> > > share of a host.
> > >
> > > So I???ve tried using:
> > > /bin/bash /etc/BackupPC/notify.sh -c $host -s $share -t $type -r
> > > $xferOK
> > >
> > > The log says it is being executed but also:
> > >
> > > Backup failed on server01 (DumpPostUserCmd returned error status
> > > 256)
> > >
> > > When I run the script using sh -c ? backuppc iot runs fine.
> > >
> > > So what???s my mistake here?
> >
> > Your script needs to return an exit code of 0. [...] you can add a
> > line 'exit 0' at the end to make backuppc consider it successful
> regardless.
>
> that was my first thought, too, but there is a bit of confusion in the
> question.
>
> 1. You are talking about running a script after each processed *share*, but
>the error message complains about DumpPostUserCmd, not DumpPostShareCmd.
>The remark about 'exit 0' (and all of what I'm saying) might apply to a
>different script, not your notify.sh, or you are doing something
> slightly
>different from what you are describing (or misquoting from memory).
>
> 2. You omit which BackupPC configuration variable 

Re: [BackupPC-users] Documentation version discrepancies

[Craig Barratt via BackupPC-users]

That snippet of text is from the 3.x documentation, where filling was
indeed a legacy feature.  It's not present in the 4.x documentation, where
filling has another meaning and purpose.

Craig

On Wed, Nov 22, 2017 at 9:18 AM, Jamie Burchell  wrote:

> "Filling backups takes a little extra disk space, and it does cost some
> extra disk activity for filling, and later removal. Filling is no longer
> useful, since file mangling and compression doesn't make a filled backup
> very useful. It's likely the filling option will be removed from future
> versions: filling will be delegated to the display and extraction of
> backup data."
>
> That's where I got "filled backups are more of a legacy thing from. i.e.
> the documentation.
>
>
>
> Hi,
>
> Jamie Burchell wrote on 2017-11-18 16:23:41 + [[BackupPC-users]
> Documentation version discrepancies]:
> > As I've been learning backuppc and studying the documentation I
> > noticed that the documentation supplied in the Web UI is different to
> > what's currently online. This has undoubtedly contributed towards my
> > confusion as the terminology changes depending on which document I
> > happen to have access to when I'm looking.
> >
> > For example, this excerpt talking about full and filled backups. It
> > sounds like filled backups are more of a legacy thing too.
>
> quite the opposite, I believe. Filled backups didn't have much meaning
> before BackupPC 4.x.
>
> > Why not remove the docs from the web UI and point the menu to the
> > latest online docs? I know this can be done in the admin, I mean by
> default.
>
> Off the top of my head, I can think of two good reasons.
>
> 1.) Internet access is by no means a requirement of BackupPC. Supposing
> you
> don't have internet access, the reference to the online docs won't
> work.
> As long as you have access to the Web UI, documentation contained
> therein
> will always work.
>
> 2.) There are different versions of BackupPC in use, and as development
> continues, there will be more of them. Documentation may change as
> BackupPC changes and not be applicable to previous versions. While you
> *can* reference distinct online versions of the documentation, you
> gain
> exactly nothing. If you do that, you might as well distribute the
> online
> documentation you would want to reference with the BackupPC version it
> applies to.
> What you are probably thinking of is an evolving documentation that
> gets
> better while the installed BackupPC version stays the same. This
> evolving
> documentation would need to account for differences in BackupPC
> versions,
> thus becoming more and more complex and confusing - much the opposite
> from
> what you are trying to achieve.
>
> As for the pure information, there is simply so much of it out there, that
> people don't find (or don't read) what they are looking for. I've
> explained the difference between full and incremental backups here so many
> times, that I'm simply tired of repeating it when it comes up once again.
> In a nutshell, incremental backups are a trade-off of exactness for speed,
> invented in an era when it was simply not feasible to do daily
> (tape-based) full backups.
> There might be valid reasons even today for not doing full backups daily,
> but the apparent general attitude of "I don't need exact backups, I just
> need fast backups" begs for the answer "don't do any backups at all -
> that's as fast as it gets, and it's not much worse than inaccurate
> backups". Of course, your application may vary (and BackupPC incremental
> backups are in general reasonably accurate, presuming you are using
> rsync(d)).
>
> Regards,
> Holger
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] problem with samba

[Craig Barratt via BackupPC-users]

>
> [root@barak ~]# smbclient //hayun-34/gis -U micha -E -d 3 -c tarmode full


I believe you need to pass a single argument to -c, so either quote it, or
add a backslash:

[root@barak ~]# smbclient //hayun-34/gis -U micha -E -d 3 -c 'tarmode full'

What is $Conf{SmbClientFullCmd} set to on this client, and on a client that
works?  It should be something like:

$Conf{SmbClientFullCmd} = '$smbClientPath $host\\$shareName $I_option
-U $userName -E -d 1 -c tarmode\\ full -Tc$X_option - $fileList';


Craig

On Wed, Nov 22, 2017 at 8:47 AM, Micha Silver  wrote:

> Thanks for your responses, but...
>
> On 11/21/2017 05:53 PM, Les Mikesell wrote:
>
> On Tue, Nov 21, 2017 at 8:54 AM, Евгений  
>  wrote:
>
> Kinit for micha@ARAVA to access hayun-34 failed: Cannot find KDC for
> requested realm
>
> This is about Kerberos.
> Have you configured kerberos properly? Is it working when you request ticket
> (kinit command)?
> I am not sure smbclient should use kerberos authentification by tickets by
> default... can not check it for now.
>
> The windows host that I am backing up is part of a windows domain. Nothing
> has changed on that side.
>
> I believe smbclient will read the values from your /etc/samba/smb.conf
> file at startup unless you have pointed it elsewhere with the -s
> option.   If you are also running a samba server you may have
> configured options that are incompatible with the backuppc client use.
>But that still doesn't explain a difference between full and
> incremental runs.
>
> That's what has me confused. And this problem started right after an
> update to samba on the BackupPC server.
> In addition, BackupPC is successfully doing both fulls and incrementals
> from other (windows) servers.
> ??
>
>
> --
> Micha Silver
> Ben Gurion Univ.
> Sde Boker, Remote Sensing Lab
> cell: +972-523-665918
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Watching restore status

[Craig Barratt via BackupPC-users]

What BackupPC version and Xfer method are you using?  Version 4.x with
rsync does periodically report number of files transferred.

You could look at the restore log file, but it isn't flushed to disk that
often and it's compressed.  Something like this should work:

 tail -c +0 /TOPDIR/pc/HOSTNAME/RestoreLOG.z | BackupPC_zcat

Craig

On Tue, Nov 21, 2017 at 7:12 AM, Nick Bright  wrote:

> Is there a way to watch the restore status? Like being able to tail -f an
> actual log file (not the LOG file in the web UI - that doesn't tell me
> anything).
>
> I'm sitting here waiting for hours, not even knowing if the restore is
> actually doing anything. Need to be able to see what the process is doing.
> Is it working? is it hung? is it just taking a long time to compile the
> rsync list?
>
> Thanks,
>
> --
> ---
> -  Nick Bright-
> -  Vice President of Technology   -
> -  Valnet -=- We Connect You -=-  -
> -  Tel 888-332-1616 x 315 / Fax 620-331-0789  -
> -  Web http://www.valnet.net/ -
> ---
> - Are your files safe?-
> - Valnet Vault - Secure Cloud Backup  -
> - More information & 30 day free trial at -
> - http://www.valnet.net/services/valnet-vault -
> ---
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] problem with samba

[Craig Barratt via BackupPC-users]

Micha,

I've tested Samba 4.7.0 and it works; I don't think the tar options have
changed.

The NT_STATUS_LOGON_FAILURE error shouldn't be bogus.  But I can't explain
why incrementals work.

Can you experiment with running smbclient manually to see what options do
and don't work?

Craig

On Thu, Nov 16, 2017 at 1:27 PM, Micha Silver  wrote:

> About a month ago samba was updated to version 4.6 on my BackupPC server
> (version 3.3) and since then I can't do a full backup of Win7 machines.
> Incrementals work, but not the fulls. I get NT_STATUS_LOGON_FAILURE, but I
> think that's bogus. I have an idea that the problem is the "tarmode" part
> of the smbclient command. It seems that "tarmode verbose full" is not
> supported any longer. The only tarmode options that the new smbclient
> recognizes are full, inc, reset and noreset.
> Any suggestions what the smbclient command should be now with the newer
> samba version?
> Thanks
>
> --
> Micha Silver
> Ben Gurion Univ.
> Sde Boker, Remote Sensing Lab
> +972-523-665918
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] PC Backup Genie message

[Craig Barratt via BackupPC-users]

>
> Is there any easy way to make PC Backup Genie ignore this file during its
> checks ?


No, unfortunately it's not configurable.  You could comment the code out in
BackupPC_sendEmail if you want, specifically this line:

 push(@oldDirs, "$TopDir/pc/$host");

Craig

On Thu, Nov 16, 2017 at 12:01 AM,  wrote:

> Hello,
>
> We are using BPC4 on a Gentoo system, with our home-brewed ebuilds for
> install. Everything is OK, except a (minor) annoyance with PC Backup Genie.
>
> We "locked" some directories in the ebuilds, meaning that if we
> uninstall BPC, those directories will not be destroyed (same idea with
> keeping config files : an upgrade means automatically uninstalling the
> old version, and some stuff must be kept).
>
> The PC Backup Genie is thus sending a daily message while doing its
> normal chores, because it finds a "wrong" file/directory in the BPC/pc
> subdir :
>
> The following directories are bogus and are not being used by
> BackupPC.  This typically happens when PCs are removed from the
> backup list.  If you don't need any old backups from these PCs you
> should remove these directories.  If there are machines on this
> list that should be backed up then there is a problem with the
> hosts file:
>   - /home/BackupPC/pc/.keep_app-backup_backuppc-0
>
> Is there any easy way to make PC Backup Genie ignore this file during
> its checks ?
>
> Thanks,
> --
> B Consultants
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Documentation version discrepancies

[Craig Barratt via BackupPC-users]

To be clear, the documentation link in the BackupPC CGI interface (and all
links for things like config parameters) point to the (locally stored)
documentation for the version you are running.  That way it's consistent
with whatever version you are running.

Craig

On Sat, Nov 18, 2017 at 11:15 AM, Holger Parplies  wrote:

> Hi,
>
> Jamie Burchell wrote on 2017-11-18 16:23:41 + [[BackupPC-users]
> Documentation version discrepancies]:
> > As I've been learning backuppc and studying the documentation I noticed
> > that the documentation supplied in the Web UI is different to what's
> > currently online. This has undoubtedly contributed towards my confusion
> as
> > the terminology changes depending on which document I happen to have
> access
> > to when I'm looking.
> >
> > For example, this excerpt talking about full and filled backups. It
> sounds
> > like filled backups are more of a legacy thing too.
>
> quite the opposite, I believe. Filled backups didn't have much meaning
> before
> BackupPC 4.x.
>
> > Why not remove the docs from the web UI and point the menu to the latest
> > online docs? I know this can be done in the admin, I mean by default.
>
> Off the top of my head, I can think of two good reasons.
>
> 1.) Internet access is by no means a requirement of BackupPC. Supposing you
> don't have internet access, the reference to the online docs won't
> work.
> As long as you have access to the Web UI, documentation contained
> therein
> will always work.
>
> 2.) There are different versions of BackupPC in use, and as development
> continues, there will be more of them. Documentation may change as
> BackupPC changes and not be applicable to previous versions. While you
> *can* reference distinct online versions of the documentation, you gain
> exactly nothing. If you do that, you might as well distribute the
> online
> documentation you would want to reference with the BackupPC version it
> applies to.
> What you are probably thinking of is an evolving documentation that
> gets
> better while the installed BackupPC version stays the same. This
> evolving
> documentation would need to account for differences in BackupPC
> versions,
> thus becoming more and more complex and confusing - much the opposite
> from
> what you are trying to achieve.
>
> As for the pure information, there is simply so much of it out there, that
> people don't find (or don't read) what they are looking for. I've explained
> the difference between full and incremental backups here so many times,
> that
> I'm simply tired of repeating it when it comes up once again. In a
> nutshell,
> incremental backups are a trade-off of exactness for speed, invented in an
> era when it was simply not feasible to do daily (tape-based) full backups.
> There might be valid reasons even today for not doing full backups daily,
> but
> the apparent general attitude of "I don't need exact backups, I just need
> fast
> backups" begs for the answer "don't do any backups at all - that's as fast
> as it gets, and it's not much worse than inaccurate backups". Of course,
> your
> application may vary (and BackupPC incremental backups are in general
> reasonably accurate, presuming you are using rsync(d)).
>
> Regards,
> Holger
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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 v3 to v4.1.3: v3 pool is still very large

[Craig Barratt via BackupPC-users]

Chrisich,

Do you have any hosts that didn't get backed up (or have backups disabled)
during that period?

Craig

On Wed, Oct 4, 2017 at 8:27 AM, oetschi.ex...@bluewin.ch <
oetschi.ex...@bluewin.ch> wrote:

> Hello all of you,
>
> For years I am using backuppc and I like it very much. There is only one
> (hopefully small) problem:
> After the upgrade from version 3 to version 4.1.3 on July 8th the pool of
> version 3 stays the the same for weeks.
> I reduced the FullAgeMax and IncrAgeMax to 50 days. So all the v3 files
> should have gone, but they are still here...
> I put in the lines from status:
>
>
>- Pool is 3050.47+1877.42GiB comprising 501222+61158 files and
>16512+4369 directories (as of 10/3 15:09),
>- Pool hashing gives 0+13 repeated files with longest chain 0+1,
>- Nightly cleanup removed 277+0 files of size 0.23+0.00GiB (around
>10/3 15:09),
>
> My question now is: How can I delete all these v3 files?
>
> Thanks for any help and kind regards
>
> Chrisich
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Archive to tape library

[Craig Barratt via BackupPC-users]

No, this isn't supported.  There are tools (like BackupPC_tarCreate) in
BackupPC that could be used with external tools or scripts to write/manage
tapes.

Or you could run something like Bacula in parallel with BackupPC if you
really want tapes.

Craig

On Thu, Oct 12, 2017 at 11:08 AM, Gandalf Corvotempesta <
gandalf.corvotempe...@gmail.com> wrote:

> Hi to all
> Is possible to use backuppc archive function to make tar archives on a
> tape library?
>
> While backuppc able to automatically change tapes?
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] BPC4: checksum

[Craig Barratt via BackupPC-users]

I was hoping the docs were clear :).

"Filled" means a backup contains a complete representation of the backup.
No other backups have to be merged to view/browse/restore.  Any backup can
be filled.  The most recent backup is always filled.

Non-filled backups are represented only as deltas (changes) from the next
more recent backup.  So to view/browse/restore a non-filled backup,
BackupPC has to start with the nearest future filled backup, and work
backwards merging every delta until you get to the backup of interest.

The reason you want some backups periodically filled is that
viewing/browsing/restoring an old back would otherwise be very slow.  In
your example with FullPeriod = 120 and you keep 120+ incrementals, you will
have to merge 119 backups to view/browse/restore the backup from 119 days
ago.

By default (with $Conf{FillCycle}) set to zero, every full backup is
filled, and every incremental backup is not filled.  When $Conf{FillCycle}
is non-zero, some of the incrementals will be filled. In your case, if you
set $Conf{FillCycle} to 10, then every 10th backup will be filled, and
you'll only need to merge at most 9 deltas to view/browse/restore any older
backup.

Note that a filled backup does use more inodes than a delta (~3 per
directory), but otherwise doesn't use much more storage, so the cost is
relatively small in terms of storage.

Craig

On Sun, Nov 5, 2017 at 7:55 PM, Gandalf Corvotempesta <
gandalf.corvotempe...@gmail.com> wrote:

> What's the difference between a filled backup and a full one?
>
> Currently I have set FullPeriod to 120 as we would like to only do
> incrementals, but what's the fillcycle?
> Doc's are unclear about this, at least for non native English readers
>
>
>
>
>
> Il 6 nov 2017 2:38 AM, "Craig Barratt via BackupPC-users" <
> backuppc-users@lists.sourceforge.net> ha scritto:
>
> Removing --checksum will make an rsync full behave just like an
> incremental.
>
> An equivalent, and clearer, way to do that is to only do incrementals.
> BackupPC 4.x allows you to do that.  That can be accomplished by setting
> $Conf{FullPeriod} to a large value.  You should also set $Conf{FillCycle}
> to, eg, 7, so that every 7th backup is stored filled (doesn't affect the
> client transfer).
>
> I agree with Les that a reasonable compromise is to set $Conf{FullPeriod}
> to, eg, 28 or 56 so you do actually get a full backup every 4 or 8 weeks.
>
> Craig
>
> On Fri, Oct 27, 2017 at 9:42 AM, Les Mikesell <lesmikes...@gmail.com>
> wrote:
>
>> On Fri, Oct 27, 2017 at 10:11 AM, Gandalf Corvotempesta
>> <gandalf.corvotempe...@gmail.com> wrote:
>> > I'm using ZFS, so checksumming is done by ZFS itself, is not an issue
>> for me
>> > to skip any data corruption check, as zfs does this automatically
>> >
>> > What I would like is to keep load as low as possible on clients and
>> > checksumming every file is slowing down everything
>>
>> I don't currently have a system running so I can't give very specific
>> advice, but if I were doing it I'd probably try to fix the schedule to
>> do fulls every 4 or 8 weeks and make them happen on weekends if that
>> is down time on the clients, skewing them so different large clients
>> get the full on different weekends and ones that complete overnight on
>> weekdays.Alternatively, if the target data is neatly subdivided
>> into top level directories, I might try to split runs to a single
>> large host giving it multiple names, each with different shares, using
>> ClientNameAlias to point it to the same target to make it possible to
>> split the fulls into different days so each completes in the available
>> time.
>>
>> --
>>Les Mikesell
>>  lesmikes...@gmail.com
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> 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/
>>
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-u

Re: [BackupPC-users] Backup hung well past timeout value

[Craig Barratt via BackupPC-users]

What's your BackupPC version and XferMethod?

Craig

On Wed, Oct 25, 2017 at 6:28 AM, Jenkins, Wade William 
wrote:

> I’ve got the timeout for my backups set at 36000 seconds (10hrs).  I’ve
> currently got two backups that appear to have been hung/inactive for almost
> 5 days.
>
>
>
> I’m trying to dig through the logs and see what might have happened, but I
> can’t figure out why it would a backup would persist that far beyond the
> timeout value.  Any help?
>
>
>
> -Wade
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] BPC4: checksum

[Craig Barratt via BackupPC-users]

Removing --checksum will make an rsync full behave just like an incremental.

An equivalent, and clearer, way to do that is to only do incrementals.
BackupPC 4.x allows you to do that.  That can be accomplished by setting
$Conf{FullPeriod} to a large value.  You should also set $Conf{FillCycle}
to, eg, 7, so that every 7th backup is stored filled (doesn't affect the
client transfer).

I agree with Les that a reasonable compromise is to set $Conf{FullPeriod}
to, eg, 28 or 56 so you do actually get a full backup every 4 or 8 weeks.

Craig

On Fri, Oct 27, 2017 at 9:42 AM, Les Mikesell  wrote:

> On Fri, Oct 27, 2017 at 10:11 AM, Gandalf Corvotempesta
>  wrote:
> > I'm using ZFS, so checksumming is done by ZFS itself, is not an issue
> for me
> > to skip any data corruption check, as zfs does this automatically
> >
> > What I would like is to keep load as low as possible on clients and
> > checksumming every file is slowing down everything
>
> I don't currently have a system running so I can't give very specific
> advice, but if I were doing it I'd probably try to fix the schedule to
> do fulls every 4 or 8 weeks and make them happen on weekends if that
> is down time on the clients, skewing them so different large clients
> get the full on different weekends and ones that complete overnight on
> weekdays.Alternatively, if the target data is neatly subdivided
> into top level directories, I might try to split runs to a single
> large host giving it multiple names, each with different shares, using
> ClientNameAlias to point it to the same target to make it possible to
> split the fulls into different days so each completes in the available
> time.
>
> --
>Les Mikesell
>  lesmikes...@gmail.com
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Backups missing from webpage

[Craig Barratt via BackupPC-users]

Gerald,

3.1 is a pretty old version.  But it includes a script
bin/BackupPC_fixupBackupSummary which tries to re-create the backups file.

I'd recommend making a backup copy of the backups file:

su backuppc
cd /var/lib/backuppc/pc/wpg-sbs.erlphase.com

cp backups backups.save

/usr/local/BackupPC/bin/BackupPC_fixupBackupSummary wpg-sbs.erlphase.com

Then compare the updated backups file with the old one.  Does it now
include additional entries for the old backups?

Craig

On Wed, Nov 1, 2017 at 12:05 PM, Gerald Brandt  wrote:

> BackupPC 3.1
>
> Ubuntu 14.04
>
>
> The web page doesn't show some of my early backups for one of my PCs. When
> I check the storage, I still see all my saved backup directories.
>
>
> Backup#TypeFilledLevelStart Date Duration/mins
> Age/daysServer Backup Path
> 904fullyes02017-07-31 19:49939.3 92.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/904
> 925fullyes02017-08-25 19:16844.3 67.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/925
> 929fullyes02017-08-31 19:58970.5 61.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/929
> 930fullyes02017-09-01 19:12910.5 60.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/930
> 935fullyes02017-09-08 19:23863.4 53.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/935
> 940fullyes02017-09-15 19:26915.5 46.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/940
> 946fullyes02017-09-22 18:59853.1 39.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/946
> 952fullyes02017-09-29 19:33751.7 32.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/952
> 958fullyes02017-10-06 19:22716.9 25.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/958
> 964fullyes02017-10-13 19:26753.3 18.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/964
> 970fullyes02017-10-20 18:58721.1 11.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/970
> 972incrno12017-10-23 18:1457.0 8.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/972
> 973incrno12017-10-24 18:1460.5 7.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/973
> 974incrno12017-10-25 18:1459.6 6.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/974
> 975incrno12017-10-26 18:1555.3 5.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/975
> 976fullyes02017-10-27 18:33748.5 4.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/976
> 977incrno12017-10-29 18:1158.9 2.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/977
> 978incrno12017-10-30 18:0749.6 1.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/978
> 979fullyes02017-10-31 18:20838.2 0.8
> /var/lib/backuppc/pc/wpg-sbs.erlphase.com/979
>
>
> # ls
>
> root@backuppc:/var/lib/backuppc/pc/wpg-sbs.erlphase.com# ls
> 101  739  978 RestoreInfo.5XferLOG.139.z XferLOG.236.z
> XferLOG.304.z  XferLOG.404.z  XferLOG.509.z XferLOG.608.z  XferLOG.720.z
> XferLOG.827.z  XferLOG.925.z
> 159  777  979 RestoreInfo.6XferLOG.142.z XferLOG.237.z
> XferLOG.305.z  XferLOG.408.z  XferLOG.515.z XferLOG.609.z  XferLOG.726.z
> XferLOG.828.z  XferLOG.929.z
> 181  804  backups RestoreInfo.7XferLOG.149.z XferLOG.238.z
> XferLOG.311.z  XferLOG.414.z  XferLOG.521.z XferLOG.614.z  XferLOG.732.z
> XferLOG.833.z  XferLOG.930.z
> 20   828  backups~RestoreInfo.8XferLOG.14.z XferLOG.23.z
> XferLOG.317.z  XferLOG.41.z   XferLOG.527.z XferLOG.620.z  XferLOG.738.z
> XferLOG.839.z  XferLOG.935.z
> 202  854  backups.old RestoreInfo.9XferLOG.153.z XferLOG.244.z
> XferLOG.323.z  XferLOG.420.z  XferLOG.533.z XferLOG.626.z  XferLOG.739.z
> XferLOG.83.z   XferLOG.940.z
> 223  879  LOCKRestoreLOG.10.z  XferLOG.159.z XferLOG.245.z
> XferLOG.325.z  XferLOG.426.z  XferLOG.534.z XferLOG.632.z  XferLOG.744.z
> XferLOG.845.z  XferLOG.946.z
> 245  904  LOG.012017.zRestoreLOG.11.z  XferLOG.165.z XferLOG.250.z
> XferLOG.329.z  XferLOG.431.z  XferLOG.53.z XferLOG.636.z  XferLOG.750.z
> XferLOG.850.z  XferLOG.952.z
> 271  925  LOG.022017.zRestoreLOG.12.z  XferLOG.172.z XferLOG.256.z
> XferLOG.335.z  XferLOG.432.z  XferLOG.540.z XferLOG.638.z  XferLOG.756.z
> XferLOG.854.z  XferLOG.958.z
> 298  929  LOG.032017.zRestoreLOG.13.z  XferLOG.180.z XferLOG.262.z
> XferLOG.341.z  XferLOG.438.z  XferLOG.541.z XferLOG.644.z  XferLOG.762.z
> XferLOG.856.z  XferLOG.95.z
> 325  930  LOG.042017.zRestoreLOG.4.z   XferLOG.181.z XferLOG.268.z
> XferLOG.347.z  XferLOG.444.z  XferLOG.542.z XferLOG.650.z  XferLOG.767.z
> XferLOG.862.z  XferLOG.964.z
> 351  935  LOG.052017.zRestoreLOG.5.z   XferLOG.187.z XferLOG.271.z
> XferLOG.351.z  XferLOG.450.z  XferLOG.543.z XferLOG.656.z  XferLOG.777.z
> XferLOG.868.z  XferLOG.970.z
> 378  940  LOG.062017.zRestoreLOG.6.z   XferLOG.192.z XferLOG.274.z
> XferLOG.353.z  

Re: [BackupPC-users] Backup via FTP not using overrides

[Craig Barratt via BackupPC-users]

I'm not sure why those lines got commented out - clearly a mistake. Thanks
for figuring it out. I just made a commit with them uncommented.

Craig

On Sun, Nov 5, 2017 at 12:13 PM, Adam W  wrote:

> After looking through the code, I noticed that the line to read in the
> override was commented out in Ftp.pm.  I removed the comment it and appears
> to be working now.
>
>
> Is there a reason this line (along with a few others) are commented out?
>
>
> Thanks.
>
>
> Adam
>
>
> --
> *From:* Adam W 
> *Sent:* Sunday, November 5, 2017 12:23 AM
> *To:* backuppc-users@lists.sourceforge.net
> *Subject:* Backup via FTP not using overrides
>
>
> It appears that when backing up using FTP that the overrides are not being
> used.  This worked in version 3.x but appears to have broke after upgrading
> to 4.1.3.
>
>
> For example, here is the error from the host log:
>
>
> 2017-11-05 00:15:04 xfer start failed: Can't open ftp connection to
> 192.168.1.109: Connection refused
>
>
> Here is the config:
>
>
> cat /etc/BackupPC/pc/192.168.1.109.pl
> $Conf{XferMethod} = 'ftp';
> $Conf{FtpShareName} = [
>   '/sdcard'
> ];
> $Conf{FtpUserName} = 'someuser';
> $Conf{FtpPasswd} = 'somepassword';
> $Conf{FtpPort} = 42546;
>
>
> Here is the tcpdump (.104 is where BackupPC is running and .109 is what I
> want to backup):
>
>
> tcpdump: listening on ens32, link-type EN10MB (Ethernet), capture size
> 262144 bytes
> 00:15:04.832970 IP (tos 0x0, ttl 64, id 53945, offset 0, flags [DF], proto
> TCP (6), length 60)
> 192.168.1.104.39280 > 192.168.1.109.21: Flags [S], cksum 0x8454
> (incorrect -> 0x9476), seq 336259106, win 29200, options [mss
> 1460,sackOK,TS val 3976542875 ecr 0,nop,wscale 7], length 0
> 0x:  4500 003c d2b9 4000 4006 e3dc c0a8 0168  E..<..@.@..h
> 0x0010:  c0a8 016d 9970 0015 140a e822    ...m.p."
> 0x0020:  a002 7210 8454  0204 05b4 0402 080a  ..r..T..
> 0x0030:  ed05 3a9b   0103 0307..:.
> 00:15:04.837357 IP (tos 0x0, ttl 64, id 6730, offset 0, flags [DF], proto
> TCP (6), length 40)
> 192.168.1.109.21 > 192.168.1.104.39280: Flags [R.], cksum 0x95f7
> (correct), seq 0, ack 336259107, win 0, length 0
> 0x:  4500 0028 1a4a 4000 4006 9c60 c0a8 016d  E..(.J@.@..`...m
> 0x0010:  c0a8 0168 0015 9970   140a e823  ...h...p...#
> 0x0020:  5014  95f7       P.
> ^C
> 2 packets captured
> 2 packets received by filter
> 0 packets dropped by kernel
>
>
>
> Notice that it is trying to connect on port 21 instead of using the
> override of 42546 which is leading to the connection refused error.
>
>
> Any thoughts on why the override isn't being used?
>
>
> Thanks.
>
>
> Adam
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] Automatic backups not working

[Craig Barratt via BackupPC-users]

Have you looked in both the main server log, and the per-host log?

An alternative is to manually run BackupPC_dump with the -v option.  It
should say what it's doing or not doing:

su backuppcUser
/usr/local/BackupPC/bin/BackupPC_dump -v HOST

Also, please confirm that your HOST's (and/or main) config file have
reasonable values for
$Conf{BackupsDisable}, $Conf{IncrPeriod}, $Conf{FullPeriod},
$Conf{BlackoutPeriods}
and $Conf{BlackoutGoodCnt}.

Craig

On Sat, Oct 7, 2017 at 5:09 PM, Gandalf Corvotempesta <
gandalf.corvotempe...@gmail.com> wrote:

> It doesn't log anything.
> Simply it doesn't connect and wait up to the timeout value
>
> If I run backup manually from the interface, it works
>
> Il 7 ott 2017 11:04 PM, "Michael Stowe" 
> ha scritto:
>
>> On 2017-10-07 02:07, Gandalf Corvotempesta wrote:
>>
>> Any hint ?
>>
>> 2017-10-06 9:38 GMT+02:00 Gandalf Corvotempesta <
>> gandalf.corvotempe...@gmail.com>:
>>
>> Hi, I have a strange issue. Automatic backup scheduling is unable to
>> backup (every time) 3 hosts. If I abort the automatic scheduled backup and
>> run it manually from CGI, backup is running properly.
>>
>> Any idea ?
>>
>> “Unable to backup” is virtually nothing to go on. BackupPC has logs that
>> can be reviewed, both for the main backup and for individual transports.
>>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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] netbios name not retrieved

[Craig Barratt via BackupPC-users]

That's not the expected output from nmblookup for a valid netbios host name.

If the host has a fixed IP address, it's much better to use that.  You can
use whatever host name you want, and set $Conf{ClientNameAlias} to its IP
address.

Craig

On Fri, Sep 29, 2017 at 6:11 AM, François Dagorn 
wrote:

> Hello all,
>
> I'm just beginning with BackupPc, my main goal is to backup the single
> Linux smb server of a brand new small company
> and when it will be ok, then I will try to save some Windows 10 laptops.
> Well, both smb server and BackupPc server are running Centos 7.
> I've installed the whole stuff using "*yum install backuppc*" and I'm
> just trying to use it by now.
>
> I've got a problem with the netbios name and the way BackupPc is supposed
> to find hosts :
>
> - I've read that i*f gethostbyname() fails, BackupPC then attempts a
> NetBios multicast to find the host*
> - running by hand "*nmblookup*" on the BacpupPc side runs well, the
> result is as follows :
>
>   nmblookup myshare
>   192.168.1.10 myshare <00>
>
> - so I guess all is ok.
>
> Unfortunately, if I add a host with the netbios name, it does not work at
> all
> If I add the same host using his IP address, then it works fine !
>
> Any help would be appreciated.
>
> Cheers.
>
> François Dagorn
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> 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/
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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/