On 11/2/21 7:54 AM, G.W. Haywood via BackupPC-users wrote:
Hi there,
Hi G.W.! Thanks for responding.
FWIW I wouldn't use NFS for anything that even vaguely bears a passing
resemblance to a backup system. In my experience NFS is always flaky.
Even if you do get it more or less under control, there always seem to
be gotchas lurking in there.
Namely?
I use NFS for a lot of things. And apart from an abysmal security model
(that can fortunately be hardened with a lot of extra work), I've had no
complaints.
One of the things to watch out for is indirection, where processes are
using some configured value. This is particularly true when the value
is a filesystem path. That might be helpful and it might not, in this
case, I throw it in because at this stage I can't immediately think of
anything else _concrete_ that might be relevant to your issue. You've
done enough already, however, to give anybody, er, pause for thought.
Indirection of configuration variables? I'm not so sure that's an issue
with my config, but how would I know?
My gut feeling is no, your backups will not be lost - unless you do
something rash. But given that
(1) you seem to think that your backups are important to you and
(2) you've been messing about wantonly with the architecture and
(3) it appears that this is your only backup then
what you have done so far seems to me a bit on the rash side.
How do you mean?
Anything that MIGHT have involved writing or modification of data would
have involved the running of: BackupPC_fixupBackupSummary,
BackupPC_fsck, BackupPC_migrateV3toV4, BackupPC_nightly, or
BackupPC_refCountUpdate, which in some cases I ran manually but in
others, the system has been just left on overnight.
There have been no rm's, mv's, or other form of data modification.
So I would like to think that point (2) you make is inaccurate and would
hope that in doing so my backups are indeed safe.
However, as I've tried to look back at particular backup #s that used to
have backups (or at least give me the error about missing files), it
seems that for certain machines, the entire backup process has
restarted, numbering from 0, with more inaccessible backups. It seems to
be turning into quite a mess and it seems the cleanup system is
spiraling out of control and deleting all my files. Joy.
I have attached a PNG of the current rrdtool graph of the 4-week Pool
Size, which might give you an idea of what is happening. I have a
feeling it will be rejected by the mailing list but I am CC:'ing you
directly.
I am open to paying for one-on-one assistance with this. I would very
much like to salvage this situation, if at all possible.
Well I probably should't pass up an offer like that, but first things
first: what version(s) of BackupPC are we talking about?
My apologies, I usually provide this information. This is BackupPC 4.4.0.
Again, this is the Docker container (adferrand/backuppc), which it turns
out, requires a few Perl modules, which I discovered were not installed
by default, once I attempted to run a few of the utility programs
manually. They are now installed but I will need to fork and modify the
Dockerfile in order for them to stick around.
- acc
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
