Once you’ve setup Azure Backup to protect your Azure Virtual Machine (see this guide for more info), the process to restore it is quite simple. I recommend running test restores on a regular schedule to make sure it’s working correctly.
To restore an instance of your Azure Virtual Machine follow this quick guide.
Click to open the backup vault you created for the virtual machine.
Click the “Protected items” tab across the top.
Click “Restore” down the bottom to restore the selected virtual machine.
Select a recovery point and click next.
Fill out the restore instance details. You will need to give it a unique name, but make sure you select the appropriate cloud service, storage account, and virtual network if you’re following this in a disaster recovery scenario.
Click the tick in the bottom right to start the restore process
Once the restore is completed you can download the new RDP connect file and test.
https://gcits.com/wp-content/uploads/gcit-logo-300x138.png00Elliot Munrohttps://gcits.com/wp-content/uploads/gcit-logo-300x138.pngElliot Munro2015-12-07 08:14:322015-12-07 08:21:25How to Restore an Azure Virtual Machine from Backup
If you’re running Azure Virtual Machines in production, you’ll probably want to protect them with Azure Backup. The good news is Azure provides a simple way to protect an entire virtual machine, so you can easily restore it if things go wrong.
Protecting Virtual Machine instances differs from the typical Azure Backup client that is usually installed on client PCs and On-premises servers.
Here’s how to set Azure Backup for an Azure Virtual Machine:
We use Microsoft’s AzCopy to move large amounts of data from external sources into Microsoft Azure Storage.
The typical scenario for us is a customer who is moving onto an Azure Virtual Machine, and wants their data stored on that machine.
AzCopy is a versatile command line utility that allows you to move files from another PC or Server into Azure Storage, and then into your Azure virtual machine.
When migrating data to an Azure VM, the solution looks like this:
To get started, you need to install AzCopy from here.
Next, create an Azure Storage Account. You can do this in either the old portal or the new portal.
Once you’ve created a storage account, you’ll need to create a storage container. Here is a quick guide for the old portal and the new portal.
Now that you’ve installed AzCopy, created a storage account and a container, you can put together your AzCopy commands. Typically you’ll create two commands, one that uploads your data into Azure Storage, and the other downloads your data from Azure Storage into your Azure Virtual Machine.
Here’s an example that will move local data from E:\NAS into Azure Storage, and then download it to E:\NAS on the destination virtual machine:
These commands will also create a log file under C:\temp\NASDrive.log
Running the AzCopy commands
Open Command Prompt and navigate to the location where AzCopy was installed. Typically this is under “C:\Program Files (x86)\Microsoft SDKs\Azure\AzCopy”
Paste in your first command and run it to start the upload. In the meantime, you can install AzCopy on the destination server.
Once the upload is complete, go to the destination server and run the second command to download the data from Azure Blob Storage.
If you experience errors
Occasionally you may experience errors in the AzCopy transfer (usually the upload), where certain files will fail. The solution for this is usually to append the /NC: parameter and run the command again. The /NC: parameter limits the number of concurrent connections to Azure storage. I usually set it to /NC:5, where 5 is the maximum number of concurrent files that will be uploaded. The upper limit of concurrent connections is 512.
Updated command for uploading to Azure Blob Storage
If you’re rerunning the command, you will be asked whether you want to skip files that already exist. Choose to skip All.
Here’s the results of the second transfer. You may notice that the number of files transferred in this image is different to the number of files that failed in the previous image. In this case, we removed some unnecessary files before restarting the upload.
Here’s how to create an Azure Storage Account Container in the old Microsoft Azure portal at https://manage.windowsazure.com, assuming you already have an Azure subscription and existing Azure Storage account.
https://gcits.com/wp-content/uploads/gcit-logo-300x138.png00Elliot Munrohttps://gcits.com/wp-content/uploads/gcit-logo-300x138.pngElliot Munro2015-12-04 09:40:262015-12-04 09:40:46How to create an Azure Storage Container in the old portal
Create the new container by clicking ‘+ Container’ then choosing a Name and Access type for it:
You can now refer to this container from other services using https://<yourstorageaccountname>.blob.core.windows.net/<yourcontainername>
Depending on the Access type you chose, you may need your storage account name and primary key. See the end of this guide for how to retrieve these.
https://gcits.com/wp-content/uploads/gcit-logo-300x138.png00Elliot Munrohttps://gcits.com/wp-content/uploads/gcit-logo-300x138.pngElliot Munro2015-12-04 09:27:222015-12-04 09:41:16How to create an Azure Storage Container in the new portal
This will be the storage account name that you’ll use to access your storage.
Choose a pricing tier.
This is the replication level of your storage across Azure’s physical data centre locations. Different levels of replication offer greater redundancy in case of a datacentre outage.
Choose a Resource Group,
This groups your related services together in Azure. If you don’t have any other services running yet, click Create a new resource group
Choose the subscription
This will add the storage account under the chosen subscription, you may only have one.
Choose the location of the data
This is the physical location of the datacentres that will hold your storage account. If you’ve chosen Geo Replication, your data will also be replicated outside of this location.
Choose whether you want to use Diagnostics
Diagnostics will disable the regular monitoring charts and alerts for your storage resource, though will send diagnostic data into a storage account for your own monitoring.
Now, click Create.
Wait a few moments for your storage account to be created. Once completed, you can open your brand new Azure storage account!
To make use of this Storage account, click ‘Keys‘ on the settings blade to retrieve the storage account name and primary access key.
https://gcits.com/wp-content/uploads/gcit-logo-300x138.png00Elliot Munrohttps://gcits.com/wp-content/uploads/gcit-logo-300x138.pngElliot Munro2015-12-04 08:59:492015-12-04 09:35:39How to create an Azure Storage Account in the new portal
Click Quick Create, then choose a name for the storage account.
Choose the location you want your data to be stored, make it close to you or your other Azure resources.
Choose the Azure Subscription you want the Storage Account associated with.
Choose the replication level for your storage, this will affect pricing, though different levels of replication offer greater redundancy in case of a datacentre outage.
Click Create Storage Account.
Your storage account will show as ‘Creating’ in the storage window.Wait for it to change to Online
Once it’s created you can open it up. You now have a new Azure Storage account! Click Manage Access Keys at the bottom of the page to retrieve the Storage account keys. You’ll usually only need the Storage account name and Primary Key to make use of your storage account.
https://gcits.com/wp-content/uploads/gcit-logo-300x138.png00Elliot Munrohttps://gcits.com/wp-content/uploads/gcit-logo-300x138.pngElliot Munro2015-12-04 08:43:052015-12-04 10:37:57How to create an Azure Storage Account in the old portal
We may request cookies to be set on your device. We use cookies to let us know when you visit our websites, how you interact with us, to enrich your user experience, and to customize your relationship with our website.
Click on the different category headings to find out more. You can also change some of your preferences. Note that blocking some types of cookies may impact your experience on our websites and the services we are able to offer.
Essential Website Cookies
These cookies are strictly necessary to provide you with services available through our website and to use some of its features.
Because these cookies are strictly necessary to deliver the website, refuseing them will have impact how our site functions. You always can block or delete cookies by changing your browser settings and force blocking all cookies on this website. But this will always prompt you to accept/refuse cookies when revisiting our site.
We fully respect if you want to refuse cookies but to avoid asking you again and again kindly allow us to store a cookie for that. You are free to opt out any time or opt in for other cookies to get a better experience. If you refuse cookies we will remove all set cookies in our domain.
We provide you with a list of stored cookies on your computer in our domain so you can check what we stored. Due to security reasons we are not able to show or modify cookies from other domains. You can check these in your browser security settings.
Google Analytics Cookies
These cookies collect information that is used either in aggregate form to help us understand how our website is being used or how effective our marketing campaigns are, or to help us customize our website and application for you in order to enhance your experience.
If you do not want that we track your visit to our site you can disable tracking in your browser here:
Other external services
We also use different external services like Google Webfonts, Google Maps, and external Video providers. Since these providers may collect personal data like your IP address we allow you to block them here. Please be aware that this might heavily reduce the functionality and appearance of our site. Changes will take effect once you reload the page.
Google Webfont Settings:
Google Map Settings:
Google reCaptcha Settings:
Vimeo and Youtube video embeds:
Other cookies
The following cookies are also needed - You can choose if you want to allow them: