How to set up local server replication and redundancy
Small MSP environments often lack straightforward tools for full local server replication, forcing technicians to piece together complex solutions without clear best practices. This makes it difficult to design reliable redundancy setups or validate configurations left behind by previous engineers before presenting them to clients.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1Setting up separate domain controllers per rack
- 2Using DFS for file servers
- 3Installing a new Windows Server VM and promoting it to a domain controller
- 4Bypassing slow shared storage restores by attaching a temporary local disk to only the primary node, which leaves the database outside the availability group and breaks failover.
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“I've been looking for software or a solution that could replicate the entire server to the second local machine, but I'm having a hard time figuring out what would be the best approach.”source ↗
“I'm dealing with a messy SQL Server cluster issue left behind by a terminated engineer and could really use a sanity check on my assessment before I present the final options to the management/client.”source ↗
Where this came up
People with this problem also raised
- 4How to set up a reliable backup internet connection
- 3How to make offsite immutable backups affordable and recoverable
- 2How do I use a transfer switch for a backup generator?
- 2How do I take over home tech and cameras when my partner is gone?
- 2What to do when your cloud service suddenly shuts down
- 4Who wins when warehouse data and CRM updates clash?