Was testing setting up the backup and restore jobs for my nas.
TS-253D connect to the TL-D400S (this nas uses QTS to access the TL box and HBS app to perform backup and restores)
For connectivity, the TL is connected to 253D via SFF. And the 253D is connected to switch via 2.5gbe And the TS-877 will hopefully be connected to the switch via 10g (though the bottleneck will be 2.5g for the obvious reasons)
TS-877 (this will be the main nas and will be using truenas scale)
Note: before getting started, it’s best if you add all the nas devices in the hbs storage spaces, so when you are creating your sync back/restore jobs, you can then easily select them from the list of servers you added earlier.
So how this works is,
In HBS under SYNC, setup an active sync job
What this does is, pull the data from the TS-877 to the TL-D400S. Whereas before, i had a regular one way sync. But after making these changes, we have to do it this way instead. Either way it achieves the goal, backing up from TS-877 (truenas) to the TL-D400S.
Because i had yet to switch to truenas, for placeholder i had to use the RTRR option for the TS-877 (RTRR is a option only available to QTS/quts hero OS only as native solution. Supposedly it’s superior to rsync). Later after changing to truenas, you need to change it to RSYNC. This are the settings to set for truenas rsync to work with QNAP (i’ve tested this before and it was working with this setting)
Note: i disabled restore jobs to prevent any accidental restores which would overwrite valid data. I use that with caution and only enable it when needed. Rest of the time it’s disabled for safety precautions. I also disabled backup jobs though normally i don’t do that, simply because i have yet to transition the main nas to truenas, and i already did my backup already. So i will wait till that is all done, before i re-enable the backup job (which is an active sync)
I know what you are thinking. All this bending over backwards just to setup the backup and restore just to get that to work. Agreed, but it is what it is, we make do with what we have and mcgyver a solution that works 
The alternative to doing this, would be having 2 nas both setup as truenas, then using the truenas rsync module. Much simpler.
This guy elaborates how that works
Anyway point here is, now we have the backup and restore setup, making the transition to truenas for the ts-877 that much easier.
I strongly recommend before using any sort of backup or recovery solution you test it thoroughly to properly understand how that works (use an unimportant small data sample in a source/destination you can delete later when you are done testing), before deploying it to production. I did, so i am confident in my settings
TIPS: when backing up/restoring, it’s probably best to disable ssl encryption. This only applies to lan since you are doing this from the safety of your own private network. If however you are doing this remotely over the internet, be sure to enable it definitely. But the reason why for lan we disable, is because it slows down transfer speed performance. Don’t use when not needed.
Another thing that may impact performance is the enable checksum verification in HBS. This slows down performance a lot. If you uncheck this option, it does basic level checksum comparison (file name and file date i think? don’t quote me on that). It’s much faster. that said i don’t mind the wait time so i left it enabled. But you can disable that setting if you prefer. I just thought i’d mention this because it affects performance a lot when doing backup/restoring
)
don’t really want to spend more if i can help it, but the show must go on and this seems to be as good as it gets at this price point for a decent enough gpu that is on the compatibility list.
