Restoring Tapes from Azure Blob Archive tier storage

[dgbegfb]

VTL tapes are not immutable by design. So, is your request about introducing immutability on the VTL level?

Not exactly, I can and I do a tape immutability at Azure level using retention policy but VTL doesn't see it and doesn't check so when VTL issue a deletion command it doesn't report about an unsuccessful operation.

Yes, please I will be happy to have that chart. Thanks!

Here you are. The first is upload/download by VTL and the second one is the same thing using web gui.

Screenshot 2023-11-06 at 22.44.54.png (152.64 KiB) Viewed 37617 times

Screenshot 2023-11-06 at 22.47.32.png (230.58 KiB) Viewed 37617 times

[yaroslav (staff)]

I will forward your request to R&D Stay tuned!
Thanks.

[yaroslav (staff)]

Hi,

I finally got some updates.
1. CloudReplicator does not support immutable storage yet. It was put on the road map.
2. It is possible to increase the block size in replicator settings to reduce the number of i/o requests.

[dgbegfb]

Hi.

Thank you for the feedback.

1. I don't know what do you mean then talk about support of immutable storage. I meant just a deletion errors handling for whatever reason they arise whether because of a storage immutability or any other reason.

2. There no such variable in VTLReplicationSetting.ps. Do you mean that I can edit config.json in CloudReplicator folder? That the value of AzurePartSizeMb is safe, optimal or recommended?

3. You still have provide with no feedback to another topic from my previous post:

VTL rehydrate archive tape using Set Blob Tier to the same container. It leads to early deletion and impossibility of using life cycle management in the case of immutability. Microsoft recommends using Copy Blob command to Hot tier and if it can be done to another container it will be possible to delete it automatically.

Is this issue on the road map or it's just an out of importance detail for you?

[yaroslav (staff)]

You are always welcome

1. I don't know what do you mean then talk about support of immutable storage. I meant just a deletion errors handling for whatever reason they arise whether because of a storage immutability or any other reason.

I was answering your question about immutability support.

2. There no such variable in VTLReplicationSetting.ps. Do you mean that I can edit config.json in CloudReplicator folder? That the value of AzurePartSizeMb is safe, optimal or recommended?

You can tweak the Cloud Replicator JSON, however, I am not sure if adding immutability support as a parameter there will help.

3. You still have provide with no feedback to another topic from my previous post:

I believe it is on the Road Map. I have brought this thread to the dev team, so they should be aware of your suggestions.

many thanks for your efforts!

[dgbegfb]

Thanks, everything is clear but I have a mess with one question:

I asked previously:

using VTL to upload/download tape to/from Azure it uses much many write/read operation in comparison to make the same operation by web gui. I have a chart to compare it if you will need. It just the question of money.

You answered:

It is possible to increase the block size in replicator settings to reduce the number of i/o requests.

I asked then how to do it if there is no such option in VTLReplicationSetting.ps?
and your answer a bit irrelevant:

You can tweak the Cloud Replicator JSON, however, I am not sure if adding immutability support as a parameter there will help.

so how to increase the block size in replicator settings in a right way?

[yaroslav (staff)]

You are always welcome. Sorry if my answers appear to be misleading.
Yes, you are right.