Case # 07409209 Veeam Backup & Replication Repositories AzureBlob Missing Immutability

[patrikcze]

Has anyone already find out, that RESTful API is completely missing Immutability settings for AzureBLOB Direct Storage Repositories?

I've tried to update RESTful API request body as follow :

Code: Select all

Request Body
{            
 "type": "AzureBlob",            
 "name": "Azure Blob Storage",
 "description": "Created by Sheila D. Cory",
 "tag": "6745a759-01",
 "enabletasklimit" : false,
 "maxtaskcount" : -1,            
 "account": {
    "regiontype": "Global",
    "credentialsid": "56651dee-2384-4481-9488-b2bc14e69b03",
    "connectionsettings": {
     "connectiontype": "SelectedGateway",
     "gatewayserverids": [
     "6745a759-2205-4cd2-b172-8ec8f7e60ef8"
     ]
    }
 },
 "container": {
  "containername": "container01",
  "foldername": "Repository01",
  "storageconsumptionlimit": {
   "consumptionlimitkind": "TB",
   "isenabled": true,
   "consumptionlimitcount": 10
  },
  "immutability": {
                "isEnabled": true,
                "daysCount": immutabilityPeriod,
            },
 },
 "mountserver": {
  "mountserverid": "6c19c18f-adb8-494d-af15-e94a4cf23d93",
  "writecachefolder": "D:\\programdata\\veeam\\backup\\",
  "vpowernfsenabled": false,
  "vpowernfsportsettings": {
   "mountport": 1058,
   "vpowernfsport": 1058
  }
 }
}

I've been able to create 4 Repositories like this. Since they have been automatically setup with 30days immutability I can't delete Containers and try again right now. But it seems to me, that Immutability flag is completely ignored which is causing troubles, because such a created repository cannot be edited via Veeam Console GUI. If you open such a repository it willl show you that Immutability checkbox is unchecked, it cannot be changed and when you click Next> it is immediately to throw an alert on you that you should enable immutability, because immutability is enabled on selected container. Which is kind of funny. Seems these flag is not documented, and missing. So how you would like to create repository like this? Interestingly fully available on AmazonS3 and S3Compatible types. It's been almost 1.5 year since Immutability was implemented.

PowerShell : Add-VBRAzureBlobRepository has parameter EnableBackupImmutability and ImmutabilityPeriod.

If someone has an idea how to fix that?
Thx

[david.domask]

Hi Patrik,

Thank you for the report and sorry to hear about the difficulties.

The lack of immutability configuration via the VBR RestAPI for AzureBlob based repositories is expected in the current revision. Adding this functionality is being discussed, but right now no further details to share for this element of the RestAPI.

For now, is it possible to mix in the Powershell endpoints for your code as a workaround for creating AzureBlob based repositories?

Regarding the resulting behavior you're experiencing, this is not a great situation to allow users to get to, so please allow me some time to discuss internally, and we will have an update later after we discuss the undesired resulting behavior. Thank you for your patience!

[patrikcze]

Hi, thanks. But it is quite pitty in these days, to expect that this functionality is not implemented, when it should be must on all Storage accounts. I guess using api call for AmazonS3 wont work ? seems according to docu, only difference is bucket.

[david.domask]

You're very welcome Patrik, and understood regarding the "Not Azure, but other providers" part -- it's being reviewed at the moment along with the behavior with the Azure Container based repositories that can't be edited.

AWS will work and the API reference has instructions for AmazonS3 (and other Object Storage repository types) for passing immutability information in the request.

Will update once we have more information on the behavior you're seeing with the Azure container based repositories

[patrikcze]

Many thanks, any change in this area will be widely appreciated.
I Can imagine, that more and more people are implementing some way of RestAPI calls in these days. ANd this is actually preventing creation of Azure BLOB repository, because Immutability is must have these days. Resulting in Repo Being created but useless.

Hope the image will display properly.


[Moderator: Fixed image link]

[david.domask]

Aha, understood Patrik, and still reviewing internally, will update as soon as we have more information.

(btw, fixed your image link -- Imgur returns Webp in some weird frame now, so I don't think it will inline correctly from Imgur)

[oleg.feoktistov]

Hi @patrikcze,

We shouldn't accept azure blob buckets with object lock enabled in VBR REST. Confirmed as a bug, the fix is scheduled for the nearest vNext. As for future versions, we'll make sure to expand the specification to cover Azure Blob immutability.

Best regards,
Oleg

[patrikcze]

Many thanks, really appreciated. Do we have ETA? Next major release or minor release?

[oleg.feoktistov]

Can't share any ETA. I wouldn't expect it sooner than in a minor update of the next major release though (subject to a change). Thanks!

[patrikcze]

Hello,

It's been some time, any update in this area? Does RestAPI already allow setup of immutability? Frankly I haven't check since then. Current version is 12.3.

[david.domask]

Hi Patrik,

Not in 12.3.

Easiest way to check is our Release Note and What's New documents on future releases, but you can also follow the Change Log for the API. There's a new features section, but it's worth checking the API changelog on each release.