Manuale d’uso / di manutenzione del prodotto NX3600 del fabbricante Dell
Vai alla pagina of 189
Dell FluidFS V3 NAS Solutions For PowerVault NX3500, NX3600, And NX3610 Administrator's Guide.
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
Contents 1 Introduction .............................................................................................................. 11 How PowerVault FluidFS NAS Works ................................................................................
Viewing The Event Log .................................................................................................................. 32 Viewing Event Details .........................................................................................
Adding or Removing SNMP Trap Recipients ............................................................................... 45 Enabling or Disabling SNMP Traps .............................................................................................. 46 Managing the Health Scan Throttling Mode .
Creating a Client Network ............................................................................................................ 58 Changing the Netmask for a Client Network .......................................................................
Deleting a Local User .................................................................................................................... 73 Managing Password Age and Expiration ........................................................................
Thin and Thick Provisioning for NAS Volumes ............................................................................ 90 Choosing a Strategy for NAS Volume Creation ........................................................................... 90 Example NAS Volume Creation Scenarios .
Configuring Anti-Virus Scanning ................................................................................................ 120 Viewing Anti-Virus Events ............................................................................................
Deleting a NAS Appliance from the FluidFS Cluster ................................................................... 161 Detaching, Attaching, and Replacing a NAS Controller ................................................................... 161 Detaching a NAS Controller .
1 Introduction The Dell Fluid File System (FluidFS) network attached storage (NAS) solution is a highly-available file storage solution. The solution aggregates multiple NAS controllers into one system and presents them to UNIX, Linux, and Microsoft Windows clients as one virtual file server.
Term Description Fluid File System (FluidFS) A special purpose, Dell proprietary operating system providing enterprise class, high ‐ performance, scalable NAS services using Dell PowerVault, EqualLogic or Dell Compellent SAN storage systems. FluidFS Controller (NAS controller) Dell hardware device capable of running the FluidFS firmware.
Feature Description Connectivity options 1GbE and 10GbE, copper and optical options for connectivity to the client network. Highly available and active ‐ active design Redundant, hot ‐ swappable NAS controllers in each NAS appliance. Both NAS controllers in a NAS appliance process I/O.
NOTE: To identify the physical hardware displayed in PowerVault FluidFS Manager, match the Service Tag shown in FluidFS Manager with the Service Tag printed on a sticker on the front right side of the NAS appliance.
• NAS appliance network interface connections: – Client/LAN network – SAN network – Internal network The following figure shows an overview of the PowerVault FluidFS architecture: Figure 1. PowerVault FluidFS Architecture Overview Client/LAN Network The client/LAN network is used for client access to the CIFS shares and NFS exports.
MD System The PowerVault MD array provides the storage capacity for NAS; the NX36x0 cannot be used as a stand ‐ alone NAS appliance. The MD array eliminates the need for separate storage capacity for block and file storage. SAN Network The NX36x0 shares a back ‐ end infrastructure with the MD array.
High Availability And Load Balancing To optimize availability and performance, client connections are load balanced across the available NAS controllers. Both NAS controllers in a NAS appliance operate simultaneously. If one NAS controller fails, clients are automatically failed over to the remaining controllers.
Scenario System Status Data Integrity Comments system, same NAS appliance Dual ‐ NAS controller failure in multiple NAS appliance system, separate NAS appliances Available, degraded Unaffected • P.
Port Protocol Service Name 88 TCP and UDP Kerberos 123 UDP NTP 135 TCP AD ‐ RPC 138 UDP NetBIOS 139 TCP NetBIOS 161 UDP SNMP Agent 162 TCP SNMP trap 389 TCP and UDP LDAP 464 TCP and UDP Kerberos v5 .
NOTE: Always check for updates on dell.com/support/manuals and read the updates first because they often supersede information in other documents. 20.
2 Upgrading to FluidFS Version 3 Supported Upgrade Paths To upgrade to FluidFS version 3.0, the FluidFS cluster must be at FluidFS version 2.0.7630 or later. If the FluidFS cluster is at a pre ‐ 2.0.7630 version, upgrade to version 2.0.7680 prior to upgrading to version 3.
Feature Version 2.0 Version 3.0 remember this password because it is required to manage the FluidFS cluster in version 3.0. User ‐ defined management accounts Only local administrator accounts can be created.
Feature Version 2.0 Version 3.0 CIFS home shares Clients can access CIFS home shares in two ways: <client_VIP_or_name> <path_prefix><username> <client_VIP_or_name> homes Both access methods point to the same folder. Version 3.
Feature Version 2.0 Version 3.0 command, and then repeat the upgrade: system networking subnets add NEWINTER Primary 255.255.255.0 -PrivateIPs x.y.z.1,x.
• Delete local user names that have a period as the last character and re ‐ create the accounts with a different name, if needed. • Change the NDMP client port to be in the range 10000–10100, if needed. You must also make the reciprocal change on the DMA servers.
NOTE: • Perform pre ‐ upgrade tasks. • Installing a service pack causes the NAS controllers to reboot during the installation process. This might cause interruptions in CIFS and NFS client connections. Therefore, Dell recommends scheduling a maintenance window to perform service pack installations.
3. When the file is uploaded, click Install . The upgrade process starts and may take an hour or more. The upgrade’s progress is displayed as follows: 4. During the upgrade, you will be notified that a node has been rebooted. After receiving this message, wait 15 minutes more so that the reboot of both nodes and the Final Sync are completed.
28.
3 FluidFS Manager User Interface Overview FluidFS Manager Layout The following image and legend describe the layout of the FluidFS Manager. Figure 2. FluidFS Manager Web User Interface Layout FluidFS Manager Sections ❶ Left-hand tabs, used to select a view topic.
Figure 3. Navigating Views in FluidFS Manager Working With Panes, Menus, And Dialogs Showing And Hiding Panes Panes within the main view area display FluidFS elements and settings. A pane’s contents may be hidden by clicking the button, and displayed by clicking the button.
Changing Settings Within A Dialog When you select a menu option, a dialog box is displayed, which allows you to modify or delete the element or setting you chose.
Accessing NAS Volume SubTopics NAS Volumes have additional configuration subtopics that are not displayed by default. To display NAS Volume subtopics and their views: 1. Enter the NAS Volumes / All NAS Volumes view. 2. In the All NAS Volumes pane, click in the row of the volume whose subtopic views you want to display.
Figure 4. Event Log Viewing Event Details View detailed information for an event contained in the Event Log . In the Events pane on the bottom of the FluidFS Manager interface, click in the row of the event whose details you want to view. A dialog box displays the event details.
34.
4 FluidFS 3.0 System Management Connecting to the FluidFS Cluster As a storage administrator, you can use either the FluidFS Manager web client or command line interface (CLI) to connect to and manage the FluidFS cluster. The FluidFS cluster is accessed through the client network.
Connecting to the FluidFS Cluster CLI through SSH Using a Password Log on to the CLI through SSH to manage the FluidFS cluster. 1. Use either of the following options: – For Windows — Using an SSH client, connect to a client VIP.
traffic. Other subnets will not have any of the management ports listening on them, making them available only for client access, replication, and NDMP traffic. This prevents users on client (data) access subnets from accessing any FluidFS cluster management functions.
9. (Optional) Configure the remaining FluidFS management subnet attributes as needed. – To change the netmask of the network, type a netmask in the Netmask field.
7. Click OK . Changing the NAS Controller IP Addresses for the Secured Management Subnet Change the NAS controller IP addresses for the secured management subnet. 1. Click the System tab on the left. 2. Click the Internal tab on top. 3. In the Security Access pane, click .
4. Click Restrict Access of FluidFS Management . The Restrict Access of FluidFS Management dialog box appears. 5. Check the box whose text starts with All FluidFS management communication… . 6. Click OK . Disabling Secured Management Disable secured management to allow management traffic from any subnet.
Managing Licensing The license determines which NAS features are available in the FluidFS cluster. Viewing License Information All FluidFS cluster features are automatically included in the license for PowerVault scale ‐ out NAS. FluidFS Manager displays FluidFS cluster license information, but the license cannot be modified.
Setting the Time Zone Set the time zone for the FluidFS cluster. 1. Click the Performance & Connectivity tab on the left. 2. Click the Client Network & Time tab on the top. 3. In the Time pane, click . 4. Click Modify Time Configuration . The Modify Time Configuration dialog box appears.
Add or Remove NTP Servers Add one or more NTP servers with which to synchronize the FluidFS cluster time. Adding multiple NTP servers ensures continued time synchronization in the event of an NTP server failure. If the FluidFS cluster cannot establish contact with the first server, it attempts to connect to the remaining servers in order.
Managing the FTP Server The FluidFS cluster includes an FTP server that provides a storage location for the following types of system files: • Diagnostic results files • License file • SNMP MIBs.
Obtaining SNMP MIBs and Traps The SNMP MIBs and traps for the FluidFS cluster are available for download from the FluidFS cluster FTP server. NOTE: The FTP server must be enabled.
5. Add or remove SNMP trap recipients. – To add an SNMP trap recipient, type a host name or IP address in the Trap Recipients text field and click Add . – To remove an SNMP trap recipient, select an SNMP trap recipient and click the button. 6. Click OK .
Changing the Health Scan Throttling Mode Change the health scan throttling mode. Dell recommends keeping the health scan throttling mode set to Normal unless specifically directed otherwise by Dell Technical Support Services. 1. Click the System tab on the left.
Managing Client Connections Displaying the Distribution of Clients between NAS Controllers Display the current distribution of clients between NAS controllers. 1. Click the Performance & Connectivity tab on the left. 2. Click the Load Balancing tab on the top.
4. Click Pin Client to NAS Controller . The Pin Client to NAS Controller dialog box appears. 5. Ensure that the Pin Client to NAS Controller check box is unchecked.
4. Click Balance Clients . The Balance Clients Across NAS Controllers dialog box appears. 5. Click Rebalance clients . 6. Click OK . Shutting Down and Restarting NAS Controllers In some cases, you must temporarily shut down a FluidFS cluster or reboot a NAS controller.
4. Click Reboot . The Reboot NAS Controller dialog box appears. 5. Click OK . Managing NAS Appliance and NAS Controller You can configure the system identification button on the NAS appliances or controllers to blink, in order to easily locate that particular NAS appliance or controller within a rack.
52.
5 FluidFS 3.0 Networking Managing the Default Gateway The default gateway enables client access across subnets. Only one default gateway can be defined. If client access does not go through a router (i.e. this is a flat network), a default gateway does not need to be defined.
Viewing DNS Servers and Suffixes View the current DNS servers providing name resolution services for the FluidFS cluster and the associated DNS suffixes. 1. Click the Performance & Connectivity tab on the left. 2. Click the Client Network & Time tab on the top.
7. Click OK . Managing Static Routes To minimize hops between routers, static routes are recommended in routed networks when there are multiple direct paths from the FluidFS cluster to various routers. Static routes allow you to configure the exact paths in which the system communicates with various clients on a routed network.
4. Click Add Static Route . The New Static Route dialog box appears. 5. In the Target network subnet ID field, type a network IP address. For example, 10.10.5.0 6. In the Target subnet netmask field, type a netmask. For example, 255.255.255.0 7. In the Gateway field, type the gateway IP address through which to access the subnet.
3. In the Routing pane, select the static route that you want modify and click . 4. Click Delete static route . The Delete Static Route dialog box appears. 5. Click OK . Managing the Internal Network The internal network defines the private subnet dedicated to the FluidFS cluster for internal communication.
Viewing the Client Networks View the current client networks. 1. Click the Performance & Connectivity tab on the left. 2. Click the Client Network & Time tab on the top. The client networks are displayed in the Subnets pane. Creating a Client Network Create a client network on which clients access CIFS shares and NFS exports.
4. Click Modify . The Modify Client Subnet dialog box appears. 5. In the Netmask field, type a netmask for the client network. 6. Click OK . Changing the VLAN Tag for a Client Network Change the netmask for a client network. 1. Click the Performance & Connectivity tab on the left.
5. To edit one of the NAS Controller IP values (NAS Controller 0 or NAS Controller 1): a) Select the relevant row in the IP address list and click to edit. The Edit NAS Controller dialog box appears. b) In the IP Address field, type an IP address for the NAS controller and click OK .
Changing the Client Network Bonding Mode Change the bonding mode (Adaptive Load Balancing or Link Aggregation Control Protocol) of the client network interface to match your environment. • If using ALB, use one client VIP per client port in the FluidFS cluster.
Managing SAN Fabrics/Subnets In the FluidFS Manager, the SAN Fabrics view allows you to manage the various subnets and addresses on the PowerVault FluidFS system to ensure they match the configuration of the MD array(s). Viewing the SAN Network Configuration To view the SAN network configuration: 1.
5. In the Network interface dropdown, select the network interface to be used by the SAN fabric. 6. In the Netmask field, type the netmask IP address. 7. In the VLAN Id field, type the VLAN ID for the iSCSI subnet. 8. In the NAS Controller table, for each NAS controller: a) Click in the row of the NAS controller.
Viewing Storage Identifiers To view the NAS controller storage identifiers: 1. Click the Hardware tab on the left. 2. Click the SAN Fabrics tab on the top. The NAS controller storage identifiers are displayed in the Storage Identifier of Type: iSCSI pane.
6 FluidFS 3.0 Account Management And Authentication Account Management and Authentication There are two types of access to the FluidFS cluster: • Administrator ‐ level access for FluidFS cluster management • Client ‐ level access to CIFS shares and NFS exports Administrator accounts control administrator ‐ level access.
Login Name Purpose SSH Access Enabled by Default SSH Access Allowed VGA Console Access Enabled by Default VGA Console Access Allowed Default Password Administrator FluidFS cluster management (not a UN.
3. In the Security Access pane, click . 4. Click Modify Remote Support Policy . The Modify Remote Support Policy dialog box appears. 5. Enable or disable the support account. – To enable the support account, select the Allow Remote Support check box.
CLI Account The CLI account is used with an administrator account to access the command-line interface of the FluidFS cluster. Default Local User and Local Group Accounts The FluidFS cluster has the following built ‐ in local user and local group accounts, each of which serves a particular purpose.
NAS Volume Setting Volume Administrator Allowed to Change Setting? Data reduction Yes NAS volume space settings and alert thresholds Yes CIFS shares and NFS exports Yes Snapshots and snapshot schedule.
8. Click OK . Assigning NAS Volumes to a Volume Administrator By default, new volume administrators can manage all NAS volumes. After a volume administrator is created, you can change the NAS volumes that can be managed by the volume administrator. 1.
5. In the Email Address field, type the new email address for the administrator. 6. Click OK . Changing a Local Administrator Password You can change the password only for a local administrator account. The password for remote administrators is maintained in the external database.
NOTE: The group to which the local user is assigned must exist. 1. Click the Access Control tab on the left. 2. Click the User Repositories tab on the top. 3. In the Local Users pane, click . 4. Click New Local User . The New Local User dialog box appears.
3. Enable or disable the local user. – To enable the local user, clear the Disable access from this local user check box. – To disable the local user, select the Disable access from this local user check box. 4. Click OK . Changing a Local User Password Change the password for a local user account.
5. Click Edit Password Expiration . The Edit Password Expiration dialog box appears. 6. In the within [ ] days field, type the number of days after which the password will expire.
5. In the Local group name field, type a name for the group. 6. To add local users to the group: a) Click the […] button under the Local users in this group list. The User Browser dialog box appears. b) In the Search field, type either the full name of the user or the beginning of the user name and click the button.
5. To add local users to the group: a) Click the […] button under the Local users in this group list. The User Browser dialog box appears. b) In the Search field, type either the full name of the user or the beginning of the user name and click the button.
Enabling Active Directory Authentication Join the FluidFS cluster to an Active Directory domain to allow it to communicate with the directory service. By default, the FluidFS cluster uses the domain controller returned by Active Directory.
7. Click OK . Modifying Active Directory Authentication Settings You cannot directly modify the settings for Active Directory authentication. You must remove the FluidFS cluster from the Active Directory domain and then re ‐ join it to the Active Directory domain.
Adding multiple LDAP servers ensures continued authentication of users in the event of an LDAP server failure. If the FluidFS cluster cannot establish contact with the preferred server, it will attempt to connect to the remaining servers in order. 1. Click the Access Control tab on the left.
Adding or Removing LDAP Servers There must be at least one LDAP server. 1. Click the Access Control tab on the left. 2. Click the User Repositories tab on the top. 3. In the NIS or LDAP repository for NFS users pane, click . 4. Click Modify Settings .
6. Enable or disable authentication for the LDAP connection. – To enable authentication for the LDAP connection, select the Use Non ‐ Anonymous LDAP bind check box. Then, type the LDAP bind distinguished name used to authenticate the connection in the Bind DN field and type the LDAP bind password in the Bind Password field.
Enabling NIS Authentication Configure the FluidFS cluster to communicate with the NIS directory service. Adding multiple NIS servers ensures continued authentication of users in the event of a NIS server failure. If the FluidFS cluster cannot establish contact with the preferred server, it will attempt to connect to the remaining servers in order.
5. NIS servers are listed in descending order of preference. – To increase the precedence for a NIS server, select a NIS server and click . – To decrease the precedence for a NIS server, select a NIS server and click .
• NTFS security style: Permissions are controlled by Windows and NTFS. The UNIX/ Linux user adheres to the permissions of the corresponding Windows user, regardless of the UNIX/Linux permission settings. • UNIX security style: Permissions are based on the UNIX/Linux permissions.
5. Click the […] button to the right of the CIFS User (Active Directory) field. The User Browser dialog box appears. a) From the Domain drop ‐ down menu, select the domain to which the user is assigned. b) In the Starts with field, type either the full name of the user or the beginning of the user name and click the button.
86.
7 FluidFS 3.0 NAS Volumes, Shares, and Exports Managing the NAS Pool The amount of raw space allocated to the FluidFS cluster (NAS pool) is determined by the MD Array LUNs assigned to the NAS controllers. The maximum size of the PowerVault FluidFS NAS pool is 1 PB.
Expanding the Size of the NAS Pool You can increase the size of the NAS pool as your NAS storage space requirements increase, without affecting the services to the clients. However, you cannot decrease the size of the NAS pool. The maximum size of the NAS pool is 1 PB.
5. Enable or disable the NAS pool unused space alert. – To enable the NAS pool unused space alert, select the Alert when unused space is over check box. – To disable the NAS pool unused space alert, clear the Alert when unused space is over check box.
If you need to access the same set of files from both Windows and UNIX/Linux, the best way to implement multi ‐ protocol access is by setting up individual user mapping rules or by enabling automatic user mapping. Ownership and access permissions are automatically translated based on user mapping settings and file access credentials.
various data access patterns. The security style can also be set to Mixed which supports both POSIX security and Windows ACLs on the same NAS volume. • Quotas: Different quota policies can be applied to different NAS volumes, allowing the administrator to focus on managing quotas when it is appropriate.
• Disadvantage : User mapping is required. A user needs to choose one security style, either NTFS or UNIX, and based on the security style chosen the correct mapping for other users is set. NAS Volumes Storage Space Terminology FluidFS Manager displays storage space details for individual NAS volumes and for all NAS volumes collectively.
Adding a NAS Volume Add a NAS volume to allocate storage that can be shared on the network. When a NAS volume is added, default values are applied for some settings. To change the defaults, you must modify the NAS volume. 1. Click the NAS Volumes tab on the left.
Changing Permissions Interoperability for a NAS Volume Change the permissions interoperability settings of a NAS volume to change the file access security style for the NAS volume. 1. Click the NAS Volumes tab on the left. 2. Click the All NAS Volumes tab on the top.
7. For Thin NAS Volumes: in the Reserved Space field, type the size of the storage that is statically allocated to the NAS volume and select the units as megabytes (MB), gigabytes (GB), or terabytes (TB). NOTE: The reserved space must be smaller than the configured size of the NAS volume.
5. Enable or disable a NAS volume snapshot space consumption threshold alert. – To enable a NAS volume snapshot space consumption threshold alert, select the Alert when snapshot space is over check box. – To disable a NAS volume snapshot space consumption threshold alert, clear the Alert when snapshot space is over check box.
NAS Volume Clone Restrictions The following restrictions apply to cloned NAS volumes: • You cannot create a clone NAS volume of a clone NAS volume (nested clones) unless a clone NAS volume is replicated to another FluidFS cluster and then cloned. • You cannot delete a base volume until all of its clone NAS volumes have been deleted.
• The snapshot space consumption threshold alert must be disabled on the base volume. 1. Click the NAS Volumes tab on the left. 2. Click the All NAS Volumes tab on the top. 3. In the All NAS Volumes pane, click in the row of the volume whose NAS volume clones you want to view.
Viewing All CIFS Shares on the FluidFS Cluster View all current CIFS shares for the FluidFS cluster. 1. Click the NAS Volumes tab on the left. 2. Click the All CIFS Shares tab on the top. The CIFS shares are displayed in the All CIFS Shares pane. Viewing CIFS Shares on a NAS Volume View the current CIFS shares for a NAS volume.
user or group. When SLP access ‐ based share enumeration is disabled, the CIFS share, and its folders and files, will be visible to users and groups regardless of whether they have permissions for the CIFS share. To enable or disable accessed-based share enumeration for a CIFS share: 1.
4. Click Disconnect . The Disconnect Connection dialog box appears. 5. Click OK . Using CIFS Home Shares The FluidFS cluster enables you to create a share per client that is limited to that client.
Changing the Owner of a CIFS Share When a CIFS share is created, the owner of the CIFS share must be changed before setting any access control lists (ACLs) or share level permissions (SLP), or attempting to access the CIFS share.
9. Click Other users or groups . The Select User or Group dialog box appears. 10. Choose the domain admin user account that is used to set ACLs for this CIFS share or choose the Domain Admins group. Alternatively, the FluidFS cluster Administrator account can be used.
NOTE: You might need to reset the local administrator password first. If there are no predefined MMC files: 1. Select Start → Run . 2. Type mmc and click OK . The [Console 1 ‐ Console Root] window is displayed. 3. Select File → Add/Remove Snap ‐ n .
Accessing a CIFS Share Using the Windows Network Connect to the share using the Windows Network. This option does not map the share. 1. From the Start menu, select Computer . The Computer window is displayed. 2. Click Network . 3. Locate the NAS appliance and double ‐ click it.
4. Click View Details . 5. Click the NFS Exports tab on the top. Adding an NFS Export Create an NFS export to share a directory in a NAS volume using the NFS protocol. When an NFS export is added, default values are applied for some settings. To change the defaults, you must modify the NFS export.
Changing the Client Access Permissions for an NFS Export Change the permissions for clients accessing an NFS export. 1. Click the NAS Volumes tab on the left. 2. Click the All NAS Volumes tab on the top. 3. In the All NAS Volumes pane, click in the row of the volume whose NFS exports shares you want to modify.
9. Click OK . Enabling or Disabling Reported Size Limiting for an NFS Export To enable access for client machines that cannot handle large file systems, limit the reported size of the NFS export. 1. Click the NAS Volumes tab on the left. 2. Click the All NAS Volumes tab on the top.
3. In the All NFS Exports pane, click in the row of the NFS export you want to delete. 4. Click Delete . The Delete dialog box appears. 5. Click OK . Enabling or Disabling NFS v4 NFS v4 is enabled or disabled on a system wide basis. By default, NFS v4 is disabled, which forces clients to use NFS v3 and earlier.
# mount -o nfsvers=3,rsize=32768,wsize=32768 <client_VIP_or_name>:/ <volume_name>/<exported_folder> <local_folder> Accessing an NFS Export with UNIX/Linux without Default Use of TCP Older versions of UNIX/Linux do not use TCP by default.
9. To enable a hard quota limit, select the Hard Quota check box and type a hard quota limit in megabytes (MB), gigabytes (GB), or terabytes (TB) at which no more writing to the NAS volume will be permitted. 10. Click OK . Setting the Default Quota per Group Configure the quota applied to groups for which no other quota is defined.
15. To enable a hard quota limit, select the Hard Quota check box and type a hard quota limit in megabytes (MB), gigabytes (GB), or terabytes (TB) at which no more writing to the NAS volume is permitted. 16. Click OK . Adding a Quota Rule for Each User in a Specific Group Configure the quota applied to each user that belongs to a group.
9. From the Domain drop ‐ down menu, select the group’s domain. 10. In the Starts with field, type either the full name of the group or the beginning of the group name. 11. Click Display . 12. Select a group from the search results. 13. Click OK .
8. Enable or disable the soft quota limit. – To enable the soft quota limit, select the Soft Quota check box. – To disable the soft quota limit, clear the Soft Quota check box. 9. Enable or disable the hard quota limit. – To enable the hard quota limit, select the Hard Quota check box.
There are several factors to consider when enabling data reduction: • Data reduction processing has a 5 ‐ 20% impact on the performance of read operations on reduced data. There is no impact on write operations on reduced data. • Increased internal traffic during data reduction processing.
9. To change the number of days after which data reduction is applied to files that have not been accessed, type the number of days in the Optimize files that were not accessed in the last field.
Disabling Data Reduction on a NAS Volume By default, after disabling data reduction on a NAS volume, data remains in its reduced state during subsequent read operations.
118.
8 FluidFS 3.0 Data Protection Managing the Anti-Virus Service The FluidFS cluster anti ‐ virus service provides real ‐ time anti ‐ virus scanning of files stored in CIFS shares. The anti ‐ virus service applies only to CIFS shares; NFS is not supported.
Excluding Files and Directory Paths from Scans You can determine which files and directory paths are scanned, using extension or location properties as follows: • File Extensions Excluded From Virus Scan : Specifies file extensions (file types) to exclude from scanning, such as docx .
5. In the Antivirus Server field, type the host name or IP address of the anti ‐ virus server. 6. In the Port field, type the port that the FluidFS cluster uses to connect to the anti ‐ virus server. 7. Click OK . Deleting an Anti-virus Server Delete an anti ‐ virus server when it is no longer available.
Allowing or Denying Access to Large Unscanned Files Specify whether to allow or deny access to files that are larger than the specified anti ‐ virus scanning file size threshold for a CIFS share. 1. Click the NAS Volumes tab on the left. 2. Click the All CIFS Shares tab on the top.
8. To remove an extension or folder from the exemption list, select the extension or folder and click . 9. Click OK . Disabling Anti-virus Scanning for a CIFS Share Anti ‐ virus scanning is disabled on a per CIFS share basis. 1. Click the NAS Volumes tab on the left.
Creating On-Demand Snapshots Create a NAS volume snapshot to take an immediate point ‐ in ‐ time copy of the data. 1. Click the NAS Volumes tab on the left. 2. Click the All NAS Volumes tab on the top. 3. In the All NAS Volumes pane, click in the row of the volume for which you want to create a snapshot.
10. (Optional) Configure the remaining snapshot schedule attributes as needed. – To retain all snapshots that are created by the snapshot schedule indefinitely, clear the Retain each snapshot for check box.
Deleting a Snapshot Schedule Specify whether to retain all snapshots that are created by a snapshot schedule, or configure the snapshots to expire after a certain period of time. 1. Click the NAS Volumes tab on the left. 2. Click the All NAS Volumes tab on the top.
7. Click Modify . The Modify Snapshot dialog box appears. 8. To retain all snapshots that are created by the snapshot schedule indefinitely, clear the Retain each snapshot for check box.
5. Click the Snapshots tab on the top. The snapshots are displayed in the Snapshots pane. Restoring a NAS Volume from a Snapshot View the snapshots available for restoring data. The storage administrator can restore an entire NAS volume from a snapshot.
Restoring Files Using Windows Only Snapshots integrate into the Shadow Copies and previous versions features of Windows. This restore option allows clients to restore a file using previous versions. 1. Right ‐ click the file, select Properties , and then click the Previous Versions tab.
The following steps are involved in backing up NAS volume data using NDMP: 1. The DMA server creates a connection to the FluidFS cluster IP address. NOTE: NDMP does not provide High Availability (HA). If a backup session is interrupted due to connection loss, the session is terminated.
4. Click Modify Settings . The Modify NDMP Settings dialog box appears. 5. In the DMA Servers text field, type the IP address of a DMA server and click Add . Repeat this step for any additional DNA servers. 6. Click OK . Removing a DMA Server Remove a DMA server if it is no longer needed for NDMP backups.
Changing the NDMP Client Port By default, the NDMP server monitors port 10000 for incoming connections. You can change the client port to match the port used by the DMA. 1. Click the System tab on the left. 2. Click the Data Protection tab on the top.
Viewing Active NDMP Jobs View all NDMP backup and restore operations being processed by the FluidFS cluster. 1. Click the Performance & Connectivity tab on the left. 2. Click the CIFS & NDMP Sessions tab on the top. The NDMP jobs are displayed in the NDMP Sessions pane.
Replication can be used in various scenarios to achieve different levels of data protection. Replication Scenarios Description Fast backup and restore Maintain full copies of data for protection again.
different NAS volumes to different partners, depending on operational requirements. However, each individual NAS volume can be replicated to only one target NAS volume on one replication partner. The following figure summarizes which replications scenarios are supported and unsupported.
Once a partner relationship is established, replication is bi ‐ directional. One system could hold target NAS volumes for the other system as well as source NAS volumes to replicate to that other system. A replication policy can be set up to run according to a set schedule or on demand.
NOTE: • Both the source and target FluidFS clusters have the same NAS appliance count. For example, if the source FluidFS cluster has two NAS appliances, the target FluidFS cluster must have two NAS appliances. Do not attempt to replicate a four ‐ NAS appliance FluidFS cluster to a two ‐ NAS appliance FluidFS cluster.
systems is down or unreachable, the partnership is deleted only on the system that is running. Once the other system comes back up, the partnership must be deleted on that system too. 1. Click the System tab on the left. 2. Click the Data Protection tab on the top.
NOTE: • The target NAS volume must be promoted to a standalone NAS volume. • You must remove replication schedules for the replication. 1. Click the NAS Volumes tab on the left. 2. Click the All NAS Volumes tab on the top. 3. In the All NAS Volumes pane, click in the row of the volume whose replication you want to delete.
9. Specify when to run replication: – To run replication based on a period of time, select Take replication every [ ] minutes and type in the number of minutes. – To run replication based on day and time, select Take replication on and select the day, hour and minute at which to run replication.
place in a FluidFS cluster, or between a specified pair of replication partners. You can pause replication only from the source FluidFS cluster. 1. Click the NAS Volumes tab on the left. 2. Click the All NAS Volumes tab on the top. 3. In the All NAS Volumes pane, click in the row of the volume whose replication schedule you want to delete.
Promoting a Target NAS Volume When you resume replication, any replication operations that were in progress at the time the operation was disabled will resume.
• NFS exports • Snapshot schedules • Quota rules This is useful in the following circumstances: • After recovering a system • After recovering a NAS volume • When failing over to a replica.
6. Select the settings to restore from backup: – To restore CIFS shares, select the CIFS Shares check box. – To restore NFS exports, select the NFS Exports check box. – To restore snapshot schedules, select the Snapshot Scheduling check box. – To restore quota rules, select the Quota Rules check box.
6. In the Restore local users from backup taken from cluster drop ‐ down menu, select the cluster whose backup will be used to restore local users. 7. Click OK . Restoring Local Groups Restoring the local group configuration provides an effective way to restore all local groups without having to manually reconfigure them.
Using Replication for Disaster Recovery You can create a disaster recovery configuration in which you replicate data from a primary FluidFS cluster to a target FluidFS cluster. You can fail over to the target cluster if the primary FluidFS cluster stops responding because of an unexpected failure (hardware, disk, and so on).
Dell recommends that you maintain a table to track which DNS entries are used to access each NAS volume. This helps when performing failover and setting up group policies. Setting Up and Performing Disaster Recovery This section contains a high ‐ level overview of setting up and performing disaster recovery.
Phase 2 — Cluster A Fails And Client Requests Fail Over To Backup Cluster B If source cluster A stops responding because of an unexpected failure (hardware, disk, and so on), you must: 1. Log on to backup cluster B. 2. Delete the existing replication policy for all replication target volumes.
5. Ensure that cluster B is used to temporarily serve client requests during the fail over time. Administrators must perform the following steps to set up DNS and authentication: a) Point the DNS names from customer DNS server to cluster B instead of cluster A.
5. In the NAS Manager web interface, select Data Protection → Replication → NAS Replication and click Replicate Now for all the volumes in cluster B (B1, B2, .., B n ). If the replication fails, fix the problems encountered and restart the replication process.
9. Start using cluster A to serve client requests. Administrators must perform the following steps to set up DNS and authentication: a) Point the DNS names from customer DNS server to cluster A instead of cluster B. Ensure that the DNS server on cluster A is the same as the DNS server or in the same DNS farm as the DNS server of cluster B.
152.
9 FluidFS 3.0 Monitoring Viewing the Status of Hardware Components FluidFS Manager displays the status of the following NAS appliance and NAS controller hardware components: • Networks • Disks •.
Viewing the Status of the Power Supplies View the status of the power supplies in a NAS appliance. 1. Click the Hardware tab on the left. 2. Click the NAS Appliances tab on the top. 3. In the pane of the NAS appliance you want to view, expand the NAS Controllers node.
155.
Viewing the Status of Background Processes Some operations take some time to perform and do not complete immediately, such as detaching a NAS controller. In these cases, you can monitor the progress of operations in FluidFS Manager. 1. Click the System tab on the left.
3. Graphs for the following performance values are displayed: – Overall Read Throughput – click the Client , Replication , and NDMP buttons to display or hide the relevant performance graphs. – Overall Write Throughput – click the Client , Replication , and NDMP buttons to display or hide the relevant performance graphs.
158.
10 FluidFS 3.0 Maintenance Adding and Deleting NAS Appliances in a FluidFS Cluster Use FluidFS Manager to add or delete a NAS appliance in a FluidFS cluster. Adding NAS Appliances to the FluidFS Cluster You can add a NAS appliance (two NAS controllers) to the FluidFS cluster to increase processing power.
5. Click New NAS Appliance . The New NAS Appliance dialog box appears. 6. Select the NAS appliance to add to the FluidFS cluster. a) In the top pane, select the NAS appliance. b) Click Add Appliance . The selected NAS appliance is moved to the bottom pane.
12. Click Next . After you are finished configuring each client network, the Connectivity Report page displays. 13. Use the Connectivity Report page to verify connectivity between the FluidFS cluster and the MD array. The NAS controller ports must show the status Up before you can complete the wizard.
3. In the Overview pane, click in the row of the NAS appliance whose controller you want to detach. 4. Click Detach . The Detach NAS Controller dialog box appears. 5. In the NAS controller dropdown, select the controller you want to detach. 6. Click OK .
3. Disconnect all cables from the back of the existing NAS controller. 4. Remove the existing NAS controller from the NAS appliance chassis. a) Press the controller release button to disengage the controller handle. b) Push the controller handle down until the controller disengages from the appliance.
ftp open <client_VIP_or_name> 44421 <FluidFS_administrator_user_name> <FluidFS_administrator_password> cd servicepack bin put <path_to_service_pack>/DellFluidFS-3.0.<xxxx>-SP.sh quit To upload and install the service pack upgrade file using the web UI: 1.
NOTE: • If the NAS controller is still an active member in the FluidFS cluster, you must first detach it. • Connect a monitor to the NAS controller’s VGA port and connect a keyboard to one of the NAS controller’s USB ports. 1. Press and release the recessed power button at the back of the NAS controller to shut down the NAS controller.
166.
11 Troubleshooting Viewing the Event Log You can view messages about system events and errors in the Event Log. Running Diagnostics Running diagnostics helps you detect problems with the FluidFS cluster. The diagnostic options available for the FluidFS cluster are: • FluidFS diagnostics : Used to diagnose software issues.
5. Enter any requested diagnostic parameters and click OK . After the diagnostics have been run, FluidFS Manager will perform a Phone Home of the diagnostics if the FluidFS cluster FTP server is enabled.
Troubleshooting Common Issues Troubleshooting Active Directory Issues Group Quota For An Active Directory User Does Not Work Description Group quota is defined for an Active Directory group; however, when a group member consumes space, the actual usage of the group does not grow and the group limitation is not enforced.
Workaround When configuring the system to connect to an Active Directory domain: 1. Ensure that you use FQDN and not the NETBIOS name of the domain or IP address of the domain controller. 2. Ensure that the user has permissions to add systems to the domain.
2. On the NAS Manager, go to Data Protection → NDMP → NDMP Configuration page. In NAS CLI, go to Data Protection NDMP Configuration menu. 3. Verify that NDMP is enabled. If NDMP is enabled, go to step 5. 4. On the NAS Manager, the Enabled check box must be checked.
CIFS ACL Corruption Description CIFS ACL corruption. Cause • ACLs were accidently changed by a user or script. • ACL is corrupted after an antivirus application accidently quarantined corresponding files. • ACL got corrupted after data recovery by backup application due to compatibility issues.
Workaround Interactive users can retry with correct password. Applications and servers may need special attention as the user/password, which is usually set in a script or configuration file, has probably expired. CIFS Connection Failure Description CIFS client share access denied.
CIFS Locking Inconsistency Description CIFS service is interrupted due to CIFS interlocking issues. Cause CIFS client interlocking scenarios. Workaround System recovers itself automatically, issuing the above event when recovered. CIFS Maximum Connections Reached Description Maximum number of CIFS connections per NAS controller is reached.
2. Manually create the missing directories. Set permissions to control access as required. 3. Remove the share and communicate to the client. CIFS Write To Read Only Volume Description Client tries to modify a file on read-only volume. Cause A NAS volume is set to read-only when it is the target of a replication.
• Check that the system's IP address, IP range, domain name or netgroup is in the exports list. If the appliance not responding due to a port mapper failure: • Check the NAS cluster appliance status. • Check the network connection by trying to NFS mount from some other system.
NFS Insecure Access To Secure Export Description User tries to access a secure export from an insecure port. Cause Secure export requirement means that the accessing clients must use a well-known port (below 1024), which usually means that they must be a root (uid=0) on the client.
Identify the relevant export and the options defined for it, while focusing on the netgroup definition. Document the used netgroup in order to restore it after the issue is solved and remove the netgroup limitation. NFS Mount Path Does Not Exist Description Client tries to mount a mount path that does not exists on a NAS container.
NFS Write To Snapshot Description An NFS user tries to modify a file located in a snapshot. Cause NAS volume snapshots cannot be modified by design. Workaround Snapshot data cannot be modified. A snapshot is an exact representation of the NAS volume data at the time of its creation.
a. Verify there is enough free space on the NAS volume or expand it. b. Verify that the accessed NAS volume is not a target of a replication. Mixed File Ownership Denied Description Both file owner and group owner must be from the same identity type (either UNIX or NTFS).
Troubleshooting Networking Issues Name Server Unresponsive Description All NIS, LDAP, or DNS servers are unreachable or not responding. Workaround For each server: 1. Ping the server from a client on NAS cluster solution subnet and verify it responds.
Troubleshooting RX And TX Pause Warning Messages Description The following warning messages may be displayed when the NAS Manager reports connectivity in a Not Optimal state: Rx_pause for eth(x) on node 1 is off. Tx_pause for eth(x) on node 1 is off. Cause Flow control is not enabled on the switch(es) connected to a NAS cluster solution controller.
Replication Destination Is Not Optimal Description Replication between the NAS source volume and the NAS destination volume fails because the destination NAS volume is not optimal. Cause Replication fails because file system of the destination NAS volume is not optimal.
Replication Internal Error Description Replication between the source and the destination NAS volumes fails due to an internal error. Workaround Contact Dell to resolve this issue.
Workaround The administrator must check the file system status of source system, using the monitoring section in the NAS Manager, to understand why the file system is not optimal.
Multiple Errors Received During File System Format Description You receive multiple errors during a file system format. Cause Probable causes may be: • Incorrect SAN IPs are used in the Dell NAS Initial Deployment Utility (IDU). • Incorrect IQNs used while defining hosts in the MDSM.
3. Try to format the system. Associating LUN Names To Virtual Disks Description Determining which LUNs in the NAS Manager are virtual disks in the Modular Disk Storage Manager (MDSM). Workaround Open the NAS Manager web interface and go to Cluster Management → Maintenance → Add Luns.
• Do not reboot the controller manually if it is in the boot phase Executing System Upgrades . 188.
12 Getting Help Contacting Dell NOTE: Dell provides several online and telephone-based support and service options. If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog.
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il Dell NX3600 è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del Dell NX3600 - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso Dell NX3600 imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul Dell NX3600 ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il Dell NX3600, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del Dell NX3600.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il Dell NX3600. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo Dell NX3600 insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
