asked on

redundant server hardware setup

I have a customer whom has 30 workstations all win 7 pro 64 they are on a 2003 domain. I want to replace the servers. I need recommendations on a setup. I need the following dhcp, dns, file and print roles. I don't want a San cause that would be over kill. I need all the roles to be redundant incase a server goes down. As for space they don't have a lot about 300 gb of data. The server will also house a quick books db. I would like some recommendations.

Thanks

RantCan

Two servers;
Windows server 2012 (each license of windows server 2012 standard gives you two VMs, so this will give you four VMs to run.

Set up a hyper-v failover cluster;

Create a role with two domain controllers, both dns with a split scope dhcp 60/40;

Create a file server and a print server.

Here is an article on Hyper-v and failover clustering.

http://technet.microsoft.com/en-us/library/cc732181%28v=ws.10%29.aspx

Joseph O'Loughlin

I agree with RantCan
AD relies on DNS
Get DNS working on both servers first. Test DDNS and don't be tempted to go AD integrated
Get AD working and have plans for moving FSMO roles for if and when failures happen.
The cluster nodes need external DNS to register resources, e.g. the cluster name, than can fall over from one node to the other.

Your cluster will look something like
http://blogs.technet.com/b/keithmayer/archive/2013/03/21/virtual-machine-guest-clustering-with-windows-server-2012-become-a-virtualization-expert-in-20-days-part-14-of-20.aspx

The external shared storage needs a dedicated lun for the quorum, and separate luns for the accounts database and resources to be clustered.

ASKER CERTIFIED SOLUTION

Member_2_231077

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial