Hey everyone, we're running a Windows Server for Active Directory and file hosting in one of our offices. Unfortunately, we've been experiencing a lot of power outages which results in unreliable access for users, both local and remote. We're thinking of setting up a second server in another city to create a backup solution. Ideally, users in both locations should access their local servers quickly, and if one goes down, they should easily switch to access the other server. We have about 15 internal users and around 20 external partners who access files mainly through FTP or WireGuard VPN. We're not looking to switch to systems like Nextcloud, but we want a reliable redundant solution for file access across our two offices. Has anyone implemented something similar? Would something like DFS Replication with DFS Namespace work, or are there better options? Thanks in advance for the advice!
6 Answers
I think collocating your servers in a data center could be a solid move. That way, you eliminate local power issues while keeping your existing setup. Just ensure that your VPN connection is consistently up for access.
Using Syncthing for local sync might be another option, especially for file redundancy without dealing with server outages.
If you still want to stick with your current setup, just keep in mind that using DFS has its challenges. You might run into problems where files get locked if someone opens them right before a server outage. Solutions like Egnyte or SharePoint might handle this better and are worth considering, given the risks with on-site servers losing power.
Great tip! Those issues with temporary files and user conflicts can be costly.
You might want to look into Azure File Shares as well. They can provide redundancy and might simplify your setup.
Why not consider moving everything to the cloud? Managing two physical locations can get complicated and pricey, especially for around 35 users. If file access is your only concern, a service like Egnyte or a cloud-based solution might save you a lot of headaches in the long run.
True, that could be a simpler solution if the only issue is access.
Using DFS is probably the easiest way to create a failover situation, but you need to plan carefully. Make sure your VPN users can connect to the secondary server if the main site goes down. Setting up a DNS alias that points to your backup VPN entry could help in this case. You may also want to create an AD site in the second location, and consider having a domain controller there to manage things effectively. This setup could allow for automatic switching when users connect through VPN.
That's a good point! Having a local AD in place would make failover smoother.
Yeah, adding an AD site can really help with reliability!
That sounds smart! Reduces down-time significantly.