Overview - Panzura CloudFS

This guide describes Panzura CloudFS and how to deploy and manage it.

* Only pertains to Panzura CloudFS 7

** Only pertains to Panzura CloudFS 8

The Panzura Freedom Family enables organizations to solve growing unstructured data challenges by combining data center performance with the economics, scalability, and durability of cloud storage.

Powered by the Panzura Freedom Operating System (PFOS), the Freedom Family delivers unprecedented performance and scale, expanded data center workloads, deployment on any platform and any cloud, automated, centralized management, and unmatched cloud data protection.

  • Panzura Freedom Archive: Replaces expensive single site NAS systems with a hybrid cloud storage platform that combines data center performance with the economics, scalability, and durability of the cloud. Freedom Archive can replace your entire backup and archive infrastructure with a more resilient, automated solution. It provides business continuity because it appears to users like a local network drive while storing all unstructured data in the cloud. Local performance is provided by high-performance flash and advanced caching algorithms that ensure that every application has the data it needs when it is needed.
  • Panzura Freedom NAS: Empowers organizations to break free from the storage status quo and eliminate islands of storage by consolidating their unstructured data to the cloud. Expensive, traditional NAS storage can be eliminated by centralizing unstructured data in the cloud, while keeping active data cached close to users. This modern cloud plus cache model is simpler, faster, and less expensive than deploying traditional primary, backup, and archive storage at each site.
  • Freedom Collaboration: Enables real-time collaboration across the enterprise by consolidating unstructured data to the cloud. Freedom Collaboration looks and behaves just like a local, locking NAS or Windows filer to users, but is backed by a central cloud data repository and can span hundreds of sites. Byte‐range locking, combined with the immediate consistency of the PFOS, enables globally distributed users to work together as if they are in the same room. It's simpler, faster, and less expensive than deploying primary, backup, and archive storage at each site, and running WAN optimization over private networks.

Filer Platform Options

The following platform options are available for the Panzura Freedom Filers. See the installation guide for your model for additional information and installation instructions.

Cloud Storage Tier Options

The following object storage services and products have been validated to work as object storage for Panzura Freedom Filers.

*Data download (per GB) cost may be more than Tiered Cost Savings. Please check with your Account Manager for more details.

Object Storage Cloud Storage Tier Panzura Support Availability Description
Amazon S3 S3 Standard YES S3 Standard offers high durability, availability, and performance object storage for frequently accessed data. Because it delivers low latency and high throughput, S3 Standard is appropriate for a wide variety of use cases, including cloud applications, dynamic websites, content distribution, mobile and gaming applications, and big data analytics.
S3 Standard-Infrequent Access YES* S3 Standard-IA is for data that is accessed less frequently but requires rapid access when needed. S3 Standard-IA offers the high durability, high throughput, and low latency of S3 Standard with a low per GB storage price and per GB retrieval fee. This combination of low cost and high performance make S3 Standard-IA ideal for long-term storage, backups, and as a data store for disaster recovery files.
S3 Intelligent Tiering YES S3 Intelligent-Tiering is a new Amazon S3 storage class designed for customers who want to optimize storage costs automatically when data access patterns change, without performance impact or operational overhead
S3 One Zone-Infrequent Access YES*

S3 One Zone-Infrequent Access (S3 One Zone-IA; Z-IA) is a storage class designed for customers who want a lower-cost option for infrequently accessed data, but do not require the multiple Availability Zone data resilience model of the S3 Standard and S3 Standard-Infrequent Access (S3 Standard-IA; S-IA) storage classes. S3 One Zone-IA is intended for use cases with infrequently accessed data that is re-creatable, such as storing secondary backup copies of on-premises data or for storage that is already replicated in another AWS Region for compliance or disaster recovery purposes.

