Connect Core and Scale and share users and data

I have had a large TrueNas Core installation for years. Mainly film and media ~4-10 people / 10G interfaces client/switch/server.

Super stable since FreeNas - we love ZFS and we love snapshots

But now I repeatedly have things that would be easier or better to solve with TrueNas Scale and a Linux base. (Docker, various Linux software …) But I don’t want to migrate because operational security is the top priority.

The idea now is to connect a second smaller server via 10G and run Scale there and mount files and users from TruenasCore.

Now for the question: How :wink:
Is there a TrueNas way?
Or is it NFS/NIS or iSCSI?
I don’t need step-by-step instructions, rather tried and tested ideas and concepts.

Grateful for any hints and ideas.

There really isn’t a way to do this, at least as I understand the question. If your CORE system is pulling users from Active Directory, the SCALE system could be joined to the same AD domain and then would have the same users.

But what would you want to be doing on the SCALE system? If it’s “running apps that use storage on the CORE system,” the apps are able to connect to a SMB share (which would presumably be on the CORE system). If you want to share out the same set of files from each, there really isn’t a way to do that.

My core system is alone in the network. All users are local users on the core system.
The scale system should be able to use all files on the core (SMB/NFS).
However, I would also like to have the users of the core system on the scale system - but not create a copy of them on the scale.

Otherwise I will have a problem with rights and passwords if I have two user databases.

As an example of my current configuration:
A Nextcloud jail is running on the core - all users can log in here, as the authentication with the SMB module works via the local Truenas users.

As I said. I am open to ideas.
The second server should actually only provide services. All data and users should still only be provided by the core system.

The correct way to do this is to join both servers to AD. You can’t make one truenas server the identity provider for another.

:sob: Thank you for the clear - although sad - solution