rsync backup not working

[Mechano]

I've the same problem with a commercial web hosting that gives me SSH access.
I can rsync by shell but I can't create a job from the interface.

The only way is to insert a line into crontab after exchange ssh keys.

After key creation (use root user) with the command:

Code: Select all

ssh-keygen -t rsa

The key exchange CANNOT be done with

Code: Select all

ssh-copy-id user@host

because that command is missing so you have to use the form:

Code: Select all

cat ~/.ssh/id_rsa.pub | ssh user@host "cat >> ~/.ssh/authorized_keys"

After that you can automate your command using crontab -e and adding the line:

Code: Select all

m h dom mon dow rsync -az -e ssh user@host:/remote/folder /local/folder

change m h dom mon dow for your needing.

You don't need to launch crontab command and restart the cron daemon like other NAS operating systems, the entry has immediate effect.

I had same problem with my previous QNAP TS-212P, but into that nas's interface there wasn't the option for SSH authentication for rsync.
Into my AS-202TE there's the option but it's broken I've the error "Connection timeout ref. 5608".

[katla]

NAS ---> rsync comp server
rsync backup job over ssh is not working.
It ignores "Use encrypted transmission" and uses the rsync port 873.
Is there a fix?

After having spent more than 2000 USD on two AS-602T with a total of four 4TB disks - solely for the purpose of being able to backup locally and then Rsync this to a remote site for my business - I see that I perhaps should have consulted this forum before I did such a silly thing.

It works great if the two NAS-boxes are on the same LAN but when they are on different LANs it does not work.

* I can SSH from the office box to the remote box - so the firewall is open and there should be no problem doing that.
* I have even opened the firewall to allow RSYNC without SSH (port 873) but that does not work either.
* I can rsync from my MAC to the office when I am using it locally but when I use it from remote I get connection refused.

I can of course do the same thing using two linux servers and that was also my initial idea. However - having a simple userinterface like the ADM interface seemed a lot easier than spending time going through setting up two linux installations with mirroring and then setting up all the necessary security settings and making crontab jobs - something an experienced Linux user probably would be able to do and I am not exactly a very experienced Linux user.

That is a pity because my initial experience with these NAS boxes were great - the user interface made it simple to set up and user interface also was responsive.

Great is Asustor could acknowledge this problem and tell us when we can expect this to be fixed. Especially since this has been a problem since at least july 2013 and so far seem to have not been adressed.