Glacier NO S3 Glacier Storage Class is intended for long-term storage Archive that is not meant to be accessed quickly
Google Cloud Storage Multi-Region YES Google Cloud Storage Multi-Regional stores data in data centers across the globe and has 99.95% availability. It is suitable for companies that need to access data frequently, such as for website content and mobile application data. Multi-Regional class data is stored in at least two separate locations, which improves availability.
Regional Storage YES Google Cloud Storage Regional stores data in one geographic location, rather than spreading it out. It offers 99.9% availability and is best for compute, analytics, and machine learning workloads. When storage and compute resources are in the same region, Google Cloud Storage Regional provides high performance and availability.
Nearline Storage YES* Google Cloud Storage Nearline is for customers who need long-term storage for data that users access less than once a month. It's best used for archiving data, backup, and disaster recovery (DR). Ideal for back-up and serving long-tail multimedia content.
Coldline Storage YES* Google Cloud Storage Coldline is for customers who need to store data they access less than once a year. It is mainly for archiving and DR. It requires a 90-day minimum storage duration and is the least expensive of the three storage tiers. Typically, this is for disaster recovery or data that is archived and might or might not be needed in the future
Azure Storage Hot YES Optimized for storing data that is accessed frequently. Hot Blob Storage tier offers 99.9% availability with latency in milliseconds with general purpose version 1 and 2 account type.
Cool YES* Optimized for storing data that is infrequently accessed and stored for at least 30 days. Cool Blob Storage tier offers 99.9% availability with latency in milliseconds with general purpose version 2 account type only
Archive NO Optimized for storing data that is rarely accessed and stored for at least 180 days with flexible latency requirements (on the order of hours).
IBM Public Cloud Standard YES The Standard storage tier is used for active workloads that require high performance and low latency, and data needs to be frequently accessed (multiple times a month). There is no charge for data retrieval besides the cost of the operational request and public outbound bandwidth. Common use cases include streaming mobile and web content, DevOps, analytics, collaboration, and active content repositories.
Vault YES* The Vault storage tier is used for less active workloads that require infrequent data access (accessed once a month or less), but require immediate, real-time access when needed. A low retrieval charge applies when reading data. Vault offers the same high durability, high throughput, and low latency of the Standard class tier. Vault includes a threshold for object size and storage period that’s consistent with the intended use of this service for cooler, less active data. Common use cases include backup and digital asset retention.
Cold Vault. YES* The Cold Vault storage class tier is used for cold workloads where data is primarily archived (accessed a few times a year) but requires immediate, real-time access when needed. A larger retrieval charge applies for reading data. Cold Vault includes a threshold for object size and storage period that’s consistent with the intended use of this service to store cold, inactive data. Common use cases include long-term backup, large data set preservation such as scientific data, or older media content that needs to be stored cost effectively but required access when needed.
Flex YES The Flex storage class tier is used for dynamic workloads (mix of hot and cold workloads) where access patterns are more difficult to predict. Flex offers a low price to store data with a retrieval charge based on access patterns. Depending on usage, if the lower price of cooler storage combined with retrieval charges exceeds a cap value, then the storage price increases, and no retrieval charges apply. Common use cases include cloud-native analytics and cognitive workloads and user-generated apps
Wasabi   YES Wasabi is at the core of your enterprise-ready business cloud. For many companies, migrating their data to the cloud is a necessity, but with Wasabi, it offers the opportunity to choose a bottomless cloud of storage that’s 1/5th the cost and up to 6x the speed of most cloud providers with free unlimited egress. Panzura Freedom Filers are compatible with the following Wasabi tier: Wasabi Hot Cloud Storage. Wasabi has one offering that is supported by Panzura. Wasabi Hot Cloud Storage is an enterprise class, tier-free, instantly available and allows you to store an infinite amount of data affordably. Wasabi provides an S3-compliant interface to use with storage applications, gateways and other platforms
Dell   YES Virtustream Enterprise Cloud was purpose-built to run complex, mission-critical, I/O-intensive applications like SAP, Oracle and more with unmatched economics, infrastructure availability SLAs and integrated security and compliance.
NetApp StorageGrid   YES StorageGRID provides greater data management intelligence on a simplified platform for your object data. Because StorageGRID leverages S3, it painlessly bridges hybrid cloud workflows and enable your data to be fluid to meet your business demands.
Scality   YES Scality, world leader in object and cloud storage, develops cost-effective Software Defined Storage (SDS): the RING, which serves over 500 million end-users worldwide with over 800 billion objects in production; and the open-source S3 Server. Scality RING software deploys on any industry-standard x86 server, uniquely delivering performance, 100% availability and data durability, while integrating easily in the datacenter thanks to its native support for directory integration, traditional file applications and over 45 certified applications. Scality's complete solutions excel at serving the specific storage needs of Global 2000 Enterprise, Media and Entertainment, Government and Cloud Provider customers while delivering up to 90% reduction in TCO versus legacy storage.
IIJ GIO Service   YES The IIJ GIO Service provides a highly-flexible cloud environment for IIJ customers in Japan and beyond. With fully managed and dedicated services on demand, IIJ offers the VW Series, an option for customers to have dedicated VMware environments in the cloud. Customers can migrate their on-premise environments without modification, because the VW Series offers total freedom in designing and deploying OSs and applications run on the VMware virtualization platform.
WD ActiveScale System – Western Digital   YES ActiveScale helps customers implement a Data Forever strategy with seamless scalability of up to 52 petabytes and extreme data durability required for long-term data storage.
Dell EMC-ECS Cloud Storage   YES Dell EMC ECS is an industry-leading object storage platform built to support traditional and next-generation workloads. Available in multiple consumption models — software defined, as a turnkey appliance, or as a service operated by Dell EMC— ECS empowers organizations of all sizes to economically store and manage unstructured data at any scale, for any length of time.
Hitachi Cloud Provider (HCP/HDS)   YES HCP helps unify data with cost-effective object storage software to organize, preserve and govern vast data repositories through intelligent policy-based management and deliver differentiated cloud storage services and securely incorporate hybrid cloud – on your terms – to react faster to change and reduce costs
Cloudian Cloud Storage   YES Cloudian allows consolidation of data, organization-wide, to a single, exabyte-scalable data fabric. Cloudian’s modular design makes it easy to grow. It allows user to expand capacity and geographic reach simply by adding nodes anywhere the user needs capacity.

