MVPLAB Serie Installing SCOM 2022 monitoring with SQL Cluster #SCOM #MVPBuzz

System Center 2022 Operations Manager (SCOM)

Before we can install Microsoft System Center Operations Manager 2022 in my mvplab.local domain, I installed the following:

• MVPLAB Serie Windows Server Insider Cluster with ISCSI Target Server

• MVPLAB Serie Cluster Aware Updating – CAU for Windows Server Insider

• MVPLAB Serie Installing SQL Server 2022 CTP on Windows Server Insider Cluster

Installing Operations Manager creates a management group. The management group is the basic unit of functionality. At a minimum, a management group consists of a management server, the operational database, and the reporting data warehouse database.

• The management server is the focal point for administering the management group and communicating with the database. When you open the Operations console and connect to a management group, you connect to a management server for that management group. Depending on the size of your computing environment, a management group can contain a single management server or multiple management servers.
• The operational database is a SQL Server database that contains all configuration data for the management group and stores all monitoring data that is collected and processed for the management group. The operational database retains short-term data, by default 7 days.
• The data warehouse database is a SQL Server database that stores monitoring and alerting data for historical purposes. Data that is written to the Operations Manager database is also written to the data warehouse database, so reports always contain current data. The data warehouse database retains long-term data.

When Operations Manager reporting functionality is installed, the management group also contains a Reporting server which builds and presents reports from data in the data warehouse database.

These core components of a management group can exist on a single server, or they can be distributed across multiple servers, as shown in the following image.

In my Test LAB mvplab.local I will install the Management Server on a Windows Server Insider member Server and the Operational Database with the Data Warehouse Database on the SQL Cluster Instance. Here you find more Microsoft Information about System Center 2022 Operations Manager

Architecture SCOM 2022

IMPORTANT : In my MVPLAB I’m working with Windows Server Insider Preview Builds and with SQL Server 2022 CTP2.1 Preview version on a Cluster and is not supported yet for Production workloads, then you have to wait for Microsoft to make it General Available!

Now we have a SQL Cluster Instance running in my mvplab.local domain, I’m going to install Microsoft System Center 2022 Operations Manager (SCOM) for monitoring in the following step-by-step guide :

Run SCOM_2022 as Administrator

Click on Next

Click on Accept the Agreement.
Click on Next

Extract the files to your location.
Click on Next

Click on Extract

Completed Click on Finish

Run Setup

Click on Install

I’m installing only the Management Server and Operations Console.
When this was Production I would install every feature on separated Servers with
two Management Servers.
Click on Next

Select installation location
Click on Next

Click on Next

Give your Management Group a Name.
Click on Next

Agree with the License Terms.
Click on Next

Select de SQL Instance and Port.
Set Database Size.
and Data File Folders.
Click on Next

Here you can select de Instance for data warehouse database.
Click Next

Select the Service accounts
Click on Next

Click on Next

Check the Summary.
Click on Install

SCOM 2022 Installation in Progress.

Processing

SCOM License we set later.

I have installed both databases in one SQL Instance for in my MVPLAB.

 

System Center 2022 Operations Manager (SCOM)

Now you can Configure the Management Packs in SCOM for your environment and set the Alerts. More information about System Center 2022 Operations Manager can you find here :

What’s New in Operations Manager

What is in an Operations Manager management pack?

Microsoft System Center Blog on MS Tech Community

In the following MVPLAB Serie Blogpost I will Install Microsoft System Center Operations Manager Web Server 2022 for Monitoring with your web browser.

MVPLAB Serie Installing SQL Server 2022 CTP on Windows Server Insider Cluster #SQLServer #WIMVP

SQL Server 2022 CTP2.1

In this blogpost of MVPLAB Serie, we are going to install Microsoft SQL Server 2022 CTP2.1 on my Windows Server Insider Preview Cluster in mvplab.local domain. Before this blogpost I installed the following basics in mvplab.local domain :

• MVPLAB Serie Windows Server Insider Cluster with ISCSI Target Server

• MVPLAB Serie Cluster Aware Updating – CAU for Windows Server Insider

Now we are going to install the Backend of the datacenter, and that is SQL Server 2022 CTP2.1 on a Cluster resource with the first SQL Instance for databases which is High Available (HA).

First we download SQL Server 2022 CTP2.1

SQL Server 2022 Preview is the most Azure-enabled release of SQL Server yet, with continued innovation in security, availability, and performance.

• Integration with Azure Synapse Link and Azure Purview enables customers to drive deeper insights, predictions, and governance from their data at scale.
• Cloud integration is enhanced with disaster recovery (DR) to Azure SQL Managed Instance, along with no-ETL (extract, transform, and load) connections to cloud analytics, which allow database administrators to manage their data estates with greater flexibility and minimal impact to the end-user.
• Performance and scalability are automatically enhanced via built-in query intelligence.
• There is choice and flexibility across languages and platforms, including Linux, Windows, and Kubernetes.

