Azure
Last week Microsoft announced public preview of VNet Peering feature. After some registration issues, I finally got through to try the feature today. Before diving into configuration, let’s take a look at what VNet Peering actually is, and what scenarios we can use it in. Until now, when we
Azure
This morning I woke up to a nice email from Microsoft Azure. The occasional “pricing and services updates”. From time to time, some really awesome features shows up in these mails, and this one had more than one! VNet Peering This one has been on the drawing board for quite
Azure
In my last post we talked about moving resources between gesource groups in Azure Resource Manager (ARM). But what if you are not yet using Azure Resource Manager, and instead is stuck on Azure Service Management (ASM), or as Microsoft tend to call it: Azure Classic? Well, you have some
Azure
A nice new addition to Azure Resource Manager, is the ability to move Azure VMs, vnets and Storage Accounts between Resource Groups. We’ve had the ability to move resources for a long time, but only recently for the above resources. It’s important to note, that while you can
Azure
***UPDATE – November 22nd 2016*** Microsoft just announced a single-instance SLA of 99,9%. To get this SLA, you need to deploy Premium Storage VMs. Very nice addition to Azure, since we can now get a financially backed SLA for applications that do not run in a multi-instance configuration. Links: https:
Azure
Okay, time to get this series started again. Sorry for the delay, but it turns out moving to a new apartment took a bit more time and energy than expected 🙂 On the other hand, I have fiber at home now, so ASR will be way quicker 😉 This post will focus
Azure
In the 2nd post of this series about Azure Site Recovery (ASR), we will create a new Recovery Services Vaults and go through the different settings we can configure here. Links to other posts in this series: Azure Site Recovery – Part 1 – Introduction Azure Site Recovery – Part 2 – Getting Started
Azure
In this series of posts, I will walk through Azure Site Recovery configuration in a few different scenarios. The series will cover both SMB/enterprise setups, and multi-tenant setups from a Service Provider perspective. This first post will cover the basics to get started with Azure Site Recovery, and from
Azure
I got the following error in my ASR lab a couple of weeks ago, and finally had the time to look into it. It caused my replication to stop working, so had it been a production environment, it would have been critical. Clicking it showed this: Error ID 582 Error
Azure
I’ve done quite a few Azure Backup projects lately, all based on Microsoft Azure Backup Server (MABS) with Azure Resource Manager based vaults – check out this post for more info on Azure Backup. Recently I got an error when installing Azure Backup Server though. Actually it was when registering
Azure
As promised earlier, VM backup is now available in Azure Resource Manager. I’ve been testing it a lot recently, and the experience seems very good! If you want to know more about VM backup and other Azure Backup options, take a look here: https://cloudpuzzles.net/2016/02/understanding-microsoft-azure-backup-solutions/
Azure
I’ve run into this error a couple of times now, when trying to resize Azure VM’s: The current deployment cannot be updated with the API version specified. This is because the current deployment contains multiple virtual IPs created with a newer version of the service management API. So,