Panzura Vendor Feature Compatibility

  • AWS Intelligent Tiering - Panzura recommends using AWS Intelligent Tiering where available
  • AWS Transfer Acceleration - Panzura supports AWS Transfer Acceleration (Panzura AWS S3 Install Guide)
  • AWS SSE-KMS - Panzura supports Server Side Encryption via Key Management Service (Panzura AWS S3 Install GuidePanzura EC2 Deployment Guide)
  • Bucket Replication
  • Both AWS and Azure Asynchronous bucket replication. Panzura does not support this functionality.
  • Azure GRS - Panzura does not support Read Only regions and therefore cannot support Azure GRS

Using Bucket Snapshots can be a good Security Practice. In order to recover using Bucket Snapshots, please contact Panzura Professional Services. Significant downtime will be required.

EOL Products

The following services and products have reached the end of life. For information on how to access support for these cloud providers, please contact the service provider’s support team. Panzura Freedom Filers no longer support the following CSPs:

  • AT&T
  • HGST (Hitachi Global Storage Technologies)
  • ATMOS

Panzura Architecture

The Panzura architecture is based on the Panzura Freedom Operating System (PFOS), which provides a highly scalable, high performance Distributed Cloud File System (CloudFS™) that natively integrates with public, private and dark cloud storage systems. CloudFS supports applications that require global collaboration and file locking, combined with on‐premises NAS performance. Services include FIPS‐140 certified encryption, deduplication, and snapshots. Enterprises no longer have to plan for local backup and disaster recovery, as all the data and snapshots are in the cloud.

The Panzura Filer is an edge appliance that provides local-feeling performance. These virtual machines are reliable, high performance, optimized cloud storage appliances that can manage massive data densities within its scalable file system. The resilient storage subsystem protects data using military-grade encryption, multiple RAID parity protection schemes, efficient user-managed snapshots, and cloud storage.

The filer provides local and cloud storage for widely‐used file storage protocols, file management technologies, and directory services integration.

  • Network File System (NFS), used by Unix/Linux clients and servers
  • Server Message Block (SMB), used by Microsoft Windows clients and servers
  • Microsoft Active Directory (AD)

