Azure Backup is the Azure-based service you can use to back up (or protect) and restore your data in the Microsoft cloud. Azure Backup replaces your existing on-premises or off-site backup solution with a cloud-based solution that is reliable, secure, and cost-competitive. Azure Backup offers multiple components that you download and deploy on the appropriate computer, server, or in the cloud. The component, or agent, that you deploy depends on what you want to protect. All Azure Backup components (no matter whether you’re protecting data on-premises or in the cloud) can be used to back up data to a Backup vault in Azure.
See the Azure Backup components table
Azure Backup’s cloud-first approach and why it matters by Principal Group Program Manager, Azure BackupShreesh Dubey
Cloud-first value propositions
These are the benefits customers would likely expect in backup scenarios as they augment the public cloud to their IT infrastructure:
Consistent management experience for Hybrid IT: Companies will be in a hybrid model where in addition to the on-premise IT, they will have a cloud foot print that has IaaS (“lift-and-shift applications”) that possibly extends to PaaS (“born-in-the-cloud applications”) and SaaS (O365). It is important to have a consistent experience to manage backups across the IT assets in this hybrid model.
Agility: Business owners are seeking more agility offered by the public cloud where they can deploy solutions from the marketplace to meet their business needs. From a backup perspective, an application admin should be able to sign up for backup and do self-service restores without having to go through a central IT process to provision compute/storage in the cloud to enable backup.
Reduce TCO (Total Cost of Ownership): A subscription based model (PAYG) is an obvious benefit of the public cloud, but it is also important to consider overall IT cost for backup. For example, if you need to deploy additional infrastructure in the cloud (compute and storage) for backups your overall costs would be higher.
Freedom from infrastructure: This is one of the fundamental benefits companies seek when they move their IT to the cloud and since backup has a significant infrastructure footprint in on-premises IT (storage, compute, licenses, etc), an infrastructure-less backup solution would be a natural expectation for customers
Any developer or IT professional can be productive with Azure. The integrated tools, pre-built templates and managed services make it easier to build and manage enterprise, mobile, Web and Internet of Things (IoT) apps faster, using skills you already have and technologies you already know. Microsoft is also the only vendor positioned as a Leader across Gartner’s Magic Quadrants for Cloud Infrastructure as a Service, Application Platform as a Service, and Cloud Storage Services for the second consecutive year.
In today’s world it is all about mobility and Applications. On your work, at School, at Home, and even when you do Sport like biking or running. I think that’s why
Microsoft makes One Platform Windows 10 to get the best experience with Applications on every Device.
Making your own websites is really Easy with Microsoft Azure and is Cool to work with.
To run all those Web Apps in the Cloud you need Storage and capacity to store your data save in the Cloud with high security policies.
Microsoft Azure has all kind of diffenrent Storage in the Cloud for your data.
Microsoft Azure Data and Storage
Learn about Azure Storage, and how to create applications using Azure blobs, tables, queues, and files :
Of course when you have a lot of data, you like to analyze it for the business and make good Reports or Dashboard to
make the right decisions. Microsoft Azure Cloud Services has Data and Analytics :
Microsoft Azure Data and Analytics
Learn to create Hadoop clusters, process big data, develop solutions using streaming or historical data, and analyze the results :
When you are still working on an On-premises datacenter only, Microsoft makes it’s easy to transform your datacenter into Hybrid Cloud Scenarios.
You can think of a Twin Datacenter for your Core Business Applications, or save your longtime protection data into an Azure Backup Vault.
Microsoft Azure Hybrid Integration
Learn how to integrate the enterprise and the cloud with BizTalk Services :
To make those Microsoft Solutions Available for everyone, you need Developers and Developer Environments.
Microsoft Azure Developer Services
Learn how to detect issues, diagnose crashes and track usage of your mobile apps, and web apps hosted anywhere: on Azure or on your own IIS or J2EE servers :
This is a super simple “getting started” experience for deploying single and multi-container Dockerized applications utilizing Azure Resource Manager templates and the new Docker Extension
This Blogpost is about Deploying Microsoft Azure Site Recovery Manager to replicate and failover virtual machines on Hyper-V host servers that are located in System Center Virtual Machine Manager (VMM) clouds. It’s not Microsoft Hyper-V alone protection anymore, they have managed to protect VMWare and Physical Servers on Primary Sites too.
SCVMM 2012 R2 to Azure
Microsoft Azure Site Recovery Quick Start
On April 30, 2015. You could choose from the Quick Start page the following configurations :
Between an On-Premises VMM Site and Azure
Between Two On-Premises VMM Sites
Between an On-Premises Hyper-V Site and Azure
Between Two On-Premises VMWare Sites
Between Two On-Premises VMM Sites with SAN Array Replication.
When Your Microsoft Azure Subscription is Active and you have created a Storagepool in Azure, you can follow the next step.
Quick Create a Site Recovery Vault by giving it a Name and choose a Region
This is my Azure Site Recovery called HybridCloud
From here start the Quick Start Page of your Azure Site Recovery Vault by clicking on
I Choose for SCVMM to Azure
Just Click on the links for a Registration key and the SCVMM Provider Software
Click on Install
Set the Proxy settings when you behind an Proxy Server
Browse to your downloaded Registration key of the Azure Site Recovery
Give the directory path for the Certificate
Registration software in SCVMM is completed
Here you see your SCVMM Server in the Azure Site Recovery Vault
In System Center 2012 R2 Virtual Machine Manager RU6 is ASR also Active
Next Step is to install the ASR Agent on Hyper-V :
Choose your Cache Location with Enough Storage
Set your Proxy Settings and Click Next
Click Install
Click on Proceed to Registration
Next Step in Virtual Machine Manager
If you don’t have your Virtual Machines in a SCVMM Cloud, you have to make Cloud(s) with Virtual Machine Manger.
The next step is to make a Cloud if you don’t have any.
Give your Private Cloud a Name and Mark the Checkbox for ASR Protection
Select your Resources
Choose the right network
Click Next
Choose the right Storage pool(s) for this Cloud
Check the Summary and make your Private Cloud with SCVMM
When you have a VM in your Cloud Click on Manage Protection
Select the Replication settings
The SCVMM Cloud is in the Azure Recovery Site
Configure now the network Maps
Map the Azure VNET to your Local Network
When you protect the Virtual Machine you will see this in Azure :
And after this Hyper-V Replica to Azure is replicating the VM to the Microsoft Cloud :
When the Sync is completed we can make an Azure Recovery Plan :
In my Next blogpost I will write more about Microsoft Azure Recovery Plans.
Azure Site Recovery contributes to your business continuity and disaster recovery (BCDR) strategy by orchestrating replication, failover and recovery of virtual machines and physical servers. Read about possible deployment scenarios in the Azure Site Recovery overview.
This walkthrough describes how to deploy Site Recovery to:
Protect on-premises VMware virtual machines to Azure
Protect on-premises physical Windows and Linux servers to Azure
Business advantages include:
Protection of physical Windows or Linux servers.
Simple replication, failover, and recovery using the Azure Site Recovery portal.
Data replication over the Internet, a site-to-site VPN connection, or over Azure ExpressRoute.
Failback (restore) from Azure to an on-premises VMware infrastructure.
Simplified discovery of VMware virtual machines.
Multi VM consistency so that virtual machines and physical servers running specific workloads can be recovered together to a consistent data point.
Recovery plans for simplified failover and recovery of workloads tiered over multiple machines.
Deployment components
On-premises machines—Your on-premises site has machines that you want to protect. These are either virtual machines running on a VMware hypervisor, or physical servers running Windows or Linux.
On-premises process server—Protected machines send replication data to the on-premises process server. The process server performs a number of actions on that data. It optimizes it before sending it on to the master target server in Azure. It has a disk-based cache to cache replication data that it receives. It also handles push installation of the Mobility Service which must be installed on each virtual machine or physical server you want to protect, and performs automatic discovery of VMware vCenter servers. The process server is a virtual or physical server running Windows Server 2012 R2. We recommend it’s placed on the same network and LAN segment as the machines that you want to protect, but it can run on a different network as long as protected machines have L3 network visibility to it. During deploy you’ll set up the process server and register it to the configuration server.
Azure Site Recovery vault—The vault coordinates and orchestrates data replica, failover, and recovery between your on-premises site and Azure.
Azure configuration server—The configuration server coordinates communication between protected machines, the process server, and master target servers in Azure. It sets up replication and coordinates recovery in Azure when failover occurs. The configuration server runs on an Azure Standard A3 virtual machine in your Azure subscription. During deployment you’ll set up the server and register it to the Azure Site Recovery vault.
Master target server—The master target server in Azure holds replicated data from your protected machines using attached VHDs created on blob storage in your Azure storage account. You deploy it as an Azure virtual machine as a Windows server based on a Windows Server 2012 R2 gallery image (to protect Windows machines) or as a Linux server based on a OpenLogic CentOS 6.6 gallery image (to protect Linux machines). Two sizing options are available – standard A3 and standard D14. The server is connected to the same Azure network as the configuration server. During deployment you’ll create the server and register it to the configuration server.
Mobility service—You install the Mobility service on each VMware virtual machine or Windows/Linux physical server that you want to protect. The service sends replication data to the process server, which in turn sends it to the master target server in Azure. The process server can automatically install the Mobility service on protected machines, or you can deploy the service manually using your internal software deployment process.
Data communication and replication channel—There are a couple of options. Note that neither option requires you to open any inbound network ports on protected machines. All network communication is initiated from the on-premises site.
Over the Internet—Communicates and replicates data from protected on-premises servers and Azure over a secure public internet connection. This is the default option.
VPN/ExpressRoute—Communicates and replicates data between on-premises servers and Azure over a VPN connection. You’ll need to set up a site-to-site VPN or an ExpressRoute connection between the on-premises site and your Azure network.
