US 12,216,550 B2
Automatic backup distribution for clustered databases
Udbhav Prasad, Mountain View, CA (US)
Assigned to Rubrik, Inc., Palo Alto, CA (US)
Filed by Rubrik, Inc., Palo Alto, CA (US)
Filed on Jan. 27, 2022, as Appl. No. 17/586,586.
Prior Publication US 2023/0236936 A1, Jul. 27, 2023
Int. Cl. G06F 11/00 (2006.01); G06F 9/50 (2006.01); G06F 11/14 (2006.01)
CPC G06F 11/1464 (2013.01) [G06F 9/5038 (2013.01); G06F 9/5083 (2013.01); G06F 11/1435 (2013.01); G06F 11/1469 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method, comprising:
receiving, from a user of a data management platform, a first job request to perform a backup of data from a data source to a database managed by the user of the data management platform, wherein the database is configured as a plurality of database instances running on a plurality of computing nodes of a computing cluster;
storing, in a metadata file, a backup load indication that indicates which computing node of the plurality of computing nodes is assigned to perform the backup of the data based at least in part on receiving the first job request, wherein the metadata file is configured to store a plurality of backup load indications for the database and a set of load balancing metrics for the plurality of backup load indications, wherein the set of load balancing metrics indicate a quantity of current backup jobs running on a first computing node of one or more computing nodes, the current backup jobs being associated with a backup job type comprising a transaction log backup job type or a database backup job type;
receiving, from the user of the data management platform, one or more second job requests of the database backup job type;
determining a time taken to run a previous backup job at the first computing node, the previous backup job having the database backup job type;
determining a backup load for the first computing node based at least in part on a subset of the quantity of current backup jobs running on the first computing node indicated in the metadata file and the time taken to run the previous backup job, wherein the subset of the quantity of current backup jobs has a same backup job type as the one or more second job requests, and wherein a remaining subset of the current backup jobs has a different backup job type from the one or more second job requests; and
assigning the one or more second job requests of the database backup job type to the first computing node based at least in part on the backup load for the first computing node determined based at least in part on the time taken to run the previous backup job at the first computing node.