HP File System Extender (FSE) manual # mkdir /var/opt/fse/diskbuf/NewFileSystemMountPoint

Page 33

8.Manually mount the corresponding file systems for these four directories. You must use the device (logical volume) names from your actual LVM configuration:

#mount /dev/mapper/vg_fse-fsepart

#mount /dev/mapper/vg_fse-fsefri

#mount /dev/mapper/vg_fse-fselog

#mount /dev/mapper/vg_fse-fsediskbuf

9.In case of FSE disk buffer configuration with additional assigned file systems, follow the substeps for each additional file system:

a. Create the file system mount point:

#mkdir /var/opt/fse/diskbuf/NewFileSystemMountPoint

NewFileSystemMountPoint should be a unique subdirectory name.

b.Invoke the following command to retrieve the name of the device file. Use the symbolic link from the step 1 of section ”Creating file systems on top of LVM logical volumes”:

# ls -la /dev/vg_fse/fsediskbufNumber

lrwxrwxrwx 1 root root 25 Aug 17 09:12 /dev/vg_fse/fsediskbufNumber -> /dev/mapper/vg_fse-fsediskbufNumber

c.Add the appropriate entry to the file system table in the file /etc/fstab. When adding the entry, note that the device name in the first column corresponds to the device file that you retrieved in the previous substep:

/dev/mapper/vg_fse-fsediskbufNumber\

/var/opt/fse/diskbuf/NewFileSystemMountPoint \

ext3

defaults

1 2

NOTE: If you created an Ext2 file system, modify the above fstab entry accordingly.

d.Manually mount the corresponding file system. You must use the device (logical volume) name from your actual LVM configuration:

#mount /dev/mapper/vg_fse-fsediskbufNumber

10.Use the following command to check that all file systems have been mounted successfully, for example:

#cat /etc/mtab /dev/hda2 / ext3 rw 0 0 proc /proc proc rw 0 0

devpts /dev/pts devpts rw,mode=0620,gid=5 0 0 /dev/hda1 /boot ext3 rw 0 0

/dev/hda5 /usr ext3 rw 0 0 /dev/hda6 /var ext3 rw 0 0

/dev/vg_fse/fsevar /var/opt/fse ext3 rw 0 2

/dev/vg_fse/fsepart /var/opt/fse/part ext3 rw,data=journal 0 2 /dev/vg_fse/fsefri /var/opt/fse/fri ext3 rw 0 2 /dev/vg_fse/fselog /var/opt/fse/log ext3 rw 0 2 /dev/vg_fse/fsediskbuf /var/opt/fse/diskbuf ext3 rw 0 2 /dev/vg_fse/fsediskbuf1 /var/opt/fse/diskbuf1 ext3 rw 0 2

HP StorageWorks File System Extender Software installation guide for Linux 33

