Web Access Architecture and Sizing

Audience

This guide is intended for the IT architect or person planning the deployment of Web Access to provide remote access and file sharing.

This guide applies to Nasuni Edge Appliance 10.1 and higher.

Introduction

Web Access provides remote file access and secure file sharing for the Nasuni Edge Appliance.

Deployment

The Web Access application runs within a Nasuni Edge Appliance (NEA).

Considerations include the following:

• The Web Access application is designed to be accessed by remote and distributed users over the Internet, without the need for a VPN.

• Web Access requires port 443 to be open from the internet (inbound access). For more information, see Firewall and Port Requirements.

• Additionally, an Application Proxy can be used. For more information, see Azure Entra ID Application Proxy.

• Nasuni recommends enabling Web Access on a dedicated Nasuni Edge Appliance (NEA) and managing it through a Nasuni Management Console (NMC). A dedicated NEA provides easier workload management and allows for deployment outside the office, such as in a data center.

Sizing

*Max Users – This is the estimated maximum number of active users the system can handle. The calculation assumes that each active user sends one request every 5 seconds. Since roughly 7% of these users would have a request pending at any point in time, we can estimate the maximum number of “concurrent users” as 7% of the maximum number of “active users”.

NFS Exports

To access data in an NFS export, you must enable the SMB (CIFS) protocol for the NFS volume in order to create a share. For more information, see Using Multiple Protocols.