HP File System Extender (FSE) manual Defining your backup strategy, Backup, Restore, Recovery

Page 219

7 Backup, restore, and recovery

This chapter includes the following topics:

•Introduction, page 219

•Defining your backup strategy, page 219

•Backup, page 221

•Restore, page 230

•Recovery, page 235

Introduction

There are several methods that you can use to increase safety of data in the FSE implementation. Nevertheless, if data loss occurs, FSE includes features which help recreating data that has been lost in disaster on any component of the FSE implementation. These features are FSE backup, FSE restore and FSE recovery. FSE restore can only be used if FSE backup has been performed before and backup images are available, while FSE recovery does not depend on any other processes.

When user data on HSM file systems is concerned, an appropriate level of their safety can be achieved by properly configuring migration policies for the belonging FSE partitions (see section ”Migration” on page 127), considering multiple copying (see section ”Multiple copying” on page 147), and executing periodic monitoring of physical condition of FSE media in the assigned FSE media pools (see section ”Checking the status of media” on page 117). If disaster occurs on an HSM file system, you can use the recovery feature of FSE to completely recreate damaged or destroyed HSM file system. FSE recovery recreates data and metadata on HSM file system from the belonging Name Space Catalog, which is part of File System Catalog.

Besides user data, FSE implementation also includes other data which are essential for normal operation of FSE. These data are referred to as FSE databases and system files, and contain global configuration files, configuration of FSE resources, not yet migrated metadata, and other entities. They are located on the consolidated FSE system or FSE server, depending on the type of your FSE implementation. To maintain appropriate level of safety of these data, you can equip the FSE server host with a RAID storage subsystem (see the latest support matrices), organize and prepare local file systems (see the FSE installation guide for a particular platform, chapter ”Preparing file systems for FSE”), and define a thoughtful FSE backup policy (see section ”Defining your backup strategy” on page 219). In case of disaster on the FSE server host and when the FSE databases and system files are affected, you can use the FSE restore feature to restore a complete FSE server state from an FSE backup image. As an alternative, when File System Catalogs are only affected, FSE recovery can be used to completely recreate each particular File System Catalog. In this case, the FSE recovery process uses Fast Recovery Information and metadata from FSE media to build a File System Catalog from scratch.

NOTE: Backup and restore of FSE clients is not supported. During backup, only the client-related data on the consolidated FSE system or FSE server is backed up.

If all hosts of the FSE implementation are struck, FSE restore and FSE recovery processes must be used in sequence to revert the FSE implementation into operable state: the FSE server needs to be restored, and HSM file systems on the FSE clients need to be recreated using the HSM file system recovery functionality.

The next sections provide helpful hints on how to define your backup strategy, recommendations on recreating your data, and information on how to recover from an actual data loss.

Defining your backup strategy

Typically, if you only perform FSE backup on a regular basis and according to recommendations, you are only able to restore FSE databases and system files on the FSE server. You should also consider using FSE recovery as a method of recreating your data, and define your backup strategy accordingly.

HP StorageWorks File System Extender Software user guide 219

