Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

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

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

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

For information on updating your instance: 

Updating Software

For upgrading a SNAP HA pairing:

Maintenance Mode

To migrate SoftNAS Instances:

How To Migrate SoftNAS Cloud® Instances

Fixed in SoftNAS Cloud® 3.5.1

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® NAS 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.


Note: Your update can take up to 2 hours for the update to complete if updating from below 3.4.9.4. If updating from more recent versions, the update could still take some time (up to 45 minutes). Do NOT terminate the update while in progress else errors may 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 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: As of version 3.5.1, the technical requirements for our No Downtime Guarantee have changed. In particular, the following minimum requirements must be met:

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

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

SoftNAS Cloud® NAS 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

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

For information on updating your instance: 

Updating Software

For upgrading a SNAP HA pairing:

Maintenance Mode

To migrate SoftNAS Instances:

How To Migrate SoftNAS Cloud® Instances

New in SoftNAS Cloud® NAS 3.5

New SoftNAS Cloud® NAS Editions and Capacities 

  • General Purpose: For workloads with basic networking, caching, deduplication and encryption requirements, SoftNAS Cloud® NAS General Purpose Edition balances cost vs. memory and CPU resources and  is a good starting point for basic workloads.
    • AWS: M4.2Xlarge
    • Azure: DS4_v2

  • High Performance: For read-intensive workloads needing larger memory-based read cache and additional CPU cores, SoftNAS Cloud® NAS High Performance Edition improves performance for deduplication, encryption and compression compared to SoftNAS Cloud NAS General Purpose Edition.
    • AWS: M4.4Xlarge
    • Azure: DS5_v2

  • Extreme Performance: For very demanding workloads requiring thousands of concurrent connections, SoftNAS Cloud® NAS Extreme Performance Edition utilizes maximum CPU power, IOPS, memory and very high speed networking throughput.
    • AWS: M4.10Xlarge
    • Azure: DS15_v2

  • Marketplace options now exist for 1TB up to 1PB capacities.

    For VM (Instance) and storage sizing guidance on  please see:

Object Backer for Object Storage -  ObjectBacker™ Backend Storage Acceleration - Patent pending ObjFast™ technology writes data to object storage up to 400% faster than prior SoftNAS Cloud® NAS versions, enabling customers to use lower cost cloud object storage backends (e.g., AWS S3 and Azure Blob) with performance levels rivaling that of cloud block storage backends (e.g., AWS EBS and Azure Disk).

Simplified Active Directory Wizard - It is now simpler to join Active Directory, and status messages are improved to help troubleshoot any issues faster.

In-Context Help - To improve user experience, In-Context QuickHelp is now provided as in-product links that lead to helpful technical documentation, Knowledgebase articles and videos as the user is accessing the relevant feature within the UI.

Simplified Secure Software Updates - Based on network security best practices, Simplified Secure Software Updates requires users to open only a single firewall port for SoftNAS Cloud NAS software updates instead of multiple firewall ports for connection to different Linux software update depots.

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

Fixed in SoftNAS Cloud® NAS 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.

iSCSI Intermittent dropouts during write cycles fixed - An issue in which intermittent LUN dropouts resulting in slow performance occurring in the write cycle has been resolved.

Update Process Fix - SoftNAS now uses SSL to mirror.softnas.com to provide updates.

Improved Error Messaging regarding Multi-Factor Authentication Limitations - SoftNAS currently cannot use accounts with Azure Multi-Factor Authentication when setting up SNAP HA. The error message provided ensures this problem is easily identified so the user can resolve the issue.

Proxy Update Issues Resolved - SoftNAS' simplified secure software update efforts have resulted in easier proxy setup, and has ensured that updates can get through without compromising security.

Internationalization of Active Directory Join Feature - Improvements added to ensure that our AD Join wizard recognizes UTF characters, and can accept domain controllers of foreign language origin.

Memory Validation checks - SoftNAS now ensures that a minimum RAM requirement of 3.5 GB is enforced for users of S3backer (Object Backer).

IAM Role flexibility - SoftNAS have introduced a new variable to our s3config.ini file to allow clients to use IAM Role names using their own naming conventions. SoftNAS has also simplified the default SofTNAS IAM Role by replacing specified EC2 ARNs and S3 ARNs with a variable.

Improved Object Storage Read Performance - S3 pools are now set to 1 MB record size on creation, ensuring that read performance is not throttled by heavy write cycles.

Windows 2012R2 Azure AD Join issue fixed - A bug preventing SoftNAS instances from joining an Azure based DC has been resolved.

