SOLVED Replication task creation error

[awil95]

I am attempting to create a replication task between two systems. Both are running TrueNAS-SCALE-22.12.0 and were built on a clean install not an upgrade. During the creation of my replication task, I try to select the folder I want to replicate to on the destination system and then the source system does this weird loading process and just gets stuck on a loading screen. See attached pictures for reference. Has anyone encountered this issue before or have any ideas on how to remedy it?

EDIT: For anyone with this same issue in the future, the SOLUTION to the problem is in post #8.

 

[morganL]

Can you confirm whether you are replicating to a folder or a dataset?

 

[awil95]

Can you confirm whether you are replicating to a folder or a dataset?

I am attempting to replicate a dataset from system "A" to system "B". The UI lets me make all of my appropriate selections on the source location, and it will let me select the destination as "on a different system" and it will let me select the appropriate "ssh connection". The issue I have is when i click the folder drop down for the destination system. The UI just says "Waiting for active TrueNAS controller to come up" and then it just fails to do anything.

It did do the auto creation of ssh credentials between the two systems just fine. It only gives me the error when I click the folder drop down for the destination system.

 

[morganL]

Are there multiple datsets on the destination system already? ( a screenshot of dataset structure might help).
Have you tried typing in a path manually?

/scale/scaletutorials/dataprotection/replication/

 

[awil95]

Are there multiple datsets on the destination system already? ( a screenshot of dataset structure might help).
Have you tried typing in a path manually?

/scale/scaletutorials/dataprotection/replication/

The destination system (Atlas) does not have a copy of the source dataset that I am looking to replicate, the dataset called Wilson. I manually entered the destination path and the task was able to save; however, when I run the task I keep getting Authentication (publickey) failed errors. Which is really interesting because the source system was able to create the ssh connection using the automated process. I am using non-root user accounts to create the ssh connection, but this shouldn't be an issue with the new system update to SCALE that allows non-root admin accounts correct?

I have followed the TrueNAS documentation and even watched Lawrence Systems tutorials on replication from youtube and I cannot get this replication task to work between these two systems. I'm really hoping I can get it figured out because rsync just takes way to long to complete frequent updates with this much data.

 

[morganL]

The destination system (Atlas) does not have a copy of the source dataset that I am looking to replicate, the dataset called Wilson. I manually entered the destination path and the task was able to save; however, when I run the task I keep getting Authentication (publickey) failed errors. Which is really interesting because the source system was able to create the ssh connection using the automated process. I am using non-root user accounts to create the ssh connection, but this shouldn't be an issue with the new system update to SCALE that allows non-root admin accounts correct?

I have followed the TrueNAS documentation and even watched Lawrence Systems tutorials on replication from youtube and I cannot get this replication task to work between these two systems. I'm really hoping I can get it figured out because rsync just takes way to long to complete frequent updates with this much data.

There are a couple of replication bugs/issues related to non-root users that will be fixed in 22.12.1 ... later in Feb.

Going back to root, might be a workaround.

 

[awil95]

There are a couple of replication bugs/issues related to non-root users that will be fixed in 22.12.1 ... later in Feb.

Going back to root, might be a workaround.

Ah that would make sense. I will try re-enabling the root user on both systems tonight and attempt to do the auto-setup for replication and see how it goes. I will report back with my findings.

Thanks for your help!

 

[awil95]

There are a couple of replication bugs/issues related to non-root users that will be fixed in 22.12.1 ... later in Feb.

Going back to root, might be a workaround.

MorganL, thank you for pointing out the bug with using non-root user accounts. This was 100% why I could not create a replication task. I re-enabled the root user account on both systems and I was able to complete the replication auto-setup between the two systems with no issues.