{"id":19452,"date":"2017-03-08T09:00:54","date_gmt":"2017-03-08T08:00:54","guid":{"rendered":"http:\/\/nolabnoparty.com\/en\/?p=19452"},"modified":"2020-03-15T18:09:50","modified_gmt":"2020-03-15T17:09:50","slug":"veeam-9-5-direct-restore-to-azure-configure-veeam-pt2","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/veeam-9-5-direct-restore-to-azure-configure-veeam-pt2\/","title":{"rendered":"Veeam 9.5 Direct Restore to Azure: configure Veeam - pt.2"},"content":{"rendered":"

\"veeamdirectrestoreazure01\"<\/p>\n

Direct Restore to Azure is a new feature introduced in Veeam Backup & Replication 9.5 to restore VMs to the Azure cloud<\/strong>.<\/p>\n

The process of restoring on-premises Hyper-V and VMware VMs to the cloud requires that Azure's resources and Veeam<\/strong> environment are properly configured.<\/p>\n

 <\/p>\n

Blog series<\/h2>\n

Veeam 9.5 direct restore to Azure: setup the infrastructure - pt.1<\/a>
\nVeeam 9.5 direct restore to Azure: configure\u00a0Veeam - pt.2<\/p>\n

 <\/p>\n

Configure Azure proxy<\/h2>\n

To optimize traffic and performance, it's recommended the use of an Azure proxy.<\/p>\n

From the Veeam console, access the Backup Infrastructure<\/strong> area and select Backup Proxies<\/strong>. Right click somewhere in the right side and select Add Azure Proxy<\/strong> option.<\/p>\n

\"veeamdirectrestoreazure02\"<\/p>\n

Give the proxy a Name<\/strong> and click Next<\/strong>.<\/p>\n

\"veeamdirectrestoreazure03\"<\/p>\n

Specify a local administrator to create on the Azure proxy. The account name must be plain<\/strong> without domain or machine name. Click Next<\/strong>.<\/p>\n

\"veeamdirectrestoreazure04\"<\/p>\n

Select Azure Resource manager<\/strong> as deployment model since Classic model is now deprecated. Click Next<\/strong> to continue.<\/p>\n

\"veeamdirectrestoreazure05\"<\/p>\n

Specify the Location<\/strong>\u00a0with configured resources in Azure then click Next<\/strong>.<\/p>\n

\"veeamdirectrestoreazure06\"<\/p>\n

Specify the Size<\/strong> (resources) of the Azure proxy and the Storage account<\/strong>. Click Next<\/strong> to continue.<\/p>\n

\"veeamdirectrestoreazure07\"<\/p>\n

Select Create a new resource group<\/strong>\u00a0option and enter a Name<\/strong>. Specify also a\u00a0DNS name label<\/strong> then click Next<\/strong>.<\/p>\n

\"veeamdirectrestoreazure08\"<\/p>\n

Specify the Virtual network<\/strong> and Subnet<\/strong>\u00a0configured in Azure then click Next<\/strong>.<\/p>\n

\"veeamdirectrestoreazure09\"<\/p>\n

The proxy VM is deployed to Azure. Click Next<\/strong> when done.<\/p>\n

\"veeamdirectrestoreazure10\"<\/p>\n

Click Finish<\/strong> to exit the wizard. The proxy configuration is complete.<\/p>\n

\"veeamdirectrestoreazure11\"<\/p>\n

 <\/p>\n

Direct Restore to Azure<\/h2>\n

To restore a VM to Azure, access the Backup & Replication<\/strong> area and select Backups<\/strong>. Right click the backup containing the VM to restore and select Restore to Microsoft Azure<\/strong>.<\/p>\n

\"veeamdirectrestoreazure12\"<\/p>\n

Select Azure Resource manager<\/strong> as deployment model since Classic model is now deprecated. Click Next<\/strong> to continue.<\/p>\n

\"veeamdirectrestoreazure13\"<\/p>\n

Specify the Location<\/strong> and enable the Use Azure proxy VM<\/strong>\u00a0option selecting the proxy configured in previous steps. Click Next<\/strong> to continue.<\/p>\n

\"veeamdirectrestoreazure14\"<\/p>\n

Specify the storage account<\/strong>\u00a0to use and click Next<\/strong>.<\/p>\n

\"veeamdirectrestoreazure15\"<\/p>\n

Specify the resource group<\/strong>\u00a0to use and click Next<\/strong>.<\/p>\n

\"veeamdirectrestoreazure16\"<\/p>\n

Click on\u00a0Network<\/strong> button and specify the VNet<\/strong> to use. Click OK<\/strong>\u00a0to confirm the selection.<\/p>\n

\"veeamdirectrestoreazure17\"<\/p>\n

When the VNet has been specify, click Next<\/strong>.<\/p>\n

\"veeamdirectrestoreazure18\"<\/p>\n

Optionally type a reason for the restore then click Next<\/strong>.<\/p>\n

\"veeamdirectrestoreazure19\"<\/p>\n

Click Finish<\/strong> to\u00a0begin the VM restore.<\/p>\n

\"veeamdirectrestoreazure20\"<\/p>\n

The selected VM is restored to Azure. Note that the restore is processing a Linux-based machine<\/strong>.<\/p>\n

\"veeamdirectrestoreazure21\"<\/p>\n

In Azure portal, select Virtual machines<\/strong>\u00a0tab to see the restored VM.<\/p>\n

\"veeamdirectrestoreazure22\"<\/p>\n

Accessing the\u00a0All resources<\/strong> tab, Direct Restore feature creates\u00a0several components<\/strong>\u00a0for its\u00a0functionality.<\/p>\n

\"veeamdirectrestoreazure23\"<\/p>\n

The Direct Restore to Azure procedure has been completed successfully.<\/p>\n

\"signature\"<\/p>\n","protected":false},"excerpt":{"rendered":"

Direct Restore to Azure is a new feature introduced in Veeam Backup & Replication 9.5 to restore VMs to the Azure cloud. The process of restoring on-premises Hyper-V and VMware VMs to the cloud requires that Azure's resources and Veeam environment are properly configured.<\/p>\n","protected":false},"author":3,"featured_media":19498,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[2138,933,903],"tags":[1682,579,936,584],"class_list":["post-19452","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-backup-en","category-veeam-en","category-vmware-en","tag-azure","tag-backup-en","tag-restore-en","tag-veeam-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/19452","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=19452"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/19452\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/19498"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=19452"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=19452"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=19452"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}