Skip to main content
Solved

Using Immutable Storage Pools in Azure for Commvault Backup Target

  • October 25, 2021
  • 5 replies
  • 893 views

Forum|alt.badge.img+1

We have a Commvault infrastructure running in Azure with all clients in Azure and we are thinking of converting the Azure storage accounts to be immutable, has anyone any experience of doing this?

I think that this will increase the amount of storage being used by a factor of between 2 and 3 but just wanted someone who had actual experience of doing this to comment on this?

Best answer by Scott Moseman

davided wrote:

I think that this will increase the amount of storage being used by a factor of between 2 and 3 but just wanted someone who had actual experience of doing this to comment on this?


I have not done this in production yet, but have done it in a couple POCs.

Logically these should be your expectations based on a “30 day” retention:

Protected Retention        30 days
DDB Sealing                   30 days  (1 x Protected Retention)
SP Retention                   61 days  (2 x Protected Retention +1)
Immutable                       60 days  (2 x Protected Retention)
Max Size on Disk            90 days  (3 x Protected Retention)

Only “30 days” of data is ever guaranteed immutable.  It’s harder to explain why the 60 days immutability and 90 days on disk exist without walking through it on a whiteboard.

Note: Using a Commvault HyperScale appliance with Ransomware Protection and WORM, you can achieve an immutable disk storage target using only 1x the disk space.

Thanks,
Scott

View original
Did this answer your question?

5 replies

Mike Struening
Vaulter
Forum|alt.badge.img+23

Hi @davided !  Thank you for the post and welcome!

Are you concerned about the space usage by going to Azure immutable, or are you concerned about the impact of not having the option to prune off jobs as needed?  do you plan to increase your retention as a result?

I want to be sure I’m addressing your concern properly :nerd: .

Thanks!


Scott Moseman
Vaulter
Forum|alt.badge.img+18
  • Vaulter
  • 511 replies
  • Answer
  • October 25, 2021
davided wrote:

I think that this will increase the amount of storage being used by a factor of between 2 and 3 but just wanted someone who had actual experience of doing this to comment on this?


I have not done this in production yet, but have done it in a couple POCs.

Logically these should be your expectations based on a “30 day” retention:

Protected Retention        30 days
DDB Sealing                   30 days  (1 x Protected Retention)
SP Retention                   61 days  (2 x Protected Retention +1)
Immutable                       60 days  (2 x Protected Retention)
Max Size on Disk            90 days  (3 x Protected Retention)

Only “30 days” of data is ever guaranteed immutable.  It’s harder to explain why the 60 days immutability and 90 days on disk exist without walking through it on a whiteboard.

Note: Using a Commvault HyperScale appliance with Ransomware Protection and WORM, you can achieve an immutable disk storage target using only 1x the disk space.

Thanks,
Scott


Forum|alt.badge.img+1
  • Author
  • Bit
  • 2 replies
  • October 26, 2021

Thanks Mike it really is the increase storage and the additional cost that is the concern, the retention periods of 35 days will stay the same.


Forum|alt.badge.img+1
  • Author
  • Bit
  • 2 replies
  • October 26, 2021

Thanks Scott that is exactly what I needed perfect.


Mike Struening
Vaulter
Forum|alt.badge.img+23

@Scott Moseman is a legend!


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings