Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Presented below for your convenience and information are the release notes of the latest releases.


SoftNAS Cloud® 4.

...

3.

...

0 Release -

...

September 5th, 2019

Overview

SoftNAS Cloud® 4.

...

3.

...

0 is a maintenance release containing bug fixes and important security updates

...

.

New in 4.

...

3.

...

0

...

New Kernel 4.14.138 - The kernel has been updated to 4.14.

...

Responding to the results of a security scan

Recommended minimum Instance/VM requirements - As  of the SoftNAS Cloud 4.2.1 release, SoftNAS recommends that customers only deploy SoftNAS Cloud Instances/VMs with minimum system resources of 16GB or more of RAM and 4 or more vCPUs.

Fixed in 4.2.1

NGINX security issue fixed – An authentication bypass vulnerability has been fixed. This issue only affects SoftNAS Cloud v 4.2, and is only externally exploitable for customers who have not followed best practices in restricting StorageCenter port access to only their private networks and/or IP-restricted client as documented in Instance Planning: Security(15764)

EBS Backup and Restore issue fixed - An issue in which EBS backups would not complete on certain AWS instance sizes on 4.2 has been resolved. (15586)

EBS Backup and Restore/NVMe issue fixed - An issue in which if NVMe EBS disks were used, EBS backup and restore would be unable to restore the data, has been resolved. (15425)

SmartTiers Scheduling issue resolved - Events scheduled for evening with a morning end time (for example 8pm -3am) would not process properly because the system assumed the scheduled events were the same day and therefore in conflict. This issue has been resolved. 

Azure OMS agent new service name issue -Scripts to prevent the incompatible OMS agent from running were updated in order to reflect a new service name for the agent.

138 to eliminate potential security risks including MLPDS, RIDL/ZombieLoad, MFBDS, and MDSUM. The new kernel is up to 11% faster for certain block I/O operations. 

Updated ZFS to 0.8.1 - ZFS has been updated in order to provide fixes and performance improvements. Major improvements to memory management, trim/discard and several obscure, known ZFS hang issues are resolved. Details on ZFS 0.8 and 0.8.1 fixes can be found here. This version of ZFS includes additional feature enhancements that are not yet supported. 

Samba 4.8.3-11 update - Samba has been updated to the latest stable release in order to eliminate potential security issues with previous versions of CIFS/SMB and incorporates minor bug fixes. 

Improved Monit Alerts - SoftNAS has added improved monit alerts to detect system issues earlier, including the following, which are now monitored and alerted upon:

  • excessive repeated retries for AWS S3 or Azure Blob.
  • s3backer errors
  • root volume space low
  • SnapReplicate replication time lag
  • Delta Sync failures 

Lift and Shift CIFS/SMB Performance Improvements - CIFS/SMB Lift and Shift now offers performance comparable to NFS and overall Lift and Shift data migration throughput has been optimized. 

HA controller bucket naming improvements - Buckets created for your HA Controller are now by default prefixed with 'softnasha' upon creation in order to allow the user to better identify these required buckets and prevent accidental deletion. Existing buckets remain unchanged in order to preserve continuity. 

Improved replication performance - Performance changes have been made to SnapReplicated delivering an average of 40% faster replication throughput by use of AES-NI hardware-based encryption acceleration.


Fixed in 4.3.0

Object Storage Support Updates - Object Storage durability and reliability has been improved when using AWS S3 and Azure Blobs.   After upgrade, there will be a “cooldown period” for object storage disks/pools, as object-backed pools are migrated to the new format. This cooldown period will be indicated on the loading screen after rebooting following the update. This cooldown period can take approximately 1 minute per 500 MB/.5 GB and should be included in upgrade maintenance window planning. 

Object Storage VDEV Limits - SoftNAS Cloud now limits object-backed pools to 4 devices per instance/VM, to help ensure the supported limits of object storage are not exceeded, and performance is optimal. Existing instances/VMs that exceed 4 object backed devices will not be modified when upgrading to 4.3.0. 

Erroneous DeltaSync error messages fixed - An erroneous error message requesting that users perform a force sync in order to establish high availability has now been fixed. 

Faster Boot Time - Modified Shutdown sequence to use ACPI and other changes resulting in up to 2x faster boot time.

Multiple SNAP HA pairs in same Azure VNET - SoftNAS Cloud now supports deployment of up to five SNAP HA pairs in the same VNET.

SNAP HA with VIPs in same Azure subnet Users can now implement SNAP HA with VIPs in the same subnet.

Max File Descriptor Limit increase - The global Max FD limit has been increased to 1,048,756 in order to match up with the limits set in other Linux distributions. Any environment already customized with a higher FD limit will not be modified.

Errata 4.3.0

Default Internet Explorer 11 on Server 2012 R2 not supported - Unable to login to the SoftNAS instance from the default IE 11 browser provided with Windows Server 2012 R2. The issue is resolved by applying latest updates, including updates to IE 11.

Webmin Download issue - Unable to download files from the web to your SoftNAS Cloud instance using webmin. This is a known issue that will be resolved in a later release. 

Incompatible Samba Config Prevention - If SoftNAS detects an incompatible SAMBA Active Directory configuration, the upgrade will not proceed and an error message will be presented.
Recommended Action: If the upgrade is blocked, contact support for further assistance.

Changes 4.3.0

SNAP HA Behavior change - If object storage is in use, a failover sequence will no longer shut down the original primary node.
Recommended Action:
 Restart the primary node manually before re-establishing the HA Pair.  To restart the primary node manually, log into the primary node and in the Storage Administration panel, select Settings>System Services, and scroll down to the bottom. Select Reboot Now

Object Storage no longer supported for SmartTiers - SoftNAS no longer supports the creation of new SmartTier pools with object storage included as a tier. Existing customers configured to use SmartTiers pools that include object storage are not affected. 

DCHA no longer supported - Dual Controller High Availability is no longer supported in new configurations, as this feature is deprecated. Customers with an existing DCHA configuration will receive continued support and will not be affected. However, in place upgrades will be prevented to avoid disruptions as this feature has been removed.

Upgrading

SoftNAS recommends that a reboot of the instance be performed prior to performing an upgrade to ensure the upgrade process starts from a stable system.

Upgrading from 4.0 or later

1-click upgrades are supported from versions 4.0 and later to version 4.2.

For information on updating your instance: 

Updating Software

Note: It is important to note that for SnapReplication™, SNAP HA™, and DCHA™ environments, you must follow the upgrade process linked below and perform the suggested reboot after deactivation has been completed.

