Skip to main content
Solved

Unable to create Azure archive appliance


Hello Veeam Community, I am very new to Veeam. I am encountering a problem. Please help and guide. I cannot proceed or find a solution that works for me.

I am getting an error below in VBR SOBR archive job while deploying the Archive appliance in Azure.:-

Failed to deploy archive appliance: The installation of SDK files failed after five attempt 

I have 500TB data that I would like to move from the capacity tier to the archive tier. Everything is created in Azure automatically by VBR. Every time the archive job runs I am presented with the above error. The four appliances are created in Azure 3 appliance are deleted and one is running. One is appliance is not enough to move large amount of data from capacity to archive tier in my situation.  


  

Best answer by usman651

Thanks community for your support. It turned out that I did not have enough quota in Azure for multiple Azure Archive appliance. 

View original
Did this topic help you find an answer to your question?

4 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8449 comments
  • July 11, 2024

See if this KB can possibly help as I don't personally use Azure - https://www.veeam.com/kb4320

There is also this community post from a while back - https://community.veeam.com/discussion-boards-66/archive-offload-to-aws-glacier-error-795

 


MicoolPaul
Forum|alt.badge.img+23
  • 2360 comments
  • July 12, 2024

This looks like you’ve got issues communicating to the archiver appliances, are you trying to communicate with them directly out to the internet via their public IP addresses, or are you trying to communicate with them via a site-to-site VPN or ExpressRoute?

 

Lets start here :)


  • Author
  • Not a newbie anymore
  • 3 comments
  • July 13, 2024

@MicoolPaul communicate with them directly out to the internet via their public IP addresses.

 


  • Author
  • Not a newbie anymore
  • 3 comments
  • Answer
  • July 14, 2024

Thanks community for your support. It turned out that I did not have enough quota in Azure for multiple Azure Archive appliance. 


Comment