Notes from TechEd NA 2012 session WSV303:
One of the traits of the Scale-Out File Server is Transparent Failover for server-server apps such as SQL Server or Hyper-V. During a host power/crash/network failure, the IO is paused briefly and flipped over to an alternative node in the SOFS.
The Witness Service and state persistence enable Transparent Failover in SMB 3.0 SOFS. The Witness plays a role in unplanned failover. Instead of a TCP timeout (40 seconds and causing application issues), speeds up the process. It tells the client that the server that they were connected to has failed and should switch to a different server in the SOFS.
NTFS Online Scan and Repair
- CHKDSK can take hours/days on large volumes.
- Scan done online
- Repair is only done when the volume is offline
- Zero downtime with CSV with transparent repair
Clustered Hardware RAID
Designed for when using JBOD, probably with Storage Spaces.
Resilient File System (ReFS)
A new file system as an alternative to NTFS (which is very old now). CHKDSK is not needed at all. This will become the standard file system for Windows over the course of the next few releases.
Comparing the Performance of SMB 3.0
Wow! SMB 3.0 over 1 Gbps network connection achieved 98% of DAS performance using SQL in transactional processing.
If there are multiple 1 Gbps NICs then you can use SMB Multichannel which gives aggregated bandwidth and LBFO. And go extreme with SMB Direct (RDMA) to save CPU.
VSS and SMB 3.0 File Shares
You need a way to support remote VSS snapshots for SMB 3.0 file shares if supporting Hyper-V. We can do app consistent snapshots of VMs stored on a WS2012 file server. Backup just works as normal – backing up VMs on the host.
- Backup talks to backup agent on host.
- Hyper-V VSS Writer reaches into all the VMs and ensures everything is consistent.
- VSS engine is then asked to do the snapshot. In this case, the request is relayed to the file server where the VSS snapshot is done.
- The path to the snapshot is returned to the Hyper-V host and that path is handed back to the backup server.
- The backup server can then choose to either grab the snapshot from the share or from the Hyper-V host.
Dedup is built into Windows Server 2012. It is turned on per-volume. You can exclude folders/file types. By default files not modified in 5 days are deduped – SO IT DOES NOT APPLY TO RUNNING VMs. It identifies redundant data, compresses the chunks, and stores them. Files are deduped automatically and reconstituted on the fly.
REPEAT: Deduplication is not intended for running virtual machines.
The iSCSI target is now built into WS2012 and can provide block storage for Hyper-V before WS2012. ?!?!?! I’m confused. Can be used to boot Hyper-V hosts – probably requiring iSCSI NICs with boot functionality.