Abstract:
PROBLEM TO BE SOLVED: To manage an appropriate storage infrastructure having a plurality of storage components in accordance with consumer service level objectives (SLOs). SOLUTION: The storage components for storing consumer data are identified under consideration of specified service level objectives, and consumer SLO policies are mapped to the storage components to select available storage components for specified data classes to configure the storage components. The storage infrastructure comprises a management instance which automatically ensures that consumer data is stored on appropriate storage components satisfying the corresponding SLO policies, a consumer service level interface for providing SLO policies to the management instance, a component discovery and classification module (CDC module) for identifying storage components for storing consumer data, and a repository for storing metadata associated with the storing of consumer data under consideration of SLO policies. COPYRIGHT: (C)2009,JPO&INPIT
Abstract:
PROBLEM TO BE SOLVED: To provide a mechanism for processing the fail-over of a data management application about a shared disk file system in a distributed computing environment having a cluster of loosely coupled nodes providing a service. SOLUTION: According to this mechanism, given nodes of the cluster is defined as a fail-over candidate node. Configuration information about all of the fail-over candidate nodes is preferably stored in a central storage region. Message information that includes the failure information of at least one fail- over candidate node and is not defined by the failure information is distributed between fail-over candidate nodes. The fail-over candidate nodes decide whether to succeed the service of a failed node by analyzing the distributed message information and the stored configuration information. The fail-over candidate nodes succeed the service and the configuration information is subsequently updated in the central storage region.
Abstract:
Disclosed is a mechanism of managing an hierarchical storage management (HSM) system including an HSM server and a file server having a managed file system where the HSM server and the file server are interconnected via a network. Migration of data files from the file server to the HSM server is accomplished by providing at least one list for identifying candidate files to be migrated, scanning the managed file system until having detected a prespecified number of migration candidate files, recording the detected migration candidate files in the provided at least one list of candidate files, monitoring a current state of the managed file system, and migrating at least part of the candidate files identified in the at least one list of candidate files from the file server to the HSM server, dependent on the monitored current state of the managed file system. In parallel, the migrated data files can be identified by a unique identifier that allows direct access to the migrated files. The mechanism enables an efficient handling of large amounts of file based information in the HSM environment by way of an automigration process and is highly scalable with respect to the amount of file based information.
Abstract:
Share nothing cluster system (SNCS) 100 comprises backup server 126 for backing up data elements 135. SNCS 100 includes common namespace component 101 (e.g. file system mount point), nodes 110-112 with storage devices 120-122, and local table 128. Data 135 is partitioned in block sequences 137A-137E distributed across storage 120-122 as set of blocks BS1-BS3. For example BS1 comprises sequences 137A, 137C. Placement information is stored in table 128. After a request for backing-up data 135, each node identifies corresponding block sequences and sends them to the back up server alongside information on the ordering of block sequences, the node, and the data element (e.g. filename). The server organises the information for a block sequence as an entry in backup information table 300. It adds a first flag after complete reception and storage of each sequence and a second flag at completion of the back-up for the entire data element.
Abstract:
A computer-implemented method for providing storÂage resources (R01-R09) of a storage management system (201), the method comprising: receiving (101) a storage service request comprising an indication of a service class (301-303); determining (102) all resource managers (RM1-RM5) mapped to the inÂdicated service class according to a first mapping (212) each resource manager having a generic API; for each of the determined resource managers, determine (104) seÂlected ones of all the storage resources controllable by said reÂsource manager; gathering (105) monitoring data of the selected storage resources; comparing (106) the gathered monitoring data for calculating a score for each one of the selected storage resources; and calling (107) at least one function of the resource manager operable to control the storage resource having an optimum score.
Abstract:
Disclosed is a mechanism of managing an hierarchical storage management (HSM) system including an HSM server and a file server having a managed file system where the HSM server and the file server are interconnected via a network. Migration of data files from the file server to the HSM server is accomplished by providing at least one list for identifying candidate files to be migrated, scanning the managed file system until having detected a prespecified number of migration candidate files, recording the detected migration candidate files in the provided at least one list of candidate files, monitoring a current state of the managed file system, and migrating at least part of the candidate files identified in the at least one list of candidate files from the file server to the HSM server, dependent on the monitored current state of the managed file system. In parallel, the migrated data files can be identified by a unique identifier that allows direct access to the migrated files. The mechanism enables an efficient handling of large amounts of file based information in the HSM environment by way of an automigration process and is highly scalable with respect to the amount of file based information.
Abstract:
Disclosed is a mechanism for handling failover of a data management application for a shared disk file system in a distributed computing environment having a cluster of loosely coupled nodes which provide services. According to the mechanism, certain nodes of the cluster are defined as failover candidate nodes. Configuration information for all the failover candidate nodes is stored preferably in a central storage. Message information including but not limited to failure information of at least one failover candidate node is distributed amongst the failover candidate nodes. By analyzing the distributed message information and the stored configuration information it is determined whether to take over the service of a failure node by a failover candidate node or not. After a take-over of a service by a failover candidate node the configuration information is updated in the central storage.
Abstract:
Disclosed is a mechanism of managing an hierarchical storage management (HSM) system including an HSM server and a file server having a managed file system where the HSM server and the file server are interconnected via a network. Migration of data files from the file server to the HSM server is accomplished by providing at least one list for identifying candidate files to be migrated, scanning the managed file system until having detected a prespecified number of migration candidate files, recording the detected migration candidate files in the provided at least one list of candidate files, monitoring a current state of the managed file system, and migrating at least part of the candidate files identified in the at least one list of candidate files from the file server to the HSM server, dependent on the monitored current state of the managed file system. In parallel, the migrated data files can be identified by a unique identifier that allows direct access to the migrated files. The mechanism enables an efficient handling of large amounts of file based information in the HSM environment by way of an automigration process and is highly scalable with respect to the amount of file based information.
Abstract:
The data management system uses a group of nodes (200) Some nodes (2) serve a parallel data system and others (1,3) provided service to these. Other nodes (4) use common data .The group connects with group data register (210) and a group service (220)