Sp upgrade from 11.32.76 to 11.36

Hi ​@Egor Skepko 

Request to take DR backup before you proceed with upgrade process and refer to the below link to understand the changes and announcements on SP36.

The existing policy will continue to function as it is configured on current version.

https://documentation.commvault.com/2024e/essential/changes_in_commvault_platform_release_2024e.html

​@Pradeep 

Yes, I saw the change in the new SP, but is it safe to upgrade? Does the new SP function well enough? 

I also understand that before I start the upgrade I must first upgrade SQL to 2022? Or will it happen automatically with the upgrade of the SP? 

Do I also have to convert all storage policies to PLAN first or does this also happen with the upgrade?

Hi ​@Egor Skepko 

We recommend upgrading to the latest Service Pack to take advantage of new features. The SQL upgrade will be part of the SP upgrade process. However, if it is missed during the upgrade, you can manually upgrade the SQL Server afterward.

Additionally, if needed, you can convert existing policies to plans. However, both policies and plans will continue to function based on the existing configuration without any issues.

​@Pradeep 

So I start a regular upgrade, and then everything (CommServe to the new SP and SQL to the new version) will be upgraded, including the HA components on the passive server?

​@Egor Skepko 

Passive nodes will not be upgraded with this process, We need to upgrade passive machine separately either through push install or manual upgrade process.

​@Pradeep Thank you.

Assuming you are referring to a CS LIveSync Passive Node by “HA components” - The following section of the documentation will ensure those also get upgraded during the process

https://documentation.commvault.com/2023e/expert/installing_maintenance_releases_02.html

Can I please get a confirmation on this? If it is part of the upgrade process, we would have expected it be included in the software download (via the CommCell Console), however we cannot find any trace of SQL 2022 binaries within the downloaded files.

Do we need to use the download manager to pull a complete media kit?

Hi ​@Erase4ndReuseMedia ,

If the SQL 2022 folders are missing from the software media, you can use the Download Manager tool. Ensure to select the option "Include SQL Server files" to download the full media kit and copy to commserve cache.

​@Erase4ndReuseMedia  have you managed to upgrade Commvault successfully? Could you please share the steps you performed eventually?

​@AndresL 

The SQL  should be in thirdparty folder

Hi ​@Egor Skepko,

Could you please provide more details on environment you have and steps you performed during upgrade:
1) Do you use CommServe LiveSync? 
2) What version of SQL you had before upgrade? It was upgraded automatically by commvault installer?
 

​@AndresL 

The first step you can do is install sql management studio 2020. After juist install from Java console and during the installation its should upgrade the sql. That is the part of installation. 

Yes we are using livesync aswell. 

Make sure you can contact cloud.commvault during the installation. 

Yes. Upgrades were completed successfully across multiple CommCell environments, though we still have Command Center issues in one environment. 

We did have a failure during the SQL upgrade process on two of our CommServe instances, which required the manual uninstallation of some SQL components. 

The following are my rough working notes from the upgrade process:

Downloaded Full Media Kit with SQL Server.

Full Media Kit has been copied to the CommServe (E:\Commvault\11.36).
Upgrade is being performed manually (via E:\Commvault\11.36\WinX64\Setup.exe).

Language Selection: English (United States), Next
License Agreement dialog, accept, Next
Choose Installation Type: Install Packages on this computer, Next
Instance Selection: Use Existing Instance: Instance001, Next
Install Option dialog, Upgrade Feature Release, Next 

Feature Release Upgrade Confirmation, Next

Note: Installation failed during the SQL Standard Upgrade process

From the Summary Log:
	Detailed results:
	  Feature:                       Database Engine Services
	  Status:                        Failed
	  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.

	  Next Step:                     Use the following information to resolve the error, and then try the setup process again.

	  Component name:                Microsoft ODBC Driver for SQL Server
	  Component error code:          1603
	  Component log file:            C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20250122_111021\msodbcsql_Cpu64_1_Local.log

	  Error description:             Fatal error during installation.

Opened Programs and Features (appwiz.cpl)
    Manually Uninstalled the following items:
        Microsoft ODBC Driver 17 for SQL Server
        Microsoft OLE DB Driver for SQL Server
Restarted CommServe

On reboot, the upgrade needed to be manually resumed by running Setup.exe, and selecting the Resume option. 

A subsequent reboot is required as part of the upgrade process.
On reboot, the upgrade needs to be manually resumed by running Setup.exe, and selecting the Resume option. 

Upgrade Completed successfully. 

The above process was then repeated on the Standby CommServe.

Upon the successful upgrade of the CommServe / Standby CommServe, the CommServe LiveSync instances were upgraded via the CommCell Console

CommCell Console > Clients > COMMSERVE_SQL > All Tasks > Add / Remove Software > Upgrade Software

CommCell Console > Clients > DRCOMMSERVE_SQL > All Tasks > Add / Remove Software > Upgrade Software

As info if you do a push upgrade (right click on commserve, all tasks, upgrade) it won’t upgrade SQL. You have to manually install from the exe to do that. In my lab I did the push and had to install SQL separately. Also as info I have hyperscale and pushing 11.36.60 to the nodes is not smooth, i’ve even had to reboot some for the upgrade to work, not sure the deal on that issue.

When we upgraded to 11.36 we ran into some backup performance degradation. About 25% slower.  We have rather large DDB’s > 15 billion records.  Turns out the Faircom DB under the hood gets upgraded and is not as fast as the previous version.

Farmer do you have a case we can reference when talking to our CV support team? Thx

Sure.  It is still an active ticket. 250123-846