Dj0k3
October 3, 2018, 5:49am
4
Check out these other topics to see if you can find some answers there.
I’m migrating from Crashplan, and I like the continuous backup feature. Crashplan used inotify to monitor for file changes and every 15 minutes backed up the modified files.
What are the implications if I run a backup every 15 minutes?
It will create around 100 snapshots per day - is this a problem?
Files have to be scanned every run. It’s a bit of a waste - is there a better solution?
If I hack my own solution (for example by getting a list of modified files with inotify) can I merg…
This is a bit of information I think others might find useful, and might spark a bit of discussion.
I noticed that Restic 0.9.1 was using the disk a lot when it was running backups. I posted about this on another thread, asking why restic didn’t just check the modified date, to be told it did. I could see a lot of disk access when a backup ran on my PC, so I dug into it.
This was the key graphic that helped me work out what was going on.
[restic3]
As you can see “avguard.exe” was scanning e…
This is an architectural limitation restic currently has: some of the exclude functions (e.g. --one-file-system) need to have the information lstat returns, and so we’re currently running lstat on the files before checking the excludes. The solution would be to have two types of excludes:
The ones which can decide by name/path if a file is to be excluded
The ones which need the lstat information (e.g. --one-file-system)
Until this is implemented, restic runs lstat() on all files. Sorry about …
Edit:
1 Like