You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(19) |
Nov
(2) |
Dec
(23) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(18) |
Feb
(15) |
Mar
(27) |
Apr
(6) |
May
(40) |
Jun
(53) |
Jul
(67) |
Aug
(107) |
Sep
(75) |
Oct
(74) |
Nov
(73) |
Dec
(63) |
| 2003 |
Jan
(93) |
Feb
(97) |
Mar
(72) |
Apr
(129) |
May
(110) |
Jun
(97) |
Jul
(151) |
Aug
(124) |
Sep
(66) |
Oct
(216) |
Nov
(105) |
Dec
(151) |
| 2004 |
Jan
(107) |
Feb
(181) |
Mar
(235) |
Apr
(212) |
May
(231) |
Jun
(231) |
Jul
(264) |
Aug
(278) |
Sep
(173) |
Oct
(259) |
Nov
(164) |
Dec
(244) |
| 2005 |
Jan
(318) |
Feb
(206) |
Mar
(287) |
Apr
(222) |
May
(240) |
Jun
(255) |
Jul
(166) |
Aug
(289) |
Sep
(233) |
Oct
(200) |
Nov
(307) |
Dec
(170) |
| 2006 |
Jan
(289) |
Feb
(270) |
Mar
(306) |
Apr
(150) |
May
(181) |
Jun
(263) |
Jul
(181) |
Aug
(291) |
Sep
(147) |
Oct
(155) |
Nov
(381) |
Dec
(310) |
| 2007 |
Jan
(431) |
Feb
(306) |
Mar
(378) |
Apr
(216) |
May
(313) |
Jun
(235) |
Jul
(373) |
Aug
(171) |
Sep
(459) |
Oct
(642) |
Nov
(464) |
Dec
(419) |
| 2008 |
Jan
(374) |
Feb
(445) |
Mar
(400) |
Apr
(406) |
May
(374) |
Jun
(346) |
Jul
(387) |
Aug
(302) |
Sep
(255) |
Oct
(374) |
Nov
(292) |
Dec
(488) |
| 2009 |
Jan
(392) |
Feb
(240) |
Mar
(245) |
Apr
(483) |
May
(310) |
Jun
(494) |
Jul
(265) |
Aug
(515) |
Sep
(514) |
Oct
(284) |
Nov
(338) |
Dec
(329) |
| 2010 |
Jan
(305) |
Feb
(246) |
Mar
(404) |
Apr
(391) |
May
(302) |
Jun
(166) |
Jul
(166) |
Aug
(234) |
Sep
(222) |
Oct
(267) |
Nov
(219) |
Dec
(244) |
| 2011 |
Jan
(189) |
Feb
(220) |
Mar
(353) |
Apr
(322) |
May
(270) |
Jun
(202) |
Jul
(172) |
Aug
(215) |
Sep
(226) |
Oct
(169) |
Nov
(163) |
Dec
(152) |
| 2012 |
Jan
(182) |
Feb
(221) |
Mar
(117) |
Apr
(151) |
May
(169) |
Jun
(135) |
Jul
(140) |
Aug
(108) |
Sep
(148) |
Oct
(97) |
Nov
(119) |
Dec
(66) |
| 2013 |
Jan
(105) |
Feb
(127) |
Mar
(265) |
Apr
(84) |
May
(75) |
Jun
(116) |
Jul
(89) |
Aug
(118) |
Sep
(132) |
Oct
(247) |
Nov
(98) |
Dec
(109) |
| 2014 |
Jan
(81) |
Feb
(101) |
Mar
(101) |
Apr
(79) |
May
(132) |
Jun
(102) |
Jul
(91) |
Aug
(114) |
Sep
(104) |
Oct
(126) |
Nov
(146) |
Dec
(46) |
| 2015 |
Jan
(51) |
Feb
(44) |
Mar
(83) |
Apr
(40) |
May
(68) |
Jun
(43) |
Jul
(38) |
Aug
(33) |
Sep
(88) |
Oct
(54) |
Nov
(53) |
Dec
(119) |
| 2016 |
Jan
(268) |
Feb
(42) |
Mar
(86) |
Apr
(73) |
May
(239) |
Jun
(93) |
Jul
(89) |
Aug
(60) |
Sep
(49) |
Oct
(66) |
Nov
(70) |
Dec
(34) |
| 2017 |
Jan
(81) |
Feb
(103) |
Mar
(161) |
Apr
(137) |
May
(230) |
Jun
(111) |
Jul
(135) |
Aug
(92) |
Sep
(118) |
Oct
(85) |
Nov
(110) |
Dec
(84) |
| 2018 |
Jan
(75) |
Feb
(59) |
Mar
(48) |
Apr
(50) |
May
(63) |
Jun
(44) |
Jul
(44) |
Aug
(61) |
Sep
(42) |
Oct
(108) |
Nov
(76) |
Dec
(48) |
| 2019 |
Jan
(38) |
Feb
(47) |
Mar
(18) |
Apr
(98) |
May
(47) |
Jun
(53) |
Jul
(48) |
Aug
(52) |
Sep
(33) |
Oct
(20) |
Nov
(30) |
Dec
(38) |
| 2020 |
Jan
(29) |
Feb
(49) |
Mar
(37) |
Apr
(87) |
May
(66) |
Jun
(98) |
Jul
(25) |
Aug
(49) |
Sep
(22) |
Oct
(124) |
Nov
(66) |
Dec
(26) |
| 2021 |
Jan
(131) |
Feb
(109) |
Mar
(71) |
Apr
(56) |
May
(29) |
Jun
(12) |
Jul
(36) |
Aug
(38) |
Sep
(54) |
Oct
(17) |
Nov
(38) |
Dec
(23) |
| 2022 |
Jan
(56) |
Feb
(56) |
Mar
(73) |
Apr
(25) |
May
(15) |
Jun
(22) |
Jul
(20) |
Aug
(36) |
Sep
(24) |
Oct
(21) |
Nov
(78) |
Dec
(42) |
| 2023 |
Jan
(47) |
Feb
(45) |
Mar
(31) |
Apr
(4) |
May
(15) |
Jun
(10) |
Jul
(37) |
Aug
(24) |
Sep
(21) |
Oct
(15) |
Nov
(15) |
Dec
(20) |
| 2024 |
Jan
(24) |
Feb
(37) |
Mar
(14) |
Apr
(23) |
May
(12) |
Jun
(1) |
Jul
(14) |
Aug
(34) |
Sep
(38) |
Oct
(13) |
Nov
(33) |
Dec
(14) |
| 2025 |
Jan
(15) |
Feb
(19) |
Mar
(28) |
Apr
(12) |
May
(23) |
Jun
(43) |
Jul
(32) |
Aug
(29) |
Sep
(11) |
Oct
(17) |
Nov
(66) |
Dec
(34) |
| 2026 |
Jan
(15) |
Feb
(2) |
Mar
(12) |
Apr
(9) |
May
(27) |
Jun
(34) |
Jul
(45) |
Aug
(34) |
Sep
(10) |
Oct
(18) |
Nov
(23) |
Dec
|
|
From: G.W. H. <ba...@ju...> - 2026-11-15 16:39:34
|
Hello again, On Sun, 15 Nov 2026, G.W. Haywood wrote: > ... > Do you have 'htop'? That should give us some useful information. > ... Sorry, 'atop' not 'htop'. -- 73, Ged. |
|
From: G.W. H. <ba...@ju...> - 2026-11-15 16:33:18
|
Hi Micah, On Sun, 15 Nov 2026, Micah Leier wrote: > Hey I am on x64, the fix you sent me worked. However I am noticing > that the newer version takes between 2 and 5 times as long for the > same job, I switched between them several times running fulls and > incrementals on a 4gb and 130gb backup and got the same results > consistently. There isn't a noticeable difference in CPU usage, > both stay between 5 and 15 percent (on an ancient Celeron G440). Curious that the CPU usage is similar, I suppose that means it's I/O that's taking the time - either mass storage or network traffic. Do you have 'htop'? That should give us some useful information. Also, please can you let me have the output of rsync_bpc-3.5.2.0 --bpc-top-dir='/var/lib/BackupPC/' --bpc-share-name='/' --bpc-host-name='dummy' --bpc-bkup-num=0 --version Note that, at the moment, version 3.2.5.0 requires the extra command line options even for the version command. I plan to fix that so it doesn't break e.g. systemd unit files but right now it's not on the critical path. -- 73, Ged. |
|
From: <Mat...@gm...> - 2026-11-15 15:38:32
|
Hello Ged, I've added the documentation patch in https://github.com/backuppc/backuppc/issues/565 Gemini wrote the patch, and I tested it. Hopefully you like it 😊️ Br Matthias Am Freitag, dem 06.11.2026 um 13:25 +0000 schrieb G.W. Haywood: > Hi there, > > Sorry Matthias, somehow this one was lost in this week's noise. > > On Wed, 4 Nov 2026, Matthias@... wrote: > > Am Montag, dem 02.11.2026 um 10:46 +0000 schrieb G.W. Haywood: > > > On Fri, 30 Oct 2026, Matthias@... wrote: > > > > > > > .. patch in https://github.com/backuppc/backuppc/issues/565 > > > > > > Thanks Matthias, your patch looks uncontroversial.? I've applied it > > > here, it will go into the next release. > > > > Nice to hear > > If I'd develop a patch to integrate it into the GUI configuration as > > well as documentation - would you include it too? > > For a newly developed feature I'm reluctant to make changes to the GUI > until there's some evidence that people will find it useful (and also, > that they find that it works as intended... :) > > If you produce some documentation patches for what you have already > done I should be very happy to apply them. Comments in the config.pl > file would be welcome too. |
|
From: Micah L. <nix...@gm...> - 2026-11-15 03:06:26
|
Hey I am on x64, the fix you sent me worked. However I am noticing that the newer version takes between 2 and 5 times as long for the same job, I switched between them several times running fulls and incrementals on a 4gb and 130gb backup and got the same results consistently. There isn't a noticeable difference in CPU usage, both stay between 5 and 15 percent (on an ancient Celeron G440). I ran enough tests to feel confident it isn't my (very slow, 5mbps upload) internet connection. On Thu, Nov 12, 2026 at 10:12 AM G.W. Haywood <ba...@ju...> wrote: > > Hi there, > > On Thu, 12 Nov 2026, Micah Leier wrote: > > > Hey I installed the rsync_bpc compiled from the tarball you sent me, > > instead of copying the new binary over the old or anything so drastic > > I just edited the rsync-bpc location in the config :) > > That's sensible. :) > > > First run got an error, thought it was possibly due to an older > > version (3.2.7) of rsync on the other end, upgraded to 3.5.1 and ran > > again, same error. Tried on another host, same error again. Reverting > > to legacy rsync_bpc everything is fine. > > That makes sense. ;) > > > I am running the last stable release of BackupPC still, I assume that > > shouldn't matter but I can update to the latest git if needed. > > Rsync-bpc isn't at all fussy about the version of BackupPC, and it is > only slightly fussy about the version of rsync on the client. > > > Attached log: > > > > XferLOG file /var/lib/backuppc/pc/nas-misc/XferLOG.113 created 2026-11-06 19:58:02 > > ... > > ... > > Old package separator used in string at /usr/share/backuppc/bin/BackupPC_backupDuplicate line 89. (Did you mean "$Host\'s" instead?) > > This is a benign message caused by a change in behaviour of the Perl > interpreter (around version 5.38). BackupPC version 4.4.1rc1 prepends > escapes to single-quotes in text strings; see Github commit b607ac0c. > > > ... > > Running: /usr/local/bin/rsync_bpc-3.5.2.0 --bpc-top-dir /var/lib/backuppc ... > > ... > > ... > > full backup started for directory /home/nixcamic > > ... > > ... > > *** buffer overflow detected ***: terminated > > Oh, that's a new one. Any sign of a core dump? Can you let me have > some details about the system? Architecture; distro; versions of the > kernel, glibc, gcc, and anything else you think might be useful. > > On x86_64 another tester came up with a segfault. After looking at > his core dump I sent a revised version of bpc_syscall.c for testing. > If it fixes his (different) error I'll let you have the revised file. > If you could get a core dump from your buffer overflow it might help > me to pin down the issue more quickly. > > -- > > 73, > Ged. > > > _______________________________________________ > BackupPC-users mailing list > Bac...@li... > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: https://github.com/backuppc/backuppc/wiki > Project: https://backuppc.github.io/backuppc/ |
|
From: G.W. H. <ba...@ju...> - 2026-11-12 16:11:02
|
Hi there, On Thu, 12 Nov 2026, Micah Leier wrote: > Hey I installed the rsync_bpc compiled from the tarball you sent me, > instead of copying the new binary over the old or anything so drastic > I just edited the rsync-bpc location in the config :) That's sensible. :) > First run got an error, thought it was possibly due to an older > version (3.2.7) of rsync on the other end, upgraded to 3.5.1 and ran > again, same error. Tried on another host, same error again. Reverting > to legacy rsync_bpc everything is fine. That makes sense. ;) > I am running the last stable release of BackupPC still, I assume that > shouldn't matter but I can update to the latest git if needed. Rsync-bpc isn't at all fussy about the version of BackupPC, and it is only slightly fussy about the version of rsync on the client. > Attached log: > > XferLOG file /var/lib/backuppc/pc/nas-misc/XferLOG.113 created 2026-11-06 19:58:02 > ... > ... > Old package separator used in string at /usr/share/backuppc/bin/BackupPC_backupDuplicate line 89. (Did you mean "$Host\'s" instead?) This is a benign message caused by a change in behaviour of the Perl interpreter (around version 5.38). BackupPC version 4.4.1rc1 prepends escapes to single-quotes in text strings; see Github commit b607ac0c. > ... > Running: /usr/local/bin/rsync_bpc-3.5.2.0 --bpc-top-dir /var/lib/backuppc ... > ... > ... > full backup started for directory /home/nixcamic > ... > ... > *** buffer overflow detected ***: terminated Oh, that's a new one. Any sign of a core dump? Can you let me have some details about the system? Architecture; distro; versions of the kernel, glibc, gcc, and anything else you think might be useful. On x86_64 another tester came up with a segfault. After looking at his core dump I sent a revised version of bpc_syscall.c for testing. If it fixes his (different) error I'll let you have the revised file. If you could get a core dump from your buffer overflow it might help me to pin down the issue more quickly. -- 73, Ged. |
|
From: Micah L. <nix...@gm...> - 2026-11-12 02:56:24
|
Hey I installed the rsync_bpc compiled from the tarball you sent me, instead of copying the new binary over the old or anything so drastic I just edited the rsync-bpc location in the config :) First run got an error, thought it was possibly due to an older version (3.2.7) of rsync on the other end, upgraded to 3.5.1 and ran again, same error. Tried on another host, same error again. Reverting to legacy rsync_bpc everything is fine. I am running the last stable release of BackupPC still, I assume that shouldn't matter but I can update to the latest git if needed. Attached log: XferLOG file /var/lib/backuppc/pc/nas-misc/XferLOG.113 created 2026-11-06 19:58:02 Backup prep: type = full, case = 3, inPlace = 1, doDuplicate = 1, newBkupNum = 113, newBkupIdx = 8, lastBkupNum = , lastBkupIdx = (FillCycle = 0, noFillCnt = 6) Executing /usr/share/backuppc/bin/BackupPC_backupDuplicate -m -h nas-misc Old package separator used in string at /usr/share/backuppc/bin/BackupPC_backupDuplicate line 89. (Did you mean "$Host\'s" instead?) Xfer PIDs are now 2405 Copying backup #112 to #113 Xfer PIDs are now 2405,2409 BackupPC_refCountUpdate: host nas-misc got 0 errors (took 2 secs) Xfer PIDs are now 2405 BackupPC_backupDuplicate: got 0 errors and 0 file open errors Finished BackupPC_backupDuplicate (running time: 5 sec) Running: /usr/local/bin/rsync_bpc-3.5.2.0 --bpc-top-dir /var/lib/backuppc --bpc-host-name nas-misc --bpc-share-name /home/nixcamic --bpc-bkup-num 113 --bpc-bkup-comp 0 --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 28760 --bpc-log-level 1 --bpc-attrib-new -e /usr/bin/ssh\ -l\ root --rsync-path=/usr/bin/rsync --super --recursive --protect-args --numeric-ids --perms --owner --group -D --times --links --hard-links --delete --delete-excluded --one-file-system --partial --log-format=log:\ %o\ %i\ %B\ %8U,%8G\ %9l\ %f%L --stats --checksum --timeout=72000 homenas:/home/nixcamic/ / full backup started for directory /home/nixcamic Xfer PIDs are now 2413 This is the rsync child about to exec /usr/local/bin/rsync_bpc-3.5.2.0 Xfer PIDs are now 2413,2423 xferPids 2413,2423 *** buffer overflow detected ***: terminated rsync_bpc: [receiver] write error: Broken pipe (32)\#012 Done: 0 errors, 0 filesExist, 0 sizeExist, 0 sizeExistComp, 0 filesTotal, 0 sizeTotal, 0 filesNew, 0 sizeNew, 0 sizeNewComp, 28761 inode rsync error: error in socket IO (code 10) at io.c(962) [receiver=3.5.2.0]\#012 rsync_bpc exited with fatal status 0 (134) (rsync error: error in socket IO (code 10) at io.c(962) [receiver=3.5.2.0]\#012) Xfer PIDs are now Got fatal error during xfer (rsync error: error in socket IO (code 10) at io.c(962) [receiver=3.5.2.0]\#012) Backup aborted (rsync error: error in socket IO (code 10) at io.c(962) [receiver=3.5.2.0]\#012) BackupFailCleanup: nFilesTotal = 0, type = full, BackupCase = 3, inPlace = 1, lastBkupNum = BackupFailCleanup: inPlace with no new files... no cleanup Running BackupPC_refCountUpdate -h nas-misc -f on nas-misc |
|
From: Bill F. <bi...@fa...> - 2026-11-09 01:04:11
|
Hi everyone, I've pushed an update to backuppc-find.sh (a CLI search wrapper around BackupPC_ls for BackupPC v4) with several performance and usability improvements: 1. Parallel Multi-Core Processing (-j / --jobs) Searches across hosts and historical backups now run concurrently across multiple CPU cores rather than sequentially. On multi-host searches, this cuts total execution time significantly (typically 2x–3x faster or more). By default, the script detects and utilizes all available CPU cores via nproc. Throttling CPU Load: On servers with dozens of hosts or large historical catalogs, running wide open across every core can spike CPU load. You can limit concurrency to keep server load in check using the -j (or --jobs / --max-cores) option: # Limit search to 2 cores sudo -u backuppc /usr/share/backuppc/bin/backuppc-find.sh -j 2 all "\.ods$" 2. Grouped Output by Host With parallel execution, standard terminal output would normally interleave lines from different hosts as they finish. Results are now buffered per host using a temporary scratch directory in /tmp, so output always prints in clean, contiguous host blocks. 3. Natural Regex End-of-Line Matching ($ Anchor)BackupPC_ls prints a trailing MD5 checksum at the end of each line, which previously required appending a trailing space to patterns (e.g., "\.sh ") to avoid matching false positives. The script now strips that trailing checksum before filtering, allowing you to use standard regex anchors like $ cleanly: # Example search for all *.sh (bash scripts) in a users home directory across all hosts sudo -u backuppc /usr/share/backuppc/bin/backuppc-find.sh all "/home/user/[^/]+\.sh$" The updated script and README are available on GitHub:https://github.com/wfahren/BackupPC_find_file Feedback and suggestions are welcome! Thanks, Bill On 11/8/26 6:54 AM, G.W. Haywood wrote: > Hi there, > > On Sat, 7 Nov 2026, kosowsky wrote: >> >> I find that 'backuppcfs.pl' (BackupPC FUSE filesystem) is INFINITELY >> more powerful and useful than BackuPC_ls or any other official tool >> for finding and reading files in BackupPC. >> >> I have long thought that this *simple* script should be added to the >> standard BackupPC distro as it is so incredibly powerful and useful. > > IIRC I already asked you a couple of times if you'd add it to the Wiki > but that doesn't seem to have happened. :( > >> ... >> ... @GEG - what do you think about adding it? > > Assuming you mean @GED, now that I'm beginning to see a way out of the > rsync-bpc woods it sounds like a reasonable idea. :) > > Looking at the history on the mailing list I've been a little concerned > that people who have tried to use it seem to have some trouble with it. > If we can get it to the stage where it will Just Work [TM] (most of the > time:) then I think it would make a very useful addition to the stable. > > See Gihub issue #543, which I've just re-opened. > |
|
From: G.W. H. <ba...@ju...> - 2026-11-08 13:55:09
|
Hi there, On Sat, 7 Nov 2026, kosowsky wrote: > > I find that 'backuppcfs.pl' (BackupPC FUSE filesystem) is INFINITELY > more powerful and useful than BackuPC_ls or any other official tool > for finding and reading files in BackupPC. > > I have long thought that this *simple* script should be added to the > standard BackupPC distro as it is so incredibly powerful and useful. IIRC I already asked you a couple of times if you'd add it to the Wiki but that doesn't seem to have happened. :( > ... > ... > @GEG - what do you think about adding it? Assuming you mean @GED, now that I'm beginning to see a way out of the rsync-bpc woods it sounds like a reasonable idea. :) Looking at the history on the mailing list I've been a little concerned that people who have tried to use it seem to have some trouble with it. If we can get it to the stage where it will Just Work [TM] (most of the time:) then I think it would make a very useful addition to the stable. See Gihub issue #543, which I've just re-opened. -- 73, Ged. |
|
From: <bac...@ko...> - 2026-11-07 23:31:28
|
I find that 'backuppcfs.pl' (BackupPC FUSE filesystem) is INFINITELY
more powerful and useful than BackuPC_ls or any other official tool
for finding and reading files in BackupPC.
I have long thought that this *simple* script should be added to the
standard BackupPC distro as it is so incredibly powerful and useful.
See below for what it does...
@GEG - what do you think about adding it?
It hasn't been updated in forever but it still seems to work
perfectly. There might be opportunities to improve caching efficiency
and speed (perhaps rewrite in 'C') as well as adding extended
attributes (ACLs and SELinux) to the extent that they are already
supported in BackupPC and rsync.
Presumably AI could be helpful here
Using the above script mounts ALL your BackupPC backups across all
hosts and backup numbers as FUSE filesystems. Backups can be accessed
as:
<mount point>/<host>/<backup_number>/<share>/<path-to-file>
OR
<mount point>/<host>/<backup-date-time>/<share>/<path-to-file>
With special links for:
<mount point>/<host>/oldest/<share>/<path-to-file>
<mount point>/<host>/latest/<share>/<path-to-file>
You can use all your favorite Gnu/Linux tools to list, find, grep,
read, word count, sed, etc your backup files.
Only limitation is that the mount is (obviously) read-only.
I always keep the BackupPC FUSE file system mounted which allows me to
easily browse, find, and retrieve individual old copies. In fact, it
is so useful that I essentilly never use tools like BackupPC_ls
anymore.
No extra computation is needed until you start accessing the backuppc
fuse file system but lookups are cached so that repeated access to a
directory tree gets faster after the first access.
Bill Fahrenkrug wrote at about 09:38:56 -0700 on Saturday, November 7, 2026:
> Thanks for the feedback!
>
> To clarify:the script actually uses |BackupPC_ls|under the hood!It’s
> designed as an automation wrapper around it.
>
> While |BackupPC_ls|works great for inspecting a specific
> snapshot,running it by hand has a few pain points when you don't know
> where or when a file lived:
>
> *
>
> *Scope:*|BackupPC_ls|requires you to specify a single host (|-h|)
> and a single backup run (|-n|).If you have 10 hosts with 30
> historical backups each,you would have to run it hundreds of times
> manually.
>
> *
>
> *Automation:*The wrapper queries |pc/<host>/backups|to automatically
> walk through all historical snapshots (|--all|),can sweep across all
> hosts at once (|all|),and prefixes matches with the host name and
> backup number so you immediately know where to restore from.
>
> I'll update the GitHub README to make that distinction much clearer.
>
> Adding it to the BackupPC Wiki is a great idea—I'll get a page/link
> added there so others running into the same issue can find it
> easily.Thanks for pointing me in that direction!
>
>
> On 11/7/26 7:06 AM, G.W. Haywood wrote:
> > Hi there,
> >
> > On Sat, 7 Nov 2026, Bill Fahrenkrug wrote:
> >
> >> I have been using BackupPC for 10+ years and have gone though many
> >> workstations. I don't restore all of my documents or other files to
> >> my new workstation, I normally want to start with a clean slate. But
> >> sometimes I need to find that one file I should have. Using the the
> >> web interface and clicking through all the different folders looking
> >> for a file was painful to say the least.
> >
> > Agreed the Web interface isn't great for doing this sort of thing. :/
> >
> >> I searched the list many times and didn't find a good solution.
> >
> > Doesn't the BackupPC_ls script help with what you need to do?
> >
> >> So I created a bash script to find files using regex pattern and
> >> thought I would share.
> >>
> >> It's on Git Hub. the README includes how to install and some examples.
> >>
> >> https://github.com/wfahren/BackupPC_find_file
> >
> > It might be useful to contrast your script with BAckupPC_ls, and maybe
> > put your script in the BackupPC Wiki:
> >
> > https://github.com/backuppc/backuppc/wiki
> >
> > That's probably the best place to collect itches that need a scratch.
> >
> _______________________________________________
> BackupPC-users mailing list
> Bac...@li...
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: https://github.com/backuppc/backuppc/wiki
> Project: https://backuppc.github.io/backuppc/
|
|
From: Bill F. <bi...@fa...> - 2026-11-07 17:06:34
|
Thanks for the feedback!
To clarify:the script actually uses |BackupPC_ls|under the hood!It’s
designed as an automation wrapper around it.
While |BackupPC_ls|works great for inspecting a specific
snapshot,running it by hand has a few pain points when you don't know
where or when a file lived:
*
*Scope:*|BackupPC_ls|requires you to specify a single host (|-h|)
and a single backup run (|-n|).If you have 10 hosts with 30
historical backups each,you would have to run it hundreds of times
manually.
*
*Automation:*The wrapper queries |pc/<host>/backups|to automatically
walk through all historical snapshots (|--all|),can sweep across all
hosts at once (|all|),and prefixes matches with the host name and
backup number so you immediately know where to restore from.
I'll update the GitHub README to make that distinction much clearer.
Adding it to the BackupPC Wiki is a great idea—I'll get a page/link
added there so others running into the same issue can find it
easily.Thanks for pointing me in that direction!
On 11/7/26 7:06 AM, G.W. Haywood wrote:
> Hi there,
>
> On Sat, 7 Nov 2026, Bill Fahrenkrug wrote:
>
>> I have been using BackupPC for 10+ years and have gone though many
>> workstations. I don't restore all of my documents or other files to
>> my new workstation, I normally want to start with a clean slate. But
>> sometimes I need to find that one file I should have. Using the the
>> web interface and clicking through all the different folders looking
>> for a file was painful to say the least.
>
> Agreed the Web interface isn't great for doing this sort of thing. :/
>
>> I searched the list many times and didn't find a good solution.
>
> Doesn't the BackupPC_ls script help with what you need to do?
>
>> So I created a bash script to find files using regex pattern and
>> thought I would share.
>>
>> It's on Git Hub. the README includes how to install and some examples.
>>
>> https://github.com/wfahren/BackupPC_find_file
>
> It might be useful to contrast your script with BAckupPC_ls, and maybe
> put your script in the BackupPC Wiki:
>
> https://github.com/backuppc/backuppc/wiki
>
> That's probably the best place to collect itches that need a scratch.
> |
|
From: Bill F. <bi...@fa...> - 2026-11-07 16:57:27
|
On 11/7/26 7:06 AM, G.W. Haywood wrote: > Hi there, > > On Sat, 7 Nov 2026, Bill Fahrenkrug wrote: > >> I have been using BackupPC for 10+ years and have gone though many >> workstations. I don't restore all of my documents or other files to >> my new workstation, I normally want to start with a clean slate. But >> sometimes I need to find that one file I should have. Using the the >> web interface and clicking through all the different folders looking >> for a file was painful to say the least. > > Agreed the Web interface isn't great for doing this sort of thing. :/ > >> I searched the list many times and didn't find a good solution. > > Doesn't the BackupPC_ls script help with what you need to do? > >> So I created a bash script to find files using regex pattern and >> thought I would share. >> >> It's on Git Hub. the README includes how to install and some examples. >> >> https://github.com/wfahren/BackupPC_find_file > > It might be useful to contrast your script with BAckupPC_ls, and maybe I updated the README to "A lightweight Bash wrapper around BackupPC_ls for BackupPC v4" to make it clear it's just a wrapper of BackupPC_ls > put your script in the BackupPC Wiki: > > https://github.com/backuppc/backuppc/wiki > > That's probably the best place to collect itches that need a scratch. > I added the repository link it to the wiki under the "Extensions and Scripts" section |
|
From: G.W. H. <ba...@ju...> - 2026-11-07 14:06:24
|
Hi there, On Sat, 7 Nov 2026, Bill Fahrenkrug wrote: > I have been using BackupPC for 10+ years and have gone though many > workstations. I don't restore all of my documents or other files to my > new workstation, I normally want to start with a clean slate. But > sometimes I need to find that one file I should have. Using the the web > interface and clicking through all the different folders looking for a > file was painful to say the least. Agreed the Web interface isn't great for doing this sort of thing. :/ > I searched the list many times and didn't find a good solution. Doesn't the BackupPC_ls script help with what you need to do? > So I created a bash script to find files using regex pattern and > thought I would share. > > It's on Git Hub. the README includes how to install and some examples. > > https://github.com/wfahren/BackupPC_find_file It might be useful to contrast your script with BAckupPC_ls, and maybe put your script in the BackupPC Wiki: https://github.com/backuppc/backuppc/wiki That's probably the best place to collect itches that need a scratch. -- 73, Ged. |
|
From: Bill F. <bi...@fa...> - 2026-11-07 03:36:38
|
I have been using BackupPC for 10+ years and have gone though many workstations. I don't restore all of my documents or other files to my new workstation, I normally want to start with a clean slate. But sometimes I need to find that one file I should have. Using the the web interface and clicking through all the different folders looking for a file was painful to say the least. Pool is 1304.07GiB comprising 740434 files and 16512 directories I searched the list many times and didn't find a good solution. So I created a bash script to find files using regex pattern and thought I would share. It's on Git Hub. the README includes how to install and some examples. https://github.com/wfahren/BackupPC_find_file Bill |
|
From: G.W. H. <ba...@ju...> - 2026-11-06 14:00:43
|
Hi there, Please would anyone wishing to help with testing of the latest version of rsync-bpc (version 3.5.2.0) please get in touch with me? Apart from adding the 'make dist' target missing from the rsync code it's as near to ready for release as I can make it without some more help in testing. Yes, I know I said that it would be version 3.5.0.0 but things seem to be moving very fast in this world of AI-assisted vulnerability chasing. -- 73, Ged. |
|
From: G.W. H. <ba...@ju...> - 2026-11-06 13:40:26
|
Hi there, This probably wouldn't rate a mention on this list except for the fact that there seems to be quite a few people using BackupPC under Docker, and AFAICT most of the Docker images use lightweight versions of Linux such as Alpine Linux. A serious vulnerability in the implementation of openssh with the musl library (as opposed to the glibc library), together with certain setup configurations, results in it being trivial to log in remotely without valid credentials. At the moment there seems to be some debate about who takes the blame for this one but that really isn't important. As always, my advice is don't open any BackupPC server to the Internet but if you do currently have a BackupPC server that allows access from the Internet to port 22, then please ensure that it is not vulnerable. The same applies to any other box really. Routers are obvious targets as they often run Alpine Linux or a similar lightweight Linux distro. As yet I don't know of a CVE, there's a writeup on Ars Technica here: https://arstechnica.com/security/2026/11/vulnerability-allows-attackers-to-log-into-some-linux-devices-sans-password/ -- 73, Ged. |
|
From: G.W. H. <ba...@ju...> - 2026-11-06 13:25:22
|
Hi there, Sorry Matthias, somehow this one was lost in this week's noise. On Wed, 4 Nov 2026, Matthias@... wrote: > Am Montag, dem 02.11.2026 um 10:46 +0000 schrieb G.W. Haywood: > > On Fri, 30 Oct 2026, Matthias@... wrote: > > > > > .. patch in https://github.com/backuppc/backuppc/issues/565 > > > > Thanks Matthias, your patch looks uncontroversial.? I've applied it > > here, it will go into the next release. > > Nice to hear > If I'd develop a patch to integrate it into the GUI configuration as > well as documentation - would you include it too? For a newly developed feature I'm reluctant to make changes to the GUI until there's some evidence that people will find it useful (and also, that they find that it works as intended... :) If you produce some documentation patches for what you have already done I should be very happy to apply them. Comments in the config.pl file would be welcome too. -- 73, Ged. |
|
From: G.W. H. <ba...@ju...> - 2026-11-04 13:37:24
|
Hi there,
On Wed, 4 Nov 2026, Matthias@... wrote:
> ...
> --super is required in $Conf{RsyncArgs}
> ...
Yes, and AFAICT it is present in a default Debian installation.
So did you break it? ;)
--
73,
Ged.
|
|
From: <Mat...@gm...> - 2026-11-04 08:36:15
|
Hello
--super is required in $Conf{RsyncArgs}
After adding it, the uid/gid will be stored in the attrib files again💃️🕺🏿
best regards
Matthias
Am Dienstag, dem 03.11.2026 um 19:49 +0100 schrieb Mat...@gm...:
> Hello again ;)
>
> I'm using Debian Trixie with:
> root@fileserver:~# dpkg --list | grep backuppc
> ii backuppc 4.4.0-11 amd64
> high-performance, enterprise-grade system for backing up PCs
> ii backuppc-rsync 3.1.3.0-4 amd64
> patched rsync for BackupPC version 4
> ii libbackuppc-xs-perl:amd64 0.62-2+b5 amd64
> Perl module with C backend for BackupPC 4
>
> The Backup 4724 has been done with Debian Bullseye and the Backup 4779 is done with Debian Trixie.
>
>
> $Conf{RsyncArgs} = [
> '--numeric-ids',
> '--protect-args',
> '--perms',
> '--acls',
> '--xattrs',
> '--owner',
> '--group',
> '--times',
> '-D',
> '--links',
> '--hard-links',
> '--recursive',
> '--partial',
> '--one-file-system',
> '--timeout=21600',
> '--contimeout=300',
> '--stats',
> '--ignore-errors',
> '--force',
> '--sparse'
> ];
>
> root@fileserver:~# sudo -u backuppc /usr/share/backuppc/bin/BackupPC_attribPrint
> /var/lib/backuppc/pc/athlux/4724/fhome/fBackup4U/attrib* | grep -B12 "remoteAccess.sh' ="
> 'compress' => 0,
> 'digest' => '',
> 'gid' => 1004,
> 'inode' => 13980926,
> 'mode' => 16832,
> 'mtime' => 1744873687,
> 'name' => '.config',
> 'nlinks' => 0,
> 'size' => 4096,
> 'type' => 5,
> 'uid' => 1004
> },
> 'remoteAccess.sh' => {
>
> root@fileserver:~# sudo -u backuppc /usr/share/backuppc/bin/BackupPC_attribPrint
> /var/lib/backuppc/pc/athlux/4779/fhome/fBackup4U/attrib* | grep -B12 "remoteAccess.sh' ="
> 'compress' => 0,
> 'digest' => '',
> 'gid' => 0,
> 'inode' => 19064670,
> 'mode' => 448,
> 'mtime' => 1744873687,
> 'name' => '.config',
> 'nlinks' => 0,
> 'size' => 0,
> 'type' => 5,
> 'uid' => 0
> },
> 'remoteAccess.sh' => {
>
> best regard
> Matthias
>
> Am Dienstag, dem 03.11.2026 um 13:05 +0000 schrieb G.W. Haywood:
> > Hi there,
> >
> > On Tue, 3 Nov 2026, Matthias@... wrote:
> > >
> > > I need a restore these days and recognized that all restored files are owned by root:root.
> > > As far as I could analyze in the atrib-files, since my upgrade from debian bullseye to
> > > bookworm
> > > and
> > > trixie the backups don't backup the owner information anymore.
> > >
> > > Does anyone know's something about?
> >
> > After reading your mail I recovered a directory from another user's
> > desktop machine to both a zip file and a tar file. I checked the UIDs
> > and GIDs in both files and they were as expected for the user. Then I
> > looked directly at the attrib files in the pool, and they were also as
> > I expected them to be. I have not attempted to restore files directly
> > in place - I feel that's tempting fate a little too much, especially
> > if the reason that you're recovering from a backup is because you've
> > already had one accident.
> >
> > However, I am using the 'upstream' versions of BackupPC and rsync_bpc
> > and not something from a distribution. Also my testing was of just a
> > few random files in one directory, I haven't for example written any
> > code to inspect the entire pool although that would be easy enough.
> >
> > Please can you give the exact versions of the BackupPC distribution's
> > software involved, and also please describe exactly how you recovered
> > the files? I have Debian Bullseye, Bookworm and Trixie installations
> > here, so it shouldn't be too difficult for me to reproduce your issue
> > if there's enough information.
|
|
From: <Mat...@gm...> - 2026-11-03 19:09:51
|
Hello, Nice to hear 🤗 If I'd develop a patch to integrate it into the GUI configuration as well as documentation - would you include it too? best regards Matthias Am Montag, dem 02.11.2026 um 10:46 +0000 schrieb G.W. Haywood: > Hi there, > > On Fri, 30 Oct 2026, Matthias@... wrote: > > > .. patch in https://github.com/backuppc/backuppc/issues/565 > > Thanks Matthias, your patch looks uncontroversial. I've applied it > here, it will go into the next release. |
|
From: <Mat...@gm...> - 2026-11-03 18:49:44
|
Hello again ;)
I'm using Debian Trixie with:
root@fileserver:~# dpkg --list | grep backuppc
ii backuppc 4.4.0-11 amd64
high-performance, enterprise-grade system for backing up PCs
ii backuppc-rsync 3.1.3.0-4 amd64
patched rsync for BackupPC version 4
ii libbackuppc-xs-perl:amd64 0.62-2+b5 amd64
Perl module with C backend for BackupPC 4
The Backup 4724 has been done with Debian Bullseye and the Backup 4779 is done with Debian Trixie.
$Conf{RsyncArgs} = [
'--numeric-ids',
'--protect-args',
'--perms',
'--acls',
'--xattrs',
'--owner',
'--group',
'--times',
'-D',
'--links',
'--hard-links',
'--recursive',
'--partial',
'--one-file-system',
'--timeout=21600',
'--contimeout=300',
'--stats',
'--ignore-errors',
'--force',
'--sparse'
];
root@fileserver:~# sudo -u backuppc /usr/share/backuppc/bin/BackupPC_attribPrint
/var/lib/backuppc/pc/athlux/4724/fhome/fBackup4U/attrib* | grep -B12 "remoteAccess.sh' ="
'compress' => 0,
'digest' => '',
'gid' => 1004,
'inode' => 13980926,
'mode' => 16832,
'mtime' => 1744873687,
'name' => '.config',
'nlinks' => 0,
'size' => 4096,
'type' => 5,
'uid' => 1004
},
'remoteAccess.sh' => {
root@fileserver:~# sudo -u backuppc /usr/share/backuppc/bin/BackupPC_attribPrint
/var/lib/backuppc/pc/athlux/4779/fhome/fBackup4U/attrib* | grep -B12 "remoteAccess.sh' ="
'compress' => 0,
'digest' => '',
'gid' => 0,
'inode' => 19064670,
'mode' => 448,
'mtime' => 1744873687,
'name' => '.config',
'nlinks' => 0,
'size' => 0,
'type' => 5,
'uid' => 0
},
'remoteAccess.sh' => {
best regard
Matthias
Am Dienstag, dem 03.11.2026 um 13:05 +0000 schrieb G.W. Haywood:
> Hi there,
>
> On Tue, 3 Nov 2026, Matthias@... wrote:
> >
> > I need a restore these days and recognized that all restored files are owned by root:root.
> > As far as I could analyze in the atrib-files, since my upgrade from debian bullseye to bookworm
> > and
> > trixie the backups don't backup the owner information anymore.
> >
> > Does anyone know's something about?
>
> After reading your mail I recovered a directory from another user's
> desktop machine to both a zip file and a tar file. I checked the UIDs
> and GIDs in both files and they were as expected for the user. Then I
> looked directly at the attrib files in the pool, and they were also as
> I expected them to be. I have not attempted to restore files directly
> in place - I feel that's tempting fate a little too much, especially
> if the reason that you're recovering from a backup is because you've
> already had one accident.
>
> However, I am using the 'upstream' versions of BackupPC and rsync_bpc
> and not something from a distribution. Also my testing was of just a
> few random files in one directory, I haven't for example written any
> code to inspect the entire pool although that would be easy enough.
>
> Please can you give the exact versions of the BackupPC distribution's
> software involved, and also please describe exactly how you recovered
> the files? I have Debian Bullseye, Bookworm and Trixie installations
> here, so it shouldn't be too difficult for me to reproduce your issue
> if there's enough information.
|
|
From: G.W. H. <ba...@ju...> - 2026-11-03 13:06:09
|
Hi there, On Tue, 3 Nov 2026, Matthias@... wrote: > > I need a restore these days and recognized that all restored files are owned by root:root. > As far as I could analyze in the atrib-files, since my upgrade from debian bullseye to bookworm and > trixie the backups don't backup the owner information anymore. > > Does anyone know's something about? After reading your mail I recovered a directory from another user's desktop machine to both a zip file and a tar file. I checked the UIDs and GIDs in both files and they were as expected for the user. Then I looked directly at the attrib files in the pool, and they were also as I expected them to be. I have not attempted to restore files directly in place - I feel that's tempting fate a little too much, especially if the reason that you're recovering from a backup is because you've already had one accident. However, I am using the 'upstream' versions of BackupPC and rsync_bpc and not something from a distribution. Also my testing was of just a few random files in one directory, I haven't for example written any code to inspect the entire pool although that would be easy enough. Please can you give the exact versions of the BackupPC distribution's software involved, and also please describe exactly how you recovered the files? I have Debian Bullseye, Bookworm and Trixie installations here, so it shouldn't be too difficult for me to reproduce your issue if there's enough information. -- 73, Ged. |
|
From: <Mat...@gm...> - 2026-11-03 03:23:10
|
Hello, I need a restore these days and recognized that all restored files are owned by root:root. As far as I could analyze in the atrib-files, since my upgrade from debian bullseye to bookworm and trixie the backups don't backup the owner information anymore. Does anyone know's something about? Thanks in advance Matthias |
|
From: G.W. H. <ba...@ju...> - 2026-11-02 10:47:03
|
Hi there, On Fri, 30 Oct 2026, Matthias@... wrote: > .. patch in https://github.com/backuppc/backuppc/issues/565 Thanks Matthias, your patch looks uncontroversial. I've applied it here, it will go into the next release. -- 73, Ged. |
|
From: <Mat...@gm...> - 2026-10-30 16:28:34
|
Hello Ged, I just provided the patch in https://github.com/backuppc/backuppc/issues/565 Br Matthias Am Donnerstag, dem 11.06.2026 um 17:12 +0200 schrieb Mat...@gm...: > Hello Ged, > > "required" - I'm a german. I imagine my english could be improved🤣️ > > I'll develop and test the patch with $Conf{patch-defined-command} without impementation in GUI and > send it here in the mailing list. > > Have a great day > Matthias > > > Am Donnerstag, dem 11.06.2026 um 15:20 +0100 schrieb G.W. Haywood: > > Hi there, > > > > On Wed, 10 Jun 2026, Matthias@gmx... wrote: > > > > > In BackupPC V4, if a new backup is started, we begin with BackupPC_backupDuplicate of the last > > > recent backup number into the new backup number and DumpPreUserCmd will be called afterwards. > > > This > > > can have a duration from some seconds till some hours. If the client go to sleep during this > > > time, > > > the backup will fail. > > > I developed a patch to move the call of DumpPreUserCmd before execution of > > > BackupPC_backupDuplicate > > > to allow a users DumpPreUserCmd to disable hibernation on client side. > > > > > > You said it required to use a $Conf{patch-defined-command}. > > > > 'Require' is perhaps a stronger word than I would have used, but OK, > > what I said is effectively the same thing. :) > > > > > I can easily implement it in my config.pl and in the BackupPC_dump patch. Would this be > > > sufficient > > > to apply it in a master branch? > > > > Yes. The idea is that if people want to try it out they can, but if > > they don't then they also don't need to worry about it and IMPORTANTLY > > they also don't need to backport any fixes to existing configurations. > > > > > Or would you expect to put it also in the web UI? > > > > No, I much prefer *not* to change the UI. That's asking for trouble. > > > > > I've done this in 2014 with another patch in BackupPC 3.1. It was a > > > lot of work and testing ?? > > > > I'm sure it was. As far as possible I want to leave the Web UI alone: > > > > 1. There are in any case already things in the configuration that the > > Web UI cannot change. > > > > 2. As it is, the UI code is a nightmare. Adding complexity will give > > more things more opportunities to go wrogn. > > > > 3. To improve security, the lowest hanging fruit by a long way is the > > Web server. BackupPC works just fine without one. (But you may need > > to dust off that text editor manual. Read the bit about old versions > > being saved with an incrementing suffix. If that isn't an option for > > your editor, you can always install Emacs. :) > > |
|
From: G.W. H. <ba...@ju...> - 2026-10-30 12:57:59
|
Hi there,
On Fri, 30 Oct 2026, Matthias@... wrote:
> I got an error with BackupPC_nightly in Debian Trixie:
> sudo -u backuppc /usr/share/backuppc/bin/BackupPC_nightly -h
> Attempt to call undefined import method with arguments (":BPC_DT_ALL") via package "BackupPC::Lib"
> ...
> ...
https://sourceforge.net/p/backuppc/mailman/message/58851406/
--
73,
Ged.
|