As the subject says.
Asking more out of curiosity than anything - I don't actually plan to attempt such an upgrade. I'm still running OMV5 on Debian Buster and it's been performing admirably. I don't feel the need to upgrade yet, but once I do, I will start fresh with a clean install of OMV7 and reconfigure everything to my needs.
Also, it's nice to see the forums are alive and well after a few years of me not hanging around here, and so is OMV. 
Generally I'd agree with you - I do use Docker containers for a few other things, but find Emby well-behaved enough to not interfere with other things the host is doing. If that ever changed, I would definitely containerize it.
On a side note, I have a habit of installing an OS once and never again (even Windows on my PCs). I spend too much time tweaking and customizing things to ever want to do it again from scratch; that's what disk image backups are for, IMHO.
I run Emby directly (no Docker)... it just works, and I've never had to manually set it up for autostart at boot time.
I guess where I'm coming from, the question is "why bother with Docker, running Emby at host level is so ridiculously easy to run and manage," but maybe I'm missing something. 
One thing you could do is place a specific file - even a zero-byte file with a specific name - on your hard disk. Set up Syncback to check for the existence of that file and start the backup only when it's found.
Since the file wouldn't appear in your Samba shared folder if the disk is disconnected (as it's not on the SD card), that would stop Syncback from running the backup.
Gut gemacht. Genau das versuchte das System Dir mit config/service/smb/shares/share mitzuteilen.
Try different ports in OMV - something like, say, 18000 for http and 19000 for https. Then forward these ports through the router, but keep the same ports on the local and public side, avoiding 8080 and 8443 altogether.
I think that's what gderf was getting at as well.
...and what error, pray tell, are you getting?
We're not mind readers.
Device or resource busy - something else has a lock on the disk.
You could start a secure wipe, then abort it after a few seconds. For good measure, you might also disconnect the drive after that wipe, wait a moment, then reconnect it.
And did you set a range of ports in your FTP settings for passive connections? These will also need to be forwarded through your router. For example, something like 11500 to 11600.
After that many updates, I would strongly suggest you reboot your system immediately, if you haven't already. Then you can continue to try and get docker working.
LUKS is a Linux standard encryption scheme and not dependent on OMV. So yes, it will work in OMV 6.
Where can I enable this option? I'm not seeing it in OMV under FTP settings. Thanks!
It's on the Advanced page of the FTP settings.
Yes, and I think so. Try it and see. It won’t hurt anything.
Are you sure Agricola ? I have changed multiple settings before applying them before with no issues.
As for moving between sections before applying - I'm not 100% sure but I think any settings made to a section are lost when going to another section (and will show as having reverted when you go back).
It may be that the disk you're having issues with needs a filesystem check, i.e. e2fsck /dev/sdxy where x = the drive letter and y = the partition (usually 1).
As for Emby, is it running alongside OMV or as a Docker container? I use Emby myself and might be able to help with the cache clearing issue.
Or get a phone that's supported by Lineage OS and either add microG or skip the Google services framework altogether. There are plenty of ways.
I don't think you'll need a VPN solution, since rsync connects to remote servers through an SSH tunnel. By simply forwarding your Macbook's SSH port to the public Internet (use a custom port other than 22), then creating a private/public key pair and disabling password-based logins, you should have a straightforward way of running remote backups while maintaining appropriate security.
You may find some of these useful...
Enable the option 'No session reuse required.' That should fix your issue.
Sounds like a Postfix issue; also it looks like Postfix has its own resolv.conf file... I googled and found this thread which may point you in the right direction (hopefully).
