HP File System Extender (FSE) manual Recall, recall job, Recovery job, Also release, Database Rmdb

Page 317

recall, recall job

A process, executed by the Partition Manager, that copies the file contents from the FSE media

 

to the HSM file system. Once the process is completed, the offline file becomes online again. Its

 

file entry is then added to the release candidate list.

recovery

A process, executed by the Partition Manager, that recovers the HSM file system or the File

(FSE recovery)

System Catalog (FSC) without requiring FSE backup copies. The HSM file system is recreated

 

from the Name Space Catalog (NSC), while the FSC is recreated either from Fast Recovery

 

Information (FRI) or from migrated metadata. FSE recovery can be used as a fallback if restore

 

of FSE is not possible due to missing FSE backup data. A recovery job is triggered explicitly on

 

an FSE user's request with the fserecover command.

recovery job

See ”recovery (FSE recovery)”.

recycled medium

An FSE medium volume from which all selected data was copied to another medium volume

volume

during media reorganization. The data on recycled medium volumes can no longer be

 

retrieved, but the storage space on such volumes can be reused for new migrated data.

redundant data copy A process in FSE that recreates a copy of a file set that has become unreadable, most probably

recreation because the FSE medium to which it was migrated is damaged. The process recreates the damaged data copy using copies of the same data that were migrated to other FSE media pools. Therefore, the main prerequisite to execute this process is a multiple media pool configuration of the corresponding FSE partition. A redundant data copy recreation process is triggered manually by the FSE administrator.

regular release

Release of files on an HSM file system that are on the release candidate list and meet the

 

predefined criteria, triggered when the high watermark of usage is reached on the HSM file

 

system. The process is stopped when the low watermark on the HSM file system is reached. See

 

also ”release”.

release

A process that usually follows a migration or recall, executed by the Hierarchical Storage

 

Manager. This process removes the file data from the HSM file system, leaving only the file

 

header. Release is triggered by the Partition Manager according to the defined watermarks.

 

After release, files are offline and their file entries are removed from the release candidate list.

release candidate

An online file that is scheduled for release and that has either been migrated or was brought

 

online by recall.

release candidate list A list of online files that have already been migrated or that have recently been recalled and are waiting to be released. The list is maintained by the Hierarchical Storage Manager.

release policy

A set of rules by which the release process for files on a release candidate list is initiated.

 

Configuration parameters for the release policy are specified in the FSE partition configuration

 

file. Each FSE partition has its own release policy.

resource

Either an FSE partition, FSE library, FSE drive, FSE media pool, or FSE medium including

(FSE resource)

medium volumes. Each FSE resource is configured using an FSE configuration file and has an

 

entry in the Resource Management Database.

Resource

A database with records of all configured FSE resources. It contains all relevant resource

Management

information, such as configuration parameters, resource characteristics, current status, usage

Database (RMDB)

statistics, and relations to other resources. The Resource Management Database is located in

 

the directory /var/opt/fse/rmdb (on Linux platform) or in the directory

 

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

Resource Manager

An FSE daemon (service) responsible for managing data in the Resource Management

(RM)

Database, allocating and releasing FSE resources and providing resource information to other

 

FSE daemons (services) and processes. The Resource Manager process name is fse-rm.

HP StorageWorks File System Extender Software user guide 317

