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.

Note:  Please ensure that the root volume disk usage is below 75%, (at least 25% capacity remaining). If not enough space remains, please clear unused files from the root partition or call support to help you.
The software update will abort if there is less than 25% free space available on the root file system.

New in 4.3.0

New Kernel 4.14.138 - The kernel has been updated to 4.14.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

...