Appliance Patch Release Notes v2.1.1 (

Last modified


Last modified - 06/10/2014

Document attachment - Release Notes pdf

This document provides release notes identifying open issues with the software version installed on your appliance. The document is broken down into following sections:


What's New in v2.1.1 (

This version has the following changes:

  1. Improved Disaster Recovery: 

The previous implementation involved a lengthy bucket-to-bucket data copy that left unmanaged backups and duplicate data which required manual cleanup. With this patch release, workflow will transfer the bucket ownership cutting down significantly​ on the total DR time. Refer to KB article on DR flow for details.

  1. Support for Azure China:

Starting with this release, StorSimple appliance has support built-in for product launch in China. The supported fields in Web UI will now accept and display Chinese (GB18030-25) characters.  

  1. Supported Platforms: 

There are changes to the list of supported platforms from this release onwards. Refer to StorSimple System Requirements for details on the supported platforms.

  1. Call Home Privacy Statement Changes:

The StorSimple Call home Privacy Statement has been changed in this release. After upgrading to this version, you will be prompted to review the call home privacy statement to learn more about how the information collected in call home is used. You can then choose to enable call home and configure email notification settings. 


Issues Resolved in v2.1.1 (

The following issues have been addressed in this software version (


ID Description
CSC-4659 Additional pre-upgrade checks to improve the upgrade experience.

Fix vulnerabilities by:

  • Avoiding plain text display of cloud account key
  • Allowing only encrypted configuration file download
CSC-4508 Limit ARPing only to the network interface being configured.
CSC-4481 Administrator password complexity requirements have changed. The password must contain a minimum of 8 characters and should be a combination of uppercase, lowercase, numeric and special characters.
CSC-4476 In Web UI, default  access changed to HTTPS from HTTP. 
CSC-4418 Cloning of a volume from a backup failed when SSDPC used host network for communicating with the appliance rather than iSCSI interface.
CSC-4414 Under rare conditions, iSCSI assert condition is seen when deleting old backup and creating a new one.


CSC-4409 In Web UI,  space is not allowed for a cloned volume name.
CSC-4384 Disaster Recovery bucket information not preserved when a cloud configuration is edited
CSC-4382 Problems with enumeration of VSS writes caused SSDPC backups to fail.
CSC-4379 Improve registry restore times for disaster recovery when there are a large number of backups.



Add retry logic for bringing volumes online after the reboot of active controller.

In Web UI, add an alert for registry restore operation during disaster recovery.

CSC-4326 Upgrade may fail if the SSDs have been replaced with newer SSDs.


Known Limitations for v2.1.1 (

The known limitations for StorSimple software version 2.1.1 ( are tabulated below.  The limitations reported in this version of software are marked with an *.  All the other limitations have carried over from previous releases.




Comments and/or Workarounds


Using quick format to re-format a large volume on Windows Server 2012 may take a long time.

On Windows Server 2012, the thin-provisioning feature is enabled when using a StorSimple iSCSI volume. It is recommended that you delete a thin-provisioned volume and create a new volume instead of reformatting. If you still prefer to reformat a volume, apply the following command prior to the reformat to avoid space reclamation delays:
fsutil behavior set disabledeletenotify 1

Once the formatting is complete, apply the following command to re-enable space reclamation:
fsutil behavior set disabledeletenotify 0


If the internal platform firmware engine is rebooted, the system software may sporadically lose access to vital information about the health of each hardware component.

In such a scenario, the hardware page would not be able to display correctly the status of all the hardware elements. To avoid this issue, please force a reboot of the active controller which would automatically trigger a failover in the system.

CSC-4255, CSC-4231

UI errors with Internet Explorer versions older than 8.

Internet Explorer version 8, 9 or 10 are supported with the StorSimple web UI. Please make sure to install the latest update available for the version of choice.


CHAP initiator secret length must not exceed 255 characters, even though Web UI allows 256 characters.



A Google cloud account restore during configuration import may lead to "Forbidden Access" to the cloud.

This is a known Google limitation on the number of different devices that can use the same Google credentials and authentication tokens. If possible, avoid performing multiple imports of the same Google account. You can also contact StorSimple support for alternative solution to address this known limitation.


SCSI ABORT may occur with Round Robin multipath policy set on Centos host. iSCSI sessions might get disconnected/connected resulting in high host I/O latencies.

There is no known workaround for this issue at this time.


When the fingerprint type is altered for a custom type volume, the write and read performance can be impacted.

The performance can be reduced because the data may need to be de-duplicated again based on the different type; such operation requires additional CPU cycles as well as extra reads and writes from storage. Once the entire volume content is fully rewritten, the write and read throughput will stabilize to the optimal value again.


Printing reports in portrait orientation may overflow and not print correctly.

Printing of reports is supported in only Landscape orientation.


When the appliance is powered off and quickly powered on, some drives show up as missing. 

This issue has been observed very sporadically when forcing a quick power off/on through a managed APC that would cut the power to the appliance for less than 1 second.
As a work-around, please ensure that the power is applied again a few seconds after the power-off (what is usually called a "delayed power-on" in a managed APC).


In rare instances, on resetting the active controller, the Host I/Os may get aborted.

In some high load scenarios, host I/Os are aborted because the appliance takes more than 20 seconds before completing the operation. The issue subsides after the load reduces.
As a workaround, a reduction in host load, and/or a failover of the controller is recommended.

CSC- 3217, CSC-2335

Printer-friendly version of reports does not work in IE9 and Firefox.

Use the browser print option for printing out reports.


A canceled Cloud Clone or Cloud Snapshot restore/clone job may resume after a controller failover.

If the user cancels the restore/clone job, and then triggers a controller fail-over or the system fails over automatically for some other reason, then a canceled job will resume unless the cancel action has been completely processed by the system.
To work-around this issue, the user needs to cancel the job again and ensure no more fail-overs are triggered until the cancel action has been fully processed by the system.


A different state may be displayed on the serial console when the system is in recovery mode.

Only one controller may display the management console screen, with the state shown as "OFFLINE".


If one of the Web UI charts is kept open in Auto-refresh mode, the refresh may stop after some time.

Normally this issue can be overcome by opening a new browser session and select the same chart display page again with Auto-refresh mode.
If the Web application fails to open, i.e. the login page does not come up; the issue can be worked around by forcing an active controller reboot.


Rate limiting enforces the lowest limit value configured across cloud configurations.

When multiple cloud configurations are setup and rate limiting is enabled in more than one, the overall throughput towards the cloud will converge over time to the smallest rate limiting value configured (as opposed to the sum of the configured rates).


An existing iSCSI session remains active even after disabling the iSCSI checkbox in the UI.

The "iSCSI Enabled" setting is effective only after a controller reboot/failover. The existing sessions are not altered, therefore:

  • Existing iSCSI sessions from hosts remain active after disabling the checkbox
  • New iSCSI sessions to a target are successful using the IP address of the interface which is unmarked as "iSCSI Enabled"

In order to overcome this issue, please reboot the active controller. The automatic failover will ensure that the desired configuration is applied correctly from that point onwards.


Active Directory domain user is able to login with old password after the password is changed in the domain.

This is due to the old password being cached by the Domain Controller server that has been configured. This password remains available when authentication occurs. Since the StorSimple application cannot force a flush of the old passwords, please connect to the Domain Controller server and perform the necessary flush operation.


In the Hardware page, the standby controller appears in a different state when it has been shut down or pulled out.

There are no negative side effects on the system behavior.


Known Issues for v2.1.1 (

The known issues for StorSimple software version 2.1.1 ( are tabulated below.  The issues reported in this version of software are marked with an *.  All the other issues have carried over from previous releases.




Comments and/or Workarounds

CSC-4675* When configuring new email settings or editing existing ones via Notification Settings page, the user is allowed to specify only a single email address.

Please use a distribution list ( fronting multiple emails) as a workaround.

If you are upgrading, and already have multiple emails in the “email to” field, all accounts will receive the emails. However, editing an existing setting will restrict you to provide only one email address.
CSC-4672* SSDPC should only be installed in the C: drive of your Windows host. Backups will fail if the installation is in any other drive.  
CSC-4657* There are known issues with pop-ups and UI not rendering properly.

To workaround this problem, perform the following steps:

  1. Clear the entire cache.​
  2. Press Ctrl+F5 to refresh the browser and the UI.
CSC-4650* In some instance, Web UI hangs due to mono issues.

To workaround this problem, perform the following steps:

  1. Access the appliance using management serial console.
  2. In the command window, at the prompt type:

web restart

CSC-4649* There is an issue where the Y-Axis of the Deduplication Report can show Trillions of Bytes instead of Gigabytes.  
CSC-4636* A temporary warning alert is seen immediately after upgrading to this patch release: "Backup Registry Incomplete - Rebuilding catalog. If you recently upgraded, this should automatically resolve. If this alert persists for more than 24 hours or you did not recently upgrade, please contact Microsoft Support."

This is a transient alert that requires no user intervention. The alert automatically clears in less than 24 hours after the catalog is completely rebuilt. 

If you have not upgraded the software and see this alert, or if the alert persists for longer than 24 hours, please contact your Microsoft Support. 

CSC-4631* The maximum volume size in this release has been limited to 64TB. After you have upgraded to this version of software, volumes larger than 64TB will fail volume size check.  Create new volumes to migrate data from volumes larger than 64TB.
CSC-4609* If the original appliance is alive and clones need to be accessed on the secondary appliance, please do NOT delete cloud snapshots on the original appliance.  
CSC-4607* If the SSDPC installation package is copied in a folder with a Chinese name, SSDPC cannot be extracted from this folder.  Ensure that SSDPC installation package is always copied into a folder with an English name and then extracted.
CSC-4529* In some instances, you may see an error on Cloud credential verification that reads "Could not synchronize the device time. Please verify that your NTP servers are properly configured, the servers are online and reachable, and that the network between your device and your NTP servers is operating correctly."​ In most cases, retrying the operation or simply refreshing the browser solves this issue.
CSC-4248* After a DR from appliance A to appliance B, backups that are deleted on appliance A will continue to be visible on appliance B. Attempts to clone or restore the deleted backup will fail.  This is a known issue and the workaround is to manually delete the corresponding backup(s) on appliance B.
CSC-4413 With recent Chrome version 31.0.1650.57, the Web UI page for QoS template may have issues displaying the pop-up for creating the template. The issue is related to cached data and can be resolved by a complete refresh of the page using Ctrl+F5.


"Use SSL" checkbox in cloud credentials dialog is unchecked by default for all cloud service providers, resulting in cloud communications over HTTP if the user doesn't check it before saving the configuration. This is a change in behavior compared to prior versions. 

It is recommended that SSL is enabled to ensure validation of cloud service authenticity. A valid SSL server certificate is required to be installed on the cloud service side to establish SSL communication.


A valid backup policy schedule cannot be saved in 'Create Scheduled Policy' dialog, following a failed save attempt of an invalid schedule.

Close the 'Create Scheduled Policy' dialog and reopen to create a valid schedule.


The web UI displays an Oops! error when a 31 or 32-character long encryption key is entered in the corresponding field in Cloud Configuration.

When a 31 or 32-character key is to be configured, either type or copy/paste the key string without pressing the Enter key at the end.


When configuring a monthly backup policy with an invalid day for the selected month, an Oops error is presented.

Select a valid day for the month.


When performing a backup registry restore on other appliance, while original appliance is still active, any backup deleted on the original appliance will continue to appear on the second appliance until it is either manually deleted or expired per configured schedule. An attempt to restore from a backup run that appears in the catalog but has been deleted on the original appliance will result in an error notice and the operation will not proceed.

Manually delete the invalid backup on the second appliance or let it expire if expiration date is configured.

CSC-4159, CSC-4154

The Web UI may briefly display an Object Reference Error or a Server Error.

In rare circumstances, the Web UI becomes inaccessible and displays the error mentioned. The Web UI only remains in this state for a brief period of time and it will become accessible again after a refresh of the page.


Migration Upgrade: Stage 3 of 8: 'Converting data to new format' shows percentage complete above 100%.

This can happen if new volumes are created during stage 3 of upgrade. This is not a severe issue and no user action is required. The upgrade will progress once the new volumes have been properly handled.


Login to the UI home page may get stuck indefinitely following a fail-over.

This can happen if a fail-over occurs in an appliance with no gateway configured for cloud access.
A possible work-around, if acceptable in the customer network topology, is to configure the gateway for the MGMT interface using the console connection. Once the UI is accessible again, please re-configure the network interface settings with the appropriate gateway details.


Web UI is not reachable after 2.0.1 to 2.1.1 upgrade.

Please contact Customer Support. The workaround is to restart the management service from serial console access.


The Web UI should not allow preferred LUN settings greater than 255 for a volume.

Avoid setting preferred LUN of a volume to a value greater than 255. Preferred LUN of a volume should be within 0-255 range.


The web UI may not be accessible for few minutes during the upgrade from 2.0.3 to 2.1.1.

During the upgrade from version 2.0.3 to version 2.1.1, the Web UI may display the error message "Operation completed with status = CSA_STATUS_SERVER_API_DISABLED" for a few minutes during a specific phase of the upgrade. Please try to access the UI after a couple of minutes and the monitoring of the upgrade progress should be available again.


When a volume is deleted without removing it from a volume group, further backups on the VG for remaining volumes will fail with "One or more of the source volumes unavailable (Backupexception)".

Edit the volume group and save it again without making any changes. Any further backups will now succeed.


Deletion of a volume during upgrade can cause the upgrade to fail.

This failure does not impact the Host/Application I/Os. The upgrade operation can be retried but the volume deletion operation should be avoided until the upgrade process is complete.


After a successful pre-validation on the Software Upgrade screen, the Start Upgrade button may not be accessible.

As a work-around, please retry the operation after waiting for an hour. If the issue still persists, restart the active controller and then start the upgrade process again.


The 5000-7000 series appliance controller may reboot under heavy load.

Under very rare circumstances, the controller may become very slow or unresponsive. When the system detects such a situation, a reboot of the active controller is automatically triggered and a failover to the standby controller occurs. The system then continues to operate normally without any host disruption. If this doesn't occur, please contact StorSimple support to restore the system to a fully functional state.


Upload of the upgrade package for version 2.0.3 may stop abruptly.

This is generally seen when the upload reaches 35-40%, in particular when the system is operating under heavy load. This issue is addressed in build, therefore it is recommended to perform a patch upgrade to build first and then again upgrade to version 2.0.3. 


The cloud properties popup may not close properly when clicking on the X button on the top right hand corner.

As a work-around, please refresh the whole page and reopen the pop up again.


Invalid cloud configuration/credential settings may lead to the entire system becoming very slow connecting to the cloud for valid accounts.

Please contact StorSimple support to help resolve the problem and bring the system back to its full functionality. 


Using invalid credentials for Web Proxy settings may result in a controller failover.

If invalid credentials have been input in the Web Proxy Settings in Web UI, the active node will reboot and there will be a cluster failover. Ensure that valid credentials are applied for the Web Proxy settings.

CSC- 3224

In Firefox 3, while configuring QoS templates, the Save/View Timeline buttons may get disabled.

This issue can be observed only in some specific sequences of operations involving deleting and creating multiple QoS templates. The issue can be overcome by refreshing the browser page and then attempting the configuration of the QoS template again.

CSC- 3222

In RDP sessions Web UI popups cannot be closed by clicking on the x in the top right corner for the first time.

Click on the red icon again to close the popup.

CSC- 3211

The Web UI displays the error "Server Error:'~/Telerik.Web.UI.WebResource.axd' is missing in web.config. RadScriptManager requires a HttpHandler registration in web.config."

There is a rare known issue in which the Web UI becomes inaccessible and displays the error mentioned. The Web UI only remains in this state for a brief period of time and will become accessible again within one minute. No user intervention is required.


Web UI may render incorrectly on a restarted appliance.

Accessing the Web UI on a new browser window will resolve the issue.


Under rare circumstances a disk failure may cause the system to go offline.

There are some corner case scenarios that may occur with a high stress read workload. When the StorSimple software detects a failure in a drive from which it cannot quickly and easily recover from, it intentionally brings down the system in order to protect the data integrity. Should such an event occur, please contact StorSimple support to address the issue and restore its full functionality.

CSC-3042, CSC-3067

The appliance controller reboots when an I/O to the internal disks takes an abnormally long time to complete.

Under extremely rare circumstances, an I/O to a drive (SSD or HDD) may take an abnormally long time. The StorSimple software detects such an incomplete operation and forces a controller fail over to ensure that the system can continue serving I/Os without causing application timeouts.


Rebooting the controller from the shell results in a "500 Internal Server Error" in the Web UI.

This issue is caused by a rare race condition when web requests coincide with the web service starting up. The problem can be worked around by forcing an additional controller reboot.


When a configuration restore/import fails, the same cloud account may be configured multiple times.

Upon configuration restore or import failures, in few rare circumstances some portions of the configuration are restored/imported. In case the restore or import operation is repeated again, the same cloud account might be configured multiple times. In order to work around this issue, please check the configuration after the failure and delete any partially imported information, especially the cloud account portion.


Multiple failovers performed under heavy load may result in loss of iSCSI connection between the host and the appliance.

Under heavy I/O, if there are failovers performed there is possibility of active controller reboot. This may result in loss of iSCSI connection between initiator and target. In order to restore the proper connectivity, reboot the appliance.


Under stress testing of the system failover, the host may lose access to the appliance volumes.

When performing stress testing of the system failover, inducing continuous failures (artificially), a Windows host may lose access to the volumes. In order to restore the volume access, please force an iSCSI rediscovery of the target or power cycle the host.


Microsoft iSCSI initiator doesn't support LUN ID 255.

Use a LUN ID of 0 to 254.


Contacting Technical Support

Should you encounter any issues with your appliance, please do not hesitate to contact StorSimple Technical Support at:

  • Telephone: 1-800-642-7676
  • Web:
    • In the page presented, click on plus icon to expand the 'Get Technical Support' node. In the expanded pane, click on 'Get Microsoft Technical Support'.





Page statistics
3162 view(s) and 89 edit(s)
Social share
Share this page?


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