There are new Virtual Machines available in Windows Azure.
The following versions of Windows Server are offered in the Windows Azure image gallery: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2. Prices as shown in the table below apply to all versions except Windows Server 2012 R2, which is currently in preview and is being offered for customers to test and experience at Linux rates (see pricing details under the "Linux" tab).
Memory-intensive VMs in Windows Azure provide larger amounts of memory and are optimal for running high-throughput applications such as databases. For more information, visit the Virtual Machines webpage.
Provide optimal set of compute, memory and IO resources for running a vast array of applications. Detailed configuration of the instances is available azurehere.
|Compute Instance Name
||Price Per Hour
|Extra Small (A0)
|Extra Large (A4)
Memory Intensive Instances
Provide larger amounts of memory optimal for running high-throughput applications, such as databases or SharePoint server farms. Detailed configurations of these instances are available here.
|COMPUTE INSTANCE NAME
||PRICE PER HOUR
The Windows Azure Pack delivers Windows Azure technologies for you to run inside your datacenter, enabling you to offer rich, self-service, multi-tenant services that are consistent with Windows Azure.
The Microsoft Cloud OS: One Consistent Platform
The Cloud OS is Microsoft’s vision of a consistent, modern platform for the world’s apps running across multiple clouds; enterprise datacenters, hosting service provider datacenters and Windows Azure. The Windows Azure Pack helps to deliver on this vision by bringing consistent Windows Azure experiences and services to enterprise and hosting service provider datacenters with existing investments in System Center and Windows Server.
Consistent with Windows Azure Web Sites, this service helps provide a high-density, scalable shared web hosting platform for ASP.NET, PHP and Node.js web applications. It includes a customizable web application gallery of popular open source web applications and integration with source control systems for custom-developed web sites and applications.
Consistent with Windows Azure Virtual Machines, this service helps provide Infrastructure-as-a-Service (IaaS) capabilities for Windows and Linux virtual machines (VMs). It includes a VM template gallery, scaling options and virtual networking capabilities.
Consistent with Windows Azure Service Bus, this service helps provide reliable messaging services between distributed applications. It includes queued and topic-based publish/subscribe capabilities.
Automation and extensibility
The Windows Azure Pack also includes capabilities for automation and integrating additional custom services into the services framework, including a runbook editor and execution environment.
Get started with Windows Azure Pack
Windows Server 2012 Hyper-V Role introduces a new capability, Hyper-V Replica, as a built-in replication mechanism at a virtual machine (VM) level. Hyper-V Replica can asynchronously replicate a selected VM running at a primary site to a designated replica site across LAN/WAN
there is a great guide for you LAB on this site http://blogs.technet.com/b/yungchou/archive/2013/03/24/hyper-v-replica-broker-explained.aspx
Hyper-V Replica Cluster
To Deploy a Hyper-v failover cluster as a replica site, must use Failover Cluster Manager to perform all Hyper-V Replica configurations and management. And first create a Hyper-V Replica Broker role.
In this case I have two clusters left and right. first go to the FCM and add a role
A Hyper-V Replica Broker is the focal point in this case. It queries the associated cluster database to realize which node is the correct one to redirect VM specific events such as Live Migration requests in a replica cluster.
Windows Active Directory domain is not a requirement for Hyper-V Replica which can also be implemented between workgroups and untrusted domains with a certificate-based authentication. Active Directory is however a requirement if involving a Hyper-v host which is part of a failover cluster, and in such case all Hyper-V hosts of a failover cluster must be in the same Active Directory domain with security enforced at the cluster level. I see sometimes that the broker creations is failing. The resource will not come online.
So During the creation of the cluster resource you will need a Name ( netbios ) and a IP. that is all. But remember as all cluster resources the cluster will create the items and not you Mister Admin. Just make sure Your DNS and cluster resource can create Items.
If you are not sure about this check my old blog post http://robertsmit.wordpress.com/2012/06/26/cluster-network-name-resource-failed-to-create-its-associated-computer-object-in-domain/
Now that my Resource is created and it is in my cluster In both Cluster I want to do Cross Replication
If you know Hyper-v then you would do the settings in the hyper-v settings but as you can see all the options are grayed out.
Go to the Cluster manager and right click on the broker select replication settings.
Same menu and configurable.
First enable the replica server in the first case I use Kerberos ( the easy one )
So don’t check the certificate based box.
here you can do give any server access to this replica easy to do and quick just fill in the path where the VM files need to be stored.
the other option is give only server that I want access. Well in my case I also used a * not that smart well now Only server in my domain can replicate and not every server. If you want to do a point to point connection just fill in the FQDN of the server.
once you have filled in the entry you can’t change the name only the storage path. Well that is fine for now.
Again we add the Resource this time a Virtual machine. Just make sure there is a VM in the Hyper-v
What we do here is make the VM high available and yes you could also replicate the VM right from the Hyper-v console.
but that does not make the VM High Available.
Selecting the VM Now we can start the machine and the VM is HA
We have the broker in place and a VM it is time to replicate.
Don’t use the broker on the current cluster you can’t replicate to your own cluster
All you have to know is the name of your cluster where the VM is placed
So I use the name of the cluster and see if it works, The wizard does see that there is a other broker in the left01 cluster and ask me to change that YES click on update
again Here can I choose Kerberos or certificate Rememeber I checked both boxes on the broker cluster resource If I made a choice there I could no choose here.
I go for……Kerberos
Check what VM disk are needed to replicate If you have a disk that holds stuff that si not needed for replications then unselect the disk here.
You can create multiple recovery points or just one and change the time currently you can set this from 1 hour to 12 hours. It is a wish to get this sooner.
and how to copy the stuff , over the network or with media. and the time to start.
I take the right now option
and If you want to change the settings just go to the settings of the VM and change it
In the Cluster or in the Hyper-v console you can see the status easy quick and fast replication.
In my next blog post I will do the same with a Certificate and you need extra steps for this.