Upgrade CDP in clustered environment

In an Active/Passive SQL Server Cluster, the node on which the SQL Server Service is running at a point in time is considered as Active, and the other node is considered as Passive. In case the SQL Server Service is stopped on an Active node, the other node (which was Passive till now) becomes Active and the SQL Server Service starts running on it. This Active node might be different from the one on which the full installation was performed.

Upgrade steps

Upgrading CDP in an Active/Passive SQL Server Cluster requires the following steps:

• Making the Full Installation Node as Active

• Upgrading the Full Installation (Active Node)

• Upgrading the Failover Installation (Passive Node)

Making the full installation node active

To make the full installation active, start the SQL Server Service on this node.

Upgrading active node

To upgrade active node, refer to How to upgrade a standalone CDP.

Upgrading the Failover Installation

After upgrading the Active node, initiate the Failover (Files Only) upgrade at Passive node (where previous Files Only installation was performed).

To verify a Passive (Failover) node, check the installation name in the Add or Remove Programs dialog box. The instance name of the Failover installation contains the "failover" text.

The Files Only upgrade replaces only the binaries, and it does not interact with the metadata. Therefore, during the upgrade, there is no need to make this node Active.

To upgrade a Failover installation:

1. Run setup.exe. This launches an InstallShield Wizard that walks you through the upgrade process.

   The installer detects all the installed instances and list them.

2. Select Maintain or update the application selected below and click Next.

   Note

   If you select Install a new instance of this application, and no SQL instance is free, then the upgrade stops with a message stating that all SQL Instances have been used. If an SQL instance is available, then the upgrade proceeds as normal installation.

   

3. On the Welcome screen of the Installation Wizard, click Next.

   

4. On the Database Connection screen of the InstallShield Wizard, enter the database connection parameters and click Next.

   

   Note

   If the user upgrading CDP is different from the user that installed the instance, the Installation Wizard prompts for confirmation. Click Yes to continue upgrade.

5. On the NAE Server Configuration screen of the Installation Wizard, enter the parameters to configure NAE Server and click Next.

   

6. On the Provider Configuration screen of the Installation Wizard, enter the CDP configuration information and click Next.

   

   Note

   When upgrading from PDB to CDP, ensure the log level is selected on the Provider Configuration screen before proceeding to the next steps.

   The installer displays the progress of the upgrade.

7. The installer needs to copy the libcrypto-3-x64.dll and libssl-3-x64.dll files to C:\Windows\system32. As per Windows' design any file copied to C:\Windows\system32 gets redirected to C:\Windows\SysWOW64. On the Setup Status screen of the Installation Wizard:

   

   • Click Yes to disable the redirector from copying the files to the SysWOW64 directory.

   • Click No to manually copy libcrypto-3-x64.dll and libssl-3-x64.dll from C:\Program Files (x86)\CipherTrust\CDP_MSSQLServer\MSSQLSERVER to C:\Windows\system32 and click OK.

   Note

   Instead of manually copying the files, you can also add the installation path of CDP_MSSQLServer to the list of system variables and restart the SQL Server services.

   Upgrading from 8.12.0 and lower versions to 8.12.2

   When upgrading from 8.12.0 and lower versions, the installer will copy the libcrypto-3-x64.dll and libssl-3-x64.dll files to C:\Windows\system32.

   Upgrading from 8.12.1 to 8.12.2

   When upgrading from 8.12.1, the installer will first delete libcrypto-1.1-x64.dll and libssl-1_1-x64.dll files and then copy libcrypto-3-x64.dll and libssl-3-x64.dll files to C:\Windows\system32.

8. On the Upgrading user mapping screen, click OK. At this step, the old user mappings are migrated to the new columns.

   

   While upgrading, if migration of user mapping fails, following pop-up will appear on the screen. A folder, named, InstallationLogs is created at the installation directory. It contains a file named UserMappingUpgrade_failed.log which stores the list of database users for whom user mapping migration has failed.

   

   Caution

   Due to security reasons, it is recommended to delete the UserMappingUpgrade_failed.log file after you have viewed its content.

9. On the Update Complete screen of the Installation Wizard, click Finish to complete the upgrade.