Mount the ISO file and Copy the files to a local disk location, then run Setup as Administrator with your personal Domain Administrator Account to install SQL Server 2022 CTP2.1. Before the installation read Configure Cluster accounts in Active Directory (AD)

Click on Yes.

Click on the left on Installation
Then Click on New SQL Server Failover Cluster Installation

Here I choose for the Developer edition.
Click on Next

Accept the License terms
Click on Next

Check for Updates (recommended)
Click on Next

Check the Warnings and solve issues.
Click on Next

I Installed only the default for SQL Database.
(You can install later Shared SQL Features if you need them.)
Click on Next

Specify a network name for the New SQL Server Failover Cluster.
mvpsql01
Click on Named Instance and type INSTANCE01
Click on Next

Click on Next

Select your Cluster disk
Click on Next

Select IPv4 and type the IP-Address of your Cluster Resource
mvpsql01
Then Click on Next

Select your domain Service accounts and type the passwords.
Select if you want Maintenance Tasks privilege to your SQL Server Database Engine Service.
Click Next

Here you can add the SQL Admin Group from Active Directory (AD)
Click on top tab Data Directories

I Changed the User Database Log Directory.
Here you can set your directories.
Have a look at the Other TAB fields, I set Memory later.
When you finished all the Tabs then click Next

Check the Summary and click on Install

SQL Server 2022 CTP2.1 Installed Successfully Click on Close.

This was on the first mvpfs01.mvplab.local, now you have to do the installation on the other node mvpfs02.mvplab.local.
Here we will add a SQL Node to the Cluster.

 

Click on the left on Installation
Then Click on Add Node to a SQL Server Failover Cluster

Add Node in Progress

Add Node to SQL Server 2022 CTP2.1 Failover Cluster is Successful
Click on Close

Here you see your SQL Server 2022 CTP2.1 Cluster Instance Running in Failover Cluster Manager.

Here I installed the new Microsoft SQL Server Management Studio (SSMS) version 19 preview 2

Connecting the High Available SQL 2022 CTP2.1 Cluster Resource Instance01.

And you can connect the SQL Instance with Azure Data Studio 😉

With Azure Data Studio you can install marketplace extensions working with your SQL Instance.
Here you find more information about Microsoft Azure Data Studio

+

MVPLAB Serie Cluster Aware Updating – CAU for Windows Server Insider #WindowsServerInsider #MVPBuzz #Winserv

Cluster Aware Updating (CAU)

In my last MVPLAB Serie blogpost, I wrote about setting-up a Microsoft Domain mvplab.local and making a Windows Server Insider Cluster with an iSCSI Target Host Server for Shared iSCSI Storage provisioning. First thing I did was Installing Windows Admin Center for Hybrid IT Management. With WAC we can Manage the Cluster Nodes but also the Cluster, Installing new features via Windows Admin Center like Kubernetes for running Containers and microservices. But first we start with Microsoft Cluster Aware Updating to keep your Cluster up-to-date.

Windows Admin Center Cluster Manager

Installing Cluster Aware Updating

In the following steps you can see how easy it is to install Cluster Aware Updating with Windows Admin Center on your Windows Server Cluster, in my case mvpcl01.mvplab.local

Go to your Windows Server Insider Cluster

In Cluster Manager, go to Updates.
Click on Add Cluster Aware Updating Role

Successfully configured Cluster Aware Updating (CAU)

On both Cluster Nodes is the Update Available.
Click on Install

Click on Install

Look at the status to see what is happening on the Cluster Nodes.

First Cluster Node is done

Both Cluster Nodes are updated successfully.

Here you can read more about Microsoft Cluster Aware Updating

Conclusion

Microsoft Windows Admin Center is the Administrator Management tool to use in your hybrid datacenter. You see how easy it is to configure Cluster Aware Updating (CAU) on your Cluster. When you use Windows Server Core or Azure Stack HCI then Windows Admin Center is really handy instead of command-line tools or PowerShell scripting.  here you can find more information about
Cluster Aware Updating requirements and Best Practices

Here you can JOIN the Windows Admin Center Community Group on LinkedIn

MVPLAB Serie Windows Server Insider Cluster with ISCSI Target Server #WindowsServerInsider #Winserv

mvplab.local Domain

I have made a new MVPLAB with Microsoft Windows Server Insider Preview Build 25158 to install Services and Features for learning but also to give Microsoft feedback about the products. When the MVPLAB domain and Clusters are ready in basic then I can use new Microsoft Azure Hybrid solutions as well, like Azure Arc Kubernetes services and Azure Cloud Defender for Servers and SQL.
Before we start, you need to become a Windows Server Insider so that you can download the newest Windows Server Insider Builds ISO.
Here you get more information for the Windows Server Insider Program registration 

