Compatibility and Support

Introduction

This document explains how Nasuni components integrate with one another and with third-party infrastructure. Use the sections below, based on what you need:

• Planning an update? See Updating Nasuni software.

• Checking if Nasuni components are compatible with each other? → Edge Appliance and NMC Compatibility

• Verifying third-party support? → Third-Party Compatibility

Current supported versions

Update chokepoints

Before updating, you might need to install these mandatory intermediate versions:

For detailed instructions, see Updating Nasuni software.

Updating Nasuni software

Introduction

Updating Nasuni components from your current software version to a target software version might require installing certain intermediate versions first. This is because certain versions have introduced new features that make them incompatible with earlier versions. We call these special intermediate versions “chokepoints“. Therefore, it is important for you to find and follow the appropriate update path for your current version.

Key Principle: Always update the NMC first, then update any Edge Appliances. The NMC must be able to manage all Edge Appliance versions in your environment.

Edge Appliance update paths

Mandatory Chokepoints

The following versions are required chokepoints. You must update to these versions before proceeding to later versions.

Specific update paths

Determine the software version your Edge Appliance is running.

9.15.x or later

You are on the current update path. Update directly to the next version:

9.12.x or 9.14.x

You must reach version 9.15.4 before updating to 10.0.x+:

9.7.x through 9.10.x

You must pass through two chokepoints. First, version 9.9.5 or 9.10.2. Then version 9.12.x:

9.0.x through 9.5.x

You must pass through three chokepoints. First, version 9.5.x. Then version 9.9.5 or 9.10.2. Then version 9.12.x:

8.x or earlier

You have a longer update path. Contact Nasuni Support for guidance on your specific situation.

• Version 7.10.9+ is required before updating to 8.0.x
  Therefore, if your version is before 7.10.9, update to 7.10.9 first.

• Version 8.8.3+ is required before updating to 9.0.x
  Therefore, if your version is after 7.10.9 but before 8.8.3, update to 8.8.3 first.

• After updating to 9.0.x, continue with the 9.0.x update path as described above.

NMC Update Paths

Mandatory Chokepoints

The following versions are required chokepoints. You must update to these versions before proceeding to later versions.

Specific NMC update paths

Determine the software version your NMC is running.

25.1.x or later

You are on the current update path. Update directly to the next version:

23.2.x through 24.1.x

You must reach version 24.1.6 before updating to 25.1.x:

22.x through 23.1.x

You must reach version 22.3.5 or 23.1.2, then version 24.1.6, then version 25.1.x:

21.2.x or earlier

You must reach version 22.3.5, then version 24.1.6, then version 25.1.x:

Edge Appliance and NMC Compatibility

The NMC must be compatible with all Edge Appliances it manages. Use this information to verify compatibility.

Compatibility rules

1. The NMC version should be equal to or newer than the Edge Appliance version it manages.

2. There is a maximum version gap. Very old Edge Appliances might not work with the newest NMC.

3. Update the NMC first, then update Edge Appliances (NEAs).

Current compatibility of NEA with NMC (NMC 23.1+)

Note: Edge Appliance versions 9.5.x and earlier are only compatible with NMC versions 22.2.x and earlier. See legacy compatibility below.

Legacy Compatibility (NMC 22.3 and earlier)

For detailed legacy compatibility, contact Nasuni Support.

Current compatibility of NMC with NEA (9.7+)

Shared Volume Release Compatibility

As Edge Appliances sharing a volume are upgraded, new capabilities on that volume activate automatically — but only once every connected appliance, including the owner, has reached the required version. Once a capability is active, any new appliance joining the volume must also meet the minimum version for that capability. This applies only in the rare cases listed below; most major and patch releases do not introduce these requirements.

How to check shared volume compatibility

1. Find the lowest version of the appliances sharing the volume (owner and connected).

2. Identify the row in the table below that contains that version.

3. Find the column that lists the appliance version you want to join to the shared volume. The cell where the row and column intersect indicates whether the appliance is compatible or requires an update before it can join the volume.

Version Notes

1. Mergelist v2 was introduced in 9.5 — volumes on this format require all connected appliances to be ≥ 9.5.

2. First handle sync conflict resolution introduced in 9.15.3 — minimum build raised to 9.15.3.

3. Write Oplocks introduced in 10.0.2 — minimum build raised to 10.0.2.

4. Change Log introduced in 10.2.3 — minimum build raised to 10.2.3. Change Logging activates automatically once all connected appliances reach 10.2.3.

Third-Party Compatibility

This section details Nasuni's compatibility with third-party infrastructure, including hypervisors, cloud storage, applications, and protocols.

Support Designations

Throughout this document, third-party products are classified into separate support levels:

Hypervisors

Nasuni Edge Appliances (NEAs), the Nasuni Management Console (NMC), and File IQ appliances deploy as virtual machines on your existing infrastructure.

Note: This table shows specifically tested configurations. Nasuni customers receive full contractual support for Nasuni software regardless of hypervisor. Any KVM-derived or Xen-derived hypervisor not listed is considered Compatible.

Cloud Platforms

Legacy Active Directory (End of Support)

Client Operating Systems

Currently Supported

End-of-Life Operating Systems

Windows DFS Support

Windows DFS Namespaces can organize SMB shares from multiple Edge Appliances under a single logical path.

NTFS Permissions

Traverse Permissions:

• NTFS Exclusive & Multiprotocol: Traverse not required from volume root; required from share root for browsing; direct subfolder access doesn't require traverse.

• NTFS Compatible: Traverse required at volume root and all intermediate levels; direct subfolder access requires traverse.

Note: You cannot switch from NTFS Exclusive mode to NTFS Compatible mode.

Web Browsers

Nasuni Edge Appliances, the Nasuni Management Console (NMC), the Nasuni Orchestration Center (NOC), and the Web Access file explorer all provide Web browser interfaces for end-user and administrative access. The following Web browsers are qualified:

APIs

Nasuni Hardware Appliances

Currently Supported Hardware

End-of-Life Hardware

Technical Specifications

Cache Sizing

Note:

For new deployments running version 10.2 or later, the maximum tested cache size is 400 TiB (439 TB). For a larger cache size, consult Nasuni Product Management. For all other deployments, the maximum tested cache size is 36 TiB (39 TB). Although resizing the cache is allowed and fully supported, Nasuni recommends deploying with as large of a cache as intended instead of deploying with a smaller cache and then resizing to larger cache later.

Note: Multiple cache disks can be combined.
Physical pass-through disks are supported.

RAM

Maximum configurable RAM: 128 GB (additional RAM is ignored)

Encryption

• Default: AES-256 (256-bit Advanced Encryption Standard)

• Protocol: OpenPGP

• Key compatibility: OpenPGP-compatible key files; IDEA cipher supported

• Hardware appliances: FIPS 140-2 compliant libraries for disk encryption

Network

Nasuni Add-Ons

Ransomware Protection

Nasuni File IQ (NFIQ)

Requirements: Azure Blob Storage only

Global File Acceleration (GFA)

Nasuni Web Access

Support Levels

• Certified - Supported. Fully tested and validated by Nasuni.

Microsoft 365

The Microsoft 365 integration supports the following document formats.

Local Edit - Supported Extensions

Local Edit Clients

Load Balancers

Nasuni Access Anywhere

Extends high-performance file access to remote workers with Microsoft 365, Teams, and Slack integration.

Note: Applications requiring Advanced GFL are not compatible with Nasuni Access Anywhere.

Application Support

Deployment Options

Authentication

Supports internal user database, Active Directory, and SAML 2.0 providers (including Google Workspace, Okta, Duo).

Protocols

Client Platforms