Skip to end of metadata
Go to start of metadata

For major SoftNAS StorageCenter upgrades that require downtime, Buurst has provided a way to protect replications and SNAP HA pairings while also keeping storage connectivity and data access uninterrupted. To check whether an upgrade is required, click Settings > Software Updates in the main menu on the left.

Ensure that both nodes are in sync by forcing the event through SoftNAS StorageCenter. Sign in to each node of the HA pair to be upgraded in separate browsers to more easily switch between nodes.

Note: Ensure that source and target nodes have been established. For the purposes of this document, the following terminology will be used:

Original Status

Document Reference

Source Node

Node A

Target Node

Node B

 Note: Please note that since the introduction of 4.3.0 the upgrade process is slightly different now. So please follow the steps in each Section closely.

Note: If upgrading from 4.2.4 to 4.3.1 please refer to Section A. 

Note: If upgrading from pre-4.2.4 to 4.3.1 please refer to Section B.

Note: Buurst recommends a reboot of your system be performed prior to performing a system upgrade. This ensures that the upgrade is performed on a stable system. 

Note: Buurst also recommends all AWS customers to take a snapshot of their root volumes prior to performing a SoftNAS upgrade. More details can be found from the link here.

Warning: If putting only one node into maintenance mode, synchronization need not occur. If both HA nodes need to be placed into maintenance, a forced synchronization will need to occur.

Section A: Upgrading from 4.2.4 and above to 4.3.0 or Later 

  1. In the SoftNAS StorageCenter interface for Node A, navigate to the SnapReplicate / SNAP HA menu. Click Action and then Replicate Now as shown below.

    To verify sync completion, watch the Event Log at the bottom of the UI. Click Refresh to ensure current status visibility if necessary.

  2. In the SoftNAS StorageCenter interface for Node A, navigate to the SnapReplicate / SNAP HA menu. Click Action and then Deactivate. 
  3. Next, in your browser once more, enter the IP of Node B, and log in.  Navigate to Settings/Software Updates and click Apply Update. Confirm the update is successful and refresh the browser

  4. After update, login to Node B and navigate to the SnapReplicate/SNAP HA menu.  Click Action and then Takeover. Node A will shut down and Node B will be promoted to Primary.

    Note: Please note that in rare cases if you perform the takeover and end up with two Primary nodes it is okay. Just reboot node A and continue from step #5  

  5. Power on Node A.  HA will still be deactivated on this node as it was shut down by the takeover operation. Navigate to the SoftNAS StorageCenter for Node A, then to Settings > Software Updates and click Apply Update. Wait for the confirmation that the update has been successful and allow the browser to refresh itself. Node A will automatically reboot to complete the update process.

  6. Confirm the Update is successful and refresh the browser.

    Restore HA

    Reactivate Replication

  7. In the SoftNAS StorageCenter interface for Node A, navigate to the SnapReplicate / SNAP HA menu. Click Action and then Activate. Click Yes to confirm.

  8. The system will then automatically synchronize using Deltasync. However, if Delsync fails please contact SoftNAS Support ASAP before doing anything else

Section B:  Upgrading from pre-4.2.4 to 4.3.0 or Later

  1. If upgrading from a version earlier than 4.2.4, we need to ensure by using command line that all SoftNAS HA services have been stopped. This additional step is performed after Step 5 of Section A. Enter the following command from within the SoftNAS UI, by following these steps:

    1. Under Settings, select General System Settings.

    2. This will open a console known as Webmin. Select Others from the list on the left. Select Command Shell

      In the space provided under 'Module Config', enter the following command: 
      # service softnasha stop 

  2. Close Webmin, and return to SnapReplicate/SNAP HA. Complete the upgrade process as directed in Section A