So recently (like last week) BackBlaze announced the support of S3 API calls. Something people have wanted literally for years now. Me included.
Anyway you all know me, I don't throw a bunch of fluff out.. here is how to add a B2 bucket as a repository.
First off some things that took me way too long to discover:
Buckets created prior to May 4 2020 won't work. So you have to create a new bucket.
Here's a handy link of tips: Help.Backblaze.Com
Open Veeam (duh)
Click on Backup Infrastructure
Right-Click Backup Repositories
Choose 'Add Backup Repository'
Click on Object Storage
S3 Compatible
Service Point: The entire S3 Endpoint url in your Application Key
Region: Just the 'us-west-000' or equivalent in your app key
Credentials: Create a new one based off your Key ID and Application Key
Make sure the bucket you associated with the Application ID is correct, create a new folder within
That's it!
Technology tidbits and things related to small farming including Powershell, AD, Exchange, Security, Chickens, Dogs, General Construction and the like.
Showing posts with label Veeam. Show all posts
Showing posts with label Veeam. Show all posts
Monday, May 11, 2020
Friday, September 7, 2018
Unable to consolidate guest, Vcenter 5.5U3
Forgive me but this was a week ago so I don;t have copies of the actual error messages.
So I logged into Vcenter last Monday and found two of my guests needed to have their snapshots consolidated. Except looking under Snapshot manager neither guest had any listed!
So long story short: I contacted Vmware support and learned that since we use Veeam to backup our vm guests.. that Veeam proxy machines actually mount the VMDK's of my target guests as RO then backs them up. Well turns out that for whatever reason one of my proxies did not un-mount a couple of guests VMDK files once the backup job was complete.
So if you run into this where you tell a guest to consolidate snapshots and it fails, *AND* you use Veeam then check your proxy machines to verify they have no disks mounted that do not normally belong to it.
So I logged into Vcenter last Monday and found two of my guests needed to have their snapshots consolidated. Except looking under Snapshot manager neither guest had any listed!
So long story short: I contacted Vmware support and learned that since we use Veeam to backup our vm guests.. that Veeam proxy machines actually mount the VMDK's of my target guests as RO then backs them up. Well turns out that for whatever reason one of my proxies did not un-mount a couple of guests VMDK files once the backup job was complete.
So if you run into this where you tell a guest to consolidate snapshots and it fails, *AND* you use Veeam then check your proxy machines to verify they have no disks mounted that do not normally belong to it.
Subscribe to:
Posts (Atom)