<div>
it looks pretty good right now. &nbsp;I would put a SAN in each location and add a VMHOST for redundancy. &nbsp;if you have a host go down, you can implement VMOTION so if a host goes down, the server will be moved to the new host. &nbsp;( You would have to implement VCenter, but it's worth it, &nbsp;if you have ESXi there is a free version, but i can't remember the name of it) &nbsp; &nbsp;if would also set up your LUNs on the SAN by performance. &nbsp;For exmaple, create a LUN for SQL servers, anther LUN for Exchange data stores ETC. &nbsp;This is all assuming you're using VMWARE. &nbsp;if you're using Hyper-V i can make different recommendations.
</div>


<div>
Yeah my thoughts were to use free esxi for virtualization. &nbsp;If I were to go one VM box, one physical box for a DC, and a SAN, what recommendations for a SAN and any idea on cost?
</div>


<div>
We did a SAN because of multiple hosts, so I'm not sure on this but... With a single host why not use cheaper NAS or DAS? &nbsp;The main advantage of a SAN is connecting multiple hosts to it and they be expensive.
</div>


<div>
If you are going to stay smallish, a single server with 10K SAS drives (not SATA) in RAID 10 makes more sense than a SAN. The free VMware product doesn't really let you do backups, but you can if you use Hyper-V.
</div>


<div>
Whats the best way to have failover between the two VM boxes? &nbsp;So backup for exchange and sql... &nbsp;I use DFS right now for fileshares and redirected mydocs, that seems to work pretty well even though I think MS doesn't recommend using DFS for DR purposes for some reason...<br />

</div>


<div>
<div class="content wysiwyg-content">
So the numbers are the number of servers then the details behind them. &nbsp;Any thoughts? &nbsp;There are 2 data centers, one has about 15 people the other has about 25 and some remotes via VPN so about 55 users total. &nbsp;Current 2003 infrastructure, all on 1u servers now. &nbsp;How does this look and what would you change?<br />
<br />
1. &nbsp;DC2 - Basic domain controller server 08 std, maybe dual xeon, 12gb ram, 1TB raid 10<br />
2. &nbsp;VMBOX2 - &nbsp;Beefy box, quad xeon, 26-30GB ram, 3TB raid 5<br />
-exchange02 - MS Exchange 2010<br />
-ISA exch - Server 2008 std, Microsoft ISA server<br />
-Sql01 - Server 2008 std<br />
<br />
3. &nbsp;DC1 - Same as DC2<br />
4. &nbsp;Exchange01 - Same as DC2 <br />
VMBOX -Same as VMBOX2<br />
-ISA - Server 2008 std, Microsoft ISA server<br />
-SQL02 - Server 2008 std<br />
-SBFileserv1 - Server 2008 std<br />
-SBApp01 - Server 2008 std
</div>
</div>


So the numbers are the number of servers then the details behind them.  Any thoughts?  There are 2 data centers, one has about 15 people the other has about 25 and some remotes via VPN so about 55 users total.  Current 2003 infrastructure, all on 1u servers now.  How does this look and what would you change?

1.  DC2 - Basic domain controller server 08 std, maybe dual xeon, 12gb ram, 1TB raid 10
2.  VMBOX2 -  Beefy box, quad xeon, 26-30GB ram, 3TB raid 5
-exchange02 - MS Exchange 2010
-ISA exch - Server 2008 std, Microsoft ISA server
-Sql01 - Server 2008 std

3.  DC1 - Same as DC2
4.  Exchange01 - Same as DC2 
VMBOX -Same as VMBOX2
-ISA - Server 2008 std, Microsoft ISA server
-SQL02 - Server 2008 std
-SBFileserv1 - Server 2008 std
-SBApp01 - Server 2008 std

Upgrading medium sized business - going virtual

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

IT Administration is the processes and best practices for programming and development, and incorporates methodologies for managing activities and projects. Common methodologies include waterfall, prototyping, iterative and incremental development, spiral development, rapid application development, extreme programming and various types of agile methodology. The life-cycle "model" is a more general term for a category of methodologies, and a software development "process" a more specific term to refer to a specific process chosen by a specific organization.

IT Administration

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.