For upgrading a SNAP HA™ pairing:

Upgrading a SNAP HA™ pairing

Upgrading from versions before 4.0

For versions below 4.0, 1-click upgrades are not supported, and require a migration. Follow the instructions below to migrate, contact SoftNAS Support for assistance.

How To Migrate SoftNAS Cloud® Instances

Upgrading from an AWS PV Instance to AWS HVM Instance

Running SoftNAS Cloud on an AWS PV (paravirtual) instance is not supported.  You will need to migrate your SoftNAS instance from an AWS PV (paravirtual) instance to a supported AWS HVM (hardware virtual machine) instance.  Follow the instructions below to migrate or contact SoftNAS Support to for assistance.

How To Migrate SoftNAS Cloud® Instances


Note: SoftNAS does not support running the ASM and OMS Azure Extensions. If SoftNAS detects these agents running during a periodic scan, the agent will be de-installed by SoftNAS, proper removal of these Azure extensions must occur through the Azure

...

portal (more information here). 

Note: Upon investigation of recent customer reports of poor performance, we have determined that a large percentage of these cases the customer has been impacted by rate limiting and throttling by the cloud providers. If you are experiencing performance related issues, we recommend first contacting your cloud provider and

...

asking if you are being rate limited or throttled.

Note:

...

 In-place

...

upgrades can take 45 minutes or longer to complete. Do NOT terminate the update while in progress else errors will occur. If you feel that your update is taking longer than expected, please contact SoftNAS Support for assistance and do not reboot your instance.

Note: SoftNAS Cloud will not prompt for a reboot post-update. Reboot will occur automatically. Schedule update to coincide with maintenance downtime.

Note: As of version 3.4.8 SoftNAS does not support launching SoftNAS Cloud® VMs on the Azure Classic Portal. The Azure Resource Manager (ARM) is the only supported platform on Azure.

Note: For version 4.2,  our No Downtime Guarantee™ has the following minimum technical requirements:

  • Software version must be 4.2 or above.
  • Software updates must be applied within 30 days of availability.

For more details on our No Downtime Guarantee, click here.

SoftNAS Cloud® 4.2.3 Release - March 29th, 2019

Overview

SoftNAS Cloud® 4.2.3 is a maintenance release containing bug fixes.

Fixed in 4.2.3

AWS S3 bucket and IAM token issue -  During the week of March 25th, AWS made a change to the IAM token length, which impacted SoftNAS' StorageCenter's  ability to authenticate to S3 via IAM roles. This issue did not impact customers currently actively running S3 buckets, but any access requiring IAM authentication from StorageCenter would fail, including creation of new S3 buckets and other actions, such as SoftNAS upgrades, S3 storage migration, and reboots of the SoftNAS instance. This issue is resolved in this 4.2.3 release, and upgrades are now available. SoftNAS recommends that all AWS customers upgrade as soon as possible. New 4.2.3 AWS Marketplace AMIs will be available within 2 weeks.

Upgrading

SoftNAS recommends that a reboot of the instance be performed prior to performing an upgrade to ensure the upgrade process starts from a stable system. If using S3 within AWS, and updating from a version earlier than 4.2.3, your S3 bucket will not mount after the reboot. Please proceed with the upgrade process, and the S3 buckets will mount correctly following the upgrade reboot.

Upgrading from 4.0 or later

1-click upgrades are supported from versions 4.0 and later to version 4.2.

For information on updating your instance: 

Updating Software

Note: It is important to note that for SnapReplication™, in SNAP HA™ environments, you must follow the upgrade process linked below and perform the suggested reboot after deactivation has been completed.

For upgrading a SNAP HA™ pairing:

Upgrading a SNAP HA™ pairing

Upgrading from versions before 4.0

For versions below 4.0, 1-click upgrades are not supported, and require a migration. Follow the instructions below to migrate, contact SoftNAS Support for assistance.

How To Migrate SoftNAS Cloud® Instances

Upgrading from an AWS PV Instance to AWS HVM Instance

Running SoftNAS Cloud on an AWS PV (paravirtual) instance is not supported.  You will need to migrate your SoftNAS instance from an AWS PV (paravirtual) instance to a supported AWS HVM (hardware virtual machine) instance.  Follow the instructions below to migrate or contact SoftNAS Support to for assistance.

How To Migrate SoftNAS Cloud® Instances



SoftNAS Cloud® 4.2.2 Release - March 12th, 2019

Overview

SoftNAS Cloud® 4.2.2 is a maintenance release containing security updates and bug fixes.

New in 4.2.2

Security Fix - A vulnerability existed with 4.2.x releases in which systems deployed with ports exposed to the internet against SoftNAS best practices could be compromised, allowing access to the system without valid user credentials, has been addressed.

Replication Retries added - In order to prevent premature fail-overs, SnapHA ™ will now attempt to reconnect to the HA Controller 3 times before SoftNAS deactivates HA. 

SnapReplicate™ UI Alert Message - In order to prevent users from attempting a forced fail-over, an alert message stating "An Initial SnapRep sync is in progress. HA with full data availability will not be achieved until the initial SnapRep cycle is complete" will be visible until the initial cycle is complete. 

Fixed in 4.2.2

Mbuffer configuration option removed from UI - The toggle to disable the mbuffer configuration option has been removed from Modify Replication Settings in order to prevent users mistakenly disabling the mbuffer feature. The option to disable this feature is still available from within the CLI. Please contact support should this be needed. (15813)

SSH compression setting removed from UI - The option to set SSH compression has been removed from Modify Replication Settings, in order to prevent SSH compression and ZFS compression from being used in tandem, causing system performance degradation. 

Replication Bandwidth Throttling display issue - An issue in which StorageCenter mistakenly showed bandwidth throttling enabled by default in Modify Replication Settings has been resolved. 

Errata 4.2.2


Potential Performance Degradation when using Azure ephemeral devices as L2ARC (read cache) - Azure ephemeral disk devices are throttled. When the performance of the ephemeral L2ARC device is slower than the storage pool that it serves, overall performance may be degraded. If considering using an Azure ephemeral disk device as L2ARC and are unsure of the potential performance impact, feel free to contact support for further guidance.

Upgrading

SoftNAS recommends that a reboot of the instance be performed prior to performing an upgrade to ensure the upgrade process starts from a stable system.

Upgrading from 4.0 or later

1-click upgrades are supported from versions 4.0 and later to version 4.2.

For information on updating your instance: 

Updating Software

