MR IT Surgeon

Veeam Replicate to Azure with PowerShell & API. I’ve done a previous post on restoring VMs into azure using PowerShell Here: http://www.mritsurgeon.co.za/2020/02/restoring-multiple-vms-to-azure-part-2.html I wanted to further enhance this with Azure so that a scheduled script would remove older VM and restore newer VM, I additionally wanted there to be a revert option to older version of the VM through a VM snapshot.

Restoring Multiple VMs to Azure: Part 2 PowerShell Hopefully you have read Part 1 of my Azure Multiple VM restores though Veeam GUI. This is a continuation of that post where i share how to achieve the same process but using only PowerShell . I built this script off a base script on this Blog post from a Colleague. Michael Cade is a Global Technologist for Veeam Software. Here is a Link to Michael's  Blog & Here is the Original Post. Prerequisites are the same as Part 1 so please follow the same. To execute the Script, you need to Add VeeamPSSnapin & connect to the backup server holding the required backups. Add -Server “Name of your Veeam Backup Server” mine in this case was “veeam” Next we need to set the required Variables, like the Backups we want to use, the restore point , the Azure accoun t & subscription , the network , storage & VM size we will use during the restore. I’ve made Duplicate lines of Variables for each backup point t

Restoring Multiple VMs to Azure:  Part 1 Use Cases:  Migration: The most obvious use would be for migration, moving your Veeam VM backup (AHV, VMware Hyper-V) or your Physical Server backups (Windows or Linux) off your aging infrastructure to a hyper-scaler like Azure. When considering purchasing new hardware for your data centre the discussion on whether to go cloud is always an interesting one. Azure will provide you with a rental type infrastructure ensuring uptime on the underlying hardware. This is in its definition Infrastructure as A Service IaaS . Dev Ops: Customers that are not ready to move production into Azure IaaS can still consider using Azure as a Development platform, this makes a lot of financial sense. Rent Infrastructure for the limited time period that the company will be testing or developing on application workloads, only pay as you use. Why purchase or keep hardware around just to run development on copies of production for the development

  Nesting Azure Stack Development Kit on a VM (ASDK) This is the post on my new blog started 2020, I wasn't sure what to blog about, so I referred to my most recent project which was testing Azure Stack Development Kit. I don’t have the hardware in a lab to run it, so I was forced to nest ASDK on a VM. I searched & reference a lot of websites/blogs & had to alter more than what was suggested. Some of these references got me 50%-60% of way but I had to scrub logs and resolve issues one at a time and then rerun the installer. So, I’m consolidating that all into this one post hopefully making this a much simpler process, with new versions of ASDK installer files being uploaded & different hypervisors being used this could work 100% or get you most of the way. What i will show is how to check the installer log which will reference the errors on script that you can either # out or edit to satisfy prerequisites.