Microsoft Azure September 2017 Software Defined Data Infrastructure Updates

Microsoft Azure September 2017 Software Defined Data Infrastructure Updates

server storage I/O data infrastructure trends

Microsoft and Azure September 2017 Software Defined Data infrastructure Updates

September was a busy month for data infrastructure topics as well as Microsoft in terms of new and enhanced technologies. Wrapping up September was Microsoft Ignite where Azure, Azure Stack, Windows, O365, AI, IoT, development tools announcements occurred, along with others from earlier in the month. As part of the September announcements, Microsoft released a new version of Windows server (e.g. 1709) that has a focus for enhanced container support. Note that if you have deployed Storage Spaces Direct (S2D) and are looking to upgrade to 1709, do your homework as there are some caveats that will cause you to wait for the next release. Note that there had been new storage related enhancements slated for the September update, however those were announced at Ignite to being pushed to the next semi-annual release. Learn more here and also here.

Azure Files and NFS

Microsoft made several Azure file storage related announcements and public previews during September including Native NFS based file sharing as companion to existing Azure Files, along with public preview of new Azure File Sync Service. Native NFS based file sharing (public preview announced, service is slated to be available in 2018) is a software defined storage deployment of NetApp OnTAP running on top of Azure data infrastructure including virtual machines and leverage Azure underlying storage.

Note that the new native NFS is in addition to the earlier native Azure Files accessed via HTTP REST and SMB3 enabling sharing of files inside Azure public cloud, as well as accessible externally from Windows based and Linux platforms including on premises. Learn more about Azure Storage and Azure Files here.

Azure File Sync (AFS)

Azure File Sync AFS

Azure File Sync (AFS) has now entered public preview. While users of Windows-based systems have been able to access and share Azure Files in the past, AFS is something different. I have used AFS for some time now during several private preview iterations having seen how it has evolved, along with how Microsoft listens incorporating feedback into the solution.

Lets take a look at what is AFS, what it does, how it works, where and when to use it among other considerations. With AFS, different and independent systems can now synchronize file shares through Azure. Currently in the AFS preview Windows Server 2012 and 2016 are supported including bare metal, virtual, and cloud based. For example I have had bare metal, virtual (VMware), cloud (Azure and AWS) as part of participating in a file sync activities using AFS.

Not to be confused with some other storage related AFS including Andrew File System among others, the new Microsoft Azure File Sync service enables files to be synchronized across different servers via Azure. This is different then the previous available Azure File Share service that enables files stored in Azure cloud storage to be accessed via Windows and Linux systems within Azure, as well as natively by Windows platforms outside of Azure. Likewise this is different from the recently announced Microsoft Azure native NFS file sharing serving service in partnership with NetApp (e.g. powered by OnTAP cloud).

AFS can be used to synchronize across different on premise as well as cloud servers that can also function as cache. What this means is that for Windows work folders served via different on premise servers, those files can be synchronized across Azure to other locations. Besides providing a cache, cloud tiering and enterprise file sync share (EFSS) capabilities, AFS also has robust optimization for data movement to and from the cloud and across sites, along with management tools. Management tools including diagnostics, performance and activity monitoring among others.

Check out the AFS preview including planning for an Azure File Sync (preview) deployment (Docs Microsoft), and for those who have Yammer accounts, here is the AFS preview group link.

Microsoft Azure Blob Events via Microsoft

Azure Blob Storage Tiering and Event Triggers

Two other Azure storage features that are in public preview include blob tiering (for cold archiving) and event triggers for events. As their names imply, blob tiering enables automatic migration from active to cold inactive storage of dormant date. Event triggers are policies rules (code) that get executed when a blob is stored to do various functions or tasks. Here is an overview of blob events and a quick start from Microsoft here.

Keep in mind that not all blob and object storage are the same, a good example is Microsoft Azure that has page, block and append blobs. Append blobs are similar to what you might be familiar with other services objects. Here is a Microsoft overview of various Azure blobs including what to use when.

Project Honolulu and Windows Server Enhancements