Note: It is important to note that for SnapReplication™, SNAP HA™, and DCHA™ environments, you must follow the upgrade process linked below and perform the suggested reboot after deactivation has been completed.

For upgrading a SNAP HA™ pairing:

Upgrading a SNAP HA™ pairing

Upgrading from versions before 4.0

For versions below 4.0, 1-click upgrades are not supported, and require a migration. Follow the instructions below to migrate, contact SoftNAS Support for assistance.

How To Migrate SoftNAS Cloud® Instances

Upgrading from an AWS PV Instance to AWS HVM Instance

Running SoftNAS Cloud on an AWS PV (paravirtual) instance is not supported.  You will need to migrate your SoftNAS instance from an AWS PV (paravirtual) instance to a supported AWS HVM (hardware virtual machine) instance.  Follow the instructions below to migrate or contact SoftNAS Support to for assistance.

How To Migrate SoftNAS Cloud® Instances


SoftNAS Cloud® 4.2.1 Release - Feb 14th, 2019

Overview

SoftNAS Cloud® 4.2.1 is a maintenance release containing security updates and bug fixes.

New in 4.2.1

Kernel update and vulnerability fixes - SoftNAS Cloud is now updated to kernel version 4.14.87, and patched to address relevant kernel vulnerabilities, as well as Azure storage drivers. Kernel vulnerabilities have been researched, and the results posted in the following knowledgebase article to help you determine relevance: 

Responding to the results of a security scan

Recommended minimum Instance/VM requirements - As  of the SoftNAS Cloud 4.2.1 release, SoftNAS recommends that customers only deploy SoftNAS Cloud Instances/VMs with minimum system resources of 16GB or more of RAM and 4 or more vCPUs.

Fixed in 4.2.1

NGINX security issue fixed – An authentication bypass vulnerability has been fixed. This issue only affects SoftNAS Cloud v 4.2, and is only externally exploitable for customers who have not followed best practices in restricting StorageCenter port access to only their private networks and/or IP-restricted client as documented in Instance Planning: Security(15764)

EBS Backup and Restore issue fixed - An issue in which EBS backups would not complete on certain AWS instance sizes on 4.2 has been resolved. (15586)

EBS Backup and Restore/NVMe issue fixed - An issue in which if NVMe EBS disks were used, EBS backup and restore would be unable to restore the data, has been resolved. (15425)

SmartTiers Scheduling issue resolved - Events scheduled for evening with a morning end time (for example 8pm -3am) would not process properly because the system assumed the scheduled events were the same day and therefore in conflict. This issue has been resolved. 

Azure OMS agent new service name issue -Scripts to prevent the incompatible OMS agent from running were updated in order to reflect a new service name for the agent.


SoftNAS Cloud® 4.2 Release - November 15th, 2018

Overview

SoftNAS Cloud® 4.2 is a maintenance release containing security updates, performance improvements and bug fixes.

...

Root Disk Size increase - To take advantage of increased IOPS / throughput, the default root disk size for SoftNAS Cloud instances/virtual machines has been increased from 30GB to 100GB for newly launched instances/virtual machines on AWS and Azure (Only applicable to AWS and Azure, no change made or required for VMware). The root partition and file system will remain at 30GB.  Existing instances can be increased to this new size.  Please contact support for instructions if needed. 

Fixed in 4.2

SmartTiers Tiered Storage Configuration issue - An issue in which attempts to make changes to the existing tiered storage configuration would fail due to the Tiered Storage Configuration wizard failing to load has been resolved. 

...

FlexFiles on Firefox issue - Upon first attempt to use FlexFiles and associated NiFi functionality on the Firefox browser, the user will receive a "Your connection is not secure" message. 
Recommended Action: Under Firefox settings,  open the  FlexFiles Architect frame in a new tab and using Add Exception, add an exception. 

Upgrading

SoftNAS recommends that a reboot of the instance be performed prior to performing an upgrade to ensure the upgrade process starts from a stable system.

...

How To Migrate SoftNAS Cloud® Instances

Upgrading from an AWS PV Instance to AWS HVM Instance

Running SoftNAS Cloud on an AWS PV (paravirtual) instance is not supported.  You will need to migrate your SoftNAS instance from an AWS PV (paravirtual) instance to a supported AWS HVM (hardware virtual machine) instance.  Follow the instructions below to migrate or contact SoftNAS Support to for assistance.

...

SoftNAS Cloud® 4.1 Release - September 17th, 2018

Overview

SoftNAS Cloud® 4.1 is a feature release containing new features, improvements and bug fixes.

...

Unable to add second NIC without reboot - If deploying instances without adding the second Network interface at the outset, then adding the Network interface after the fact via script/command line, the second NIC will not be active until after a reboot. 
Recommended Action: Reboot the instance, or use the following command to activate the NIC without reboot: 
echo 1 > /sys/bus/pci/rescan 

Upgrading

SoftNAS recommends that a reboot of the instance be performed prior to performing an upgrade to ensure the upgrade process starts from a stable system.

...

How To Migrate SoftNAS Cloud® Instances

Upgrading from an AWS PV Instance to AWS HVM Instance

Running SoftNAS Cloud on an AWS PV (paravirtual) instance is not supported.  You will need to migrate you SoftNAS instance from an AWS PV (paravirtual) instance to a supported AWS HVM (hardware virtual machine) instance.  Follow the instructions below to migrate or contact SoftNAS Support to for assistance.

...

SoftNAS Cloud® 4.0.3 Release - July 18th, 2018

Overview

SoftNAS Cloud® Enterprise 4.0.3 is a maintenance release containing bug fixes.

Upgrading

SoftNAS recommends that a reboot of the instance be performed prior to performing an upgrade to ensure the upgrade process starts from a stable system.
It is important to note that for SnapReplication™, SNAP HA™, and DCHA™ environments, you must follow the documented upgrade process and perform this suggested reboot after deactivation has been completed.

...

How To Migrate SoftNAS Cloud® Instances

Upgrading from an AWS PV Instance to AWS HVM Instance

Running SoftNAS Cloud on an AWS PV (paravirtual) instance is not supported.  You will need to migrate you SoftNAS instance from an AWS PV (paravirtual) instance to a supported AWS HVM (hardware virtual machine) instance.  Follow the instructions below to migrate or contact SoftNAS Support to for assistance.

...

SoftNAS Cloud® 4.0.2 Release - June 15th, 2018

Overview

SoftNAS Cloud® Enterprise 4.0.2 is a maintenance release containing bug fixes.

Upgrading

