Matrix File Serving Solution Pack for CIFS Administration Guide Matrix File Serving Solution Pack for CIFS 3.
Copyright © 2004-2007 PolyServe, Inc. Use, reproduction and distribution of this document and the software it describes are subject to the terms of the software license agreement distributed with the product (“License Agreement”). Any use, reproduction, or distribution of this document or the described software not explicitly permitted pursuant to the License Agreement is strictly prohibited unless prior written permission from PolyServe has been received.
Contents 1 HP Technical Support HP Storage Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 HP NAS Services Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 Introduction Virtual CIFS Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Matrix File Shares. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MxFS for CIFS and Legacy Client Operating Systems . . . .
Contents iv DNS Requirement for Virtual CIFS Servers . . . . . . . . . . . . . . . . . Create a Virtual CIFS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add a Virtual File Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Virtual File Share Advanced Configuration. . . . . . . . . . . . . . . . . . . . Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Scripts . . . . . . . . . . . . . . . . . . .
1 HP Technical Support Telephone numbers for worldwide technical support are listed on the following HP website: http://www.hp.com/support. From this website, select the country of origin. For example, the North American technical support number is 800-633-3600. NOTE: For continuous quality improvement, calls may be recorded or monitored.
Chapter 1: HP Technical Support 2 HP NAS Services Website The HP NAS Services site allows you to choose from convenient HP Care Pack Services packages or implement a custom support solution delivered by HP ProLiant Storage Server specialists and/or our certified service partners. For more information see us at http://www.hp.com/hps/storage/ns_nas.html. Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
2 Introduction The Matrix File Serving Solution Pack for CIFS (MxFS for CIFS) and PolyServe Matrix Server provide scalability and high availability for the Common Internet FileSystem (CIFS). CIFS is a variation of the Server Message Block (SMB) protocol. It runs over TCP/IP and is commonly used on Windows systems to share files remotely.
Chapter 2: Introduction 4 with Matrix Server) will fail over, or migrate, the Virtual CIFS Server to one of the backup servers, where it will continue to provide access to the same PSFS filesystem data under the same name/IP-address pair. This deployment method works well with clients running modern Windows operating systems such as Windows XP and Windows 2000.
Chapter 2: Introduction 5 MxFS for CIFS and Legacy Client Operating Systems Several legacy client operating systems do not support the modern networking infrastructure required to connect to a virtualized network connection such as that provided by the Virtual CIFS Server. These operating systems include Windows NT4, Windows ME, Windows 98, Windows 95, Windows 3.1, DOS, MAC SMB client, and some Linux versions.
Chapter 2: Introduction 6 A Linux client implemented in Java is available at this location: http://jcifs.samba.org/ In addition to interoperating with DFS, Linux clients can also connect directly to Virtual File Shares. (See “Linux Clients” on page 34 for more information.) NOTE: The Samba smbcacls utility can be helpful for Linux clients that need to handle Windows DACLs on PSFS filesystems. See the Samba smbcacls man page for details.
Chapter 2: Introduction 7 MxFS for CIFS operations. If desired, the Matrix Server Role-Based Security Control Panel can be used to create a role specifically for file-sharing operations. See the PolyServe Matrix Server Administration Guide for more information. Matrix Server requires that Active Directory be configured. See the “Administrative Considerations and Restrictions” section of the PolyServe Matrix Server Administration Guide for more information. Copyright © 1999-2007 PolyServe, Inc.
3 Configure MxFS for CIFS with Matrix File Shares Configuration Overview Matrix File Shares are Windows CIFS shares associated with a MxFS for CIFS filesystem health monitor. Clients connect to Matrix File Shares using the network name or IP address of any physical server in the cluster. Each node in the cluster provides access to the same PSFS filesystems through its Matrix File Shares.
Chapter 3: Configure MxFS for CIFS with Matrix File Shares 9 There are two steps to the configuration process: first create Matrix File Shares and then configure DFS (or another load balancer). NOTE: Before creating Matrix File Shares, you will need to create PSFS cluster filesystems to store the files that will be shared via CIFS. For each filesystem, you will need to assign a drive letter or path that will be used to access the filesystem.
Chapter 3: Configure MxFS for CIFS with Matrix File Shares 10 Application: An “application” provides a tag to group Matrix File Shares and related resources on the Applications tab. All of the resources associated with the application can then be treated as a unit. You can specify a new application name, select an existing application name, or leave this field blank. However, if you do not assign a name, Matrix Server will use the name of the Matrix File Share as the application name.
Chapter 3: Configure MxFS for CIFS with Matrix File Shares 11 Caching: Offline caching allows users to cache files and programs from the share to their local machines. There are three options: • Only the files and programs that users specify will be available offline. This option lets users select the files that will be available offline. • All files and programs that users open from the share will be automatically available offline.
Chapter 3: Configure MxFS for CIFS with Matrix File Shares The Applications tab lists the Matrix File Shares under the associated applications. Following is the Applications view of the above configuration. Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
Chapter 3: Configure MxFS for CIFS with Matrix File Shares 13 To add a Matrix File Share from the command line, use this command: mx mfs add --path --servers ALL_SERVERS| , ,... [arguments] See the Matrix Server Command Reference for more information about this command. Configure DFS The Microsoft Distributed File System (DFS) can be used in conjunction with MxFS for CIFS to provide high availability failover and load balancing across the nodes in the matrix.
Chapter 3: Configure MxFS for CIFS with Matrix File Shares 14 Considerations for Using DFS When using DFS with MxFS for CIFS, you should be aware of the following: • We strongly recommend that domain-based DFS be used. Stand-alone DFS does not provide fault tolerance on root. • Shares created on a PSFS filesystem and deployed via DFS must be under the control of Matrix Server. Use only Matrix File Shares; they are designed to work properly with DFS and MxFS for CIFS.
Chapter 3: Configure MxFS for CIFS with Matrix File Shares 15 3. Configure all link targets with “manual replication” because you are using a shared filesystem. There is no need to replicate data between nodes in the same matrix sharing the same filesystem. However, some form of manual replication will be needed if you create link targets of this same DFS link on nodes outside of this matrix.
Chapter 3: Configure MxFS for CIFS with Matrix File Shares 16 [--enabled|--disabled] [--active|--inactive] Remove a Matrix File Share from a Server This procedure removes the selected server from the configuration of the Matrix File Share. Select the Matrix File Share on the Servers tab, right-click, and select Remove From Server. (On the Applications tab, right-click in the cell for the server from which the Matrix File Share is to be deleted.
4 Configure MxFS for CIFS with Virtual CIFS Servers Configuration Overview When CIFS is configured with Matrix Server and MxFS for CIFS, the data to be shared is stored on PSFS clustered filesystems. A set of Virtual File Shares, one per node in the matrix, is typically created for each filesystem. MxFS for CIFS uses “Virtual CIFS Servers” to provide CIFS access to the Virtual File Shares.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 18 CIFS clients use a Virtual CIFS Server to access file share data1 Ethernet VFS1 Primary VFS1 Backup1 VFS1 Backup2 file share file share file share data1 data1 data1 Matrix Server FC Fabric \data1 filesystem Disk Array If MxFS for CIFS detects that a Virtual File Share can no longer be accessed on the primary node, by default Matrix Server will fail over the associated Virtual CIFS Server to one of the designated backup nodes.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 19 Virtual CIFS Servers Providing Multiple Virtual File Shares Multiple Virtual File Shares can be associated with a Virtual CIFS Server, and multiple Virtual CIFS Servers can be supported on a physical node. Also, a node can host multiple active Virtual CIFS Servers while simultaneously serving as a backup for Virtual CIFS Servers that are active on other nodes.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 20 VFS1, VFS2, and VFS3. The Virtual File Share is configured identically on each Virtual CIFS Server. Node 1 is primary for Virtual CIFS Server VFS1, node 2 is primary for VFS2, and node 3 is primary for VFS3. Each node is a backup for the other Virtual CIFS Servers. CIFS clients connect to the load balancer (such as round-robin DNS or a hardware load balancer) and the clients are then routed to one of the nodes.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 21 Configuration Steps Perform the configuration in this order: • Create PSFS cluster filesystems to store the files that will be shared via CIFS. For each filesystem, you will need to assign a drive letter or path that will be used to access the filesystem. See the PolyServe Matrix Server Administration Guide for details about creating and configuring filesystems. • Create a Virtual CIFS Server, specifying a primary node.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 22 Create a Virtual CIFS Server To create a Virtual CIFS Server, from the PolyServe Management Console select Matrix > Add >Add Virtual CIFS Server. The Add Virtual CIFS Server window then appears. Address: Specify either the IP address or the DNS name that will be associated with this Virtual CIFS Server. The DNS name must already be configured in the DNS service. DNS/NetBIOS name: Use this field to specify a DNS/NetBIOS name.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 23 resources associated with the application can then be treated as a unit. You can specify a new application name, select an existing application name, or leave this field blank. However, if you do not assign a name, Matrix Server will use the IP address of the Virtual CIFS Server as the application name. Policy: The policy determines the failback action that the Virtual CIFS Server will take following a failover to a backup node.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 24 To add a Virtual CIFS Server from the command-line, use this command: mx vfs add [--policy autofailback|nofailback] [--application ] ALL_SERVERS | ... See the PolyServe Matrix Server Command Reference for more information about using this command.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 25 Virtual CIFS Server: This field contains the IP address of the Virtual CIFS Server that you selected. Share Name: Type a name for the Virtual File Share. NOTE: You can use the same share name for Virtual File Shares assigned to different Virtual CIFS Servers. However, if the Virtual CIFS Servers are configured on any of the same nodes, the Virtual File Shares must be configured identically.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 26 Path: Type the location of the Virtual File Share (such as y:\). This is typically the drive letter or path assigned to the PSFS filesystem that will be accessed via this share. Share subdirectories: Check this box to share all subdirectories that are one level under the specified path. CIFS clients can then attach directly to the subdirectories. (Subdirectories that are two or more levels below the path will not be shared.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 27 NOTE: The probe behavior of the Virtual File Share monitor differs from the behavior of the service monitors provided with Matrix Server. In Matrix Server, the monitor probes the associated service on all nodes on which it is configured. The Virtual File Share Monitor probes only on the node where the Virtual CIFS Server is active. When you click OK, the Virtual File Share appears on the Servers, Virtual Hosts, and Applications tabs.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 28 To add a Virtual File Share from the command line, use this command: mx vfs_share add --path [arguments] \\\ See the PolyServe Matrix Server Command Reference for more information about using this command. Virtual File Share Advanced Configuration You can customize the operation of the Virtual File Share monitor by using the Advanced options provided on the Add Virtual File Share window.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 29 Timeout and Failure Severity: This setting works with the Virtual CIFS Server policy (either AUTOFAILBACK or NOFAILBACK) to determine what happens when the monitor’s probe fails. The default policies (NOFAILBACK for the virtual host and AUTORECOVER for the monitor) cause the ClusterPulse process to fail over the Virtual CIFS Server to a backup node.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 30 AUTORECOVER. When the monitor probe fails, the ClusterPulse process automatically fails over the associated Virtual CIFS Server to a backup node. Failback occurs in accordance with the policy setting for the Virtual CIFS Server (either AUTOFAILBACK or NOFAILBACK). See“Create a Virtual CIFS Server” on page 22 for a description of these settings.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 31 Script Pathnames: The Virtual File Share monitor can optionally be configured with the following types of scripts: Recovery script. Runs after a monitor probe failure is detected, in an attempt to restore access to the Virtual File Share. Start script. Runs as the Virtual File Share is becoming active on a server. Stop script. Runs as the Virtual File Share is becoming inactive on a server.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 32 This behavior is necessary because the Start and Stop scripts are run to establish the desired start/stop activity, even though the service may actually have been started by something other than MxFS for CIFS. The Start and Stop scripts must also handle recovery from events that may cause them to run unsuccessfully. For example, if the system encounters a problem, the script will fail and exit non-zero.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 33 CONSIDER. This is the default value. Events are considered when the ClusterPulse process makes failover decisions. IGNORE. Events are ignored; script failures and DOWN status reports from the monitor will not cause failover. This is useful when the DOWN status or the action performed by the scripts is not critical, but is important enough that you want to keep a record of it.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 34 Linux Clients Linux clients can mount Virtual File Shares using the Virtual CIFS Server address. If a mount command fails with the message “Connection Refused,” retry the command with the port=445 option. Following is an example: # mount -t smbfs -o ‘username=Administrator,uid=Administrator,port=445’ //10.11.200.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 35 Delete a Virtual CIFS Server To remove a Virtual CIFS Server, select that Virtual CIFS Server on the PolyServe Management Console, right-click, and select Delete. You can also enter the following at the Command Prompt: mx vfs delete | Disable or Enable a Virtual CIFS Server By default, Virtual CIFS Servers are enabled.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 36 Virtual File Shares Modify the Configuration To change the configuration of a Virtual File Share, select that Virtual File Share on the Servers, Virtual Hosts, or Applications tab, right-click, and select Properties. You can then modify the configuration as necessary.
Chapter 4: Configure MxFS for CIFS with Virtual CIFS Servers 37 Display Status for a Virtual File Share Enter the following at the Command Prompt: mx vfs_share status [arguments] \\vfs>\ The arguments are: [--up|--down] [--primary|--backup] [--enabled|--disabled] [--active|--inactive] Delete a Virtual File Share To remove a Virtual File Share, select that Virtual File Share on the Servers, Virtual Hosts, or Applications tab, right-click, and select Delete.
Index A probe configuration 11 on Applications tab 12 overview 4 user limit 10 Applications tab Matrix File Share 12 Virtual CIFS Server 27 C N clients DNS name resolution 6 NetBIOS name resolution 6 operating systems 5 O D DFS, configure 13 DNS requirement for Virtual CIFS Servers 21 NetBIOS name resolution 6 offline caching Matrix File Share 11 Virtual File Share 26 R Recovery script 31 S G getting help 1 H HP NAS services website 2 storage web site 1 technical support 1 scripts event severi
Index 39 DNS/NetBIOS name 22 on Applications tab 27 overview 17 primary and backup interfaces 23 Virtual File Share add 24 configuration modify 36 delete 37 failover policy 28 monitor custom starting/stopping actions 32 disable 36 enable 36 event severity 32 scripts, configure 30 probe configuration 26 service priority 30 user limit 26 Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
