News:

RAID is not a replacement for a backup! Here's why.

Main Menu

TeraStation LIVE to/from TeraStation Pro Backups

Started by sierra2469alpha, September 19, 2008, 05:17:53 AM

Previous topic - Next topic

sierra2469alpha

   

There seems to be much in the press that these products cannot use the inbuilt backup over a private network, VPN, or over a direct public IP address, or a DDNS.

 

Can anybody confirm that they have these devices working in such a manner?

 

Thanks in advance, Sierra!!!!


Matt_M

You can back these devices up to one another over a WAN, there's a couple tricks to it though. Namely you have to make sure the RSync ports are open on both networks, also within the configuration pages of the devices you'll need to add the WAN IP to the terrastation list by hand. Other than that though you shouldn't have any problem with WAN backups.

boatlog

   

 

Which ports need open for Rsync and in which direction?... I think I found the answer to my own question.

 

According to Buffalo KB#000120 - Setting up LinkStation Remote Backup,

 

  • To set up remote backup using the internal backup, users will need to go into the Web Configuration for both Linkstations.
  • Under Disk backup->Add Linkstation, enter the IP address of the opposite Linkstation. The destination LinkStation needs to have a shared folder created with Disk Backup as one of the supported protocols.
  • In case they need to be opened or forwarded, the ports used are TCP 22939 for discovery, TCP 873 for unencrypted transfer, and TCP 8873 for encrypted transfer. Also, the remote LinkStation passes its assigned IP address to the master.  This means the remote must have a public IP address for this to work.
  • Once the LinkStations can see each other, create the Backup job by going to Disk Backup->Disk Backup. There can be up to 8 assigned jobs. Click on the job you wish to assign and set the schedule and the source and destination folders along with any other settings. Once you click apply the job will run at the scheduled time.

 

 

In my case, my NAS is sitting behind a router firewall and I needed to open those ports and re-direct them to  theNAS. I have my NAS and another server set up as fixed IP addresses, with port re-routing as required for specific services. 

 



 

 

Message Edited by boatlog on 10-08-2008 11:20 PM

sierra2469alpha

   

Cool :smileyhappy:

 

In our proposed architecture, we will have one TeraStation sitting on a WAN which is also accessible via VPN.  A second TeraStation lives outside of that LAN on the Internet, behind a NAS router, (while it is sitting on a LAN, none of its drives will be mapped via the VPN).  Assuming I can get the direct IP addresses for both units, plus open up the required ports, then it should work?

 

I'm wondering if anyone would like to do some testing on this.  I am happy to avail my teraStation for such an exercise.

 

Cheers


boatlog

   I am going to try to get this working tomorrow. One of my linkstations sits behind a corporate firewall, so I will need to get the IT guy to open a port for me to get into it before I can test it. The other linkstation is at home, so I have full control over that one.

boatlog

   

Update: http://forums.buffalotech.com/buffalo/view_profile?user.id=36">sierra2469alpha and I gave this a try. However, it turns out that while we could use FTP successfully without a hitch, the backup was a problem. When the Terrastation and linkstation software ads a remote NAS IP address,

 

"the remote LinkStation passes its assigned IP address to the master.  This means the remote must have a public IP address for this to work. "

 

So, I see his local IP address and my linkstation tries to find his local IP address rather than use the WAN IP address I told it to use.  Looks like both NAS would have to have a public IP address.

 

That is a horrible design flaw in remote backup if you ask me, since all the needed information was given and there is no reason I can think of for passing a local IP address back to the master of the backup. Wish they would change that.


sierra2469alpha

   Matt - boatlog and I just tried this, but it keeps resolving the remote IP's to the local IP of the terastation or linkstation.  You mention adding it by hand, could you explain further for us please?  Thanks!
Message Edited by sierra2469alpha on 10-09-2008 01:12 AM

boatlog

   

Looks like there are ways to rsync through a firewall with tunneling.

http://samba.anu.edu.au/rsync/FAQ.html#6

 

This is getting over my head, but it appears possible.

http://samba.anu.edu.au/rsync/firewall.html

 

But that would require more linux/rsync/networking address that I have and hacking into the Linkstation. In other words, not practical at all.

 



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: 264 (show)
Files included: 35 - 1354KB. (show)
Memory used: 1047KB.
Tokens: post-login.
Queries used: 15.

[Show Queries]