The filer can virtualize multiple disk media types within the same file system. Supported media include spinning hard disk drives (HDDs), solid-state drives (SSD), networked WAN‐addressable cloud storage, and LAN‐addressable NAS filer volumes. PFOS serves data to clients with SMB and NFS protocols.

Clustered Deployments

Geographically dispersed filers allow users who connect to CloudFS to experience a high‐speed file system, regardless of location. Updates to the file system are shared in the background, in near real-time, with all the other filers in the cluster. Integrated with CloudFS is a global file locking technology, called Global Read Write (GRW), which controls read and write file locking. This technology allows many users and work-sharing applications to leverage global CloudFS without suffering file locking or performance issues.

Within Panzura's distributed cluster architecture, all filers share access to a common storage cloud. The cloud is the authoritative source of data for all filers. The Panzura architecture includes technologies to leverage the difference in capacity and manage the aspects of deploying a NAS storage system that operates under this paradigm. Each Panzura filer provides LAN performance to CloudFS filer by locally caching data while presenting a complete metadata view of the entire DCFS that can span geographically.

Master and Subordinate Filers

The master/subordinate configuration refers to the management relationship between filers in a cluster deployment.

Configuration Replication

The configuration details of a Master Filer are automatically replicated and distributed to all Subordinate Filers. This simplifies the management of the CloudFS deployment. The replicated information includes:

  • Licenses
  • CloudFS operation mode
  • Filers that are permitted to participate in the shared CloudFS topology
  • Encryption certification for accessing data in the cloud between filers
  • SMB shares
  • NFS exports
  • Drive file size
  • Schedule filesystem snapshots
  • Deduplication setting
  • Data compression setting
  • Cloud upload order
  • SMB signing mode

Local and Remote Filers

The local filer is the filer nearest the user on a local LAN. A remote filer is one that is physically located in another office, somewhere around the globe. These terms are used when describing the flow of files and metadata within CloudFS, from one filer to another filer.

Users connect to their local filer, have a complete view of the shared file system, and experience LAN access speeds to the data in the global file system.

Sample Deployment

The following figure shows a Panzura deployment with three working sites—Los Angeles, London, and Paris—and two sites provisioned for high availability (HA)—Phoenix and Amsterdam. A Panzura filer is physically deployed at each site. Users at the three working sites connect to their local filer, have a complete view of the shared file system, and experience LAN access speeds to the data in the global file system.

Filer Features

The Panzura Filer provides the following features:

Software

  • Highly scalable 128‐bit transactional object file system
  • Intelligent read and write caching
  • In‐band file system Policy Engine
  • User managed snapshots
  • Globally distributed file sharing and locking for SMB
  • High availability

Hardware

  • Global namespace
  • RAID data protection
  • SSD and HDD

Security

  • Microsoft Active Directory (AD) integration
  • Extended file system ACLs
  • Kerberos authentication
  • Key Management Interoperability Protocol (KMIP) support
  • Scalable in‐line global deduplication
  • Multi‐protocol SMBv3, and NFSv4 file services
  • SMB load balancing
  • Military grade FIPS 140‐2 encryption
  • Policy‐based LAN and WAN bandwidth management
  • SNMPv3 monitoring, traps, and alerting
  • Email alerts for rapid response
  • Online remote monitoring and support
  • High‐speed parallelized WAN‐optimized cloud IO
  • Multiple cloud topologies (public, hybrid, private)
  • Real‐time cloud storage diagnostics
  • Full system recovery from the cloud
  • 1GbE and 10GbE NIC support (optical and copper)
  • Bandwidth shaping and connection tuning

Key Features

The following sections describe key features in detail.

Panzura Global Namespace

The Panzura unified namespace is an in‐band file system fabric that consists of multiple physical file system instances converged into a single file system metaspace and mounted locally on each node with the root label “CloudFS.”

The Panzura unified namespace does not rely on underlying distributed databases and thereby avoids common global namespace limitations that can affect speed, transactional data coherence, write order fidelity, open files, atomic precision, in‐band operation, and global snapshots. By contrast, other global namespace architectures require a database process on each storage system and changes to file metadata require complex out‐of‐band operations.

Cloud Mirroring

Cloud Mirroring allows you to copy data in real-time from one cloud object store to another cloud object store. Cloud Mirroring allows you to have an exact copy of your dataset. **