After the free registration you can download the new Microsoft Windows Server Insider Builds here :

While I’m writing a new blogpost, Microsoft published a new Build 25169.
Here you can download the ISO or VHDX file

To Build your Test and innovation LAB with the newest Microsoft technologies, you need a platform to Build on. Of course Microsoft Azure Cloud Services is Awesome to work with and Great to make test environments but I like to make a Azure Hybrid scenario with Azure Cloud and On-premises datacenter services like for example a Microsoft SQL Cluster with Cluster resources / Instances.
So my MVPLAB will be Azure Hybrid and for On-premises I use Windows Server Hyper-V to make virtual servers.

It’s Great when your hardware provider like Dell is Microsoft Azure Stack HCI compliant to build your Hyper Converged Infrastructure in your on-premises datacenter.

Microsoft Azure Stack HCI Solution

When you work with Microsoft Azure and Azure Stack HCI, you really need Windows Admin Center for Hybrid IT Management.
This is a Great Administrator tool for managing your Windows Servers, Clusters, Azure Stack HCI, and Azure VM’s in a Hybrid environment.

Windows Admin Center Cluster Overview

Now that we have everything and Hyper-V is running, we will build the Following Windows Servers with the Insider Preview Build:

• MVPDC01 ( the first domain controller for mvplab.local domain )
• MVPStore01 ( ISCSI Target Host for deploying ISCSI Virtual Disks to my Cluster)
• MVPFS01 ( Cluster Node 01 of Cluster MVPCL01 )
• MVPFS02 ( Cluster Node 02 of Cluster MVPCL01 )

I install all the virtual servers with 50GB local harddisk for OS and start with 4GB of Dynamic Memory and a Nic.
Only the Cluster nodes get two Nics (One for Heartbeat of the Cluster)
This is for my MVPLAB, but for Production environments I always start with 3 Nics ( 1 = Production 2 = Heartbeat 3 = Storage )

In Hyper-V we make a New Virtual Machine with these specifications and we attach the Windows Server Insider Preview Build ISO.
We install Windows Server Insider Preview Build default and after the installation we set the NIC IP-Address on static and gave the Server the name MVPDC01. Then I installed all the Windows Updates, and after that I started Server Manager to install the Active Directory Feature :

Active Directory just follow the wizard and don’t forget to run DCPromo to
build your domain.

Active Directory and DNS is running locally like
mvplab.local

So now is my domain and DNS running in my MVPLAB, but what do I need more first to build a Windows Server Insider Cluster?
We need Shared storage, so we build a Windows Server Insider ISCSI Target Host to provision Shared VHD’s via ISCSI Initiator to the Cluster Nodes.

The Next member Windows Server Insider is MVPStore01.mvplab.local joined in our new domain. Here I installed the iSCSI Host features:

Start Server Manager and the Add Server role :
– iSCSI Target Server
– iSCSI Target Storage Provider

Click on Install

In Hyper-V Settings of the Virtual Machine MVPStore01, I have installed a extra disk of 25GB so that we can use that for iSCSI Target Host which is now running on this Server. Now we can provision storage when the new Windows Server Insider Cluster MVPCL01.mvplab.local is installed with the iSCSI Initiator to get Cluster storage. So now we are first going to build a Windows Server Insider Cluster and after that we will provision the Cluster Storage.

Installing a Windows Server Cluster with Insider preview Build 25158.

I deployed two member servers MVPFS01.mvplab.local and MVPFS02.mvplab.local into the new domain. they have static IP-Address and are working fine with DNS resolving. On both Servers I installed the Feature Failover Clustering

Failover Clustering Installed.

from here we are going to install the new Windows Server Insider Cluster MVPCL01.mvplab.local

Start Failover Cluster Manager.
Create Cluster.

Click on Next

select the two new Cluster Nodes
Click on Next

Select Yes, run configuration validation tests
Click on Next

Click on Next

Run all tests
Click Next

Confirmation
Click Next

Type in the new Cluster name => mvpcl01
IP-Address => 192.168.2.43
Click Next

Confirmation
Click on Next

Creating Cluster….

We now have a Cluster mvpcl01.mvplab.local running, but without storage and without the witness disk. the iSCSI initiator is running on both Cluster nodes, so now we have to provision storage to the Cluster via the iSCSI Target Host MVPStore01.mvplab.local.

iSCSI Storage provisioning to Windows Server Insider Cluster

via the Server Manager of the iSCSI Target host, we are going to create a new iSCSI Virtual Disk for both Cluster Nodes :

