mountpoint missing after restoring a backup

[Christoph.Caina]

Hi,
today I've tried to restore a backup from one of my CT's.
After the backup was restored, I've noticed that the application could not access to its storage as I would have expected.
The storage was a folder on a ZFS volume - and after checking the container's config file, I just noticed that the mountpoint which I had configured was missing.

Here's the configuration:

arch: amd64
cores: 4
features: nesting=1
hostname: emby-server
memory: 15259
mp0: /volume2/media/,mp=/volume2/media
nameserver: 192.168.52.251
...

After addint the mp0 manually, everything was working again, but I wonder why this parameter was missing after restore.
at the moment, I am just concerned, that none of my backups (of several containers) would restore their mountpoints - at least, when they have been added manually to the containers configuration file... ?!

Does anyone know why this might be the case and how I could prevent this from happening again?

thanks!

 

[fabian]

check the restore log - bind mounts are not restored when restoring as unprivileged user (they require root privileges to be added in the first place, so the same applies on restore as well). if the bind mount entry was part of the backed-up config, the restore task log should contain a warning referencing this fact.