Microsoft has evolved from command prompt (e.g. early MSDOS) to GUI with Windows to command line extending into PowerShell that left some thinking there is no longer need for GUI. Even though Microsoft has extended its CLI with PowerShell spanning WIndows platforms and Azure, along with adding Linux command shell, there are those who still want or need a GUI. Project Honolulu is the effort to bring GUI based management back to Windows in a simplified way for what had been headless, and desktop less deployments (e.g. Nano, Server Core). Microsoft had Server Management Tools (SMT) accessible via the Azure Portal which has been discontinued.


Project Honolulu Image via Microsoft.com

This is where project Honolulu comes into play for managing Windows Server platforms. What this means is that for those who dont want to rely on or have a PowerShell dependency have an alternative option. Learn more about Project Honolulu here and here, including download the public preview here.

Storage Spaces Direct (S2D) Kepler Appliance

Data Infrastructure provider DataOn has announced a new turnkey Windows Server 2016 Storage Spaces Direct (S2D) powered Hyper-Converged Infrastructure (e.g. productization of project Kepler-47) solution with two node small form factor servers (partner with MSI). How small? Think suitcase or airplane roller board carry on luggage size.

What this means is that you can get into the converged, hyper-converged software defined storage game with Windows-based servers supporting Hyper-V virtual machines (Windows and Linux) including hardware for around $10,000 USD (varies by configuration and other options).

Azure and Microsoft Networking News

Speaking of Microsoft Azure public cloud, ever wonder what the network that enables the service looks like and some of the software defined networking (SDN) along with network virtualization function (NFV) objectives are, have a look at this piece from over at Data Center Knowledge.

In related Windows, Azure and other focus areas, Microsoft, Facebook and Telxius have completed the installation of a high-capacity subsea cable (network) to cross the atlantic ocean. Whats so interesting from a data infrastructure, cloud or legacy server storage I/O and data center focus perspective? The new network was built by the combined companies vs. in the past by a Telco provider consortium with the subsequent bandwidth sold or leased to others.

This new network is also 4,000 miles long including in depths of 11,000 feet, supports with current optics 160 terabits (e.g. 20 TeraBytes) per second capable of supporting 71 million HD videos streamed simultaneous. To put things into perspective, some residential Fiber Optic services can operate best case up to 1 gigabit per second (line speed) and in an asymmetrical fashion (faster download than uploads). Granted there are some 10 Gbit based services out there more common with commercial than residential. Simply put, there is a large amount of bandwidth increased across the atlantic for Microsoft and Facebook to support growing demands.

Where To Learn More

Learn more about related technology, trends, tools, techniques, and tips with the following links.

What This All Means

Microsoft announced a new release of Windows Server at Ignite as part of its new semi-annual release cycle. This latest version of Windows server is optimized for containers. In addition to Windows server enhancements, Microsoft continues to extend Azure and related technologies for public, private and hybrid cloud as well as software defined data infrastructures.

By the way, if you have not heard, its Blogtober, check out some of the other blogs and posts occurring during October here.

Ok, nuff said, for now.
Gs

Greg Schulz – Microsoft MVP Cloud and Data Center Management, VMware vExpert 2010-2017 (and vSAN). Author of Software Defined Data Infrastructure Essentials (CRC Press), as well as Cloud and Virtual Data Storage Networking (CRC Press), The Green and Virtual Data Center (CRC Press), Resilient Storage Networks (Elsevier) and twitter @storageio.

Courteous comments are welcome for consideration. First published on https://storageioblog.com any reproduction in whole, in part, with changes to content, without source attribution under title or without permission is forbidden.

All Comments, (C) and (TM) belong to their owners/posters, Other content (C) Copyright 2006-2023 Server StorageIO(R) and UnlimitedIO. All Rights Reserved.

Microsoft Windows Server, Azure, Nano Life cycle Updates

server storage I/O trends

Microsoft Windows Server, Azure, Nano and life cycle Updates

For those of you who have an interest in Microsoft Windows Server on-premises, on Azure, on Hyper-V or Nano life cycle here are some recently announced updates.
Microsoft Windows Server Nano Lifecycle

Microsoft has announced updates to Windows Server Core and Nano along with semi-annual channel updates (read more here). The synopsis of this new update via Microsoft (read more here) is:

In this new model, Windows Server releases are identified by  the year and month of release: for example, in 2017, a release in the 9th month  (September) would be identified as version 1709. Windows Server will release  semi-annually in fall and spring. Another release in March 2018 would be  version 1803. The support lifecycle for each release is 18 months.

Microsoft has announced that its lightweight variant of WIndows Server 2016 (if you need a refresh on server requirements visit here) known as nano will now be focused for WIndows based containers as opposed to being for bare metal. As part of this change, Microsoft has reiterated that Server Core the headless (aka non-desktop user interface) version of WIndows Server 2016 will continue as the platform for BM along with other deployments where a GUI interface is not needed. Note that one of the original premises of Nano was that it could be leveraged as a replacement for Server Core.

As part of this shift, Microsoft has also stated their intention to further streamline the already slimmed down version of WIndows Server known as Nano by reducing its size another 50%. Keep in mind that Nano is already a fraction of the footprint size of regular Windows Server (Core or Desktop UI). The footprint of Nano includes both its capacity size on disk (HDD or SSD), as well as its memory requirements, speed of startup boot, along with number of components that cut the number of updates.

By focusing Nano for container use (e.g. Windows containers) Microsoft is providing multiple micro services engines (e.g. Linux and Windows) along with various management including Docker. Similar to providing multiple container engines (e.g. Linux and Windows) Microsoft is also supporting management from Windows along with Unix.

Does This Confirm Rumor FUD that Nano is Dead

IMHO the answer to the FUD rumors that are circulating around that NANO is dead are false.

Granted Nano is being refocused by Microsoft for containers and will not be the lightweight headless Windows Server 2016 replacement for Server Core. Instead, the Microsoft focus is two path with continued enhancements on Server Core for headless full Windows Server 2016 deployment, while Nano gets further streamlined for containers. This means that Nano is no longer bare metal or Hyper-V focused with Microsoft indicating that Server Core should be used for those types of deployments.

What is clear (besides no bare metal) is that Microsoft is working to slim down Nano even further by removing bare metal items, Powershell,.Net and other items instead of making those into optional items. The goal of Microsoft is to make the base Nano image on disk (or via pull) as small as possible with the initial goal of being 50% of its current uncompressed 1GB disk size. What this means is that if you need Powershell, you add it as a layer, need .Net then add as a layer instead of having the overhead of those items if you do not need tem. It will be interesting to see how much Microsoft is able to remove as standard components and make them options that you can simply add as layers if needed.

What About Azure and Bring Your Own License

In case you were not aware or had forgotten when you use Microsoft Azure and deploy virtual machine (aka cloud instances), you have the option of bringing (e.g. using) your own WIndows Server licenses. What this means is that by using your own Windows Server licenses you can cut the monthly cost of your Azure VMs. Check out the Azure site and explore various configuration options to learn more about pricing and various virtual machine instances from Windows to Linux here as well as hybrid deployments.

Where To Learn More

What This All Means

Microsoft has refocused Windows Server 2016 Core and Desktop as its primary bare metal including for virtual as well as Azure OS platforms, while Nano is now focused on being optimized for Windows-based containers including Docker among other container orchestration.

Ok, nuff said (for now…).

Cheers
Gs

Greg Schulz – Multi-year Microsoft MVP Cloud and Data Center Management, VMware vExpert (and vSAN). Author of Software Defined Data Infrastructure Essentials (CRC Press), as well as Cloud and Virtual Data Storage Networking (CRC Press), The Green and Virtual Data Center (CRC Press), Resilient Storage Networks (Elsevier) and twitter @storageio.

Courteous comments are welcome for consideration. First published on https://storageioblog.com any reproduction in whole, in part, with changes to content, without source attribution under title or without permission is forbidden.

All Comments, (C) and (TM) belong to their owners/posters, Other content (C) Copyright 2006-2023 Server StorageIO(R) and UnlimitedIO. All Rights Reserved.

Gaining Server Storage I/O Insight into Microsoft Windows Server 2016

Server Storage I/O Insight into Microsoft Windows Server 2016

server storage I/O trends
Updated 12/8/16

In case you had not heard, Microsoft announced the general availability (GA, also known as Release To Manufacturing (RTM) ) of the newest version of its Windows server operating system aka Windows Server 2016 along with System Center 2016. Note that as well as being released to traditional manufacturing distribution mediums as well as MSDN, the Windows Server 2016 bits are also available on Azure.

