Skip to main content
commvault.com commvault.com
Solved

Azure VM has v2 index and startsynthfull trying to pullindex from on-premise MA

  • September 29, 2022
  • 3 replies
  • 60 views
D
Byte
Forum|alt.badge.img+13

Hello team,

Azure VM(V2) backup via a MA lives in Azure and backup working fine

 

just noticed an interesting thing when synth full runs, during startsynthfull phase, it attached to on-premise index server to retrieve index

supposed it should pull index from its own index server (index server to which the VM Storage Policy associated )

972   5fac  09/28 02:15:12 748707 CVOnDemandSvcClient::SubmitTask() - On Demand service CVODS_indexserver_On_premise_MA_01_1 launched at host TOAPVLTMDA01.nbfc.com*toapvltmda01*8400*8402. Unique ID is DCF190B8-BFE8-40DD-9920-08F7503F60A1
972   5fac  09/28 02:15:12 748707 CVOnDemandSvcClient::Attach() - Successfully attached to on Demand service CVODS_indexserver_On_premise_MA_01_1 launched at host On_premise_MA_01.XXX.com*On_premise_MA_01*8400*8402. Unique ID is DCF190B8-BFE8-40DD-9920-08F7503F60A1
972   5fac  09/28 02:15:44 748707 ProcessSynthFullResponse called.
972   5fac  09/28 02:15:44 748707 JM Client  CVJobClient::initialize(): Got remote host [azcp-cvserv01.nbfc.com].
972   5fac  09/28 02:15:44 748707 Updating Job Manager with total number of files:[266060] for backup:[748707]

972   5fac  09/28 02:15:44 748707 STARTRESTORE Synthetic Full preparation phase successfully completed. Updating Job Manager

 

Best answer by Collin Harper

Hello @DanC 

Simply, there are index logs that need to be transferred from the on-prem Media Agent to the cloud based one. This can happen when the subclient or policy were moved\changed in the middle of a cycle. Once the Synth Full runs we would try to transfer the index files from the old MA to the new MA. This process should be seemless unless there are connectivity issues between the source and target Media Agents.

We can also encounter index issues like this when aux copies are not fully caught up. If the earlier part of the cycle has been copied and aged off the Primary copy, we will restore the index from another copy.

To determine the root cause of why this is happening we would need logging and a database (would be best to get a Support Case opened) but if there are no issues being reported and the jobs are running you should be OK.

 

Thank you,

Collin

 

View original
Did this answer your question?

3 replies

C
Vaulter
Forum|alt.badge.img+14
  • Collin HarperVaulter
  • Vaulter
  • 490 replies
  • Answer
  • September 29, 2022

Hello @DanC 

Simply, there are index logs that need to be transferred from the on-prem Media Agent to the cloud based one. This can happen when the subclient or policy were moved\changed in the middle of a cycle. Once the Synth Full runs we would try to transfer the index files from the old MA to the new MA. This process should be seemless unless there are connectivity issues between the source and target Media Agents.

We can also encounter index issues like this when aux copies are not fully caught up. If the earlier part of the cycle has been copied and aged off the Primary copy, we will restore the index from another copy.

To determine the root cause of why this is happening we would need logging and a database (would be best to get a Support Case opened) but if there are no issues being reported and the jobs are running you should be OK.

 

Thank you,

Collin

 

MichaelCapon
1 person likes this
  • MichaelCapon
    MichaelCapon
D
Byte
Forum|alt.badge.img+13
  • DanC
  • Author
  • Byte
  • 104 replies
  • September 29, 2022

@Collin Harper  thank you

 

 

C
1 person likes this
  • C
    Collin Harper
C
Vaulter
Forum|alt.badge.img+14

@DanC You’re welcome!

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