Image 317
Contents HP StorageWorks File System Extender Software user guide File System Extender Software user guide Contents Migration, release, recall, and deletion Managing mediaTroubleshooting Backup, restore, and recoveryIntroduction FSE startup and shut-down problems Monitoring and maintaining FSEDirectory layout B FSE configuration templates Intended audience Document conventions and symbolsRelated documentation Document conventions Convention ElementHP technical support Subscription serviceHP web sites Documentation feedbackWhat is FSE?, FSE basics, FSE architecture, What is FSE?FSE basics Infinite file systemLibrary tape compatibility Automatic error detectionAutomatic detection of low storage space NFS and Cifs supportMigration FSE architectureFSE operations \Program Files\Hewlett-Packard\FSE ReleaseRecall Deletion FSE componentsHSM file system FSE partitionFSE medium FSE media poolFSE library File System CatalogConsolidated implementation FSE implementation optionsFSE drive Distributed implementation Page FSE implementation with multiple libraries FSE daemons services and FSE agentsFse-hsm Fse-fsevtmgrFse-svc Fse.exeFse-bea FSE utility daemons servicesFse-la-s FSE user interfaces FSE command-line interfaceIntroduction to the FSE command-line interface Remove,--list,--show,--status, and so on FSE command listFSE Management Console Accessing the online FSE command-line referenceFSE command Description FSE Management Console client FSE Management Console serverConfiguring the FSE Management Console InstallPath%\var\cfg\gui\guisrv.users.db InstallPath%\var\log\guisrv.logInstallPath%\var\log\fse.log Var/opt/fse/log/guisrv.logParameter Description Configuring the logging levelStarting and stopping the FSE Management Console Example of a configured FSE Management Console loggingStarting and stopping the FSE Management Console server Debuglevel = -d4 -DAll Debuglevel = -dTrc -DAllD# /opt/fse/lbin/guisrv Options Starting the FSE Management Console server on Linux systems# /etc/init.d/guisrv start # /etc/init.d/guisrv stop Stopping the FSE Management Console server on Linux systemsHP StorageWorks File System Extender Software user guide InstallPath%\binguisrv -F InstallPath%\binguisrv Options\cd %InstallPath%\bin Starting and stopping the FSE Management Console client \Documents and Settings\Username\Application Data\guicltrcStarting the FSE Management Console client on Linux systems # export DISPLAY=fsemcclient0# guiclt Options Stopping the FSE Management Console client on Linux systemsPage Before you start Configuring FSEFSE configuration file elements Configuration basicsConfiguration files Templates Configuration DatabaseResource Management Database Configuring a new FSE resourceVar/opt/fse/cfg Var/opt/fse/rmdbFsepartition --list --detail Modifying the configuration of an FSE resourceFsepartition --show Partition01 MyFile Fsepartition --modify Partition01 MyFileFsepartition --show PartitionName --history Operational modes of the FSE Management Console client# /opt/fse/bin/guiclt Choosing online operational modeGraphical user interface overview Choosing offline operational modeGUI layout Graphical user interface layoutSystemName Object treePage Configuring FSE HP StorageWorks File System Extender Software user guide Configuring FSE HP StorageWorks File System Extender Software user guide Configuration dialog box Menu bar contains several menus Menu barNew Connection Menu item action Applicable objects Action description View is displayed ToolbarStatus bar Open Recovery modeUnusable UnreliableManaging FSE Management Console users FSE Management Console usersKeyboard shortcuts FSE Management Console user properties Configuration procedureConfiguring an FSE resource using an FSE user interface About Scsi identification Overview of the configuration procedurePhase 1 configuring FSE libraries and FSE drives Library and drive configuration procedure Name Library MediaFamily Opt/fse/newconfig. Windows specificName Host ControlDevice LibType MediaFamily Slots Fselibrary --addLibraryCfgFileName DriveIndex Capabilities Host ControlDeviceExample of a library configuration file Library and tape drive configuration examples= LTO # AIT Sony AIT Family # LTO LTO Ultrium MediaFamilyExample of an LTO Ultrium tape drive configuration file Example of an LTO Ultrium Worm tape drive configuration file Name Phase 2 configuring FSE media poolsName MediaFamily PoolType BlockSize VolumeSize Phase 3 preparing HSM file systemsPreparing HSM file systems on the Linux platform Creating and preparing new HSM file systemsPreparing HSM file systems on the Windows platform \mkdir hsmfsfolderIntegrating existing file systems on the Windows platform Integrating existing file systems in the FSE implementationIntegrating existing file systems on the Linux platform Configuring a regular FSE partition on the Linux platform Phase 4 configuring FSE partitionsFsepartition --status PartitionName Configuring an FSE partition Click OK Configuring a regular FSE partition on the Windows platform\\?\Volumef6f3e1b6-b2ac-11d7-9c99-00b0d02fadef\ Fsepartition --addPartitionCfgFileName Examples of configuration files for Worm FSE partitions Configuring a Worm FSE partitionFselibrary --update-inventory LibraryName --rescan Phase 5 preparing FSE mediaFsemedium --format Barcode Fsemedium --format Barcode --forceFsemedium --init Barcode --force For forced initialization use the following commandFsemedium --init Barcode Fsesystem --status Phase 6 mounting HSM file systemsMounting HSM file systems on the Linux platform Command generates an output similar to the following \\?\VolumeVolumeGUID\ Reconfiguring FSE interprocess communicationMounting HSM file systems on the Windows platform \fsepartition --listServices.cfg Etc/opt/fse Reconfiguration procedureVar/opt/fse/omniorb. Windows specific OmniORB.cfg Etc/opt/fsePrivate network connection Ordinary LAN connectionServer = fse-server1.company.com Hostname = fseserver.fsenet Server = fseserver.fsenetServices.cfg and omniORB.cfg files OmniORB.cfg file, configure the parameters in the sectionServices.cfg file Hostname = fseclient.fsenet Server = fseserver.fsenet Reconfiguring communication on external Linux FSE clientsReconfiguring communication on external Windows FSE clients Changing the IP address of an FSE host Configuring FSE Introduction Media pool types and their characteristicsFSE media pools Introduction, FSE media pools, FSE media,MyConfiguration. Linux specific Configuring a media pool# Regular Regular media pool for FSE partition LTOSysVolLocation = None SizeOfSysVol = 0MB Example of an LTO Worm media pool configuration fileFsepool --list --detail Determining the configured media poolsExample of a disk media pool configuration file Managing media Excerpt from the fsepool --list --detail output Checking the status of a particular media poolExcerpt from the fsepool --list output Excerpt from the fsepartition --status output FSE medium volumesFSE media Disk media FSE media typesLTO Ultrium 3 Worm Disk mediaVar/opt/fse/dm/dm000001 Var/opt/fse/dm/dm000002 Local and remote file systems as disk mediaCapacity disk `-- dm000001 Disk media specificsMnt/diskmedium linuxhost.company.comrw,nosquashroot Formatting media Adding media to an FSE media poolMedium is initialized using the following command Medium is formatted using the following commandInitializing media Skipping media formattingDuplicating media How it works Procedure for duplicating mediaPrerequisites LTO 1 100 GiB * 2 = 200 GiBLTO 2 200 GiB * 2 = 400 GiB LTO 3 400 GiB * 2 = 800 GiB Normal duplicationForced duplication Limitation Reorganizing mediaMedia reorganization process Enabled/mounted Fsemedium --list Barcode --volumeExceptions to the reorganizational rule Media reorganization parametersBoundary migration date and time parameter Number of latest generations parameterScanning media for obsolete data Example command outputDisplaying the FSE media pool-based statistics Meaning of the columns is the followingDisplaying the FSE media-based statistics Job to the command shell for --no-monitoroptionRunning the media reorganization job Fsemedium --list Reusing the recycled medium volumesAn example output is the following 052002 Data 5949 Open, scanned Empty System 1019 Recreating redundant copies of migrated dataRedundant copy recreation process Media Pool Fsemedium --copy-contents Barcode --no-monitor Command output will be similar to the followingDetermining the unusable media Starting redundant copy recreationFsefile -M Filename Resolving situations with no alternative migrated copiesChecking the status of media Example output of the fsemedium --list --detail command Example output of the fsemedium --list commandPoolLTO Open LiblibLTO3 000046 PoolLTO Open LiblibLTO5 000116Status of the medium can be one of the following Changing the condition status of mediaChecking the status of a particular medium Recreating Fast Recovery Information from media Closing medium volumesPreventing writing to an FSE medium Preventing reading from and writing to an FSE mediumFsemedium --recreate-fri Barcode --volume VolumeNumber Fselibrary --update-inventory command for this purposeRemoving FSE media Fsemedium --remove BarcodeManaging media How does FSE function? FSE operation basicsPolicies HSM listsFSE disk buffer Storage space allocation in an extended FSE disk buffer Hierarchical Storage Manager listsChanges of states of files under FSE PoliciesMigration What is a retried migration?Migration policy parameters Minimum file age for migration MinFileAgeMaximum wait time for migration MaxWaitTime Minimum wait time for migration MinWaitTimeMinimum number of files for migration MinNumMigFiles Maximum number of files for migration MaxNumMigFilesRelease Default migration policyExample situations that trigger migration WatermarksReaching the critical watermark on an HSM file system High watermarkLow watermark Exclusion from releaseLimitations Considerations before configuring exclusion from releaseFilename pattern conventions Special pattern-matching characters Release policy parameters Migration retention time MigRetentionTime Example situations that trigger releaseRecall retention time RecallRetentionTime Minimum file size for release MinFileSizeRecall parameters Default release policyRecall Recall timeout RecallTimeout Default recall policyDeletion Automatic deletion processDirectory paths Path Deletion policy parametersFile expiration time FileExpiration Default deletion policy Examples of a configured deletion policyStarting the deletion job Resource allocationRecalling deleted files Resource allocation conceptsSeveral allocation parameters Central FSE resource managerMedia selection by media location System allocation and job priority policy parameters System allocation and job priority policyJob priorities ThresholdJobCount = 3/2 * MaxNumDrivesTime step TimeStep Resource allocation threshold ResourceAllocationThresholdPartition allocation and job priority policy parameters Partition allocation and job priority policyRecovery priority RecoveryPriority Maximum number of drives for recovery MaxNumDrivesRecoveryMaintenance priority MaintenancePriority Default partition allocation and job priority policyPriority calculation Administrative and backup job priority calculationExample of resource allocation Multiple copyingParallel copying Sequential copying HSM file system access modesLimited Access Mode LAM and Full Access Mode FAM HP StorageWorks File System Extender Software user guide Migration, release, recall, and deletion About monitoring and maintaining in FSE Procedures in this chapter provide instructions forMonitoring general FSE implementation status Number of running jobsManaging FSE partitions Example output of the fsesystem --status commandMonitoring FSE partition status Host and mount point of the belonging HSM file systemDisplaying the status of an FSE partition Disabling an FSE partition Example output of the fsepartition --status commandWindows specific Invoke the following command To enable an FSE partition, do the followingEnabling an FSE partition Removing an FSE partitionRetrieving detailed information for an FSE partition Switching the access mode for an HSM file systemSwitching to Full Access Mode Switching to Limited Access ModeLimited Access Mode error messages Monitoring FSE jobsFsejob --list --maint PartitionName --detail Example output of the fsejob --list commandExample output of the fsejob --list --detail command Fsejob --status JobID Displaying the status of a particular FSE jobRecalling older generations of a file Example output of the fsejob --status commandExample output of the fsefile --history command Example of recall by date Recalling sets of files in an efficient wayExample of recall by file migration ID Example of recall by file ID instead of filenameEfficient recall invocation Command fsefile --recall --ifLogging file recalls 512MBc, and 512MBdManaging FSE recall jobs Example excerpt from the FSE error log fileRetrieving detailed information Fselibrary --list Fsemedium --list --volumeFsedrive --list Fsepool --listName Drv01 Family ScsiAc3050b1-a838-458e-9a21-d3d3429cade9 UsageCount 137 Capabilities Key Name Drv02 FamilyPool Pool01 47b5fddc-03f7-4b80-8dab-5d2f6fe18cc1 33d4ef52-7ec8-4926-97f9-909edfe66c41HP StorageWorks File System Extender Software user guide 1acf6a41-a23f-4836-9e4d-539d31ad572f Barcode 000009 VolNumCfe954e0-21bb-428b-84fa-076754539f76 Eca50ba5-f068-4650-a587-945fcffda2878920cdd9-57ee-4f2e-a09a-d701249c6434 B8e4d73b-890c-41d0-bb20-eefe19d3f057Partition Part01 LastVer 1970/01/01 ValidData TotalData583 Bfca4697-a1e0-4881-ba12-953acbb72a02Monitoring and maintaining FSE HP StorageWorks File System Extender Software user guide Extending storage space of FSE disk buffer Benefits of extended FSE disk buffer How to extend the FSE disk buffer?Removing a file system from the FSE disk buffer Checking the consistency of the File System CatalogConsistency check of FSC vs. HSM file system Fsecheck --fsc-hsmfs PartitionName Types of inconsistenciesOwnerID 154336 Hsmfs NotesMigID 273932147200 FileSize 18691 REPORTING-BUGS REPORTING-BUGS MigID 273931007488 FileSize 2815Starting the consistency check Consistency check of FSC vs. FSE mediaOptions for consistency check of FSC against FSE media MigID MediaKey MedVolNum Inconsistency typesExample results of the FSC vs. FSE media consistency check Dump FRI Var/opt/fse Low storage space detectionVar/opt/fse/part Var/opt/fse/log HHM configuration fileGeneral HHM settings Triggered actions definitions Mail settingsKey Description Default value on Linux Windows Variable Description Examples or possible values Monitored items definitions Triggered actions section of the configuration fileCriticalThreshold FilesystemtypeCriticalActionGE CriticalActionLTMonitoring and maintaining FSE HP StorageWorks File System Extender Software user guide Monitoring and maintaining FSE Modifying the contents of the HHM configuration file Configuring low storage space detectionListing the contents of the HHM configuration file Viewing FSE log files FSE log filesFSE event log /var/opt/fse/log/fse.log Configuring monitoring and analysis of FSE log filesMonitoring and analyzing FSE log files LogAnalyzerRules.py General configuration file# --- Debug LogAnalyzerActivityLog = /var/opt/fse/log/loganalyzermessages.log # --- To # To-Part of the mailheader # --- Subject # Subject-Part of the mailheader# --- From # From-Part of the mailheader # CommunityName # The community name of the machine # Default is 1 minuteSleepTime DebugProcessFileFromBeginning UseSMTPAuthenticationIgnoreCase ServerNameRules = \ Rules configuration fileMailCurrentLogMessagesbj MailLogMessagesMailLogMessagessbj Action Name Description Starting the monitoring and analysis of log filesFSE event log Reconfiguring the monitoring and analysis of log filesLogging FSE media operations Example FSE event logMonitoring and maintaining FSE HP StorageWorks File System Extender Software user guide Windows specific HP StorageWorks File System Extender Software user guide Example FSE error log FSE error logHP StorageWorks File System Extender Software user guide Monitoring and maintaining FSE Windows specific Monitoring and maintaining FSE HP StorageWorks File System Extender Software user guide Generated report conforms to the following example Determining total offline storage capacity# cd /opt/fse/sbin/tools # ./checklic Checklic checklic-output.txtBackup, Restore, Recovery, Defining your backup strategyIntroduction, Defining your backup strategy, See HSM file system Recovery methods for FSE componentsFSE component Description Recovery method BackupWhat is FSE backup? How it works? Backup configuration file on Linux platformPrerequisites # modprobe dm-snapshotMODULESLOADEDONBOOT=dm-snapshot Backup media managementBackup process Estimating resources Configuring a backup media poolPreparation of new media Preparation of already used mediaBackup media recycling Defining the backup policyEstimating backup frequency Fsebackup --medium Barcode --initExamples of backing up to disk Starting FSE backupFsebackup command Activity logging Example FSE backup log fileExample of backing up to tape Example of backing up to disk and tapeCMD HP StorageWorks File System Extender Software user guide Aborting FSE backup RestoreWhat is FSE restore? Restore process Fserestore command Starting FSE restoreExamples of retrieving backup images from tape Examples of restoring from diskOpt/fse/lbin/fserestore.py -f /root/test.tar.bz2 Example FSE restore log fileFsebackup --device /dev/sg1 --offset 3 --count CMD Post-restore steps RecoveryFile System Catalog recovery Aborting FSE restoreHSM file system recovery procedure HSM file system recoveryEnable the FSE partition Start the recovery of FSC Prerequisite\fserecover --hsmfs PartitionName Status of user data on the recovered HSM file system# fserecover --hsmfs PartitionName Backup, restore, and recovery Troubleshooting # ps -ef grep CommandName FSE startup and shut-down problemsDefaults to C\Program Files\Hewlett-Packard\FSE Examining the process list in Windows Task Manager# ls -a /etc/opt/fse Agent.pkg Cli-admin.pkg Common.pkg Server.pkgCli-user.pkg Client.pkg Common.pkg # rpm -qa grep fse- grep -v fse-gui.client.pkgResolve it OmniORB cannot work with such a configurationTry to start them manually, the following error is reported Use the kill command to terminate the FSE processesOperating system tools to terminate all FSE processes Use Task Manager to terminate the FSE processesFirebird.sourceforge.net Firebird server problems# /etc/init.d/firebird status Ibserver pid 896 895 581 577 576 is runningIt defaults to C\Program Files\Hewlett-Packard\FSE Communication problemsRun the command omniNames --statusand inspect its output Service daemon serviceStop the FSE processes with the fse --stopcommand You must restart FSE with the fse --restartcommandFsepartition --status PartitionName Use the command ps -ef grep fse-hsmDriver is disabled Scsi problemsCat /proc/scsi/scsi Etc/rc.d/rc.localHprescan -a Options scsimod maxscsiluns=255 Tape library problems# echo scsi scan-new-devices /proc/scsi/scsi # cat /proc/scsi/scsiFsedrive --remove Name Fselibrary --update-inventory LibraryName --rescanVolume Overflow 0x00,0x02 End-of-partition/medium detected Media management problemsFseError 11005 Medium overflow physical EOM Is known Problematic medium volumeInto the Rmdb ExecutionWorkaround HSM file system mounting problems Fse --mount I\fse\fsefs01 \\?\Volume \fse --dismount-ntfs VolumeNameFse --umount I\fse\fsefs01 \\?\Volume...\ Fse --mount I\fse\fsefs01 \\?\Volume...\Fsepartition --enable PartitionName Fsepartition --disable PartitionNameFsepartition --remove PartitionName Fsepartition --add PartitionNameFse --dismount-ntfs VolumeName HSM file system filter problemsAccessed for the first time HSM file system mounting problems onFsecheck --fsc-hsmfs PartitionName Fse --stopFse --start Start writing to tape Migration problemsRuns out of free space Prevent it from running out of free spaceFsefile --recall --id PartitionName FileID --into Path Fsefile --history FileNameFile DirectoryPath/FileName FSE error logComplete Migration of the file is startedUse the ps -ef grep fse-hsmcommand for this purpose Recall problemsHas been allocated for recall Unusable FSE medium to become good usableScanning against viruses Recall them manually Backup, restore, and recovery problemsNot indicate data loss \fse --stop Section Verifying and repairing the installed FSE softwareFSE Windows Service stopped File backup.pid and start FSE backup once again FSE backup cannot be startedLayout Status of the medium will be empty# modprobe dm-snapshot Dm-snapshot to the variable Modulesloadedonboot in the fileEtc/sysconfig/kernel, like shown in the following example To directories cannot be shared Sharing problemsFsefile --migrate FileName Other problemsAcpi=oldboot pci=noacpi apm=power-off Following message is written to the FSE event log Directory and its contents from the external FSE clientNo space left on device On this partitionExplanation Workaround File System Catalog recovery onIs running on the associated FSE partition LogFor files that cannot be deleted FSE troubleshooting tools Tool name Description Debugging and operation fine-tuning optionsDebugging FSE processes Debugging options InstallPath%\var\log\debugExample Var/opt/fse/log/debugInstallPath%\var\log\error.log Var/opt/fse/log/error.logWindows specific Flag value Description Operation fine-tuning options Export HSMPTDIRECT=no Export HSMFRISAFETYBUFTAPE=1000Export HSMBEAVERIFYPOSITION=ALWAYS Export HSMLASERIALUNLOAD=yesRestart the syslogd daemon Debugging FSE backup and restore processesDebugging HSM file system filter Gathering information about your problem Potential problems with debuggingBackup or restore debugging results in job failure Checklist for required informationContact FSE error codes1001 9991002 10032005 20042006 20073002 30013003 30044024 40234025 40268005 80048006 800710003 1000210004 1000513003 1300213004 13005Opt/fse/bin OmniNames commandOpt/fse/doc Opt/fse/lbinPath on Linux platform Path on Windows platform Contents FSE configuration templates Libraryhostname Template for FSE librariesSlots Slots = 1-15 # Tips Template for FSE drivesHP StorageWorks File System Extender Software user guide Template for LTO media pools SysVolLocation = None SizeOfSysVol = 0MB Template for disk media pools Write-Once-Read-Many file system Template for FSE partitions General partTemplate for FSE partitions Migration part Template for FSE partitions Release part FSE configuration templates Template for FSE partitions Recall and Allocation part Template for FSE partitions Deletion part Template for FSE system configuration FSE configuration templates Media pool FSE media pool Configuration file FSE configuration file templateExternal client FSE external client File System Catalog FSCOwn deletion policy Needs cleaning or servicingDisk buffer 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 MAMMedium 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 medium320 Index 184 Default job priority policy 144Default partition allocation policy Configuring, consolidated FSE system GUI HP StorageWorks File System Extender Software user guide 326 Media 117, 119 media pools FSE Management Console GUI 57 status check328
Related manuals
Manual 99 pages 2.23 Kb Manual 115 pages 39.56 Kb Manual 92 pages 24.26 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.