Upgrade form 11.32 to 11.36 with Commserve LiveSync

SQL gets upgraded during the CV upgrade. Make sure you include SQL in your Media Kit when downloading.

On a Live Sync setup I usually download the media kit and run the upgrade interactively on the the Prod Commserve.

After the upgrade I copy the media kit to cache and push out the upgrade to the Prod second instance & then the DR server. 

Super abbreviated version:

• Download the full media kit -- including MS SQL Server
• Run Setup.exe on the Primary and update Instance001
  (With SQL upgrade, this may require a couple reboots)
• Run Setup.exe on the Standby and update Instance001
  (With SQL upgrade, this may require a couple reboots)
• Run a Download Software to populate the Software Cache
• Run an Upgrade Software on CCG | CSLiveSync | CSLiveSync
  (This will upgrade the remaining Instance002s)

Enjoy your FR36 environment.

Thanks,
Scott

Copy / Paste from the other thread - but 

We completed upgrades 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

Thank you for fast reply guys!

Two additional questions:

1) How you control Commvault service startup during upgrade, especially on standby node?  For command line installation there is “/nostartsvc” parameter. But it is not clear what will happen with commvault services startup if you run Interactive Installer (GUI)?

2) Do you disable All Activity in CommCell properties during upgrades? Makes it sense? Could it somehow disturb upgrade process?

The installer should take care of it.  When you run the installer on a Standby CommServe you will have to select an Instance to upgrade, once you select CommServe instance, the installer should detect that it is a Standby CommServe and you will receive the following notification: 

This is a standby CommServe computer. DB updates will be skipped. Click Next to proceed

My standard process for anything involving / potentially impacting the CommServe:

• Disable the Scheduler
• Allow Running Operations to Complete / Suspend / Kill as appropriate
• Disable DDB Activity 
• Perform a CommServeDR Backup.