SoFS|W2k12R2|2x1GB|4x10GB|4xFC

Scale out Fileserver Cluster Network configuration with following parameters:

The following configuration leverages 2x 1GB Ethernet, 4x 10GB Ethernet NICs and LOM (LAN on Motherboard) and 2x Fibre channel connections. There are 4 NICs useable for SMB 3.x.x Multichannel.

The storage is provisioned to the Scale out Fileserver Hosts via Fibrechannel.


 Pro’s and Con’s of that solution

 Pro Con
– High Bandwidth
– Full fault redundant
– Fibrechannel ist most common SAN technology
– many NICs
– a lot of NICs and Switches needed
– a lot of technologies involved
– no separed Team for Cluster and Management
– expensiv

 Switches

Switch name Bandwidth Switchtyp
1GBE SW01 1 GBit/s physical stacked or independed
1GBE SW02 1 GBit/s physical stacked or independed
10GBE SW01 10 GBit/s physical stacked or independed
10GBE SW02 10 GBit/s physical stacked or independed
FC SW01 4/8 GB FC/s physical stacked or independed
FC SW02 4/8 GB FC/s physical stacked or independed

 Neccessary Networks

Networkname VLAN IP Network (IPv4) Connected to Switch
Management 100 10.11.100.0/24  1GBE SW01 & 1GBE SW02 (via NIC Team & VLAN Tagging)
Cluster 101 10.11.101.0/24  1GBE SW01 & 1GBE SW02 (via NIC Team & VLAN Tagging)
SMB 01 200 10.11.45.0/24  10GBE SW01
SMB 02 200 10.11.46.0/24 10GBE SW02
SMB 03 200 10.11.47.0/24 10GBE SW01
SMB 04 200 10.11.48.0/24 10GBE SW02
FC 01 FC SW01
FC 01 FC SW01

 Possible rearview Server


 Schematic representation


Switch Port Configuration

   
 

QoS Configuration Switch

Networkname Priority
Management medium
Cluster high
SMB Traffic High

 

Blogpost about Scale out Fileserver @Elanity Technik Blogs

Hey all,

for that guy’s who speak german. I published a blogpost about Scale ot Fileserver at the German Technik Blog of Elanity Network Partner GmbH.

Just click http://www.elanity.de/technikblog/scale-out-fileserver. 🙂

Cheers,

Flo

White paper – Building High Performance Storage for Hyper-V Cluster on Scale-Out

A few days ago, Microsoft published a whitepaper how to build High Performance Storage for Hyper-V Cluster on Scale-Out File Servers using Violin Windows Flash Arrays.

To take a look on, please click here.

Hyper-V VHD files inaccessable after reinstallation from Hyper-V host

Today I had a funny session with my coworker Jens Nilsson. Last week we encountert an issue with his Hyper-V cluster and we needed reinstall one of his hosts.

After we reinstalled the host and tried to import some of his no clustered VMs, stored on a local drive, we encounter follwing issue.

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          9/19/2014 4:11:06 AM
Event ID:      12620
Task Category: None
Level:         Error
Keywords:

User: SYSTEM
Computer: HV02.test.local
Description:
”: Cannot get information for attachment ‘D:\virtualmachines\VHD\CLY01.vhdx’. (Virtual machine ID )

Microsoft-Windows-Hyper-V-VMMS-Admin
HV02.test.local

D:\virtualmachines\VHD\CLY01.vhdx
%%2147944320
0x80070780

So at first we thought it was an security issue and we checked those. They were fine and no services were blocking the access. During our discussion, Jens told me, he was using Windows Server 2012 R2 data deduplication on that drive with the old installation.

Ok that was the information I needed. In our case that meas, the file was still on the disk but when you tried to open it, Windows was missing the index to reassemble the blocks belonging to the file.

Now comes the issue, how can we fix that. Our first and for us both studid idea. Lets install data depluction again. Maybe he will be able to find his index again. Aehm … you know what happens with stupid ideas? They often work, in that moment too.

Next we wanted to find out why, the only possible solution was, the index for dedup is stored in the system volume information of the drive where it is configured. Which means, when you backup a drive where you use dedup, do not forget to save the system volume information too.