HP File System Extender (FSE) manual FSE implementation, See media pool FSE media pool

Page 86

restore

A process that recreates complete and consistent state of the FSE server at a particular point in

(FSE restore)

time, using data from the backup image. Restore is required after disaster causes data on the

 

FSE server to be damaged or lost.

restore log

A file that stores information about activity of the FSE restore process. FSE restore log is named

(FSE restore log)

restore.log and located in the directory /var/opt/fse/log (on Linux platform) or in the

 

directory %InstallPath%\var\log (on Windows platform).

retention time

A defined period of time for files on the release candidate list during which a file is kept online

 

(after it was migrated or recalled) before it is released. The retention time is reset when any of

 

following changes: file contents, standard attributes, time stamps, permissions, or ownership.

Samba

Software that allows a Linux server to act as a file server to Windows clients. A Samba server

 

must be running on the machine that hosts the HSM file system to allow Samba clients to access

 

the HSM file system. See also ”CIFS”.

secondary storage

A space on FSE media controlled by the FSE implementation. Secondary storage space

space

transparently extends primary storage space, which is the HSM file system. It has to be

 

configured, formatted, and initialized before it can be used.

server

A set of FSE daemons (services) that are responsible for managing the configured FSE

(FSE server)

resources, accepting and executing user commands, executing all types of FSE jobs, and

 

monitoring and operating the FSE implementation. These daemons (services) are: Resource

 

Manager, Management Interface, Partition Manager, Library Agent, and Back End Agent.

Service

An FSE daemon (service) which launches other FSE daemons (services) and agents. The Service

 

process name is fse-svc.

shared library

A proprietary dynamically loaded library, included in the FSE package, that is used by the FSE

(FSE shared library)

processes.

slack space

Space on FSE media that is occupied by the migrated file generations that were treated as

(FSE slack space)

obsolete by the FSE reorganizational scan job. The FSE medium volumes with a relatively high

 

slack space percentage should eventually be reorganized and reused.

slot

A physical place in the FSE library that holds a single FSE tape medium when it is not loaded

(FSE slot)

in an FSE drive. FSE slots have their entries in the Resource Management Database.

SMR

See ”system maintenance release (FSE system maintenance release)”.

software

The programs and data files that are included in the FSE package. Once installed, they actively

(FSE software)

control the FSE implementation and provide functionality to its users. See also ”implementation

 

(FSE implementation)”.

system file

A temporary file, created by the FSE software, which contains information about the current

(FSE system file)

status of the FSE implementation. FSE system files are Fast Recovery Information, File System

 

Catalog transaction logs, Hierarchical Storage Manager lists, and files stored in the FSE disk

 

buffer.

system maintenance

A complete set of rebuilt FSE installation packages that include updates from several FSE hot

release

fixes and other improvements, which can be installed over initial FSE release software. System

(FSE system

maintenance release can be used to update any FSE implementation with an appropriate FSE

maintenance release) release version installed.

tape media pool

See ”media pool (FSE media pool)”.

(FSE tape media pool)

 

86