When Panzura Filers are configured with two clouds, they have a cloud connector. This connects the Rest API to the object store. One cloud object store is labeled as the primary cloud, and the other cloud object store is labeled as the secondary cloud. When you have two clouds and data is being written, data is written to both cloud object stores at the same time. The data is not released from the cache until an MD5 checksum is received and matched to both of the cloud object stores. This ensures that your data gets to each cloud location without data corruption or data loss. When your Panzura filer reads, it only reads from the primary cloud object store because it's unnecessary to read from both clouds when the data is identical. Writing to a cloud object store is free, but reading from a cloud object store can become expensive. Panzura filers will only read from the secondary cloud object store if the primary cloud object store fails. If you have multiple filers, communication (read and write requests) to each cloud object store occurs at each filer location. This ensures that we have consistent data in both cloud object stores. **

What triggers a failure? **

One hundred and sixty consecutive read or write failures on the same piece of data triggers a cloud failure. If the primary cloud fails, a failure is triggered across the entire CloudFS. An entire CloudFS will not failover to an inconsistent cloud. After a failure occurs, every write and read request is sent to the secondary cloud. With every read and write that occurs, the primary cloud becomes more outdated because it's in failure mode. **

While the primary cloud is down, the secondary cloud tracks the data that isn't being written to the primary cloud. When the primary cloud comes back up, your Panzura filer detects this and starts writing to both clouds again. In the background, your Panzura filer reads from the secondary cloud and writes the data that it missed while it was down to the primary cloud. The primary cloud does not become the primary again until the clouds are consistent again. Your Panzura filer cannot absorb a failure until the primary cloud is consistent again. **

How do I set up Cloud Mirroring if I'm an existing Panzura customer? **

If you configure cloud mirroring as an existing customer that's been operating for some time, your primary and secondary cloud begin to receive write requests for new data, but the Filer needs to synchronize all of the existing data from the primary cloud to the secondary cloud before they are considered fully synced.

The time that it takes for the secondary cloud to become consistent with the primary cloud depends on the amount of existing data that your primary cloud has stored, the bandwidth allocated for each filer to send data to the cloud, and latency. If you have a large amount of data, it could take days, weeks, or months for both of your clouds to become consistent. **

You must have the proper bandwidth policy to support Cloud Mirroring. You must talk with your SE or Support representative if you are considering enabling this feature. **

As a best practice, for all existing and new users, always create a master snapshot before enabling the Cloud Mirroring. Under ideal conditions, Master Snapshot must also be created before any Disaster Recover (DR) to keep the big picture intact and quicken the DR process in case necessary. **

In order to set up Cloud Mirroring, existing Panzura customers must upgrade to an 8.x release and contact support to ensure proper licensing.

Additional Links:

File Locking

PFOS and CloudFS support several file locking mechanisms. A traditional file lock is a lock issued against a file by a file system, a server, or an application. The lock can consist of extensive application-specific meta information and be written into parts of the file payload and/or its file system metadata.

File coherency locks are file system locks that are issued by applications to arbitrate guaranteed consistency between applications writing/reading to a single file, for example, MSFT Office Application locks.

Opportunistic caching locks are delegated rights that are issued by a file server protocol engine for a remote client to cache a file locally to increase client‐side performance. This is not necessarily a guaranteed write lock, because the delegation can be revoked by a file server at any time. Example: Microsoft SMB OPLOCKS.

Snapshots

Panzura uses snapshots to capture the state of the file system at a given point in time. In PFOS there are two types of snapshots; system managed and user managed. The system managed snapshots are used to provide file system consistency between filers. In a process called syncing, PFOS takes the changes (deltas) that occur to files and to the file system metadata, captures the delta information in a snapshot, and sends them to the cloud. The metadata portion of these changes is retrieved from the cloud by all other Panzura filers in the cluster where they are used to update the state of the file system and maintain concurrency. This system updating occurs continuously across all filers, with each filer sending and receiving extremely small metadata snapshot deltas and using them to update the file system.

