Hello @Mike_Agsteribbe,
Thank you for the detailed explanation — I can see why this behavior was unexpected, so let me clarify what’s happening and how to get things back on track.
How Roon stores settings and metadata
Roon settings, metadata, and library information are stored inside the database on the Roon Server, and that database is associated with a specific Roon account. When you restore a backup, you’re restoring the entire server identity as it existed at the time of that backup — not just metadata.
Because of this, after a restore:
- The server may present itself with the same identity and name as the old server
- Roon Remotes may appear to “reconnect” to what looks like the old server, even though it’s now running on new hardware
Important question to confirm
After restoring the backup, are you logging in with the exact same Roon account that was used on the original Rhein Z1Plus?
If a different account is used, Roon will treat the restored server as a new, unlicensed server, which explains why it appears as a trial.
About the Mac server you’re seeing
The Roon Server instance on your Mac does not affect the Antipodes server in any way. It’s completely independent and can simply be stopped or ignored — it will not interfere with licensing or server selection on your network.
What to try next
- Fully power off the old server (Rhein Z1Plus), if it is still present anywhere on the network
- Launch Roon and make sure you are logged in using the same Roon account that owns the subscription
- When prompted to select a server, choose the Antipodes S40
- If you see an “Unauthorize” option, use it — this will free the license and allow it to attach to the correct server
Once logged in with the correct account, the restored server should correctly attach to your existing subscription.