musicalbas.blogg.se - Veeam backup to azure blob

#Veeam backup to azure blob software#
#Veeam backup to azure blob trial#
#Veeam backup to azure blob password#
#Veeam backup to azure blob license#

Leave them in the comments section, I’ll be happy to help (if I can).Last year, with the launch of Veeam Backup & Replication v10, the company announced the general availability of Veeam Backup for Microsoft Azure.

add a new Backup Repository (connected to the created Object Storage Repository this local repository will only store metadata – backup data will be offloaded to the object storage and can be encrypted, if needed):Īny questions/difficulties with your setup?.

#Veeam backup to azure blob password#

lastly, I’ve created an app password for my (global admin) account (which will also be required for Veeam configuration):.

after that, I’ve enabled the “legacy authentication protocols”, which is still a requirement (you can do it in Office 365 admin center – SharePoint admin center – Access Control – Apps that don’t use modern authentication – Allow access or via PowerShell command “Set-SPOTenant -LegacyAuthProtocolsEnabled $True”):.

UPDATE: Got back the word from Veeam development – additional SharePoint permissions may not be necessary after all, maybe I needed to wait a bit longer… will retry next time without those permissions.

then, I’ve added the minimal required API permissions to this app (as per the official docs) – but note that the official docs have an error (at this time), which I reported to Veeam – you’ll need the SharePoint Online API access permissions even if you don’t use the certificate based authentication(!) – so, the permissions which work for me are:.I’ve added a secret (which you should also take a note of, because you’ll need it later) to this app:.for this, I created a custom application in Azure Active Directory (AAD) (under App registrations – New registration) (take a note of the Application (client) ID, as you will need it when configuring Veeam):.note: I’m using the Modern authentication option because of MFA on my tenant and… it’s the right way to do it!.one other thing you’ll need from this section is the Storage API Endpoint, which depends on the zone you’ve created your bucket in (mine was created inside AT-VIE-1 zone, so my endpoint is ):.to access your bucket from Veeam, you’ll need your API keys, which you can find in the Account – Profile – API keys section:.if you need to make adjustments to the ACL of the bucket, you can ( quick ACL with private setting is just fine for this one):.

#Veeam backup to azure blob trial#

creating the Exoscale SOS bucket is relatively easy, once you have your account (you can request a trial here) – you choose the bucket name and zone in which data will be stored and… voilà:.

#Veeam backup to azure blob software#

no real prerequisites and tips here – simple Windows VM, on which I’m installing the downloaded software (there is a list of system requirements if want to make sure it’s all “by the book”).

Now, a few tips on the “configuration part”:

created a backup job for this Office 365 organization.

added a new Office 365 organization with AAD app and Global Admin account credentials ( docs).

configured a custom AAD app (with the right permissions).

added a new Backup Repository which offloads the backup data to the previously created Object Storage Repository.

configured Veeam Backup for Office 365 (not so hard, if you know what you are doing and you’ve read the official docs).

(it’s a “Next-Next-Finish” type of installation, hard to get it wrong) (good people at Exoscale/A1TAG/A1.digital/A1HR provided me credits, so… why not?!)

created an Exoscale SOS bucket for my backups.

#Veeam backup to azure blob license#

(good people at Veeam provided me NFR license for it, so I’ve used it instead of Community Edition)

(good people at Microsoft provided me Azure credits, so… why not?!) created a standard Windows Server 2019 VM on top of Microsoft Azure, to hold my Veeam Backup for Office 365 installation.I’ve created a small environment to support this test (and later production, if it works as it should) and basically done the following: To test this, I decided to use the Exoscale SOS (also S3-compatible) storage for backups of my personal Office 365 via Veeam Backup for Office 365. And even better – you can use any S3-compatible storage to do the same! How cool is that?! So, this means that you can take Amazon S3, Microsoft Azure Blob Storage or even IBM Cloud Object Storage and use it for your Veeam Backup for Office 365. This feature is “ object storage support“, as you may have guessed it already from the title of this fine post! I would like to focus on one of the features of the new Veeam Backup for Office 365 v4, which was released just the other day. I’m not going into the lengthy and exhausting discussion of why you should take care of your data, even if it’s stored in something unbreakable like “the cloud”, at least not in this post. Are you backing up your Office 365? And… why not? 🙂