User managed snapshots are controlled by the administrator to provide file system backups in the shared cloud storage backend. You can schedule automatic snapshot creation or take snapshots on demand. They are visible to the end user so they can be used to retrieve old versions of files without involving IT administration. Panzura guarantees that each filer will support more than 10,000 user‐managed snapshots.

Panzura recommends creating a user snapshot schedule that meets your business needs while maintaining a reasonable number of snapshots per filer when using a multi‐filer CloudFS configuration.

Smart Cache

PFOS supports Smart Cache, which reserves a percentage of local storage to intelligently track hot, warm, and cold file block structures as they are accessed. The cache dramatically increases data availability and I/O performance, because file data‐blocks reads have a higher probability of being serviced from local disk than directly from external cloud storage. The cache also increases overall data availability by masking variations in cloud availability. This allows the file system to continue serving I/O and cache‐resident data‐block reads even when the WAN link to the cloud storage slows or is unavailable, or if the cloud itself is down.

Cache policies govern what data is cached locally on the filer. PFOS provides fine‐grained configuration control over caching through the use of policies, rules, and actions that result in improved performance and enhanced cloud storage availability for users. When configuring cache policies, Panzura recommends using the auto cache action with prepopulate enabled. This ensures that files are available in disk cache for end users. Prepopulating makes the data available without forcing a reduction in cache.

Pinning allows an administrator to forcefully localize (pin) data in the cache within a filer to provide guaranteed LAN speed performance. Because pinning consumes cache space, it should be considered only if needed for performance, with the trade‐off between performance and cache space kept in mind.

Data is always protected in the cloud, irrespective of polices rules and pinning. See Smart Cache Settings.

Extended File System ACLs

The Panzura file system supports extended file system access control lists (ACLs) with full POSIX semantic compliance. For SMB, clients use a native Microsoft method with the Server Message Block (SMB) protocol for reading and writing extended ACLs. PFOS provides the ability to turn SMB signing on or off.

Scale out Global Deduplication

The filer supports enhanced data deduplication within the global file system with high performance, scalability, and system‐wide efficiency. The deduplication data architecture and physical layout on disk is optimized for local and global write performance and data addressability.

Enhanced Cloud Diagnostics

The filer provides a robust set of diagnostic and measurement tools for monitoring and understanding the health, status, and performance of the Panzura cloud storage infrastructure and interactions. The cloud diagnostics features include tools to analyze the cloud, while the cloud metrics features present a detailed set of trended graphs to visually display metrics about cloud reads and writes. The system also generates alerts if the cloud becomes unavailable.

Intelligent Symantec NetBackup Integration

PFOS supports intelligent integration with Symantec NetBackup, including awareness of the NetBackup data format stream. The system efficiently deduplicates the data stream inline with high optimization ratios. Tivoli TSM, Microsoft Robocopy and Symantec Backup Exec are also supported as cloud backup and cloud archive applications.

High Availability Solution

The Panzura High Availability (HA) solution consists of the following configuration options: *

  • HA Local: An active filer is protected by a dedicated standby. When the active filer fails, the passive standby assumes its identity and takes over operations. The takeover operation can be automatic or manual. HA Local is similar to the methods used by legacy enterprise storage product. In this configuration, an active filer is protected by a dedicated, passive standby. When the active filer fails, the standby takes over ownership of the file system and the filer operations. The following HA Local options are supported: *
  • Local: The active and standby filers have different hostnames and IP addresses. *
  • Local with shared address: The active filer and passive standby have an additional shared hostname and IP address, which simplifies the takeover process. This is required for Auto Failover. (Maximum length of the shared hostname is 15 characters.) *
  • HA Global: One or more filers are protected by one or more shared standbys, which can be separated geographically from the filers they protect. *

Auto Failover *

HA Local can be configured for Auto Failover. Auto Failover enables either of the filers in an active-standby pair that have a shared virtual IP (VIP) address to automatically perform a failover. *

In an Auto Failover configuration, both the active and standby filers regularly exchange health and status information. The filers regularly exchange status information in two ways: *

  • Directly over a peer-to-peer connection (SSH) *
  • Post status information to the cloud in state files *

DR Cloud Recovery

