Skip to main content
Solved

Index Restore Jobs vsa v2


Forum|alt.badge.img+12
  • Commvault Certified Expert
  • 90 replies

Hi All,

 

we are running vsa backups ( vmware ) with indexv2 . During all synthfull backup jobs ( running every week ) we get for each vm an index restore job. 

 

Operation Type: Index Restore

iDataAgent: CommServe Management

Job Started From: Native Application Interface

Job Started By: System

 

The job restored 0 objects

 

I checked alle index reports and health reports but found no error. 

 

Do you have an idear what happend here ?

 

Best answer by MichaelCapon

I would suggest checking the logs for the Synth Full and also the Index Restore Job, from that you should see any related errors and also the Index’s GUID.

When you have the GUID you could check the Browse, IndexState, IndexServer and LogManager log file on the MA (as the time of Synth/IdxRestore) for clues as to what is happening.

 

 

View original
Did this answer your question?

5 replies

Forum|alt.badge.img+4
  • Vaulter
  • 6 replies
  • May 6, 2021

Hi SSchmidt,

 

Does the Index Restore job complete successfully or sits pending?

Do the backup operations complete successfully?

Do you have ample space in your Index Cache location?

 

 

Thanks.

 

 


Forum|alt.badge.img+12
  • Author
  • Commvault Certified Expert
  • 90 replies
  • May 6, 2021

Hi samwise,

 

yes all index restore jobs are completed but number of objects restored is 0 . Yes the synthfull backup job runs without any error or any event completed. I checked all index reports and i dont see any error message


MichaelCapon
Vaulter
Forum|alt.badge.img+14
  • Vaulter
  • 349 replies
  • Answer
  • May 6, 2021

I would suggest checking the logs for the Synth Full and also the Index Restore Job, from that you should see any related errors and also the Index’s GUID.

When you have the GUID you could check the Browse, IndexState, IndexServer and LogManager log file on the MA (as the time of Synth/IdxRestore) for clues as to what is happening.

 

 


Forum|alt.badge.img+6

this is a known and expected behavior according to Devs. Archive Index always triggers a Index Restore, regardless of it being needed or not.

We logged CMR 344442 to change this, last we know that is planned for FR29.


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

Thanks for sharing, @Stefan Vollrath !


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