BackupPC-4.4.0-9.el9.x86_64
I see now this is a bigger problem than I thought initially.
I thought that each backup # was a restore point to the
state of the share at the time of that backup but instead it
is an accumulation of all backups w/o reflecting any of the
deletions of files now non existent on the source machine. I
had never browsed the backups to see if they were what I
expected for one to one state of the current source. I've
always used the default rsync args and now I think I need to
modify them but I guess I'm really nave as to how backuppc
is working.
Some historical background. I've been using BackupPC for at
least 15 years and migrated my backups from version 3. to
version 4 a year and a half ago when I installed Rocky8 but
I'm now running Rocky9 on the server. My logs, error and
otherwise are not showing any backup issues.
Here are a few lines from a recent backup of one of my
machines xferlogs to illustrate the current rsync arguments
in use. The full list of includes/excludes has been
truncated. Note that the pasted lines don't wrap, at least
not for me in my email client.
#############
XferLOG file /var/lib/BackupPC//pc/xjbk7/XferLOG.64.z created 2023-07-25
15:45:31
Backup prep: type = full, case = 3, inPlace = 1, doDuplicate = 1, newBkupNum =
64, newBkupIdx = 3, lastBkupNum = , lastBkupIdx = (FillCycle = 0, noFillCnt =
0)
Executing /usr/share/BackupPC/bin/BackupPC_backupDuplicate -m -h xjbk7
Xfer PIDs are now 540945
Copying backup #63 to #64
Xfer PIDs are now 540946,540945
BackupPC_refCountUpdate: host xjbk7 got 0 errors (took 2 secs)
Xfer PIDs are now 540945
BackupPC_backupDuplicate: got 0 errors and 0 file open errors
Finished BackupPC_backupDuplicate (running time: 7 sec)
Running: /usr/bin/rsync_bpc --bpc-top-dir /var/lib/BackupPC/ --bpc-host-name
xjbk7 --bpc-share-name / --bpc-bkup-num 64 --bpc-bkup-comp 3 --bpc-bkup-prevnum
-1 --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 121320 --bpc-log-level 1
--bpc-attrib-new -e /usr/bin/ssh\ -l\ backuppc\ \ --rsync-path=/usr/bin/sudo\
/usr/bin/rsync --numeric-ids --perms --owner --group -D --links --hard-links
--times --block-size=2048 --recursive --one-file-system --checksum
--timeout=72000 --include=/boot
#############
I'm wondering if I need to add a "delete" argument to the
rsync line but am not sure of the consequences.
What I want is that for say backup #32 that a restore of
that backup would be just the current state of the files on
that machine at the time of backup and backup #31 would be a
reflection of the share state at the time of that prior backup.
jbk
On 7/26/23 20:36, jbk wrote:
On one of my machine shares I did some file consolidation
that involved creating a new top level directory and
moving files from adjacent top level directories into sub
directories under the newly created directory I then
deleted those other empty top level directories.
Backuppc ran a couple days later a incremental backup, and
in this backup there was the new directory with sub
directories and files I had moved as well as the old and
no longer existing top level directories and files. I
waited till the next nightly ran and then checked again
and the deleted directories and files were still present.
So I haven't lost data but if I had a disk failure the
restore would recreate deleted data on the new destination
share. So the question is how do I delete old share data
structures in my backups or how should I approach such
changes so I don't end up with over populated restores.
--
Jim KR
--
Jim KR
_______________________________________________
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/