Click on New iSCSI Virtual Disk

iSCSI Virtual Disk Name
Click on Next

Type in the Size I’m using 20GB of 24,9 because I need also a Quorum disk for the Cluster.
Select Fixed Size.
Click on Next.

New iSCSI Target
Click on Next

Give the iSCSI Target a Name
Click on Next

Add the Access Servers via iSCSI Initiator
Click on Next

Here you can set Authentication if you want.
Click on Next

Confirmation
Click on Create

the iSCSI Virtual Disk is successfully created.

the iSCSI Target VHD is not connected yet.
Now we connect with iSCSI Initiator from the Cluster Nodes.
The work on iSCSI Taget Host MVPStore01.mvplab.local is Done.

When you start the iSCSI Initiator it will set the services and the firewall settings on the Server.
You have to do this on both Cluster nodes.

First we add the Target portal and that is our iSCSI Taget Host MVPStore01.mvplab.local with
IP-Address 192.168.2.46 with port 3260.
This is under the discovery tab.

Select Targets tab
you see the Target mvpstore01 Inactive.
Select and click on Connect.

If you had Multi-path IO running, you could enable Multipath too.
Click on Ok

The iSCSI Taget Virtual Disk is connected.

On the iSCSI Target Host MVPStore01.mvplab.local is the target now also in Connected status.

You now can now bring the 20GB disk Online via Disk Management and give it a drive letter
for the Cluster.
Then you can add the 20GB disk via Storage of Cluster Manager tool.

 

 

You can make Cluster Shared Volume.

I made a Cluster for a SQL Instance and I made
a 2GB iSCSI Taget VHD for the Witness Disk.

So Now we have Cluster storage running and failovers are working, now we need to configure Quorum witness disk via
Failover Cluster Manager.

Go to more actions on the Cluster.
Configure Cluster Quorum

Click on Next

Select the quorum witness
Click on Next

You can configure your witness on different locations.
I will select our 2GB witness disk on our Cluster

Select the Quorum disk
Click on Next

Confirmation
Click on Next

You have successfully configured the quorum settings for the Cluster
Click on Finish

Witness disk is running.

So my Microsoft Windows Server Insider Cluster is ready for workloads, if you want to you can run a Cluster validation to see
if everything is okay. Now my MVPLAB is ready for the next installation on my Cluster and that is :

Installing the Newest SQL Server 2022 CTP2.1 on my Windows Server Insider Cluster.

But that will be a next Blogpost : Installing SQL Server 2022 CTP2.1 on a Windows Server Cluster 😉
Follow me on Twitter : @Jamesvandenberg

 

Deploying Azure Stack HCI Cluster with Windows Admin Center #WAC #AzureStackHCI #WindowsAdminCenter #Hyperv #AKS

Azure Stack HCI is a Hyper-Converged Infrastructure (HCI) cluster solution that hosts virtualized Windows and Linux workloads and their storage in a hybrid on-premises environment. Azure hybrid services enhance the cluster with capabilities such as cloud-based monitoring, Site Recovery, and VM backups, as well as a central view of all of your Azure Stack HCI deployments in the Azure portal. You can manage the cluster with your existing tools including Windows Admin Center, System Center, and PowerShell.

Azure Stack HCI, version 20H2 is a new operating system now in Public Preview and available for download. It’s intended for on-premises clusters running virtualized workloads, with hybrid-cloud connections built-in. As such, Azure Stack HCI is delivered as an Azure service and billed on an Azure subscription. Azure Stack HCI also now includes the ability to host the Azure Kubernetes Service; for details, see Azure Kubernetes Service on Azure Stack HCI.

Get Started with Azure Stack HCI and Windows Admin Center

Windows Admin Center is a locally deployed, browser-based app for managing Azure Stack HCI. The simplest way to install Windows Admin Center is on a local management PC (desktop mode), although you can also install it on a server (service mode).

If you install Windows Admin Center on a server, tasks that require CredSSP, such as cluster creation and installing updates and extensions, require using an account that’s a member of the Gateway Administrators group on the Windows Admin Center server. For more information, see the first two sections of Configure User Access Control and Permissions.

Before you begin, you have to know that Azure Stack HCI is still in Preview and not for Production usage ready. But I’m installing it in my MVPLAB for testing purpose only and learn all the New Features.

What’s New in Azure Stack HCI

Clusters running Azure Stack HCI, version 20H2 have the following new features as compared to Windows Server 2019-based solutions:

• New capabilities in Windows Admin Center: With the ability to create and update hyper-converged clusters via an intuitive UI, Azure Stack HCI is easier than ever to use.
• Stretched clusters for automatic failover: Multi-site clustering with Storage Replica replication and automatic VM failover provides native disaster recovery and business continuity to clusters that use Storage Spaces Direct.
• Affinity and anti-affinity rules: These can be used similarly to how Azure uses Availability Zones to keep VMs and storage together or apart in clusters with multiple fault domains, such as stretched clusters.
• Azure portal integration: The Azure portal experience for Azure Stack HCI is designed to view all of your Azure Stack HCI clusters across the globe, with new features in development.
• GPU acceleration for high-performance workloads: AI/ML applications can benefit from boosting performance with GPUs.
• BitLocker encryption: You can now use BitLocker to encrypt the contents of data volumes on Azure Stack HCI, helping government and other customers stay compliant with standards such as FIPS 140-2 and HIPAA.
• Improved Storage Spaces Direct volume repair speed: Repair volumes quickly and seamlessly.

In the Following Step-by-Step guide we install Azure Stack HCI Cluster with Windows Admin Center.

 

Click on Add and then Create New Server Cluster.

Choose for Azure Stack HCI.

Here you can also choose for both Azure Stack HCI nodes are in the same Site or you have more Azure Stack HCI Nodes in Two Sites for disaster Recovery and Business Continuity.
In my MVPLAB I have all Azure Stack HCI nodes in One Site. More information about Microsoft Azure Stack HCI Stretching Clusters can be found here.

Prerequisites before you begin with Windows Admin Center wizard for Creating Azure Stack HCI Cluster.

This is what I like about Windows Admin Center, supporting you in all steps and choices for making an Azure Stack HCI Cluster with Storage Spaces Direct.

 

Specify your administrator Account and password and add the Azure Stack HCI Node Servers

Add the Nodes to the Domain.

Install Required Features on the Azure Stack HCI Node Servers

Install Updates on the Azure Stack HCI Node Servers

Here you get options from your hardware vendor
I don’t get this because it’s virtual.

Restart the Azure Stack HCI Node Servers and Click Next Networking

Networking adapters are UP and Running.

When you have Enough Nics in your Azure Stack HCI Node Server, you can choose here for a Teamed Management NIC.
I choose for a single management NIC.
Plan your Azure Stack HCI Node network

Configure your Production and Storage network

Here you can configure different Switches for your workloads.
Windows Admin Center will work with Software Defined Networking (SDN)
I Skipped this in my MVPLAB.

Before creating the Azure Stack HCI Cluster, we have to Validate the Cluster first.

When the Cluster Validation is done, you can download the Cluster Validation report.

Here we give the Cluster a Name and a static IP.
Click Create Cluster.

Microsoft Azure Stack HCI Cluster is created 😉
Click Next for Storage.

Click Next

I Got some small disks Click Next.

Storage is validated and suitable for Storage Spaces Direct.

Storage Spaces Direct is enabled on your Azure Stack HCI Cluster.
Click Next for SDN

Here you can configure the Network Controller for the Azure Stack HCI Cluster

Done your Azure Stack HCI Cluster is made 🙂

Here we have the Dashboard in Windows Admin Center of my Azure Stack HCI Cluster

Management of your Azure Stack HCI Cluster

Managing your Azure Stack HCI Cluster with Windows Admin Center is important, because I have connected WAC with my Azure Subscription I can use Azure Monitor.
From here the Cluster is also connected with my Analytics workspace of Azure Monitor.

Azure Stack HCI Cluster Nodes connected with Azure Monitor.

With Windows Admin Center you can manage the Azure Stack HCI updates with Cluster Aware Updating (CAU) without any downtime for your workloads.

Start Cluster Aware Updating

Click on Install

One Azure Stack HCI Node is waiting and the other is Installing.

Now the other Azure Stack HCI Node is Installing the Update.

Updates Succeeded on both Azure Stack HCI Nodes.

Microsoft Azure Stack HCI Cluster is Running

Create your Virtual Machine on Azure Stack HCI Cluster.

Conclusion

Windows Admin Center supports you all the way for making your Microsoft Azure Stack HCI Cluster in easy steps deployment wizard. Of course you can make also your own PowerShell deployment scripts when you have to make more Azure Stack HCI Clusters for different platforms like Deploying virtual machines or AKS Kubernetes Clusters for Container Applications or a SQL environment.
Here you find more information about PowerShell commands

After deploying Azure Stack HCI Clusters with your own PowerShell Script, you can add the Cluster into Windows Admin Center for IT Management.
The Installation time of the Cluster is really fast. I hope this will give you more inside information about the Preview of Microsoft Azure Stack HCI Cluster and Windows Admin Center better Together!
Next Step is AKS Kubernetes on Azure Stack HCI 😉

Kubernetes Containers on your Azure Stack HCI

Installing and Maintaining #Azure Kubernetes Cluster with Multi Pool Nodes (Preview) for #Linux #Winserv Containers

Install AKS-Preview extension via Azure Cloudshell

NOTE ! This is a Preview blogpost, do not use in production! (only for test environments)

To create an AKS cluster that can use multiple node pools and run Windows Server containers, first enable the WindowsPreview feature flags on your subscription. The WindowsPreview feature also uses multi-node pool clusters and virtual machine scale set to manage the deployment and configuration of the Kubernetes nodes. Register the WindowsPreview feature flag using the az feature register command as shown in the following example:

I Have registered the following Preview Features from the Azure CloudShell :

• az feature register –name WindowsPreview –namespace Microsoft.ContainerService
• az feature register –name MultiAgentpoolPreview –namespace Microsoft.ContainerService
• az feature register –name VMSSPreview –namespace Microsoft.ContainerService

This will take a few minutes and you can check the registration with the following command :

az feature list -o table –query “[?contains(name, ‘Microsoft.ContainerService/WindowsPreview’)].{Name:name,State:properties.state}”

When ready, refresh the registration of the Microsoft.ContainerService resource provider using the az provider register command:

 

Creating Azure Kubernetes Cluster

First you create a Resource Group in the right Azure Region for your AKS Cluster to run:

az group create –name myResourceGroup –location eastus

I created Resource Group KubeCon in location West-Europe.

Creating KubeCluster

With the following CLI command in Azure Cloudshell, I created the Kubernetes Cluster with a single node:

$PASSWORD_WIN=”P@ssw0rd1234″

az aks create –resource-group KubeCon –name KubeCluster –node-count 1 –enable-addons monitoring –kubernetes-version 1.14.0 –generate-ssh-keys –windows-admin-password $PASSWORD_WIN –windows-admin-username azureuser –enable-vmss –network-plugin azure

The Azure Kubernetes Cluster “KubeCluster” is created in the resource group “KubeCon” in a view minutes.

Adding a Windows Pool

Adding a Windows Server Node Pool

By default, an AKS cluster is created with a node pool that can run Linux containers. Use az aks nodepool add command to add an additional node pool that can run Windows Server containers.

az aks nodepool add –resource-group KubeCon –cluster-name KubeCluster –os-type Windows –name pool02 –node-count 1 –kubernetes-version 1.14.0

I added the Windows Server Pool via the Azure Portal.

When this has finished, we have an Azure Kubernetes Cluster with Multi node Pools for Linux and Windows Server Containers :

Pools for Linux and Windows Server Containers

The following will be created in Microsoft Azure too :

VNET, NSG and Virtual Machine Scale Set (VMSS)

Azure Monitor for containers is a feature designed to monitor the performance of container workloads deployed to either Azure Container Instances or managed Kubernetes clusters hosted on Azure Kubernetes Service (AKS). Monitoring your containers is critical, especially when you’re running a production cluster, at scale, with multiple applications.
Azure Monitor for containers gives you performance visibility by collecting memory and processor metrics from controllers, nodes, and containers that are available in Kubernetes through the Metrics API. Container logs are also collected. After you enable monitoring from Kubernetes clusters, these metrics and logs are automatically collected for you through a containerized version of the Log Analytics agent for Linux and stored in your Log Analytics workspace.

Container Insights Monitoring of the Linux Node

Container Insights Monitoring of the Windows Server Node

Here you can read all about Azure Monitoring with Container Insights

Scaling Multi Pool Node AKS Cluster

To Scale your Multi Pool Node AKS Cluster, you need to do this via the Azure Cloudshell CLI.

Here you see the two pools ( Linux and Windows Server)

Scaling up the Windows Server Pool

You can do this with the following command :

az aks nodepool scale –resource-group KubeCon –cluster-name KubeCluster –name pool02 –node-count 2 –no-wait

Scaling

Scaling Succesful after a few minutes

Upgrading Windows Server Pool Instance

When I scaled the Cluster there was a update released by Microsoft.

Windows Server Pool Instances

Just Click on Upgrade

Upgrade is Done 😉

#Microsoft SQL Always-On Cluster vs #SQL Managed Instance in #Azure

SQL Always-On Cluster in Azure

Before we start with building this SQL Always-On Cluster we already have some Azure SDK Components Active in the Azure Subscription to work with:

• Virtual Network VNET-001 is already installed
• Subnet-SQL and Subnet-Domaincontrollers
• Network Security Groups (NSG) with the right rules active
• Two domain controllers
• Azure Keyvault ( for disk Encryption)

We deployed three Virtual Machines in an Availability Set :

• Primary SQL Node VM01
• Secondary SQL Node VM02
• Witness Server

The deployment was with ARM Template :

VM Deployment

Copy and paste the JSON in your template editor like Visual Studio Code for Example or in the Azure Portal Template builder.