SoftNAS recommends that a reboot of the instance be performed prior to performing an upgrade to ensure the upgrade process starts from a stable system.
It is important to note that for SnapReplication™, SNAP HA™, and DCHA™ environments, you must follow the documented upgrade process and perform this suggested reboot after deactivation has been completed.

...

How To Migrate SoftNAS Cloud® Instances

Upgrading from an AWS PV Instance to AWS HVM Instance

Running SoftNAS Cloud on an AWS PV (paravirtual) instance is not supported.  You will need to migrate you SoftNAS instance from an AWS PV (paravirtual) instance to a supported AWS HVM (hardware virtual machine) instance.  Follow the instructions below to migrate or contact SoftNAS Support to for assistance.

...

SoftNAS Cloud® 4.0.1 Release - June 1st, 2018

Overview

SoftNAS Cloud® Enterprise 4.0.1 is a maintenance release containing bug fixes.

...

SoftNAS Cloud® 4.0 Release - May 28th, 2018

Overview

SoftNAS Cloud® 4.0 is a feature release containing new features, improvements and bug fixes.

Upgrading

Upgrading from 3.4.9 or later

...

How To Migrate SoftNAS Cloud® Instances

Upgrading from an AWS PV Instance to AWS HVM Instance

Running SoftNAS Cloud on an AWS PV (paravirtual) instance is not supported.  You will need to migrate you SoftNAS instance from an AWS PV (paravirtual) instance to a supported AWS HVM (hardware virtual machine) instance.  Follow the instructions below to migrate or contact SoftNAS Support to for assistance.

...

SoftNAS Cloud® 3.7.3 Release - June 29th, 2018

Overview

SoftNAS Cloud® Enterprise 3.7.3 is a maintenance release containing bug fixes.

...

SoftNAS Cloud® 3.7.2 Release - March 28th, 2018

Overview

SoftNAS Cloud® Enterprise 3.7.2 is a maintenance release containing bug fixes.

Upgrading

Upgrading from versions prior to 3.4.9

...

SoftNAS Cloud® 3.7.1 Release - Feb 20, 2018

Overview

SoftNAS Cloud® Enterprise 3.7.1 is a maintenance release containing bug fixes.

...

With the current release, we are including a kernel update for the Spectre and Meltdown vulnerabilities. As SoftNAS Cloud® is hosted on AWS, Azure, and VMware platforms, this kernel update and fixes provided by each platform will mitigate the risk. As such, no action beyond upgrading to the latest version of SoftNAS Cloud® is necessary.

Upgrading

Upgrading from versions prior to 3.4.9

...

SoftNAS Cloud® 3.7 Release - JAN 22nd, 2018

Overview

SoftNAS Cloud® Enterprise 3.7 is a feature release containing new features, beta additions, improvements and bug fixes.

...

With the current release, we are including a kernel update for the Spectre and Meltdown vulnerabilities. As SoftNAS Cloud® is hosted on AWS, Azure, and VMware platforms, this kernel update and fixes provided by each platform will mitigate the risk. As such, no action beyond upgrading to the latest version of SoftNAS Cloud® is necessary.

Upgrading

Upgrading from versions prior to 3.4.9

...

SoftNAS Cloud® 3.6.1 Release - Oct 26th, 2017

Overview

SoftNAS Cloud® 3.6.1 is a maintenance release containing fixes, and improvements.

Upgrading

Upgrading from versions prior to 3.4.9

...

SoftNAS Cloud® 3.6 Release - Sept 18th, 2017

Overview

SoftNAS Cloud® Enterprise 3.6 is a feature release containing new features, beta additions, improvements and bug fixes. 

Upgrading

Upgrading from versions prior to 3.4.9

...

Deleted Ultrafast™ Connection not reflected on both sides - If an UltraFast™ connection is established between two AWS Ultrafast™ instances, then deleted on the target side, the source will not recognize that the connection is missing, and will continuously remain in a connecting/pending connection state.

UltraFast™ Unresponsive Create Button after wrong credentials used - If credentials are entered incorrectly or the wrong credentials used when creating a new UltraFast™ Connection, a subsequent attempt to create a flow using the 'Create' button will fail, as the button becomes unresponsive.
Recommended Action: Close the UltraFast™ applet (tab), and re-open. The Create button will respond again.

SoftNAS Cloud 3.5.6 Release - July 28th , 2017

Overview

SoftNAS Cloud® 3.5.6 is a maintenance release containing fixes, and improvements. Version 3.5.6 is compatible with all editions of SoftNAS Cloud®.

Upgrading

Upgrading from versions prior to 3.4.9

...

NFS Server Default Thread Count Value- Default thread count logic is improved, and is now based on the amount of available RAM, rather than a set default.


SoftNAS Cloud 3.5.5 Release - July 17th , 2017

Overview

SoftNAS Cloud® 3.5.5 is a maintenance release containing fixes, and improvements. Version 3.5.5 is compatible with all editions of SoftNAS Cloud®.

Upgrading

Upgrading from versions prior to 3.4.9

...

UltraFast Log Fix - An issue in which an excessive amount of UltraFast configuration error sand alerts would appear in the log even when instances were not configured for UltraFast has been resolved.


SoftNAS Cloud 3.5.4 Release - June 28th , 2017

Overview

SoftNAS Cloud® 3.5.4 is a maintenance release containing fixes, and improvements. Version 3.5.4 is compatible with all editions of SoftNAS Cloud®.

Upgrading

Upgrading from versions prior to 3.4.9

...

Multiple Volume SnapReplicate™ Issue - Fixed an issue in SnapReplicate™ where if the customer had multiple volumes the SSH connection was getting disconnected.


SoftNAS Cloud 3.5.3 Release - June 23rd , 2017

Overview

SoftNAS Cloud® 3.5.3 is a maintenance release containing fixes, and improvements. Version 3.5.3 is compatible with all editions of SoftNAS Cloud®.

Upgrading

Upgrading from versions prior to 3.4.9

...

Licensing Fix - Fixed an issue with license identification for new AWS and Azure Marketplace SKU's.


SoftNAS Cloud 3.5.2 Release - June 19th , 2017

Overview

SoftNAS Cloud® 3.5.2 is a maintenance release containing fixes, and improvements. Version 3.5.3 is compatible with all editions of SoftNAS Cloud®.

Upgrading

Upgrading from versions prior to 3.4.9

...

Update Issue - Fixed an issue where upgrades via UI were not functional on Azure instances.

SoftNAS Cloud 3.5.1 Release - June 9th , 2017

Overview

