Release Notes HP StorageWorks File System Extender 3.
Legal and notice information © Copyright 2005 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Contents Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . .
Limited symbolic link support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File size limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Append-only and immutable files cannot be released . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pathname length limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this guide This guide provides information about: • Preparing your environment prior to installing software • Installing the software • Verifying successful installation and troubleshooting problems Intended audience This guide is intended for use by system administrators who are experienced with the following (depending on the type of installation): • SUSE LINUX Enterprise Server 8 (SLES) or Red Hat Enterprise Linux 3 (RHEL) operating systems (abbreviated to Linux throughout this guide) NOTE: You mu
Prerequisites Prerequisites for setting up product include: Software requirements For information on software requirements, see the FSE Release Notes and the FSE Installation Guide. Hardware requirements For information on hardware requirements, see the FSE Release Notes. Document conventions and symbols Document conventions Table 1 Convention Element Medium blue text: Figure 1 Cross-reference links and e-mail addresses Medium blue, underlined text (http://www.hp.
HP technical support Telephone numbers for worldwide technical support are listed on the HP support web site: http://www.hp.com/support/.
1 Supported hardware and software This chapter provides information about supported hardware configurations, supported operating systems, and supported third-party software. Hardware requirements FSE server software runs on systems with Intel i386 architecture. FSE client software runs on systems with Intel i386. FSE can be configured in different implementations: • consolidated implementation: an FSE server and an FSE client are integrated on the same host.
Array type Comments HP StorageWorks Modular Smart Array 30 SCSI drives HP StorageWorks XP12000 Disk Array FC, FICON, or ESCON interconnection The following tape drives are supported.
• 2.4.21-20.ELsmp Red Hat Linux kernel that supports symmetric multiprocessing (multiple processor machines) Windows platform FSE software, including the server and client components of the FSE Management Console, runs on the following Windows operating system families: • Windows 2000 Server, updated with Windows 2000 Service Pack 3 or later • Windows Server 2003, Enterprise Edition With Windows platform, the supported processor architecture is Intel Pentium.
Supported third-party software Windows platform On Windows systems with installed FSE software, the following third-party anti-virus software can be used: • McAfee VirusScan Enterprise, version 8.0i • Sophos Anti-Virus, version 3.87 To prevent data corruption, you must exclude certain directories on the FSE software installation tree structure from being scanned for viruses.
2 New features Enhanced robustness FSE 3.2 introduces several changes in the operation of FSE server to enhance the robustness of FSE operations. The changes enable the FSE server to detect anomalies on media and to prevent improper operation which could lead to data loss.
New features
3 Recommendations This chapter includes recommendations that help improving performance and minimizing problems in the FSE implementation. It contains the following sections: • General recommendations, page 15 • Linux-specific recommendations, page 17 • Windows-specific recommendations, page 18 General recommendations Keeping the FSC and HSMDB journals small The journals of File System Catalog (FSC) and Hierarchical Storage Manager (HSMDB) can grow quite large with daily FSE usage.
FSE process clean-up may be noticed when working with FSE commands. After an FSE command completes its task, it returns control to the command prompt after a short delay. This is because the command, after termination, leaves its connection open until the omniORB thread terminates it. omniORB scans for idle connections at regular intervals. A shorter interval will result in a shorter delay after the FSE command termination. To shorten this interval, add the following line to the file omniORB.cfg.
The value of %InstallPath% depends on the choice made in the FSE installation process. It defaults to C:\Program Files\Hewlett-Packard\FSE. 4. Modify the file omniORB.cfg with the following values: scanGranularity=1 inConScanPeriod=15 outConScanPeriod=10 If omniORB.cfg is not yet present in its directory, copy its template to this directory and add the above lines to it. Linux specific omniORB.cfg is located in the directory /etc/opt/fse, and its template is located in the directory /opt/fse/newconfig.
Windows-specific recommendations Improving performance of the FSE-Samba integration You can improve performance of clients running on Windows 2000 systems using Samba shares on the HSM file systems by modifying the timing parameters of the Workstation Service (formerly LAN Manager), depending on the particular environment load and usage policy. These parameters are described in Microsoft Knowledge Base articles Q102981 and Q102067.
4 Limitations This chapter lists known limitations of the current FSE release, and where appropriate, provides possible solutions. It contains the following sections: • Common limitations, page 19 • Linux-specific limitations, page 20 • Windows-specific limitations, page 23 Common limitations FSE client–server connection limitation The FSE implementation does not support a proxy server or a firewall between the FSE client and the FSE server.
The following is an example of an error message that may be written to the FSE error log file after a bus reset and the consequent FSE tape media rewind: CRITICAL ERROR: Internal error. Contact support. (5: MAJOR INTERNAL ERROR: Data corruption detected. 'Counted medium position (395405) is different from actual (12897). Job: 20050607000206 Medium/volume: 000391/1'). Other messages that can be displayed are: (5. MAJOR INTERNAL ERROR: Data corruption detected. 'Data loss detected. Medium was overwritten.
• sockets • pipes Consequently, these files cannot be created on an HSM file system. Directories with sticky bit not supported The FSE implementation does not support handling of “sticky directories”, that is, directories with the sticky bit set. Such directories cannot be copied to HSM file systems and the sticky bit cannot be applied to existing directories on HSM file systems.
Limitations of CIFS protocol (Samba) usage with FSE implementation These limitations apply to FSE users that are accessing HSM file systems located on Linux systems using the CIFS protocol and Samba servers. Samba servers are mostly used by Windows clients. File transfer blockage between Samba client and server Samba client processes provide only one thread per session.
Windows NTFS Alternate Data Streams are not supported through Samba Windows NTFS Alternate Data Streams are not supported on Ext2/Ext3 file systems and consequently neither on HSM file systems. Therefore, they cannot be migrated to FSE media.
\Explorer \BitBucket: NukeOnDelete [REG_DWORD] = 1 NOTE: This registry key affects the whole system, so once it is modified, the Recycle Bin is also not available for other disk volumes. Pointing to files in WinZip and Total Commander triggers recalls With WinZip installed, dragging the mouse over an offline .zip file in Windows Explorer triggers a recall of the file.
5 Known issues and workarounds Description After starting FSE daemons with the command fse --start, the following error appears in the FSE error log: ERROR: *** NO OWNER set for INO... *** File must be migrated again! fileID= file / Explanation While FSE daemons on a particular FSE client are stopped and modifications are made on an HSM file system located on the client, it may happen that a file system event is lost.
Known issues and workarounds
