18060184. POINT-IN-TIME DATA COPY IN A DISTRIBUTED SYSTEM simplified abstract (INTERNATIONAL BUSINESS MACHINES CORPORATION)
Contents
- 1 POINT-IN-TIME DATA COPY IN A DISTRIBUTED SYSTEM
- 1.1 Organization Name
- 1.2 Inventor(s)
- 1.3 POINT-IN-TIME DATA COPY IN A DISTRIBUTED SYSTEM - A simplified explanation of the abstract
- 1.4 Simplified Explanation
- 1.5 Potential Applications
- 1.6 Problems Solved
- 1.7 Benefits
- 1.8 Potential Commercial Applications
- 1.9 Possible Prior Art
- 1.10 Original Abstract Submitted
POINT-IN-TIME DATA COPY IN A DISTRIBUTED SYSTEM
Organization Name
INTERNATIONAL BUSINESS MACHINES CORPORATION
Inventor(s)
Walter Charles Dietrich, Jr. of Armonk NY (US)
Michael Patrick Shute of Stratford CT (US)
Marcelo Fernandes De Oliveira of Sorocaba (BR)
Tiago Jose Adami of Centro (BR)
Norberto Gasparotto Filho of Agua Verde (BR)
POINT-IN-TIME DATA COPY IN A DISTRIBUTED SYSTEM - A simplified explanation of the abstract
This abstract first appeared for US patent application 18060184 titled 'POINT-IN-TIME DATA COPY IN A DISTRIBUTED SYSTEM
Simplified Explanation
The abstract of the patent application describes a method, computer program product, and computer system for managing file sets and databases in a primary and secondary site computer environment. The system includes a controller component that verifies the state of file sets and initiates a sub-controller component to suspend write operations to databases at the primary site computer, execute point-in-time copy processes for databases and non-database files, and then resume write operations. The point-in-time copies are sent to the secondary site computer for continued operation in case of primary site unavailability.
- Controller component verifies state of file sets
- Sub-controller suspends write operations to databases at primary site
- Point-in-time copy processes are executed for databases and non-database files
- Write operations are resumed after point-in-time copies are completed
- Copies are sent to secondary site for continued operation
Potential Applications
This technology could be applied in disaster recovery scenarios where seamless transition of operations from a primary to a secondary site is crucial.
Problems Solved
This technology solves the problem of ensuring data integrity and continuity of operations in case of primary site computer unavailability.
Benefits
The benefits of this technology include improved data protection, reduced downtime, and increased reliability in critical business operations.
Potential Commercial Applications
A potential commercial application of this technology could be in the field of data backup and disaster recovery services for businesses.
Possible Prior Art
One possible prior art could be traditional backup and recovery systems that may not offer the same level of automation and seamless transition as described in this patent application.
Unanswered Questions
How does this technology handle potential conflicts during the point-in-time copy processes?
The technology does not explicitly address how conflicts, such as simultaneous write operations, are managed during the point-in-time copy processes.
What is the scalability of this technology for large-scale databases and file sets?
The scalability of this technology for handling large-scale databases and file sets is not detailed in the abstract.
Original Abstract Submitted
Method, computer program product, and computer system are provided. A controller component verifies the state of all file sets. The controller component initiates a sub-controller component, based on successfully verifying the state of the file sets. The sub-controller component suspends write operations to all databases at the primary site computer. Based on the suspending completing without error, the sub-controller executes point-in-time copy processes for each of the databases and for application non-database files at the primary site computer. Applications using the databases and non-database files are not suspended. Based on all of the point-in-time copy processes completing without error, the sub-controller component resumes write operations to all databases at the primary site computer. The point-in-time copies are automatically sent to the secondary site computer so that the applications can operate at the secondary site computer if the primary site computer becomes unavailable.