Page 218 Page 220
Image 219
Page 218 Page 220
Contents HP StorageWorks File System Extender Software user guide File System Extender Software user guide Contents Migration, release, recall, and deletion Managing mediaMonitoring and maintaining FSE Backup, restore, and recoveryTroubleshooting Introduction FSE startup and shut-down problemsDirectory layout B FSE configuration templates Document conventions Convention Element Document conventions and symbolsIntended audience Related documentationDocumentation feedback Subscription serviceHP technical support HP web sitesInfinite file system What is FSE?What is FSE?, FSE basics, FSE architecture, FSE basicsNFS and Cifs support Automatic error detectionLibrary tape compatibility Automatic detection of low storage spaceFSE architecture FSE operationsMigration Release Recall\Program Files\Hewlett-Packard\FSE FSE partition FSE componentsDeletion HSM file systemFile System Catalog FSE media poolFSE medium FSE libraryFSE implementation options FSE driveConsolidated implementation Distributed implementation Page FSE implementation with multiple libraries FSE daemons services and FSE agentsFse.exe Fse-fsevtmgrFse-hsm Fse-svcFSE utility daemons services Fse-la-sFse-bea FSE command-line interface Introduction to the FSE command-line interfaceFSE user interfaces Remove,--list,--show,--status, and so on FSE command listAccessing the online FSE command-line reference FSE command DescriptionFSE Management Console FSE Management Console client FSE Management Console serverConfiguring the FSE Management Console Var/opt/fse/log/guisrv.log InstallPath%\var\log\guisrv.logInstallPath%\var\cfg\gui\guisrv.users.db InstallPath%\var\log\fse.logParameter Description Configuring the logging levelDebuglevel = -d4 -DAll Debuglevel = -dTrc -DAllD Example of a configured FSE Management Console loggingStarting and stopping the FSE Management Console Starting and stopping the FSE Management Console serverStarting the FSE Management Console server on Linux systems # /etc/init.d/guisrv start# /opt/fse/lbin/guisrv Options # /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 # export DISPLAY=fsemcclient0 \Documents and Settings\Username\Application Data\guicltrcStarting and stopping the FSE Management Console client Starting the FSE Management Console client on Linux systems# guiclt Options Stopping the FSE Management Console client on Linux systemsPage Before you start Configuring FSEConfiguration basics Configuration filesFSE configuration file elements Templates Configuration DatabaseVar/opt/fse/rmdb Configuring a new FSE resourceResource Management Database Var/opt/fse/cfgFsepartition --modify Partition01 MyFile Modifying the configuration of an FSE resourceFsepartition --list --detail Fsepartition --show 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 Unreliable Recovery modeOpen UnusableFSE Management Console users Keyboard shortcutsManaging FSE Management Console users Configuration procedure Configuring an FSE resource using an FSE user interfaceFSE Management Console user properties Overview of the configuration procedure Phase 1 configuring FSE libraries and FSE drivesAbout Scsi identification Library and drive configuration procedure Opt/fse/newconfig. Windows specific Name Host ControlDevice LibType MediaFamily SlotsName Library MediaFamily 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 systems\mkdir hsmfsfolder Creating and preparing new HSM file systemsPreparing HSM file systems on the Linux platform Preparing HSM file systems on the Windows platformIntegrating existing file systems in the FSE implementation Integrating existing file systems on the Linux platformIntegrating existing file systems on the Windows 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 partitionFsemedium --format Barcode --force Phase 5 preparing FSE mediaFselibrary --update-inventory LibraryName --rescan Fsemedium --format BarcodeFor forced initialization use the following command Fsemedium --init BarcodeFsemedium --init Barcode --force Phase 6 mounting HSM file systems Mounting HSM file systems on the Linux platformFsesystem --status Command generates an output similar to the following \fsepartition --list Reconfiguring FSE interprocess communication\\?\VolumeVolumeGUID\ Mounting HSM file systems on the Windows platformOmniORB.cfg Etc/opt/fse Reconfiguration procedureServices.cfg Etc/opt/fse Var/opt/fse/omniorb. Windows specificHostname = fseserver.fsenet Server = fseserver.fsenet Ordinary LAN connectionPrivate network connection Server = fse-server1.company.comOmniORB.cfg file, configure the parameters in the section Services.cfg fileServices.cfg and omniORB.cfg files 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, FSE media pools, FSE media, Media pool types and their characteristicsIntroduction FSE media poolsMyConfiguration. 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 fileDetermining the configured media pools Example of a disk media pool configuration fileFsepool --list --detail Managing media Checking the status of a particular media pool Excerpt from the fsepool --list outputExcerpt from the fsepool --list --detail output FSE medium volumes FSE mediaExcerpt from the fsepartition --status output Disk media FSE media typesDisk media LTO Ultrium 3 WormLocal and remote file systems as disk media Capacity diskVar/opt/fse/dm/dm000001 Var/opt/fse/dm/dm000002 Disk media specifics Mnt/diskmedium linuxhost.company.comrw,nosquashroot`-- dm000001 Formatting media Adding media to an FSE media poolSkipping media formatting Medium is formatted using the following commandMedium is initialized using the following command Initializing mediaDuplicating media LTO 1 100 GiB * 2 = 200 GiB Procedure for duplicating mediaHow it works PrerequisitesNormal duplication Forced duplicationLTO 2 200 GiB * 2 = 400 GiB LTO 3 400 GiB * 2 = 800 GiB Reorganizing media Media reorganization processLimitation Enabled/mounted Fsemedium --list Barcode --volumeNumber of latest generations parameter Media reorganization parametersExceptions to the reorganizational rule Boundary migration date and time parameterMeaning of the columns is the following Example command outputScanning media for obsolete data Displaying the FSE media pool-based statisticsJob to the command shell for --no-monitoroption Running the media reorganization jobDisplaying the FSE media-based statistics Reusing the recycled medium volumes An example output is the followingFsemedium --list Recreating redundant copies of migrated data Redundant copy recreation process052002 Data 5949 Open, scanned Empty System 1019 Media Pool Starting redundant copy recreation Command output will be similar to the followingFsemedium --copy-contents Barcode --no-monitor Determining the unusable mediaFsefile -M Filename Resolving situations with no alternative migrated copiesChecking the status of media PoolLTO Open LiblibLTO5 000116 Example output of the fsemedium --list commandExample output of the fsemedium --list --detail command PoolLTO Open LiblibLTO3 000046Changing the condition status of media Checking the status of a particular mediumStatus of the medium can be one of the following Preventing reading from and writing to an FSE medium Closing medium volumesRecreating Fast Recovery Information from media Preventing writing to an FSE mediumFsemedium --remove Barcode Fselibrary --update-inventory command for this purposeFsemedium --recreate-fri Barcode --volume VolumeNumber Removing FSE mediaManaging media HSM lists FSE operation basicsHow does FSE function? PoliciesFSE disk buffer Storage space allocation in an extended FSE disk buffer Hierarchical Storage Manager listsChanges of states of files under FSE PoliciesMinimum file age for migration MinFileAge What is a retried migration?Migration Migration policy parametersMaximum number of files for migration MaxNumMigFiles Minimum wait time for migration MinWaitTimeMaximum wait time for migration MaxWaitTime Minimum number of files for migration MinNumMigFilesWatermarks Default migration policyRelease Example situations that trigger migrationReaching the critical watermark on an HSM file system High watermarkLow watermark Exclusion from releaseConsiderations before configuring exclusion from release Filename pattern conventionsLimitations Special pattern-matching characters Release policy parameters Minimum file size for release MinFileSize Example situations that trigger releaseMigration retention time MigRetentionTime Recall retention time RecallRetentionTimeDefault release policy RecallRecall parameters Automatic deletion process Default recall policyRecall timeout RecallTimeout DeletionDeletion policy parameters File expiration time FileExpirationDirectory paths Path Default deletion policy Examples of a configured deletion policyResource allocation concepts Resource allocationStarting the deletion job Recalling deleted filesCentral FSE resource manager Media selection by media locationSeveral allocation parameters ThresholdJobCount = 3/2 * MaxNumDrives System allocation and job priority policySystem allocation and job priority policy parameters Job prioritiesTime step TimeStep Resource allocation threshold ResourceAllocationThresholdPartition allocation and job priority policy parameters Partition allocation and job priority policyDefault partition allocation and job priority policy Maximum number of drives for recovery MaxNumDrivesRecoveryRecovery priority RecoveryPriority Maintenance priority MaintenancePriorityPriority calculation Administrative and backup job priority calculationMultiple copying Parallel copyingExample of resource allocation HSM file system access modes Limited Access Mode LAM and Full Access Mode FAMSequential copying HP StorageWorks File System Extender Software user guide Migration, release, recall, and deletion Number of running jobs Procedures in this chapter provide instructions forAbout monitoring and maintaining in FSE Monitoring general FSE implementation statusHost and mount point of the belonging HSM file system Example output of the fsesystem --status commandManaging FSE partitions Monitoring FSE partition statusDisplaying the status of an FSE partition Disabling an FSE partition Example output of the fsepartition --status commandRemoving an FSE partition To enable an FSE partition, do the followingWindows specific Invoke the following command Enabling an FSE partitionRetrieving detailed information for an FSE partition Switching the access mode for an HSM file systemMonitoring FSE jobs Switching to Limited Access ModeSwitching to Full Access Mode Limited Access Mode error messagesExample output of the fsejob --list command Example output of the fsejob --list --detail commandFsejob --list --maint PartitionName --detail 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 file ID instead of filename Recalling sets of files in an efficient wayExample of recall by date Example of recall by file migration ID512MBc, and 512MBd Command fsefile --recall --ifEfficient recall invocation Logging file recallsExample excerpt from the FSE error log file Retrieving detailed informationManaging FSE recall jobs Fsepool --list Fsemedium --list --volumeFselibrary --list Fsedrive --listName Drv01 Family ScsiUsageCount 137 Capabilities Key Name Drv02 Family Pool Pool01Ac3050b1-a838-458e-9a21-d3d3429cade9 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-eefe19d3f057Bfca4697-a1e0-4881-ba12-953acbb72a02 LastVer 1970/01/01 ValidData TotalDataPartition Part01 583Monitoring 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?Checking the consistency of the File System Catalog Consistency check of FSC vs. HSM file systemRemoving a file system from the FSE disk buffer Fsecheck --fsc-hsmfs PartitionName Types of inconsistenciesHsmfs Notes MigID 273932147200 FileSize 18691OwnerID 154336 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 Inconsistency types Example results of the FSC vs. FSE media consistency checkMigID MediaKey MedVolNum Dump FRI Var/opt/fse Low storage space detectionHHM configuration file General HHM settingsVar/opt/fse/part Var/opt/fse/log Mail settings Key Description Default value on Linux WindowsTriggered actions definitions Variable Description Examples or possible values Monitored items definitions Triggered actions section of the configuration fileCriticalActionLT FilesystemtypeCriticalThreshold CriticalActionGEMonitoring and maintaining FSE HP StorageWorks File System Extender Software user guide Monitoring and maintaining FSE Configuring low storage space detection Listing the contents of the HHM configuration fileModifying the contents of the HHM configuration file Viewing FSE log files FSE log filesConfiguring monitoring and analysis of FSE log files Monitoring and analyzing FSE log filesFSE event log /var/opt/fse/log/fse.log LogAnalyzerRules.py General configuration file# --- Debug LogAnalyzerActivityLog = /var/opt/fse/log/loganalyzermessages.log # --- Subject # Subject-Part of the mailheader # --- From # From-Part of the mailheader# --- To # To-Part of the mailheader Debug # Default is 1 minute# CommunityName # The community name of the machine SleepTimeServerName UseSMTPAuthenticationProcessFileFromBeginning IgnoreCaseRules = \ Rules configuration fileMailLogMessages MailLogMessagessbjMailCurrentLogMessagesbj Action Name Description Starting the monitoring and analysis of log filesExample FSE event log Reconfiguring the monitoring and analysis of log filesFSE event log Logging FSE media operationsMonitoring 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 Checklic checklic-output.txt Determining total offline storage capacityGenerated report conforms to the following example # cd /opt/fse/sbin/tools # ./checklicDefining your backup strategy Introduction, Defining your backup strategy,Backup, Restore, Recovery, See HSM file system Recovery methods for FSE componentsBackup What is FSE backup?FSE component Description Recovery method # modprobe dm-snapshot Backup configuration file on Linux platformHow it works? PrerequisitesBackup media management Backup processMODULESLOADEDONBOOT=dm-snapshot Preparation of already used media Configuring a backup media poolEstimating resources Preparation of new mediaFsebackup --medium Barcode --init Defining the backup policyBackup media recycling Estimating backup frequencyStarting FSE backup Fsebackup commandExamples of backing up to disk Example of backing up to disk and tape Example FSE backup log fileActivity logging Example of backing up to tapeCMD HP StorageWorks File System Extender Software user guide Restore What is FSE restore?Aborting FSE backup Restore process Examples of restoring from disk Starting FSE restoreFserestore command Examples of retrieving backup images from tapeExample FSE restore log file Fsebackup --device /dev/sg1 --offset 3 --countOpt/fse/lbin/fserestore.py -f /root/test.tar.bz2 CMD Aborting FSE restore RecoveryPost-restore steps File System Catalog recoveryPrerequisite HSM file system recoveryHSM file system recovery procedure Enable the FSE partition Start the recovery of FSCStatus of user data on the recovered HSM file system # fserecover --hsmfs PartitionName\fserecover --hsmfs PartitionName Backup, restore, and recovery Troubleshooting Examining the process list in Windows Task Manager FSE startup and shut-down problems# ps -ef grep CommandName Defaults to C\Program Files\Hewlett-Packard\FSE# rpm -qa grep fse- grep -v fse-gui.client.pkg Agent.pkg Cli-admin.pkg Common.pkg Server.pkg# ls -a /etc/opt/fse Cli-user.pkg Client.pkg Common.pkgResolve it OmniORB cannot work with such a configurationUse Task Manager to terminate the FSE processes Use the kill command to terminate the FSE processesTry to start them manually, the following error is reported Operating system tools to terminate all FSE processesIbserver pid 896 895 581 577 576 is running Firebird server problemsFirebird.sourceforge.net # /etc/init.d/firebird statusIt defaults to C\Program Files\Hewlett-Packard\FSE Communication problemsYou must restart FSE with the fse --restartcommand Service daemon serviceRun the command omniNames --statusand inspect its output Stop the FSE processes with the fse --stopcommandFsepartition --status PartitionName Use the command ps -ef grep fse-hsmDriver is disabled Scsi problemsEtc/rc.d/rc.local Hprescan -aCat /proc/scsi/scsi # cat /proc/scsi/scsi Tape library problemsOptions scsimod maxscsiluns=255 # echo scsi scan-new-devices /proc/scsi/scsiFsedrive --remove Name Fselibrary --update-inventory LibraryName --rescanMedia management problems FseError 11005 Medium overflow physical EOMVolume Overflow 0x00,0x02 End-of-partition/medium detected Execution Problematic medium volumeIs known Into the RmdbWorkaround HSM file system mounting problems Fse --mount I\fse\fsefs01 \\?\Volume...\ \fse --dismount-ntfs VolumeNameFse --mount I\fse\fsefs01 \\?\Volume Fse --umount I\fse\fsefs01 \\?\Volume...\Fsepartition --add PartitionName Fsepartition --disable PartitionNameFsepartition --enable PartitionName Fsepartition --remove PartitionNameHSM file system mounting problems on HSM file system filter problemsFse --dismount-ntfs VolumeName Accessed for the first timeFse --stop Fse --startFsecheck --fsc-hsmfs PartitionName Prevent it from running out of free space Migration problemsStart writing to tape Runs out of free spaceFsefile --recall --id PartitionName FileID --into Path Fsefile --history FileNameMigration of the file is started FSE error logFile DirectoryPath/FileName CompleteUnusable FSE medium to become good usable Recall problemsUse the ps -ef grep fse-hsmcommand for this purpose Has been allocated for recallScanning against viruses Backup, restore, and recovery problems Not indicate data lossRecall them manually Section Verifying and repairing the installed FSE software FSE Windows Service stopped\fse --stop Status of the medium will be empty FSE backup cannot be startedFile backup.pid and start FSE backup once again LayoutDm-snapshot to the variable Modulesloadedonboot in the file Etc/sysconfig/kernel, like shown in the following example# modprobe dm-snapshot To directories cannot be shared Sharing problemsOther problems Acpi=oldboot pci=noacpi apm=power-offFsefile --migrate FileName On this partition Directory and its contents from the external FSE clientFollowing message is written to the FSE event log No space left on deviceExplanation Workaround File System Catalog recovery onLog For files that cannot be deletedIs running on the associated FSE partition FSE troubleshooting tools Debugging and operation fine-tuning options Debugging FSE processesTool name Description Var/opt/fse/log/debug InstallPath%\var\log\debugDebugging options ExampleInstallPath%\var\log\error.log Var/opt/fse/log/error.logWindows specific Flag value Description Operation fine-tuning options Export HSMLASERIALUNLOAD=yes Export HSMFRISAFETYBUFTAPE=1000Export HSMPTDIRECT=no Export HSMBEAVERIFYPOSITION=ALWAYSDebugging FSE backup and restore processes Debugging HSM file system filterRestart the syslogd daemon Checklist for required information Potential problems with debuggingGathering information about your problem Backup or restore debugging results in job failureContact FSE error codes1003 9991001 10022007 20042005 20063004 30013002 30034026 40234024 40258007 80048005 800610005 1000210003 1000413005 1300213003 13004Opt/fse/lbin OmniNames commandOpt/fse/bin Opt/fse/docPath 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 File System Catalog FSC FSE configuration file templateConfiguration file External client FSE external clientSee media duplication Needs cleaning or servicingOwn deletion policy Disk bufferSee 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 Set to unusable Offline mediumLibrary Online mediumRecall, recall job An FSE users request with the fserecover commandRecovery job InstallPath%\var\rmdb directory on Windows platformSee media pool FSE media pool FSE implementationUnusable medium Is set by enabling the drive with the fsedrive commandUltrium See LTO Ultrium320 Index Default job priority policy 144 Default partition allocation policy184 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.
Top Page Image Contents