Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[MrBloke]

I'm trying to back up my DNS-345 (main NAS) to my DNS-320 (backup NAS) over my LAN and am having problems regardless of the direction of the backup.

When I try to push the backup (local to remote) from the 345 to the 320, the backup stops after about 100G of the 400G that needs to be backed up.  Also the incremental backup option isn't offered.  The status line says that the backup has completed but no other information is offered.

When trying to pull the backup from the 345 to the 320 (remote to local) I get as far as the Remote Settings dialog which allows me to select the remote path. After doing this I'm simply told "RSYNC Test Failed.", with no information as to why it failed.  I can't get any further than this.

One the advice of another post, I've shortened the password to 6 characters but to no effect.

There is no usable log information that I can find (is there anything other than the most basic log anywhere on these?).

I am at the end of my tether here.  After a month of trying to get USB backups to work (and failing) NAS to NAS backups won't work ether.  If anyone has any ideas on how to get this working, I would be very, very grateful.

Thanks,

Mark

[ivan]

Very strange, we do what you are trying to do on a nightly basis without problems - full replace backup every Saturday with every day incremental backups.

I would suspect your network in the first instance and, if you have the boxes connected through a router, the router settings.  We have moved all our clients over to using Gigabit switches on their internal networks rather than routers because of the simplicity of the setup - OK, we use managed switches on our internal network for our own convenience.

How are your boxes connected to your network, cat6 cable or something else?  If there is a wireless leg in there somewhere that can cause problems if it is not setup correctly.  If you have a switch or can borrow one you can try connecting the NAS boxes to it rather than the router and then connect the router to it as well to allow you access to the NAS web interface.

[MrBloke]

Both NAS boxes are connected to a TP-Link gigabit switch.  The switch is then connected to the router (some Technicolour thing).  The Mac that I'm using to access the web interface is connected to the router using ethernet.  All connections are via cat6, the router does provide a wireless network but it's not in play between the NAS boxes & the Mac.

I can pull files between the NAS boxes with no problem via the Mac and can get several steps into the RSYNC backup wizard before I get the error message.

Maybe I'll try a full power down reset of everything over the weekend.

Very frustrating!

[ivan]

What you describe should work without problems.

One point that might have a bearing, if you haven't already set it up this way, is to give each NAS a fixed IP address.  I do have to say it should work with DHCP addresses but if you have short lease times set that may account for the backup stopping - lease renewal drops the IP address and picks it up again but the transfer stops.

[MrBloke]

Already running with fixed IP addresses!  Problem is happening during the setup wizard rather than the backup execution (never managed to get as far as the execution).

For the time being, I've managed to get local backups working over the LAN which is achieving the same effect.  I'm putting Rsync to bed now as it's given me a headache.

Thanks for your help,
Mark