News:

Buffalo provides Data Recovery services. Read about it here.

Main Menu

backup

Started by anonymons, April 23, 2009, 04:24:45 PM

Previous topic - Next topic

anonymons

   

ok i'll try this again. Not trying to do anything evil. Just backing up files.

 

I have

TS-HTGL/R5 F/W 1.33 at the office.
I have 
TS-HTGL/R5 F/W 1.33 at the house.
 
I have a gateway to gateway vpn tunnel (pptp) linking the two.
 
Sometimes I get this error:
 rsync: writefd_unbuffered failed to write 4 bytes [sender]: Connection reset by peer (104)
rsync: connection unexpectedly closed (4452 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]
-------- END BACKUP 2009/04/22 18:28:01 array1/clientfiles -> BACKUP@array1/clientfiles --------
 
Wondering if anyone has seen this before and has any advice thats all.
 
 

 


Dustrega

Ah, I was under the impression you were running a 3rd party firmware on the NAS themselves. Usually, the ports that would need to be open over a VPN for NAS to NAS backup would be TCP 22939 for discovery, TCP 873 for unencrypted transfer, and TCP 8873 for encrypted. Hope this helps you a lot :)

anonymons

   

I can 'see' the terastation at my house from the office and I can start the backup jobs, it just fails sometimes. Do you think maybe if I manually open/forward the ports you suggest it will make the backup more consistant?

 


Dustrega

That would be my best guess. It's possible the routers are trying to communicate to each other through UPnP  (i.e. the NAS devices communicate to the routers on their own ports and the routers to each other through UPnP) but the limitation of UPnP is one connection only is allowed so perhaps the communication of the two devices "discovering" each other isn't allowing the routers enough downtime to establish a connection on an alternate port before clearing the next one. Long story short I would recommend manual port forwarding in this case just because there are multiple communications being used by the NAS devices.

Dustrega

Alright so that theory is completely shot after a night of research. It's possbile there could be a bad cable in the mix (i.e. ethernet). Also, is there any wireless involved?

anonymons

   

No wireless involved. Well there is a wireless repeater thing but it is on a seprate subnet/vlan than the terastation.

I could swap the wires, just using the one that came with the nas box.


anonymons

   

Cable, hmmm I think i remember the small piece of plastic broken off of the cable. I'll look tonight.

Thing is that the other back up jobs finish, only this one fails and it just happens to be the one with the most stuff to transfer.


Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 218 (show)
Files included: 35 - 1354KB. (show)
Memory used: 998KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]