Nasuni Edge Appliance Configuration Recommendations for Resilio

Location and performance

Deploy the Resilio Primary Storage Agent (PSA) as close as possible to the Nasuni Edge Appliance (NEA). Target a round-trip latency below 5 ms, with as few network hops as possible.

Tip

Use the connectivity-check script provided on the download page to measure PSA-to-NEA latency.
For on-premises deployments, use the same data center and, where practical, the same rack or network segment. For cloud deployments, place the PSA and NEA in the same region.
For large jobs, assess whether a dedicated Nasuni volume is appropriate based on the active dataset, change rate, collaboration requirements and participating NEAs. A separate volume provides independent snapshot and synchronization policies, but does not provide separate appliance resources or cache capacity. Validate sizing with Nasuni’s sizing tools or Nasuni Support. For details, see Nasuni volume architecture guidance.

Quality of Service (QoS)

Review the NEA’s inbound and outbound QoS limits and any scheduled rules. Nasuni documents a default outbound limit of 10 Mbps which may be insufficient for the workload.
Do not disable QoS as a general performance recommendation. Nasuni’s current guidance recommends setting an explicit limit at, or slightly above, the available bandwidth to retain traffic prioritization. Low inbound limits can slow retrieval of uncached data; low outbound limits can delay snapshots, data propagation and the release of cache space. Locally cached SMB operations are not directly throttled by these cloud-transfer limits.
Confirm appropriate values with Nasuni for the deployment. For details, see Nasuni QoS settings.

User impersonation

Configure Kerberos delegation in Active Directory. This configuration allows the PSA to access SMB shares using each end user’s identity, with the NEA enforcing that user’s existing permissions.
Configure the required service principal names (SPNs) and delegation permissions for every NEA that may serve the job. See Resilio authentication and impersonation and deployment prerequisites.

Cache capacity and reserved space

Size the NEA cache for the working set – the files and metadata actively used by users and applications – and allow sufficient space for incoming writes. Insufficient cache capacity increases cloud retrievals and can reduce performance.
Leave reserved-space management on Automatic unless workload measurements or Nasuni Support justify an override. Review cache misses, eviction activity and unprotected data when investigating performance. For details, see Nasuni cache configuration.

Use an SMB configuration compatible with the PSA’s Windows SMB client, normally negotiating SMB 3.x. Retain the supported defaults for SMB signing, encryption and opportunistic locks unless troubleshooting identifies a specific reason to change them.

Case sensitivity

Nasuni provides two related settings:

Volume > Case Sensitive – Determines how the file system treats uppercase and lowercase names. This is selected when creating the volume and cannot be changed later.
SMB share > Case-Sensitive Paths – Controls case-sensitive name matching through an SMB share on a case-sensitive volume. Configure it under NMC > Volumes > Shares > Edit > Advanced settings.

Example

An application requesting financial\reports\budget.xlsx may fail to access Financial\Reports\Budget.xlsx when exact case matching applies.

Important

Effective behavior depends on the client operating system and the application. Do not change case sensitivity solely because Resilio is being deployed; verify consistent behavior across the supported clients. See Nasuni case-sensitivity guidance.

Snapshots and previous versions

Keep Nasuni data protection enabled and configure snapshot retention according to recovery requirements. Snapshot and synchronization schedules affect recovery points and the propagation of changes between NEAs; they are separate from Resilio’s own file transfer process.

For more information, see Nasuni snapshot and synchronization guidance.

Allowed Hosts

If an SMB share uses an Allowed Hosts restriction, ensure that the PSA’s source IP address as seen by the NEA is not restricted.
Apply the appropriate rule to every NEA that may serve the job. End users’ external IP addresses generally do not belong in this list because the PSA establishes the SMB connections. For more information, see Nasuni share security settings.

Verify both share-level restrictions and file/folder access control lists (ACLs) using representative end-user accounts. With impersonation enabled, these controls determine what each user can list, read, create, modify or delete.
Confirm that the share is writable where required and that ordinary users have not been assigned an SMB administrative role that bypasses normal ACL restrictions. For more information, see Nasuni permissions guidance.

Volume and folder quotas

Review volume and folder quotas to ensure sufficient capacity for expected growth. Reaching a quota can prevent writes even when the user has the necessary permissions. For more information, see Nasuni quota configuration.

Asynchronous I/O

Nasuni enables Asynchronous I/O by default for authenticated SMB shares to support concurrent reads and writes. Retain the Nasuni default unless testing demonstrates a workload-specific benefit from changing it. The presence of synchronous operations, such as opening files, does not establish that this setting has no effect. For more information, see Nasuni SMB share settings.

CNAME aliases and DFS Namespaces

Resilio accepts an SMB share path or a Nasuni DFS namespace path. A DNS CNAME can provide a stable alias, but it does not independently provide DFS Namespace target selection or automatic failover.
When using a Nasuni DFS namespace, enable Follow symlinks and set preserve_logical_path=true in the PSA’s job profile. For more information, see Resilio Enterprise Hybrid Work configuration.

For alias-based access, configure the alias on the NEA using a Nasuni-supported procedure and ensure that Kerberos resolves the SMB service to the correct AD computer account. Microsoft documents SPNs in the form serviceclass/hostname. For an explicit SMB service identity, that is, for example, cifs/alias.example.com, rather than the bare hostname alias.example.com. For more information, see Microsoft’s SPN format and command syntax.

Do not register the same alias SPN on multiple NEA computer accounts in the same forest. Configure delegation for each potential target and validate how the service identity is handled during a switch. For more information, see Nasuni naming guidance and Microsoft SPN documentation.

Multiple Active Directory forests

If the PSA and NEA are in one forest and users are in another, configure the required domain or forest trusts and enable the users’ trusted domain on the NEA.

In NEA > Configuration > Directory Services, select Update Domains, edit the relevant trusted domain and select Enable Source. This setting enables the trusted domain as an authentication source; it does not replace delegation configuration or file permissions. For more information, see Nasuni Directory Services configuration.

Also validate Resilio user and group assignment across forests. Users and groups from trusted domains may need to be assigned separately. For more information, see Resilio domain prerequisites.