Abstract: The present disclosure provides a hierarchical storage management system for storing data. A first controller receives a request to migrate a data item to a first storage tier. The data item is associated with at least an initial object ID. The first controller, in response to the request, generates a new object ID and identifies a first record in a data structure, wherein the initial object ID is identical to an object ID of the first record and to a parent object ID of the first record. The first controller replaces the object ID of the first record with the new object ID, creates in the data structure a new record that is associated with the data item, sets an object ID of the new record and a parent object ID of the new record to the initial object ID, and stores the data item to the first storage tier.

Abstract: Techniques for managing data stored in a hierarchical storage management (HSM) system are provided. A first controller receives a request to migrate a data item to a first storage tier managed by the first controller, wherein the data item is not associated with an object ID and a HSM status value indicates that the data item is resident on a second storage tier. The first controller generates an initial object ID, creates a new record for the data item in a data structure, sets an object ID field and a parent ID field of the record to the initial object ID. The first controller stores the data item on the first storage tier and sends an acknowledgement identifying the initial object ID as an object ID of the data item to a second controller that manages the second storage tier. The second controller updates the HSM status value.

Abstract: Described are embodiments of an invention for a sample assembly with an electrical conductor for detection of the antigens by electromagnetic read heads. In one embodiment, a sample assembly includes: a substrate; one or more base layers above the substrate; an outer layer above the one or more base layers; a plurality of sample trenches formed in the outer layer and/or the one or more base layers, each sample trench being characterized by an upper surface, a bottom surface, and a longitudinal axis; an electrical conductor disposed in the substrate, the electrical conductor being configured to generate an electromagnetic field in proximity to the plurality of sample trenches to enhance nanoparticle movement toward the bottom surface of the plurality of sample trenches; and at least one alignment trench formed above the substrate, each alignment trench having a longitudinal axis substantially parallel to a longitudinal axis of at least one of the sample trenches.

Abstract: In an approach to maintain data integrity in a computer data storage system, a clone management table is generated for a clone file tree that includes a relationship between at least one parent file and a clone file. The parent file is restored by: (i) determining that the parent-child relationship exists between the parent file and the clone file based on an entry in the clone management table, (ii) restoring data blocks in the parent file to the file system based on an analysis of an entry in the clone management table for the parent file and an identification of data blocks included in the clone file, and (iii) generating a new instance of the parent file based on the data blocks included in the file system and the entry in the clone management table for the clone file tree.

Abstract: For data backup and recovery based on linked file repositories with each of the linked file repositories representing an individual file system capable of storing at least one version of a file and being connected to at least one server system, each of the linked file repositories are placed in a certain position for storing a certain version of the file. Each position of each of the linked file repositories is continuously numbered. A number of the versions of the file are determined by the position of the one of the linked file repositories.

Abstract: Embodiments of the disclosure relate to methods of storing and using biosamples with a cartridge that includes slots for storing biosample capillary tubes. The methods include providing access to a holder inside an enclosure of the cartridge, the enclosure having a same form factor as a data tape cartridge used in an automated tape library. The holder is configured to receive a plurality of capillary tubes in the holder, the capillary tubes including one or more biosamples. Exemplary methods may also include receiving capillary tubes in the cartridge, withdrawing capillary tubes from the cartridge, scanning and/or analyzing the capillary tubes and/or biosamples. Exemplary methods may additionally or alternatively include retrieving the cartridge from a storage slot of the automated tape library, loading the cartridge onto a drive of the automated tape library, and/or receiving and/or exporting a cartridge to/from the automated tape library via a mail slot.

Abstract: In an approach to backup and restore one or more clone file trees, one or more processors generate a clone management table. One or more processors record a clone management information in the clone management table about each clone file. To backup a clone file, one or more processors update the clone management information, and store one or more data blocks that are in the clone file trees. To restore a clone file, one or more processors analyze a clone management information and restore one or more data blocks in the clone file. To restore a clone file parent, one or more processors analyze a clone management information and restore one or more data blocks in the clone file parent. To restore a clone file tree, one or more processors analyze a clone management information and restore one or more data blocks in the clone file tree.

Abstract: In an approach to backup and restore one or more clone file trees, one or more processors generate a clone management table. One or more processors record a clone management information in the clone management table about each clone file. To backup a clone file, one or more processors update the clone management information, and store one or more data blocks that are in the clone file trees. To restore a clone file, one or more processors analyze a clone management information and restore one or more data blocks in the clone file. To restore a clone file parent, one or more processors analyze a clone management information and restore one or more data blocks in the clone file parent. To restore a clone file tree, one or more processors analyze a clone management information and restore one or more data blocks in the clone file tree.

Abstract: A tape drive system server includes a non-volatile memory used as a cache memory for storing data files, at least part of the cache memory comprising a first region managed using a First In First Out policy management and a second region managed using a Least Recently Used policy management; a file system interface for interacting with data files stored on a tape drive system; an interface for allowing one or more remote systems reading and writing data stored on the cache memory; the server configured to: receive from the one or more remote systems one or more write requests for writing one or more data files; interpret attributes associated to data files instructed to be written by the one or more remote systems; and store data files instructed to be written by the remote systems according to the interpreted attributes.

Abstract: Automatically configuring backup client systems and backup server systems in a backup environment includes the following steps: determining if a new backup client system is available in the backup environment; in case of an available new backup client system a backup configuration module performs the sub-steps of: determining data types the new backup client system has to backup; determining corresponding backup policies for the determined data types based on a backup policy table mapping data types with backup policies; selecting a backup server system for the determined data types based on a backup server table including connection details of available backup server systems; configuring the determined backup policies for the data types of the new backup client system on the selected backup server systems; and updating the backup server table with an identifier of the new backup client system and an identifier of the backup policy.

