This will be a series of blog posts mostly serving as a reminder for myself on how and why the demo setup was build.
The purpose of the setup is to have a static enviroment that is high performing and always will be able to demo system center products , and to have a playground for testing new version and having a place to experiment outside of production enviroments.
The demo setup currently contains 4 servers dedicated to HyperV and one for ESX/XEN providing legacy support for Virtual Machine Manager integration testing.
Storage is currently a single point of failure one server is running Microsoft ISCSI 3.2 (pending 3.3) hosting 15*300gb and 6*146gb , with a quad port 1gb for iscsi support so each HyperV have a dedicated nic for storage access , again currently due to lack of hardware a single point of failure.
There is also one server dedicated for Data Protection Manager , that have internal drives to provide protection , this mainly provide backup of the demo setup and wont be used for experimenting there will be created virtual Data Protection Manager Servers for that.
Networking is one layer 3 switch
On HV01 and HV02 there are a domain controller running outside of the cluster to ensure that the cluster can get up and running again after a power failure or a shutdown
On HV01 there are also a jump host installed installed locally so if i somehow manage to kill the Threat Managment Gateway i wont be locked out and would have to drive to the datacenter to be able to continue working (not that i ever needed that …right )
Microsoft ISCSI Server hosting Qourum Lun and 6 data luns , the “larger” of the drives is each a 3disk raid 5 , and the last drive is 6 smaller drives in a raid5 , this was mainly done to ensure that one VM couldnt take all IO on one LUN but the offset is cost in drives
Only “complaint” about ISCSI Server is the lack of hardware vss support for test Data Protection Manager with HyperV but then again you cant get everything with a free product.
So first few steps , getting firmware updated to Virtual Machine Manager is able to control the hardware , installing base OS , installing Domain Controller , Setting up Clustering and Virtual Machine Manager , then the baseline is in place for the real “work” to begin.