That did it.
Could have sworn I'd tried that ... evidently not!
(in my little head /cygdrive implied a full cygwin install)
Thanks,
Kent
On Thu, Oct 22, 2020 at 7:31 PM Michael Huntley wrote:
> Try /cygdrive/c/users/ktenny
>
> Cheers!
>
> On Oct 22, 2020, at 4:47 PM, Kent Tenney wrote:
>
>
I am building a new backuppc server to replace a aging one that someone else
setup. The old one is 3.31 and i am using the latest 4.4.0. I have it making
backups but they seem extremely small since many of the backups are around a
terabyte in size. I noticed this as i was comparing a smaller
This is normal. In 4.x just an attrib file captures all the information
about which files are in that directory, with all their metadata (size,
modes, links, xattrs etc). As you note, the file is actually empty and all
that matters is the md5 digest in its name. That refers to the actual
attribut
Wow thats a relief, i thought it wasn't working without seeing any errors. By
the way my issues with rsync_bpc are solved, it all seems to be working now.
Thank you for your help.
Ok so that brings up another question. We have a synology boxes that we use to
take offsite. In the past we did a
Hi Craig,
Every time people ask about referencing file contents or their
attribs, I can't help but think how the backuppc-fuse is such an
underutilized asset.
That utility makes it so easy and natural to browse backups using
built-in file system commands -- whether via CLI or GUI.
As a wish-list,
Ghislain,
This looks like a bug. It seems that $Conf{DumpPostUserCmd} is run before
the backups file is re-written with the new backup information. Before that
there is just a placeholder for the new backup.
You could see if you can fix it by moving the $Conf{UserCmdCheckStatus} run
in bin/Backu
