distributed filesystem over internet/VPN Post: 302696103

Sponsored Content

Special Forums Hardware Filesystems, Disks and Memory distributed filesystem over internet/VPN Post 302696103 by Domino on Tuesday 4th of September 2012 09:51:46 AM

09-04-2012

Registered User

distributed filesystem over internet/VPN

On this forum was already posted similar question, but it was 4 years ago and didn't give me answers.

I have two groups of engineers that works in far locations connected via VPN. Physically, the connection is a DSL. Currently we have a linux server in one location that provide files over SMB/CIFS. Thus live of people in the second location is a nightmare.

I can change a lot on the server, but one thing must remain. Workstation need to access files using standard windows mechanisms (SMB/CIFS). No extra software (drivers, clients etc).

To solve it, I want to install second server in the second location and use a distributed filessystem that mainly works in replication mode. Files on both servers will be redistributed by samba in the local network.

There is a great list of distributed filesystems on wikipedia.

The most advanced seams to be lustre. But I have some doubts if it will work for me. Lustre is dedicated to a true cluster with a high speed connection (10GigE or special hardware like RDMA). It also stripe space from all nodes, while I rather want to have replication/mirroring.

XtreemFS seams to be more adequate to me. At least from functional site. But it seams that it is JAVA based solution... I'm very afraid for the performance. There is also some limitation for read/write replication.

GlusterFS: according to some blog this filesystem is not good choice for high-latency connection like DSL. (sorry, forum disallow me to publish valid link, add http prefix: joejulian.name/blog/glusterfs-replication-dos-and-donts/)

What is your recommendation?
Had anyone similar problem?

Domino

View Public Profile for Domino

Find all posts by Domino

3 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Wanted: Geographically distributed filesystem solution

I'm looking for a means to ensure that servers in the two or three datacenters, connected in a ring via IP through two ISPs, can distribute load and/or replicate data among at least two SAN-class disk devices. I want to evaluate several solutions, and I'm open to solutions ranging from free,...

2. UNIX for Dummies Questions & Answers

hwo to find shared filesystem and local filesystem in AIX

Hi, I wanted to find out that in my database server which filesystems are shared storage and which filesystems are local. Like when I use df -k, it shows "filesystem" and "mounted on" but I want to know which one is shared and which one is local. Please tell me the commands which I can run...

3. IP Networking

Internet connection single interface through vpn

Hi. Can you please help me with a routing problem? There are 2 networks: 192.168.10.0/24 (eth0) 192.168.11.0/24 (eth0:1) The default gateway is 192.168.10.1 iPv4 routing is already enabled and working. With vpnc I've built up an VPN connection and can access my home network...

LEARN ABOUT DEBIAN

gnunet-vpn

GNUNET-VPN(1)						      General Commands Manual						     GNUNET-VPN(1)

NAME

       gnunet-vpn - manually setup a GNUnet VPN tunnel

SYNOPSIS

       gnunet-vpn [options]

DESCRIPTION

       gnunet-vpn  can	be  used  to manually setup a VPN tunnel via the GNUnet network.  There are two main types of tunnels.	Tunnels to an exit
       node which routes the traffic to the global Internet, and tunnels to a node that runs a service only within GNUnet.  Depending on the  type
       of  tunnel, gnunet-vpn takes different options.	The "-i" option is required for tunnels to an exit node, whereas the "-p" and "-s" options
       in conjunction with either "-u" or "-t" are required for tunnels to services.  For exit tunnels, both UDP and TCP  traffic  will  be  redi-
       rected.	For service tunnels, either UDP ("-u") or TCP ("-t") traffic will be redirected.

       The  tool  will	display the IP address for this end of the tunnel.  The address can be displayed as soon as it has been allocated, or only
       after ("-a") the tunnel has been created.

OPTIONS

       -4, --ipv4
	      Desired IP address on this end of the tunnel should be an IPv4 address.

       -6, --ipv6
	      Desired IP address on this end of the tunnel should be an IPv6 address.

       -a, --after-connect
	      Display IP address only after the tunnel is fully connected.

       -c FILENAME,  --config=FILENAME
	      Use the configuration file FILENAME.

       -d SEC, --duration SEC
	      The mapping should be established for SEC seconds.  Default is 5 minutes.

       -h, --help
	      Print short help on options.

       -i IP, --ip IP
	      Tunnel should be to an exit node and connect to the given IPv4 or IPv6 IP address.  Note that you can specify an IPv6 address as the
	      target here, even in combination with "-4" (4to6) and similarly you can specify an IPv4 address in combination with "-6" (6to4).

       -L LOGLEVEL, --loglevel=LOGLEVEL
	      Use LOGLEVEL for logging.  Valid values are DEBUG, INFO, WARNING and ERROR.

       -p PEERID,  --peer=PEERID
	      Name of the peer offering the service to connect to.  Cannot be used in conjunction with "-i", requires "-s".

       -s NAME,  --service=NAME
	      Name of the service running on the target peer.  Cannot be used in conjunction with "-i", requires "-p".

       -t, --tcp
	      Service runs TCP.  Either "-t" or "-u" must be specified when using "-s".

       -u, --udp
	      Service runs UDP.  Either "-t" or "-u" must be specified when using "-s".

       -V, --verbose
	      Be verbose.

       -v, --version
	      Print GNUnet version number.

BUGS

       Report bugs by using Mantis <https://gnunet.org/bugs/> or by sending electronic mail to <gnunet-developers@gnu.org>

SEE ALSO

       gnunet-setup(1)

GNUnet								    25 Feb 2012 						     GNUNET-VPN(1)