Guaranteeing the authenticity of the data stored in the archive storage
First Claim
1. A method for archiving data from an operational database comprising the steps of:
- storing data segments from said operational database that match a selection criteria in a temporary file;
providing contents of said temporary file to a component configured to write contents of said temporary file into an archive storage;
creating a storage unit in said archive storage to archive said contents of said temporary file in said archive storage, wherein said archive storage has one or more storage units; and
determining which storage unit within said archive storage is to be accessed in response to an access request using scoping variables stored in a repository.
1 Assignment
0 Petitions
Accused Products
Abstract
A method, computer program product and system for archiving data from an operational database. Data to be archived from the operational database may be stored either as received or transformed in a manner that allows the transformed archived data to be retrieved bit-for-bit identical to the original input received. Further, the data stored in the archive storage is read-only meaning that the data cannot be updated, deleted or modified. Further, backup copies of each of the storage units, which store the archived data, in the archive storage are created for disaster recovery purposes. Additionally, hash values are computed for each of the storage units in the archive storage which are used to detect unauthorized changes to the data stored in the storage units. In this manner, the authenticity of the data stored in the archive storage may be substantially guaranteed.
-
Citations
63 Claims
-
1. A method for archiving data from an operational database comprising the steps of:
-
storing data segments from said operational database that match a selection criteria in a temporary file; providing contents of said temporary file to a component configured to write contents of said temporary file into an archive storage; creating a storage unit in said archive storage to archive said contents of said temporary file in said archive storage, wherein said archive storage has one or more storage units; and determining which storage unit within said archive storage is to be accessed in response to an access request using scoping variables stored in a repository. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21)
-
-
22. A computer program product embodied in a computer readable medium for archiving data from an operational database comprising the programming steps of:
-
storing data segments read from said operational database that match a selection criteria in a temporary file; providing contents of said temporary file to a component configured to write contents of said temporary file into an archive storage; creating a storage unit in said archive storage to archive said contents of said temporary file in said archive storage, wherein said archive storage has one or more storage units; and determining which storage unit within said archive storage is to be accessed in response to an access request using scoping variables stored in a repository. - View Dependent Claims (23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42)
-
-
43. A system, comprising:
-
a memory unit for storing a computer program for archiving data from an operational database; and a processor coupled to said memory unit, wherein said processor, responsive to said computer program, comprises; circuitry for storing data segments from said operational database that match a selection criteria in a temporary file; circuitry for providing contents of said temporary file to a component configured to write contents of said temporary file into an archive storage; circuitry for creating a storage unit in said archive storage to archive said contents of said temporary file in said archive storage, wherein said archive storage has one or more storage units; and determining which storage unit within said archive storage is to be accessed in response to an access request using scoping variables stored in a repository. - View Dependent Claims (44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63)
-
Specification