We got a server to act as a LIVE backup to our main TrueNAS Core server. I've been through the documentation multiple times and because we need it to be a live server, i.e. able to take over for the actual server if failure happens. Because, according to the documentation, a replication task sets it up as read only because it's a snapshot being sent to the new server, I decided to setup a rsync task to copy it over. The first time I ran it, it worked, but of course it built all of the sub-datasets under the new server as sub-folders, not data sets. Then I meticulously rebuilt all of the data sets under the new servers with the same authorities as the existing data sets on the old server. Now it fails with a "failed: Operation not permitted (1)" for every file sent. I thought maybe it was the Delay Updates flag, but after unchecking the option and re-running the sync, it failed with the same errors.
This brings up another problem I'm having with active directory authorities. Both servers are attached to our active directory domain. The old server's datasets are owned by an active directory user and group. When running rsync with preserve permissions, it created the sub-folders within the target data sets, but it's still owned by root and the group doesn't match the active directory group. The rid mapping for both systems are identical but the uids don't match across systems.
I fought with it all day yesterday, and it's frustrating that something that should be relatively easy is so frustratingly complex. Can anyone point me in the correct direction or give me some advice on how I can do this and keep the new server in sync with old?
This brings up another problem I'm having with active directory authorities. Both servers are attached to our active directory domain. The old server's datasets are owned by an active directory user and group. When running rsync with preserve permissions, it created the sub-folders within the target data sets, but it's still owned by root and the group doesn't match the active directory group. The rid mapping for both systems are identical but the uids don't match across systems.
I fought with it all day yesterday, and it's frustrating that something that should be relatively easy is so frustratingly complex. Can anyone point me in the correct direction or give me some advice on how I can do this and keep the new server in sync with old?