Snapshot Threshold/Hourly Retention Bug Fix - An issue in which the Hourly Snapshot Retention  value was tied to the Snapshot Retention value has been resolved.

SNAP HA Azure VNET Flexibility - It is now possible to set two SoftNAS nodes as an HA pair using an Azure VNET created in a separate resource group.

Scheduled Snapshots now keep accurate count - only the number of snapshots specified are kept.

S3 support for Canada and London Regions - issues adding S3 devices to Canada and London region instances have now been resolved.

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

Errata for SoftNAS Cloud® NAS 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.

UTF-8 value display known issue - UTF-8 values from files (for example cyrillic usernames added from the Active Directory Wizard) are displayed incorrectly within the UI.

Quick Help Feature Known Issue -  Quick Help pop ups are currently resizeable, and show a vertical scroll bar, whether one is required or not.  These pop ups should not be resizeable, and the scroll bar should only appear if the content within the Quick Help pop up warrants it.

Kerberos Known Issue\Expected Behavior -  The Kerberos configuration will not be updated with the Domain Controller IP addresses (DCIPs) and records from the new AD wizard. Kerberos will instead use DNS to resolve all necessary records.

Error Message Unit Measurement Discrepancy - An error message alerting the user that he/she does not have adequate RAM for a selected feature displays the current available RAM in MB, and the amount required in GB. For example: "Insufficient RAM for this feature: 2047MB. At least 3.5 GB of RAM is required."

RAID 1 S3 Degraded Disk Misrepresentation - If a pool is created with software RAID 1 S3 object storage, and a disk is deleted, the pool does not show as degraded, despite the missing disk.
Note: Using software RAID other than RAID-0 on object storage is not SoftNAS recommended best practice.

Pool Status Known Issue - Storage Pool status (for example if a disk device is taken offline, and a pool is in a degraded or offline status) must be manually refreshed in order for the current status to be accurately displayed.

AD Wizard Update Known Issue - The AD wizard icon in Volumes and LUNs should have 3 status options, but currently only shows 2, reflecting only if the AD wizard is currently connected successfully or not. The third status that is not currently showing would normally display that the AD wizard has been run successfully in the past, but is no longer connected. Instead, the icon returns to status 1,  in which it appears that the AD wizard has never been run.

Failed Request error - After software update, a failed request error may appear due to browser calling up cached content.
Recommended Action: Refresh the browser (Ctrl +f5) to return to login.

AWS Manage Samba Users Unknown Group prompt - When creating a new group from CIFS Shares>Samba Groups> Add New Group, a group name of "Unknown Group" is displayed by default. Using said default group name results in an error.
Recommended Action: Use a group name of your own choosing, rather than the prompted default.

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® NAS 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

Reboot Required for AWS and VMware instances if updating from 3.4.9.5 or earlier. No reboot required for upgrades from 3.4.9.6

Upgrading from 3.3.3 or 3.3.4

Reboot Required for AWS and VMware instances if updating from 3.4.9.5 or earlier. No reboot required for upgrades from 3.4.9.6.
Follow instructions to upgrade a highly available SNAP HA™ pair.

Upgrading from versions prior to 3.3.3

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® NAS 3.4.9.7

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

Fixed in SoftNAS Cloud® NAS 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.

Update Warning - Language added to beginning of update process logs reminding customers that an update can take up to two hours, and not to reboot system.


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

Reboot required for AWS and VMware instances.

Upgrading from 3.3.3 or 3.3.4

Reboot Required for AWS and VMware instances.
Follow instructions to upgrade a highly available SNAP HA™ pair.

Upgrading from versions prior to 3.3.3

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® NAS 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

Reboot required for AWS and VMware instances.

WARNING: Due to the size of the 3.4.9.5 update, it can take up to 2 hours for the update to complete. Do NOT terminate the update while in progress else errors may occur. If you feel that your update is taking longer than 2 hours, please contact SoftNAS support for assistance and do not reboot your instance.

Upgrading from 3.3.3 or 3.3.4

Reboot Required for AWS and VMware instances.
Follow instructions to upgrade a highly available SNAP HA™ pair.

WARNING: Due to the size of the 3.4.9.5 update, it can take up to 2 hours for the update to complete. Do NOT terminate the update while in progress else errors may occur. If you feel that your update is taking longer than 2 hours, please contact SoftNAS support for assistance and do not reboot your instance.

Upgrading from versions prior to 3.3.3

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® NAS 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.

Sipcalc included in installation package - This allows SoftNAS HA to operate in isolated environments (without access to the internet) without needing to connect externally for sipcalc download.

