This page outlines the key parameters and operational limits of Nasuni Data Service (NDS) for Azure. These values reflect current product behavior and are intended to help customers plan and optimize their use of NDS.
Operational Boundaries
Read-only access - data cannot be added, modified, or deleted via NDS.
Volume-level authentication - access is granted at the container/volume scope.
ACLs as metadata only - file permissions/ACLs are presented in metadata but not enforced by NDS.
Large File Downloads
Condition | Limit / Guidance |
|---|---|
Single Get Blob request | ≤ 1.1 GB / 1,181,116,007 bytes |
Files > 1.1 GB | Download in parts with HTTP Range headers |
Example (2 GB file):
First request:
Range: bytes=0-1073741823(first 1 GB chunk)Second request:
Range: bytes=1073741824-2147483647(remaining)
Connectivity Requirements
Traffic over SSL/443 must be allowed between the UaaS/NDS deployment, the Nasuni Management Console (NMC), and the volume owner Edge Appliances for the target volume(s).
Traffic over SSL/443 must also be allowed between the UaaS/NDS deployment and the Azure Storage Account(s) backing the target Nasuni volume(s). Public Network Access on the storage accounts must be unrestricted.