US8190572B2 - High-availability and data protection of OLTP databases - Google Patents
High-availability and data protection of OLTP databases Download PDFInfo
- Publication number
- US8190572B2 US8190572B2 US11/675,368 US67536807A US8190572B2 US 8190572 B2 US8190572 B2 US 8190572B2 US 67536807 A US67536807 A US 67536807A US 8190572 B2 US8190572 B2 US 8190572B2
- Authority
- US
- United States
- Prior art keywords
- primary
- database
- data files
- oltp
- oltp database
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related, expires
Links
- 238000000034 method Methods 0.000 claims abstract description 14
- 238000004590 computer program Methods 0.000 claims 7
- 238000013500 data storage Methods 0.000 description 16
- 238000010586 diagram Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 210000004556 brain Anatomy 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
Definitions
- An online transactional processing (OLTP) database is a repository of transactional data of an enterprise, typically used by the enterprise to store transactional data in real time.
- An underlying implementation of an OLTP database may be, for example, a commercially available relational database, such as provided by Oracle Corporation.
- an OLTP database may be used to track customer support issues for an enterprise (e.g., e-mailed customer support inquiries), and it is desirable that none of the customer support issues be lost.
- a backup of the files of an OLTP database may be maintained.
- this backup is typically stored on a storage medium such as a tape and, in the event of a failure of the OLTP database, the downtime to restore the database from the tape can be unacceptably long.
- transactions that were received after the backup was created (including those received while the OLTP database is being restored from the backup) will not be present on the backup storage medium and, thus, will not be present in the restored OLTP database.
- a method is for use with a primary online transactional processing (OLTP) database, to maintain a secondary storage usable by a backup OLTP database, wherein the primary storage, of the primary OLTP database, includes data files.
- OLTP online transactional processing
- the primary storage, of the primary OLTP database includes data files.
- the transaction indications for the primary OLTP database are recorded in at least one transaction log file, in the primary storage of the primary OLTP database, the transaction indications are caused to be mirrored to the secondary storage.
- a state of data files of the primary OLTP database is occasionally caused to be duplicated from the primary storage to the secondary storage.
- FIG. 1 is a block diagram illustrating an example system to accomplish synchronization of a primary OLTP database to a backup OLTP database.
- FIG. 2 illustrates an example timeline to illustrate an example of the interoperation (including synchronization) of primary and backup OLTP databases.
- FIG. 3 is a flowchart illustrating a method to “fail over” an OLTP database to secondary storage from primary storage.
- the inventors have realized that it is desirable for OLTP database transactions to continue to be stored in the event primary storage of the OLTP database fails. In addition, it is desirable that secondary (backup) storage be entirely current in the event primary storage of the OLTP database fails.
- synchronization of primary storage of an OLTP database with secondary storage of the OLTP database is accomplished by mirroring control files of the database to the secondary storage from which, in the short term, the backup OLTP database can be expediently brought into synchronization with the primary OLTP database.
- the data itself of the primary OLTP database is occasionally synchronized to the secondary storage.
- a backup OLTP database, using the secondary storage, may be used in place of the primary OLTP database without loss of transactions.
- the backup OLTP database may be “brought current” at any time and operate in place of the primary OLTP database.
- FIG. 1 is a block diagram illustrating an example system 100 to accomplish synchronization of a primary OLTP database 102 to secondary storage for use when desired or required by a backup OLTP database 152 .
- the primary OLTP database 102 and the target OLTP database 152 are each implemented by an Oracle relational database, although the OLTP databases 102 and 152 may be implemented by other types of databases.
- the primary OLTP database 102 includes a database server 104 interoperating with database storage 106 implemented by an underlying file system 108 .
- the database storage 106 holds transactional data files including control files 110 , redo logs 112 and archived logs 114 .
- the database storage also includes data files 116 .
- the data files 116 include the underlying data stored in the primary OLTP database 102 .
- the control files 110 , redo logs 112 and archived logs 114 include transactional information used and usable in the operation and maintenance of the primary OLTP database 102 . That is, the control files 110 are the “brains” of the database, and include information to make the database operate.
- the redo logs 112 are used to record transactions against the data files 116 . For example, if for some reason a transaction is not properly applied to a data file, then the redo logs 112 can be used to construct the proper state of the data files 116 .
- the archived logs 114 include redo logs 112 that have been flushed to the archive.
- the backup OLTP database 152 may be similar to the primary OLTP database 102 .
- the backup OLTP database 152 includes a database server 154 interoperating with secondary database storage 156 implemented by an underlying file system 158 .
- the secondary database storage 156 holds control files 160 , redo logs 162 , archived logs 164 and data files 166 .
- the data files 166 include the underlying data stored in the target data warehouse 152
- the control files 160 , redo logs 162 and archived logs 164 include metadata used in the operation and maintenance of the target data warehouse 152 .
- the system 100 includes a filer synchronizer 180 configured to, at a file system level, take a “snapshot” of the database storage 106 and of the secondary database storage 156 .
- the filer synchronizer 180 is further configured to compare the snapshots and transfer block changes from the database storage 106 to the secondary database storage 156 .
- the filer synchronizer 180 may be, for example, implemented by “Snapshot,” “SnapRestore” and “SnapMirror” products provided by Network Appliance, of Sunnyvale, Calif.
- the file synchronizer 180 is configured to occasionally synchronize the data files 116 of the primary OLTP database 102 with the data files 166 of the secondary data storage 156 , for use by the backup OLTP database 152 .
- the system may be configured such that the file synchronizer 180 synchronizes the data files 116 of the primary OLTP database 102 with the data files 166 of the secondary data storage 156 , for use by the backup OLTP database 152 , three times per day.
- the file synchronizer 180 is not configured to synchronize the control files 110 , redo logs 112 and archived logs 114 of the primary OLTP database 102 with the control files 160 , redo logs 162 and archived logs 164 of the secondary storage 156 , for use by the backup OLTP database 152 .
- the primary OLTP database 102 is configured such that, during operation of the primary OLTP database 102 , as information is being stored into the control files 110 , redo logs 112 and archived logs 114 of the primary OLTP database 102 , such information is also being stored into the control files 160 , redo logs 162 and archived logs 164 of the secondary storage 156 , for use by the backup OLTP database 152 .
- redo logs 112 and archived logs 114 of the primary OLTP database 102 such information is also being stored into the control files 160 , redo logs 162 and archived logs 164 of the secondary storage 156 , for use by the backup OLTP database 152 .
- mirroring functions provided by Oracle may be utilized.
- control files 110 , redo logs 112 and archived logs 114 of the primary OLTP database 102 are mirrored to the secondary storage 156 , for use by the backup OLTP database 152
- the information in these files is not applied to the data files 166 of the secondary storage 156 , for use by the backup OLTP database 152 , as part of the mirroring operation.
- control files 160 , redo logs 162 and archived logs 164 are always consistent with the control files 110 , redo logs 112 and archive log files of the primary data storage 106 . More specifically, if there is a need for the backup OLTP database 152 to operate from the secondary storage 156 then, to the extent the backup data files 166 may not be current (i.e., accounting for all transactions, including the most recent transaction), the control files 160 , redo logs 162 and archived logs 164 may be utilized to bring the data files 166 current for use by the backup OLTP database 152 current based on the logged transactions.
- Oracle provides functionality for bringing the data files of a database current based on logged transactions. For example, bringing the data files of a database current may include comparing a “last sequence number” of a transaction accounted for in the data files to sequence numbers of transactions indicated in control files, redo logs or archive logs, to determine whether there are later transactions than those already accounted for in the data files. In the event it is determined that there are such later unaccounted for transactions, these transactions are applied, thus bringing the data files of the database current.
- FIG. 2 illustrates such a timeline.
- the primary OLTP database is recording and applying transactions prior to 9:00:00 am. That is, the transactions are being recorded in the various control, redo log and archive log files and, in addition, the transactions are being applied to the data files of the primary storage associated with the primary OLTP database.
- the secondary storage usable by the backup OLTP database prior to 9:00:00 am, the transactions are being recorded, by virtue of the mirroring operation, but there is no action with respect to the data files on the secondary storage.
- a “hot backup” mode of the primary OLTP database is initiated, such that the data files of the primary storage are “locked.” That is, the transactions continue to be recorded in the various control, redo log and archive log files of the primary storage, but the transactions are not applied to the data files of the primary storage.
- the transaction mirroring operation continues, such that the transactions are being recorded to the various control, redo log and archive files of the secondary storage usable by the OLTP database. Thus, even during the backup processing, no transactions are lost.
- a “snap shot” is taken of the data files of the primary OLTP database.
- the snap shot taken of the data files of the primary OLTP database is compared to a snap shot of the data files of the secondary OLTP database (which may be, for example, taken at this time or may have been taken earlier). Based on the snap shot comparison, the data files of the secondary storage, usable by the OLTP database, are updated to be consistent with the snap shot of the data files of the primary OLTP database.
- the underlying file systems of the primary and secondary data storage may operate based on blocks, where the “snap shots” identify characteristics of each block such that a snap shot comparison can be easily made to identify blocks that are different between the primary data storage and the secondary data storage.
- the updating of the data files of the secondary OLTP database is complete and the primary OLTP database is taken out of “hot backup” mode. Thereafter, those transactions that have been recorded, but not yet applied, are then applied.
- the primary OLTP database resumes normal operation using the primary data storage, nominally recording transactions and mirroring the transactions to the secondary storage usable by the secondary OLTP database, as well as applying transactions to the data files of the primary OLTP database as the transactions are received. Some time later (e.g., one hour later or eight hours later), the process is repeated. This process may be, but need not be, performed on a regular basis.
- the secondary data storage includes all the information needed for the secondary OLTP database to take over operation from the primary OLTP database.
- the secondary OLTP database simply applies, against the data files of the secondary storage, all transactions in the redo log file and/or archive log file that have not yet been applied to the data files in the secondary storage.
- the amount of time it will take to apply the as yet unapplied transactions may depend, at least in part, on the number of such transactions.
- the number of such transactions may depend, at least in part, on how long it has been since the data files of the secondary data storage have been updated from the primary data storage.
- FIG. 3 is a flowchart illustrating an example of a method to “fail over” to the secondary data storage from the primary data storage.
- the database is stopped from using the primary data storage, if the primary data storage is even still operating (e.g., the lack of operation of the primary data storage may have triggered the fail over).
- the database configuration parameters are edited to exclude the primary data storage from being used for the redo log, control and archived log files.
- the database is started with the latest mirrored copy of the data files, from the secondary storage.
- the secondary database is recovered using the latest backed up copy of the data files in conjunction with the mirrored copies of the redo logs, control and archived log files.
- the backup OLTP database may be used in place of the primary OLTP database, using the secondary storage, without loss of transactions and with minimal downtime during the transition.
- the backup OLTP database may be “brought current” at any time and operate in place of the primary OLTP database.
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A method is for use with a primary online transactional processing (OLTP) database, to maintain a secondary storage usable by a backup OLTP database, wherein the primary storage, of the primary OLTP database, includes data files. In accordance with the method, as transaction indications for the primary OLTP database are recorded in at least one transaction log file, in the primary storage of the primary OLTP database, the transaction indications are caused to be mirrored to the secondary storage. At the file system level of the storage of the primary OLTP database and of the secondary storage, a state of data files of the primary OLTP database is occasionally caused to be duplicated from the primary storage to the secondary storage.
Description
An online transactional processing (OLTP) database is a repository of transactional data of an enterprise, typically used by the enterprise to store transactional data in real time. An underlying implementation of an OLTP database may be, for example, a commercially available relational database, such as provided by Oracle Corporation.
Given the importance of transactions to a business, it is desirable that no transactions be “lost.” For example, an OLTP database may be used to track customer support issues for an enterprise (e.g., e-mailed customer support inquiries), and it is desirable that none of the customer support issues be lost. In some environments, a backup of the files of an OLTP database may be maintained. However, this backup is typically stored on a storage medium such as a tape and, in the event of a failure of the OLTP database, the downtime to restore the database from the tape can be unacceptably long. In addition, transactions that were received after the backup was created (including those received while the OLTP database is being restored from the backup) will not be present on the backup storage medium and, thus, will not be present in the restored OLTP database.
In accordance with an aspect, a method is for use with a primary online transactional processing (OLTP) database, to maintain a secondary storage usable by a backup OLTP database, wherein the primary storage, of the primary OLTP database, includes data files. In accordance with the method, as transaction indications for the primary OLTP database are recorded in at least one transaction log file, in the primary storage of the primary OLTP database, the transaction indications are caused to be mirrored to the secondary storage. At the file system level of the storage of the primary OLTP database and of the secondary storage, a state of data files of the primary OLTP database is occasionally caused to be duplicated from the primary storage to the secondary storage.
The inventors have realized that it is desirable for OLTP database transactions to continue to be stored in the event primary storage of the OLTP database fails. In addition, it is desirable that secondary (backup) storage be entirely current in the event primary storage of the OLTP database fails.
In accordance with a broad aspect, synchronization of primary storage of an OLTP database with secondary storage of the OLTP database is accomplished by mirroring control files of the database to the secondary storage from which, in the short term, the backup OLTP database can be expediently brought into synchronization with the primary OLTP database. The data itself of the primary OLTP database is occasionally synchronized to the secondary storage. A backup OLTP database, using the secondary storage, may be used in place of the primary OLTP database without loss of transactions. Thus, for example, the backup OLTP database may be “brought current” at any time and operate in place of the primary OLTP database.
Referring to FIG. 1 , the primary OLTP database 102 includes a database server 104 interoperating with database storage 106 implemented by an underlying file system 108. The database storage 106 holds transactional data files including control files 110, redo logs 112 and archived logs 114. The database storage also includes data files 116. The data files 116 include the underlying data stored in the primary OLTP database 102.
The control files 110, redo logs 112 and archived logs 114 include transactional information used and usable in the operation and maintenance of the primary OLTP database 102. That is, the control files 110 are the “brains” of the database, and include information to make the database operate. The redo logs 112 are used to record transactions against the data files 116. For example, if for some reason a transaction is not properly applied to a data file, then the redo logs 112 can be used to construct the proper state of the data files 116. The archived logs 114 include redo logs 112 that have been flushed to the archive.
The backup OLTP database 152 may be similar to the primary OLTP database 102. In the FIG. 1 example, the backup OLTP database 152 includes a database server 154 interoperating with secondary database storage 156 implemented by an underlying file system 158. The secondary database storage 156 holds control files 160, redo logs 162, archived logs 164 and data files 166. The data files 166 include the underlying data stored in the target data warehouse 152, and the control files 160, redo logs 162 and archived logs 164 include metadata used in the operation and maintenance of the target data warehouse 152.
Still referring to FIG. 1 , the system 100 includes a filer synchronizer 180 configured to, at a file system level, take a “snapshot” of the database storage 106 and of the secondary database storage 156. The filer synchronizer 180 is further configured to compare the snapshots and transfer block changes from the database storage 106 to the secondary database storage 156. The filer synchronizer 180 may be, for example, implemented by “Snapshot,” “SnapRestore” and “SnapMirror” products provided by Network Appliance, of Sunnyvale, Calif.
In accordance with one example, in one configuration, the file synchronizer 180 is configured to occasionally synchronize the data files 116 of the primary OLTP database 102 with the data files 166 of the secondary data storage 156, for use by the backup OLTP database 152. For example, the system may be configured such that the file synchronizer 180 synchronizes the data files 116 of the primary OLTP database 102 with the data files 166 of the secondary data storage 156, for use by the backup OLTP database 152, three times per day.
The file synchronizer 180 is not configured to synchronize the control files 110, redo logs 112 and archived logs 114 of the primary OLTP database 102 with the control files 160, redo logs 162 and archived logs 164 of the secondary storage 156, for use by the backup OLTP database 152. Rather, the primary OLTP database 102 is configured such that, during operation of the primary OLTP database 102, as information is being stored into the control files 110, redo logs 112 and archived logs 114 of the primary OLTP database 102, such information is also being stored into the control files 160, redo logs 162 and archived logs 164 of the secondary storage 156, for use by the backup OLTP database 152. For example, for an Oracle database, mirroring functions provided by Oracle may be utilized. Notably, however, while the control files 110, redo logs 112 and archived logs 114 of the primary OLTP database 102 are mirrored to the secondary storage 156, for use by the backup OLTP database 152, the information in these files is not applied to the data files 166 of the secondary storage 156, for use by the backup OLTP database 152, as part of the mirroring operation.
In this way, the control files 160, redo logs 162 and archived logs 164 are always consistent with the control files 110, redo logs 112 and archive log files of the primary data storage 106. More specifically, if there is a need for the backup OLTP database 152 to operate from the secondary storage 156 then, to the extent the backup data files 166 may not be current (i.e., accounting for all transactions, including the most recent transaction), the control files 160, redo logs 162 and archived logs 164 may be utilized to bring the data files 166 current for use by the backup OLTP database 152 current based on the logged transactions.
For Oracle databases, Oracle provides functionality for bringing the data files of a database current based on logged transactions. For example, bringing the data files of a database current may include comparing a “last sequence number” of a transaction accounted for in the data files to sequence numbers of transactions indicated in control files, redo logs or archive logs, to determine whether there are later transactions than those already accounted for in the data files. In the event it is determined that there are such later unaccounted for transactions, these transactions are applied, thus bringing the data files of the database current.
Having described an example system to accomplish synchronization of a primary OLTP database to secondary storage usable by a backup OLTP database, we now describe an example timeline to illustrate an example of the operation (including synchronization) of the primary OLTP database with regard to primary storage and secondary storage. FIG. 2 illustrates such a timeline. Referring to FIG. 2 , in the example, the primary OLTP database is recording and applying transactions prior to 9:00:00 am. That is, the transactions are being recorded in the various control, redo log and archive log files and, in addition, the transactions are being applied to the data files of the primary storage associated with the primary OLTP database. With respect to the secondary storage usable by the backup OLTP database, prior to 9:00:00 am, the transactions are being recorded, by virtue of the mirroring operation, but there is no action with respect to the data files on the secondary storage.
At 9:00:00 am, a “hot backup” mode of the primary OLTP database is initiated, such that the data files of the primary storage are “locked.” That is, the transactions continue to be recorded in the various control, redo log and archive log files of the primary storage, but the transactions are not applied to the data files of the primary storage. In addition, even after 9:00:00 am, the transaction mirroring operation continues, such that the transactions are being recorded to the various control, redo log and archive files of the secondary storage usable by the OLTP database. Thus, even during the backup processing, no transactions are lost.
From 9:10:00 am to 9:10:02 am, a “snap shot” is taken of the data files of the primary OLTP database. After 9:10:02 am, the snap shot taken of the data files of the primary OLTP database is compared to a snap shot of the data files of the secondary OLTP database (which may be, for example, taken at this time or may have been taken earlier). Based on the snap shot comparison, the data files of the secondary storage, usable by the OLTP database, are updated to be consistent with the snap shot of the data files of the primary OLTP database. For example, the underlying file systems of the primary and secondary data storage may operate based on blocks, where the “snap shots” identify characteristics of each block such that a snap shot comparison can be easily made to identify blocks that are different between the primary data storage and the secondary data storage.
At 9:30:02 am, the updating of the data files of the secondary OLTP database is complete and the primary OLTP database is taken out of “hot backup” mode. Thereafter, those transactions that have been recorded, but not yet applied, are then applied. The primary OLTP database resumes normal operation using the primary data storage, nominally recording transactions and mirroring the transactions to the secondary storage usable by the secondary OLTP database, as well as applying transactions to the data files of the primary OLTP database as the transactions are received. Some time later (e.g., one hour later or eight hours later), the process is repeated. This process may be, but need not be, performed on a regular basis.
In general, at any time, the secondary data storage includes all the information needed for the secondary OLTP database to take over operation from the primary OLTP database. When the secondary OLTP database takes over operation from the primary OLTP database, the secondary OLTP database simply applies, against the data files of the secondary storage, all transactions in the redo log file and/or archive log file that have not yet been applied to the data files in the secondary storage. The amount of time it will take to apply the as yet unapplied transactions may depend, at least in part, on the number of such transactions. The number of such transactions may depend, at least in part, on how long it has been since the data files of the secondary data storage have been updated from the primary data storage.
It can thus be seen that the backup OLTP database may be used in place of the primary OLTP database, using the secondary storage, without loss of transactions and with minimal downtime during the transition. In particular, the backup OLTP database may be “brought current” at any time and operate in place of the primary OLTP database.
Claims (12)
1. A method, for use with a primary online transactional processing (OLTP) database, to maintain a secondary storage usable by a backup OLTP database,
wherein primary storage, of the primary OLTP database, is configured to interoperate with a first database server of the primary OLTP database,
secondary storage of the backup OLTP database is configured to interoperate with a second database server of the backup OLTP database, and
the primary storage includes data files of a file system underlying the primary OLTP database, the method comprising:
as transaction indications for the primary OLTP database are recorded in at least one transaction log file, in the primary storage of the primary OLTP database, causing the first database server to mirror the transaction indications to the secondary storage using mirroring functions provided by the first and second database servers;
at a file system level of the primary storage of the primary OLTP database and at a file system level of the secondary storage, occasionally causing changes identified in the data files of the primary OLTP database, including changes in the underlying data stored in the data files, to be copied from the primary storage to the secondary storage via a synchronizer configured to compare a snapshot of the data files of the primary OLTP database to a snapshot of data files of the backup OLTP database without reference to the transaction indications, and to transfer any changes in the data files of the primary OLTP database identified by the comparison from the primary storage to the secondary storage independently of the first database server, wherein further transaction indications continue to be mirrored to the secondary storage during the comparison of the snapshots and the transfer of the changes in the data files of the primary OLTP database, and wherein the further transaction indications are not applied to either the primary OLTP database or the backup OLTP database during the comparison of the snapshots and the transfer of the changes in the data files of the primary OLTP database; and
applying the further transaction indications to the backup OLTP database after the transfer of the changes in the data files of the primary OLTP database.
2. The method of claim 1 , wherein the secondary storage includes data files of a file system underlying the secondary OLTP database, the method further comprising:
applying the transaction indications, that have been mirrored to the secondary storage, to the data files of the secondary storage, whereby the data files of the secondary storage are brought current with the data files of the primary storage.
3. The method of claim 1 , wherein:
occasionally causing changes identified in the data files to be copied from the primary storage to the secondary storage includes:
causing a snap shot of the data files on the primary storage to be compared with a snap shot of the data files on the secondary storage; and
causing changes identified in data files to be copied from the primary storage to the secondary storage based on a result of the comparison.
4. The method of claim 1 , wherein:
causing the first database server to mirror the transaction indications to the secondary storage includes using a standard mirror function of the OLTP database.
5. A system, for use with a primary online transactional processing (OLTP) database, to maintain a secondary storage usable by a backup OLTP database,
wherein primary storage, of the primary OLTP database, is configured to interoperate with a first database server of the primary OLTP database,
secondary storage of the backup OLTP database is configured to interoperate with a second database server of the backup OLTP database, and
the primary storage includes data files of a file system underlying the primary OLTP database, the system including at least one computing device configured to:
as transaction indications for the primary OLTP database are recorded in at least one transaction log file, in the primary storage of the primary OLTP database, cause the first database server to mirror the transaction indications to the secondary storage using mirroring functions provided by the first and second database servers;
at a file system level of the primary storage of the primary OLTP database and at a file system level of the secondary storage, occasionally cause changes identified in the data files of the primary OLTP database, including changes in the underlying data stored in the data files, to be copied from the primary storage to the secondary storage via a synchronizer configured to compare a snapshot of the data files of the primary OLTP database to a snapshot of data files of the backup OLTP database without reference to the transaction indications, and to transfer any changes in the data files of the primary OLTP database identified by the comparison from the primary storage to the secondary storage independently of the first database server, wherein further transaction indications continue to be mirrored to the secondary storage during the comparison of the snapshots and the transfer of the changes in the data files of the primary OLTP database, and wherein the further transaction indications are not applied to either the primary OLTP database or the backup OLTP database during the comparison of the snapshots and the transfer of the changes in the data files of the primary OLTP database; and
apply the further transaction indications to the backup OLTP database after the transfer of the changes in the data files of the primary OLTP database.
6. The system of claim 5 , wherein the secondary storage includes data files of a file system underlying the secondary OLTP database, and the at least one computing device is further configured to:
apply the transaction indications, that have been mirrored to the secondary storage, to the data files of the secondary storage, whereby the data files of the secondary storage are brought current with the data files of the primary storage.
7. The system of claim 5 , wherein:
the at least one computing device being configured to occasionally cause changes identified in the data files to be copied from the primary storage to the secondary storage includes the at least one computing device being configured to:
cause a snap shot of the data files on the primary storage to be compared with a snap shot of the data files on the secondary storage; and
cause changes identified in the data files to be copied from the primary storage to the secondary storage based on a result of the comparison.
8. The system of claim 5 , wherein:
the at least one computing device being configured to cause the first database server to mirror the transaction indications to the secondary storage includes the at least one computing device being configured to use a standard mirror function of the OLTP database.
9. A computer program product for use with a primary online transactional processing (OLTP) database, to maintain a secondary storage located at a backup OLTP database,
wherein primary storage, of the primary OLTP database, is configured to interoperate with a first database server of the primary OLTP database,
secondary storage of the backup OLTP database is configured to interoperate with a second database server of the backup OLTP database, and
the primary storage includes data files of a file system underlying the primary OLTP database, the computer program product comprising at least one non-transitory computer-readable medium having computer program instructions stored therein which are operable to cause at least one computing device to:
as transaction indications for the primary OLTP database are recorded in at least one transaction log file, in the primary storage of the primary OLTP database, cause the first database server to mirror the transaction indications to the secondary storage using mirroring functions provided by the first and second database servers;
at a file system level of the primary storage of the primary OLTP database and at a file system level of the secondary storage, occasionally cause changes identified in the data files of the primary OLTP database, including changes in the underlying data stored in the data files, to be copied from the primary storage to the secondary storage via a synchronizer configured to compare a snapshot of the data files of the primary OLTP database to a snapshot of data files of the backup OLTP database without reference to the transaction indications, and to transfer any changes in the data files of the primary OLTP database identified by the comparison from the primary storage to the secondary storage independently of the first database server, wherein further transaction indications continue to be mirrored to the secondary storage during the comparison of the snapshots and the transfer of the changes in the data files of the primary OLTP database, and wherein the further transaction indications are not applied to either the primary OLTP database or the backup OLTP database during the comparison of the snapshots and the transfer of the changes in the data files of the primary OLTP database; and
apply the further transaction indications to the backup OLTP database after the transfer of the changes in the data files of the primary OLTP database.
10. The computer program product of claim 9 , wherein the secondary storage includes data files of a file system underlying the secondary OLTP database, and the computer program instructions are further operable to cause the at least one computing device to:
apply the transaction indications, that have been mirrored to the secondary storage, to the data files of the secondary storage, whereby the data files of the secondary storage are brought current with the data files of the primary storage.
11. The computer program product of claim 9 , wherein:
the at least one computing device being configured to occasionally cause changes identified in the data files to be copied from the primary storage to the secondary storage includes the at least one computing device being configured to:
cause a snap shot of the data files on the primary storage to be compared with a snap shot of the data files on the secondary storage; and
cause changes identified in data files to be copied from the primary storage to the secondary storage based on a result of the comparison.
12. The computer program product of claim 9 , wherein:
the at least one computing device being configured to cause the first database server to mirror the transaction indications to the secondary storage includes the at least one computing device being configured to use a standard mirror function of the OLTP database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US11/675,368 US8190572B2 (en) | 2007-02-15 | 2007-02-15 | High-availability and data protection of OLTP databases |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US11/675,368 US8190572B2 (en) | 2007-02-15 | 2007-02-15 | High-availability and data protection of OLTP databases |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| US20080201390A1 US20080201390A1 (en) | 2008-08-21 |
| US8190572B2 true US8190572B2 (en) | 2012-05-29 |
Family
ID=39707564
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US11/675,368 Expired - Fee Related US8190572B2 (en) | 2007-02-15 | 2007-02-15 | High-availability and data protection of OLTP databases |
Country Status (1)
| Country | Link |
|---|---|
| US (1) | US8190572B2 (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110225448A1 (en) * | 2006-08-04 | 2011-09-15 | Tsx Inc. | Failover system and method |
| US20130073516A1 (en) * | 2011-06-23 | 2013-03-21 | Alibaba Group Holding Limited | Extracting Incremental Data |
| WO2014197963A1 (en) * | 2013-06-13 | 2014-12-18 | Tsx Inc. | Failover system and method |
| US20160170837A1 (en) * | 2014-06-30 | 2016-06-16 | International Business Machines Corporation | Use of replicated copies to improve database backup performance |
Families Citing this family (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8949395B2 (en) | 2004-06-01 | 2015-02-03 | Inmage Systems, Inc. | Systems and methods of event driven recovery management |
| WO2010079447A1 (en) * | 2009-01-12 | 2010-07-15 | Axxana (Israel) Ltd | Disaster-proof data recovery |
| EP2328089B1 (en) * | 2005-04-20 | 2014-07-09 | Axxana (Israel) Ltd. | Remote data mirroring system |
| US9195397B2 (en) | 2005-04-20 | 2015-11-24 | Axxana (Israel) Ltd. | Disaster-proof data recovery |
| EP2201456A4 (en) * | 2007-10-08 | 2012-02-15 | Axxana Israel Ltd | Fast data recovery system |
| US9098676B2 (en) * | 2008-04-16 | 2015-08-04 | Safenet, Inc. | System and methods for detecting rollback |
| EP2286343A4 (en) * | 2008-05-19 | 2012-02-15 | Axxana Israel Ltd | Resilient data storage in the presence of replication faults and rolling disasters |
| US8069227B2 (en) * | 2008-12-26 | 2011-11-29 | Inmage Systems, Inc. | Configuring hosts of a secondary data storage and recovery system |
| WO2010076755A2 (en) * | 2009-01-05 | 2010-07-08 | Axxana (Israel) Ltd | Disaster-proof storage unit having transmission capabilities |
| US8510263B2 (en) * | 2009-06-15 | 2013-08-13 | Verisign, Inc. | Method and system for auditing transaction data from database operations |
| JP2013501293A (en) * | 2009-08-04 | 2013-01-10 | アクサナ・（イスラエル）・リミテッド | Data gap management in remote data mirroring system |
| WO2011067702A1 (en) | 2009-12-02 | 2011-06-09 | Axxana (Israel) Ltd. | Distributed intelligent network |
| US8311986B2 (en) * | 2010-09-16 | 2012-11-13 | Mimosa Systems, Inc. | Determining database record content changes |
| US9569477B1 (en) * | 2010-12-29 | 2017-02-14 | EMC IP Holding Company LLC | Managing scanning of databases in data storage systems |
| CN103455557B (en) * | 2013-08-08 | 2016-06-29 | 上海新炬网络技术有限公司 | A kind of structural data synchronous method based on daily record |
| WO2015056169A1 (en) | 2013-10-16 | 2015-04-23 | Axxana (Israel) Ltd. | Zero-transaction-loss recovery for database systems |
| US9558078B2 (en) | 2014-10-28 | 2017-01-31 | Microsoft Technology Licensing, Llc | Point in time database restore from storage snapshots |
| US10379958B2 (en) | 2015-06-03 | 2019-08-13 | Axxana (Israel) Ltd. | Fast archiving for database systems |
| US10592326B2 (en) | 2017-03-08 | 2020-03-17 | Axxana (Israel) Ltd. | Method and apparatus for data loss assessment |
| CN108614892A (en) * | 2018-05-09 | 2018-10-02 | 浪潮软件集团有限公司 | Oracle data real-time synchronization method based on redolog |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020049776A1 (en) * | 2000-02-11 | 2002-04-25 | Aronoff Eyal M. | System and method for reconciling transactions between a replication system and a recovered database |
| US20030037029A1 (en) * | 2001-08-15 | 2003-02-20 | Iti, Inc. | Synchronization of plural databases in a database replication system |
| US20030182325A1 (en) * | 2002-03-19 | 2003-09-25 | Manley Stephen L. | System and method for asynchronous mirroring of snapshots at a destination using a purgatory directory and inode mapping |
| US20030182326A1 (en) * | 2002-03-19 | 2003-09-25 | Hugo Patterson | System and method for coalescing a plurality of snapshots |
| US20040158549A1 (en) * | 2003-02-07 | 2004-08-12 | Vladimir Matena | Method and apparatus for online transaction processing |
| US6877016B1 (en) * | 2001-09-13 | 2005-04-05 | Unisys Corporation | Method of capturing a physically consistent mirrored snapshot of an online database |
| US20050138461A1 (en) * | 2003-11-24 | 2005-06-23 | Tsx Inc. | System and method for failover |
| US6957221B1 (en) * | 2002-09-05 | 2005-10-18 | Unisys Corporation | Method for capturing a physically consistent mirrored snapshot of an online database from a remote database backup system |
-
2007
- 2007-02-15 US US11/675,368 patent/US8190572B2/en not_active Expired - Fee Related
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020049776A1 (en) * | 2000-02-11 | 2002-04-25 | Aronoff Eyal M. | System and method for reconciling transactions between a replication system and a recovered database |
| US20030037029A1 (en) * | 2001-08-15 | 2003-02-20 | Iti, Inc. | Synchronization of plural databases in a database replication system |
| US6877016B1 (en) * | 2001-09-13 | 2005-04-05 | Unisys Corporation | Method of capturing a physically consistent mirrored snapshot of an online database |
| US20030182325A1 (en) * | 2002-03-19 | 2003-09-25 | Manley Stephen L. | System and method for asynchronous mirroring of snapshots at a destination using a purgatory directory and inode mapping |
| US20030182326A1 (en) * | 2002-03-19 | 2003-09-25 | Hugo Patterson | System and method for coalescing a plurality of snapshots |
| US6957221B1 (en) * | 2002-09-05 | 2005-10-18 | Unisys Corporation | Method for capturing a physically consistent mirrored snapshot of an online database from a remote database backup system |
| US20040158549A1 (en) * | 2003-02-07 | 2004-08-12 | Vladimir Matena | Method and apparatus for online transaction processing |
| US20050138461A1 (en) * | 2003-11-24 | 2005-06-23 | Tsx Inc. | System and method for failover |
Non-Patent Citations (5)
| Title |
|---|
| Lee et al., "Technical Report : Cloning Oracle® E-Business Suite Using SnapMirror®", Jan. 15, 2004, Downloaded from http://www.netapp.com/library/tr/3300.pdf, Feb. 15, 2007. |
| Network Appliance Inc., "Network Appliance(TM) Snapmirror® Software", (c) 2006, Downloaded from http://www.netapp.com/ftp/snapmirror.pdf, Feb. 15, 2007. |
| Network Appliance Inc., "Network Appliance(TM) Technology Deployment At Oracle: Making Complex Storage Environments Simpler to Manage with a Low TCO", Aug. 2004, Downloaded from http://www.netapp.com/library/tr/3330.pdf, Feb. 15, 2007. |
| Network Appliance Inc., "Network Appliance™ Snapmirror® Software", (c) 2006, Downloaded from http://www.netapp.com/ftp/snapmirror.pdf, Feb. 15, 2007. |
| Network Appliance Inc., "Network Appliance™ Technology Deployment At Oracle: Making Complex Storage Environments Simpler to Manage with a Low TCO", Aug. 2004, Downloaded from http://www.netapp.com/library/tr/3330.pdf, Feb. 15, 2007. |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110225448A1 (en) * | 2006-08-04 | 2011-09-15 | Tsx Inc. | Failover system and method |
| US8683257B2 (en) | 2006-08-04 | 2014-03-25 | Tsx Inc. | Failover system and method |
| US20130073516A1 (en) * | 2011-06-23 | 2013-03-21 | Alibaba Group Holding Limited | Extracting Incremental Data |
| WO2014197963A1 (en) * | 2013-06-13 | 2014-12-18 | Tsx Inc. | Failover system and method |
| US9798639B2 (en) | 2013-06-13 | 2017-10-24 | Tsx Inc. | Failover system and method replicating client message to backup server from primary server |
| US20160170837A1 (en) * | 2014-06-30 | 2016-06-16 | International Business Machines Corporation | Use of replicated copies to improve database backup performance |
| US10078557B2 (en) | 2014-06-30 | 2018-09-18 | International Business Machines Corporation | Use of replicated copies to improve database backup performance |
| US10108496B2 (en) | 2014-06-30 | 2018-10-23 | International Business Machines Corporation | Use of replicated copies to improve database backup performance |
Also Published As
| Publication number | Publication date |
|---|---|
| US20080201390A1 (en) | 2008-08-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8190572B2 (en) | High-availability and data protection of OLTP databases | |
| US11740974B2 (en) | Restoring a database using a fully hydrated backup | |
| EP1540510B1 (en) | Method and apparatus for managing data integrity of backup and disaster recovery data | |
| US9251008B2 (en) | Client object replication between a first backup server and a second backup server | |
| US7310654B2 (en) | Method and system for providing image incremental and disaster recovery | |
| US9830223B1 (en) | Methods for repairing a corrupted database to a new, correct state | |
| US7953707B2 (en) | System and program product for sequential coordination of external database application events with asynchronous internal database events | |
| US8429121B2 (en) | Apparatus and method for creating a real time database replica | |
| US6065018A (en) | Synchronizing recovery log having time stamp to a remote site for disaster recovery of a primary database having related hierarchial and relational databases | |
| EP3451173B1 (en) | Restoring a database using a fully hydrated backup | |
| US7685189B2 (en) | Optimizing backup and recovery utilizing change tracking | |
| US20060235905A1 (en) | Method and system for preserving real-time access to a system in case of a disaster | |
| US7801867B2 (en) | Optimizing backup and recovery utilizing change tracking | |
| US10922186B1 (en) | Method and system for implementing current, consistent, and complete backups by rolling a change log backwards | |
| US10282256B1 (en) | System and method to enable deduplication engine to sustain operational continuity | |
| US7725428B1 (en) | System and method for restoring a database in a distributed database system | |
| US20170300387A1 (en) | Always Current backup and recovery method on large databases with minimum resource utilization. | |
| EP1715425A2 (en) | Method and system for preserving access to a system in case of a disaster | |
| US11874751B2 (en) | Operating a data center | |
| Korotkevitch et al. | Backup and Restore | |
| GB2425376A (en) | Method and system for producing a data backup system of a primary system in a document management system | |
| CA2545532A1 (en) | Method and system for providing network attached system for disaster recovery and upgrade testing | |
| CA2531714C (en) | A method and system for preserving access to a system in case of a disaster | |
| Sack | Backup and Recovery | |
| Kuhn et al. | Backup and Recovery 101 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| AS | Assignment |
Owner name: YAHOO! INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ANGUELOV, TRIFON M.;REEL/FRAME:018895/0484 Effective date: 20070214 |
|
| ZAAA | Notice of allowance and fees due |
Free format text: ORIGINAL CODE: NOA |
|
| ZAAB | Notice of allowance mailed |
Free format text: ORIGINAL CODE: MN/=. |
|
| STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
| FPAY | Fee payment |
Year of fee payment: 4 |
|
| AS | Assignment |
Owner name: EXCALIBUR IP, LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:YAHOO! INC.;REEL/FRAME:038383/0466 Effective date: 20160418 |
|
| AS | Assignment |
Owner name: YAHOO! INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EXCALIBUR IP, LLC;REEL/FRAME:038951/0295 Effective date: 20160531 |
|
| AS | Assignment |
Owner name: EXCALIBUR IP, LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:YAHOO! INC.;REEL/FRAME:038950/0592 Effective date: 20160531 |
|
| MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
| AS | Assignment |
Owner name: STARBOARD VALUE INTERMEDIATE FUND LP, AS COLLATERAL AGENT, NEW YORK Free format text: PATENT SECURITY AGREEMENT;ASSIGNORS:ACACIA RESEARCH GROUP LLC;AMERICAN VEHICULAR SCIENCES LLC;BONUTTI SKELETAL INNOVATIONS LLC;AND OTHERS;REEL/FRAME:052853/0153 Effective date: 20200604 |
|
| AS | Assignment |
Owner name: R2 SOLUTIONS LLC, TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EXCALIBUR IP, LLC;REEL/FRAME:053459/0059 Effective date: 20200428 |
|
| AS | Assignment |
Owner name: CELLULAR COMMUNICATIONS EQUIPMENT LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: PARTHENON UNIFIED MEMORY ARCHITECTURE LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: INNOVATIVE DISPLAY TECHNOLOGIES LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: TELECONFERENCE SYSTEMS LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: R2 SOLUTIONS LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: UNIFICATION TECHNOLOGIES LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: MONARCH NETWORKING SOLUTIONS LLC, CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: LIMESTONE MEMORY SYSTEMS LLC, CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: ACACIA RESEARCH GROUP LLC, NEW YORK Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: STINGRAY IP SOLUTIONS LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: NEXUS DISPLAY TECHNOLOGIES LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: SUPER INTERCONNECT TECHNOLOGIES LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: LIFEPORT SCIENCES LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: SAINT LAWRENCE COMMUNICATIONS LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: MOBILE ENHANCEMENT SOLUTIONS LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: BONUTTI SKELETAL INNOVATIONS LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 Owner name: AMERICAN VEHICULAR SCIENCES LLC, TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:053654/0254 Effective date: 20200630 |
|
| AS | Assignment |
Owner name: R2 SOLUTIONS LLC, TEXAS Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE NAME PREVIOUSLY RECORDED ON REEL 053654 FRAME 0254. ASSIGNOR(S) HEREBY CONFIRMS THE RELEASE OF SECURITY INTEREST GRANTED PURSUANT TO THE PATENT SECURITY AGREEMENT PREVIOUSLY RECORDED;ASSIGNOR:STARBOARD VALUE INTERMEDIATE FUND LP;REEL/FRAME:054981/0377 Effective date: 20200630 |
|
| AS | Assignment |
Owner name: STARBOARD VALUE INTERMEDIATE FUND LP, AS COLLATERAL AGENT, NEW YORK Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE THE ASSIGNOR NAME PREVIOUSLY RECORDED AT REEL: 052853 FRAME: 0153. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:R2 SOLUTIONS LLC;REEL/FRAME:056832/0001 Effective date: 20200604 |
|
| FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
| STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
| FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20240529 |