SnapReplicate Throttling Improvements - Throttling now operates on all streams, rather than a per stream basis, ensuring that total outbound replication is throttled, rather than per individual volumes.Throttling levels update according to available bandwidth based on iptables. Throttling can be enabled and disabled through settings.

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® NAS 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.

Deletion of Disks in Active Pool Prevented - A "loophole" in which it was possible to accidentally delete a disk in an active pool has now been prevented.

Kerberos DNS issue fixed - Fixed an issue hard-coding Kerberos to a single KDC/Admin Server, rather than using DNS lookup to find a KDC/Admin server. This eliminates KDC/Admin Server as a single point of failure.

Hosts File Issue corrected - Fixed a bug in which the etc/hosts file would not return with correct values after a reboot in some cases.

Volume Naming Issue corrected - Users can now create volumes of the same name on different pools.

Snapclone Volume Mount issue fixed - A bug in which volumes created from Snapclones within the UI (but not if mounted from command line) would appear but without data has been resolved.

Consumption-based licensing persistent billing error message resolved - An issue in which the “Can not connect to AWS Billing” error would persist even after connectivity issues were fixed has now been eliminated.

Replication Hang Issue Resolved - Fixed an issue where replication could hang for lengthy periods without an error or notification.

Samba/NFS Failover issue - After a failover, Delta-Sync by design temporarily shuts down Samba and NFS to prevent data loss during a transfer. The ability to restart the service immediately has been introduced.

Premium Disk Raid 0 Pool Creation Error fixed - An erroneous error when creating a RAID 0 pool from P20 512GB Azure disks has been resolved.

Delta-Sync File-mapping issue fixed - An issue in which failures could occur due to Delta-Sync failing to map files correctly to .CSV has been resolved.

VIP mapping failure upon reboot fixed - An issue was occurring when a reboot was performed when HA was deactivated resulting in loss of the VIP(becomes unassigned). This has now been resolved.

Ensured that a reboot prompt is provided after each update.

Log verbiage fix - Improved instructions matching the user interface have been introduced in log messages to resolve SnapReplicate failures.

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

Errata for SoftNAS Cloud® NAS 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® NAS 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

A reboot is required for any users leveraging cloud disks.

Upgrading from 3.3.3 or 3.3.4

A reboot is required for any users leveraging cloud disks.

Follow instructions to upgrade a highly available SNAP HA™ pair.

Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 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

A reboot is required for any users leveraging cloud disks.

Upgrading from 3.3.3 or 3.3.4

A reboot is required for any users leveraging cloud disks.
Follow instructions to upgrade a highly available SNAP HA™ pair.

Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 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

A reboot is required for any users leveraging cloud disks.

Upgrading from 3.3.3 or 3.3.4

A reboot is required for any users leveraging cloud disks.
Follow instructions to upgrade a highly available SNAP HA™ pair.

Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 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® NAS 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® NAS 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

A reboot is required for any users leveraging cloud disks.

Upgrading from 3.3.3 or 3.3.4

A reboot is required for any users leveraging cloud disks.
Follow instructions to upgrade a highly available SNAP HA™ pair.

Upgrading from versions prior to 3.3.3

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® NAS 3.4.9.1

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

Case Sensitivity Option/Volume Creation - A checkbox has been provided to allow users to determine whether to apply case sensitivity to a pool.

Selectable Software Updates - Software Updates now shows up to 3 of the latest release versions available for upgrade (if the user has not updated for more than 3 releases), and allows the user to select from between them, based on linked release notes.

Self-Configured Disk Authentication Version Option - In the Add Cloud Disk Extender wizard for Self-Configured Disks, users can now specify the authentication version (v2 or v4) used for the object storage in question.

AWS Billing Gateway Failure to Connect Alert added - FCP customers will now be alerted if the connection to the AWS Billing Gateway fails, and provided a timer in order to know when services will be disconnected.

Support for AWS US East Ohio Region - The AWS/Ohio region is now accessible from within StorageCenter's Add Devices wizard, allowing users to create S3 disks from this region.

HA Validation Pre-Checks - Validations have been added to ensure key HA requirements are all configured prior to SNAP HA setup. These include:

  • 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® NAS 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.

Etc./Hosts File Fix - Duplicate 127.0.0.1 entries no longer appear in the hosts file after a reboot.

Importing S3 Disk Fix - If importing an S3 volume and the user specified an incorrect volume size (ie; a smaller size than it was created as), StorageCenter did not alert the user of the issue. This has been corrected.

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® NAS 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.

