Upgrade to 2.0.1 Software

Last modified
<< PrevNext >>

This step in the process requires the user to upgrade the software from 1.2.2 software to the released version 2.0.1 software. The 2.0.1 software can be downloaded from the StorSimple Support site. This is a time-intensive step. Depending upon the amount of data that resides on your appliance, it may run into days. This step consists of the following tasks:

Back to Top

Pre-requisites

Prior to upgrading to 2.0.1 software, please ensure the following -

  • All the steps enumerated in 'Preparing for Upgrade' section have been completed.
  • Ensure that 'Hardware Upgrade' has completed successfully without any errors.
  • 'Firmware upgrade' has completed successfully without any errors.
  • System is running 1.2.2 software.
  • Navigate to Home → Manage → Hardware and ensure that all the components are healthy (as indicated by green status).
  • Access the StorSimple Support page to download the installation software. For 2.0.1 software, use "storsimple-2.0.2.29-aggregate-patch-install-patch.tar".

Back to Top

Upgrade the Standby Controller to 2.0.1 Software

The first step is to upgrade the software on the standby controller to 2.0.1 software. Perform the following steps to upgrade the software version on the standby controller:

  • In 1.2.2 software, navigate to Home Manage Software Upgrade page.

ElbaUpgradeNG2S.png

 

  • Click the Browse button. Select package “storsimple-2.0.2.29-aggregate-patch-install-patch.tar” and click on Upload.

ElbaUpgradeNG1S.png

 

  • The software will now begin to upload. You have the option of stopping and then resuming the upload by using the Pause and Resume buttons.
  • Once the upload is complete, the Upgrade button will become available. Click on Upgrade.
  • A confirmation dialog will be presented. Type in "CONFIRM" and click Confirm.

 

 Upgrade5.png

 

  • You will be directed to the Software Upgrade screen. Click on I Agree.

ElbaUpgrade4.png

 

  • The software upgrade will start and an appropriate message is displayed on the screen.

Back to Top

Monitoring the status of the cluster

Once the standby controller is successfully upgraded, perform the following steps to monitor the status of the cluster.

  • Navigate to Home Manage Hardware. In the Shared Components view, check the status of ‘Cluster’ component, it will show as DEGRADED which indicates that the standby controller is being upgraded. Also, note that standby 'Cluster Node’ will be reported as FAILED.

 

ElbaUpgrade5a.png

 

ElbaUpgrade5b.png

 

  • Watch the screen until the ‘Cluster’ and the standby ‘Cluster node’ shows ‘Healthy’ again as shown below.

 

ElbaUpgrade8a.png

 

ElbaUpgrade8b.png

 

  • Once the Cluster component status changes to HEALTHY, it indicates the successful upgrade of standby controller.

Back to Top

Failover and transfer of control

The active controller is now ready to be upgraded to the new software version. The controls will be transferred to the standby controller that will now resume operations as the new active controller. This process is also referred to as “Failover”. The user needs to perform the following steps:

  • The user is required to restart the active controller by clicking on Restart Active Controller button.

ElbaUpgrade8c.png

 

  • You will be notified with the following message.

 

Upgrade12.png

 

  • Click OK to restart the ‘Active Controller’.
  • During the restart process, the following screen is shown to the user. At this point, the standby controller (with the upgraded software) takes over and becomes the active controller.

ElbaUpgrade9.png

  • Once the failover has completed the user is directed to the login screen.
  • Login to the Web UI and proceed to the next step.

Back to Top

Upgrade the new Standby Controller to 2.0.1 Software

Navigate to Manage Software Upgrade. Repeat the steps listed under Upgrading the standby controller and Monitor the status of the cluster. As soon as this controller finishes upgrading, the active controller will fail over automatically. The new standby controller will now become active.  

Note.png Note: Do not 'Restart Active Controller' at this point. A restart will cancel the upgrade and system will revert to 1.2.2 software. Instead follow the steps in the next section.

 

Back to Top

Monitor 2.0.1 upgrade progress

Perform the following steps to monitor the upgrade progress:

  • After login, you will be directed to the home page. Note the presence of an upgrade alert shown as a banner message.

