Upgrading The following topics explain how to upgrade to BrickStor SP Release 23.2 for single-node configurations. Please contact RackTop support for specific upgrade instructions if you are upgrading from release 21.x or prior. Please contact RackTop support to arrange for assistance when upgrading a BrickStor SP HA cluster configuration. If your BrickStor is in an air-gapped network or otherwise unable to download the latest version from the public internet, you can request a download link at https://support.racktopsystems.com or by contacting RackTop support to arrange alternative means. Pre-upgrade Considerations There are some important items to note when upgrading from Release 22 to Release 23.2. The email and report system has been greatly improved in Release 23.2, but this means any existing email and report configurations will not be carried forward and will need to be configured after the upgrade is complete. Please review these settings and note them where necessary prior to commencing with the upgrade. Upgrading a Single Node BrickStor using the latest BrickStor SP Manager The following steps demonstrate the upgrade process for a single, standalone BrickStor SP configuration. 1. Beginning the upgrade Connect the BrickStor SP Manager to your appliance. Choose Upgrade OS / Manage Versions to perform the upgrade. 2. Download the new OS version Choose the version to download by clicking the Download link. 3. Activating OS Version Once downloaded, click the "play" icon to activate at next boot. 4. Commit the OS Upgrade Change Commit the change in the Changes pane. 5. Reboot the System The BrickStor SP appliance will now reboot into the new version of the OS. After it does so, navigate to its IP address or hostname in a web browser and log in. You will be asked to review and accept the Terms & Conditions before proceeding. Once you have done that, you will be able to download the new version of the BrickStor SP Manager. Post-Upgrade Tasks Once you are connected to your BrickStor SP system using the new version of the BrickStor SP Manager, be sure to do the following: Reconfigure any SMTP email settings. Review and configure any desired report settings. Review the rest of this documentation for new features that you may wish to configure or activate. BrickStor SP Cluster Upgrade BrickStor SP Upgrade Prerequisites When upgrading BrickStor SP it is always recommended to ensure that any encryption keys are exported and backed up. Follow these steps if using encrypted datasets or have encrypted storage pools. Navigate to the Encryption Tab. Click the Resync Encryption Keys with Peers Button. Click the Export All Encryption Keys button. A prompt denoting the entrance of a password will present. Once entered, click the Export All Keys button. This password must be recorded in a password manager or printed. If lost, the exported key data will be unusable. A Windows File Explorer window will present a default file name. Click the Save button. A prompt denoting successful key export will present showing the Encrypted Key File, as well as the Key Report File. BrickStor SP OS Upgrade Procedure The following steps will outline the process by which the BrickStor SP Manager and OS is updated (for the purposes of this example, the example cluster consists of a Node A, Node B, and a Witness. Node A is considered the Passive Node, and Node B is considered the Active Node. If the system is running two Active Nodes, consider Node A to be the Active Node carrying the lower serving load): If at any point the upgrade process is inhibited, contact the support team. Upgrade Node A To begin the upgrade process of the BrickStor SP Manager, first navigate to the System tab of Node A. In the Systems tab, click the Upgrade OS/ Manage Upgrade Versions button. This will take you to the OS Upgrade screen (shown below). image:up-clusteros-1.png[alt="New OS Available", align=left] In the OS Upgrade Screen, navigate to the new version (in this case, 23.4). Click the Download icon to the right of the release version of the desired upgrade (shown below). image:up-downloadv-2.png[alt="Download New Release", align=left] A prompt displaying the downloading of the release version will present, as well as a progress bar. Once download is complete, click Activate. Navigate to the System tab. A message stating that a Different OS will run on next boot will present (shown below). Click Reboot. A window will present on the right-side of the screen showing the active changes to the system. This will display the changes that will occur to the system when rebooting. Click the checkbox to acknowledge the warning. Click Commit (1) Change(s). A prompt will ask if you want to migrate resources and disable node Click Yes. Once the node has rebooted, ensure that it is enabled. Node A must be manually re-enabled before upgrading Node B by clicking the play button next to Node A on the HA tab in the BrickStor SP Manager. Verify this via the navigation to Node B. Click the HA tab. Ensure that HA is enabled. Exit the running instance of the BrickStor SP Manager Client. Upgrade Node B Repeat steps a - e on Node B to upgrade the second node. Navigate to the BrickStor SP web interface. Entering the IP of the BrickStor SP Node A into an internet browser search bar. Log in to the website with the admin Username and Password of Node A. Download and install the standalone BrickStor SP Manager client. From the Witness system, download the High Availability Witness Binaries (this will be used in the Witness Upgrade Procedure and Confd Upgrade Procedure). Launch the standalone BrickStor SP Manager client (downloaded in step 3c). The BrickStor SP Manager will automatically load the credentials of the system. Select Node A, verify that the cluster is running (the homepage will display that the HA system requires an upgrade). Witness Upgrade Procedure (Windows) The following steps will outline the process to upgrade the Witness: Log in as administrator. Navigate to Windows Services and locate RackTop High Availability Service. Right-click on RackTop High Availability Service and click Stop to stop the service from running. Navigate to the location of the downloaded .zip file in the Windows File Explorer. Extract the .zip file using default system processes. Once located, right-click on hiavd.exe and click Copy. Navigate to the location of the outdated hiavd.exe on the system. This will be in either c:\racktop or C:\Program Files\Racktop\BrickStor\ Locate hiavd.exe and right-click it. Click Paste. Confirm the replacement of the file. Navigate to Windows Services. Refresh the list of services. Locate RackTop High Availability Service. Right-click RackTop High Availability Service. Click Run. On the BrickStor SP Manager, click the refresh button on the top right of the screen to ensure the Witness has been upgraded (The HA tab will display green LEDs, and the warning message denoting a version mismatch will disappear within 30 seconds). Confd Upgrade Procedure (Windows) The following steps will outline the process to upgrade confd: Navigate to the location of the downloaded confd.exe file in the Windows File Explorer (the same directory as the hiavd.exe file). Once located, right-click on confd.exe and click Run As Administrator. A command prompt window will present. Enter 1 to install. Press Return. Enter 0 for instance number. Press Return. Enter y to confirm the installation. Press Return. Enter y to confirm the update. Press Return. Enter y as response to backup query. Press Return. Enter y to start the confd service after installation. Press Return. Press Return to exit and close the window. Navigate to the Windows File Explorer and locate the new confadm.exe. Right-click the confadm.exe file. Click Copy. Navigate to C:\Program Files\RackTop\BrickStor\confd\00. Right-click the existing confadm.exe. Click Paste. Navigate to Windows Services. Refresh the list of services. Verify the new confd service is running. Open a command prompt and cd to C:\Program Files\RackTop\BrickStor\confd\00. Enter confadm member show status to confirm the cluster is healthy by assessing that all three nodes are online and communicating.