SoftNAS Cloud® 3.5.1 is a maintenance release containing fixes, and improvements. Version 3.5 is compatible with all editions of SoftNAS Cloud®.

Upgrading

Upgrading from versions prior to 3.4.9

...

High Availability Fix - An issue in which upgrading an existing HA pairing from versions 3.4.9.7 and prior (to 3.5) would disrupt high availability has been resolved.

Errata for SoftNAS Cloud®

...

3.5.

EPEL Repository Removed - SoftNAS has removed the EPEL repository in the 3.5 release, however if a customer wishes to enable/install it, they can do so at their discretion.

SoftNAS

...

Cloud® 3.5 Release - June 1st , 2017

Overview

SoftNAS Cloud® NAS 3.5 is a feature release containing linux and kernel updates, fixes, and improvements. Version 3.5 is compatible with all editions of SoftNAS Cloud® NAS.

Upgrading

Upgrading from versions prior to 3.4.9

...

How To Migrate SoftNAS Cloud® Instances

New in SoftNAS Cloud®

...

3.5

New SoftNAS Cloud® NAS Editions and Capacities 

...

Update to Linux Kernel 4.4 and latest ZFS version - Improved security and performance.

Fixed in SoftNAS Cloud®

...

3.5

Dirty Cow Security Vulnerability Fixed - With version 3.5, the new linux kernel update to 4.4 eliminates known linux security vulnerabilities, notably the Dirty Cow  linux vulnerability.

...

SnapCloned Volumes Replication Issue fixed - SnapClone created volumes now replicate successfully via SnapReplicate™.

Errata for SoftNAS Cloud®

...

3.5.

Prior to version 3.5, SoftNAS Cloud® NAS used a TDB backend, and has now switched to RID -  If planning to unjoin and rejoin Active Directory (AD) after your 3.5 upgrade, be aware that this will require AD rejoin permissions to enumerate across all files. For large scale AD configurations, this can be a significant undertaking. You will not be affected by this change if you do not plan to unjoin and rejoin your domain.  If you have upgraded to 3.5 and need to rejoin your SoftNAS instance to your domain please contact SoftNAS Support for assistance.

...

VMware Deleted Disk records still visible in Monitoring - On VMware instances, deleted disks may continue to appear in the Disk Activity Monitoring dropdown.





SoftNAS

...

Cloud® 3.4.9.7 Release - March 27, 2017

Overview

SoftNAS Cloud® NAS 3.4.9.7 is a maintenance release containing fixes, and improvements. Version 3.4.9.7 is compatible with all editions of SoftNAS Cloud® NAS.

Upgrading

Upgrading from 3.4.0 through 3.4.9.6

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

New in SoftNAS Cloud®

...

3.4.9.7

Instance support update - New instance sizes supported in the AWS Marketplace.

Fixed in SoftNAS Cloud®

...

3.4.9.7

Improved Disk Status Reporting for HA failover - Failover is now triggered if an individual pool becomes unavailable, rather than only during a node failure.

...


SoftNAS Cloud 3.4.9.6 Release - March 03, 2017

Overview

SoftNAS Cloud® NAS 3.4.9.6 is a maintenance release containing fixes, and improvements. Version 3.4.9.6 is compatible with all editions of SoftNAS Cloud® NAS.

Upgrading

Upgrading from 3.4.0 through 3.4.9.5

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

Fixed in SoftNAS Cloud®

...

3.4.9.6

High Availability IP re-assignment issue - Fixed an issue in which the virtual IP address would not reassign itself to the primary node after a hard failover (ie, shut-down of primary node) and node recovery. This resulted in being unable to connect to CIFS and NFS shares post failover.

...


SoftNAS Cloud® NAS 3.4.9.5 Release - Feb 21, 2017

Overview

SoftNAS Cloud® NAS 3.4.9.5 is a maintenance release containing fixes, and improvements. Version 3.4.9.5 is compatible with all editions of SoftNAS Cloud® NAS.

Upgrading

Upgrading from 3.4.0 through 3.4.9.4

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

New in SoftNAS Cloud®

...

3.4.9.5

Improved Disk Status Reporting for HA failover - Failover is now triggered if an individual pool becomes unavailable, rather than only during a node failure.

...

Improved logging/support reports - Additional log files files added to default list of log files submitted when a support report if generated and sent to SoftNAS support, to make troubleshooting easier.

Fixed in SoftNAS Cloud®

...

3.4.9.5

NFS Bind Issue causing Client Mount hang fixed - An issue that caused client mounts to hang, and resulted in "stale file handle" errors. This has now been resolved.

...

S3 bucket name fix - Numerical values can now be applied to bucket names.

Errata for SoftNAS Cloud®

...

3.4.9.5

If updating a SnapReplicate™ pairing to 3.4.9.5 according to the instructions found here, you may run across an error in which SoftNAS Cloud falsely reports SnapReplicate™ as still active, but with the deactivate button to continue the process grayed out.
Recommended Action: If the above occurs, switch to the SnapReplicate/Snap HA tab, and activate and deactivate replication, then return to the update process.



SoftNAS Cloud®

...

3.4.9.4 Release - Dec 21, 2016 

Overview

SoftNAS Cloud® NAS 3.4.9.4 is a maintenance release containing fixes, and improvements.  Version 3.4.9.4 is compatible with all editions of SoftNAS Cloud® NAS. 

Upgrading

Upgrading from 3.4.0 through 3.4.9.2

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

Fixed in SoftNAS Cloud®

...

3.4.9.4

Auto Failover Issue – Fixed an issue where in some cases auto-failover did not assign the VIP address to the proper interface.

SoftNAS Cloud®

...

3.4.9.3 Release - Nov 21, 2016

Overview

SoftNAS Cloud® NAS 3.4.9.3 is a maintenance release containing fixes, and improvements. Version 3.4.9.3 is compatible with all editions of SoftNAS Cloud® NAS.

Upgrading

Upgrading from 3.4.0 through 3.4.9.2

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

Fixed in SoftNAS Cloud®

...

3.4.9.2

License Validation bug fix - Fixed an issue in which large storage volumes misrepresented terabytes as gigabytes, resulting in an error mistakenly stating the customer had exceeded his license limit.

SoftNAS Cloud®

...

3.4.9.2 Release - Nov 15, 2016

Overview

SoftNAS Cloud® NAS 3.4.9.2 is a maintenance release containing fixes, and improvements. Version 3.4.9.2 is compatible with all editions of SoftNAS Cloud® NAS.

Upgrading

Upgrading from 3.4.0 through 3.4.9.1

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

New in SoftNAS Cloud®

...

