![\"Photo](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/hsg-1-24-14-1.jpg\" "\\"Photo")
<\/a><\/p>\nKeith Mayer is a senior technical evangelist at Microsoft, and he focuses on the Windows infrastructure, datacenter virtualization, systems management, and the private cloud. Keith has over 20 years of experience as a technical leader of complex IT projects, in diverse roles, including network engineer, IT manager, technical instructor, and consultant. He has consulted and trained thousands of IT professionals worldwide on the design and implementation of enterprise technology solutions.<\/b><\/p>\n
You can find Keith online at http:\/\/KeithMayer.com<\/a>.<\/p>\n Windows Azure Infrastructure Services<\/a> provides the ability to easily provision or migrate storage, virtual machines, and virtual networks to the global Windows Azure cloud platform by using a cost-effective Pay-As-You-Go<\/a> model. In my prior Weekend Scripter posts, Getting Started with Windows Azure and PowerShell<\/a> and Remoting the Cloud with Windows Azure and PowerShell<\/a>, I provided an introduction to using Windows PowerShell for automated provisioning of Windows Azure cloud fabric resources and workloads running inside virtual machines in Windows Azure.<\/p>\n Once you’ve provisioned a few lab virtual machines on Windows Azure, you’ll likely want to create a backup copy of each virtual machine. This is particularly useful in test lab scenarios, so that you can quickly revert virtual machines back to a known state prior to performing a set of tests.<\/p>\n When you are working in the on-premises world, this is typically performed via virtual machine backup, snapshot, or checkpoint capabilities. In Windows Azure, back up and restore of virtual hard disks can be quickly performed in the cloud with the Windows Azure PowerShell Module<\/a> by leveraging the Start-AzureStorageBlobCopy<\/a> cmdlet. However, there’s a bit of work we’ll need to do upfront to capture the information we’ll need for completing this process.<\/p>\n In this post, we’ll step through the process of building a Windows PowerShell script to back up virtual machines in Windows Azure. At the end of this post, I’ve provided a link to the next step, restoring virtual machines in Windows Azure, so that you’ll have the complete end-to-end process.<\/p>\n To back up virtual machines in Windows Azure, we’ll step through the following tasks:<\/p>\n Note<\/b> To learn more about the basics of Windows Azure Infrastructure Services, you might also be interested in the “Early Experts” Cloud Quest<\/a> and our scenario-based Cloud Labs<\/a> step-by-step guides. Both are free online study resources that provide hands-on lab exercises for leveraging Windows Azure and building key IT pro cloud scenarios.<\/p>\n The virtual machine you want to back up and restore can be selected by using the Get-AzureVM<\/a> cmdlet. Running Get-AzureVM<\/b> alone returns a list of virtual machines that are currently provisioned in Windows Azure.<\/p>\n To select a particular virtual machine, you can pass the ServiceName<\/b> <\/i>and Name<\/b> <\/i>values as parameters and set the output to a new Windows PowerShell variable.<\/p>\n Now our selected Windows Azure virtual machine can be referenced by using the variable $vm<\/b> in the remainder of our script.<\/p>\n To capture a valid backup of each virtual hard disk, we also need to temporarily shut down the virtual machine to a state where the virtual machine is not running, but its configuration is kept in a provisioned state. We can accomplish this with the Stop-AzureVM<\/a> cmdlet.<\/p>\n Now that our virtual machine is selected and in the right state, we can proceed to the next step of finding each virtual hard disk we want to back up and restore.<\/p>\n Virtual machines in Windows Azure can be provisioned with two general types of virtual hard disks: operating system disks and data disks. Each virtual machine will have one operating system disk from which it boots and runs the operating system. In addition, each virtual machine can have one or more additional data disks on which program code and data files can be stored. To perform a complete virtual machine backup, we’ll need to locate all of the virtual hard disks that our virtual machine is currently using.<\/p>\n To store the location for the operating system disk, we can use the Get-AzureOSDisk<\/a> cmdlet.<\/p>\n For any virtual hard disk that we want to back up or restore, the two property values in which we’ll be most interested are the DiskName<\/b> and MediaLink<\/b> values, which are shown in the following image. These values provide the information that we’ll need to properly back up and restore each virtual hard disk that is associated with a virtual machine.<\/p>\n To store the location for all data disks, we can use the Get-AzureDataDisk<\/a> cmdlet. Because virtual machines can be provisioned with multiple data disks, this cmdlet returns of a collection of data virtual hard disks.<\/p>\n Prior to performing a backup, we’ll need to make sure that a container exists in our Windows Azure Storage Account to store these backup copies. First, we’ll need to determine the name of our Windows Azure Storage Account. We can do this by leveraging the MediaLink<\/b> <\/i>property of Azure Disks mentioned earlier.<\/p>\n Now that we know the name of our Windows Azure Storage Account, we’ll want to set it as the current storage account for the remainder of our script by using the Set-AzureSubscription<\/a> cmdlet.<\/p>\n Next, we can easily check to see if our desired container location for storing backups already exists inside our storage account, and if not, we can quickly create it by using the New-AzureStorageContainer<\/a> cmdlet.<\/p>\n We can confirm that the new storage container has been created by using the Get-AzureStorageContainer<\/a> cmdlet without parameters.<\/p>\n Now, we’re ready to back up our virtual machine!<\/p>\n To create a backup copy of the operating system disk on our virtual machine, we’ll first set the values for a couple variables that identify the blob and container names for the virtual disk that we want to back up. Then, we’ll use the Start-AzureStorageBlobCopy<\/a> cmdlet to begin the copy process to our previously defined backup container location.<\/p>\n It’s important to note that the copy process performed by the Start-AzureStorageBlobCopy<\/b> cmdlet is asynchronous in nature, and it runs in the background on the Windows Azure platform. To ensure that the copy process has completed before continuing with the next line in a script, we can use the Get-AzureStorageBlobCopyState<\/a> cmdlet to wait until the copy process is finished.<\/p>\n To back up our Windows Azure data disks, we’ll use a similar set of cmdlets, but we’ll run them inside a ForEach<\/b> loop because Windows Azure data disks are returned as a collection.<\/p>\n After the backup process has completed, use the Get-AzureStorageBlob<\/a> cmdlet to confirm that a copy of each virtual hard disk now exists in the backup storage container location.<\/p>\n Our backup process is complete, and we can now restart the Windows Azure virtual machine by using the Start-AzureVM<\/a> cmdlet.<\/p>\n Congratulations! But keep learning!<\/p>\n You’ve completed the process for creating cloud backups of virtual machines in Windows Azure with Windows PowerShell! You can use the cmdlets and snippets in this post to quite easily build an automated approach to capture a backup of each Windows Azure virtual machine in your subscription, perhaps on a nightly basis.<\/p>\n In Part 2 of this series, we’ll walk through the process of restoring virtual machines in Windows Azure from these backups so that you can automate the complete end-to-end backup and restore process.<\/p>\n In addition, you may want to leverage these resources to continue your learning about Windows Azure Infrastructure Services:<\/p>\n Thank you, Keith, for sharing your time and knowledge.<\/p>\n I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n Ed Wilson, Microsoft Scripting Guy<\/b><\/p>\n","protected":false},"excerpt":{"rendered":" Summary: Guest blogger, Keith Mayer, talks about using Windows PowerShell to manage cloud-based backups. Microsoft Scripting Guy, Ed Wilson, is here. Welcome back Keith Mayer as our guest blogger today. This is Part 1 of a two-part series. In Part 2, we’ll restore virtual machines in Windows Azure from these backups. Keith Mayer is a […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[476,56,432,3,45],"class_list":["post-2159","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-azure","tag-guest-blogger","tag-keith-mayer","tag-scripting-guy","tag-windows-powershell"],"acf":[],"blog_post_summary":" Summary: Guest blogger, Keith Mayer, talks about using Windows PowerShell to manage cloud-based backups. Microsoft Scripting Guy, Ed Wilson, is here. Welcome back Keith Mayer as our guest blogger today. This is Part 1 of a two-part series. In Part 2, we’ll restore virtual machines in Windows Azure from these backups. Keith Mayer is a […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/2159","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=2159"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/2159\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=2159"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=2159"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=2159"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/a><\/p>\n\n
Select virtual machine to back up<\/h3>\n
<\/a>
Get-AzureVM cmdlet output<\/strong><\/p>\n<\/a>
Selecting a Windows Azure virtual machine<\/strong><\/p>\n<\/a>
Using Stop-AzureVM with the StayProvisioned parameter<\/strong><\/p>\nIdentify virtual hard disks<\/h3>\n
<\/a>
Locating the virtual machine operating system disk with Get-AzureOSDisk<\/strong><\/p>\n<\/a>
Common property values for a Windows Azure virtual hard disk<\/strong><\/p>\n<\/a>
Storing location for data disks with the Get-AzureDataDisk cmdlet<\/strong><\/p>\nCreate cloud storage container for storing backups<\/h3>\n
<\/a>
Determining the name of Windows Azure Storage Account by using MediaLink property<\/strong><\/p>\n<\/a>
Setting the current storage account<\/strong><\/p>\n<\/a>
Creating a new Windows Azure storage container<\/strong><\/p>\n<\/a>
Confirming creation of storage container with Get-AzureStorageContainer cmdlet<\/strong><\/p>\nBack up virtual machines in Windows Azure to cloud storage<\/h3>\n
<\/a>
Using Start-AzureStorageBlobCopy cmdlet to back up virtual hard disk<\/strong><\/p>\n<\/a>
Using Get-AzureStorageBlobCopyState to confirm that the copy process completed<\/strong><\/p>\n<\/a>
Back up data disks by using ForEach loop<\/strong><\/p>\n<\/a>
Using Get-AzureStorageBlob to confirm backup copies<\/strong><\/p>\n<\/a>
Using Start-AzureVM to restart virtual machine after back up is complete<\/strong><\/p>\n\n
\n