Microsoft Windows Server 2016
Windows Server 2016 Welcome Screen – Source Server StorageIOlab.com

For some this might be new news, or a refresh of what Microsoft announced a few weeks ago (e.g. the formal announcement). Likewise, some of you may not be aware that Microsoft is celebrating WIndows Server 20th Birthday (read more here).

Yet for others who have participated in the public beta aka public technical previews (TP) over the past year or two or simply after the information coming out of Microsoft and other venues, there should not be a lot of surprises.

Whats New With Windows Server 2016

Microsoft Windows Server 2016 Desktop
Windows Server 2016 Desktop and tools – Source Server StorageIOlab.com

Besides a new user interface including visual GUI and Powershell among others, there are many new feature functionalities summarized below:

  • Enhanced time-server with 1ms accuracy
  • Nano and Windows Containers (Linux via Hyper-V)
  • Hyper-V enhanced Linux services including shielded VMs
  • Simplified management (on-premisess and cloud)
  • Storage Spaces Direct (S2D) and Storage Replica (SR) – view more here and here


Storage Replica (SR) Scenarios including synchronous and asynchronous – Via Microsoft.com

  • Resilient File System aka ReFS (now default file system) storage tiering (cache)
  • Hot-swap virtual networking device support
  • Reliable Change Tracking (RCT) for faster Hyper-V backups
  • RCT improves resiliency vs. VSS change tracking
  • PowerShell and other management enhancements
  • Including subordinated / delegated management roles
  • Compliment Azure AD with on premise AD
  • Resilient/HA RDS using Azure SQL DB for connection broker
  • Encrypted VMs (at rest and during live migration)
  • AD Federation Services (FS) authenticate users in LDAP dir.
  • vTPM for securing and encrypting Hyper-V VMs
  • AD Certificate Services (CS) increase support for TPM
  • Enhanced TPM support for smart card access management
  • AD Domain Services (DS) security resiliency for hybrid and mobile devices

Here is a Microsoft TechNet post that goes into more detail of what is new in WIndows Server 2016.

Free ebook: Introducing Windows Server 2016 Technical Preview (Via Microsoft Press)

Check out the above free ebook, after looking through it, I recommend adding it to your bookshelf. There are lots of good intro and overview material for Windows Server 2016 to get you up to speed quickly, or as a refresh.

Storage Spaces Direct (S2D) CI and HCI

Storage Spaces Direct (S2D) builds on Storage Spaces that appeared in earlier Windows and Windows Server editions. Some of the major changes and enhancements include ability to leverage local direct attached storage (DAS) such as internal (or external) dedicated NVMe, SAS and SATA HDDs as well as flash SSDs that used for creating software defined storage for various scenarios.

Scenarios include converged infrastructure (CI) disaggregated as well as aggregated hyper-converged infrastructure (HCI) for Hyper-V among other workloads. Windows Server 2016 S2D nodes communicate (from a storage perspective) via a software storage bus. Data Protection and availability is enabled between S2D nodes via Storage Replica (SR) that can do software based synchronous and asynchronous replication.


Aggregated – Hyper-Converged Infrastructure (HCI) – Source Microsoft.com


Desegregated – Converged Infrastructure (CI) – Source Microsoft.com

The following is a Microsoft produced YouTube video providing a nice overview and insight into Windows Server 2016 and Microsoft Software Defined Storage aka S2D.




YouTube Video Storage Spaces Direct (S2D) via Microsoft.com

Server storage I/O performance

What About Performance?

A common question that comes up with servers, storage, I/O and software defined data infrastructure is what about performance?

Following are some various links to different workloads showing performance for Hyper-V, S2D and Windows Server. Note as with any benchmark, workload or simulation take them for what they are, something to compare that may or might not be applicable to your own workload and environments.

  • Large scale VM performance with Hyper-V and in-memory transaction processing (Via Technet)
  • Benchmarking Microsoft Hyper-V server, VMware ESXi and Xen Hypervisors (Via cisjournal PDF)
  • Server 2016 Impact on VDI User Experience (Via LoginVSI)
  • Storage IOPS update with Storage Spaces Direct (Via TechNet)
  • SQL Server workload (benchmark) Order Processing Benchmark using In-Memory OLTP (Via Github)
  • Setting up testing Windows Server 2016 and S2D using virtual machines (Via MSDN blogs)
  • Storage throughput with Storage Spaces Direct (S2D TP5 (Via TechNet)
  • Server and Storage I/O Benchmark Tools: Microsoft Diskspd (Part I)

Where To Learn More

For those of you not as familiar with Microsoft Windows Server and related topics, or that simply need a refresh, here are several handy links as well as resources.

  • Introducing Windows Server 2016 (Free ebook from Microsoft Press)
  • What’s New in Windows Server 2016 (Via TechNet)
  • Microsoft S2D Software Storage Bus (Via TechNet)
  • Understanding Software Defined Storage with S2D in Windows Server 2016 (Via TechNet)
  • Microsoft Storage Replica (SR) (Via TechNet)
  • Server and Storage I/O Benchmark Tools: Microsoft Diskspd (Part I)
  • Microsoft Windows S2D Software Defined Storage (Via TechNet)
  • Windows Server 2016 and Active Directory (Redmond Magazine Webinar)
  • Data Protection for Modern Microsoft Environments (Redmond Magazine Webinar)
  • Resilient File System aka ReFS (Via TechNet)
  • DISKSPD now on GitHub, and the mysterious VMFLEET released (Via TechNet)
  • Hyper-converged solution using Storage Spaces Direct in Windows Server 2016 (Via TechNet)
  • NVMe, SSD and HDD storage configurations in Storage Spaces Direct TP5 (Via TechNet)
  • General information about SSD at www.thessdplace.com and NVMe at www.thenvmeplace.com
  • How to run nested Hyper-V and Windows Server 2016 (Via Altaro and via MSDN)
  • How to run Nested Windows Server and Hyper-V on VMware vSphere ESXi (Via Nokitel)
  • Get the Windows Server 2016 evaluation bits here
  • Microsoft Azure Stack overview and related material via Microsoft
  • Introducing Windows Server 2016 (Via MicrosoftPress)
  • Various WIndows Server and S2D lab scripts (Via Github)
  • Storage Spaces Direct – Lab Environment Setup (Via Argon Systems)
  • Setting up S2D with a 4 node configuration (Via StarWind blog)
  • SQL Server workload (benchmark) Order Processing Benchmark using In-Memory OLTP (Via Github)
  • Setting up testing Windows Server 2016 and S2D here using virtual machines (Via MSDN blogs)
  • Hyper-V large-scale VM performance for in-memory transaction processing (Via Technet)
  • BrightTalk Webinar – Software-Defined Data Centers (SDDC) are in your Future (if not already here)
  • Microsoft TechNet: Understand the cache in Storage Spaces Direct
  • BrightTalk Weibniar – Software-Defined Data Infrastructures Enabling Software-Defined Data Centers
  • Happy 20th Birthday Windows Server, ready for Server 2016?
  • Server StorageIO resources including added links, tools, reports, events and more.

What This All Means

While Microsoft Windows Server recently celebrated its 20th birthday (or anniversary), a lot has changed as well as evolved. This includes Windows Servers 2016 supporting new deployment and consumption models (e.g. lightweight Nano, full data center with desktop interface, on-premises, bare metal, virtualized (Hyper-V, VMware, etc) as well as cloud). Besides how consumed and configured, which can also be for CI and HCI modes, Windows Server 2016 along with Hyper-V extend the virtualization and container capabilities into non-Microsoft environments specifically around Linux and Docker. Not only are the support for those environments and platforms enhanced, so to are the management capabilities and interfaces from Powershell to Bash Linux shell being part of WIndows 10 and Server 2016.

What this all means is that if you have not looked at Windows Server in some time, its time you do, even if you are not a WIndows or Microsoft fan, you will want to know what it is that has been updated (perhaps even update your fud if that is the case) to stay current. Get your hands on the bits and try Windows Server 2016 on a bare metal server, or as a VM guest, or via cloud including Azure, or simply leverage the above resources to learn more and stay informed.

Ok, nuff said, for now…

Cheers
Gs

Greg Schulz – Microsoft MVP Cloud and Data Center Management, vSAN and VMware vExpert. Author Cloud and Virtual Data Storage Networking (CRC Press), The Green and Virtual Data Center (CRC Press) and Resilient Storage Networks (Elsevier) and twitter @storageio

All Comments, (C) and (TM) belong to their owners/posters, Other content (C) Copyright 2006-2023 Server StorageIO(R) and UnlimitedIO All Rights Reserved

Happy 20th Birthday Microsoft Windows Server, get ready for Windows Server 2016

Happy 20th Birthday Windows Server, ready for Server 2016?

server storage I/O trends

In case you have not heard, Microsoft is celebrating the 20th birthday (or anniversary) of Windows Server.

Microsoft has a nice site with info graphics and timelines of where Windows Server has been and accomplished over the past 20 years (view here).

Some of you may remember from 20 years ago Windows Server with a different name aka Windows NT Server. Back in the day, if you recall (or read), server requirements were more in the 33 MHz vs. 3.3GHz range, 32MB of RAM Memory vs. 32GB to 320GB, 150MB HDD vs. 150GB SSD or 1.5TB HDD.

Keep in mind that 20 years ago Linux was a relative new thing with Red Hat not yet quite household or more specific enterprise name. The various Unix (e.g. IBM AIX, HP HP-UX, Sun Solaris, DEC Unix and Ultrix among many others) were still dominate, OS2 had peaked or close to, among others. Virtual Machines were Logical Partitions (LPAR) on Mainframes along with virtual PCs software and hardware assist boards.

IMHO there is no coincidence of Microsoft celebrating 20 years of WIndows Server going into the fall of 2016 and the upcoming release of Server 2016.

What’s New in Server 2016 (TP5)?

If you have not done so, check out the latest Tech Preview 5 (TP5) of Windows Server 2016 (get the bits e.g. software here to try) which includes Storage Spaces Direct (S2D) that leverages internal PCIe and drive format SSD (NVMe, SAS, SATA) along with HDDs (SAS, SATA) for creating local and scale-out converged (desegregated) and hyper-converged (aggregated) solutions. In addition to S2D there is Storage Replica (SR) which is replication of local storage part of S2D (not to be confused with DFS or other replication).

Other enhancements include ReFS as the default file system instead of NTFS (don’t worry, NTFS like FAT does not go away yet). There are enhancements to Hyper-V including VM shielding, hot-plug virtual network adapters, enhanced Linux support and fail over priorities among others. Other enhancements include updates for AD including improved integration with on-premises as well as Azure AD for hybrid environments, PowerShell updates, Docker management including Linux (via Hyper-V) and Windows via Nano) container engines.

