Virtualization Manager Database Change Compensation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In virtualization systems, long transactions can lead to resource lockup and make it difficult to recover from failures, as committed changes cannot be rolled back, resulting in potential system crashes and loss of data integrity.
Innovation Solution
Implementing a method for database change compensation by creating business entity snapshots before committing transactions, allowing the system to revert to a previous state in case of failures, using a virtualization manager that breaks down commands into shorter transactions and maintains snapshots until all transactions are completed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If transactions are made shorter to reduce resource lockup, then productivity and system responsiveness improve, but the ability to recover from failures deteriorates because committed changes cannot be rolled back
Solution Approach 1:
The system creates snapshots of database records before transactions commit changes. These snapshots serve as preliminary backup states that enable rollback capability even after short transactions commit their changes. The snapshot creation happens in advance of potential failures, allowing the system to recover by reverting to pre-snapshot states.
Solution Approach 2:
The invention creates copies of database records in snapshot tables before transactions modify them. These copies preserve the original state of data, allowing the system to revert to previous states after short transactions commit. The copying mechanism enables rollback without requiring long transaction locks.
2Reliability
If transactions are made longer to ensure atomicity and recovery capability, then system reliability improves, but resource lockup increases and productivity decreases
Solution Approach 1:
The invention segments the transaction process into two independent parts: the short transaction that commits changes quickly, and the separate snapshot management system that handles rollback logic. This segmentation allows transactions to commit atomically without holding locks for extended periods, while recovery operations can be performed independently on snapshots without blocking resource access.
Solution Approach 2:
The snapshot table acts as an intermediary between the transaction system and the rollback mechanism. Instead of requiring long transactions to maintain atomicity, the snapshot intermediary captures the state before transactions, allowing quick commits followed by independent rollback operations if needed. This mediator enables both short transactions and reliable recovery.
3Reliability
If snapshots are maintained for all transactions to enable rollback, then system reliability improves, but device complexity and storage requirements increase
Solution Approach 1:
The system applies snapshot creation selectively rather than universally. Snapshots are created for specific records that need rollback protection, not for all database operations. This local approach reduces storage overhead and simplifies snapshot management by focusing only on critical data elements that require recovery capability.
Solution Approach 2:
The system discards snapshots after they have served their purpose for potential rollback. Once a transaction completes successfully and the window for potential failure passes, or once rollback is determined unnecessary, the associated snapshots are discarded to free storage resources. This lifecycle management reduces overall storage requirements and simplifies snapshot table maintenance.
Data Source
AI summary
A virtualization manager receives a request to perform a command in a virtual machine system and executes a plurality of transactions associated with the command, each of the plurality of transactions comprising one or more operations executed on entities in the virtual machine system. The virtualization manager commits changes made to the entities in the virtual machine system as a result of the plurality of transactions to a management database for the virtual machine system. In addition, the virtualization manager generates a business entity snapshot corresponding to a first transaction of the plurality of transactions, the business entity snapshot comprising state information for one or more entities in the virtual machine system affected by the first transaction.