Abstract:
PROBLEM TO BE SOLVED: To provide HSM two-way orphan reconciliation for extremely large files. SOLUTION: An HSM application generates a migrated file identifier which is a hex string for each migrated file. A file system provides a list of migrated file identifiers in a file system queue 210, and a storage repository server has a list of migrated file identifiers provided in a file system queue 220. File system orphans and server object orphans are identified by comparing the migrated file identifier of the server object queue 220 with the migrated file identifier of the file system queue 210 (240 or 250). COPYRIGHT: (C)2010,JPO&INPIT
Abstract:
A distributed file system 102 is used by compute nodes 1113 to access storage devices 1213 via a network 120. A monitor 104 creates events in response to operations, which modify the file system. The events are grouped 106 and sent to backup clients 1313. The backup clients process the events to produce backup requests. The backup clients may use a shared database 150 to co-ordinate the processing. The backup requests are then sent to a backup server 140. Each event group has an identifier and a size. Each event includes the handle of the object in the file system, which is being modified, or the handle of its parent directory. It also includes the event type and the type of object. The events and handles may be Data Management Application Program Interface (DMAPI) events and handles. The file system objects may be file or directory objects.
Abstract:
Ein Computer empfängt einen Satz von Objekten von einem Client (201), wobei wenigstens eines der Objekte des Satzes einem eindeutigen Dateiverschlüsselungsschlüssel (FEK) zugehörig und mit diesem verschlüsselt ist. Der Computer verschlüsselt jeden der FEKs mit einem gemeinsamen Hauptverschlüsselungsschlüssel MEK, was entsprechende gesperrte Schlüssel zur Folge hat. Bei einem anfänglichen Backup werden die verschlüsselten Objekte zusammen mit ihren zugehörigen gesperrten Schlüsseln zu einem Backup-Server (205) übertragen, wo ein erstes Modul ermittelt, ob sich der gesperrte Schlüssel geändert hat, indem auf einen Verschlüsselungszustand Bezug genommen wird, der den verschlüsselten Objekten zugehörig ist. Wenn sich ein MEK geändert hat, werden die vorhandenen FEKs mit dem geänderten MEK neu verschlüsselt, um neue gesperrte Schlüssel zu erzeugen, und in einer nachfolgenden Backup-Operation werden die neuen gesperrten Schlüssel an den Backup-Server (205) gesendet, um die vorhandenen gesperrten Schlüssel zu ersetzen, während das Übertragen der Objekte, deren zugehörige FEKs von dem geänderten MEK betroffen sind, an den Backup-Server (205) vermieden wird.
Abstract:
Methods of versioning or backing up data a hierarchical storage management, HSM, system which includes at least a first storage tier and second storage tier managed by a HSM client and HSM server respectively, wherein the HSM server and the HSM client are interconnected via a network of the HSM system, wherein a data item stored in the HSM system is associated with a HSM status parameter that is stored in the HSM client, the HSM status parameter having a first, second or third value, the first value indicating a pre-migrated state of the data item in which the data item is stored in the first and second storage tiers, the second value indicating a migrated state of the data item in which the data item is stored in the second storage tier, the third value indicating a resident state of the data item in which the data item is stored in the first storage tier, wherein in case the HSM status parameter has at least one of the first and second values the data item is further associated with a predetermined initial object ID that is stored in the HSM client and the HSM server, the initial object ID corresponding to a first version of the data item, the HSM server being configured with a data structure comprising an object ID field comprising at least the initial object ID and a newly created parent object ID field comprising the initial object ID.
Abstract:
A method for testing a software product (10) comprising a plurality of software packages (P1, ..., P(Z)), which are to be installed or de-installed in defined order, comprises the steps: providing software package dependency and prerequiÂsite information (142) for the software product (10); analyzing the software package dependency and prerequisite information for each software package and creating a dependency matrix (112) for said software packages with each row representing one dependency levÂel; assigning each software package to at least one level based on its dependencies to other softÂware packages; wherein in the dependency matrix (112) each level contains software packages, which have no dependencies amongst themselves and deÂpend on at least one other software package assigned to a previÂous level; and a lowest level contains software packages without any dependencies; reducing the dependÂency matrix (112) by searching for software packages assigned to more than one level, determinÂing the highest level the software package is asÂsigned to, and deleting the software package from lower levels it is assigned to; determining possible software package test combinations of the software product based on the reduced dependency matrix (112); and performÂing installation or de-installation procedure of software packÂages of the software product (10) based on the software package test combinations to test installation or deinstallation order of the software packages of the software product (10).