Appliance Release Notes v.1.2.1

Last modified

Welcome

Thank you for purchasing StorSimple's Storage Appliance. This document provides release notes identifying open issues for the software version 1.2.1 installed on your StorSimple Appliance. This document is broken down into following sections:

New Features in v.1.2.1

The new features introduced in software version 1.2.1 have been tabulated as below.

 

Feature Name

Description

VMware Ready Certification

Enables use of StorSimple appliance models 5010 and 7010 for data center deployments with virtualized servers using VMware ESXi 4.0 and 4.1.  StorSimple is the first hybrid cloud storage solution certified for use with both VMware and Microsoft

Integrated Data Protection for Windows, VMware, Linux, and Mac

In addition to the VSS-compliant Snapshots, Cloud Snaps, and Cloud Clones provided in OS v1.1 for Microsoft environments (enabled through the Data Protection MMC snap-in), StorSimple now supports management of Snapshots, Cloud Snaps, and Cloud Clones in the appliance web GUI for Windows, VMware, Linux, and Mac environments

Fully-Independent Live Backups

Using Cloud Snaps or Cloud Clones, backup copies can be accessed by a secondary appliance, enabling a multitude of use cases such as live backup validation in the cloud, disaster recovery, deployment of staging/testing/lab environments, migration of applications to the cloud, and cloudbursting

SharePoint Geo-Collaboration

Coupled with the StorSimple SharePoint Database Optimizer (SSDO), organizations with SharePoint deployments can provide data center performance to large remote offices where deployment of a Web Front End (WFE) server was not possible.  This enables users that are geographically dispersed to better collaborate via improved performance, and simplifies data protection through the use of Cloud Snaps and Cloud Clones

StorSimple Data Restore Console for SharePoint

StorSimple Data Restore Console (SDRC) for SharePoint is a Windows Server application that can mount snapshot, Cloud Snap, and Cloud Clone backup copies from SharePoint environments and perform item, folder, and site-level restore operations.  This is in addition to the point-in-time volume restore capabilities already provided by StorSimple

StorSimple Data Restore Console for Exchange

StorSimple Data Restore Console (SDRC) for Exchange is a Windows Server application that can mount snapshot, Cloud Snap, and Cloud Clone backup copies from Exchange environments and perform item, folder, and mailbox-level restore operations.  This is in addition to the point-in-time volume restore capabilities already provided by StorSimple

Large Volume Sizes

In previous software versions, StorSimple supported volumes up to 2TB in size.  With OS v1.2, StorSimple now supports volumes that are up to 100TB in size, which improves manageability for file servers, backup target applications, and others

Enterprise Manageability

Additional enterprise manageability features are introduced in OS v1.2, including support for multiple user accounts, user audit logs, simplified console setup wizard, and email call-home support both for the system administrator as well as to StorSimple support

Non-Disruptive Software Upgrades

Enables software upgrades from version 1.1 to 1.2 without downtime through the automated controller failover capabilities provided by appliance models 5010 and 7010

Back to Top

Issues resolved in v.1.2.1

The following are the issues that have been addressed in version 1.1.1 RC1.

 

ID

Summary

Comments and/or Workarounds

CSC-1591

An SSD disk may become faulty and come online and offline in a loop.

Due to a known defect in the SSD firmware, the disk may appear as faulty and start looping between online and offline state. StorSimple is actively working with the SSD manufacturer to address the firmware issue. In order to resolve the problem, unplug and plug back into the system the misbehaving SSD.

CSC-949

A controller that has crashed or is rebooting may not come back online.

There is a known issue in the underlying platform that may lead to this situation very sporadically. StorSimple is actively working with its hardware manufacturer to resolve the problem and deliver a solution in the future releases. In order to bring the controller back online, it should be removed and inserted back into the chassis.

CSC-1396, CSC-1524

A standby controller failure may lead to some disks (SSDs and/or HDDs) appearing as faulty.

Under rare circumstances, a driver issue may lead to one or more disks appearing as faulty and offline while the standby controller is rebooted or it has failed. In order to bring the system to a completely functional state, restart the active controller or power cycle the entire chassis.

CSC-1353

Enabling or disabling any of the DATA ports causes a temporary loss of connection on all the ports.

This issue will be resolved in future releases. All the DATA ports should be configured during the initial installation to avoid this problem.

Back to Top

Release Notes for v.1.2.1

The following are the release notes for version 1.2.1 for the StorSimple Storage Appliance.

 

ID

Summary

Comments and/or Workarounds

CSC-867

Microsoft iSCSI initiator doesn't support LUN ID 255.

Use a LUN ID of 0 to 254.

CSC-1334

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. StorSimple is actively working with Microsoft to analyze the issue which may be a problem on the host side. In order to restore the volume access, please force an iSCSI rediscovery of the target or power cycle the host.

CSC-1335

While forcing multiple controller failovers in the system, one disk may be excluded from the active set.

Under stress testing of the controller failover, sporadically one of the disks may be evicted from the active set. This situation doesn't cause the system to stop operations but it puts it in a degraded state. The system should automatically recover from this situation and allow the disk to rejoin the array after a proper resync, therefore removing the degraded state.

CSC-1371

In the Hardware Page, the "Enclosure Electronics Power" state of a controller is reported as "NOT AVAILABLE".

This is a known issue in the underlying platform that will be fixed in the upcoming releases. There is no negative side effect on the system behavior.

CSC-1426

