Syncing 2 servers shares on 2 diff sites
- Thread starter Diakatarnis
- Start date
Soldato
- Joined
- 11 Oct 2008
- Posts
- 3,833
- Location
- London
Sharepoint would solve the file-locking issue but it's very, very reliant on rigid and resiliant working processes.
Worth a look at but it is pretty intensive to look after.
Worth a look at but it is pretty intensive to look after.
- Joined
- 30 Jul 2003
- Posts
- 442
stumbled accross a piece of software called peersync and peerlock .... the combination of which seem to do what im looking at, has anyone used this software before?
I'll have a look into the above sugggestions as well
I'll have a look into the above sugggestions as well
Labelling something "enterprise" doesnt make it any good now does it. We use SP and its garbage; sorry i meant enterprise garbage.
OP needs to decide between 3 things....
Do it with shares and file based utilities.
Do it with a CMS
Do it with a CMS which is hosted/cloud
- Joined
- 30 Jul 2003
- Posts
- 442
Well they have 2 servers one at each site, so it seems silly to then pay another company to host the data, so i would go with the share based utils.
Fair enough.
I think having a better insight into what they do with these files and how they get updated and by whom would really help to get the best solution here.
So....
Things id be asking...
* What kind of files are we talking about? Documents? Video? Databases?
* Who creates/edits the file/folders at Site A?
* Who creates/edits the file/folders at Site B?
* When user A at Site A edits file XYZ and user B at Site B does the same, what do they want to happen?
* Are the workers who go from A to B also the people that create/edit these files or are they read only?
* Do they want these two sites shares to be merged? is any benefit to this?
* How much data is in these folders at Site A/B?
* How much does this data change over time at both Sites?
* What servers are their currently and what OS do they have?
* What size pipe connects these sites? and what technology? vpn?
* Are both sites within the same AD infrastructure or just seperate?
Things id be asking to validate they dont have any stretch goals on the back on this first job of connecting these shares?
* Do they want to be able to access this data on their laptops when off-site?
* Do they want to be able to access these files over the internet?
* Do they want any control over the files? like version control? audit of who changed which file etc?
* Do they want to be able to access these files on a mobile device?
we had a similar setup to you with one customer
setup DFSr over Cisco ASA VPN and set outlook at Site B to use outlook over https to connect to Site A server, replication timescale is all the time and even though they are creating cad drawings it works nicely.
server at site b is also a DC for login purposes not for failover so laptops at site b work with taking files offsite when required.
SBS2008 at site A
Server 2008 at site B
running over a 15 ppm adsl line
setup DFSr over Cisco ASA VPN and set outlook at Site B to use outlook over https to connect to Site A server, replication timescale is all the time and even though they are creating cad drawings it works nicely.
server at site b is also a DC for login purposes not for failover so laptops at site b work with taking files offsite when required.
SBS2008 at site A
Server 2008 at site B
running over a 15 ppm adsl line
- Joined
- 30 Jul 2003
- Posts
- 442
can you have a replicated domain controller? i've never attempted this with sbs usualy i have 2 servers but they are doing diff jobs, would be good to have all the users / ou / gp replicated between sites
yes you can but it doesnt work as a failover as the sbs box has to own the RID and PDC master roles. the clients at site B are a member of the domain but they use the local server as a login as opposed to going up the wire and syncing their offline files on log on/off with the server at the other end.
you must not see this as a backup though, sbs goes you are still in the poo
sort of like doing the first part of a swing migration and leaving it at the stage FRS/DNS/AD is replicating
you must not see this as a backup though, sbs goes you are still in the poo
sort of like doing the first part of a swing migration and leaving it at the stage FRS/DNS/AD is replicating
Associate
- Joined
- 3 Oct 2008
- Posts
- 1,890
- Location
- South London
Just having Multiple DCs will do that if they're in the same domain/forest, in basic terms that's how AD works, DCs just cache replicas of the directory from the FSMO role holders (formerly the PDC).
Re: the other issues, do it with shares and one of a huge option of byte level sync software, E.g rSync, though I'd hesitate to suggest that as the best alternative to DFS in this instance.
As for exchange, if you have VPN then either pick a site and run mailboxes off that. So long as they're not GBs in size and they're aren't lots of users involved it should be ok. Though if the organisation isn't that big then probably bang per buck you'd be better of using a hosted exchange solution.
Issue that SBS doesnt like Multiple DC's.
Associate
- Joined
- 3 Oct 2008
- Posts
- 1,890
- Location
- South London
I wasn't referring specifically to SBS, as mentioned the reasoning for going with SBS is the exchange side. If going with hosted exchange SBS would be less appealing and something like 2008 R2 Standard would be more viable without the added cost of exchange on top.
Permabanned
- Joined
- 9 Aug 2008
- Posts
- 35,711
