Skip to main content
commvault.com commvault.com
Solved

CV11.28 AWS Combined Storage Tier Recall questions

  • February 15, 2024
  • 1 reply
  • 34 views
Patrick Dijkgraaf
Commvault Certified Expert
Forum|alt.badge.img+9

Hi all,

 

At a customer, we are using Combined Storage Tiers:

  • CV 11.28
  • AWS Deep Glacier / Standard-Infrequent Access

 

We have a few questions on this:

  • When we do a restore, the Recall workflow kicks in. We see that it initiates the Recall and then waits for 13 hours before checking the Recall Success. Why is it only checking after 13 hours? The data might be available sooner, so it would make sense checking earlier.

     

  • Which Recall type is used by default (with CV 11.28), is it Standard or Bulk?

 

Thanks in advance!

Best answer by Damian Andre

hi @Patrick Dijkgraaf,

The recall mode uses standard by default. If you manually execute it you can override it to bulk or expedited if supported on your storage class:

Retrieval option: The recall mode that must be used to recall data. Default is set to 0, which is Standard mode. Valid values are:

0 - Standard

1 - Expedited

2 - Bulk

 

The workflow does not seem to be looping or waiting at “Checking Recall Success” - this activity checks if the recall was successful from the output of the previous activity, e.g the previous activity’s output is piped into this activity. So there is no wait or inherent delay that I can see - this is actually how long it took in this instance.

View original
:wq!
Did this answer your question?

1 reply

Damian Andre
Vaulter
Forum|alt.badge.img+23
  • Damian AndreVaulter
  • Vaulter
  • 1297 replies
  • Answer
  • February 16, 2024

hi @Patrick Dijkgraaf,

The recall mode uses standard by default. If you manually execute it you can override it to bulk or expedited if supported on your storage class:

Retrieval option: The recall mode that must be used to recall data. Default is set to 0, which is Standard mode. Valid values are:

0 - Standard

1 - Expedited

2 - Bulk

 

The workflow does not seem to be looping or waiting at “Checking Recall Success” - this activity checks if the recall was successful from the output of the previous activity, e.g the previous activity’s output is piped into this activity. So there is no wait or inherent delay that I can see - this is actually how long it took in this instance.

Reply


Most helpful members this week

Terms & ConditionsCookie settings

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