: Monday, May 6, 2024 17:55
To: backuppc-users@lists.sourceforge.net
Subject: [BackupPC-users] BackupPC remembers _everything_
BackupPC has been covering up my stupid mistakes since 2005.
Fortunately, I have never done the 'rm -r *' until last week. Good thing
was that I was in my home directory so
That shouldn't of course happen -- though you did violate the first
rule of backups which is to *test* them so they are there and working
when you need them
You would need to tell us a lot more details if you want help.
My guess given the lack of any other diagnostic information is that
perhaps
BackupPC has been covering up my stupid mistakes since 2005.
Fortunately, I have never done the 'rm -r *' until last week. Good thing
was that I was in my home directory so the system itself was untouched
and I caught myself before too much could get deleted.
'Not a problem!' I thought. I
Do I need to migrate anything with V3 to V4 upgrade (using tar, no rsync)?
I am fine having old backups in V3, create a new ones with V4. Does
BackupPC V4 handles this? I know there is
/usr/share/BackupPC/bin/BackupPC_migrateV3toV4 -a
but is it mandatory to continue backuppc operation?
My
On 5/22/2023 7:48 AM, G.W. Haywood via BackupPC-users wrote:
There have been issues with differing versions of rsync, if you search
the list archives you'll find plenty of mention of that - you'll even
see the exact same error message which you posted.
I concur. I've seen similar issues with
Hi there,
On Mon, 22 May 2023, Gregory P. Ennis wrote:
I recently upgraded my raspberrypi4 to a 64 bit os from 32 which had an upgrade
of BackupPc from 3 to 4. This created an enhancement going from the 5 kernel to
6. BackupPC 3 on the 5 kernel worked perfectly, but so far BackupPC 4 fails
Everyone,
I recently upgraded my raspberrypi4 to a 64 bit os from 32 which had an upgrade
of BackupPc from 3 to 4. This created an enhancement going from the 5 kernel to
6. BackupPC 3 on the 5 kernel worked perfectly, but so far BackupPC 4 fails to
wprk on the 6 kernel.
So far I have not been
On 4/5/23 10:57, G.W. Haywood via BackupPC-users wrote:
Hi there,
On Wed, 5 Apr 2023, Mark Murawski wrote:
...
$Conf{BackupFilesOnly} = {
'/' => [
'bin',
'apps',
'opt',
'lib32',
'intellasoft',
'etc',
'manageServ',
'boot',
'var',
'lib',
'lib64',
Hi there,
On Wed, 5 Apr 2023, Mark Murawski wrote:
...
$Conf{BackupFilesOnly} = {
'/' => [
'bin',
'apps',
'opt',
'lib32',
'intellasoft',
'etc',
'manageServ',
'boot',
'var',
'lib',
'lib64',
'usr',
'home',
'sbin'
]
};
XferLOG.bad.z
Running: /usr/bin/env LC_ALL=C /usr/bin/sudo /bin/tar -c -v -f - -C /
--totals --exclude=sys --exclude=home/backuppc --exclude=proc
--exclude=var/lib/postgres --exclude=var/log ./bin ./apps ./opt
./lib32 ./intellasoft ./etc ./manageServ ./boot ./var ./lib ./lib64
./usr ./home
I'm lucky to never have faced that problem :)
I'm not sure a simple "touch" will force a new transfer. By default an
incremental backup will only check (and transfer) the new metadata, but it
will not transfer the file. A full will calculate the checksum, but again
it won't transfer the file
Hi!
So I found a few dozen corrupt files, and made some scripts to find the original
files from the hash.
Not sure how to fix the backups... Touch the original file and delete the one
in the
cpool?
Regards,
Ludo
On Sun, Jul 31, 2022 at 07:22:11PM +0200, Ludovic Drolez wrote:
> Hi!
>
> So
to a new config completely as something else may
be causing the backups to hang around forever... and not the config
settings in my original post only,
Thanks for the reply!
Johan
On Tue, Aug 2, 2022 at 12:55 PM Jon Daley via BackupPC-users <
backuppc-users@lists.sourceforge.net> wrote:
>
I'm sure we all got it. I just don't have an answer.
When I did the same upgrade, I went through the whole config file and
merged over my changes - it looked to me like there was a lot of stuff
that changed, so I wasn't confident that simply using my old config file
would work.
Since you
Hi!
So I've tried it and I have a few v3 pool files still in the cpool.
I should try to modify your script to ignore them, because they give errors.
Thanks!
Ludo
On Thu, Jul 28, 2022 at 04:34:40PM -0300, Guillermo Rozas wrote:
>You may try (and modify)
>this:
Many thanks for your script!
Ludo
On Thu, Jul 28, 2022 at 04:34:40PM -0300, Guillermo Rozas wrote:
>You may try (and modify)
>this: [1]https://github.com/guille2306/backuppc_check_pool
>It's a script I made to periodically check the V4 cpool in my server.
>Best regards,
>
You may try (and modify) this:
https://github.com/guille2306/backuppc_check_pool
It's a script I made to periodically check the V4 cpool in my server.
Best regards,
Guillermo
On Thu, Jul 28, 2022 at 4:26 PM Ludovic Drolez wrote:
> Hi there!
>
> I had to copy a Backuppc pool disk which was
Hi there!
I had to copy a Backuppc pool disk which was failing. DDrescue had to skip a
few bad blocks,
and now I'd like to check the integrity of the pool.
Is there is script to run and check which files do not have a matching MD5
checksum?
Best regards,
--
Ludo
https://drolez.com/blog/
Hi there,
On Mon, 25 Jul 2022, Iosif Fettich wrote:
... you might fight a TCP level failure between some intermediate routers.
Which I acknowledge that almost anything is possible, it's difficult
to see how a problem like that would suddenly present itself simply
because of an upgrade to
Hi Taste-Of-IT,
and thanks for the hint, but it didnt work. I tried =30 but got the same error.
I have actually no clue to solve this.
Maybe check if TCPKeepAlive would help. My doc says default is yes, but
who knows...
Maybe you can run the command manually at some point, while sitting
Hi Libor,
and thanks for the hint, but it didnt work. I tried =30 but got the same error.
I have actually no clue to solve this.
thx
Taste
--
Am 22.07.2022 12:57:31, schrieb Libor Klepáč:
> Hi,
> we used timeout of 6 ;)
>
> So maybe firewall/router kills your connection when idle. We
Hi,
we used timeout of 6 ;)
So maybe firewall/router kills your connection when idle. We send
keepalive packets in ssh
$Conf{RsyncSshArgs} = [
'-e',
'$sshPath -o ServerAliveInterval=60 -q -x -l user'
];
Libor
On Pá, 2022-07-22 at 09:33 +, Taste-Of-IT wrote:
> Hi All,
>
> i have
Hi All,
i have tried --timeout=3600 and i see it in the error log, but it seems not to
work. Strange is that i get only 14.700 Files, what is not quit a lot. Here the
errors i got:
packet_write_wait: Connection to 138.201.128.178 port 22: Broken pipe
rsync_bpc: connection unexpectedly closed
Hi,
I don't know, if it's still the case, but we used to increase --timeout
parameter of rsync in the past.
Also check, that your firewall does not close connections without
traffic
When rsync searches for changes, there can/could be long periods of
time without any traffic.
That caused timeout or
Hi all,
i had time to make some tests. I run some local tests and figure out, that its
not an problem with rsync 3.2.3. On local debian 11 systems, there was no
problem with similar configuration. Because of noticing that the runtime with
debian 11 seems to be longer than with debian 10, i
lete','--partial',
> '--log-format=log: %o %i %B %8U,%8G %9l %f%L','--stats',];*
> The above was done inside all of the .pl config files for all hosts, as we
> use a separate file per host.
>
> Hope this helps!
>
> On Mon, Jul 11, 2022 at 9:41 AM Dave Sherohman via Backu
Hi,
thanks for your reply. Rsync is installed, thats not the problem.
Am 11.07.2022 09:23:06, schrieb Dave Sherohman via BackupPC-users:
> Since you mentioned different versions of rsync, I assume you already
> checked this, but, just in case: Double-check that rsync is still
> installed on
','--partial',
'--log-format=log: %o %i %B %8U,%8G %9l %f%L','--stats',];*
The above was done inside all of the .pl config files for all hosts, as we
use a separate file per host.
Hope this helps!
On Mon, Jul 11, 2022 at 9:41 AM Dave Sherohman via BackupPC-users <
backuppc-us
Since you mentioned different versions of rsync, I assume you already
checked this, but, just in case: Double-check that rsync is still
installed on the deb11 system. I upgraded a ton of systems from deb9 to
deb11 earlier in the summer, and apt decided to uninstall rsync during
the upgrades
I had an issue after upgrading my server to Ubuntu 22.04, as if the
existing host config wasn't getting applied. What I did to help trace
the error was opening a terminal on the client I was backing up and
running 'tail -f' on the /var/log/secure (or /var/log/authlog file for
Debian based
Are you using rsync over ssh? If so, one thing I like to try is to ssh manually
using the backuppc user.
On July 10, 2022 6:23:58 AM EDT, Taste-Of-IT wrote:
>Hi all,
>
>i have latest BackupPC running on Debian 10. I upgraded one system to Debian
>11. Backup before running well and without
Hi all,
i have latest BackupPC running on Debian 10. I upgraded one system to Debian
11. Backup before running well and without problems. After upgrading the client
it fails with these errors:
Got fatal error during xfer (rsync error: unexplained error (code 255) at
io.c(820)
Does anyone have handy a Caddyfile stanza for running backuppc with
the Caddy web server, rather than Apache?
paul
=--
paul fox, p...@foxharp.boston.ma.us (arlington, ma)
___
BackupPC-users mailing list
Kenneth Porter wrote at about 20:11:19 -0800 on Sunday, January 23, 2022:
> On 1/23/2022 6:52 AM, backu...@kosowsky.org wrote:
> > BTW thanks for the help so far... it seems like you really understand
> > the rsync code...:)
>
> Not really. I've just written some network code and lots of
>
On 1/23/2022 6:52 AM, backu...@kosowsky.org wrote:
BTW thanks for the help so far... it seems like you really understand
the rsync code...:)
Not really. I've just written some network code and lots of
multi-threaded code (which rsync isn't) for embedded systems so can make
educated guesses
backu...@kosowsky.org wrote at about 13:04:21 -0500 on Sunday, January 23, 2022:
> backu...@kosowsky.org wrote at about 00:29:11 -0500 on Sunday, January 23,
> 2022:
> > backu...@kosowsky.org wrote at about 21:53:48 -0500 on Saturday, January
> 22, 2022:
> > > Kenneth Porter wrote at
backu...@kosowsky.org wrote at about 00:29:11 -0500 on Sunday, January 23, 2022:
> backu...@kosowsky.org wrote at about 21:53:48 -0500 on Saturday, January 22,
> 2022:
> > Kenneth Porter wrote at about 18:27:52 -0800 on Saturday, January 22,
> 2022:
> > > --On Saturday, January 22, 2022
backu...@kosowsky.org wrote at about 09:52:26 -0500 on Sunday, January 23, 2022:
> Kenneth Porter wrote at about 01:51:53 -0800 on Sunday, January 23, 2022:
> > On 1/22/2022 11:45 PM, backu...@kosowsky.org wrote:
> > > #1 0x5543fc43 in perform_io (needed=2, flags=2) at io.c:742
> >
Kenneth Porter wrote at about 01:51:53 -0800 on Sunday, January 23, 2022:
> On 1/22/2022 11:45 PM, backu...@kosowsky.org wrote:
> > #1 0x5543fc43 in perform_io (needed=2, flags=2) at io.c:742
>
> This smells like a deadlock. This code is waiting for 2 bytes in the
> socket output
On 1/22/2022 11:45 PM, backu...@kosowsky.org wrote:
#1 0x5543fc43 in perform_io (needed=2, flags=2) at io.c:742
This smells like a deadlock. This code is waiting for 2 bytes in the
socket output buffer so it can write the file's next block checksum.
Perhaps the other side is failing
Kenneth Porter wrote at about 18:27:52 -0800 on Saturday, January 22, 2022:
> --On Saturday, January 22, 2022 8:55 PM -0500 backu...@kosowsky.org wrote:
>
> > It gets "stuck" at varying places... as IO slows to a complete halt
> > (based on iftop) until rsync timesout.
> > Similarly,
Kenneth Porter wrote at about 19:43:07 -0800 on Saturday, January 22, 2022:
> On 1/22/2022 6:28 PM, backu...@kosowsky.org wrote:
> > write(2, "IOrename: 27 .smart_stay_hash.dm"..., 60) = 60
>
> Does it really use handle 2 (stderr) for writing a log of files it's
> processed? I haven't
backu...@kosowsky.org wrote at about 21:53:48 -0500 on Saturday, January 22,
2022:
> Kenneth Porter wrote at about 18:27:52 -0800 on Saturday, January 22, 2022:
> > --On Saturday, January 22, 2022 8:55 PM -0500 backu...@kosowsky.org wrote:
> >
> > > It gets "stuck" at varying places... as
On 1/22/2022 6:28 PM, backu...@kosowsky.org wrote:
write(2, "IOrename: 27 .smart_stay_hash.dm"..., 60) = 60
Does it really use handle 2 (stderr) for writing a log of files it's
processed? I haven't looked at the sources but I wonder if that's an
unrelated bug.
Kenneth Porter wrote at about 18:27:52 -0800 on Saturday, January 22, 2022:
> --On Saturday, January 22, 2022 8:55 PM -0500 backu...@kosowsky.org wrote:
>
> > It gets "stuck" at varying places... as IO slows to a complete halt
> > (based on iftop) until rsync timesout.
> > Similarly,
--On Saturday, January 22, 2022 8:55 PM -0500 backu...@kosowsky.org wrote:
It gets "stuck" at varying places... as IO slows to a complete halt
(based on iftop) until rsync timesout.
Similarly, 'strace' stalls.
This happens even if I run rsync_bpc from the command line directly,
but it does
Not sure if this is helpful, but the output of strace shows it stuck
in some timeout loop:
stat("/var/lib/backuppc/cpool/7e/4e/7e4e672bd913eadb030d0670aecb6607",
0x7ffe64b62770) = -1 ENOENT (No such file or directory)
stat("/var/lib/backuppc/cpool/3a/e2/3ae2b652d5cda073df7af75d3bb3ecdf",
Need to take this back.
It has nothing to do with the cam_socket.
It gets "stuck" at varying places... as IO slows to a complete halt
(based on iftop) until rsync timesout.
Similarly, 'strace' stalls.
This happens even if I run rsync_bpc from the command line directly,
but it does *not* happen
G.W. Haywood via BackupPC-users wrote at about 12:49:14 + on Saturday,
January 22, 2022:
> Hi there,
>
> On Sat, 22 Jan 2022, Jeff Kosowsky wrote:
>
> > ...
> > log: recv cS+ rwxrwx--- 1006,1006 0 cam_socket0
> > log: recv cS+ rwxrwx--- 1006,
G.W. Haywood via BackupPC-users wrote at about 12:49:14 + on Saturday,
January 22, 2022:
> Hi there,
>
> On Sat, 22 Jan 2022, Jeff Kosowsky wrote:
>
> > ...
> > log: recv cS+ rwxrwx--- 1006,1006 0 cam_socket0
> > log: recv cS+ rwxrwx--- 1006,
Hi there,
On Sat, 22 Jan 2022, Jeff Kosowsky wrote:
...
log: recv cS+ rwxrwx--- 1006,1006 0 cam_socket0
log: recv cS+ rwxrwx--- 1006,1006 0 cam_socket1
log: recv >f+ rwx-- 1000,1000 8 hidden_volume.txt
it seems
Based on the log file generated by the (equivalent) "naked" rsync
backup
log: recv cS+ rwxrwx--- 1006,1006 0 cam_socket0
log: recv cS+ rwxrwx--- 1006,1006 0 cam_socket1
log: recv >f+ rwx-- 1000,1000 8
I have long been able to back up my (rooted) Android phones using
ssh/rsync.
I also have not problem backing up my Windows and Linux machines.
However, BackupPC timesout when I try to back up an old Samsung S3 (which
used to back up perfectly before). The timeout occurs no matter what
value I use
Yes, this is what backuppc is running on the server.
On 17/01/2022 23.20, robin hammond wrote:
Invocation, as it is happening on the server:
/usr/local/bin/rsync_bpc \
--bpc-top-dir\
/vol0/www/backuppc.cg5.databit7.com/data/\
--bpc-host-name\
phantom.databit7.com\
robin hammond wrote at about 01:11:45 -0500 on Tuesday, January 18, 2022:
>
> I went with plain text. I hope this is more readable.
>
> Invocation, as it is happening on the server:
>
> /usr/local/bin/rsync_bpc \
> --bpc-top-dir\
> /vol0/www/STUFF.databit7.com/data/\
>
I went with plain text. I hope this is more readable.
Invocation, as it is happening on the server:
/usr/local/bin/rsync_bpc \
--bpc-top-dir\
/vol0/www/STUFF.databit7.com/data/\
--bpc-host-name\
phantom.databit7.com\
--bpc-share-name\
/home/administrator\
Sorry,
I'll include better html, text versions with web-links to well formatted
data and repost.
Someone said something about '--' that sounds really familar, and do
need to refresh my basic understanding of this programme again.
On 15/01/2022 07.55, G.W. Haywood via BackupPC-users wrote:
robin hammond wrote at about 01:20:37 -0500 on Saturday, January 15, 2022:
> Update,
>
>
> I'm told to not mess with RsyncClientCmd - it's "depricated" (no source)
> whatever.
It was part of v3. v4 uses RsyncSshArgs.
>
> So I changed this instead:
>
> $Conf{RsyncSshArgs} = [
>
>
On the client in /etc/sudoers did you find this line
Defaults requiretty
and change to:
# Defaults requiretty
In some distros the "Defaults" are not present so you will
have to add the line. Sudo won't run through ssh unless you
do that.
Use visudo to make the edits.
--
Jim
Hi there,
On Sat, 15 Jan 2022, robin hammond wrote:
'--exclude=/*'\
'--exclude=/home/*'\
'phantom.databit7.com:/home/administrator/'\
'/'
but rsync fails to function with the error
bash: phanton.databit7.com: command not found
The log extract looks odd to me. You seem
Update,
I'm told to not mess with RsyncClientCmd - it's "depricated" (no source)
whatever.
So I changed this instead:
$Conf{RsyncSshArgs} = [
'-e' , '$sshPath -i /home/backuppc/.ssh/backupc_cg5_id_ed25519
root@$host ',
]
fine, now it works, almost.
That said invocation of
Hi all,
First posting. I have been running BackupPC on a Ubuntu 20.04 LTS file
server for about 18 months with almost no problems
I'm using Version 3.3.2 included in the Ubuntu distro. I hadn't updated
since my Linux knowledge is not great and I didn't feel confident to carry
out the various
G.W. Haywood via BackupPC-users wrote at about 16:15:29 +0100 on Wednesday,
September 15, 2021:
> Hi there,
>
> On Wed, 15 Sep 2021, Jeffrey J. Kosowsky wrote:
> > G.W. Haywood via BackupPC-users wrote:
> > > On Tue, 14 Sep 2021, Juergen Harms wrote:
> > >
> > > > Well, this discussion
Hi there,
On Wed, 15 Sep 2021, Jeffrey J. Kosowsky wrote:
G.W. Haywood via BackupPC-users wrote:
> On Tue, 14 Sep 2021, Juergen Harms wrote:
>
> > Well, this discussion really looks like a non-issue ...
>
> Unless you have a host named 'config'.
Or more precisely config.pl :)
No, that
Or more precisely config.pl :)
G.W. Haywood via BackupPC-users wrote at about 14:25:58 +0100 on Tuesday,
September 14, 2021:
> Hi there,
>
> On Tue, 14 Sep 2021, Juergen Harms wrote:
>
> > Well, this discussion really looks like a non-issue ...
>
> Unless you have a host named
Hi there,
On Tue, 14 Sep 2021, Juergen Harms wrote:
Well, this discussion really looks like a non-issue ...
Unless you have a host named 'config'.
--
73,
Ged.
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:
On 14/09/2021 03:34, Adam Goryachev via BackupPC-users wrote:
IMHO, it would appear that you had some config issue, and because things
were not working you looked for something to blame, the pc symlink
looked strange, and so you blamed that (at least that is what I did in
the past). Once you
Le 14/09/2021 à 03:34, Adam Goryachev via BackupPC-users a écrit :
On 14/9/21 02:00, Juergen Harms wrote:
This is not the place to fight for being right, but to understand and
document help for users who hit this kind of problem.
Trying to understand: how do you define separate and different
On 9/13/21 6:00 PM, Juergen Harms wrote:
This is not the place to fight for being right, but to understand and
document help for users who hit this kind of problem.
Agreed. But what kind of response is expected when you say "what makes
it *look as if* your installation works is that...", other
On 14/9/21 02:00, Juergen Harms wrote:
This is not the place to fight for being right, but to understand and
document help for users who hit this kind of problem.
Trying to understand: how do you define separate and different
profiles ("per-host override configs") for each of your 18
This is not the place to fight for being right, but to understand and
document help for users who hit this kind of problem.
Trying to understand: how do you define separate and different profiles
("per-host override configs") for each of your 18 different PCs in one
single .pl file (i.e. your
I say "it works" because (for me, at least) it. does. work.
I have per-host override files at /etc/backuppc/hostname.pl (which is
the same as /etc/backuppc/pc/hostname.pl, thanks to the symlink that you
seem to loathe so much). They work.
Hosts which do not have per-host override files in
On 9/12/2021 1:15 PM, jbk wrote:
By the time the digest came out I had figured out the issue. But to
followup on loose ends I can recap my findings. First, the client
command variable quoted below found in V3 is deprecated in V4.
Mea culpa. This time I saw the bold text, so this list DOES
On 9/9/21 9:51 PM, Kenneth Porter wrote:
--On Thursday, September 09, 2021 4:29 PM -0400 jbk
wrote:
The portion in bold below was not executed.
Like most mailing lists, this one is plain text only and
stripped out the HTML part with the bolding. So it's not
clear what part of the command
After tidying up, here is a PS meant as documentation:
- my hypothesis on the role of the loop-back item in /etc/backuppc
proofed wrong: Debian backuppc (contrary to the backuppc documentation)
simply expects pc-specific definition .pl files to figure in the
top-level directory
--On Thursday, September 09, 2021 4:29 PM -0400 jbk wrote:
The portion in bold below was not executed.
Like most mailing lists, this one is plain text only and stripped out the
HTML part with the bolding. So it's not clear what part of the command
wasn't executed.
On 9/11/21 6:35 PM, thveillon wrote:
Debian is known for its idiosyncrasy, which often is part of the
distribution added value, sometime is just added fun for the
administrator...
I am starting to have doubts on the benefit of replacing idiosyncrasy of
disto A with that of distro B. In
Le 11/09/2021 à 12:08, Juergen Harms a écrit :
On 11/09/2021 11:14, thveillon wrote:
Hello, I am using Backuppc 4 on Debian 11, migrated from a long
running Backuppc 3 installation.
Same for me, but - so far on Mageia
The symlink is a loop-back to the same directory, where I store my
Le 11/09/2021 à 09:23, Juergen Harms a écrit :
On 10/09/2021 09:18, Dave Sherohman wrote:
I'm not sure why Debian decided to do the pc/ symlink thing, but it
works. Debian was doing that with the BPC 3.x packages in debian10
and it never caused any problems that I'm aware of.
I am coming
On 10/09/2021 09:18, Dave Sherohman wrote:
I'm not sure why Debian decided to do the pc/ symlink thing, but it
works. Debian was doing that with the BPC 3.x packages in debian10 and
it never caused any problems that I'm aware of.
I am coming back to the symlink question, I did not take it
On 10/09/2021 09:18, Dave Sherohman wrote:
I'm not sure why Debian decided to do the pc/ symlink thing, but it
works. Debian was doing that with the BPC 3.x packages in debian10 and
it never caused any problems that I'm aware of.
The symlink thing is a nice feature - if it is properly
I installed BPC4 from the pre-release debian 11 repo back in March and
it Just Worked(TM), no problems at all. I'm currently backing up 89
hosts with it and haven't had to touch any of the BPC infrastructure
aside from setting up appropriate configs. It's solid.
I'm not sure why Debian
Greetings Juergen,
> Sent: Thursday, September 09, 2021 at 7:03 PM
> From: "Juergen Harms"
> To: backuppc-users@lists.sourceforge.net
> Subject: Re: [BackupPC-users] backuppc 4 fails without any log
>
> On 07/09/2021 11:43, daggs wrote:
> > looks like
I've been using BackupPC V3 for 12 years now and have set up
V4 on a new install of Rocky linux 8.4. I'm running test
backups of a client via ssh and I'm getting partial backups
with the backup failing after a few seconds.
I figured out the issue once I read the xfer log more
carefully. The
Hi there,
the infinite loop is not really a problem. it works. the same happened
with the debian-version of 3.x
But
the package does not install all required stuff:
the following was missing and needed to be installed after installation
on debian 11:
- smbclient
- samba-common-bin
only
I've been using BackupPC V3 for 12 years now and have set up
V4 on a new install of Rocky linux 8.4. I'm running test
backups of a client via ssh and I'm getting partial backups
with the backup failing after a few seconds.
Here is some log output:
full backup started for directory /
Xfer
On 07/09/2021 11:43, daggs wrote:
looks like the reason if the fact that RunDir is missing from config.pk, even
the sample one doesn't have it, is it logic?
I am not so sure that a missing RunDir is the fault - I had the same
message where the problem was a pure configuration issue.
Did
Hallo
I had planned to migrate from my present distro (my present system runs
a correct backuppc 4 installation), and had delayed my move until the
release of Debian-11.
I am deceived - the backuppc package in Debian-11 does not look solid:
- /etc/backuppc/pc (immediately after installation)
Saturday, August 28, 2021 at 9:11 PM
> From: "daggs"
> To: backuppc-users@lists.sourceforge.net
> Cc: backuppc-users@lists.sourceforge.net
> Subject: Re: [BackupPC-users] backuppc 4 fails without any log
>
> > Sent: Saturday, August 28, 2021 at 7:18 PM
> >
Hi,
Thanks for the reply. I finally found that localhost/admin worked.
Problem solved.
thanks again.
Gary R.
On 8/28/21 1:05 AM, Pascal Legrand wrote:
Hello,
may be for this reason found in the NEWS file of the tar.gz package:
> Sent: Saturday, August 28, 2021 at 7:18 PM
> From: "daggs"
> To: backuppc-users@lists.sourceforge.net
> Subject: [BackupPC-users] backuppc 4 fails without any log
>
> Greetings,
>
> I've installed backuppc v4 on my rpi4 arch install, completed migration of
Greetings,
I've installed backuppc v4 on my rpi4 arch install, completed migration of all
hosts from v3 and I'm trying to start it up, after running systemctl start
backuppc, I get the below as status:
Aug 28 16:13:07 backupserver systemd[1]: Started BackupPC.
Aug 28 16:13:07 backupserver
Hello,
may be for this reason found in the NEWS file of the tar.gz package:
http://deb.debian.org/debian/pool/main/b/backuppc/backuppc_4.4.0-3.debian.tar.xz
Debian's default BackupPC configuration file for Apache now restricts
access to BackupPC to localhost by default because by default
Hi all,
Operating System: Debian GNU/Linux 11
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.0-8-amd64
OS Type: 64-bit
Processors: 4 × AMD FX(tm)-4350 Quad-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: AMD CAICOS
I just installed
Just as an update...
I have been running BackupPC 4.x on my RPI4 with 8GB memory and an
external USB 1TB Samsung SSD.
It's been ROCK STABLE for the past 7 months -- no crashes in more than
200 days and I only rebooted once due to a kernel upgrade.
So in summary, it's a simple, fast, stable,
Doh
I had $Conf{PoolV3Enabled} =0
This allowed BackupPC_migrateV3toV4 to do it's thing but
BackupPC_nightly did not look at the v3 pool.
Glenn
On 2021-06-16 11:07, ve...@napan.com wrote:
Hi
I have been a Backuppc user for years and I have finally upgraded to
v4. Over the last few weeks I
Hi
I have been a Backuppc user for years and I have finally upgraded to v4.
Over the last few weeks I have been running BackupPC_migrateV3toV4 for
a few hours a day on a ~2TB cpool. All hosts and backups are now
migrated. BackupPC_migrateV3toV4 -a reports zero errors. I have let
On Fri, Jun 11, 2021 at 8:38 AM Michael Stowe
wrote:
> It is worth poking at the contention that "an incremental backup with rsyncd
> unfortunately takes as long as the full backup." This probably isn't true,
> but I can understand how one can believe this after running a single
>
On 2021-05-26 07:01, Jens Potthast wrote:
Hi,
My Problem: When doing an incremental backup with smb, only files with
mtime
newer than the date and time of the last backup are being backed up.
To reproduce: If I copy a file with an old ctime, the file is not
included
in the backup even if
Hi,
My Problem: When doing an incremental backup with smb, only files with mtime
newer than the date and time of the last backup are being backed up.
To reproduce: If I copy a file with an old ctime, the file is not included
in the backup even if it is not contained in the previous complete
1 - 100 of 2817 matches
Mail list logo
