Connecting VTL to Cloud Storage

[yaroslav (staff)]

Hello,

Could you please trigger the error again and send me the logs? It will be easier for me to analyze them then. Thanks.

[kbtech]

No problem, here you go.

https://www.dropbox.com/transfer/AAAAAB ... CpX9Ig_5LY

[yaroslav (staff)]

Hello,

Here is what we found in StarWind Cloud Replicator logs:

Code: Select all

Content-Type : application/json
Accept : */*
Host : localhost
User-Agent : StarWind Service
Content-Length : 182
{"AccountName":"kbtechbackup""AccountKey":"C3zyhyEheRmhrKR/0AQ2rUTbVRH2muQjUljjRD5QDKKaYVh2HgsWjmCY95DaIc/WXvVn5qoHTpQiwGJg4fQPXg==""ContainerName":"veeambackup""Region":"Public"}

2020/01/16 07:47:18.033 [12] Cloud replicator with name SimpleFileTransferReplicator is not supported.
2020/01/16 07:47:19.018 [12] Cloud replicator with name SimpleFileTransferReplicator is not supported.
2020/01/16 07:47:19.058 [33] Error: AzureAccessTiersAreNotSuppored. Message: Access tiers are not supported for storage account kbtechbackup. Error code: 440
2020/01/16 07:47:19.073 [12] Validate settings for container: veeambackup. Result: AzureAccessTiersAreNotSuppored

Let me interpret what that means. While connecting to Azure Blob storage, VTL runs validation tests to see if storage tiers are available. Based on the reply we get, validation cannot be run as it should due to Azure account settings (i.e., storage tiering is disabled or unavailable). This may be happening if you use General-purpose v1 account; try switching to General-purpose v2 storage as access tiers are supported by v2 storage type only. That's why you get that error.
Long story short, a possible fix is checking Azure account settings and using General-purpose v2 storage.
Any feedback appreciated.

[kbtech]

Thanks for your help, that did the trick.

[yaroslav (staff)]

Hi,

I am happy to know that!