Full cloud disaster recovery (DR) allows rebuilding and recovery of an entire filer from the cloud after a disaster has occurred. In this highly optimized and efficient process, the file system is brought online and established as active from its cloud metadata instances as soon as possible following the disaster. A minimal set of data blocks are recovered from the cloud to bring the system to a state where clients can start using the filer, with remaining data downloaded in priority order.

Enterprise AntiVirus Plugin

Protecting file servers from viruses is an important part of an overall security strategy, and products such as McAfee VirusScan Enterprise and Symantec Protection Engine address this need well. You can install licenses to use these products to automatically scan files with the latest virus definitions.

cloudfs(config)# fips-mode enable *

FIPS **

Panzura CloudFS is FIPS 140-2 certified. To access this feature, FIPS 140-2 must be enabled or disabled in the command line interface (CLI) of each filer. **

You must enable or disable the FIPS mode before running the setup Wizard. **

If you need help with accessing the CLI, see Installing an Existing Key File (CLI). **

To enable FIPS 140-2 mode: **

1. Enter the admin as the user name and your registered password. **

Username: admin **

Password: **

2. Reenter your password. **

cloudfs> enable

Password: enable **

3. Enter the configuration. **

cloudfs# conf t **

4. Enter the following command to enable FIPS. **

cloudfs(config)# fips-mode enable **

5. If successful, exit the command line. **

cloudfs(config)# exit **

6. Write the following information to the memory to activate the FIPS mode. **

cloudfs# w m **

If the FIPS mode cannot be enabled, the following error message displays. **

ERROR: fips config error **

If you receive an error message, contact Panzura Support to enable the FIPS mode. **

To disable FIPS 140-2 mode: **

1. Enter admin as the user name and your registered password. **

Username: admin **

Password: **

2. Reenter your password. **

cloudfs> enable **

Password: enable **

3. Enter the configuration mode. **

cloudfs# conf t **

4. To disable FIPS, enter the following command. **

cloudfs(config)# fips-mode disable **

5. If successful, exit the command line. **

cloudfs(config)# exit **

7. Write the following information to the memory to activate the FIPS mode. **

cloudfs# w m **

If the FIPS mode cannot be enabled, the following error message displays. **

ERROR: fips config error **

If you receive an error message, contact Panzura Support to enable the FIPS mode. **

To check if FIPS 140-2 mode is enabled: **

1. Enter admin as the user name and your registered password. **

Username: admin **

Password: **

2. Enter the command to see the mode status. **

cloudfs# show fips-mode **

If a response does not display in the output, FIPS has never been configured and is disabled. After the FIPS mode is enabled once, you can view the Output value. **

FIPS mode is enabled if the output returns:- **

fipsmode: 1 **

FIPS mode is disabled if the output returns: - **

fipsmode: 0 **

You must perform steps 1-3 on each filer to enable or disable FIPS mode. **

The Enable or disable options for FIPS 140-2 mode is set on per-node basis. Users need to enable or disable all nodes within a cluster at the same time in order to activate or deactivate FIPS services on a cluster wide basis. **

User Auto Scaling **

The maximum number of SMB connections that are allowed is set based on system resources. The Panzura 5700/6700 hardware series limit is 5,000 connections. The limit for all other Panzura hardware series is 3,500 connections. A more granular scaling is applied for VM instances. **

Configuring the Filer

After the filer is installed, use the WebUI for all additional configuration and management. See the installation guide for your Panzura Filer platform for installation information.

Access the WebUI

  1. Enter the filer’s IP address into your web browser and log in using the default credentials. (See Setting Up the Panzura Filer ➡ Gather Information.)
  2. The system prompts you to change the admin password.

Navigate the WebUI

You’ll find these links on the Home page of the WebUI:

  • CloudFS: Look at the health of the overall filer network.
  • Dashboard: Get an overview of system performance.
  • Configuration: Set up the filer.
  • Maintenance: Keep the filer running smoothly.
  • Notifications: Check on alerts and other notifications

*

When you open any of the links, they show as tabs at the top of the page. Click the tabs to navigate, or click the X in a tab to close it.

You will also find these links at the top:

For the Configuration and Maintenance tabs, use the side menu to navigate to a section on the page, and then click an icon to reveal the settings within the selected category.