Due to persistent display issues with header elements in Microsoft Edge, we no longer support the browser.
Recommended Action: Open the instance in a supported browser, such as Internet Explorer or Chrome. 

In the Available Devices panel of Disk Devices, the Make and Model column presents SoftNAS created Azure disks as "Msft Virtual Disks" rather than "SoftNAS, Azure Virtual Disk". This will be corrected in a later release.
Recommended Action: None 

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


SoftNAS Cloud® NAS 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

No reboot is required.

Upgrading from 3.3.3 or 3.3.4

No reboot is required.
Follow instructions to upgrade a highly available SNAP HA™ pair.

Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 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

A reboot is required for any users leveraging cloud disks.

Upgrading from 3.3.3 or 3.3.4

A reboot is required for any users leveraging cloud disks.
Follow instructions to upgrade a highly available SNAP HA™ pair.

Upgrading from versions prior to 3.3.3

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® NAS 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.

Azure storage backends for SoftNAS Cloud:

  • Azure Premium Storage – SSD based block storage for high-performance, I/O intensive workloads.
  • Azure General Purpose Storage – HDD based block storage for general purpose workloads.
  • Azure Hot Blob Storage - Object storage optimized for frequent I/O data.
  • Azure Cool Blob Storage - Object storage optimized for low I/O and low cost (safe-keeping of less frequently accessed file data).



SNAP HA™ – now on Azure – SoftNAS' patent-pending SNAP HA™ allows easy high-availability (HA) and cluster configuration for robust non-stop application operation with automatic failover and seamless transfer across controllers. SNAP HA, combined with Azure availability sets, makes the unique SoftNAS No Storage Downtime Guarantee available for customers using SoftNAS Cloud for Microsoft Azure.

Role-based Access Control (RBAC) – Ensure greater security and control for organizations with multiple users or systems on Microsoft Azure. RBAC allows management of users, roles and permissions to provide defined parameters for delegated administration.

Support Change: As of 3.4.8 softnas does not support launching vms on the Classic Portal. The Azure Resource Manager (ARM) is the only supported platform. Prominent SoftNAS features (notably high availability) will not function on VMs using Classic Portal.

All Platforms

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® NAS 3.4.8

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

False error message removed - The false error message when restoring a pool with LUKS encryption enabled is eliminated.

Fix to SNAP HA wizard on proxy instances - EIP option no longer displays if creating a SNAP HA pairing on a proxy enabled SoftNAS instance.

Error Message fixed - If entering a non-existent pool name into the Create Volume wizard, an error message reading "Creating volume: No such pool: r0_dfaf" will be generated.

S3 Import failure display issue fixed - A disk with 0 bytes no longer displays upon a failed S3 import.

'Total Space Used' stat fixed - Space calculations for block based volumes now display correctly.

Self-Configured Disk bucket error fixed - A bucket error occurring when rebooting a proxy instance using self-configured disks has been eliminated.

Fixed Proxy exclusion list- source and target exclusions for replication now auto-populate correctly before and after replication is disabled/re-enabled.

Fixed Display Issues in Microsoft Edge - Scroll bars within UI elements now display and function properly.

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

Errata for SoftNAS Cloud® NAS 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.

1 click upgrade feature for versions below 3.3.3 is not functioning in Internet Explorer.
Recommended Action: Perform the operation in Mozilla or Firefox. 

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.

Due to SSL certificate renewal process, after software update, a failed request error may appear due to browser calling up cached content. Alternatively, the software update complete message may appear twice, followed by a white web page.
Recommended Action: For either issue, refresh the browser (Ctrl +f5) to return to login.

Azure AD password expiry can cause HA and Add Disk failures.
Recommended Action: To disable password expiry, see Azure Documentation.

When importing a deleted pool, the import pool dialog box may not disappear, though the pool imports successfully.
Recommended Action: Verify pool import, and close the dialog box.

Table headers for Disk Devices, Volumes and LUNS, Storage Pool panels may shift out of position/out of sight if you navigate to another area while a task (create/delete) is in process.
Recommended Action: Refresh browser, or log out/log in if this occurs.

SoftNAS login screen can intermittently appear in SoftNAS UI panel rather than in browser if session expires.
Recommended Action: Refresh your browser, login as usual.

Deleting an Azure Blob Disk from an instance via the Azure Portal can cause your SoftNAS instance to become unstable/unresponsive.
Recommended Action: Delete Azure Blob disks from within the SoftNAS UI.

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® NAS 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

A reboot is required for any users leveraging cloud disks.

Upgrading from 3.3.3 or 3.3.4

