Encrypted Index Recovery Using Deferred Database Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database recovery for encrypted indexes is hindered when a database server/host fails, as incomplete transactions modify encrypted indexes, and the decryption key is not available, preventing access and recovery of the encrypted index.
Innovation Solution
Deferred transactions are performed while waiting for a decryption key, and remedial actions are initiated to recover the encrypted index, allowing access to the database even without a secure enclave.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database recovery is run after server failure, then database integrity is preserved, but the decryption keys are not available in the enclave, preventing recovery of encrypted indexes
Solution Approach 1:
The system performs preliminary actions by saving metadata about encrypted indexes (including encryption algorithm, version, and associated table information) to the data file header before any failure occurs. This preliminary metadata storage enables the recovery process to identify and handle encrypted indexes without requiring the decryption key to be present in the enclave during recovery.
Solution Approach 2:
The patent introduces an intermediary mechanism where the data file header serves as a mediator between the encrypted indexes and the recovery process. The header contains metadata that allows the recovery process to locate, identify, and invalidate encrypted indexes without needing to decrypt them or have the decryption key available in the enclave.
2Ease of operation
If the database server is restarted without a secure enclave, then the database becomes accessible, but the encrypted index cannot be recovered
Solution Approach 1:
The system performs preliminary actions by storing comprehensive metadata about encrypted indexes in the data file header before restart occurs. This metadata includes information about the encryption algorithm, version, and associated tables, enabling the recovery process to identify and invalidate encrypted indexes even when the secure enclave is not available.
Solution Approach 2:
The data file header performs a self-service function by containing all necessary metadata about encrypted indexes within itself. This self-contained metadata allows the recovery process to operate independently of the secure enclave, enabling the system to identify and handle encrypted indexes using only the information stored in the header.
3Reliability
If decryption keys are required for recovery, then encrypted index integrity is maintained, but user access is denied during recovery
Solution Approach 1:
The system performs preliminary actions by storing metadata about encrypted indexes in the data file header before any failure or recovery operation. This metadata enables the recovery process to identify and invalidate encrypted indexes without requiring decryption keys, allowing user access to be restored immediately while the encrypted indexes are handled separately.
Solution Approach 2:
The patent extracts the metadata about encrypted indexes from the encrypted index structures themselves and places it in the data file header. This separation allows the recovery process to work with the metadata independently of the encrypted index data and decryption keys, enabling user access to be restored without waiting for encrypted index recovery.
Data Source
AI summary
Methods for database recovery for encrypted indexes are performed by systems and devices. A query with a decryption key is received from a client device, where the query modifies an encrypted index of a database using a secure enclave. When events requiring remedial actions for the database occur during the querying, some transactions of the query and later queries are deferred, and a remedial action is initiated that includes restarting the database. A determination of the remedial action being unsuccessful in recovering the encrypted index causes the action to be re-performed until another query having the decryption key is received whereupon the action is performed again to recover the encrypted index utilizing the decryption key. Deferred transactions are then performed with the decryption key. When a database restarts for access without secure enclaves, the encrypted index for the database is invalidated, and the remedial actions are otherwise completed or discarded.