Note that resource allocation requests from different partitions can have different drive and priority policies, and that the same media pool cannot be assigned to several partitions. For more information on parameters for resource allocation, see ”System allocation and job priority policy” on page 142 and ”Partition allocation and job priority policy” on page 144.

Job priorities

When a new job is created, if all of the requested resources are available in the FSE implementation, Resource Manager allocates them and the job starts performing its task immediately. If some resources are not available, a resource request of the job is put into the resource allocation queue of the Resource Manager, and the job waits for availability of the resources.

In case there are too many jobs already running for the corresponding FSE partition, the newly created job is not allowed to request resources yet, but is put into the state ”pending” instead. Such pending job waits until the current job count for the FSE partition decreases below a threshold value, and can only request the resources from the Resource Manager afterwards. Pending jobs are processed in the “first come first served” order. The threshold job count is defined by the MaxNumDrives variable (specified in the FSE partition configuration file) as follows:

ThresholdJobCount = 3/2 * MaxNumDrives

IMPORTANT: The status pending is applicable only for jobs that can be run on a particular FSE partition: migration, recall, reorganization, and maintenance jobs. Administrative and backup jobs are FSE implementation-wide jobs. They are immediately started or queued in the resource allocation queue, no matter how many jobs are already running in the FSE implementation.

When the resource request of a job is put into the resource allocation queue, the job is assigned an initial priority. When a new job is put into the queue, the priorities of all existing resource requests are recalculated; the priority of each job is then modified according to the elapsed time and the phase of the job. The resource request is then processed according to its job priority. Each time a resource is freed, the queue is checked again to allocate the free resource.

IMPORTANT: Only jobs with the status waiting for resources have priorities assigned.

For details on priority calculation, see ”Priority calculation” on page 146.

System allocation and job priority policy

The system allocation and job priority parameters are read by the Resource Manager upon its startup.

System allocation and job priority policy parameters

The configuration parameters for the system along with their definition and impact are listed below.

Maximum number of drives for migration (SystemMaxNumDrivesMigration)

Definition

Maximum number of drives that can be used for migration by all FSE partitions.

 

 

Impact

The purpose of this parameter is to prevent migration jobs from using all the drives in the

 

FSE implementation. By limiting drives for migration, you ensure that drives remain

 

available for other jobs (recall, administrative, recovery…). You should carefully balance

 

resources according to your environment.

 

 

142 Migration, release, recall, and deletion

Page 141 Page 143
Page 142
Image 142
HP File System Extender (FSE) manual System allocation and job priority policy, Job priorities
Page 141 Page 143

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