![]() Your bucket(s) will now show, select the destination bucket - in my case VeeamBackupO365 - now you need to browse a folder for Veeam to upload backup data too. Hit next with the new credentials selected. Then Select add credential, entering the App Key ID and Secret created and saved securely earlier. Now enter the s3 endpoint copied from the Backblaze panel into the Service endpoint on the Veeam wizard. Make your way into the Backup Infrastructure panel and Add a new backup repository. Jump into Veeam Backup for Office365 Console- time to create a new Backup Repository. You will need these in Veeam when creating the repository. ![]() Your new application key will appear, save these somewhere secure as they only appear once. Fill our your desired settings and as good practice secure it out to only allow access to your new bucket. Create some application keys/credentials - head over to the App Keys settings in Backblaze and hit create new. Now, what good is a bucket with out anyway to access it. The bucket with then appear in your list - note the new s3 endpoint, you will need this when you get into Veeam Backup for Office365 It instructs you that: Buckets created before cannot be used with our S3 Compatible APIs.Īll good, create a new one Creating a new bucket in Backblaze If you already have some you will notice that there is a blank entry next to endpoint. If you do not already have a Backblaze B2 account - create one here, first 10gb is free so you can kick the tires without even entering a credit card. TLDR it works great! no issues whatsoever, up and running in less time than you can make a cup of coffee. Why not try this out with some Veeam Backup products to see if it all fires up, starting with Backup for Office365. today I saw an email from Backblaze saying they now have native s3 api support! I already use their personal and B2 backup services with absolutely no complaints.
0 Comments
Leave a Reply. |