US2022300383A1PendingUtilityA1

Mount and migrate

Assignee: GOOGLE LLCPriority: Mar 6, 2020Filed: Jun 7, 2022Published: Sep 22, 2022
Est. expiryMar 6, 2040(~13.6 yrs left)· nominal 20-yr term from priority
G06F 16/119G06F 11/1469G06F 11/1461G06F 11/1464G06F 2201/80G06F 16/214G06F 11/2094
54
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Systems and methods are disclosed for migrating or restoring a server database such that the migrated server database can be used before data has copied to storage for the migrated server database. Data used by a server database is copied to a copy storage, which is mounted to a second server database. The second server database is brought online using the copy of data. The copy of data is copied to a second storage. The second server database is brought offline and switched to run from the second storage. The second server database is brought back online, thereby permitting use of the second server database before copying data to the second storage.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A computer-implemented method that when executed by data processing hardware causes the data processing hardware to perform operations comprising:
 receiving a migration request from a user requesting to migrate data from source storage of a source server database to target storage of a target server database;   in response to receiving the migration request, copying initial data from the source storage to a copy storage, the copy storage different than the source storage of the source server database and the target storage of the target server database;   migrating the copy of the initial data from the copy storage to the target storage of the target server database;   after migrating the copy of the initial data from the copy storage to the target storage of the target server database, determining that an update occurred in the copy of the initial data at the copy storage; and   synchronizing the target storage of the target server database with the copy storage using the updated copy of the initial data.   
     
     
         2 . The computer-implemented method of  claim 1 , wherein the target server database is the same as the source server database. 
     
     
         3 . The computer-implemented method of  claim 1 , wherein the target storage of the target server database is the same as the source storage of the source server database. 
     
     
         4 . The computer-implemented method of  claim 1 , wherein the target server database is different than the source server database. 
     
     
         5 . The computer-implemented method of  claim 1 , wherein the target storage of the target server database is different than the source storage of the source server database. 
     
     
         6 . The computer-implemented method of  claim 1 , wherein the source server database comprises an SQL server database. 
     
     
         7 . The computer-implemented method of  claim 1 , wherein copying the initial data from the source server database to the copy storage comprises capturing the initial data periodically based on a scheduled data capture. 
     
     
         8 . The computer-implemented method of  claim 1 , wherein determining that the update occurred in the copy of the initial data at the copy storage comprises maintaining a transaction log comprising information representative of transactions at the source server database. 
     
     
         9 . The computer-implemented method of  claim 1 , wherein the target server database is a distributed database. 
     
     
         10 . The computer-implemented method of  claim 1 , wherein the source server database is a distributed database. 
     
     
         11 . A system comprising:
 data processing hardware; and   memory hardware in communication with the data processing hardware, the memory hardware storing instructions that when executed on the data processing hardware cause the data processing hardware to perform operations comprising:
 receiving a migration request from a user requesting to migrate data from source storage of a source server database to target storage of a target server database; 
 in response to receiving the migration request, copying initial data from the source storage to a copy storage, the copy storage different than the source storage of the source server database and the target storage of the target server database; 
 migrating the copy of the initial data from the copy storage to the target storage of the target server database; 
 after migrating the copy of the initial data from the copy storage to the target storage of the target server database, determining that an update occurred in the copy of the initial data at the copy storage; and 
 synchronizing the target storage of the target server database with the copy storage using the updated copy of the initial data. 
   
     
     
         12 . The system of  claim 11 , wherein the target server database is the same as the source server database. 
     
     
         13 . The system of  claim 11 , wherein the target storage of the target server database is the same as the source storage of the source server database. 
     
     
         14 . The system of  claim 11 , wherein the target server database is different than the source server database. 
     
     
         15 . The system of  claim 11 , wherein the target storage of the target server database is different than the source storage of the source server database. 
     
     
         16 . The system of  claim 11 , wherein the source server database comprises an SQL server database. 
     
     
         17 . The system of  claim 11 , wherein copying the initial data from the source server database to the copy storage comprises capturing the initial data periodically based on a scheduled data capture. 
     
     
         18 . The system of  claim 11 , wherein determining that the update occurred in the copy of the initial data at the copy storage comprises maintaining a transaction log comprising information representative of transactions at the source server database. 
     
     
         19 . The system of  claim 11 , wherein the target server database is a distributed database. 
     
     
         20 . The system of  claim 11 , wherein the source server database is a distributed database.

Join the waitlist — get patent alerts

Track US2022300383A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.