Microsoft Windows Server 2016 TP5

Speaking of Nano, if you had not heard, this is a new very light weight Windows Kernel that removes 32 bit WOW and GUI support. The result is that Nano is a very small physical (under 1GB image instance size) using less disk, less memory and less CPU to do a given amount of work, oh, and boots super fast, even without SSD. By not having all the 32 bit and GUI overhead, the intent with Nano is there should be fewer updates and maintenance tasks to do, while enabling Windows containers for SQL Server and other applications.

In addition to PowerShell, AD and other management enhancements, Windows Server 2016 (TP5) also enables bridging two worlds e.g. traditional on-premises (or cloud) based Windows Server and Public Cloud (e.g. Azure) and Private or Hybrid including Azure Stack. Note that if you have not heard of Azure Stack and are looking at cloud stacks such as OpenStack, do your due diligence and at least familiarize yourself with Azure Stack.

View more about WIndows 2016 TP5 enhancements here.

Where To Learn More

What This All Means

Congratulations Microsoft and Windows Server on 20th birthday (anniversary) you have come a long way.

With the new features and functionality in Windows Server 2016, looks like there is still a good future for the software defined server.

Ok, nuff said, for now…

Cheers
Gs

Greg Schulz – Author Cloud and Virtual Data Storage Networking (CRC Press), The Green and Virtual Data Center (CRC Press) and Resilient Storage Networks (Elsevier)
twitter @storageio

All Comments, (C) and (TM) belong to their owners/posters, Other content (C) Copyright 2006-2023 Server StorageIO(R) and UnlimitedIO All Rights Reserved