3.4.9.2

Getting Started Checklist Change - To more accurately reflect the requirement of an email address for notifications and alerts, guidance is changed to create a 'notification email', rather than 'admin email'.

Fixed in SoftNAS Cloud®

...

3.4.9.2

AWS Directory Service Integration Fix - Fixed bug resulting in Ajax communication error as well as errors in authenticating group permissions.

Errata for SoftNAS Cloud®

...

3.4.9.2

Error Creating HA Controller - Fixed an issue where the longer instance ID lengths were preventing creation of the HA controller.

SoftNAS Cloud®

...

3.4.9.1 Release - Oct 25, 2016

Overview

SoftNAS Cloud® NAS 3.4.9.1 is a maintenance release containing fixes, and improvements. Version 3.4.9.1 is compatible with all editions of SoftNAS Cloud® NAS.

Upgrading

Upgrading from 3.4.0 through 3.4.9

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

New in SoftNAS Cloud®

...

3.4.9.1

Ephemeral Disks as Cache for Azure - SoftNAS Cloud® NAS can can now leverage ephemeral disks as read cache to improve performance on Azure instances.

...

  • Access to S3
  • Access to a NTP server
  • Two ENIs (one for replication traffic, one for heartbeat)
  • Checking that each ENI is set to a different subnet
  • IAM permissions
  • Admin email is validated

Fixed in SoftNAS Cloud®

...

3.4.9.1

Email Notifications Fix - SoftNAS Cloud® NAS no longer attempts to send email notifications to the default email example address of admin@example.com.

...

Email Notification Fix - An unnecessary alert email generated when checking for updates, regardless of whether updates are available, has been downgraded to info status, and will be logged rather than generating an alert email.

Errata for SoftNAS Cloud®

...

3.4.9.1

On a SnapReplicate pairing of proxy SoftNAS instances, exclusions for the source and target now populate automatically. However, upon deletion of Replication, the source entry should be removed from target exclusion list. This does not occur.
Recommended Action: If deleting replication on a proxied SoftNAS instance, remove source entry exclusion from target manually.

...

During software update, the Progress Bar may go to 102% for a few seconds prior to completion.
Recommended Action: None.


SoftNAS Cloud®

...

3.4.9 Release - Sept 15, 2016

Overview

Version 3.4.9 is a maintenance release containing critical fixes and improvements. Version 3.4.9 is compatible with all editions of SoftNAS Cloud.

Upgrading

Upgrading from 3.4.0 through 3.4.9

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

Fixed in SoftNAS Cloud®

...

3.4.9

Fixed NFSv4 bind issue - NFS was not mounting correctly after HA failover events leading to stale file handle errors This issue has been fixed.


SoftNAS Cloud®

...

3.4.8 Release - Sept 1, 2016

Overview

SoftNAS Cloud® NAS 3.4.8 is a maintenance release containing feature additions, fixes, and improvements. Version 3.4.8 is compatible with all editions of SoftNAS Cloud.

Upgrading

Upgrading from 3.4.0 through 3.4.8

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

New in SoftNAS Cloud®

...

3.4.8

Azure

Azure Blob Object Storage Support – SoftNAS Cloud® NAS frontends the object based scalable storage provided by Azure Blob Storage to present NFS, CIFS/SMB, iSCSI or AFP file sharing protocols for enterprise workloads. SoftNAS Cloud allows easy workload migrations to the Azure cloud without changing existing application data structures or workflows. Scale NAS deployments to Azure Blob Storage from gigabytes to petabytes.

...

DeltaSync™ – Reduces the Recovery Time Objective (RTO) from days to hours for cluster recovery from a high-availability (HA) failover event.

Fixed in SoftNAS Cloud®

...

3.4.8

Fixed SnapClone/HA issue - Replicating SnapClones no longer results in an HA degraded state.

...

Fixed UI Issue - Text overlapping radial button in LDAP server settings workspace is now correctly placed.

Errata for SoftNAS Cloud®

...

3.4.8

Errors may occur importing S3 disks that are members of a Storage Pool composed of multiple S3 disks.
Recommended Action: Contact SoftNAS Support to assist if it is necessary to import Storage Pools that span multiple S3 disks.

...

Currently, displayed pool or volume graphs are proportional, which can result in small pools being nearly invisible if presented along with large pools or volumes (for example a 10 GB volume next to a 100 terabyte volume).


SoftNAS Cloud®

...

 3.4.7.4 Release - Aug 19, 2016

Overview

Version 3.4.7.4 is a maintenance release containing critical fixes and improvements. Version 3.4.7.4 is compatible with all editions of SoftNAS Cloud. Upgrading to this release is highly recommended for anyone leveraging Cloud Disks.

Upgrading

Upgrading from 3.4.0 through 3.4.7

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

Fixed in SoftNAS Cloud®

...

3.4.7.4

S3 Cloud Disk Fix - A modification to S3 Cloud disks allows for proper response when the underlying object storage returns a 500 or 503 error.


SoftNAS Cloud®

...

 3.4.7.3 Release - Aug 2, 2016

Overview

Version 3.4.7.3 is a maintenance release containing critical fixes and improvements. Version 3.4.7.3 is compatible with all editions of SoftNAS Cloud.

Upgrading

Upgrading from 3.4.0 through 3.4.7

...

Fix to default settings - Disabled Linux Memory Overcommit.


SoftNAS Cloud®

...

 3.4.7.2 Release - June 13, 2016

Overview

Version 3.4.7.2 is a maintenance release containing critical fixes and improvements. Version 3.4.7.2 is compatible with all editions of SoftNAS Cloud.

Upgrading

Upgrading from 3.4.0 through 3.4.7

...

Fix to Century Link Regional S3 Bucket location error - S3 Buckets placed in US East region would be misplaced to another region. This has been resolved.


SoftNAS Cloud®

...

3.4.7.1 Release - May 23, 2016

Overview

Version 3.4.7.1 is a maintenance release containing critical fixes and improvements. Version 3.4.7.1 is compatible with all editions of SoftNAS Cloud.

Upgrading

Upgrading from 3.4.0 through 3.4.7

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

Fixed in SoftNAS Cloud®

...

3.4.7.1

VMware S3 Disk Device Errors - Fixed an issue in which S3 disks introduced to VMware instances upgraded to 3.4.7 would result in errors, or would hang. Pre-existing S3 disks (from prior to upgrade) sometimes did not display in the Volumes Table. These issues have been resolved.


SoftNAS Cloud®

...

3.4.7 Release - May 16, 2016

Overview

Version 3.4.7 is a maintenance release containing critical fixes and improvements. Version 3.4.7 is compatible with all editions of SoftNAS Cloud® NAS.

Upgrading

Upgrading from 3.4.0 through 3.4.7

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

HA Patch in SoftNAS Cloud®

...

3.4.7

HA Hotfix Release to Prevent Spontaneous Failovers and Improve Logging

3.4.7 includes new logic and logging to address an issue seen in previous releases where brief losses of communication between AWS and SoftNAS instances have resulted in unnecessary failovers. These measures will both prevent the unnecessary failovers, and aid SoftNAS in determining root cause.

Fixed in SoftNAS Cloud®

...

3.4.7

LUN Target Deletion Issue Fixed - Fixed an issue where a deleted target would result in the LUN detaching from other targets.

...

SMTP Server Authentication - Fixed an issue with SMTP Authentication where windows domain and username were not recognized as valid credentials (ie: domain/username).

Errata for SoftNAS Cloud®

...

3.4.7

Elastic IP addresses will not work when using a proxy. This option will be removed from the HA configuration wizard in a later release, if a proxy setup is detected.
Recommended Action: If planning to establish high availability and use a proxy server, plan your configuration to make use of Virtual IP addresses in your configuration.

...

If running a SnapReplicate SoftNAS pairing, for replication to occur, the IPs of both paired instances must be added to the proxy's exclusion list manually.


SoftNAS Cloud®

...

3.4.6.2 Release - March 30, 2016

Overview

Version 3.4.6.2 is a maintenance release containing critical fixes and improvements. Version 3.4.6.2 is compatible with all editions of SoftNAS Cloud.

Upgrading

Upgrading from 3.4.0 through 3.4.6

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

Fixed in SoftNAS Cloud®

...

3.4.6.2

AWS JAVA SDK update- Added support for a new reporting API resulting in a minor change to a usage reporting structure.

Version Numbering enhancement - Added support for four-digit version numbers within SoftNAS.


SoftNAS Cloud®

...

3.4.6.1 Release - March 21, 2016

Overview

Version 3.4.6.1 is an optional maintenance release containing upgrades that allow use of AWS' new Flexible Consumption Pricing model. If not switching to the Flexible Consumption Pricing model, this upgrade can be skipped. Version 3.4.6.1 is compatible with all editions of SoftNAS Cloud® NAS.

Upgrading

Upgrading from 3.4.0 through 3.4.6

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

Fixed in SoftNAS Cloud®

...

3.4.6.1

Flexible Consumption Pricing Added- SoftNAS is one of four vendors chosen to be part of the AWS flexible consumption pricing (FCP) launch. This new pricing model, only available via the AWS Marketplace, allows you to scale your software usage up or down without modifying your SoftNAS EC2-based instance and still pay through your AWS Marketplace bill. When your usage changes, your hourly charge changes to match. This means you only pay for the amount of software you need to operate your workloads.


SoftNAS Cloud®

...

3.4.6 Release - March 08, 2016

Overview

Version 3.4.6 is a maintenance release containing critical fixes and improvements. Version 3.4.6 is compatible with all editions of SoftNAS Cloud® NAS.

Upgrading

Upgrading from 3.4.0 through 3.4.6

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

Security Patch in SoftNAS Cloud®

...

3.4.6

Hotfix Release to Resolve Linux Glibc Library Vulnerability

On February 16th, a serious defect was found in the getaddrinfo() library call in glibc. This issue, labelled CVE-2015-7547, allows an attacker to cause buffer overflow to occur, creating the possibility of remote code execution in some circumstances. In order to ensure that SoftNAS instances are not vulnerable to this potentially serious security issue, a hotfix has been created in order to eliminate this risk. If this hotfix has not already been applied, we recommend applying it immediately after your update to 3.4.6, as both the hotfix and update will require a reboot. Performing a single reboot for both patch and update will save significant time. See [SoftNAS KB]: Installing Hotfix for CVE-2015-7547 for update instructions.

Fixed in SoftNAS Cloud®

...

3.4.6

Improvements to the implementation of S3 Cloud Disk Extender: A new High-Performance S3 Block Cache has been implemented that improves performance drastically by caching changes in RAM, then synchronously flushing to S3 media in concert with ZFS filesystem to ensure data integrity. The High-Performance S3 Block Cache replaces the earlier "Block Cache File", which is deprecated and no longer used or required.

...

Editing Volumes: Fixed an issue in which if a user attempted to edit a volume, modifying the volume would not complete.

Errata for SoftNAS Cloud®

...

3.4.6

As stated above, a reboot is required to obtain the improvements to S3 performance. Under certain conditions, this reboot can take a great deal of time. The reboot process performs three basic steps - applying the update, flushing the cache, then the reboot itself. If using S3 over a slow network connection, flushing the cache can take a long time. It is important NOT to interrupt this process (ie. by a hard boot) or you may lose valuable data.
Recommended Action: To avoid a lengthy reboot process, stop i/o, and wait for the cache to flush prior to performing your reboot. You can determine the amount of data in your cache by opening SoftNAS' dashboard, and viewing Cache Memory under the Performance tab. Alternatively, monitor the network writes traffic in the I/O Throughput panel. When this activity subsides, your reboot should take far less time.

...

S3 Imports to the Frankfurt AWS region fail when initiated from the UI.
Recommended Action: If you have the need to import an S3 Bucket in Frankfurt please contact SoftNAS Support.


SoftNAS Cloud®

...

3.4.5 Release - January 13, 2016

Overview

Version 3.4.5 is a maintenance release containing critical fixes and improvements. Version 3.4.5 is compatible with all editions of SoftNAS Cloud® NAS.

Upgrading

Upgrading from 3.4.0 through 3.4.5

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

Fixed in SoftNAS Cloud®

...

3.4.5

Nuisance alerts and log messages fixed - A minor issue with SNAP HATM resulted in unnecessary log messages and nuisance email alerts from the target node has been resolved.
NFS Bind on reboot fixed - A critical issue with remounting NFS bind mounts on reboot has been resolved.

Errata for SoftNAS Cloud®

...

3.4.5

If updating an instance that has as yet never been updated, there is a known issue where updating from 3.4.4 or earlier to 3.4.5 will hang at 82%, and will seemingly not update.
Recommended Action: The update completes just fine, however you will need to reboot the system, or alternatively, go to Webmin, run the command "service httpd restart", then refresh the browser to see the changes.