Image 33
Contents Part number T3648-96011 First edition October File System Extender Software installation guide for Linux Contents Troubleshooting Uninstalling FSE softwareGeneral problems Upgrading from previous FSE releasesInstallation problems FSE system maintenance releases and hot fixesIntegrating existing file systems in the FSE implementation Integrating existing file systemsPage About this guide Document conventions and symbolsIntended audience Related documentationHP technical support Subscription serviceHP web sites Documentation feedbackFSE implementation options Introduction and preparation basicsConsolidated implementation This chapter includes the following topicsConsolidated FSE implementation Distributed implementationMixed implementation Preparing file systems for FSE LicensingReasons for organizing file systems Organizing the file system layoutStorage space for FSE debug Estimating the size of file systems Formula for the expected size of Fast Recovery Information Formula for the expected HSM file system sizeFormula for the expected File System Catalog size Introduction and preparation basics Space requirements of FSE disk buffer Var/log/FSEDEBUG Tmp/FSEDEBUG Storage space for FSE debug filesInstalling the FSE Management Console on Installation overviewEtc/fstab Action Comments & where to find detailsPreparing the operating system environment Required operating system updatesPreparing the operating system Suse Linux Enterprise ServerPackage file name Rhel Package Package name in the rpm -qa output RhelPackage PackageName is not installed Installing Firebird SuperServer on an FSE server# rpm --install FirebirdSS-1.0.3.972-0.64IO.i386.rpm Verifying third-party packagesDisabling Acpi with Grub boot loader Disabling Acpi with Lilo boot loaderDisabling Acpi Page Preparing the operating system environment Preparing Logical Volume Manager LVM volumes Preparing file systems for FSEPreparing file systems Create and initialize LVM logical volume groups Create and initialize LVM logical volumes# pvcreate /dev/cciss/c0dp1 # pvcreate /dev/cciss/c0dp2 Create LVM logical volumes for HSM file systems # lvcreate -L 20G -n fsediskbufNumber vgfse# lvcreate -L 400G -n fsefs01 vgfsefs Creating file systems on top of LVM logical volumes Creating file systems for FSE databases and system files# mkfs.ext3 -b 4096 -N 1000000 /dev/vgfsefs/examplefs Command generates an output similar to the following Mounting file systems for FSE databases and system filesCreating HSM file systems Dev/mapper/vgfse-fsevar Var/opt/fse Ext3 defaults Create the four remaining directories# mount /dev/mapper/vgfse-fsevar # mkdir /var/opt/fse/diskbuf/NewFileSystemMountPoint Dev/mapper/vgfse-fsediskbufNumber\# mount /dev/mapper/vgfse-fsediskbufNumber Creating a symbolic link for debug files directory Installation overview Installing FSE softwareInstalling an FSE release PrerequisitesMonitoring the installation Installation procedureConsolidated PackagesPage Repairing the FSE software installation Verifying and repairing the installed FSE softwareDetermining the build number Server = fseserver.company.netConfiguring the FSE interprocess communication Preparing the FSE backup configuration fileModifying the Path environment variable Modifying the Ldlibrarypath environment variableNo external FSE clients or ordinary LAN connection Services.cfg Etc/opt/fse OmniORB.cfgHostname = fseserver.fsenet Server = fseserver.fsenet OmniORB.cfg file, configure the parameters in the sectionConfiguring communication on external FSE clients Server = fse-server1.company.comHostname = fseclient.fsenet Server = fseserver.fsenet # fse --start Starting the FSE implementationStarting FSE clients Starting the FSE serverBottom part of the output should match the following Consolidated FSE systemRestarting local FSE processes Restarting FSE processesFS Event Manager Mounting File SystemsChecking Firebird SuperServer Checking the status of a running FSE implementationExternal FSE client If the reported line isChecking the omniNames daemon Checking FSE ProcessesChecking Firebird SuperServer on Red Hat Enterprise Linux Configuring and starting Log Analyzer Configuring and starting HSM Health MonitorInstalling the FSE Management Console server Installing the FSE Management ConsoleInstalling the FSE Management Console client Automating the mounting of HSM file systemsPost-start script Configuring the post-start and pre-stop helper scriptsAdd the following line to the /etc/fstab file Dev/mapper/vgfsefs-fsefs01 Fse/fsefs01 Hsmfs noauto 0Example Pre-stop scriptInstalling FSE software Upgrading from previous FSE releases Upgrade overview# /etc/init.d/guisrv stop Shutting down the FSE implementation# cd /var/opt/fse/log # rm -f checkhsmfsfsc Var/opt/fse/log/checkhsmfsfscPartitionName.log# fsecheck --fsc-hsmfs PartitionName # hhm stopUpgrading the operating system on Linux hosts Command displays a report similar to the followingInstalling FSE release 3.4 software on the Linux FSE server Upgrading the Linux FSE serverAbove example, the value of DeviceFilePathname is Starting up the FSE server Starting OmniORB Naming Service FSE ServiceFor the above example, the command output is Upgrading the Windows FSE serverUpgrading Linux FSE clients Upgrading Windows FSE clients Installing FSE release 3.4 software on a Linux FSE clientStarting up a Linux FSE client Starting the HSM Health Monitor daemon on Linux systemsStarting the Log Analyzer service on Windows systems Starting the HSM Health Monitor service on Windows systemsUpgrading the FSE Management Console Starting the Log Analyzer daemons on Linux systemsVerifying availability of the configured FSE partitions # rpm -U fse-gui-client-3.4.0-Build.i386.rpmFsepartition --list Uninstalling FSE software Uninstalling FSE softwareUninstalling the FSE Management Console Uninstalling basic FSE softwareResource Manager Stopping # omninames --stop Stopping omniORB Naming Service# rpm -e `rpm -qa grep fse- grep -v fse-gui` Var/opt/fse/rmdbOpt/fse Entity Location directory Location FSE host typeUninstalling FSE software General problems TroubleshootingInstallation problems General problems, Installation problems,Adapter Line helps you determine if the adapter is connected to LANSystems, see the latest support matrices Page Troubleshooting Integrating existing file systems Integrating existing file systems in the FSE implementation# tune2fs -j /dev/fsesda/fs1 HSMFileSystemRoot # find * -type f xargs -n1 head -n0Integrating existing file systems in the FSE implementation FSE system maintenance releases FSE system maintenance releases and hot fixesFSE releases FSE hot fixesInstalling a system maintenance release FSE system maintenance releases and FSE hot fixesDetermining the installed system maintenance release Uninstalling a system maintenance releaseUninstalling a hot fix Determining the installed hot fixCommand will display an output similar to the following # fsesystem --versionFSE system maintenance releases and hot fixes Media pool FSE media pool GlossaryConfiguration file FSE configuration file templateExternal client FSE external client File System Catalog FSCOwn deletion policy Needs cleaning or servicingDisk buffer See media duplicationSee recovery FSE recovery See recovery FSE recovery, recovery jobAlso Data Location Catalog DLC and Name Space Catalog NSC Mode LAM It, you must use forced initialization JobFSE job See Medium Auxiliary Memory MAM MediumRetention time Library Offline mediumOnline medium Set to unusableRecovery job An FSE users request with the fserecover commandInstallPath%\var\rmdb directory on Windows platform Recall, recall jobSee media pool FSE media pool FSE implementationUltrium Is set by enabling the drive with the fsedrive commandSee LTO Ultrium Unusable mediumPage Index Ldlibrarypath environment variable Subscribers Choice, HP 8 Suse Linux Enterprise Server Web sites HP HP Subscribers Choice for Business
Related manuals
Manual 99 pages 2.23 Kb Manual 115 pages 39.56 Kb Manual 328 pages 27.8 Kb Manual 26 pages 22.37 Kb

