Archived: SoftNAS 4 Release Notes
- Former user (Deleted)
Buurst SoftNAS® 4.4.5 Release -, December 11th, 2020
Overview
SoftNAS has changed its name to Buurst (See https://www.buurst.com/)
Buurst's SoftNAS 4.4.5 is a maintenance release containing bug fixes.
Fixed in 4.4.5
Lift and Shift Fixes
Lift and Shift EFS Source selection issue - An issue in which the EFS source could not be selected from the UI in order to be mounted (but could be mounted from the CLI) has been resolved.
Miscellaneous Fixes
Update related bucket error - An issue in which after an update would occasionally result in an InvalidBucketName error when using CEPH based storage has been resolved. If using CEPH based object buckets please contact support prior to the upgrade for assistance.
Known Issues 4.4.5
Lift and Shift UI capacity tag issue - In the Lift and Shift UI, the capacity tag may display GB instead of TB in the "Target Disks" menu. This has no functional impact and is a display issue only. This will be addressed in a future release.
SmartTiers pool deletion issue - If a SmartTiers pool is deleted while block migration is in progress, it's child pools may not get deleted and will have to be deleted manually.
SmartTiers pool expansion error message - If expanding a SmartTiers pool while block migration is in progress a message reading “unknown error" may be displayed. This can be ignored as it is a UI only issue. Clicking OK will clear the error message.
Disk Devices UI applet unresponsive during SmartTiers Pool expansion - When expanding a SmartTiers Pool in the background, the Disk Devices UI applet could display a blank screen. This will resolve itself when the SmartTiers expansion task is complete.
Storage Administration UI - An issue wherein the storage administration menu could become duplicated has been seen. Logging out of StorageCenter and logging back in will resolve this issue.
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.4.4.
For information on updating your instance:
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 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: For version 4.4.4 our No Downtime Guarantee™ has the following minimum technical requirements:
- Software version must be 4.4.4 or above.
- Software updates must be applied within 30 days of availability.
For more details on our No Downtime Guarantee, click here.
Buurst SoftNAS® 4.4.4 Release - August 1st, 2020
Overview
SoftNAS has changed its name to Buurst (See https://www.buurst.com/)
Buurst's SoftNAS 4.4.4 is a maintenance release containing bug fixes and important security updates.
New in 4.4.4
Replication Performance improvements - Buurst has switched to ZSTD compression for replication transfers. This give a performance improvement gain of up to 40% for data replication. More info on ZSTD can be found here: https://facebook.github.io/zstd/
Lift and Shift Improved File Scan Performance - Scans of Lift and Shift source locations with a high number of file system objects are now much quicker. In lab, a source with 1 TiB of data and 1.5 million objects was cut from 92 hours to 4 hours, using 1 GbE networking.
Fixed in 4.4.4
Smart Tiers Fixes
SmartTiers Migration Policies fix - An issue in which migration policy settings were not retained after a reboot has been resolved.
SmartTiers storage expansion issue - An issue in which expansion of SmartTiers storage could potentially result in data corruption has been resolved.
SmartTiers UI - UI display now displays consistent usage status.
SmartTiers Migration Improvements - Resolved issues related to data consistency during SmartTiers migration of data between tiers.
Lift and Shift Fixes
Lift and Shift Pool Creation - The pool creation process has now been improved to provide better feedback if invalid parameters are provided.
SnapReplicate/SNAP HA Fixes
SNAP HA display issue - Removed unsupported SNAP HA recovery options within the UI on VMware.
Snapshot Retention Policy - The snapshot weekly retention policy defaulted to zero. This has been changed to 1, to ensure that snapshots are retained at least one week unless otherwise specified.
Snap Replication configuration issue - A mismatch between the mbuffer block size and the Snap Rep block size could result in memory fragmentation impacting performance has been resolved.
Miscellaneous Fixes
Updated ZFS to v0.8.3-3 -This ZFS upgrade addresses a potential ZFS panic issue with send/receive VERIFY3 operations.
Support Logs and ZFS history improvement - Fixed an issue where ZFS history logs would fill the root file system. This now gets compressed in-line instead of downloading to root and then compressing.
Buurst Support Chat options- Buurst's Support Chat window can now be disabled across reboots.
VMware Hidden Shares - A reinstall of SNAP HA™ would fail when hidden shares were present.
Software Update page link - Fixed an issue where the release note link was not functional when navigating from the “Software Update” applet.
Truncated or locking config files - An issue in which config files were truncated or locked, potentially resulting in abnormal system behavior such as unexpected failovers and intermittent loss of the VIP.
Legacy Licensing issue - An issue with inaccurate pool size calculations that could potentially result in a License error displaying that the capacity entitlement had been exceeded has been resolved.
SoftNAS CLI - An issue in which EBS based snapshots were not being created when initiated via the softnas-cmd CLI has been resolved.
Samba Logs and Log Rotation - An issue which resulted in nested compressed logs that were not usable has been resolved.
Security Fixes
Several security fixes have been resolved with SoftNAS 4.4.4, including:
CVE-2018-17192: Missing X-Frame : Indicates to a browser whether a page can be rendered into a frame or other type of embedded object
CVE-2018-12302: Missing http only attribute
CVE-2018-17192: Clickjacking: X-Frame-Options header missing
CVE-2019-19089: Missing X-Content-Type-Options
CVE-2016-6884, CVE-2013-0169: TLS v1.1
CVE-2013-2566, CVE-2015-280, CVE-2015-4000, CVE-2013-2566: Weak Ciphers
Known Issues 4.4.4
Lift and Shift UI capacity tag issue - In the Lift and Shift UI, the capacity tag may display GB instead of TB in the "Target Disks" menu. This has no functional impact and is a display issue only. This will be addressed in a future release.
SmartTiers pool deletion issue - If a SmartTiers pool is deleted while block migration is in progress, it's child pools may not get deleted and will have to be deleted manually.
SmartTiers pool expansion error message - If expanding a SmartTiers pool while block migration is in progress a message reading “unknown error" may be displayed. This can be ignored as it is a UI only issue. Clicking OK will clear the error message.
Disk Devices UI applet unresponsive during SmartTiers Pool expansion - When expanding a SmartTiers Pool in the background, the Disk Devices UI applet could display a blank screen. This will resolve itself when the SmartTiers expansion task is complete.
Storage Administration UI - An issue wherein the storage administration menu could become duplicated has been seen. Logging out of StorageCenter and logging back in will resolve this issue.
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.4.4.
For information on updating your instance:
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 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: For version 4.4.4 our No Downtime Guarantee™ has the following minimum technical requirements:
- Software version must be 4.4.4 or above.
- Software updates must be applied within 30 days of availability.
For more details on our No Downtime Guarantee, click here.
Buurst SoftNAS® 4.4.3 Release - May 21st, 2020
Overview
SoftNAS has changed its name to Buurst (See https://www.buurst.com/)
Buurst's SoftNAS 4.4.3 is a maintenance release containing bug fixes and important security updates.
New in 4.4.3
New Regions added in AWS - Milan and Cape Town regions are now enabled.
AWS CLI Update - SoftNAS has updated to AWS CLI v2 in order to:
- support the new regions added
- continue support for Python version 2.6
Fixed in 4.4.3
Configuration file writing/reading race condition - A race condition could manifest between configuration file writing and reading in SNAP HA environments. In extreme cases, a failover could be triggered as a result. This issue may also have resulted in occasional recoverable client connection loss. This issue has now been resolved.
Minor Volumes and LUNs UI issue - A white space in the graphic for capacity was shown when the volume neared capacity. This is now resolved.
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:
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 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
Buurst SoftNAS® 4.4.2 Release - May 4th, 2020
Overview
SoftNAS has changed its name to Buurst (See https://www.buurst.com/)
Buurst's SoftNAS 4.4.2 is a maintenance release containing bug fixes and important security updates.
New in 4.4.2
Login Debugging Improvements - Added additional debug logging for StorageCenter logins.
Fixed in 4.4.2
Upgrade Issue - Fixed an upgrade related race condition in SNAP HA ® where the node failure mode was not correctly set. This issue would be seen when both nodes attempted to obtain primary status and the VIP during a failover.
Routing Table issue - Fixed a timing issue where upon a transient VIP failure the check for SNAP HA® check would incorrectly update routing tables.
Reboot issue - Fixed an issue when rebooting the primary node of a SNAP HA® pair a wait of up to 20 minutes was seen before the instance became available.
VMware Console UI issue - When managing an instance on VMware, an issue could present itself where the VMware console UI would not launch and display. Instead, the following lines would repeat within the console:
openvt: exec failed: too many levels of symbolic linkssole: |
|---|
This issue has now been resolved.
Snapshot Expected Purge Issue - Fixed an issue where older snapshots were not getting purged as per schedule or aging. This issue could impact both stand-alone instances and SNAP HA® pairs. This issue would present itself in the logs by repeated lines within the snapshot scheduler regarding busy snapshots and the deletion being skipped. For example:
snserv.log:Sat Apr 04 2020 06:47:02.141 - INFO --> Scheduler: snapshot Pool1/DAA@hourly-20200402-190002 is busy, skipping it's deletion |
|---|
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:
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 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
Buurst SoftNAS® 4.4.1 Release - April 14th, 2020
Overview
SoftNAS has changed its name to Buurst (See https://www.buurst.com/)
Buurst SoftNAS 4.4.1 is a maintenance release associated with and to enable the launch of Buurst as the new company name and strategy. It contains a new packaging and pricing strategy for new deployments of the SoftNAS product for customers that start their deployment with SoftNAS version 4.4.1.
SoftNAS Previous Edition Upgrades: Customers running an existing SoftNAS Enterprise or Platinum deployment can upgrade to SoftNAS 4.4.1 if they have an existing subscription to SoftNAS in the region without changing their current pricing model. Maintenance upgrades for existing versions of SoftNAS Enterprise and Platinum will continue to be supported until further notice.
SoftNAS Marketplace Listing: As of SoftNAS 4.4.1, there will only be a single edition of the SoftNAS product in the AWS and Azure marketplaces in the form or two listings:
- Marketplace licensed: Billing is managed by the cloud marketplace for the SoftNAS software, compute (instance or VM) and storage
- BYOL: Billing for the SoftNAS software is managed by contract and license keys from Buurst Sales while compute (instance or VM) and storage continues to be managed by the cloud marketplaces (as done previously for SoftNAS Enterprise and Platinum)
SoftNAS Pricing: As of SoftNAS 4.4.1, customers using a new marketplace licensing and pricing deployment of SoftNAS will be charged by the hour based on the performance characteristics of the AWS Instance or Azure VM they deploy the new SoftNAS software on without Buurst charging additional cost for the amount of storage capacity attached to SoftNAS (no attached storage tax).
- Performance pricing is based on the resource capabilities of the underlying AWS Instance or Azure VM SoftNAS is running on.
- You will notice reflective pricing information in the marketplaces for the new SoftNAS software based on the size instance or VM you select in the marketplaces. For more information see https://www.buurst.com/
- The maximum disk capacity you can attach to SoftNAS may be limited by the selected AWS Instance or Azure VM, but there is not additional storage capacity charge as part of Buurst SoftNAS pricing.
SoftNAS Platinum Functionality: Lift and Shift™ and SmartTiers™ are included as features of the new SoftNAS product. Ultrafast™ and FlexFiles Architect™ have been deprecated and are no longer available features in the SoftNAS product.
Fixed in 4.4.1
There are no new fixes in the 4.4.1 version of SoftNAS. Customers may continue to run version 4.4.0 as the latest maintenance release for SoftNAS Enterprise and Platinum. Customers may also upgrade to version 4.4.1 to ensure they have all of the latest maintenance fixes in the 4.4.0 release.
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:
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 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.4.0 our No Downtime Guarantee™ has the following minimum technical requirements:
- Software version must be 4.4.0 or above.
- Software updates must be applied within 30 days of availability.
For more details on our No Downtime Guarantee, click here.
SoftNAS® 4.4.0 Release - April 1st, 2020
Overview
SoftNAS® 4.4.0 is a maintenance release containing bug fixes and important security updates.
New in 4.4.0
SNAP HA Enhancements - A number of enhancements have been made to SNAP HA to improve failover performance and resiliency.
- Faster Failovers - Failover data availability speed has been reduced to under 90 seconds through optimizations and quicker detection of events that trigger a failover.
- New Failover Triggers - Several new failover triggers to ensure even greater availability.
- IOping: Improved triggers to detect an issue with the ZFS file system on the primary node to detect an issue warranting a failover .
- TXG Sync Issues: New failover trigger to detect when events are occurring with TXG sync that will likely lead to a failure are detected, a failover will be triggered proactively to keep the system in a stable state.
Failed Node behavior options - An option is now available to determine the behavior of the failed node in an HA pair.
Note: VMware does not support these options and the failed node will be shut down.
- Reboot (default) - This setting will shut down and restart the failed node re-enabling HA on completion. This ensures SNAP HA ® regains HA without user intervention.
Note: In an AWS environment additional permissions are needed for the IAM role: ec2:StopInstances and ec2:RebootInstances. If these permissions are not present, the system will fall back to SSh-based shutdown mode. - Shutdown: This setting will shut down the failed node fencing it off. Manual intervention is needed to reestablish HA.
- None – This setting is for SoftNAS support use only. In this case the failed node will remain in its failed state to allow SoftNAS support to further analyze the system.
SnapReplicate™ Scheduling enhancements – Scheduling of multiple SnapReplicate jobs will now be staggered to avoid all of the replication jobs from running at once and causing high load on the system.
Lift and Shift Enhancements – Support for symlinks has been added. Currently only soft links are supported. Hard links will be treated as regular files.
Azure Managed Disks: A UI for the selection of different types of Azure managed disks has been added to StorageCenter.
AWS New Region Support – Support has been added for the use of SoftNAS in the following AWS Regions:
- China: Beijing and Ningxia
- Bahrain
Errata (Known Issues) 4.4.0
SNAP HA® may need to be manually reactivated if both nodes are manually rebooted at the same time.
SNAP HA® tuning options are currently not available with the softnas-cmd cli. These settings can currently only be modified via the UI.
SNAP HA® failed node behavior UI options are visible for VMware deployments, but the settings will have no effect. In a VMware environment the failed node will always shut down.
Azure Email Notifications: If the SoftNAS email notification is not properly configured the Monit email queue can become full, which can prevent a ZFS timeout HA failover trigger from forcing a failover. It is recommended that the SoftNAS test email functionality is used to validate the notification email configuration to avoid this issue.
Fixed in 4.4.0
Fixed an issue where SNAP HA takeovers and givebacks were allowed during a delta-sync process. This could result in unexpected data loss issues.
SnapHA Share Name Fix - Resolved an issue where having a “$” in the share name (hidden share) would not allow SNAP HA to be configured.
Fixed an issue where upgrades were not cleaning up files. Over time this filled the root drive causing upgrades to fail.
Fixed an issue where Lift and Shift flows would fail with filenames containing white spaces.
Fixed an issue where Lift and Shift flows would fail when files are renamed or moved during the execution of a flow.
Fixed an issue that prevented the Driftbot from being disabled. Driftbot would continue to launch after a new login in when disabled in the UI, this fix prevents Driftbot from reappearing when a new session is started.
Fixed an issue where SNAP HA would cause files to be created and not cleaned up. This could result in exhausting the system inodes.
Fixed an issue with softnas-cmd. Pool imports were not working due to a missing required parameter.
Fixed an issue where PHP was excluded from yum updates. This was preventing security updates from being applied.
Corrected SmartTiers Dashboard Stats - Fixed an issue where the StorageCenter Dashboard was mistakenly showing incorrect consumption statistics for SmartTiers™ Pools.
Fixed an issue with SNAP HA when using Azure peered VNETs. Using a non CIDR VIP failed to successfully fail over. Note: in CIDR VIP will not function in this configuration.
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:
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 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® 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® 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® VMs on the Azure Classic Portal. The Azure Resource Manager (ARM) is the only supported platform on Azure.
Note: For version 4.4.0 our No Downtime Guarantee™ has the following minimum technical requirements:
- Software version must be 4.4.0 or above.
- Software updates must be applied within 30 days of availability.
For more details on our No Downtime Guarantee, click here.
SoftNAS® 4.3.2 Release - February 21st, 2020
Overview
SoftNAS® 4.3.2 is a maintenance release containing bug fixes and important security updates.
Fixed in 4.3.2
Fixed SmartTiers issue - Corrected a scenario where datasets larger than 10TB with I/O access patterns that cause a high amount of tier swapping could lead to potentially zeroed datablocks for individual files. This fix will apply only to newly created SmartTiers. If you have an existing SmartTiers deployment, please immediately contact support to resolve this issue on your existing SmartTier volumes.
Server Unresponsive under heavy I/O load - By updating ZFS, SoftNAS fixed an issue where a system became unresponsive due to heavy I/O load, resulting in client connections disconnecting and inability to SSH into the SoftNAS instance/VM. You can read more about this ZFS reported issue here.
Unresponsive Lift and Shift Flow - Fixed an issue where if files or directories were renamed after a delta file scan as part of Continuous Sync was completed, Lift and Shift would appear to stall indefinitely.
Lift and Shift "Functionality Expired" - A bug in the code was inappropriately reporting via a UI message "Functionality Expired" when attempting to use Lift and Shift, Flexfiles or UltraFast. This bug has been removed.
HA reboot issues - Fixed multiple issues related to rebooting a node or both nodes of an HA Pair which would inappropriately result in a full sync.
OpenSSH and OpenSSL yum update issue - SoftNAS now prevents OpenSSH and OpenSSL packages from being updated via yum, which can cause performance issues or SnapReplicate issues.
New in 4.3.2
ZFS update - ZFS version has been updated to 0.8.3 to include patches for the issue found by “Canonical” and other fixes to ZFS. SoftNAS highly recommends upgrading to 4.3.2 and the new ZFS.
New Region Support - SoftNAS has now added support for the AWS Hong Kong region.
Kernel Update - The linux kernel has been updated to version 4.14.158.
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:
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:
/wiki/spaces/SD/pages/92999399
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® 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® Instances
SoftNAS 4.3.1 Release - October 4th, 2019
Overview
SoftNAS 4.3.1 is a maintenance release containing bug fixes and important security updates.
Fixed in 4.3.1
Unexpected SNAP HA deactivation - SoftNAS no longer deactivates HA when the HA controller is not accessible. Steps have been taken to make the process of accessing the HA controller more resilient.
Very large etc/passwd and shadow files - An issue in which files in etc/passwd and etc/shadow were growing and potentially consuming excessive root drive capacity during replication has been resolved. (16613)
SNAP HA reactivation failure post-upgrade - An issue was resolved that prevented SNAP HA from being reactivated after an upgrade in some cases. This fix is only available for releases 4.3.0 and later.
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:
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 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 Instances
Upgrading from an AWS PV Instance to AWS HVM Instance
Running SoftNAS 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 Instances
SoftNAS® 4.3.0 Release - September 5th, 2019
Overview
SoftNAS 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.
You can verify the root volume disk usage by checking the SoftNAS Dashboard (select Dashboard under the Storage Administration pane).
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 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 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 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:
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 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 Instances
Upgrading from an AWS PV Instance to AWS HVM Instance
Running SoftNAS 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 Instances
SoftNAS 4.2.3 Release - March 29th, 2019
Overview
SoftNAS 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:
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 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 Instances
Upgrading from an AWS PV Instance to AWS HVM Instance
Running SoftNAS 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 Instances
SoftNAS 4.2.2 Release - March 12th, 2019
Overview
SoftNAS 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:
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 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 Instances
Upgrading from an AWS PV Instance to AWS HVM Instance
Running SoftNAS 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 Instances
SoftNAS 4.2.1 Release - Feb 14th, 2019
Overview
SoftNAS 4.2.1 is a maintenance release containing security updates and bug fixes.
New in 4.2.1
Kernel update and vulnerability fixes - SoftNAS 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:
/wiki/spaces/KBS/pages/92734037
Recommended minimum Instance/VM requirements - As of the SoftNAS 4.2.1 release, SoftNAS recommends that customers only deploy SoftNAS 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 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 4.2 Release - November 15th, 2018
Overview
SoftNAS 4.2 is a maintenance release containing security updates, performance improvements and bug fixes.
New in 4.2
Kernel update and vulnerability fixes - SoftNAS is now updated to kernel version 4.14.71, and patched to address relevant kernel vulnerabilities. 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 II
SKU Updates to VMware, and AWS and Azure Marketplace - SKU sizes, Consumption and BYOL licenses have been updated for AWS and Azure Marketplace. OVAs and software update packages have been provided for VMware.
PHP Update - As part of the security updates, PHP has been updated to 7.2 to address several security concerns with the previous version.
JRE Updates - JRE updates have been put under the control of YUM updates to allow customers to more easily update the JRE version.
Lift and Shift Updates - Enhancements have been added to allow Lift and Shift to be used after Azure Data Box or AWS Snowball have performed the initial bulk move of data to the cloud to handle delta changes after the bulk move is complete.
Samba Update - Samba has been updated to version 4.8 with this release to incorporate the latest bug fixes and security updates. The Samba release notes can be found here.
Azure Improvements - SoftNAS supports Azure Accelerated Networking, however it must be enabled manually. For information on how to enable Azure Accelerated Networking for existing SoftNAS virtual machines updated to 4.2 (from 4.0.1 and later), click here.
Root Disk Size increase - To take advantage of increased IOPS / throughput, the default root disk size for SoftNAS 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.
Azure SNAP HA Routing Table Conflict issue - An issue in which an HA Pair could be influenced by a routing table from outside the resource group, but on the same subnet, has been resolved.
Open File Capacity issue - Increased the number of max file descriptors allowed on the instance or Virtual Machine, and ensured that this value is persistent across upgrades.
Multiple Lift and Shift flow UI issue fixed - On high load Lift and Shift instances with multiple flows , when stopping and starting flows, the UI would not show that individual Lift and Shift flows had restarted and were in progress. This UI issue has now been resolved.
Lift and Shift™ Select Target Volume UI issue fixed - A minor UI issue when selecting 'I want to use an existing SoftNAS Target Volume', in which the Target Volume Name was visible when it should not have been, has been resolved.
Lift and Shift™ root folder display issue fixed- If creating folders within the Lift and Shift™ flow data store, and still on the root folder, the description in the browse tab would read 'undefined', rather than showing the path to the target volume. This has now been resolved.
Directory Lift and Shift™ source volume data calculation issue fixed - An issue in which the original data cost value calculation would display correctly, but would not reflect changes upon subsequent addition of data has been resolved.
'Lift and Shift "Maximum disk size" field value reset issue fixed - After changing disk type in advanced disk configuration of the Lift and Shift wizard, the 'Maximum Disk Size' value would reset. This has now been resolved.
Directory Lift and Shift™ button display issue fixed - An issue where upon adding additional mappings under step 6 of the directory level flow creation ('Configure (Map) Source to Target Volumes'), the 'Update' and 'Cancel' buttons were improperly aligned, has been resolved.
Volume Lift and Shift™ Verification issue fixed - When creating a Volume Lift and Shift and selecting target volumes, creating target storage via the automated process, the 'Verify' option was available prior to any created mappings. The verify button is now only available after the user has a volume mapping created to verify.
Lift and Shift™ flow removal display issue fixed- If a flow failed, presenting an error, the user could remove the flow. However, due to background operations to pause and delete the flow, the flow would not show as deleted for up to 20 minutes. This delay has now been fixed.
Disk Type Display Issue fixed - A UI display issue where the disk type would remain static after making a disk type change from outside the SoftNAS UI (ie, the AWS console) has been resolved.
Inaccurate Notification Panel message - When creating a Lift and Shift flow on an instance using NFS, the Notification panel erroneously stated that the user had configured his flow to use CIFS/SMB. This issue has now been resolved.
Errata 4.2
Unnecessary Email Alert - If deleting an S3 disk, an email alert may be generated stating that the S3 bucket does not exist, this can safely be ignored.
NVMe and EBS Backup and Restore known issue - Pools created with NVMe disks cannot be backed up using EBS Backup and Restore.
Downloading File from Webmin issue - In Webmin, under Others>Upload and Download, using the 'Download from Web' option fails with an error. This will be resolved by back-end changes in an upcoming release.
IE11 License Agreement Display issue - In Internet Explorer 11, SoftNAS' End User License Agreement displays upon every login/refresh.
Recommended Action: Agree to the terms and conditions and continue with the task at hand.
EBS disks added to NVMe instance 'failure' - If adding an EBS disk from the CLI (command line interface) to an NVMe instance (such as the newly available AWS m5 series instances) the command will complete successfully but not show the disk. Subsequent attempts to add the disk show a persistent error stating that "the attachment point is already in use".
Recommended Action: Added disks will appear after a reboot of the SoftNAS instance. Reboot your SoftNAS instance, and if the issue persists, contact SoftNAS Support.
Large Log Files on UltraFast™/Lift and Shift™ instances - Larger than expected log files have been reported on instances running Lift and Shift with UltraFast. While SoftNAS is continuing to monitor the situation, but have observed no ill effects.
Password Save unavailable on Chrome - If logging into your instance on the Chrome browser, the browser will not offer to save your password.
Azure Add Disk Limitation - If your user name belongs to multiple subscriptions, adding disk devices will not function.
Recommended Action: Create a service principal under the desired subscription, and use the service principal to add disk devices.
Password limitation - Passwords containing the '[' special character are not supported for logging into Storage Center.
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.
Upgrading from 3.4.9 or later
1-click upgrades are supported from versions 3.4.9 and later to version 4.2.
For information on updating your instance:
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 from versions before 3.4.9
For versions below 3.4.9, 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 Instances
Upgrading from an AWS PV Instance to AWS HVM Instance
Running SoftNAS 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 Instances
SoftNAS 4.1 Release - September 17th, 2018
Overview
SoftNAS 4.1 is a feature release containing new features, improvements and bug fixes.
New in 4.1
- SoftNAS® SmartTiers™
Introduced as Platinum Beta in 3.7, SoftNAS SmartTiers™ is now live and available for use in production environments. SmartTiers™ is a SoftNAS patent-pending automated storage tiering feature that moves aging data from more expensive, high-performance block storage to less expensive object storage according to your policies, reducing public cloud storage costs up to 67%. Directory Lift and Shift™
Directory Lift and Shift™ is an enhancement to Lift and Shift™ to allow customers to select a specific sub-directory as the starting Source point for a Lift and Shift™. Lift and Shift™ in 4.0 only allows the customer to select the root directory of an entire volume as the Source starting point.
Support for CIFs/SMB NTFS ACLs in Lift and Shift™
Lift and Shift™ now maintains NTFS ACLs with CIFs for a Lift and Shift™ flow from the Source to the Target (NTFS ACLs are not supported with NFS). POSIX ACLs continue to be maintained for CIFs and NFS as in 4.0.SNAP HA/SnapReplicate™ enhancement - Should an HA Controller become unavailable for a cloud (AWS or Azure) HA deployment of SoftNAS , high availability will auto-deactivate with an error message and an email alert to ensure customer can fix the issue and re-activate HA.
SNAP HA/SNAPReplicate™ enhancement - If a pair of instances are not the same version, configuring replication will fail, and will prompt the user to upgrade both instances to the same version, in order to prevent later potential replication issues.
SNAP HA/SnapReplicate™ enhancement - Remote destruction of target node data is now only triggered if a manual force-sync is applied. This means that if the data on node A is destroyed after a failover has been performed, the data will remain on the second node until force sync is applied. A warning makes it clear that the force-sync operation will result in destruction of data, preventing accidental loss.
Azure SNAP HA in multi-subnet environment - Users can now implement SNAP HA in a multi-subnet environment. By clicking a check box, SoftNAS updates all route tables associated to all subnets on the same VNet as the HA Pair.
- Disk Import Wizard enhancement - The Disk Import Wizard now supports and includes an option to select self-configured disks.
- Cross-Region Deltasync support - Deltasync can now be used across regions.
- Azure and softnas-cmd enhancement - Azure service principals can now be used in softnas-cmd to create new disks, and add SNAP HA.
Fixed in 4.1
Samba Upgrade - Upgraded SAMBA to version 4.8 to resolve some known memory replication issues in previous versions of Samba.
Java Upgrade - Java Runtime Environment (JRE) has been updated to version 1.8, update 151.
Apache NiFi update - Apache NiFi source files, used for our Lift and Shift, FlexFile Architect, and Data Flow Templates, have been updated to the latest version, 1.7.1.
SmartTiers™ RAM guidance update - Guidance on provisioning your SoftNAS instance for a SmartTiers™ use case can be found here: RAM Sizing Guidance for SmartTiers™
SmartTiers UI Storage Sizing Discrepancy - An issue in the Beta version where the UI reported inconsistency in the sizes of SmartTier and underlying storage (ie two pools configured to the same size showing different totals) has been resolved.
Add S3 Disk behind proxy issue - An issue when attempting to add an S3 disk from behind a proxy would result in an error message has been resolved.
S3 Self-Configured Disk Endpoint overwrite issue - An issue where the provided http:// endpoint information in the self-configured disk wizard was being overwritten by https:// (and breaking the link) has been resolved.
Disk encryption issue on NVME instances - An issue when adding encryption upon creating EBS disks on NVME instances would result in an error message has been resolved.
AD Join erroneous message issue - An issue in which when joining AD via the UI on your SoftNAS instance would show the "Resolving domain name, please wait..." message despite AD join success has been resolved.
Thick-provisioned Volume increase size issue - An issue in which increasing the size of a thick-provisioned volume would result in an error has been resolved.
Upgrade hanging issue - An issue in which NVME instances using L2-ARC read cache would hang and display the "Please wait while server is starting" message after upgrading to previous versions has been resolved.
CIFS/SMB Security and Access Control Unknown parameter 'user' issue - Removed the "Possible user" and "Possible Group" from Webmin to avoid conflicts, and prevent faulty setup configurations.
Faulty Azure HA.ini script values issue - Resolved an issue where non-numeric values in the 'HAMONITOR_SECS' and 'NO_OF_RETRY' fields were not handled, resulting in take-over failures.
Azure SNAP HA with VNet in separate Resource Group fix - An issue in which Azure SNapHA setup would fail if the VNet was in a different Resource Group than the SoftNAS instance has been resolved.
Snapvol files requiring manual deletion issue - A condition where deleted volumes in a SnapRep/HA left stale SnapReplicate™ snapshots that could result in a failed takeover has been resolved.
Errata for 4.1
Large Log Files on UltraFast™/Lift and Shift™ instances - Larger than expected log files have been reported on instances running Lift and Shift with UltraFast. While SoftNAS is continuing to monitor the situation, but have observed no ill effects.
Inaccurate Notification Panel message - When creating a Lift and Shift flow on an instance using NFS, the Notification panel states that the user has configured his flow to use CIFS/SMB. This erroneous message does not affect creation of the flow, and will be addressed in a future release.
Lift and Shift™ Select Target Volume UI issue - When selecting 'I want to use an existing SoftNAS Target Volume', the expected behavior is that the Target Volume Name field should be hidden. This issue is visual in nature, and does not impact functionality, and will be addressed in a future release.
Multiple Lift and Shift flow UI issue - On high load, multiple flow Lift and Shift instances, when stopping and starting flows, the UI may not show that individual Lift and Shift flows have restarted and are in progress.
Azure Add Disk Limitation - If your user name belongs to multiple subscriptions, adding disk devices will not function.
Recommended Action: Create a service principal under the desired subscription, and use the service principal to add disk devices.
Password Save unavailable on Chrome - If logging into your instance on the Chrome browser, the browser will not offer to save your password.
Directory Lift and Shift™ root folder display issue - If creating folders within the Directory Lift and Shift™ flow data store, and you are still on the root folder, the description in the browse tab will read 'undefined', rather than showing the path to the target volume. This will be resolved in an upcoming release.
Directory Lift and Shift™ source volume data calculation issue - When creating a Directory Lift and Shift™ flow, and data cost is first calculated based on existing data, the values will be correct. However, if you revisit the wizard after adding more data, the data cost calculation will not reflect the changes.
Directory Lift and Shift™ Advanced Disk Configuration UI issue - When the user creates a new Lift and Shift™ flow, and selects EBS disk and Maximum Disk Size within Advanced Disk Configuration, the Maximum Disk Size value resets upon selecting "Type".
Directory Lift and Shift™ button display issue - Upon adding additional mappings under step 6 of a directory level flow creation ('Configure (Map) Source to Target Volumes'), the 'Update' and 'Cancel' buttons are improperly aligned. This will be resolved in an upcoming release.
Volume Lift and Shift™ Verification issue - When creating a Volume Lift and Shift and selecting target volumes, creating target storage via the automated process, the 'Verify' option is available prior to any created mappings. The expected behavior is that this button should be disabled until the user has a volume mapping created to verify. This will be resolved in an upcoming release.
Lift and Shift™ flow removal display issue - If a flow fails, presenting an error, the user can remove the flow. However, due to background operations to pause and delete the flow, the flow may not show as deleted for up to 20 minutes.
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.
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.
Upgrading from 3.4.9 or later
1-click upgrades are supported from versions 3.4.9 and later to version 4.1.
For information on updating your instance:
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 from versions before 3.4.9
For versions below 3.4.9, 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 Instances
Upgrading from an AWS PV Instance to AWS HVM Instance
Running SoftNAS 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.
How To Migrate SoftNAS Instances
SoftNAS 4.0.3 Release - July 18th, 2018
Overview
SoftNAS 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.
Upgrading from 3.4.9 or later
1-click upgrades are supported from versions 3.4.9 and later to version 4.0.
For information on updating your instance:
For upgrading a SNAP HA™ pairing:
Upgrading from versions before 3.4.9
For versions below 3.4.9, 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 Instances
Upgrading from an AWS PV Instance to AWS HVM Instance
Running SoftNAS 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.
How To Migrate SoftNAS Instances
Fixed in 4.0.3
Security Fix - Closes a command injection vulnerability in StorageCenter. Please follow SoftNAS Security best practices and restrict your source IP as described in our documentation. See Planning your Instances - Security for more information.
Improved NVMe Disk Support - Improved support for instances on AWS leveraging NVMe disks, such as the i3 series, M3 series and C5 series.
Platinum License fix - An issue in which a platinum license could not register to an account containing a space within the account name has been resolved.
SmartTier Beta Improvements - A kernel issue seen during continuous heavy client load has been resolved.
Errata 4.0.3
NVMe and EBS Backup and Restore known issue - Pools created with NVMe disks cannot be backed up using EBS Backup and Restore.
RAID 5 Hot Spare Issue - If a drive fails on a heavily loaded system with a RAID 5 configuration, the hot spare feature may fail.
Recommended Action: If this occurs a restart of the instance will typically resolve the issue. If not resolved, contact SoftNAS Support.
SoftNAS 4.0.2 Release - June 15th, 2018
Overview
SoftNAS 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.
Upgrading from 3.4.9 or later
1-click upgrades are supported from versions 3.4.9 and later to version 4.0.
For information on updating your instance:
For upgrading a SNAP HA™ pairing:
Upgrading from versions before 3.4.9
For versions below 3.4.9, 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 Instances
Upgrading from an AWS PV Instance to AWS HVM Instance
Running SoftNAS 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.
How To Migrate SoftNAS Instances
Fixed in 4.0.2
Azure CLI routing table issue - An issue in which the Azure CLI errored out unexpectedly when updating the routing table during a SNAP HA failover event has been resolved.
Azcopy and php_error.log file issue - An issue in which while using Azcopy, the php_error.log file would grow faster than the log rotation would allow has been resolved.
Azure Resource Groups Mixed Case Names issue - An issue in which using names consisting of mixed upper and lower case letters for Azure Resource Groups would result in a SNAP HA setup failure has been resolved.
Unwarranted Email Alerts issue - An issue in which monit remains active on the secondary node of a SnapReplicate™ /SNAP HA™ pair, resulting in spurious email alerts for services that have been intentionally shut down, has been resolved.
Errata 4.0.2
Joining AD with multiple domain controllers known issue - When joining a SoftNAS instance to an Active Directory Domain the UI may seem to be stuck at “Resolving domain name, please wait..” for longer than 10 seconds.
Recommended Action: In this situation it is safe to proceed. Enter the remaining required fields and click next and complete the join operation as normal. If there is an actual issue resolving the domain name the UI will correctly error out. Joining using the CLI does not have this issue. This will be resolved in a future release.
SoftNAS 4.0.1 Release - June 1st, 2018
Overview
SoftNAS Enterprise 4.0.1 is a maintenance release containing bug fixes.
Fixed in 4.0.1
Legacy SKU change - Minor change made to fix legacy marketplace SKU upgrade issues.
SoftNAS 4.0 Release - May 28th, 2018
Overview
SoftNAS 4.0 is a feature release containing new features, improvements and bug fixes.
Upgrading
Upgrading from 3.4.9 or later
1-click upgrades are supported from versions 3.4.9 and later to version 4.0.
For information on updating your instance:
For upgrading a SNAP HA™ pairing:
Upgrading from versions before 3.4.9
For versions below 3.4.9, 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 Instances
Upgrading from an AWS PV Instance to AWS HVM Instance
Running SoftNAS 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.
How To Migrate SoftNAS Instances
New in 4.0
SoftNAS Platinum edition - Introduced as Beta in 3.6, SoftNAS Platinum offers the following new features and benefits to our customer's production environments:
- SoftNAS® UltraFast™
UltraFast™ is the SoftNAS patent-pending technology that accelerates global bulk data movement up to 20 times faster compared to standard TCP/IP protocols. Accelerate transfers of data into, out of, and across private, public, hybrid clouds, and multi-clouds, saving on time and costs. UltraFast™ is supported for use with Snap Replication and Lift and Shift™. - Lift and Shift™ Live Cloud Migration (powered by Apache NiFi)
Lift and Shift with continuous sync keeps data up-to-date and usable. Point SoftNAS Platinum edition to existing NAS shared storage volumes, select your public cloud storage destination, and immediately begin moving your data. Use SoftNAS web management console to manage and control data storage and the Lift and Shift step by step, "fill in the blank" wizard to move applications and data fast and efficiently. Continuous sync keeps content up-to-date when aggregating data to the cloud and/or distributing it to remote locations. Lift and Shift supports live production data migrations, automatic restart, suspend/resume, bandwidth scheduling and network acceleration via UltraFast™.
- FlexFiles™ and FlexFiles Architect (powered by Apache NiFi)
FlexFiles and FlexFiles Architect enables you to extend the power of the Apache NiFi User Interface via FlexFiles Architect to design and monitor new custom data flow via an easy to use drag and drop interface. FlexFiles Architect also provides access to provenance data (an audit trail for compliance), associated with each step of your custom data flows. SoftNAS FlexFiles adds custom SoftNAS processors to use in conjunction with Apache NiFi's extensive set of community-supported NiFi Processors to build powerful data flows. The type of data-flows you can create with FlexFiles Architect covers a wide spectrum through the use of SoftNAS and NiFi processors including data transformation and routing, database access, data ingestion and egress, data splitting and cloud connectors. To learn more and get started creating custom flows with FlexFiles Architect, see https://nifi.apache.org/docs/nifi-docs/html/getting-started.html.
- SoftNAS DataFlow Templates (powered by Apache NiFi)
SoftNAS Platinum includes two solution templates for you to use as a starting point to build custom data aggregation and data publishing flows. The Many-to-One template helps you create a data aggregation flow that will aggregate data from multiple remote locations to a single location. The One-To-Many template helps you create a data publishing flow to push data created at a single location to multiple remote locations. Each of these templates can be expanded to the number of locations you need.
Support for new instance types - SoftNAS now supports the C5 and M5 series of instances in AWS.
Note: For Customers using M5 and C5 Instances - These instances are based upon the new AWS Nitro Hyper-visor. There is a current limitation where EBS Disks will fail to attach via the Storage Center interface. A work-around has been tested and found to work. The work-around is to add the disks via the AWS Console or AWS CLI. Once attached they can be partitioned normally via the Disk Devices Applet, and pools can then be created with these disks.
Snap Replication Optimization - Added an enhancement to SNAPReplicate™ to increase the overall throughput and reduce the time needed to complete a Full Sync.
ObjectBacker™ Performance enhancements - Improvements made to ObjectBacker now provide up to a 200% performance increase on writes, and a 50% increase on Reads. Representative graphs have been added to illustrate the improvements.
Platinum Beta Features
- SoftNAS® SmartTiers™
SmartTiers is a SoftNAS patent-pending automated storage tiering feature that moves aging data from more expensive, high-performance block storage to less expensive object storage according to your policies, reducing public cloud storage costs by up to 67%.
Platinum Licensing
If using a BYOL (Bring Your Own License) SoftNAS image, both an Enterprise license and a Platinum add-on license will be required.
The Enterprise license must be installed first. For instructions on how to add your Enterprise license, see Activating SoftNAS License.
After the Enterprise License has been applied, simply click any of the Platinum Features. You will see the following prompt:
Provide the Platinum License Key received from SoftNAS Sales, as well as the name of the registered owner (or organization). Click Submit, if activating online.
If activating manually (offline), check the box, in which case a new prompt will appear, allowing you to enter the manual activation code, also obtained from SoftNAS Sales.
Fixed in SoftNAS 4.0
ObjectBacker™ Improvements - The following changes have been made to ObjectBacker in order to prevent potential data synchronization issues after a reboot:
- Shared Throttle- Multiple Bucket pools now have the ability to share back-end cloud platform throttle information between one another.
- Persistent Cache- Allows for Block Cache to be stored on Disk, rather than in Memory (RAM)
Note: In 4.0, SoftNAS ObjectBacker supports only Object with RAID-0, allowing for legacy configurations to run un-affected.
UI displays all snapshots - Due to pagination limit, snapshots listed in the UI were limited to 25. A scroll bar has been added, allowing all available snapshots to be displayed. (14490)
Resolved whitespace issue in DeltaSync - An issue in which whitespaces were mishandled by Deltasync resulting in SNAP HA failures has been resolved. (14599)
Erroneous SNAP HA™/SnapReplicate "No Replication is Defined" message - After a failover in which the primary node has become the secondary, the former primary node would display a "No Replication is Defined message" despite SNAP HA showing as activated in the logs. This issue has now been resolved. (6852)
Java security enhancement update- Java has been updated to version 1.8.0_151.
Default Settings Change - UseDNS setting in the /etc/ssh/sshd_config file has been set to 'No', ensuring that only addresses and not host names may be used.
Update UI 'read latest versions' failure error - An issue in which an error stating that "Recent versions list read failed (error 100.4)" when performing an update from the UI has been resolved. (14194)
Azure separate VNET Resource Group HA Failure issue - An issue in which SNAP HA™ pairings on Azure using a VNET in a separate resource group would not fail over has been resolved. (14591)
Self-Configured Disk S3 bucket mount failure - An issue in which a self-configured S3 disk could not be mounted has been resolved. (14353)
S3 auto-trim feature enabled - ZFS’s Trim and discard feature is now enabled by default. This improves performance by enabling more efficient garbage collection.
Errata for SoftNAS 4.0
Active Directory Join known issue - If there is a user whose UPN prefix matches the samaccountname of the user who is performing the active directory join, the AD join will not succeed. If the samaccountname user is deleted, AD join using the upn account will succeed.
Para-virtualized instances no longer supported - PV instances are no longer supported on the EC2 platform. Updating will cause boot failure.
Azure Active Directory Password Expiry issue - If integrating your SoftNAS virtual machine with Azure Active Directory, default password expiry settings can break the HA configuration.
Recommended Action: Azure AD passwords can be set to never expire by following the instructions found in Microsoft Azure Active Directory Password Policy Help Documentation.
UltraFast™ does not support multiple connections - At this time, only point to point UltraFast™ connections are supported. An attempt to create a second connection will result in an error stating that the "Item already exists".
Deleted SoftNAS SmartTiers Pools not recoverable - After successful deletion of SmartTier pool, SmartTier Container pools may be listed as available to import, however, these pools do not contain valid data and re-importing or recreating the SmartTiers pool from them is not possible.
VMware: Deleted VM disk still displays in SoftNAS UI - If a virtual disk is created via the VMware console and connected within SoftNAS , then removed by deleting it from within the VMware console, the SoftNAS UI will still show the disk as present, but state that it "Needs Partition".
Invalid NiFi Sync Settings allowed - It is currently possible to set invalid values (such as 0 for concurrent connection count or Wait Interval), resulting in a configuration error. A validation check will be implemented preventing this in a future release.
Lift and Shift Throughput Graph Display Issue - When running a lift and shift flow, the curve effect of the line graph can make the throughput appear negative when in fact it is not. (5663)
File Monitoring system additional disks - The dashboard file monitoring system on Azure virtual machines is showing several additional disks, and those disks appear as if they are filled to capacity (as non-existent disks have no capacity).
Recommended Action: Disregard these additional disks (as they simply reflect past mount points), and verify disk count from Disk Devices.
License Display Issue - Currently, after applying a SoftNAS Essentials Edition or Platinum license to a BYOL instance, the license applet's product type field does not reflect the current license, and instead shows the former "SoftNAS Enterprise edition BYOL" product type.
Azure storage account password containing @ symbol limitation- A password for an azure storage account containing the @ symbol will prevent the user from successfully logging in. This is due to an Azure CLI bug. For more information, see https://github.com/Azure/azure-cli/issues/5058
Ultrafast™ iPerf test and Connection issues - iPerf tests using low bandwidth settings such as a simulated T-1 line can cause timeouts to occur, resulting in loss of the Ultrafast™ connection.
RAID-Z space display issue - Pools created using RAID-Z may have volumes whose used space may appear to be greater than 100%, due to parity overhead when using narrow stripe widths in ZFS. Using larger block sizes (up to 1M) or a greater number of disks in each RAIDZ vdev can reduce overhead, but will not completely eliminate it. JBOD/RAID-0 and RAID-1 pools do not exhibit this behavior.
Inaccurate SNAPFAIL Status - If on an active SnapReplicate pairing with active volumes, and SnapReplicate is deactivated without changes to the data/volumes, the volumes will display with a status of SNAPFAIL in the Replication Control Panel, rather than a more accurate "Deactivated" status.
SoftNAS® SmartTiers™ ISCSI Limitation - ISCSI LUNs are NOT supported in a SmartTiers™ configuration.
Lift and Shift Target ACLs – Lift and Shift in SoftNAS 4.0 will only maintain POSIX ACLs on the files shifted to the target storage when using CIFs or NFS. If using CIFs, Lift and Shift does not maintain NTFS ACLs and you will need to manually reset any NTFS ACLs after the Lift and Shift flow completes for the 4.0 release. Maintaining NTFS ACLs with CIFs for a Lift and Shift flow is being addressed in a future release. NTFS ACLs are not supported with NFS.
For Customers Using i3 Instances and leveraging an NVMe Disk as a Read Cache - A tested work-around is available in order to resolve a known issue with pools not importing properly after a reboot or shutdown. If you encounter this issue your data is NOT lost or damaged. Please contact SoftNAS Support for assistance in importing your pool.