Hi.
I’m good with the RESTIC echo system in normal use case.
But I’m looking for a feature or option that
checking file contents between server and client(by hash or whatever one),
not by date and time.
Because I have Database SQL daily backup files(not data),
no contents differnce between yesterday and today, but file always replaces
which means the same contents file have different createtime and modification time.
How to get over the situation not to back up if that have same file and contents but date.time stamp?
should I raise feature request?
If a file has a modified timestamp it will be backed up. However, only modified blocks will be uploaded to the repository. This means that if file content has NOT been updated, only metadata well be uploaded.
Erm, you mean. if the file has exactly same text contents in it as before, but totally rewritten(delete + write or overwrite whatever) file but very large few gigabyte.
no real data exachanges but only snapshot remain?
what I need is ignoring any snapshot history in the case to manage the real changes.
Still not support it right?
Do you know that how to raise the issue and request feature?
there’s a --skip-if-unchanged flag for backup (Backing up — restic 0.19.1 documentation), that doesn’t create a snapshot if the files have not changed.
You could combine this with --ignore-ctime and/or --ignore-mtime (Backing up — restic 0.19.1 documentation) to ignore changed file metadata.
That said, if the file is actually being deleted and recreated, the inode number will have changed, so I think a new snapshot will still be created, because, well, it is a new file. Maybe give it a test in your actual environment, and then report back?