ElbaUpgrade11.png

 

  • Navigate to Home Manage Software upgrade
  • The upgrade will involve four migration stages for the metadata, data and the configuration.
  • Note that host I/Os are always accepted throughout the upgrade process. Existing backup schedules or manually triggered backups may fail during some phases of the upgrade. This failure would happen in the "3rd phase", and will last the duration of the 3rd phase. Existing backup schedules will automatically start working once this phase in the upgrade is complete.
  • The following sections describe the system behavior as the system progresses through the rest of the upgrade. Note that this is purely informational. The user is not required to actively participate with the system at this point. The upgrade happens silently in the background.

1st Phase 

  • The metadata and data format has changed going from 1.2.1 2.0.1 software. In this phase, space is created for the new metadata and data format so that for a short duration, both the old and the new formats can co-exist. 
  • The upgrade stage is displayed as "Preparing space for new data format" during this phase.
  • Clicking on View Details link will display the detailed information about the upgrade progress.

ElbaUpgrade19S.png

 

  • This is a lengthy stage and can take up to a few days to complete. In this phase, user is allowed to take backups.

 

2nd Phase

  • This is a relatively quick phase.
  • It involves applying configuration changes to the metadata. 
  • The upgrade stage is displayed as "Converting configuration to new format".

ElbaUpgrade16.png

 

3rd Phase

  • The 3rd phase involves migration of volume metadata and data from the 1.2.1 to 2.0.1 software.
  • This is a time-consuming process and can take up to days depending on the amount of data residing on your appliance. For a system provisioned with 10TB of volume space, containing about 2TB of actual data, with 150 snapshots/cloud snaps, it will take approximately 2-3 days for the 3rd phase to complete.
  • In this phase, the upgrade stage is shown as "Converting data to new format".

ElbaUpgrade14.png

 

  • The user is not permitted to change the appliance configuration during this period. If the user attempts to change the configuration, the following exception will be presented:

OtherConfigOperationErrorDuringUpgrade.png

 

  • Automatic or manual backups triggered during this phase are failed (from either the MMC UI or from the web UI) and will appear as failed jobs in the Jobs page.

BackupErrorDuringUpgrade_S.png

 

  • The user can expect to see reduced host I/O performance during this phase. The host I/O performance will typically drop by about 30% in comparison to the performance on the 1.2.1 version of software.
  • When the migration is complete, the two controllers automatically reboot one after the other. This process is usually non-disruptive but there is a possibility of intermittent downtime. Transient errors may be displayed in the UI in case the system is disrupted.
  • When this phase is complete, the new 2.0.1 UI is loaded.
  • The data and metadata now exist in the new format.
  • The upgrade is complete for all purposes and the system can be used normally.

 

4th Phase 

  • This is the final phase of the migration and involves cleaning up of old metadata and data. Additionally, the data and metadata partitions are optimized for improved performance.
  • This stage could take up to 14-16 hours for completion on 5010 models and longer on higher models.
  • The upgrade stage is shown as "Optimizing data layout". In this stage, the upgrade is complete for all practical purposes and the user can operate the system as he would in normal conditions. In comparison to 1.2.1. software, the system performance will be at par or better during this phase.
  • Once this phase is complete, the user will no longer see the "Upgrade Progress" banner at the top of the Web UI pages.
    ElbaUpgrade18.png

 

  • Note that at this point, the software version displayed is for 2.0.1 software.

Back to Top  

Upgrade Verification

  • A final reboot is recommended upon the completion of Phase 4.
  • After all the reboots, the user will be directed to the login screen. Login to the Web UI and navigate to Manage Hardware page and ensure that all the components are 'healthy' as indicated by a green status.
  • Next, access Help Technical assistance and ensure that the software version displayed is 2.0.1 (2.0.2.29 in this case). This screen will also reflect the upgraded system model number.

Back to Top

<< PrevNext >>
Page statistics
1952 view(s) and 154 edit(s)
Social share
Share this page?

Tags

This page has no custom tags.
This page has no classifications.

Comments

You must to post a comment.

Attachments