Upgrading Microsoft SQL Server Editions on Non-CommServe Computer Clients

You can upgrade Microsoft SQL Server on non-CommServe computer clients that contain database packages (for example, Web Server, Workflow Engine, and Metrics Server). The following procedure ensures that older components such as .NET Framework are removed. You should consider performing a hardware refresh or a VM refresh at same time you upgrade to Microsoft SQL Server 2022 Standard Edition.

Before You Begin

Write down all Commvault-related components that are currently installed on the remote server computer (for example, Web Server, Workflow Engine, and Metrics Server). You will need to re-install these components in Step 6 of the Procedure, below.

To view the components that are currently installed, do the following:

1. From the CommCell Browser, in the Client Computers node, right-click a remote client and then click Properties.

   The Client Computer Properties dialog box appears.

2. On the Version tab, the installed packages are listed in the Update status area.

Procedure

1. Login to the remote server computer and then open SQL Server Management Studio.

2. Using SQL Server Management Studio, back up all Commvault databases to an accessible location as follows:

   1. Go to server_instance > Databases.

   2. Right-click a database, point to Tasks, and then click Back Up.

      The Back Up Database dialog box appears.

   3. In the Backup type box, select Full.

   4. In the Backup Component area, select Database.

   5. In the Backup set area, accept the default backup set name displayed in the Name box. If needed, you can specify a different name.

   6. In the Backup set will expire area, specify when the backup set should expire. By default, the backup set is set to never expire.

   7. In the Destination area, specify the location where the database should be backed up. By default, the database backup is saved to the local disk, in the MS SQL Server installation directory.

      If you want to specify a different location, click Remove and then click Add to specify the new location. Make sure the backup file is saved as <Database_Name>.dmp.

   8. Click OK.

   9. Copy the database .dmp file to an accessible location.

   10. For all databases listed in Step a., above, repeat Step b. to Step i., above.

3. Uninstall the database packages of the Web Server, Workflow Engine, and Metrics Server packages locally. For more information, see Uninstalling Commvault Locally from Windows Clients.

   Note

   When following that uninstallation procedure, you can selectively uninstall database packages (see Step 4, bullet 2 of the "Interactive Uninstallation" procedure on that page).

4. Uninstall the currently installed Microsoft SQL Server software. For more information, see the Microsoft documentation, Uninstall an Existing Instance of SQL Server (Setup).

5. Run the latest installer of the installed Commvault feature release on the same hardware. For more information, see Installing Commvault Locally Using the Download Manager.

   1. During the installation procedure, select the same Commvault instance, and then select Add Packages on the Install Option page, as follows:

      

   2. Select the same Commvault database packages that were selectively removed in Step 3, above.

   3. On the Database Install Option page (see below), select Use Existing Database, and then select the database packages that you added and that you performed a .dmp database backup for in Step 2, above.

      

   4. On the Database Install Option page (see above), in Database Dump Location, enter the location of the .dmp database backup file that was created in Step 2, above. This DR backup file is automatically upgraded if necessary.

   5. Click Next.

   6. After installation completes, click Finish.

6. Redeploy any custom workflows for the Workflow Engine.