Solved

Change AWS Storage Tier on Existing Copies

  • 27 August 2021
  • 2 replies
  • 301 views

Badge +1

Hey Community,

2 Questions

  1. Is it possible to change the AWS storage tier from Glacier to Deep Archive on copies that already exist beside running an aux copy? We ran 7 months of aux copies to Glacier until we were told to send it to Deep Archive.. Now we have 500TB sitting in the Glacier class and of course, costing money. I’ve started the process of just aux coping them, but it is tedious to do one job ID at a time on the Cloud Storage Archive Recall workflow.
  2. Is there a way to add multiple job IDs to the workflow?

Thanks in advanced

~John

icon

Best answer by Prasad Nara 27 August 2021, 01:09

View original

2 replies

Userlevel 4
Badge +6

There is no need to auxcopy data. Follow below 2 steps.

  1. Change storage class on the cloud library mount path to Deep Archive. This will make new jobs to write to Deep Archive. Refer below documentation for more details. https://documentation.commvault.com/11.24/expert/129205_migrating_data_between_storage_classes_in_cloud_storage_library.html
  2. Follow below documented procedure to move all existing data from Glacier to Deep Archive. You may also use AWS Life Cycle policy for this instead of running Commvault tool do the move. https://documentation.commvault.com/11.24/expert/121343_permanently_moving_data_from_one_cloud_storage_tier_to_another.html
Badge +1

Thank you very much! This is exactly what I was looking in changing the data I already had in Glacier.

Reply