A reboot is required for any users leveraging cloud disks.
Follow instructions to upgrade a highly available SNAP HA™ pair.

Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 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

No reboot is required.

Upgrading from 3.3.3 or 3.3.4

No reboot is required.
Follow instructions to upgrade a highly available SNAP HA™ pair.

Upgrading from versions prior to 3.3.3

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® NAS 3.4.7.3

Fix to default settings - Disabled Linux Memory Overcommit.


SoftNAS Cloud® NAS 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

No reboot is required.

Upgrading from 3.3.3 or 3.3.4

No reboot is required.
Follow instructions to upgrade a highly available SNAP HA™ pair.

Upgrading from versions prior to 3.3.3

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® NAS 3.4.7.2

Fix to Ajax errors - resolved an issue specific to 3.4.7 in which Ajax errors would result when rejoining a domain.

Fix to NFS Exports Functionality - When creating NFS exports, the option to make the export available to everyone was not functioning correctly. This has been resolved.

Fix to NFS Exports bind entries - An issue with NFSv4 bind entries overwriting required entries for NFSv3 compatibility has been fixed.

Fix to AWS VIP routing table - When failing over in an HA setting, an error would occur upon required update of the AWS VIP routing table. This has been resolved.

Fix to SNAP HA deletion error - An error that would occur when attempting to delete a SNAP HA pairing has been resolved.

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® NAS 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

No reboot is required.

Upgrading from 3.3.3 or 3.3.4

No reboot is required.
Follow instructions to upgrade a highly available SNAP HA™ pair.

Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 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

A reboot is required in order to see the benefits of the fixes added in this release. Existing functionality will not be affected pending reboot. SoftNAS recommends upgrading during a maintenance window.

Upgrading from 3.3.3 or 3.3.4

A reboot is required in order to see the benefits of the fixes added in this release. Existing functionality will not be affected pending reboot. SoftNAS recommends upgrading during a maintenance window.
Follow instructions to upgrade a highly available SNAP HATM pair.

Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 3.4.7

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

CIFS Samba Configuration issue fixed - Fixed an issue with user level authentication for CIFS and Active Directory integration.

AWS key error on Proxy instances - Fixed an issue in which EBS and S3 disks added to a SoftNAS instance that was protected by a proxy server would result in an AWS error message. Bucket errors on S3 when connected to a proxy were also resolved.

Software Update via Proxy - Fixed an issue where software updates could not be installed when connected via a proxy.

License Authentication/Proxy issue - Fixed an issue with activating licenses of SoftNAS instances that are installed behind a proxy.

Updates Functionality in Webmin Panel - Users can now perform OS Yum updates from within the Webmin Panel.

Log Message Classification Change - Fixed an HA failure message in SoftNAS logs which was misclassified as a "Warning" rather than an "Error". The message has been changed to:
"Error ---> HA controller is not configured! Using SnapReplicate role instead of HA Controller as authoritative."

Fix to CLI Created Disks - Fixed an issue where disks created in CLI would default to a setting of sync=disabled.

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.

Improved NFS Export Functionality - Users can now add multiple hosts via our Webmin Panel with comma separated values.

Exports and Shares Displaying after Pool Deletion - Fixed an issue in which NFS Exports and AFP Volume Shares would continue to display after a pool was deleted.

Importing S3 disks from Frankfurt Region Resolved - Errata issue identified in 3.4.6 is now resolved. Users can now import S3 disks from Frankfurt without issue.

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® NAS 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.

As we are doing a yum update as part of the 3.4.7 update, it could take time to complete. The time varies depending on Instance or VM resources.
Recommended Action: Plan the update for a maintenance window.

A misleading error message is generated if the wrong name is typed into the storage pool field when creating a volume - the error message reads 'Creating Volume: Not enough space at pool test.' It will be changed in an upcoming release to state that the pool specified does not exist.

S3 volumes created and attached as iSCSI LUNs are not displaying the disk use percentage in the Volumes table.
Recommended action: Monitor iSCSI Volumes in the Overview section to avoid running out of disk space.

After upgrading your instance, your instance will refresh. A prompt should appear telling you to reboot your instance. It currently does not.
Recommended Action: Reboot your instance after upgrade.

If running your SoftNAS instance behind a proxy, you may run into issues with running a Yum update on your SoftNAS instance. Certain mirror lists may return a 404 error (not found).
Recommended Action: In the command shell, run the 'yum clean all' command, and then 'yum update' in order to resolve the issue.

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® NAS 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

No reboot is required.

Upgrading from 3.3.3 or 3.3.4

