CN117632598B - GBase8a database online backup method - Google Patents
GBase8a database online backup method Download PDFInfo
- Publication number
- CN117632598B CN117632598B CN202410090318.7A CN202410090318A CN117632598B CN 117632598 B CN117632598 B CN 117632598B CN 202410090318 A CN202410090318 A CN 202410090318A CN 117632598 B CN117632598 B CN 117632598B
- Authority
- CN
- China
- Prior art keywords
- lock
- backup
- database
- data
- gbase8a
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 55
- 239000012634 fragment Substances 0.000 claims description 46
- 238000011084 recovery Methods 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 abstract description 21
- 230000002159 abnormal effect Effects 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 230000008602 contraction Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000002427 irreversible effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an online backup method of GBase8a database, which comprises the following steps: locking the database to be backed up, including adding meta sharing lock, hashmap sharing lock, execute sharing lock and db exclusive lock, and then carrying out metadata backup; releasing hashmap shared lock, execution shared lock and db exclusive lock of the database to be backed up, and then carrying out table data backup; releasing meta sharing lock. In the invention, the staged backup of the database is realized through the addition and the stepwise release of the meta sharing lock, the hashmap sharing lock, the execution sharing lock and the db exclusive lock, so that the DML operation can be normally carried out in most of the backup time of the database, and the meta sharing lock is held in the whole process of the database in the backup process, thereby ensuring the integrity and the consistency of the database.
Description
Technical Field
The invention belongs to the technical field of computers, and particularly relates to an online backup method for GBase8a databases.
Background
With the development of computer technology, databases are widely used in various industries, and databases based on relational models, represented by Oracle, are well accepted by various industries for their excellent performance and security. For the storage scene of mass data, a single database is insufficient, so that more enterprises select distributed databases, and the GBase8a database is widely applied as a relational database product with a distributed architecture along with the influence of domestic trend.
In practical applications, the GBase8a database may have irreversible abnormal conditions during operation, for example: disk damage, node anomalies, or human error delete data, etc. In order to cope with such abnormal conditions, data backup and restoration are required.
However, the current GBase8a database has long backup time, and both DDL operation and DML operation of the database are limited for a long time in the backup process, which affects the use experience of users. Therefore, it is important to design a more reasonable backup mode of the GBase8a database.
Disclosure of Invention
Therefore, the invention aims to provide an online backup method for GBase8a databases, so as to reduce the limitation of the backup process on database operation.
In order to achieve the above purpose, the technical scheme of the invention is realized as follows:
an online backup method of GBase8a database comprises the following steps:
locking the database to be backed up, including adding meta sharing lock, hashmap sharing lock, execute sharing lock and db exclusive lock, and then carrying out metadata backup;
releasing hashmap shared lock, execution shared lock and db exclusive lock of the database to be backed up, and then carrying out table data backup;
releasing meta sharing lock.
Further, the database to be backed up comprises data of the main shard and data of the backup shard, and the GBase8a database online backup method is carried out on the data of the main shard.
Further, before the locking operation is performed on the database to be backed up, the method further includes:
acquiring the distribution information of the main fragments and the backup fragments of the database to be backed up;
and extracting the data of the main fragments according to the distribution information of the main fragments so as to perform locking operation.
Further, the backup data of the GBase8a database is subjected to data recovery according to the distribution information of the main fragments and the backup fragments.
An electronic device comprises a processor and a memory which is in communication connection with the processor and is used for storing executable instructions of the processor, wherein the processor is used for executing the GBase8a database online backup method.
A server comprising at least one processor and a memory communicatively coupled to the processor, the memory storing instructions executable by the at least one processor, the instructions being executable by the processor to cause the at least one processor to perform the GBase8a database online backup method described above.
A computer readable storage medium storing a computer program which when executed by a processor implements the GBase8a database online backup method described above.
An online backup device for GBase8a database, comprising:
the user interface module is used for receiving the backup command and transmitting the backup command to the control module;
the control module is used for executing locking operation according to the input backup command and releasing the locking operation when receiving the execution completion instruction input by the execution module;
the execution module is used for executing backup operation of the metadata and the table data and transmitting the executed instruction to the control module;
the storage module is used for receiving the backup data of the metadata and the table data and storing the backup data in the local/remote end;
and the exception handling module is used for reporting errors and exiting when the user interface module, the control module, the execution module and the storage module are abnormal in the database backup process.
Compared with the prior art, the online backup method for the GBase8a database has the following advantages:
according to the GBase8a database online backup method, the staged backup of the database is realized through the addition and the step release of the meta sharing lock, the hashmap sharing lock, the execution sharing lock and the db exclusive lock, so that the DML operation can be normally performed in most of the backup time of the database, and the meta sharing lock is held in the whole process of the database in the backup process, so that the integrity and the consistency of the database can be ensured.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute an undue limitation on the invention. In the drawings:
FIG. 1 shows a flowchart of an online backup method for GBase8a databases according to an embodiment of the invention;
FIG. 2 shows a flowchart of a single copy backup of the GBase8a database online backup method according to an embodiment of the invention;
fig. 3 shows a schematic structural diagram of an online GBase8a database backup device according to an embodiment of the invention.
Detailed Description
It should be noted that, without conflict, the embodiments of the present invention and features of the embodiments may be combined with each other.
The invention will be described in detail below with reference to the drawings in connection with embodiments.
FIG. 1 shows a flowchart of a GBase8a database online backup method according to an embodiment of the disclosure. As shown in fig. 1, the GBase8a database online backup method S100 includes the following steps:
step S110, locking operation is carried out on the database to be backed up, including adding meta sharing lock, hashmap sharing lock, execution sharing lock and db exclusive lock, and then metadata backup is carried out.
In this embodiment, the GBase8a database online backup method is used as an online backup recovery tool independent of the GBase8a database, and when in use, a user sends an online backup command to a server through a client, and the server performs locking operation according to the online backup command.
In database systems, locks are a mechanism for controlling the operation of concurrent access to database objects (e.g., tables, rows, pages, etc.). It may ensure that when a certain transaction modifies or reads data, other transactions cannot simultaneously modify the same data, thereby maintaining the consistency and integrity of the data. Shared locks and exclusive locks are two types of locks that are common in databases.
In particular, shared locks allow multiple transactions to be held simultaneously to read locked data without interfering with each other to provide read consistency in a concurrent environment, but do not allow write operations. Exclusive locks are used to ensure exclusive access to resources during execution of a transaction, ensuring that no other transactions modify the locked data.
In this embodiment, the meta sharing lock is a lock for protecting metadata, which can prevent other transactions from modifying metadata, such as a conventional DDL operation drop library, etc.; the hashmap sharing lock is a lock for protecting hashmap values, and can prevent other transactions from writing hashmap values, and the operation does not directly modify metadata content, but also affects the accuracy of metadata in the metadata backup process; the execution sharing lock is a lock for protecting the DML operation of data in a table, and can prevent other transactions from performing DML write operation on the table, such as insert operation, which can add content in the related file of the metadata instead of direct modification and can influence the accuracy of the metadata in the metadata backup process; the db exclusive lock is an exclusive lock for protecting the operation of the library level, and can prevent other transactions from performing DDL operation on the whole database, such as drop library and the like.
In summary, in order to avoid the influence of other transactions or operations on the data backup transaction, for example, when metadata is being backed up, other transactions of the database modify metadata, which may cause errors in the backup data and cannot be recovered, the embodiment prevents the metadata from being modified in the backup process by adding meta shared lock, hashmap shared lock, execute shared lock and db exclusive lock, thereby ensuring the accuracy of the backup data. In addition, in the backup operation of the GBase8a database, the metadata backup stage is shorter than the table data backup stage, and the metadata backup can block DDL operation and DML operation, but not block Select operation until the metadata backup is completed. Therefore, in order to realize the requirement of online backup, that is, reduce the influence on DML operation in the backup process, the embodiment adopts a staged backup mode, that is, first performs metadata backup and then performs table data backup. After the metadata backup is completed, only the meta sharing lock locking state is reserved, and the hashmap sharing lock, the execute sharing lock and the db exclusive lock are released so as to ensure normal execution of the DML operation (except for full column update) in the table data backup process.
Step S120, releasing hashmap shared lock, execution shared lock and db exclusive lock of the database to be backed up, and then carrying out table data backup.
In this embodiment, after the metadata backup is completed, hashmap shared lock, execute shared lock, and db exclusive lock are released, but meta shared lock is not released. The meta sharing lock is not released to ensure that metadata is not modified, and the hashmap sharing lock, the execute sharing lock and the db exclusive lock are released to realize that DML operation is not blocked in the subsequent table data backup stage, so that normal operation of the DML operation is ensured in the table backup process of the main time-consuming stage of the backup operation, and the influence of the backup operation on a database is reduced.
Specifically, the method of holding the meta shared lock in the whole process of data backup is adopted in this embodiment, so as to avoid modification of metadata by other transactions or operations in the process of table data backup, for example, when certain table data is being backed up, the other transactions of the database execute drop table operations, which may cause loss of table data and thus cannot be recovered, thereby ensuring integrity and accuracy of table data.
In addition, after the hashmap shared lock, the execution shared lock and the db exclusive lock are released, the backup transaction blocks the DDL operation, but does not block the DML operation, for example, the insert operation of the table does not modify the metadata content and only adds the relevant information, so that the backup transaction can be normally executed, but the operation which can modify the metadata content for the full column update is still blocked.
The influence scope and the content of the table data backup are different according to whether the table relates to backup and whether the backup is completed, DDL and DML operations are not blocked for the table which does not relate to backup and the table which is completed after the backup, the application is not influenced, the DML operations are not blocked (except for full-column update) for the table which is being backed up and the table of the backup queue, and the DDL operations are blocked until the table data backup is completed; normal operation can be performed on the backed up tables, DDL and DML operation are not blocked, and application is not affected.
In this embodiment, in the subsequent recovery stage, table data recovery is performed through the metadata backed up before, for example, ten records are originally in the table, backup is started, three records are inserted before the table data backup after the metadata is backed up, and finally thirteen records are backed up.
Step S130, releasing the meta sharing lock.
After all data backups are completed, the meta sharing lock is released, and DDL operation and DML operation can be normally executed at the moment, so that the application is not influenced. After meta sharing lock is released, the current backup transaction is completed.
In this embodiment, the GBase8a database is backed up to the local/remote end. The remote backup calls a write interface of a third party, directly writes the backup file into the remote end, and the remote recovery calls a read interface of the third party, so as to read the backup file to a designated address.
According to the GBase8a database online backup method, before metadata backup, meta sharing locks, hashmap sharing locks, exect sharing locks and db exclusive locks are added, after the metadata backup is successful, metadata backup is executed, after the metadata backup is error-free, hashmap sharing locks, exect sharing locks and db exclusive locks are released, and meta sharing locks are not released until table data backup is completed. By the method, the conventional DML operation of the database is not blocked in the process of table data backup, and the integrity and consistency of data backup and recovery are ensured by holding the meta sharing lock in the whole process of backup.
FIG. 2 shows a flowchart of a single copy backup of the GBase8a database online backup method according to an embodiment of the invention.
In some embodiments, the data node of the database generally has a plurality of data fragments, including a main fragment and a backup fragment, so that in this embodiment, in order to increase the backup speed and reduce the occupation of the disk space of the server, in both metadata backup and table data backup stages, a single copy backup mode is adopted, that is, only the data of the main fragment is backed up, and in the recovery stage, the data of the backup fragment is also recovered through the main fragment.
Illustratively, if a database has three data nodes, node1, node2, and node3, respectively, each having a primary and a backup shard, then the ideal distribution for the data is: the node1 has the main fragments of test_n1 and the backup fragments of test_n2, the node2 has the main fragments of test_n2 and the backup fragments of test_n3, and the node3 has the main fragments of test_n3 and the backup fragments of test_n1. For this scenario, if all data is backed up, it is equivalent to backing up two sets of identical data, in order to increase the backup speed and reduce the occupation of the disk space of the server, this embodiment adopts a single copy backup mode, and only the main piece of data of each data node is backed up, that is, only one set of complete data (test_n1 of node1, test_n2 of node2, and test_n3 of node 3) is backed up.
Referring to fig. 2, the single copy backup process includes the following steps:
1. and acquiring the distribution information of the main fragments and the backup fragments of each data node.
And acquiring the distribution information of the main fragments and the backup fragments of each data node by calling the related interfaces, and extracting the distribution information of the main fragments of each data node for subsequent data backup.
2. And storing the distribution information of the main fragments and the backup fragments of each data node.
The strategy of single copy backup is to backup only one set of complete data, but the data of the backup fragments need to be restored together when the data is restored, in order to correctly restore the data of the backup fragments, the accuracy and consistency of the data restoration stage are ensured, the distribution information of the main fragments and the backup fragments of each data node needs to be stored into a file, and the file and the backup data are stored into a local/remote server together in the data backup stage.
3. Backup the data of the main shard.
And backing up the data of the main fragments of each data node to a local/remote server according to the distribution information of the main fragments of each data node acquired before. At this time, the data after the backup is a complete set of test_n1, test_n2, and test_n3.
4. And recovering the data through the distribution information of the main fragments and the backup fragments of each data node.
In the data recovery stage, the file which is stored together with the backup data and stores the distribution information of the main fragments and the backup fragments of each data node is read first, the fragment distribution condition of each data node is confirmed, and then the data of the backed up main fragments is used for data recovery. For example, when the slices corresponding to the node1 are test_n1 and test_n2, from the previously backed up test_n1 data, the test_n1 and the test_n2 are restored to the node1 according to the distribution information of the main slice and the backup slice. Only one complete set of data is needed to complete the recovery of all node data.
Fig. 3 shows a schematic structural diagram of an online GBase8a database backup device according to an embodiment of the invention. As shown in FIG. 3, the GBase8a database online backup device comprises a user interface module, a control module, an execution module, a storage module and an exception handling module.
Specifically, a user inputs an online backup/restore command through a client, enters a user interface module, performs validity check and special character processing on the command and parameters input by the user in the user interface module, checks a storage position designated by the user, and then transmits a message to a control module to inform the control module what the user needs to do.
The control module is responsible for flow control of the program, such as backup of which tables, locking, unlocking, checking whether the capacity expansion and contraction operation is performed when recovering, whether the topology structure is changed, etc., and is the most important part of the program. Specifically, after receiving a backup instruction transmitted from the user interface module, the control module needs to perform locking operation; if the execution completion instruction transmitted by the execution module is received, the control module needs to execute the operation of releasing the lock.
The execution module is responsible for specific backup/recovery, and after the backup/recovery is finished, the execution module interacts with the control module to inform the control module that the lock can be released. It should be noted that, the interaction between the control module and the execution module belongs to the internal interaction of the program, and the following information needs to be transmitted during the module interaction: the content to be backed up or already backed up, the level of backup, whether the metadata is consistent, the location of the backup data, and the success or failure of backup.
The storage module takes the data (in the form of path/buffer and the like) to be stored from the execution module, reads the data and puts the data to the far end/local, or gives the data stored in the far end/local to the execution module, and the execution module executes recovery.
The exception handling module is used for handling the possible exception condition of each module in the actual execution process of the program, and if the exception occurs to all the modules, the process goes to the exception handling module to report the error and exit. Abnormal conditions include, but are not limited to: command errors, parameter errors, illegal parameters, unavailable storage locations or insufficient space of the user interface module; the flow control of the control module is problematic, and the communication with the execution module is problematic; the execution module finds out that the data are different in the backup process, the topological structure is different in the recovery process, or the capacity expansion/contraction operation is carried out, and the communication between the execution module and the control module is problematic; problems arise in connection with the remote end during storage in the storage module. Backup and restore common anomalies: a failed start backup (locking), a failed metadata backup, a failed table data backup, a failed multi-table backup of one table, an incorrect backup file, a failed database recovery, and a failed table recovery.
Those of ordinary skill in the art will appreciate that the elements and method steps of each example described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the elements and steps of each example have been described generally in terms of functionality in the foregoing description to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the several embodiments provided in this application, it should be understood that the disclosed methods and systems may be implemented in other ways. For example, the above-described division of units is merely a logical function division, and there may be another division manner when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted or not performed. The units may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment of the present invention.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention, and are intended to be included within the scope of the appended claims and description.
The foregoing description of the preferred embodiments of the invention is not intended to be limiting, but rather is intended to cover all modifications, equivalents, alternatives, and improvements that fall within the spirit and scope of the invention.
Claims (8)
1. An online backup method for GBase8a databases is characterized by comprising the following steps: the method comprises the following steps:
locking the database to be backed up, including adding meta sharing lock, hashmap sharing lock, execute sharing lock and db exclusive lock, and then carrying out metadata backup; meta sharing lock is a lock for protecting metadata, which can prevent other transactions from modifying metadata; the hashmap shared lock is a lock for protecting hashmap values, and can prevent other transactions from writing hashmap values; an execution shared lock is a lock used for protecting data DML operations in a table, and can prevent other transactions from performing DML write operations on the table; the db exclusive lock is an exclusive lock for protecting the operation of the database level, and can prevent other transactions from performing DDL operation on the whole database;
releasing hashmap shared lock, execution shared lock and db exclusive lock of the database to be backed up, and then carrying out table data backup;
releasing meta sharing lock.
2. The GBase8a database online backup method according to claim 1, wherein the steps of: the database to be backed up comprises data of a main fragment and data of a backup fragment, and the GBase8a database online backup method is carried out on the data of the main fragment.
3. The GBase8a database online backup method according to claim 2, wherein: before the locking operation is performed on the database to be backed up, the method further comprises the following steps:
acquiring the distribution information of the main fragments and the backup fragments of the database to be backed up;
and extracting the data of the main fragments according to the distribution information of the main fragments so as to perform locking operation.
4. The GBase8a database online backup method according to claim 3, wherein: and the backup data of the GBase8a database is subjected to data recovery according to the distribution information of the main fragments and the backup fragments.
5. An electronic device comprising a processor and a memory communicatively coupled to the processor for storing processor-executable instructions, characterized in that: the processor is configured to execute the GBase8a database online backup method according to any one of claims 1 to 4.
6. A server, characterized by: comprising at least one processor and a memory communicatively coupled to the processor, the memory storing instructions executable by the at least one processor to cause the at least one processor to perform the GBase8a database online backup method according to any one of claims 1-4.
7. A computer-readable storage medium storing a computer program, characterized in that: the computer program, when executed by a processor, implements the GBase8a database online backup method according to any one of claims 1 to 4.
8. An online backup device for a GBase8a database, which is characterized in that: comprising the following steps:
the locking backup module is used for carrying out locking operation on the database to be backed up, and comprises the steps of adding meta sharing lock, hashmap sharing lock, execution sharing lock and db exclusive lock, and then carrying out metadata backup; meta sharing lock is a lock for protecting metadata, which can prevent other transactions from modifying metadata; the hashmap shared lock is a lock for protecting hashmap values, and can prevent other transactions from writing hashmap values; an execution shared lock is a lock used for protecting data DML operations in a table, and can prevent other transactions from performing DML write operations on the table; the db exclusive lock is an exclusive lock for protecting the operation of the database level, and can prevent other transactions from performing DDL operation on the whole database;
unlocking a backup module, which is used for releasing the hashmap shared lock, the execution shared lock and the db exclusive lock of the database to be backed up, and then carrying out table data backup;
and the unlocking module is used for releasing the meta sharing lock.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410090318.7A CN117632598B (en) | 2024-01-23 | 2024-01-23 | GBase8a database online backup method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410090318.7A CN117632598B (en) | 2024-01-23 | 2024-01-23 | GBase8a database online backup method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117632598A CN117632598A (en) | 2024-03-01 |
| CN117632598B true CN117632598B (en) | 2024-04-09 |
Family
ID=90030723
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410090318.7A Active CN117632598B (en) | 2024-01-23 | 2024-01-23 | GBase8a database online backup method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117632598B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6658589B1 (en) * | 1999-12-20 | 2003-12-02 | Emc Corporation | System and method for backup a parallel server data storage system |
| CN103677967A (en) * | 2012-09-03 | 2014-03-26 | 阿里巴巴集团控股有限公司 | Remote data service system of data base and task scheduling method |
| CN104166600A (en) * | 2014-08-01 | 2014-11-26 | 腾讯科技（深圳）有限公司 | Data backup and recovery methods and devices |
| CN113608694A (en) * | 2021-07-27 | 2021-11-05 | 北京达佳互联信息技术有限公司 | Data migration method, information processing method, device, server and medium |
| CN116483628A (en) * | 2023-05-11 | 2023-07-25 | 瀚高基础软件股份有限公司 | Distributed backup method and system based on locking |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11042620B2 (en) * | 2019-03-05 | 2021-06-22 | King Abdulaziz University | Securing electronic documents with fingerprint/biometric data |
-
2024
- 2024-01-23 CN CN202410090318.7A patent/CN117632598B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6658589B1 (en) * | 1999-12-20 | 2003-12-02 | Emc Corporation | System and method for backup a parallel server data storage system |
| CN103677967A (en) * | 2012-09-03 | 2014-03-26 | 阿里巴巴集团控股有限公司 | Remote data service system of data base and task scheduling method |
| CN104166600A (en) * | 2014-08-01 | 2014-11-26 | 腾讯科技（深圳）有限公司 | Data backup and recovery methods and devices |
| CN113608694A (en) * | 2021-07-27 | 2021-11-05 | 北京达佳互联信息技术有限公司 | Data migration method, information processing method, device, server and medium |
| CN116483628A (en) * | 2023-05-11 | 2023-07-25 | 瀚高基础软件股份有限公司 | Distributed backup method and system based on locking |
Non-Patent Citations (2)
| Title |
|---|
| Ricardo Filipe et al..Stretching the capacity of Hardware Transactional Memory in IBM POWER architectures.《PPoPP '19: Proceedings of the 24th Symposium on Principles and Practice of Parallel Programming》.2019,107–119. * |
| 基于智能存储设备的共享存储集群系统研究;黄蓉;俞建新;;计算机工程与设计;20070823(第16期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117632598A (en) | 2024-03-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100440155C (en) | Method and apparatus for creating a virtual data copy | |
| CN111753013B (en) | Distributed transaction processing method and device | |
| US8464101B1 (en) | CAS command network replication | |
| US8589649B2 (en) | Computer system and method of notifying error information of the computer system | |
| US7200626B1 (en) | System and method for verification of a quiesced database copy | |
| KR100983300B1 (en) | Recovery from failures within data processing systems | |
| US8214612B1 (en) | Ensuring consistency of replicated volumes | |
| CN113396407A (en) | System and method for augmenting database applications using blockchain techniques | |
| CN108509462B (en) | Method and device for synchronizing activity transaction table | |
| US20070239758A1 (en) | Loosely Coupled Log Sequence Identifiers | |
| CN104793988A (en) | Cross-database distributed transaction implementation method and device | |
| US20090063807A1 (en) | Data redistribution in shared nothing architecture | |
| US9330153B2 (en) | System, method, and computer readable medium that coordinates between devices using exchange of log files | |
| CN107533474B (en) | Transaction processing method and device | |
| CN110825546A (en) | Recovery method, system and equipment terminal for high-availability database cluster | |
| CN112905613A (en) | Data bidirectional synchronization method and device for heterogeneous database | |
| US20230315713A1 (en) | Operation request processing method, apparatus, device, readable storage medium, and system | |
| CN110737716B (en) | Data writing method and device | |
| CN105938446B (en) | The data supported based on RDMA and hardware transactional memory replicate fault-tolerance approach | |
| CN111352766A (en) | Database double-activity implementation method and device | |
| CN117632598B (en) | GBase8a database online backup method | |
| US7051051B1 (en) | Recovering from failed operations in a database system | |
| CN110704239B (en) | Data copying method and device and electronic equipment | |
| CN114791901A (en) | Data processing method, device, equipment and storage medium | |
| US7627873B1 (en) | System and method for handling device objects in a data storage environment for maintaining consistency during data replication |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |