Restore from Combined Storage Tier Cool/Archive

  • 7 November 2022
  • 4 replies

Badge +1

Hi All,

I have question regarding the Restore process specially for the VM Gues File system restore when done from the combined Storage Tier Cool-Archive being as used as end for long term Library.

As understand, the Index and Meta data in this case will be in Cool storage and hence we would be able to Browse the data without having to run the recall workflow.

Having selected the folders to restore, will the complete VM data/disk data be rehydrated from archive to tier or just the selected data?






Best answer by Matt Medvedeff 7 November 2022, 16:34

View original

4 replies

Userlevel 4
Badge +10

Hi @Karan 

Just the data you selected in the Browse and Restore options should be rehydrated to the Accessible tier. 

If you wanted to confirm the size of the data being recalled. Check the WorkflowCustom.log file on the Commserve and you’ll see the size and amount of files being recalled from Archive.


Badge +1

@Matt Medvedeff : Thanks for your quick response here. 

Following up on the initial question, will the recall depend on the IDA in question, or will it be same across for all. Example: will it follow the same process if we go for a 1 DB restore out of many DB’s that were part of the backup Job?

Is there any official CommVault documentation that explains this process?

Userlevel 4
Badge +10

Yep, it follows the same per iDA. What you select in browse and recovery options, is what gets recalled granularly from the Archive tier.

I don’t think the documentation specifies this exactly, but the documentation for Recalls are here -

Userlevel 3
Badge +13

Hello, please for a confirmation!

In case of Combine Storage Archive/Cool, the browse for Azure VM Guest files running without the Cloud Storage Archive Recall workflow ?

Im asking because Im getting the following error when trying to browse VM Guest files (during mounting disks), even after running the workflow!

0xEDA0000B:{CPseudoMountServer::HandleVMMountReq(1580)} + {CPseudoVMManager::MountVM(450)} + {CPseudoVM::GetVolumesInfo(438)} + {CPseudoVM::GetVolumesInfo(430)/CV.0xB-No Volumes found}

Is there anything to try or I will need to create an incident ticket?

Thank you in advance,