- Notes, Cautions, and Warnings
- Introduction
- How PowerVault FluidFS NAS Works
- FluidFS Terminology
- Key Features Of PowerVault FluidFS Systems
- Overview Of PowerVault FluidFS Systems
- PowerVault FluidFS Architecture
- Data Caching And Redundancy
- File Metadata Protection
- High Availability And Load Balancing
- Ports Used by the FluidFS System
- Other Information You May Need
- Upgrading to FluidFS Version 3
- FluidFS Manager User Interface Overview
- FluidFS 3.0
System Management
- Connecting to the FluidFS Cluster
- Managing Secured
Management
- Adding a Secured Management Subnet
- Changing the Netmask for the Secured Management Subnet
- Changing the VLAN ID for the Secured Management Subnet
- Changing the VIP for the Secured Management Subnet
- Changing the NAS Controller IP Addresses for the Secured Management Subnet
- Deleting the Secured Management Subnet
- Enabling Secured Management
- Disabling Secured Management
- Managing the FluidFS Cluster Name
- Managing Licensing
- Managing the System Time
- Managing the FTP Server
- Managing SNMP
- Managing the Health Scan Throttling Mode
- Managing the Operation Mode
- Managing Client
Connections
- Displaying the Distribution of Clients between NAS Controllers
- Viewing Clients Assigned to a NAS Controller
- Assigning a Client to a NAS Controller
- Unassigning a Client from a NAS Controller
- Manually Migrating Clients to another NAS Controller
- Failing Back Clients to Their Assigned NAS Controller
- Rebalancing Client Connections across NAS Controllers
- Shutting Down and Restarting NAS Controllers
- Managing NAS Appliance and NAS Controller
- FluidFS 3.0
Networking
- Managing the Default Gateway
- Managing DNS Servers and Suffixes
- Managing Static Routes
- Managing the Internal Network
- Managing the
Client Networks
- Viewing the Client Networks
- Creating a Client Network
- Changing the Netmask for a Client Network
- Changing the VLAN Tag for a Client Network
- Changing the Client VIPs for a Client Network
- Changing the NAS Controller IP Addresses for a Client Network
- Deleting a Client Network
- Viewing the Client Network MTU
- Changing the Client Network MTU
- Viewing the Client Network Bonding Mode
- Changing the Client Network Bonding Mode
- Managing SAN Fabrics
- FluidFS 3.0
Account Management And Authentication
- Account Management and Authentication
- Default Administrative Accounts
- Default Local User and Local Group Accounts
- Managing Administrator Accounts
- Managing Local Users
- Managing Password Age and Expiration
- Managing Local Groups
- Managing Active Directory
- Managing LDAP
- Managing NIS
- Managing User Mappings between Windows and UNIX/Linux Users
- FluidFS 3.0
NAS Volumes, Shares, and Exports
- Managing the NAS Pool
- Managing NAS Volumes
- File Security Styles
- Thin and Thick Provisioning for NAS Volumes
- Choosing a Strategy for NAS Volume Creation
- Example NAS Volume Creation Scenarios
- NAS Volumes Storage Space Terminology
- Configuring NAS Volumes
- Adding a NAS Volume
- Adding a NAS Volume
- Renaming a NAS Volume
- Changing Access Time Granularity for a NAS Volume
- Changing Permissions Interoperability for a NAS Volume
- Enabling or Disabling Zero Disk Usage Reporting for a NAS Volume
- Changing the Space Settings of a NAS Volume
- Enabling or Disabling a NAS Volume Used Space Alert
- Enabling or Disabling a NAS Volume Unused Space Alert
- Enabling or Disabling a NAS Volume Snapshot Space Consumption Threshold Alert
- Deleting a NAS Volume
- Cloning a NAS Volume
- NAS Volume Clone Defaults
- NAS Volume Clone Restrictions
- Managing NAS Volume Clones
- Managing CIFS Shares
- Managing NFS
Exports
- Configuring NFS Exports
- Viewing All NFS Exports on a FluidFS Cluster
- Viewing NFS Exports on a NAS Volume
- Adding an NFS Export
- Changing the Client Authentication Methods for an NFS Export
- Changing the Client Access Permissions for an NFS Export
- Enabling or Disabling Secure Ports for an NFS Export
- Enabling or Disabling Reported Size Limiting for an NFS Export
- Enabling or Disabling 32-bit File ID Compatibility for an NFS Export
- Deleting an NFS Export
- Enabling or Disabling NFS v4
- Setting Permissions for an NFS Export
- Accessing an NFS Export
- Configuring NFS Exports
- Managing Quota Rules
- Viewing Quota Rules for a NAS Volume
- Setting the Default Quota per User
- Setting the Default Quota per Group
- Adding a Quota Rule for a Specific User
- Adding a Quota Rule for Each User in a Specific Group
- Adding a Quota Rule for an Entire Group
- Changing the Soft Quota or Hard Quota for a User or Group
- Enabling or Disabling the Soft Quota or Hard Quota for a User or Group
- Deleting a User or Group Quota Rule
- Managing Data Reduction
- FluidFS 3.0
Data Protection
- Managing the
Anti-Virus Service
- Excluding Files and Directory Paths from Scans
- Supported Anti-Virus Applications
- Configuring
Anti-Virus Scanning
- Adding an Anti-virus Server
- Deleting an Anti-virus Server
- Enabling Anti-virus Scanning for a CIFS Share
- Allowing or Denying Access to Large Unscanned Files
- Changing the Anti-virus Scanning File Size Threshold for a CIFS Share
- Including or Excluding File Extensions and Directories in Anti-virus Scanning for a CIFS Share
- Disabling Anti-virus Scanning for a CIFS Share
- Viewing Anti-Virus Events
- Managing Snapshots
- Managing NDMP
- Managing Replication
- How Replication Works
- Target NAS Volumes
- Managing Replication Partnerships
- Replicating NAS Volumes
- Recovering an Individual NAS Volume
- Restoring the NAS Volume Configuration
- Restoring Local Users
- Restoring Local Groups
- Using Replication for Disaster Recovery
- Managing the
Anti-Virus Service
- FluidFS 3.0 Monitoring
- FluidFS 3.0 Maintenance
- Troubleshooting
- Viewing the Event Log
- Running Diagnostics
- Launching the iBMC Virtual KVM
- Troubleshooting Common Issues
- Troubleshooting Active Directory Issues
- Troubleshooting Backup Issues
- Troubleshooting CIFS Issues
- Misconfigured AV Host Settings Result In Access Denied To CIFS files
- CIFS Access Denied
- CIFS ACL Corruption
- CIFS Client Clock Skew
- CIFS Client Disconnection On File Read
- CIFS Client General Disconnection
- CIFS Client Login Failure
- CIFS Connection Failure
- CIFS Delete On Close Denial
- CIFS File Access Denied
- CIFS File Sharing Conflict
- CIFS Guest Account Invalid
- CIFS Locking Inconsistency
- CIFS Maximum Connections Reached
- CIFS Share Does Not Exist
- CIFS Path Share Not Found
- CIFS Write To Read Only Volume
- Troubleshooting NFS Issues
- Cannot Mount NFS Export
- NFS Export Does Not Exist
- NFS File Access Denied
- NFS Insecure Access To Secure Export
- NFS Mount Fails Due To Export Options
- NFS Mount Fails Due To Netgroup Failure
- NFS Mount Path Does Not Exist
- NFS Owner Restricted Operation
- NFS Write To Read-Only Export
- NFS Write To Read-Only Volume
- NFS Write To Snapshot
- NFS Access Denied To A File Or Directory
- Troubleshooting NAS File Access And Permissions Issues
- Troubleshooting Networking Issues
- Troubleshooting Replication Issues
- Replication Configuration Error
- Replication Destination Cluster Is Busy
- Replication Destination FS Is Busy
- Replication Destination Is Down
- Replication Destination Is Not Optimal
- Replication Destination Volume Is Busy Reclaiming Space
- Replication Destination Volume Is Detached
- Replication Disconnection
- Replication Incompatible Versions
- Replication Internal Error
- Replication Jumbo Frames Blocked
- Replication Destination Does Not Have Enough Space
- Replication Source Is Busy
- Replication Source Is Down
- Replication Source Is Not Optimal
- Replication Source Volume Is Busy Reclaiming Space
- Troubleshooting System Issues
- Getting Help
Dell FluidFS V3 NAS Solutions For PowerVault NX3500, NX3600, And NX3610Administrator's Guide
Failure Scenarios
The FluidFS system can tolerate a NAS controller failure without impact to data availability and without data loss. If one NAS controller becomes unavailable (for example, because the NAS controller failed, is turned off, or is disconnected from the network), the NAS appliance status is degraded. Although the FluidFS system is still operational and data is available to clients, the administrator cannot perform most configuration modifications and performance might decrease because data is no longer cached.
The impact to data availability and data integrity following a multiple NAS controller failure depends on the circumstances of the failure scenario. Dell recommends detaching a failed NAS controller as soon as possible, so that it can be safely taken offline for service. Data access remains intact as long as one of the NAS controllers in each NAS appliance in a FluidFS system is functional.
The following table summarizes the impact to data availability and data integrity of various failure scenarios.
| Scenario | System Status | Data Integrity | Comments |
|---|---|---|---|
|
Single NAS controller failure |
Available, degraded |
Unaffected |
|
|
Sequential dual‐NAS controller failure in single NAS appliance system |
Unavailable |
Unaffected |
Sequential failure assumes that there is enough time between NAS controller failures to write all data from the cache to disk (MD system or non‐volatile internal storage) |
|
Simultaneous dual‐ NAS controller failure in single NAS appliance system |
Unavailable |
Lose data in cache |
Data that has not been written to disk is lost |
|
Sequential dual‐NAS controller failure in multiple NAS appliance system, same NAS appliance |
Unavailable |
Unaffected |
Sequential failure assumes that there is enough time between NAS controller failures to write all data from the cache to disk (MD system or non‐volatile internal storage) |
|
Simultaneous dual‐NAS controller failure in multiple NAS appliance system, same NAS appliance |
Unavailable |
Lose data in cache |
Data that has not been written to disk is lost |
|
Dual‐NAS controller failure in multiple NAS appliance system, separate NAS appliances |
Available, degraded |
Unaffected |
|
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\