Note: Instances newer than 3.4.6 will not see this issue. This issue will also not be seen if the update process has previously been run, for example, if you previously updated from 3.4.3 to 3.4.4. The above issue has also been seen in VMware instances.


SoftNAS Cloud®

...

3.4.4 Release - December 22, 2015

Overview

Version 3.4.4 is a maintenance release containing critical fixes and improvements. Version 3.4.4 is compatible with all editions of SoftNAS® Cloud NAS.

Upgrading

Upgrading from 3.4.0 through 3.4.4

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

Fixed in SoftNAS Cloud®

...

3.4.4

S3 Cloud Disk data integrity fixes - Issues addressed that may result in a degradation of data integrity for S3 Cloud Disks through reboots, upgrades, and power-loss scenarios. All customers using S3 Cloud Disks are strongly encouraged to apply the following steps. Steps 1-3 are required for data integrity. #4 is a performance improvement.

...


Resync of data after a high availability failover - A SNAP HATM pair that had been failed, and repaired did not reliably replicate data to the new target node.

New in SoftNAS Cloud®

...

3.4.4

New - SoftNAS Cloud AMI is now available in the Korea region, without local Korea S3 bucket support (all other regions supported). Local Korea S3 bucket support coming in a future software update.

Errata for SoftNAS Cloud®

...

3.4.4

In a high availability configuration, with the Primary instance in a Degraded state, SNAP HATM may not be able to be deleted through the Delete HA operation on first attempt.
Recommended Action: Log out of the StorageCenter UI. Log back in, and press Delete HA again. Successive Delete HA operations will succeed.


SoftNAS Cloud®

...

3.4.3 Release - December 4, 2015

Overview

Version 3.4.3 fixes a licensing issue in 3.4.0-3.4.2 for SoftNAS Cloud Standard on AWS Marketplace. Version 3.4.3 is compatible with all editions of SoftNAS Cloud® NAS.

Upgrading

Upgrading from 3.4.0 through 3.4.2

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.


SoftNAS Cloud®

...

3.4.2 Release - November 21, 2015

Overview

Versions 3.4.2 provides additional security to major release version 3.4.0. Version 3.4.2 for all editions of SoftNAS Cloud® NAS is available. Upgrading to version 3.4.2 is highly recommended to address critical feature and security enhancements.

Upgrading

Upgrading from 3.4.0 or 3.4.1

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

Security Update in SoftNAS Cloud®

...

3.4.2

Security Update to Resolve Severe SoftNAS StorageCenter Security Vulnerability on Open Networks

This security update resolves a potentially severe security vulnerability in the SoftNAS StorageCenter Aapache web server that could allow remote code execution when combined with other attacks over an unprotected network such as the Internet. An attacker who successfully exploited the vulnerability could run arbitrary commands on the storage appliance. Customers who have properly restricted Internet-based access to StorageCenter using the recommend best practices that limit StorageCenter access to a limited number of approved IP addresses or that isolate StorageCenter access to private networks, are less likely to be impacted than those who provide open Internet-based StorageCenter access (which is never recommended).
This security update addresses the vulnerability by closing exploits in Apache web server.

New in SoftNAS Cloud®

...

3.4.0

360-degree Encryption™ – Data encryption all the time–at rest and in flight. Data-at-rest is encrypted through open source Linux Unified Key Setup (LUKs). LUKs is accepted as the standard for encryption of stored data. Data-in-flight is encrypted for CIFS and NFS file protocols.

...

Active Directory Integration Improvements – Trusted Active Directory Domains, user searches and domains with up to 1.35 million objects now supported.

Fixed in SoftNAS Cloud®

...

3.4.0

Key fixes to improve the SoftNAS experience include:

...

  • File permissions synchronize across CIFS shares and NFS exports
  • StorageCenter no longer randomly logs out user sessions
  • EULA "agree" button fixed to be accessible in FireFox 39.03

Errata for SoftNAS Cloud®

...

3.4.0 - 3.4.2

Due to a number of factors, SoftNAS instances may increase resource consumption when moving from POC to Production. Planning for production instances should reflect this by planning for these higher resource requirements. Examples where higher resources are needed include: increased IO load, replacing local storage such as EBS with S3, enabling SnapReplication, scheduling backups.
Recommended Action: Plan scale-out to production by anticipating the need to use larger instances and more resources for the SoftNAS VM.

...

Storage Pools protected with RAID 6 report Usable Capacity incorrectly by using the raw capacity value. Licensing is impacted.
Recommended Action: RAID 6 usable capacity is determined by subtracting 2 disks' capacity from a Storage Pool's raw capacity. Contact Support to obtain a larger license key.


SoftNAS Cloud®

...

3.4.0 Release - November 10, 2015

Overview

SoftNAS Cloud® NAS 3.4.0 is a maintenance release containing feature additions, fixes, and improvements.

Upgrading

Upgrading from 3.3.3 or 3.3.4:

...

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate, or Contact SoftNAS Support to schedule an upgrade session.

New in SoftNAS Cloud®

...

3.4.0

360-degree Encryption™ – Data encryption all the time–at rest and in flight. Data-at-rest is encrypted through open source Linux Unified Key Setup (LUKs). LUKs is accepted as the standard for encryption of stored data. Data-in-flight is encrypted for CIFS and NFS file protocols.

...

Active Directory Integration Improvements – Trusted Active Directory Domains, user searches and domains with up to 1.35 million objects now supported.

Fixed in SoftNAS Cloud®

...

3.4.0

Key fixes include:
• Alert system improved to decrease the number of generated emails
• Software upgrade fixed to work with HA
• 1-click software upgrade is restricted to version 3.3.0 and newer
• GUID Partition Tables (GPT) on S3 devices could have been corrupted when upgrading from versions older than 3.3.0.
• Adding 16TB EBS Volumes is now supported from StorageCenter
• IAM improved to be more restrictive
• Samba configuration file preserved across software updates
• Product Registration prompts 7 days after product launch
• NTP configurable for HA
• File permissions synchronize across CIFS shares and NFS exports
• StorageCenter no longer randomly logs out user sessions
• EULA "agree" button fixed to be accessible in FireFox 39.03

Errata for SoftNAS Cloud®

...

3.4.0

Due to a number of factors, SoftNAS instances may increase resource consumption when moving from POC to Production. Planning for production instances should reflect this by planning for these higher resource requirements. Examples where higher resources are needed include: increased IO load, replacing local storage such as EBS with S3, enabling SnapReplication, scheduling backups.
Recommended Action: Plan scale-out to production by anticipating the need to use larger instances and more resources for the SoftNAS VM.

...