Skip to main content
commvault.com commvault.com
Solved

Restore issue

  • January 18, 2022
  • 7 replies
  • 415 views
C
Forum|alt.badge.img+12

Hi Community,

 

I’m facing an issue, and maybe some of you already experienced it.

 

We had a client associated to a storage policy, which was working fine, we added a new MA and created a storage policy with this new MA. After that, we wanted to associate the client to the newly created storage policy in order to use the new MA.

 

After changing the storage policy, we faced an issue with backups, indexing wasn’t working properly, which we fixed by changing the index server of the backupset of the client from the old MA to the new one, and now we are facing an issue where we cannot restore anymore (Below a screenshot).

Please note that we restarted all services for all Commserve, old MA, new MA.

In the DATA RECOVERY JOBS summary, we have a CommServe Management jobs with the storage policy index as a client, stating that there is no communication between the 2 MA.

 

Any help or suggestions would be much appreciated.

 

Regards.

 

 

Best answer by Onno van den Berg

Switching storage policies always result in the first backup to be converted to a full. So that won't be the problem. For some reason it is not picking up the reference to the index correctly. Which version are you on @Commvault Engineer 

View original
Did this answer your question?

7 replies

S
Vaulter
Forum|alt.badge.img+14

Hi @Commvault Engineer ,

What happened to the old MA and Disk/Tape Lib?

How the Mount Paths were/are configured on the old/new MA?

Have you shared the Mount Paths from the old MA to the new MA?

Best Regards,

Sebastien Merluzzi

 

MichaelCapon
L
2 people like this
  • MichaelCapon
    MichaelCapon
  • L
    Laurent
C
Forum|alt.badge.img+12
Sebastien Merluzzi wrote:

a Hi @Commvault Engineer ,

What happened to the old MA and Disk/Tape Lib?

How the Mount Paths were/are configured on the old/new MA?

Have you shared the Mount Paths from the old MA to the new MA?

Best Regards,

Sebastien Merluzzi

 

Thanks @Sebastien Merluzzi for your availability

 

Actually the old MA is still working just fine, the only thing changed is the storage policy associated to the client which is using the new MA, and changed the index server of the backupset.

 

And we didn’t share the mount paths from old MA to new one.

Is there in a way to transfer index data of that specific client or another workaround from old MA to new one ? 

 

Thanks a lot.

L
Byte
Forum|alt.badge.img+15
  • Laurent
  • Byte
  • 386 replies
  • January 19, 2022

Hi ! 

When you switched the client(s) from old SP to new SP, did you run a real full backup, or just left untouched, so incremental ran from old SP to new SP ?

What if you try to view backup history for a client, select a full/synthfull, then browse and restore for this one ? Also if failing try to force the proper MA in the advanced options, and change the copy precedence.

 

Onno van den Berg
Commvault Certified Expert
Forum|alt.badge.img+19
  • Onno van den BergCommvault Certified Expert
  • Commvault Certified Expert
  • 1227 replies
  • Answer
  • January 19, 2022

Switching storage policies always result in the first backup to be converted to a full. So that won't be the problem. For some reason it is not picking up the reference to the index correctly. Which version are you on @Commvault Engineer 

C
Forum|alt.badge.img+12
Laurent wrote:

Hi ! 

When you switched the client(s) from old SP to new SP, did you run a real full backup, or just left untouched, so incremental ran from old SP to new SP ?

What if you try to view backup history for a client, select a full/synthfull, then browse and restore for this one ? Also if failing try to force the proper MA in the advanced options, and change the copy precedence.

 

Hi Laurent,

 

Thanks for your suggestions and hints, actually we’ve made a full backup after the change, backups work just fine, when trying to restore “Brows and restore” we got the previously shared screenshot, we couldn’t even browse the data.

C
Forum|alt.badge.img+12
Onno van den Berg wrote:

Switching storage policies always result in the first backup to be converted to a full. So that won't be the problem. For some reason it is not picking up the reference to the index correctly. Which version are you on @Commvault Engineer 

Hi Onno,

It’s index version 2

Onno van den Berg
Commvault Certified Expert
Forum|alt.badge.img+19
Commvault Engineer wrote:
Onno van den Berg wrote:

Switching storage policies always result in the first backup to be converted to a full. So that won't be the problem. For some reason it is not picking up the reference to the index correctly. Which version are you on @Commvault Engineer 

Hi Onno,

It’s index version 2

I was more referring to the Commvault feature release and related maintenance release. 

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