File System Extender (FSE) specifications

HP File System Extender (FSE) is a sophisticated solution designed to optimize data storage management for enterprises that deal with large volumes of unstructured data. This technology addresses the challenges of data growth and the need for effective data retention strategies, enabling organizations to store and manage their information more efficiently.

One of the main features of HP FSE is its ability to intelligently migrate data between primary and secondary storage. By utilizing policies that determine when to move infrequently accessed files to lower-cost storage environments, FSE helps reduce the strain on primary storage systems and saves on costs associated with high-performance storage solutions. This tiered approach to data management ensures that organizations can access the data they need quickly while still maintaining an efficient overall storage architecture.

Another notable characteristic of HP FSE is its seamless integration with existing storage infrastructures. The solution works with a variety of storage systems, allowing organizations to utilize their current investments without the need for significant changes to their infrastructure. This interoperability is powered by advanced technologies that facilitate data migration and retrieval, ensuring a smooth transition for organizations looking to optimize their storage strategies.

Additionally, HP FSE is equipped with robust reporting and analytics capabilities. This functionality provides organizations with insights into their storage usage, helping them understand data patterns and optimize their storage environments accordingly. By having visibility into which files are accessed most frequently and which are rarely used, organizations can make informed decisions on data retention policies and storage management.

Security is paramount in data management, and HP FSE addresses this concern by implementing advanced data protection features. This includes data encryption, secure access controls, and compliance with industry regulations, ensuring that sensitive information is safeguarded throughout its lifecycle.

Overall, HP File System Extender is a comprehensive data storage solution that combines intelligent data management, seamless integration, insightful analytics, and robust security features. By leveraging these capabilities, organizations can efficiently manage their unstructured data, lower costs, and enhance operational efficiency, making it an invaluable tool in today’s data-driven landscape.