I’ve got a doozy here and need a sanity check to confirm the best way of doing this. I spun up a new Scale unit as a VM in ESXI with all NVME drives and passing through a controller card, very much by the book except it’s a VM.
I have replicated some vital datasets from my original machine 10.1.0.90 to the new VM machine at 10.1.0.143 and the transfer from old to new was flawless no issue with that.
The issue or question comes in this, I have added files to the new machine at 10.1.0.143 and it’s now lost sync with 10.1.0.90 and I need to fix that.
While the original data was moved to the new machine using a replication task, what’s the best way to sync both of these datasets so that the old non-VM unit is in sync with the new?
Scale said that the snapshots on 143 don’t match what’s on .90 and advised that the only way to do this would be to wipe out everything on .90 and start over which isn’t an option.
So the question, how can I get the current data which is on .143 to catch up the data on .90 so it’s backed up with the latest file data.
Did you look at Rsync in the Documents section? Is that what you wanted?
You didn’t specify what the two Scale servers do. Is one just a backup of the other? Are they both actively used for services?
I was thinking RSync as that’s what I used many moons ago when I migrated away from Synology to Scale. The .90 machine was the daily driver and was replicated to .91 which has since been taken out of service.
The .143 machine is the new daily driver and needs to be backed to .90 every few days when I power it up (main goal was to not have 2 DL380 HPE machines on all the time).
So .143 gets new files daily, scans, spreadsheets etc., .90 when it goes online will need to pull the data as incremental backups from .143 to get it back in sync as the backup.
What I wasn’t sure of was using a replication task between the 2 machines but the task failed with the following message as soon as it tried to run -
Replication “puppy-guppy/media,puppy-guppy/media/docs - littleguy/master_media/docs” failed: No incremental base on dataset ‘puppy-guppy/media’ and replication from scratch is not allowed…
Replication is probably what you want in this instance and is recommended for TrueNAS to TrueNAS. I think you do get stuck with a do over since you are changing the direction.
You should get some feedback from others but with the Thanksgiving holiday in US, it may take a few days?
