I will leverage that share and map a drive on the new Azure Veeam VM using this short script: I have prepared an Azure SMB share as shown in this post, and stored a number of files in it that we’ll need:
VEEAM BACKUP FOR AZURE PASSWORD
Enter the name and password used during the VM setup above. Once Azure is finished provisioning the new VM, click Connect at the bottom to connect to the new Azure VM via RDP.
This size has 2 CPU cores, 3.5GB of memory, and can have a maximum of 4x 1TB disks in addition to the 127 GB boot disk and a 60 GB temporary disk.įor Azure VM pricing details see this link.Ĭonfigure the VM to use the Cloud Service and Storage account we created earlier: Create a virtual machine from Gallery using the Server 2012 R2 Data Center image:Ĭonfigure as Basic A2 size. Under Storage, select your Storage account, click the Containers link on top, then click Add at the bottom:Ĭontainers are similar to file system folders.Ĥ. Setup a Container under the Storage account: A Storage account has a 500TB maximum capacity.ģ.This costs 1/2 as much as geo-redundant replication, and provides twice the bandwidth. Locally redundant replication will maintain 3 copies of the data in a single Azure data center.This is the default, and can be changed later. Veeam Backup for Azure delivers enterprise-ready Azure backup and recovery capabilities, fully automated for protecting and managing all your Azure data at. Geo-redundant replication will maintain 6 copies of the data in 2 geographically distant Azure data centers.Storage account must be in the same region as the Cloud Service.We backup the vms in azure with that and copy them back onsite due to our physical tape requirement.
In planning this deployment, select a region that’s geographically close to to your data center to have lowest latency. Then we just carved out some of that licensing to use for Veeam Backup for Azure.
VEEAM BACKUP FOR AZURE INSTALL