How the Azure Native Qumulo Scalable File Service Works

This section gives an overview of deploying the Azure Native Qumulo Scalable File Service; lists the Azure regions and compliance postures that the service supports; and explains the differences between this service, Qumulo on AWS as an AMI, and Qumulo on premises.

This fully managed service deploys and manages resources on your behalf, runs Qumulo Core, and provides the same interfaces and functionality as Qumulo on premises.

Tip
In this guide, we refer to the collective features and functionality of Qumulo Core as Azure Native Qumulo Scalable File Service or the service.

The Azure Native Qumulo Scalable File Service lets you configure file protocols, quotas, replication, and other features regardless of underlying infrastructure or storage and without requiring the tracking of resource quotas and costs. It receives the latest updates and features continuously and, when issues occur, replaces compute and storage resources automatically.

For instructions on deploying the service in Azure, see Getting Started with Azure Native Qumulo Scalable File Service.

Note
For help with expanding the capacity of your Azure Native Qumulo Scalable File Service, email azure@qumulo.com.

Deploying the Azure Native Qumulo Scalable File Service

This section outlines the process of configuring and deploying the service.

You specify the following configuration.
- Regional Settings: The availability zone and region; for more information, see Supported Azure Regions
- Networking Settings: A virtual network in the same region; for more information, see Configuring Virtual Networking
- Usable Capacity: Actual required capacity; on this platform, this value isn’t restricted by architecture
Qumulo deploys and configures the following resources in an environment that it manages.
- Managed Resource Group: This group contains the networking resources that the service deploys.
- Delegated Subnet: The delegated subnet that the service uses to provision endpoints for your virtual network.
- Qumulo Service Resource: The Azure resource that represents one instance of the service. You can use this resource to manage the service and view configuration details.
- Marketplace SaaS Resource: The SaaS resource from the Qumulo Marketplace offer that you choose. Azure uses this resource for billing purposes.
Tip
Automated deployments let you create Azure Native Qumulo Scalable File Service instances for long-term use cases and for short-term components of automated storage workflows.

Known Limitations

IPv6 Addresses: Currently, Azure Networking features don’t support IPv6 addresses.
Initial Authentication over SMB: When you deploy the service initially, all users can use the SMB protocol. However, the admin user can authenticate over all protocols except for SMB. To allow the admin user to authenticate over the SMB protocol, change the admin user’s password. When the password change is complete, the admin user can authenticate over the SMB protocol.

Note
An incompatibility in data formats between the SMB protocol and Qumulo’s integration with Azure causes this limitation.
Namespaces Larger than 1 PB: To deploy namespaces larger than 1 PB through the Azure Portal, email azure@qumulo.com.

Supported Azure Regions

Azure Native Qumulo Scalable File Service supports all public U.S. regions. For more information, see Azure Geographies.

Feature Comparison with Qumulo on Other Platforms

The following table compares Azure Native Qumulo Scalable File Service features with those of Qumulo on other platforms.

Note
Although Qumulo manages the service fully, direct access to hosts with SSH is unavailable. You can configure the service by using the qq CLI from a remote machine or by using any of the IP addresses of the service to log in to the Web UI.

Feature	Azure Native Qumulo Scalable File Service	Qumulo on AWS as an AMI	Qumulo on Premises
Automatic Deployment	✓
Automatic Updates	✓
Available in Cloud Marketplace	✓	✓
Customer Support	✓	✓	✓
Automatic Infrastructure Replacement	✓	✓
Incremental Sizing	✓
Pay as You Go	✓	✓
Portal Integration	✓
Qumulo Core Features	✓	✓	✓
Simple, Fast Deployment Under 15 Minutes	✓

Qumulo Compliance Posture

For more information about third-party attestations that Qumulo has achieved, including SOC 2 Type II and FIPS 140-2 Level 1, see Qumulo Compliance Posture in the Qumulo Core Administrator Guide.