If there is free booze and Virtualization; I'm there!
Tag Archives: Azure
March 17, 2017Posted by on
One big challenge that I came across when starting to use Microsoft Azure & AWS is how do I connect my home lab to a VM/instance running in the cloud?
I have multiple VMs in my lab that need to communicate with the cloud VM, yet my home router doesn’t allow me to create a VPN bridge. Neither does it allow me to do any port forwarding. If I was using an application that supports direct connectivity to Azure or AWS this isn’t a problem. However, in my case, I have Zerto Virtual Replication 5.0 which requires pre-existing connectivity to be established. So how did I workaround this issue? Watch the video to find out or keep on reading!
February 16, 2017Posted by on
When planning DR or migrations from VMware vSphere to Microsoft Azure, one very important task is to configure the appropriate VM/instance sizing to match your current VM settings. This needs to be done in advance for the following key reasons:
- Ensure adequate performance of the VM when running in Azure
- Select the VM size that supports the number of vNICS and vDisks required
- Perform a cost analysis of VM runtime and storage costs
In ZVR 5.0 selecting the Azure VM size is very easy in the GUI:
But what this doesn’t do is tell you exactly which one to pick and neither does it tell you how much it is going to cost!
So how are you going to select the correct instance size and calculate the cost for all your VMware VMs? That sounds like a manual and tedious task that thousands of people are going to have to tackle over the next few years. Of course, you already know I have something that is going to help you otherwise you wouldn’t be reading this far!
February 2, 2017Posted by on
When replicating to Microsoft Azure using Zerto Virtual Replication 5.0 (or even Azure Site Recovery) the protected vDisks cannot be larger than 1TB due to the maximum page disk size being limited to 1TB by Microsoft. It’s rumored they are planning on increasing this to 8TB later this year, but in the meantime how do you work around this problem?
The good news is that there is a solution! On the protected VM you need to configure multiple sub-1TB disks. Don’t use 1TB exactly as the disk size, as this equates to 1024GB in a vSphere environment which is above the Azure page disk limit. Instead use a value of say 990GB to stay under the limit, but with a decent amount of space. Here you can see I’ve created 2 x 990GB VMDKs for my VM: