Overview

Nasuni Filer is a hybrid cloud file services platform that replaces traditional file servers and NAS appliances with a cloud-backed global file system. :contentReference[oaicite:0]{index=0}

Instead of storing data directly on local storage hardware, Nasuni stores file data in cloud object storage platforms such as:

• AWS S3
• Azure Blob Storage
• Google Cloud Storage

Users and applications continue accessing files using standard SMB and NFS shares, while Nasuni provides scalability, synchronization, versioning, and cloud-based protection behind the scenes. :contentReference[oaicite:1]{index=1}

In Softdrive environments, users access Nasuni shares from their virtual desktops just like a traditional Windows file server. Nasuni appliances provide local caching, synchronization, and continuous snapshot protection to optimize performance and resiliency. :contentReference[oaicite:2]{index=2}

Applies To

• Nasuni Filer
• Softdrive Virtual Machines
• SMB File Shares
• Cloud-backed File Storage
• Hybrid Cloud Storage Environments
• QCOW2 Nasuni Appliance Templates

Prerequisites

• Basic understanding of SMB file sharing and mapped network drives
• Active Directory authentication knowledge
• Understanding of Softdrive VM networking
• Understanding of object storage concepts
• QCOW2 Nasuni image available for deployment

Index

1. Architecture Overview
2. Global File System (UniFS)
3. Edge Appliance & Caching
4. Snapshot & Versioning Model
5. Integration with Softdrive
6. Technical Considerations
7. Creating a Nasuni Filer Template in Softdrive

1) Architecture Overview

Nasuni operates using a hybrid architecture. A local or virtual Nasuni edge appliance provides SMB and NFS file access while the authoritative copy of the data resides in cloud object storage. :contentReference[oaicite:3]{index=3}

The appliance functions as:

• An intelligent local cache
• A synchronization engine
• A cloud replication layer

This architecture allows users to experience local file server performance while benefiting from cloud scalability and resilience.

2) Global File System (UniFS)

Nasuni uses a proprietary global file system called UniFS. :contentReference[oaicite:4]{index=4}

UniFS maintains a single versioned namespace across all connected locations and appliances.

Every file modification is committed as an immutable snapshot in cloud storage, enabling:

• Multi-site collaboration
• File locking support
• Point-in-time recovery
• Ransomware resilience
• Continuous protection without traditional backups

3) Edge Appliance & Caching

The Nasuni edge appliance caches frequently accessed (“hot”) data locally to reduce latency and improve performance. :contentReference[oaicite:5]{index=5}

When files are modified:

• Changes are uploaded to cloud storage
• Snapshots are created automatically
• Other Nasuni appliances receive synchronized updates

This allows distributed offices and Softdrive environments to maintain synchronized access to shared data.

4) Snapshot & Versioning Model

Nasuni continuously versions file data by storing immutable snapshots in object storage. :contentReference[oaicite:6]{index=6}

Compared to traditional file servers, this provides:

• Continuous file protection
• Rapid recovery from accidental deletion
• Granular restore points
• Reduced Recovery Point Objective (RPO)
• Reduced Recovery Time Objective (RTO)

5) Integration with Softdrive

Within Softdrive environments, user virtual machines connect to Nasuni shares over SMB using domain credentials. :contentReference[oaicite:7]{index=7}

From the user perspective, the experience is similar to using a traditional Windows file server.

Administrators should understand that performance and synchronization depend on:

• Connectivity between Softdrive and the Nasuni appliance
• Cache sizing and appliance health
• Cloud storage provider connectivity
• Active Directory integration

6) Technical Considerations

• High latency networks may slow synchronization
• Firewall rules must allow SMB and outbound HTTPS traffic
• Distributed file locking behavior may vary in multi-site edits
• Cloud outages may delay snapshot commits
• Proper cache sizing is critical for CAD/BIM workloads

7) Creating a Nasuni Filer Template in Softdrive

To deploy a Nasuni Filer appliance within Softdrive, a QCOW2 image must first be uploaded and activated as a Softdrive template. :contentReference[oaicite:8]{index=8}

Templates cannot be deployed until validated and activated by Softdrive Engineering.

Step 1: Upload the QCOW2 Image

Begin by uploading the Nasuni QCOW2 image to the Softnet dashboard.

• Log in to:
  https://softnet.softdrive.co
• Navigate to:

  Advanced → Templates

• Click:

  Create

• Upload the QCOW2 image file
• Provide a template name such as:

  Nasuni-Filer-1

• Complete the upload process

Once uploaded, the template will appear in your account but will not yet be active for deployment. :contentReference[oaicite:9]{index=9}

Step 2: Gather Required Configuration Details

Softdrive Engineering requires infrastructure specifications before activating the Nasuni template. :contentReference[oaicite:10]{index=10}

Compute Requirements

• Number of vCPUs
• Total RAM required

Example:

8 vCPU
32 GB RAM

Storage Configuration

• Number of disks required
• Disk sizes

Example:

OS Disk: 50 GB
Cache Disk: 250 GB
Copy-on-Write Disk: 60 GB

Networking Requirements

• VLAN requirements
• Static IP requirements
• Internet egress requirements

Step 3: Submit a Support Ticket

After uploading the QCOW2 image, submit a support request to Softdrive Support. :contentReference[oaicite:11]{index=11}

Include:

• Template name
• QCOW2 upload confirmation
• vCPU requirement
• RAM requirement
• Disk configuration
• Networking requirements
• Target deployment region

Contact:
support@softdrive.co

Or open a ticket at:
https://support.softdrive.co/support/tickets/new

Step 4: Template Activation

Once the QCOW2 image and configuration details are received, Softdrive Engineering will:

• Convert the image into an active template
• Apply compute and storage configuration
• Validate deployment readiness
• Notify you when deployment is available

After deployment, administrators can connect to the Nasuni appliance by opening:

https://<IP address>:8443

Replace:

<IP address>

with the assigned Nasuni appliance IP address.

Expected Result

Administrators successfully deploy and configure a Nasuni Filer appliance within Softdrive, enabling cloud-backed SMB storage access for virtual desktops and workloads.

Troubleshooting

• Verify SMB connectivity over TCP 445
• Ensure outbound HTTPS access is available
• Validate Active Directory integration
• Confirm QCOW2 upload completed successfully
• Review cache sizing for performance-sensitive workloads
• Verify cloud provider connectivity
• If deployment issues persist, contact support@softdrive.co