No reboot is required.
Follow instructions to upgrade a highly available SNAP HATM pair.

Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 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

No reboot is required.

Upgrading from 3.3.3 or 3.3.4

No reboot is required.
Follow instructions to upgrade a highly available SNAP HATM pair.

Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 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

A number of S3 improvements are included as part of the upgrade. To take full advantage of the S3 improvements, a reboot is required. S3 Cloud Disks will continue to function without a reboot, but at the pre-upgrade level of functionality.

Upgrading from 3.3.3 or 3.3.4

A number of S3 improvements are included as part of the upgrade. To take full advantage of the S3 improvements, a reboot is required. S3 Cloud Disks will continue to function without a reboot, but at the pre-upgrade level of functionality.

Follow instructions to upgrade a highly available SNAP HATM pair.

Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 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.

After upgrading to 3.4.6 (or later) and rebooting, it is recommended to delete any unused "s3cachepool" pools that were previously assigned for the block cache file storage, as they are no longer used. The block devices used for these pools can be reassigned as read cache, write log, or decommissioned.

Additionally, after upgrading to 3.4.6, it is necessary to reboot the instance in order for all of the improvements to be installed. S3 Cloud Disks will continue to function, but until the system is rebooted not all of the improvements will have been applied. Reboot is expected to take some time as the software updates are applied, particularly for S3 customers. The time required for the reboot to complete is dependent on the amount of data in the cache, and the speed of your network connection. See Errata for more details.

Frankfurt Region HA issue: Fixed an authentication issue preventing HA setup from functioning in the Frankfurt region.

Erroneous Dialog Windows: Fixed an issue in which HA installation would display several unnecessary dialog windows.

AD Domain Field Character Limit: Increased the previously restrictive character limit to 255 characters.

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® NAS 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.

When running a software update on platforms other than AWS an error may be shown in the log: "curl: (7) couldn't connect to host".
Recommended Action: It is safe to ignore this error, and the update will complete successfully.

An issue may occur when deleting SoftNAS Cloud Extender disks where the disk continues to appear in the disk devices panel and the Storage Center user interface is unable to be displayed.
Recommended Action: The issue will resolve itself and Storage Center will provide full functionality when the delete operation completes.

The SoftNAS Dashboard> Performance Panel does not include all types of filesystem activity in the throughput graph.

Errors may occur importing S3 disks that are members of a Storage Pool composed of multiple S3 disks. SoftNAS Support can assist if it is necessary to import Storage Pools that span multiple S3 disks.
If configured in a SNAP HATM/SnapReplicate configuration, volumes deleted from the primary node are not deleted from the secondary. A takeover initiated from the target node will replicate the volume again.
Recommended Action: If you need to remove the volume and its data permanently, delete the volume from both nodes.

iSCSI targets reconnect after a reboot, but disk devices may not show as available, due to a delay to the start of ZFS services.
Recommended Action: Refresh after a minute or two, and the disks will reappear.

If restoring a pool with LUKS encryption enabled, a false error message may be generated in the logs. The restoration process will successfully restore the selected pool and data.
Recommended Action: No action required, disregard error message.

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® NAS 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

No reboot is required.

Upgrading from 3.3.3 or 3.3.4

No reboot is required.
Follow instructions to upgrade a highly available SNAP HATM pair.

Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 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® NAS 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

No reboot is required.

Upgrading from 3.3.3 or 3.3.4

No reboot is required.
Follow instructions to upgrade a highly available SNAP HATM pair.

Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 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® NAS 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® NAS 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

No reboot is required.

Upgrading from 3.3.3 or 3.3.4

No reboot is required.
Follow instructions to upgrade a highly available SNAP HATM pair.

Upgrading from versions prior to 3.3.3

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® NAS 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

No reboot is required.

Upgrading from 3.3.3 or 3.3.4

No reboot is required.
Follow instructions to upgrade a highly available SNAP HATM pair.


Upgrading from versions prior to 3.3.3

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® NAS 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® NAS 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.

Apple File Protocol Support – Apple File Protocol (AFP) offers file services for Mac OS X. Now Mac users can consolidate time machine backups and search for files with Spotlight when using SoftNAS with AFP for centralized storage.

Dual Factor Authentication – Prevent unauthorized access to SoftNAS management console with two-step authentication for SoftNAS StorageCenter™ through Google Authenticator.

Login Protection from Bots – Human verification through Google reCAPTCHA prevents bots from programmatically gaining access to the SoftNAS management console.

