Encrypted Index Recovery Using Deferred Transactions and Key Reuse
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database recovery for encrypted indexes is hindered when a database instance fails, as incomplete transactions modify encrypted indexes, and the decryption key is not available during the recovery process, preventing access to the database.
Innovation Solution
Deferred transactions that modify encrypted indexes are queued, and remedial actions are performed using a secure enclave or without one, with the decryption key from a later query, ensuring database access while waiting for key availability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If database recovery is performed using traditional methods, then database integrity is preserved, but the decryption key is not available during recovery, preventing access to encrypted indexes
Solution Approach 1:
The patent performs preliminary actions by queuing deferred transactions and preparing recovery operations before the decryption key becomes available. The system identifies incomplete transactions, queues them for later execution, and prepares the recovery framework in advance, so that when the decryption key arrives, the system can immediately complete the recovery without interruption.
Solution Approach 2:
The patent introduces an intermediary mechanism (the deferred transaction queue and recovery manager) that mediates between the unavailable decryption key and the recovery process. This intermediary allows the system to accept and hold recovery requests, manage the timing of key availability, and coordinate the completion of transactions without requiring simultaneous presence of all components.
2Reliability
If the database server waits for user connection to obtain decryption key, then key availability is ensured, but database access is denied during the waiting period
Solution Approach 1:
The system performs preliminary actions by pre-identifying and queuing all transactions that require the decryption key before the user connects. Rather than waiting passively for key availability, the system proactively prepares the complete list of deferred transactions and maintains them in a ready state, eliminating idle waiting time once the key becomes available.
Solution Approach 2:
The patent maintains continuity of useful action by keeping the database system actively managing and monitoring deferred transactions throughout the waiting period. The recovery manager continuously tracks the status of queued transactions, prepares them for execution, and immediately processes them when the decryption key arrives, ensuring no useful action is lost during the key availability gap.
3Reliability
If incomplete transactions are rolled back during recovery, then database integrity is maintained, but encrypted index modifications are lost and require re-execution
Solution Approach 1:
The patent applies the discarding and recovering principle by temporarily discarding the incomplete transactions from the active execution stream during recovery, then recovering and re-executing them after the decryption key becomes available. The deferred transaction queue serves as a temporary holding area where transactions are preserved in their original form, allowing them to be discarded from the failed execution context and later recovered for successful completion.
Solution Approach 2:
The system performs preliminary analysis and identification of incomplete transactions before the recovery process begins. By pre-scan the transaction log and identify which transactions are affected by the failure, the system prepares a precise list of deferred transactions that need re-execution, avoiding unnecessary re-processing of already completed transactions and minimizing the impact on overall productivity.
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.