Image 86
Contents Part number T3648-96011 First edition October File System Extender Software installation guide for Linux Contents General problems Uninstalling FSE softwareTroubleshooting Upgrading from previous FSE releasesIntegrating existing file systems in the FSE implementation FSE system maintenance releases and hot fixesInstallation problems Integrating existing file systemsPage Intended audience Document conventions and symbolsAbout this guide Related documentationHP web sites Subscription serviceHP technical support Documentation feedbackConsolidated implementation Introduction and preparation basicsFSE implementation options This chapter includes the following topicsDistributed implementation Consolidated FSE implementationMixed implementation Licensing Preparing file systems for FSEStorage space for FSE debug Reasons for organizing file systemsOrganizing the file system layout Estimating the size of file systems Formula for the expected File System Catalog size Formula for the expected size of Fast Recovery InformationFormula for the expected HSM file system size Introduction and preparation basics Space requirements of FSE disk buffer Storage space for FSE debug files Var/log/FSEDEBUG Tmp/FSEDEBUGInstallation overview Installing the FSE Management Console onAction Comments & where to find details Etc/fstabPreparing the operating system Required operating system updatesPreparing the operating system environment Suse Linux Enterprise ServerPackage Package name in the rpm -qa output Rhel Package file name Rhel# rpm --install FirebirdSS-1.0.3.972-0.64IO.i386.rpm Installing Firebird SuperServer on an FSE serverPackage PackageName is not installed Verifying third-party packagesDisabling Acpi Disabling Acpi with Grub boot loaderDisabling Acpi with Lilo boot loader Page Preparing the operating system environment Preparing file systems Preparing Logical Volume Manager LVM volumesPreparing file systems for FSE # pvcreate /dev/cciss/c0dp1 # pvcreate /dev/cciss/c0dp2 Create and initialize LVM logical volume groupsCreate and initialize LVM logical volumes # lvcreate -L 400G -n fsefs01 vgfsefs Create LVM logical volumes for HSM file systems# lvcreate -L 20G -n fsediskbufNumber vgfse # mkfs.ext3 -b 4096 -N 1000000 /dev/vgfsefs/examplefs Creating file systems on top of LVM logical volumesCreating file systems for FSE databases and system files Creating HSM file systems Command generates an output similar to the followingMounting file systems for FSE databases and system files # mount /dev/mapper/vgfse-fsevar Dev/mapper/vgfse-fsevar Var/opt/fse Ext3 defaultsCreate the four remaining directories # mount /dev/mapper/vgfse-fsediskbufNumber # mkdir /var/opt/fse/diskbuf/NewFileSystemMountPointDev/mapper/vgfse-fsediskbufNumber\ Creating a symbolic link for debug files directory Installing an FSE release Installing FSE softwareInstallation overview PrerequisitesConsolidated Installation procedureMonitoring the installation PackagesPage Determining the build number Verifying and repairing the installed FSE softwareRepairing the FSE software installation Server = fseserver.company.netModifying the Path environment variable Preparing the FSE backup configuration fileConfiguring the FSE interprocess communication Modifying the Ldlibrarypath environment variableServices.cfg Etc/opt/fse OmniORB.cfg No external FSE clients or ordinary LAN connectionOmniORB.cfg file, configure the parameters in the section Hostname = fseserver.fsenet Server = fseserver.fsenetHostname = fseclient.fsenet Server = fseserver.fsenet Configuring communication on external FSE clientsServer = fse-server1.company.com Starting the FSE implementation # fse --startBottom part of the output should match the following Starting the FSE serverStarting FSE clients Consolidated FSE systemFS Event Manager Mounting Restarting FSE processesRestarting local FSE processes File SystemsExternal FSE client Checking the status of a running FSE implementationChecking Firebird SuperServer If the reported line isChecking Firebird SuperServer on Red Hat Enterprise Linux Checking the omniNames daemonChecking FSE Processes Configuring and starting HSM Health Monitor Configuring and starting Log AnalyzerInstalling the FSE Management Console client Installing the FSE Management ConsoleInstalling the FSE Management Console server Automating the mounting of HSM file systemsAdd the following line to the /etc/fstab file Configuring the post-start and pre-stop helper scriptsPost-start script Dev/mapper/vgfsefs-fsefs01 Fse/fsefs01 Hsmfs noauto 0Pre-stop script ExampleInstalling FSE software Upgrade overview Upgrading from previous FSE releasesShutting down the FSE implementation # /etc/init.d/guisrv stop# fsecheck --fsc-hsmfs PartitionName Var/opt/fse/log/checkhsmfsfscPartitionName.log# cd /var/opt/fse/log # rm -f checkhsmfsfsc # hhm stopCommand displays a report similar to the following Upgrading the operating system on Linux hostsAbove example, the value of DeviceFilePathname is Installing FSE release 3.4 software on the Linux FSE serverUpgrading the Linux FSE server Starting OmniORB Naming Service FSE Service Starting up the FSE serverUpgrading Linux FSE clients For the above example, the command output isUpgrading the Windows FSE server Starting up a Linux FSE client Installing FSE release 3.4 software on a Linux FSE clientUpgrading Windows FSE clients Starting the HSM Health Monitor daemon on Linux systemsUpgrading the FSE Management Console Starting the HSM Health Monitor service on Windows systemsStarting the Log Analyzer service on Windows systems Starting the Log Analyzer daemons on Linux systemsFsepartition --list Verifying availability of the configured FSE partitions# rpm -U fse-gui-client-3.4.0-Build.i386.rpm Uninstalling the FSE Management Console Uninstalling FSE softwareUninstalling FSE software Uninstalling basic FSE software# rpm -e `rpm -qa grep fse- grep -v fse-gui` # omninames --stop Stopping omniORB Naming ServiceResource Manager Stopping Var/opt/fse/rmdbEntity Location directory Location FSE host type Opt/fseUninstalling FSE software Installation problems TroubleshootingGeneral problems General problems, Installation problems,Systems, see the latest support matrices AdapterLine helps you determine if the adapter is connected to LAN Page Troubleshooting # tune2fs -j /dev/fsesda/fs1 Integrating existing file systems in the FSE implementationIntegrating existing file systems HSMFileSystemRoot # find * -type f xargs -n1 head -n0Integrating existing file systems in the FSE implementation FSE releases FSE system maintenance releases and hot fixesFSE system maintenance releases FSE hot fixesDetermining the installed system maintenance release FSE system maintenance releases and FSE hot fixesInstalling a system maintenance release Uninstalling a system maintenance releaseCommand will display an output similar to the following Determining the installed hot fixUninstalling a hot fix # fsesystem --versionFSE system maintenance releases and hot fixes Glossary Media pool FSE media poolExternal client FSE external client FSE configuration file templateConfiguration file File System Catalog FSCDisk buffer Needs cleaning or servicingOwn deletion policy See media duplicationAlso Data Location Catalog DLC and Name Space Catalog NSC See recovery FSE recoverySee recovery FSE recovery, recovery job Mode LAM FSE job It, you must use forced initializationJob Retention time See Medium Auxiliary Memory MAM Medium Online medium Offline mediumLibrary Set to unusableInstallPath%\var\rmdb directory on Windows platform An FSE users request with the fserecover commandRecovery job Recall, recall jobFSE implementation See media pool FSE media poolSee LTO Ultrium Is set by enabling the drive with the fsedrive commandUltrium 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