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
Old 09-04-2012
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?
 

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,... (6 Replies)
Discussion started by: otheus
6 Replies

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... (2 Replies)
Discussion started by: kamranjalal
2 Replies

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... (0 Replies)
Discussion started by: tschmi
0 Replies
SYNC_CLIENT(8)						      System Manager's Manual						    SYNC_CLIENT(8)

 *

NAME
sync_client - client side of the synchronization (replication) engine SYNOPSIS
sync_client [ -v ] [ -l ] [ -z ] [ -C config-file ] [ -S servername ] [ -f input-file ] [ -F shutdown_file ] [ -w wait_interval ] [ -t timeout ] [ -d delay ] [ -r ] [ -u ] [ -m ] [ -s ] objects... DESCRIPTION
Sync_client is the client side of the replication system. It runs on the client (master) system and connects to the target (replica) sys- tem and generates an appropriate sequence of transactions to synchronize the replica system with the master system. OPTIONS
-v Verbose mode. -l Verbose logging mode. -o Only attempt to connect to the backend server once rather than waiting up to 1000 seconds before giving up. -z Enable compress. If you set 'sync_compress' in the imapd.conf or pass -z to sync_client, the replication protocol will attempt to enable deflate compression on the connection. -C config-file Read configuration options from config-file. -S servername Tells sync_client which server to communicate with. Overrides the sync_host configuration option. -f input-file In mailbox or user replication mode: provides list of users or mailboxes to replicate. In rolling replication mode, specifies an alternate log file (sync_client will exit after processing the log file). -F shutdown-file Rolling replication checks for this file at the end of each replication cycle and shuts down if it is present. Used to request nice clean shutdown at first convenient point. The file in question is removed on shutdown. Overrides sync_shutdown_file option in imapd.conf -w interval Wait this long before starting. Typically used so that we can attach a debugger to one end of the replication system or the other. -t timeout Timeout for single replication run in rolling replication. sync_client will negotiate a restart after this many seconds. Default: 600 seconds -d delay Minimum delay between replication runs in rolling replication mode. Larger values provide better efficiency as transactions can be merged. Smaller values mean that the replica system is more up to date and that you don't end up with large blocks of replication transactions as a single group. Default: 3 seconds. -r Rolling (repeat) replication mode. Pick up a list of actions recorded by the lmtpd(8), imapd(8), popd(8) and nntpd(8) daemons from the file specified in sync_log_file. Repeat until sync_shutdwon_file appears. -n Use the named channel for rolling replication mode. If multiple channels are specified in sync_log_channels then use one of them. This option is probably best combined with -S to connect to a different server with each channel. -u User mode. Remaining arguments are list of users who should be replicated. -m Mailbox mode. Remaining arguments are list of mailboxes which should be replicated. -s Sieve mode. Remaining arguments are list of users whose Sieve files should be replicated. Principally used for debugging purposes: not exposed to sync_client(8). FILES
/etc/imapd.conf SEE ALSO
sync_server(8) AUTHORS
David Carter (dpc22@cam.ac.uk), Ken Murchison (ken@oceana.com) CMU
Project Cyrus SYNC_CLIENT(8)
All times are GMT -4. The time now is 05:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy