mountainss Cloud and Datacenter Management Blog

Microsoft SystemCenter blogsite about virtualization on-premises and Cloud

Leave a comment

#HybridCloud with Microsoft Azure Virtual Networks Overview #sysctr #Azure #SCVMM #SDN

Connecting an Azure virtual network to another Azure virtual network is very similar to connecting a virtual network to an on-premises site location. Both connectivity types use a virtual network gateway to provide a secure tunnel using IPsec/IKE. The VNets you connect can be in different subscriptions and different regions. You can even combine VNet to VNet communication with multi-site configurations. This lets you establish network topologies that combine cross-premises connectivity with inter-virtual network connectivity, as shown in the diagram below:


What can I do with Vnet to Vnet connectivity ?

Cross region geo-redundancy and geo-presence

  • You can set up your own geo-replication or synchronization with secure connectivity without going over internet-facing endpoints.
  • With Azure Load Balancer and Microsoft or third party clustering technology, you can setup highly available workload with geo-redundancy across multiple Azure regions. One important example is to setup SQL Always On with Availability Groups spreading across multiple Azure regions.

Regional multi-tier applications with strong isolation boundary

  • Within the same region, you can setup multi-tier applications with multiple virtual networks connected together with strong isolation and secure inter-tier communication.

Cross subscription, inter-organization communication in Azure

  • If you have multiple Azure subscriptions, you can now connect workloads from different subscriptions together securely between virtual networks.
  • For enterprises or service providers, it is now possible to enable cross organization communication with secure VPN technology within Azure.

Here you can find all the information about Vnet to Vnet in Microsoft Azure

If you’ve already created a design plan for your virtual network, the following how-to guidance will help you configure specific settings. Keep in mind that properly designing your virtual network to support your environment is critical. Many settings cannot be changed once your virtual network is in use. If you haven’t yet made design decisions regarding your virtual network, please see Virtual Network Overview.

  • Configure a Cloud-Only Virtual Network in the Management Portal
  • Configure a Site-to-Site VPN in the Management Portal
  • Configure a Site-to-Site VPN using Windows Server 2012 Routing and Remote Access Service (RRAS)
  • Configure a Point-to-Site VPN in the Management Portal
  • Configure a Multi-Site VPN
  • Configure VNet to VNet Connectivity
  • Configure a Virtual Network Gateway in the Management Portal
  • Change a Virtual Network Gateway Routing Type
  • Create an Affinity Group in the Management Portal
  • Configure a Virtual Network Using a Network Configuration File
  • Export Virtual Network Settings to a Network Configuration File
  • Import a Network Configuration File
  • Deleting a Virtual Network
  • View and Edit Virtual Network Properties
  • Add or Remove DNS Servers for a Virtual Network
  • Configure a Static Internal IP Address (DIP) for a VM
  • Move a VM or Role Instance to a Different Subnet

Here you find the Microsoft Azure Virtual Networks Configuration Tasks

HybridCloud Networking


Leave a comment

System Center Summer Night “The MasterChef edition” – 26 juni 2014 #sysctr #Hyperv #Azure

SCUG.4014_Summer_Night_logo_2014System Center Summer Night “The MasterChef edition” – 26 juni 2014
Laat je in één middag en avond bijpraten wat nieuw is op het gebied van Azure, Hyper-V & System Center!

Ook dit jaar slaan de en de System Center User Group de handen ineen en organiseren zij gezamenlijk een community event de “System Center Summer Night”. Een mooie kans om in een paar uur helemaal bijgepraat te worden door (internationale) topsprekers en MVP’s!

Momenteel werken wij aan de laatste details van het programma en deze zal de komende dagen concreter gemaakt worden. Het voorlopige programma willen we je niet onthouden en ziet er als volgt uit:

•15:00 – 16:15 uur: How many System Center fits on one grill by Ronny de Jong / James van den Berg [MVP] / Helmer Zandbergen / Marc van Eijk [MVP] / Dieter Wijckmans [MVP]
•16:15 – 17:30 uur: How Service Manager can do everything you need – a best-of-the-best Swiss cheese selection by Marcel Zehner [MVP]
•17:30 – 17:45 uur: Break
•17:45 – 19:00 uur: Light up the fire on your Hyper-V by Hans Vredevoort [MVP] & Peter Noorderijk
•19:00 – 20:15 uur: Become a Masterchef on Microsoft Azure Automation by Maarten Goet [MVP]
•20.15 uur: BBQ time

