while working with lots of customers in different Azure projects I often here that they want to minimize and reduce their hardware on prem. or even bane every piece of server from their office locations.
In many cases that isn’t really possible. Mostly there are still applications which become very fuzzy with a latency above 30 ms between service and user.
To resolve that gap and reduce the systems on premises to a minimum and save as much money as possible, I started to place Windows Hyper-V Servers with Storage Spaces in the office were I needed lower latency.
At the end we are able to reduce the needed infrastructure to at least two servers, two switches and one router or firewall. I personally call those pieces of hardware “Cache Zone”. The picture below shows a schematic view.
With that I’m able to place services on prem. and cover them via redundancy in the cloud. Currently I have a list of a few basic services like Domain Controller, File Servers, Print Servers or internal Webservers. For the covering of File Servers you can find my post here.
So how does it look like, first you need to connect your office with your cloud provider, either via VPN, MPLS or with some services via HTTPS or other direct services via the internet. You place one partner for example a Domain Controller on prem. the other ones are placed in the cloud.
That’s nearly everything you need. If you use Windows Server 2016 Datacenter for the host, you have also all licenses you need for the features of the virtual machines like Storage Replication.
As server systems, I currently have some small systems von Secure Guard in my testlab.
If you have any questions, don’t hesitate to contact me.
This information were collected together with my old team @Dell TechCenter and Dell Engineerin and one of my best friends Carsten Rachfahl – MVP Hyper-V.
Most of you know Storage Spaces already and you know how to use them for Scale out File Server but in the past there were some “issues” we have to fight with.
For all of you who need a recap for Storage Spaces, Scale out File Server and those stuff. I would highly suggest you Jose Barretos blog (Principal Program Manager at Microsoft).
One was, that you need SCSI Endclosure Service 3.x on your JBOD or direct attached SAS storage enclosures. There are a bunch of small vendors like dataon, who use this version in their systems but many of us have a preferred vendor like HP, EMC, NetApp, IBM or Dell.
Most of them do not support this SES version. Dell came up a few weeks ago with it’s first solution that supports SES 3.x and Storage Spaces. With the second they will come up in Q2 2014 with SES 3.x support.
First solution is the Dell PowerVault MD1200 and Dell PowerVault MD1220 together with the SAS 6 Gbit/sec HBA.
For Dell PV MD1200 Hardware Specs, you can find more details here.
For Dell PV MD1220 Hardware Specs, you can find more details here.
For Dell SAS 6 Gbit/Sec HBA, you can find more details here.
To see the supported designes please check out the guides on Dell Tech Center.
Dell PowerVault MD 1200 (above) & MD 1220 (below) Source: www.dell.de
The second combination could be the Dell PowerVault MD3060e (Codename Roadking) together with LSI 9206-16e. There are no official information yet.
For Dell PV MD3060e Hardware Specs, you can find more details here.
For LSI 9206-16e HBA, you can find more details here.
Dell PowerVault MD3060e (Roadking)
Dell recently published some solution guides about “how to deploy Windows Server 2012 R2 Storage Spaces on Dell PowerVault”.
You can download the document here.
Dell now announced which of it’s Harddrive Firmware supports SCSI Persistent Reservation.
Persistent Reservation with Microsoft Storage Spaces was introduced with Windows Server 2012.
You can read more about SCSI Persistent Reservation here.
To take a look on Dells Firmware Versions please click here.
Dell recently published a blog, where they explained Clustered Storage Spaces support with PowerEdge VRTX. Please be aware that Dell not supports Storage Spaces on VRTX because it’s uses a shared RAID Controller.
To read more about the requirements for Storage Spaces please consult MSDN and read blogpost “How to Configure a Clustered Storage Space in Windows Server 2012”
Please remember, if you want to run your cluster on a shared RAID (maybe for Hyper-V) or Direct Attached Storage you need to configure it in Windows registry. You can find my PowerShell Script, to configure it here.
To read the original Dell TechCenter blogpost, please click here.
Thank you Paul giving me advice on my mistake 🙂