restore appears to be making borg reindex everything each backup

[cthulhubuddha]

I have a borg backup repo server that mounts folders to backup from other servers in the folder /mnt/. I rebuilt an openmediavault file server and then restored all borg backed up folders back to it. the file server's root is /srv/ and has folders like Music, etc. When I restored, say Music to the new file server they restored in /srv//Music/mnt/Music. I then performed a borg backup with the existing repo. Originally the files were in just /srv //Music, but the new files were in /srv//Music/mnt/Music. I realized after the backups we created what had happened and manually moved all folders from /srv//Music/mnt/Music to /srv//Music/ on the file server. Now every backup looks like it is performing a full backup instead of just deltas.

Question 1: How can you restore from backups that use the mount path to a relative folder name so it doesn't nest the backup folder on the backup server /mnt/Music in the fileserver's target folder?

Question 2: Is it going to be easier just to create a whole new set of Repos to get borg back to just backing up deltas?

Thanks all!

[ThomasWaldmann]

If you rebuilt the whole server from nothing, you likely lost the borg cache and also the local chunks index, so borg needs to rebuild caches / index.

Also, if you move directory trees inside the backup source around, you will cause misses even if you already had a files cache.
It's no problem, it will rebuild the files cache, but the first backup will not be able to quickly skip unchanged files, but will chunk them and then notice that already all chunks are present in the repo. Just let it run, next backup time it will be fast again.

A1: borg always restores to current directory, see the docs. so adjust cwd as needed and it will match. there are also "strip" options for borg create and/or extract if you like that better.

A2: that doesn't matter and won't fix the files-cache-miss-problem you caused by moving around stuff.

[cthulhubuddha]

perfect, thx!