so yesterday i just wanted to validate that a important backup is working and i found a weird type of problem on one of our nodes. Eventually it is on more nodes but i found it on one specific.
For example within the /opt directory are a file and some dirs. In every snapshot the file is included, but only in every second/third snapshot the dirs and their content is included.
The backups where the /opt directory is fully included are just 1.1-1.2 GB of size, while the backups where it isnt is up to 6 GB (5.6-5.8). However, this is independent of the snapshot tags.
Kopia doesnt report any issues, everything succeeds.
Can you elaborate a bit more on your setup? Are you using a central Kopia server or just a shared repository? Do your nodes use different hostnames so that you can distinct them in the repo?
Sorry for that - yeah we use a central kopia server - each server has a different hostname and we just have a global policy with some file/dir excludes (in general we just save important folders like /opt, /home, /srv etc.) and just one of hundred nodes which has a per-user policy. So yeah, we can distinct each node in the repo by node and user.
The Policy:
Retention:
Annual snapshots: 5 (defined for this target)
Monthly snapshots: 12 (defined for this target)
Weekly snapshots: 8 (defined for this target)
Daily snapshots: 14 (defined for this target)
Hourly snapshots: 24 (defined for this target)
Latest snapshots: 10 (defined for this target)
Ignore identical snapshots: false (defined for this target)
Files policy:
Ignore cache directories: true (defined for this target)
Ignore rules: (defined for this target)
proc/
sys/
dev/
run/
tmp/
var/run/
var/lock/
var/run
var/lock
var/log/
var/backups/
var/lib/
var/local/
var/opt/
var/tmp/
var/cache/
var/spool/
mnt/
media/
lost+found/
swap/
boot/
bin
bin/
sbin
sbin/
initrd.img
initrd.img.old
lib/
lib64/
lib
lib64
vmlinuz
vmlinuz.old
usr/
Read ignore rules from files: (defined for this target)
.kopiaignore
Scan one filesystem only: false (defined for this target)
Error handling policy:
Ignore file read errors: false (defined for this target)
Ignore directory read errors: false (defined for this target)
Ignore unknown types: true (defined for this target)
Scheduling policy:
Scheduled snapshots:
None.
Manual snapshot: false (defined for this target)
Uploads:
Max parallel snapshots (server/UI): 5 (defined for this target)
Max parallel file reads: 16 (defined for this target)
Parallel upload above size: 2.1 GB (defined for this target)
Compression:
Compressor: zstd (defined for this target)
Compress all files except the following extensions: (defined for this target)
.7z
.bz2
.gif
.gz
.iso
.jpeg
.jpg
.mkv
.mp3
.mp4
.ogg
.png
.tar
.xz
.zip
Compress files of all sizes.
Metadata compression:
Compressor: zstd-fastest (defined for this target)
Splitter:
Algorithm override: (repository default) (defined for this target)
No actions defined.
OS-level snapshot support:
Volume Shadow Copy: never (defined for this target)
Logging details (0-none, 10-maximum):
Directory snapshotted: 5 (defined for this target)
Directory ignored: 5 (defined for this target)
Entry snapshotted: 0 (defined for this target)
Entry ignored: 5 (defined for this target)
Entry cache hit: 0 (defined for this target)
Entry cache miss: 0 (defined for this target)
How many snapshots do you have in your repo? I am seeing, that you chose to not ignore identical snapshots. I once had an issue when the number of snapshots exceeded 25k or so. However, in my case Kopia server would actually fail, so there was a clear and visible issue, which then got resolved a couple of months later.
So you are saying, that you look at the snapshots and one shows only files and no directories while on other snapshots both, files ans directories are shown?