Ter afsluiting wordt aan het eind van het programma de BBQ ontstoken! Onder het genot van een hapje en een drankje biedt dit gelegenheid om de sprekers, MVP’s en experts vragen te stellen die tijdens de sessies niet aan bod zijn gekomen. Tevens wordt er onder de bezoekers van de Summer Night een kaartje verloot voor de System Center Universe in Basel (Zwitserland).

Multatulilaan 12
4103 NM Culemborg

Voor dit unieke event kun je hier inschrijven. Om dit event mogelijk te maken vragen wij je om een kleine bijdrage van EUR 12,50. Schrijf je dus nu direct in, de plaatsen zijn beperkt!

System Center User GroupSCUG Website

Leave a comment

#SQL 2014 Guest Cluster with Shared VHDX on #Hyperv 2012 R2 Cluster for #WAPack

Our configuration and requirements before we begin the Guest SQL 2014 Cluster with Shared VHDX on a Hyper-V Cluster :

  1. Microsoft Hyper-V 2012 R2 Cluster is running with Cluster Shared Volumes.
  2. We made Two virtual Machines with Microsoft Windows Server 2012 R2 called SQL01 and SQL02
  3. Networking Two NICS : One on the Production Switch and NIC two on the Heart Beat Switch.

This step shows how to create and then share a virtual hard disk that is in the .vhdx file format. Repeat this step for each shared .vhdx file that you want to add. For example, you may want to add one or more shared disks that will act as data disks, and a separate shared disk that you can designate as the disk witness for the guest failover cluster.

  1. In Failover Cluster Manager, expand the cluster name, and then click Roles.
  2. In the Roles pane, right-click the virtual machine on which you want to add a shared virtual hard disk, and then click Settings.
  3. In the virtual machine settings, under Hardware, click SCSI Controller.
  4. In the details pane, click Hard Drive, and then click Add.
  5. In the Hard Drive details pane, under Virtual hard disk, click New.The New Virtual Hard Disk Wizard opens.
  6. On the Before You Begin page, click Next.
  7. On the Choose Disk Format page, accept the default format of VHDX, and then click Next.
    To share the virtual hard disk, the format must be .vhdx.
  8. On the Choose Disk Type page, select Fixed size or Dynamically expanding, and then click Next.
    A differencing disk is not supported for a shared virtual hard disk.
  9. On the Specify Name and Location page, do the following:
    1. In the Name box, enter the name of the shared virtual hard disk.
    2. In the Location box, enter the path of the shared storage location.For Scenario 1, where the shared storage is a CSV disk, enter the path:C:\ClusterStorage\VolumeX, where C:\ represents the system drive, and X represents the desired CSV volume number.

      For Scenario 2, where the shared storage is an SMB file share, specify the path:

      \\ServerName\ShareName, where ServerName represents the client access point for the Scale-Out File Server, and ShareName represents the name of the SMB file share.

    3. Click Next.
  10. On the Configure Disk page, accept the default option of Create a new blank virtual hard disk, specify the desired size, and then click Next.
  11. On the Completing the New Virtual Hard Disk Wizard page, review the configuration, and then click Finish.
    If the virtual machine is running, do not click Apply in the virtual machine settings before you continue to the next procedure. If you do click Apply on a running virtual machine, you will need to stop the virtual machine or remove and then add the virtual hard disk without clicking Apply.
Advanced Features
  1. In the virtual machine settings, under SCSI Controller, expand the hard drive that you created in the previous procedure.
  2. Click Advanced Features.
  3. In the details pane, select the Enable virtual hard disk sharing check box.
    If the check box appears dimmed and is unavailable, you can do either of the following:

    • Remove and then add the virtual hard disk to the running virtual machine. When you do, ensure that you do not click Apply when the New Virtual Hard Disk Wizard completes. Instead, immediately configure sharing in Advanced Features.
    • Stop the virtual machine, and then select the Enable virtual hard disk sharing check box.
  4. Click Apply, and then click OK.
  5. Add the virtual hard disk to each virtual machine that will use the shared .vhdx file. When you do, repeat this procedure to enable virtual hard disk sharing for each virtual machine that will use the disk.