Abstract: A mechanism is provided for storing data files in a file system. The file system provides a plurality of reference data files, where each reference data file in the plurality of data files represents a group of similar data files. The mechanism creates a new data file and associated the new data file with one reference data file in the plurality of data files thus defining an associated reference data file of the plurality of reference data files. The mechanism informs the file system about the association of the new data file with the associated reference data file. The mechanism compresses the new data file using the associated reference data file thereby forming a compressed data file. The mechanism stores the compressed data file together with information about the association of the new data file with the associated reference data file.

Abstract: Operating a shared nothing cluster system (SNCS) in order to perform a backup of a data element. The SNCS includes at least a first and a second storage node connected via a first network of the SNCS. The first and second storage nodes are configured to store a first set and a second set of blocks, respectively, in which the first and second set of blocks form a single data element. A backup server is connected to the first and second storage nodes, and the backup server includes a backup information table. The first and second storage nodes are configured to act as backup clients in a client-server configuration involving the backup server, upon receiving at the first and the second storage nodes a request to backup the data element. For each node of the first and second storage nodes, the node identifies one or more block sequences of consecutive blocks in a set of blocks of the data element stored in the node.

Abstract: A mechanism is provided for storing data files in a file system. The file system provides a plurality of reference data files, where each reference data file in the plurality of data files represents a group of similar data files. The mechanism creates a new data file and associated the new data file with one reference data file in the plurality of data files thus defining an associated reference data file of the plurality of reference data files. The mechanism informs the file system about the association of the new data file with the associated reference data file. The mechanism compresses the new data file using the associated reference data file thereby forming a compressed data file. The mechanism stores the compressed data file together with information about the association of the new data file with the associated reference data file.

Abstract: Automatically configuring backup client systems and backup server systems in a backup environment includes the following steps: determining if a new backup client system is available in the backup environment; in case of an available new backup client system a backup configuration module performs the sub-steps of: determining data types the new backup client system has to backup; determining corresponding backup policies for the determined data types based on a backup policy table mapping data types with backup policies; selecting a backup server system for the determined data types based on a backup server table including connection details of available backup server systems; configuring the determined backup policies for the data types of the new backup client system on the selected backup server systems; and updating the backup server table with an identifier of the new backup client system and an identifier of the backup policy.

Abstract: The present invention relates to a method for data access in a storage infrastructure. The storage infrastructure comprises a host system connected to at least a first storage system and a second storage system. The first storage system receives, from the host system, a write request for storing a data chunk, the write request is indicative of a first identifier of the data chunk. The first storage system calculates a hash value of the received data chunk using a hash function. The first storage system determines a first storage location in the first storage system of the data chunk and sends a write message including the hash value, the first identifier and the first storage location to the de-duplication module. The de-duplication module determines whether the hash value exists in the data structure.

Abstract: According to one embodiment, an independent file server connected to a wide area network (WAN) includes local file storage, a file system comprising information about directory structures, path, and file names of other file systems of other file servers connected to the WAN, and a deduplication module configured to communicate with other deduplication modules of other file servers connected to the WAN, perform data deduplication of data objects stored locally in the local file storage, and create and maintain a deduplication table mapping data chunks of locally stored data objects to identification characteristics and storage location in the local file storage, and construction plans of data files including locations of data chunks within the data files. Other systems, methods, and computer program products are presented according to more embodiments.

Abstract: The present invention relates to a data block based backup method for a data management system. The data management system comprises a file system that controls access by a database application to at least one database container file stored the data management system. The data management system further comprises a backup client that is connected to a remote backup server, whereby a first version of the database container file is saved in the backup server and a first inode containing information on data blocks of the first version of the database container file. The method may include creating a change tracking table for at least the database container file and adding an entry in the change tracking table, whereby the entry has an indication of the respective data block in association with an information indicating the type of the access.

Abstract: Methods and systems are provided for displaying information on a hard disk drive assembly. One hard disk drive assembly includes a hard disk drive that includes a driver circuit coupled to a display and to a display memory. The driver circuit activates the display mounted on the hard disk drive assembly. In response to the activation of the display the driver circuit obtains information from the display memory of the hard disk drive. The driver circuit displays at least a portion of the information obtained from the display memory on the display mounted on the hard disk drive assembly.

Abstract: Operating a data processing and storage apparatus to perform continuous backup monitoring for a collection of stored file system objects. In response to changes respective to a number of the file system objects, a set of Data Management Application Program Interface (DMAPI) events is created. For each of the events, accessory file system object information relative to a file system object subject to the change is determined. The events are grouped into an event group and a unique group identifier and an overall group size count are assigned to each of the events included in the event group. The events are sent together with the respective accessory file system object information, the respective group identifier and the respective group size to a number of backup clients registered as applications. The backup clients are to process the events together with the respective accessory file system object information, the respective group identifier and the respective group size into a number of backup requests.

Abstract: Operating a data processing and storage apparatus to perform continuous backup monitoring for a collection of stored file system objects. In response to changes respective to a number of the file system objects, a set of Data Management Application Program Interface (DMAPI) events is created. For each of the events, accessory file system object information relative to a file system object subject to the change is determined. The events are grouped into an event group and a unique group identifier and an overall group size count are assigned to each of the events included in the event group. The events are sent together with the respective accessory file system object information, the respective group identifier and the respective group size to a number of backup clients registered as applications. The backup clients are to process the events together with the respective accessory file system object information, the respective group identifier and the respective group size into a number of backup requests.