Visual Studio Code

Azure Portal Template

Read more how to deploy ARM Templates via Microsoft Azure Portal here

You also can create a Private or Public Repository on GitHub and store your ARM Templates there in a Library.

GitHub Learning Lab
Learn new skills by completing fun, realistic projects in your very own GitHub repository. Get advice and helpful feedback from our friendly Learning Lab bot.

Create a SQL Server 2014 Always On Availability Group in an existing Azure VNET and an existing Active Directory instance via GitHub :

https://github.com/Azure/azure-quickstart-templates/tree/master/sql-server-2014-alwayson-existing-vnet-and-ad

Configure Always On Availability Group in Azure VM manually :

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windows-portal-sql-availability-group-tutorial

Important Tip :

Don’t forget to get the right connectivity between Azure Load Balancer and the SQL Always-On Listener :

## Get the Cluster Resource Information:
Clear-Host
Get-ClusterResource `
| Where-Object {$_.ResourceType.Name -like “IP Address”} `
| Get-ClusterParameter `
| Where-Object {($_.Name -like “Network”) -or ($_.Name -like “Address”) -or ($_.Name -like “ProbePort”) -or ($_.Name -like “SubnetMask”)}

#############################################################

## Set Cluster Parameters:
$ClusterNetworkName = “Cluster Network 1” # the cluster network name (Use Get-ClusterNetwork on Windows Server 2012 of higher to find the name)
$IPResourceName = “IPlistener” # the IP Address resource name
$ListenerILBIP = “10.x.x.x” # the IP Address of the Internal Load Balancer (ILB). This is the static IP address for the load balancer you configured in the Azure portal.
[int]$ListenerProbePort = 80

Import-Module FailoverClusters

Get-ClusterResource $IPResourceName | Set-ClusterParameter -Multiple @{“Address”=”$ListenerILBIP”;”ProbePort”=$ListenerProbePort;”SubnetMask”=”255.255.255.255″;”Network”=”$ClusterNetworkName”;”EnableDhcp”=0}

############################################################

Before you start with your SQL workloads from On-premises Datacenter on Microsoft Azure, have a look if PaaS Azure SQL Managed Instances is something for your Organization with all the benefits.

What is Microsoft Azure SQL Managed Instance?

Managed instance is a new deployment option of Azure SQL Database, providing near 100% compatibility with the latest SQL Server on-premises (Enterprise Edition) Database Engine, providing a native virtual network (VNet) implementation that addresses common security concerns, and a business model favorable for on-premises SQL Server customers. The managed instance deployment model allows existing SQL Server customers to lift and shift their on-premises applications to the cloud with minimal application and database changes. At the same time, the managed instance deployment option preserves all PaaS capabilities (automatic patching and version updates, automated backups, high-availability ), that drastically reduces management overhead and TCO.

Read here more on Microsoft Docs about Azure SQL Services

Conclusion :

When you have a lot of SQL workloads and want to go to Microsoft Azure Cloud Services, analyze your existing workloads well and have a look first at Microsoft Azure SQL Managed Instances. With this Azure PaaS Service, you don’t have to manage the Complete Infrastructure like in a SQL Always-On Cluster (IaaS).

Have a good look at the requirements and Microsoft Data Migration Services can help you out.

SQL Server instance migration to Azure SQL Database managed instance

 

#Microsoft SQL Server 2019 Preview Overview #SQL #SQL2019 #Linux #Containers #MSIgnite

Microsoft SQL Server 2019 Preview

What’s New in Microsoft SQL Server 2019 Preview

• Big Data Clusters
o Deploy a Big Data cluster with SQL and Spark Linux containers on Kubernetes
o Access your big data from HDFS
o Run Advanced analytics and machine learning with Spark
o Use Spark streaming to data to SQL data pools
o Use Azure Data Studio to run Query books that provide a notebook experience

• Database engine
o UTF-8 support
o Resumable online index create allows index create to resume after interruption
o Clustered columnstore online index build and rebuild
o Always Encrypted with secure enclaves
o Intelligent query processing
o Java language programmability extension
o SQL Graph features
o Database scoped configuration setting for online and resumable DDL operations
o Always On Availability Groups – secondary replica connection redirection
o Data discovery and classification – natively built into SQL Server
o Expanded support for persistent memory devices
o Support for columnstore statistics in DBCC CLONEDATABASE
o New options added to sp_estimate_data_compression_savings
o SQL Server Machine Learning Services failover clusters
o Lightweight query profiling infrastructure enabled by default
o New Polybase connectors
o New sys.dm_db_page_info system function returns page information

• SQL Server on Linux
o Replication support
o Support for the Microsoft Distributed Transaction Coordinator (MSDTC)
o Always On Availability Group on Docker containers with Kubernetes
o OpenLDAP support for third-party AD providers
o Machine Learning on Linux
o New container registry
o New RHEL-based container images
o Memory pressure notification

• Master Data Services
o Silverlight controls replaced

• Security
o Certificate management in SQL Server Configuration Manager

• Tools
o SQL Server Management Studio (SSMS) 18.0 (preview)
o Azure Data Studio

Introducing Microsoft SQL Server 2019 Big Data Clusters

SQL Server 2019 big data clusters make it easier for big data sets to be joined to the dimensional data typically stored in the enterprise relational database, enabling people and apps that use SQL Server to query big data more easily. The value of the big data greatly increases when it is not just in the hands of the data scientists and big data engineers but is also included in reports, dashboards, and applications. At the same time, the data scientists can continue to use big data ecosystem tools while also utilizing easy, real-time access to the high-value data in SQL Server because it is all part of one integrated, complete system.

Read the complete Awesome blogpost from Travis Wright about SQL Server 2019 Big Data Cluster here

Starting in SQL Server 2017 with support for Linux and containers, Microsoft has been on a journey of platform and operating system choice. With SQL Server 2019 preview, we are making it easier to adopt SQL Server in containers by enabling new HA scenarios and adding supported Red Hat Enterprise Linux container images. Today we are happy to announce the availability of SQL Server 2019 preview Linux-based container images on Microsoft Container Registry, Red Hat-Certified Container Images, and the SQL Server operator for Kubernetes, which makes it easy to deploy an Availability Group.

SQL Server 2019 preview containers now available

Microsoft Azure Data Studio

Azure Data Studio is a new cross-platform desktop environment for data professionals using the family of on-premises and cloud data platforms on Windows, MacOS, and Linux. Previously released under the preview name SQL Operations Studio, Azure Data Studio offers a modern editor experience with lightning fast IntelliSense, code snippets, source control integration, and an integrated terminal. It is engineered with the data platform user in mind, with built-in charting of query resultsets and customizable dashboards.

Read the Complete Blogpost About Microsoft Azure Data Studio for SQL Server here

SQL Server 2019: Celebrating 25 years of SQL Server Database Engine and the path forward

Awesome work Microsoft SQL Team and Congrats on your 25th Anniversary !

Deep-dive into Cluster OS Rolling Upgrades in Windows Server 2016 #Winserv #Hyperv

Get started with Cluster OS Rolling Upgrade in Windows Server 2016! Download the evaluation version!

Cluster Operating System Rolling Upgrade in Windows Server Technical Preview #Winserv #Hyperv

Cluster Operating System (OS) Rolling Upgrade is a new feature in Windows Server Technical Preview that enables an administrator to upgrade the operating system of the cluster nodes from Windows Server 2012 R2 to Windows Server Technical Preview without stopping the Hyper-V or the Scale-Out File Server workloads. Using this feature, the downtime penalties against Service Level Agreements (SLA) can be avoided.

Cluster OS Rolling Upgrade provides the following benefits:

• Hyper-V virtual machine and Scale-out File Server workloads can be upgraded from Windows Server 2012 R2 to Windows Server Technical Preview without downtime. Other cluster workloads will be unavailable during the time it takes to failover to Windows Server Technical Preview.
• It does not require any additional hardware.
• The cluster does not need to be stopped or restarted.
• A new cluster is not required. In addition, existing cluster objects stored in Active Directory are used.
• The upgrade process is reversible until the customer crosses the “point-of-no-return”, when all cluster nodes are running Windows Server Technical Preview, and when the Update-ClusterFunctionalLevel PowerShell cmdlet is run.
• The cluster can support patching and maintenance operations while running in the mixed-OS mode.
• It supports automation via PowerShell and WMI.
• The ClusterFunctionalLevel property indicates the state of the cluster on Windows Server Technical Preview cluster nodes.

This guide describes the various stages of the Cluster OS Rolling Upgrade process, installation steps, feature limitations and frequently asked questions (FAQs), and is applicable to the following Cluster OS Rolling Upgrade scenarios in Windows Server Technical Preview:

• Hyper-V clusters
• Scale-Out File Server clusters

The following scenarios are not supported in Windows Server Technical Preview:

• Cluster OS Rolling Upgrade of a cluster using storage with the Data Deduplication feature
• Cluster OS Rolling Upgrade of virtual machines with Data Protection Manager (DPM) backups
• Cluster OS Rolling Upgrade of guest clusters using virtual hard disk (.vhdx file) as shared storage

Important
This preview release should not be used in production environments.

Read more about Cluster Operating System Rolling Upgrade in Windows Server Technical Preview here

Cluster OS Rolling Upgrade Process :