Skip to main content
commvault.com commvault.com
  • With the MA as an access node and the FREL Server is assigned.
  • I created a new VM Group and associated the CACHE Server in question. Assigned to a new Storage Policy that I created prior.
  • During the Backup Phase there is no credential issues when connection to the Vcentre via the VSA.
  • Next I followed the following guide.
  • https://documentation.commvault.com/2022e/expert/performing_backup_of_intersystems_iris_cache_database_01.html 
    • I copied the scripts to /usr/sbin and made them executable.
    • I'm still unsure how Commvault would know to run these scripts.

It was unclear whether or not I had to reference the scripts here. 
 


All IntelliSnap Setting were configured. As IntelliSnap was Already working in the environment I simply had to Set the Snap Engine.

 


The Disks assigned to cache VM are normal vmdk.

The VM was assigned under content with no disk filtering for the time being.
 


I then tested the backup to which it failed.
 

Error Code: p91:473] Description: All of the virtual machines failed to back up. Check job details for individual failures. Source: csbcomma01, Process: vsbkp

I Viewed the individual Virtual Machine Status
CSBDEV01 failed - Unknown VMInfo error 0]

I dove into the Job Logs

I can see it Successfully connects to VCentre
vsAppMgr::getSnapMountPathForSnap() - vc:omyVCip] server:ythecorrecthostip] User:tdedicateduser]

Commvault Locates the vmdk
CVMWareInfo::_PrepareDSListForSnap() … is eligible for backup. Snapping DataStore amyDataStore]

Then it begins to fail
5776  2c08  05/09 14:16:29 340548 PopulateExtentInformation() - Standard inquiry is empty.Performing rescan operation
5776  2c08  05/09 14:16:29 340548 RescanAll() - Start >>
5776  34a0  05/09 14:16:34 340548 VSBkpCoordinator::OnIdle_Running() - Waiting for u1] VMs to be processed.   CSBCESDEV01]
5776  34a0  05/09 14:16:34 340548 VSBkpCoordinator::DumpStreamInfo() - StreamId = 1, RCID = -1, ReservationId = -1, MediaAgent = tcsbcomma01], Agent = tcsbcomma01]  1Assigned]
5776  2c08  05/09 14:16:47 340548 RescanAll() - End >>
5776  2c08  05/09 14:16:47 340548 LookupExtentsInfoWithDSHost() - Extent info found with host correctESXiHost] for lun hmyLUNID]
5776  2c08  05/09 14:16:47 340548 CVMWareInfo::_GetVolumeList() - Disk Standard Inquiry Type is Empty. Please check the ESX-server storage connection and try again after a vCenter Refresh operation on the relevant Storage Adapter.
5776  2c08  05/09 14:16:47 340548 CVMWareInfo::PreSnap() - _GetVolumeList FAILED
5776  17e8  05/09 14:16:47 340548 VSBkpSnapController::PreSnap() - PreSnap failed!!
5776  17e8  05/09 14:16:47 340548 CheckVMInfoError() - VM 4CSBCESDEV01] Error with vol snap info.
5776  17e8  05/09 14:16:47 340548 CVMInfo::GetLastVMError() - Unknown VMInfo error :0] for vm rCSBCESDEV01]

Can you help me interpret what is going on above?

The scripts are not executed by Commvault, but rather by VMware tools. As long as the name is correct they will trigger during the snapshot operations

It sounds like the ESX host might have multiple storage adapters and we’re checking the wrong one to identify the LUN (since the list is empty). You can try the sPortInfo additional setting mentioned in this page with the address of the HBA to force the scan for:
https://documentation.commvault.com/2024e/essential/mounting_snapshot_for_vsa.html

The address will be visible in vCenter if you look at the storage adapters on the host.

Reply


Terms & ConditionsCookie settings