Testing database replication with multi-container system architecture
US-2018253481-A1 · Sep 6, 2018 · US
US10496677B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10496677-B2 |
| Application number | US-201715589720-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 8, 2017 |
| Priority date | May 8, 2017 |
| Publication date | Dec 3, 2019 |
| Grant date | Dec 3, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Replicating a tenant database includes receiving at a source system a first request from a target system for replicating a first tenant database of the source system, which includes one or more first servers. Characteristics of the one or more first servers are sent to the target system to generate at the target system a second tenant database including one or more second servers. Each second server corresponds to one first server and has the same characteristics as the corresponding first server. Information from each first server is replicated, in an asynchronous mode, to the corresponding second server through a communication channel that is established between each first server and the second server. Upon receiving a second request for stopping the replication, a synchronous mode of processing statements from client applications of the first tenant database is entered. Related apparatus, systems, techniques and articles are described.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method for replicating a tenant database from a source system to a target system, the method comprising: receiving, at a source system, a first request from a target system for replicating a first tenant database of the source system, the first tenant database including one or more first servers; sending to the target system characteristics of the one or more first servers included in the first tenant database to generate at the target system a second tenant database including one or more second servers, each second server corresponding to one first server and having the same characteristics as the corresponding first server; establishing a communication channel between each first server and the corresponding second server; replicating, in an asynchronous mode, information from each first server to the corresponding second server through the communication channel; in response to receiving a second request for stopping replication of the first tenant database to the second tenant database, entering a synchronous mode of processing statements from client applications of the first tenant database; wherein: the source system includes a first system database and the target system includes a second system database; the first request is received by the first system database from the second system database; the source system includes a first name server that hosts the first system database and stores information associated with the first tenant database; and the stored information associated with the first tenant database includes landscape information associated with the source system. 2. The method of claim 1 , and further comprising: receiving a statement from a client application of the first tenant database; generating a transaction log based on the statement; and sending the transaction log to the target system to replay the transaction log at the second tenant database of the target system, and in response to processing the statement by first tenant database, sending information to the client application that indicates completion of processing the statement. 3. The method of claim 2 , wherein the entering a synchronous mode of processing statements from client applications of the first tenant database includes: in response to receiving a first notification indicating successful replication of the transaction log at the target system, processing the statement by the first tenant database. 4. The method of claim 2 , and further comprising: prior to entering a synchronous mode of processing statements from client applications of the first tenant database, processing the statement by first tenant database in the asynchronous mode. 5. The method of claim 4 , wherein in the asynchronous mode the statement is processed by the first tenant database without waiting for the first notification indicating successful replication of the transaction log at the second tenant database of the target system. 6. The method of claim 1 , and further comprising prior to entering a synchronous mode of processing statements from client applications of the first tenant database, receiving a second notification indicating successful replication of the information of the one or more first servers to the corresponding one or more second servers. 7. The method of claim 6 , wherein the second notification further indicates that the persistence of the replicated information from each first server to the corresponding second server has been initialized on the corresponding second servers. 8. The method of claim 7 , wherein a persistence flag is included in the second notification to indicate whether the persistence of the replicated information from each first server to the corresponding second server has been initialized on the corresponding second servers. 9. The method of claim 1 , and further comprising: in response to receiving a second request for stopping replication of the first tenant database to the second tenant database, initiating the shutdown of the first tenant database upon completion of the synchronous mode of processing statements from client applications of the first tenant database. 10. The method of claim 1 , and further comprising in response to receiving a second request for stopping replication of the first tenant database to the second tenant database: sending a third request to the target system to restart the second tenant database; and in response to receiving a third notification from the target system indicating a successful restart of the second tenant database, informing client applications of the first tenant database to redirect requests to the second tenant database of the target system. 11. The method of claim 1 , wherein the target system includes a second name server that hosts the second system database and stores information associated with the second tenant database, and wherein the stored information associated with the second tenant database includes landscape information associated with the target system. 12. The method of claim 1 , wherein the first tenant database includes a first index server that stores topology information associated with the first tenant database, and the second tenant database includes a second index server that stores topology information associated with the second tenant database. 13. The method of claim 12 , wherein topology information associated with a tenant databases includes information corresponding to tables associated with the tenant database, and information corresponding to table partitions associated with the tenant database. 14. The method of claim 12 , wherein the second notification indicating successful replication of the information of the one or more first servers to the corresponding one or more second server is received by the first index server of the first tenant databases from the second index server of the second tenant database. 15. The method of claim 1 , wherein the establishing a communication channel between each first server and the corresponding second server includes sending to the first server and the corresponding second server information that indicates a port of the communication channel. 16. The method of claim 1 , wherein the source system and target system communicate via a secure mutual authentication, the secure mutual authentication including: sending a temporary certificate and a key from the source system to the target system via a secure communication channel; installing the temporary certificate on the target system; and authenticating communications between the source system and the target system through the temporary certificate; wherein the temporary certificate is generated on the source system based on user credentials that are associated with a user who is authorized to access the source system and the target system. 17. A computer-implemented system for replicating a tenant database from a source system to a target system, the system comprising: one or more data processors; and a computer-readable storage medium encoded with instructions for commanding the one or more data processors to perform operations comprising: receiving, at a source system, a first request from a target system for replicating a first tenant database of the source system, the first tenant database including one or more first servers; sending to the target system characteristics of the one or more first servers included in the first tenant database to generate at the target system a second tenant database including one or more second servers
Change logging, detection, and notification (replication G06F16/27) · CPC title
Database-specific techniques · CPC title
Asynchronous replication or reconciliation · CPC title
Synchronous replication · CPC title
in transactions (updating of structured data in databases G06F16/23) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.