Skip to main content
Solved

Commserve (passive) upgrading SQL version


Forum|alt.badge.img+1

Hello,

After the testing with test failover from CommServe A to another Commserve B, I have started the production failover.

 

The production failover is successful completed.

But, the replication job don't work from CommServe B (new) to CommServe A (old).

Because the SQL-version of CommServe A is lower than CommServe B.

CommServe A have 12.00.5223 (SQL 2014)

CommServe B have 13.00.5888 (SQL 2016)


How can I fix this problem?

I think that this article will help me, but it is not about the passive Commserve.

 

https://documentation.commvault.com/commvault/v11_sp20/article?p=115437.htm

 

Do you have any advice for me?

Best answer by Niels

It is solved. I have on passive node (CommServe A) upgraded the SQL from 2014 to 2016.

View original
Did this answer your question?
If you have a question or comment, please create a topic

6 replies

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

@Niels , asking first, can you upgrade A to the same version?  You definitely want them to be the same, ideally.


Forum|alt.badge.img+1
  • Author
  • 2 replies
  • March 2, 2022

Which version?

Both CommServe have same version. Only SQL-version is different.


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

Sorry, @Niels .  Was referring to the SQL version.  I’ll confirm my suspicion, though I believe they have to be sure same.


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

Confirmed the above.

Yes, you want them to be the same; if the DR server is higher then you will not be able to failback, cause you will not be able to restore transaction logs or database from a higher version to a lower version.


Forum|alt.badge.img+1
  • Author
  • 2 replies
  • Answer
  • March 4, 2022

It is solved. I have on passive node (CommServe A) upgraded the SQL from 2014 to 2016.


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

Thanks for confirming!!


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