To share a virtual hard disk by using Windows PowerShell, use the Add-VMHardDiskDrive cmdlet with the –ShareVirtualDisk parameter. You must run this command as an administrator on the Hyper-V host for each virtual machine that will use the shared .vhdx file. For example, the following command adds a shared virtual hard disk (Data1.vhdx) on volume 1 of CSV to a virtual machine that is named VM1.Add-VMHardDiskDrive -VMName VM1 -Path C:\ClusterStorage\Volume1\Data1.vhdx -ShareVirtualDisk The following command adds a shared virtual hard disk (Witness.vhdx) that is stored on an SMB file share (\\Server1\Share1) to a virtual machine that is named VM2.Add-VMHardDiskDrive -VMName VM2 -Path \\Server1\Share1\Witness.vhdx -ShareVirtualDisk

For the Second Guest clusternode you will add the same VHDX files you created on the first Guest clusternode and share them also like on the first clusternode.

Failover Cluster Manager 2

So now we have a Shared Quorum Disk and a Shared Data Disk

The next steps :

  • Bring the disks Online on the first Guest node with Disk Management
  • Install Failover Cluster on both nodes.
  • Make a two node Cluster
  • Install a Microsoft SQL 2014 Guest Cluster.

Disk ManagementShared VHDX disks are Online

Install Microsoft Failover Cluster.

Failover Cluster Manager 3Cluster02 is Online with both Shared VHDX disks for the Guest SQL 2014 Cluster

Install Microsoft SQL 2014 Server for Clustering.

Failover Cluster Manager 3b

Microsoft SQL 2014 Server is installed on the Guest Cluster on top of an Hyper-V 2012 R2 Cluster

Failover Cluster Manager 4

Guest SQL 2014 Cluster is running on Hyper-V 2012 R2.

SQL2014 Studio

So now we are ready for installing Microsoft SPF and Windows Azure Pack for Windows Server 2012 R2 🙂

Leave a comment

#msteched Microsoft TechEd 2014 North America Day 3 Magazine #TechEd #TE14D5 #sysctr #azure

msteched Day3 Magazine

Go to Microsoft TechEd 2014 Day 3 Magazine

Leave a comment

#Microsoft ExpressRoute Technical Overview for Hybrid #Cloud with #Azure #msteched

Express Route Connectivity

Azure ExpressRoute allows you to create private connections between Azure datacenters and infrastructure that’s on your premises or in a co-location environment. With ExpressRoute, you can establish connections to Azure at an ExpressRoute partner co-location facility or directly connect to Azure from your existing WAN network (such as a MPLS VPN provided by a Network Service Provider). In order to configure ExpressRoute, you’ll have to meet the Required prerequisites.

ExpressRoute connections do not go over the public Internet. ExpressRoute connections offer higher security, more reliability, faster speeds and lower latencies than typical connections over the Internet. In some cases, using ExpressRoute connections to transfer data between on-premises and Azure can also yield significant cost benefits. Use ExpressRoute to extend your network to Azure and unlock hybrid IT scenarios. See the ExpressRoute FAQ for more details.

In the diagram, a circuit represents a redundant pair of logical cross connections between your network and Azure configured in Active-Active configuration. The circuit will be partitioned to 2 sub-circuits to isolate traffic.
The following traffic is isolated:

  • Traffic is isolated between your premises and Azure compute services. Azure compute services, namely virtual machines (IaaS) and cloud services (PaaS) deployed within a virtual network are covered.
  • Traffic is isolated between your premises and Azure services hosted on public IP addresses.
    The services that are supported are:

    – Virtual Network, Cloud Services, and Virtual Machines
    – Storage

You can choose to enable one or both types of connectivity through your circuit. You will be able to connect to all supported Azure services through the circuit only if you configure both options mentioned above.
Note the following:

  • If you connect to Azure through a network service provider, the networks service provider takes care of configuring routes to all the services. Work with your network service provider to have routes configured appropriately.
  • If you are connecting to Azure through an exchange provider location, you will need a pair of physical cross-connections and on each of them you will need to configure a pair of BGP sessions per physical cross connection (one public peering and one for private peering) in order to have a highly available link.

Read here more Technical information about Microsoft ExpressRoute for Hybrid Cloud with Microsoft Azure

ExpressRoute Trail

Go to Express Route Trail