Trying to Hyper Backup to distant QNAP

Currently reading
Trying to Hyper Backup to distant QNAP

Hi All,

I'm trying to get the Synology to backup to a remote QNAP (over the net). I know this works - as I had it working for over a year - but my mate's device messed up and he needed to re-build it. Since then, I have been unable to get the damned things working again. Does anyone have experience/knowledge of how to achieve this please? I realise I "might" need to ask in a QNAP forum, but thought I'd try here first.

Scenario: Multiple Hyper Backup jobs still configured to back up to the remote QNAP (i.e. I haven't changed these jobs since his issues. And these used to work).

The jobs are configured as:
  • 'rsync' jobs to 'rsync-compatible-server'
  • Transfer Encryption is on (so over ssh)
  • The port however is custom and mapped/forwarded from his router to 22 on the QNAP.
I know the ssh port fwding works as I also have straight-up public-key access rsync jobs running via Task Scheduler on the Synology to the QNAP across the mapped port.

Given, nothing has changed my end, I expect there to be no config. issues - as this all used to work. That means there needs to be some config on the QNAP.

So, it seems logical to me that the people to ask will be the Synology people as they are more likely to remember what QNAP config needed to happen to facilitate the Syno Hyper Backup.

Any ideas please.........?
 
Cheers Rusty.

The Syno HB job logs - for what good they are - seem to think the "backup destination does not exist." Which of course means they're not getting a response.

So, as you say, that could mean:
  • No rsync server running QNAP end - checked thanks to Syno Task Sched. jobs
  • Port mapping misconfig - as above
  • User/Pass issue - IF it is this, I would expect the HB logs to register that, rather than destination does not exist.
For QNAP config:

Screen Shot 2021-07-22 at 08.15.48.png


You can't change 873 to 22 - it doesn't like it.
For user/pass, I've tried a generic 'rsync' user, my specific backup user (is an Admin on the QNAP), and the in-built QNAP admin account - no joy.

This article from QNAP themselves shows the way (albeit with some QES O.S. as opposed to QTS O.S. which is what this specific QNAP has), but still no luck.

How to perform the rsync from Synology NAS to QNAP NAS with QES system
 
Upvote 0
So if consider that you destination "admin" account is valid (password and all), and you do have 873 open on the destination side, then I guess it all comes down to your source configuration.

You do have your task configured to use the encrypted traffic on that 873 port? Also, does this happen with a new task as well or just the current one that you already had running?

QNAP has configured again as you posted initially, so are you sure your friend configured all correctly on his/her end?

Have you tried resetting a password on the QNAP side?
 
Upvote 0
Last edited:
I would look to test the connection from the NAS’s LAN using a command line utility: could be NAS using SSH or Mac Terminal etc. You’re likely to get better feedback.
Not sure I follow @fredbert.

Which NAS, which LAN, mine or his? Which direction? NAS > out? Or firewall/router > in?

I know mine is all good. Nothing has changed my end. It has to be something to do with the QNAP config. Of course, I can't be sure he hasn't changed his firewall, but am reasonably certain.

As mentioned, the following cmd from Task Sched. in the Syno works and gets through successfully.

Bash:
rsync -rlptD -e 'ssh -p <mapped_port>' --delete --exclude="@eaDir" --exclude="#recycle" --exclude=".TemporaryItems" --exclude=".DS_Store" /volume1/MailPlus/ <my_backup_usr>@<his_host>.dyndns.org:/share/<backup_dir>/MailPlus

I think it might be time to hit up the QNAP forums.

Thanks
-- post merged: --

So if consider that you destination "admin" account is valid (password and all), and you do have 873 open on the destination side, then I guess it all comes down to your source configuration.

You do have your task configured to use the encrypted traffic on that 873 port? Also, does this happen with a new task as well or just the current one that you already had running?

QNAP has configured again as you posted initially, so are you sure your friend configured all correctly on his/her end?

Have you tried resetting a password on the QNAP side?

Thanks @Rusty,

I know the passwd is good - I can login to UI with it. Likewise <my_backup_usr> can login to UI with passwd.

873 (as I'm sure you know) is the std rsync port. This is on the QNAP inside his LAN - not exposed.
<mapped_port> in my above post is mapped in his FW through to ssh server (22) on the QNAP.
Syno HB jobs have 'transfer encryption' ON and using <mapped_port>.

And this is it. I know something has to change on the QNAP. I just have to figure out what.

Thanks the soundboard. Time to hit the QNAP forums.
 
Upvote 0
Not sure I follow @fredbert.

Which NAS, which LAN, mine or his? Which direction? NAS > out? Or firewall/router > in?
NAS = Synology NAS / your NAS ; QNAP NAS = QNAP NAS.

Though TBH what I was suggesting was: test rsync works outside of HB, whether that's on your NAS using SSH or a suitable client device connected to the same LAN as your NAS. Also, test the connectivity using the same parameters as you would in the HB task.

And don't assume anything: Just because one thing changed it may not be that thing that is causing the problem. Work through the whole flow of communications. So just confirm what you assume to be true is true, as it's probably a quick test and you'll have a definitive answer.


BTW that QNAP port 873 is not exposed isn't much protection as it's mapped to a very well-known port (22) and one that will be at the top of any hacker list. You'd probably be slightly more protected using 873 on the Internet as it'll take a few more milliseconds to get to it in the script.
 
Upvote 0
BTW that QNAP port 873 is not exposed isn't much protection as it's mapped to a very well-known port (22) and one that will be at the top of any hacker list. You'd probably be slightly more protected using 873 on the Internet as it'll take a few more milliseconds to get to it in the script.

Yeah. Should've been more clear. <mapped_port> is neither 873, nor 22. Neither are exposed directly in his FW. Only 22 via <mapped_port> with access locked to whitelisted IP's.


Let's try a different tack.

Can anyone tell me please how Hyper Backup stores its config on disk? i.e. Does it store job definitions in a shell script file? Does it create cron jobs? Checking those might actually offer a little more insight.
 
Upvote 0

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

  • Question
Thanks, I deleted all users, deleted "homes", set up "homes" first and then users and the permissions were...
Replies
6
Views
2,126
that is a good question...i do not remember :) maybe when i was experimenting 2-3 years ago i assigned...
Replies
9
Views
520
  • Question
I thought and did the same. I did fresh run and created new backup job...Ongoing...
Replies
7
Views
823
  • Question
HB/HBV updates are tied to the underlying DSM and may not be available unless your DSM is current. For...
Replies
3
Views
938
The documentation in that DSM 7 article is dated. It has evolved over time. There are still issued with...
Replies
1
Views
755
  • Question
I was trying 'entire system' backup now I'm trying again. 1 reinstalled hb on 1621 and hb vault on 1515...
Replies
2
Views
1,235

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top