Red Hat AMI on AWS – SoftNAS Cloud for Red Hat Enterprise Linux (RHEL) is now available as a separate RHEL 7 AMI on AWS Marketplace.

Hitachi Data Systems S3 Support – Easily add Hitachi Content Platform (HCP) within StorageCenter to provide file services for Hitachi object storage.

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® NAS 3.4.0

Key fixes to improve the SoftNAS experience 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® NAS 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.

S3 based Storage Pools continue to grow over time, which can affect S3 bucket usage.
Recommended Action: Contact Support for the patch for Trim/Discard.

SnapReplicate does not replicate SnapClones. The Event Log reports not transferring SnapClones as an error.
Recommended Action: Be aware that SnapClone data is not protected with SnapReplication and HA.

Log files sent by Support Report can fail when too large. Failure is indicated by a pop-up status "Failure: Ajax communication failed".
Recommended Action: Contact Support to transfer log files through FTP.

Users are allowed through StorageCenter UI to remove disk devices from newly created storage pools, even when files are stored in a pool.
Recommended Action: After creating a storage pool, close and reopen the Disk Devices tab before taking any action on devices in the tab.

EBS Volumes may be incorrectly shown as Internal Devices in the Disk Devices tab if created added from the AWS console while other devices are added from StorageCenter.
Recommended Action: Do not add disk devices from StorageCenter and AWS console at the same time.

Errant error message is shown for loading AFP in SnapReplicate event log. The errrant message can be viewed in the Events section of Replication Control Panel, "ERROR: AFP Netatalk service failed to reload in remote node…".
Recommended Action: The message is invalid. Ignore.

Refreshing the SnapReplicate tab when connected through RDP will cause the UI frames to scroll to right.
Recommended Action: The issue is cosmetic only. Avoid continual refreshes of the SnapReplicate tab when connected to the UI through RDP.

UI has compatibility issues with FireFox version 41.0.1. A specific example is that the "Next" button on SnapReplicate wizard does not get enabled.
Recommended Action: Use earlier version of FireFox such as 40.0.3 or another browser such as Internet Explorer, Chrome, Safari.

In General System Settings, the webmin screen lists NFS Exports twice under Networking. NFS v4 and v3 are supported, and are shown here as separate selections.
Recommended Action: Select each NFS Exports option to find the version interested in.

In the CIFS Shares Tab, Security and Access a user can be selected multiple times.
Recommended Action: Avoid selecting a user more than once.

On the Microsoft Azure platform, a disk device that has been assigned to a storage pool may be listed as Ready to Assign in Disk Devices.
Recommended Action: Take care with SoftNAS on Azure, to assign a disk device to a storage pool only once.

Storage Pools with a mix of encrypted and unencrypted S3 buckets are not recommended.
Issues are noted when deleting mixed encryption S3 pools.
Recommended Action: Do not mix Storage Pools with encrypted and unencrypted S3 buckets. If such pools are deleted, reboot to access StorageCenter UI.

The Disk Devices tab in StorageCenter does not update status for S3 devices when the S3 devices are deleted from the AWS console.
Recommended Action: Don't delete devices from the AWS Console that are in use. Delete S3 devices from StorageCenter Disk Devices before deleting from AWS Console.

In a storage pool with S3 devices, when a hot spare condition occurs from a spare S3 device, StorageCenter UI may be unresponsive.
Recommended Action: Due to the highly durable nature of object storage, using hot spares in an S3-based storage pool is not recommended. Reboot instance if the UI is found unresponsive when using S3 hot spares.


Deleting a target for an iSCSI share with multiple targets may cause all targets to become disconnected from that iSCSI share.
Recommended Action: Reconnect any targets from the iSCSI LUN Targets tab.


Connecting to an iSCSI LUN may cause an errant device to appear in the Disk Devices tab. Device shows up as 0 bytes and needing to be un-mounted.
Recommended Action: Avoid cleaning up or using 0 byte disk devices in the Disk Devices tab.

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® NAS 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:

No reboot is required.

Upgrading from versions prior to 3.3.3

1-click upgrades are not supported from versions older than 3.3.3. Follow instructions to migrate.

Upgrading from versions prior to 3.3.3

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® NAS 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.

Apple File Protocol Support – Apple File Protocol (AFP) offers file services for Mac OS X. Now Mac users can consolidate time machine backups and search for files with Spotlight when using SoftNAS with AFP for centralized storage.

Dual Factor Authentication – Prevent unauthorized access to SoftNAS management console with two-step authentication for SoftNAS StorageCenter™ through Google Authenticator.

Login Protection from Bots – Human verification through Google reCAPTCHA prevents bots from programmatically gaining access to the SoftNAS management console.

Red Hat AMI on AWS – SoftNAS Cloud for Red Hat Enterprise Linux (RHEL) is now available as a separate RHEL 7 AMI on AWS Marketplace.

Hitachi Data Systems S3 Support – Easily add Hitachi Content Platform (HCP) within StorageCenter to provide file services for Hitachi object storage.

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® NAS 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® NAS 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.


S3 based Storage Pools continue to grow over time, which can affect S3 bucket usage.
Recommended Action: Contact Support for the patch for Trim/Discard.


SnapReplicate does not replicate SnapClones. The Event Log reports not transferring SnapClones as an error.
Recommended Action: Be aware that SnapClone data is not protected with SnapReplication and HA.

Log files sent by Support Report can fail when too large. Failure is indicated by a pop-up status "Failure: Ajax communication failed".
Recommended Action: Contact Support to transfer log files through FTP.


Users are allowed through StorageCenter UI to remove disk devices from newly created storage pools, even when files are stored in a pool.
Recommended Action: After creating a storage pool, close and reopen the Disk Devices tab before taking any action on devices in the tab.

EBS Volumes may be incorrectly shown as Internal Devices in the Disk Devices tab if created added from the AWS console while other devices are added from StorageCenter.
Recommended Action: Do not add disk devices from StorageCenter and AWS console at the same time.


Errant error message is shown for loading AFP in SnapReplicate event log. The errrant message can be viewed in the Events section of Replication Control Panel, "ERROR: AFP Netatalk service failed to reload in remote node…".
Recommended Action: The message is invalid. Ignore.

Refreshing the SnapReplicate tab when connected through RDP will cause the UI frames to scroll to right.
Recommended Action: The issue is cosmetic only. Avoid continual refreshes of the SnapReplicate tab when connected to the UI through RDP.

UI has compatibility issues with FireFox version 41.0.1. A specific example is that the "Next" button on SnapReplicate wizard does not get enabled. Recommended Action: Use earlier version of FireFox such as 40.0.3 or another browser such as Internet Explorer, Chrome, Safari.

In General System Settings, the webmin screen lists NFS Exports twice under Networking. NFS v4 and v3 are supported, and are shown here as separate selections.
Recommended Action: Select each NFS Exports option to find the version interested in.

In the CIFS Shares Tab, Security and Access a user can be selected multiple times.
Recommended Action: Avoid selecting a user more than once.

On the Microsoft Azure platform, a disk device that has been assigned to a storage pool may be listed as Ready to Assign in Disk Devices.
Recommended Action: Take care with SoftNAS on Azure, to assign a disk device to a storage pool only once.

Storage Pools with a mix of encrypted and unencrypted S3 buckets are not recommended.
Issues are noted when deleting mixed encryption S3 pools.
Recommended Action: Do not mix Storage Pools with encrypted and unencrypted S3 buckets. If such pools are deleted, reboot to access StorageCenter UI.

The Disk Devices tab in StorageCenter does not update status for S3 devices when the S3 devices are deleted from the AWS console.
Recommended Action: Do not delete devices from the AWS Console that are in use. Delete S3 devices from StorageCenter Disk Devices before deleting from AWS Console.

In a storage pool with S3 devices, when a hot spare condition occurs from a spare S3 device, StorageCenter UI may be unresponsive.
Recommended Action: Due to the highly durable nature of object storage, using hot spares in an S3- based storage pool is not recommended. Reboot instance if the UI is found unresponsive when using S3 hot spares.

Configuring Storage Pools with encrypted S3 devices protected with RAID 5 may require a reboot to access StorageCenter.
Recommended Action: Due the highly durable nature of object storage, using RAID with S3-based storage pool is not recommended. Reboot instance if the UI is found unresponsive when using encrypted S3 with RAID 5.

Deleting a target for an iSCSI share with multiple targets may cause all targets to become disconnected from that iSCSI share.
Recommended Action: Reconnect any targets from the iSCSI LUN Targets tab.

Connecting to an iSCSI LUN may cause an errant device to appear in the Disk Devices tab. Device shows up as 0 bytes and needing to be un-mounted.
Recommended Action: Avoid cleaning up or using 0 byte disk devices in the Disk Devices tab.

An iSCSI LUN exported by SoftNAS to VMware ESXi will not automatically reconnect after the SoftNAS VM is rebooted.
Recommended Action: In StorageCenter, navigate to the tab iSCSI LUN Targets. Select the target and click Add a new iSCSI.

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.


  • No labels