In the Hardware Page, the CPU and DIMM temperature sensors are reported as NOT PRESENT or FAILED.

This is an issue in the underlying platform firmware. In case the status appears as FAILED, this would automatically trigger an alert in the system. In order to clear such alert, please reboot or remove and reinstall the controller until the status appears again as NOT PRESENT.

CSC-1492

The controller failover may exceed the application timeout.

Under certain failure scenarios, the failover to the standby controller may take longer than the application SCSI timeout. This is a sporadic event. Once the failover has occurred, normally the application will automatically re-establish the connection and continue operations. If that doesn't happen automatically, restart the application or the connection manually.

CSC-1538

In the Hardware Page, when the standby controller has been shut down or pulled out a different state is reported.

This is a known issue in the underlying platform code that will be fixed in a future release. There are no negative side effects on the system behavior.

CSC-1549

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.

CSC-1644

In some rare circumstance, the appliance interfaces may not be usable.

While performing platform discovery, it has been seen in rare occasions that the MGMT and DATA interfaces are not detected properly during the power up sequence. Under such scenarios the Web UI and the iSCSI ports are not reachable. To restore the proper functionality in the appliance, reboot the box.

CSC-1677

Enabling a DATA port not plugged in may cause connectivity issues.

Please verify the connectivity of the DATA ports either through visual inspection of the box or using the Diagnostics page. Ensure that only the ports connected and functioning properly are enabled in the UI. In order to prevent cloud access issues, once the network ports have been reconfigured reapply the Time Setting and verify the Cloud Account again.

CSC-1738

The Web UI may not be accessible when the system encounters an error

If the Web UI becomes unresponsive and an attempt to login form a different browser window seems to hang for more than 30 seconds, please reboot the system to restore it to a working state.

CSC-1740

The "Software Upgrade" page hangs after Upgrade, making the Web UI not accessible. This may also occur when pressing the "Restart Active Controller" or "Restart Appliance" buttons.

This issue occurs very infrequently, it has been observed a few times during an upgrade of the 1010 series, though it may occur on other systems too. The work-around is to reboot the appliance, or failover to the standby controller on the 5010 and 7010 models.

CSC-1919

Under very heavy iSCSI load, the controller may reboot.

Under rare circumstances, when the system is under heavy iSCSI stress testing, the controller may reboot causing either a system reboot (1010 model) or a failover (5010 and 7010 models). The system should automatically recover from this situation after the reboot or failover. StorSimple is actively working on addressing the issue permanently in the upcoming release.

CSC-1938

While forcing a continuous reboot of the active controller, access to the volume data could be lost permanently

This issue has been seen very rarely when performing stress testing of the failover capability of the active controller (either forcing a reboot or yanking it out of the chassis). The issue causes the metadata associated to a volume to become unusable. The issue will be addressed fully in the next major release, in the meantime should such an event occur, please contact StorSimple support in order to obtain the necessary help to correct the issue in the system.

CSC-2255

Microsoft MPIO doesn't work as expected when defaults are altered

It is recommended to use default MPIO parameters for Microsoft MPIO DSM on a Windows host. To find the current parameters, traverse through Computer -> Manage -> Disk Management -> Disk x -> Properties -> MPIO tab -> Details ("Disk x" is any of the StorSimple disks discovered by the host).

The default parameters are:

Path Verify Period = 30

Retry Count = 3

PDO Remove Period = 20

Retry Interval = 1

Path Verify Enabled = Unchecked

Note: to enable MPIO on StorSimple volumes, add the "SSIMPLE Model" keyword in MPIO properties (Control Panel -> Administrative Tools -> MPIO).

CSC-2267

Taking a backup of an imported volume group without changing its name can result in multiple import postfixes being applied when the new backup is imported to a different host.

When a volume group is created as the result of an imported backup run, a postfix is applied to the newly created volume group which provides an indication that the volume group was imported. The postfix consists of “(Imported from <appliance name>)”, where <appliance name> is the actual name of the StorSimple appliance from which the import occurred.

Multiple postfixes in an imported volume group name can be avoided by renaming the imported volume group prior to taking a new backup against it. When renaming the imported volume group, simply remove the “(Imported from <appliance name>)” postfix and perform any additional renaming of the volume group as desired.

CSC-2300

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.

CSC-2321

Performing a configuration restore from a saved xml file on an appliance that has a different Management IP than the one saved in the configuration file, may result in a “No Route to host” error on the Audit Logs screen.

An appliance reboot (1010 model) or a controller failover (5010 and 7010 models) would solve the issue.

CSC-2335

Using the 'Printer friendly version” link in Firefox for the charts will result in a printed page with an empty white area instead of the chart.

This issue is due to a Firefox limitation that doesn't render the content of the HTML "object" element during printing.  In order to overcome this limitation, please use a supported IE version to print charts.

Note: you need to manually select Landscape orientation before printing any of the charts to ensure an accurate print of the charts.

Back to Top

Contacting Technical Support

Please contact technical support to create your account and receive your credentials to access the documentation at:

This will allow you to access product documentation, release notes, software upgrades, and software packages including the StorSimple SharePoint Database Optimizer (SSDO), the StorSimple Data Recover Console (SDRC) for SharePoint and Exchange and the StorSimple Data Protection Console for managing Snapshots, Cloud Snapshots, and Cloud Clones.  

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

Back to Top

Related

Page statistics
930 view(s) and 13 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