US2022215110A1PendingUtilityA1

Systems and methods for multi-tenant data protection application

Assignee: NAKIVO INCPriority: Nov 27, 2013Filed: Oct 18, 2021Published: Jul 7, 2022
Est. expiryNov 27, 2033(~7.3 yrs left)· nominal 20-yr term from priority
G06F 11/2094G06F 11/3055G06F 11/2071G06F 11/3006G06F 16/256G06F 11/1448G06F 21/6218
59
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A system for providing a multi-tenant data protection application includes a server shared by all tenants for access to the provided multi-tenant data protection application. The system further includes business logic for managing tenants of the multi-tenant data protection application, tenant resource allocation and isolation of tenant operating environments. The system additionally includes a database server for creating, managing and maintaining databases, including a master database used to store configuration and monitoring data which is used for tenant management and monitoring, and a plurality of private tenant databases, each used to store tenant-specific configuration, tenant-specific data and associated tenant resources. The system includes one or more data protection engines configured to store a copy of protected data at tenant redundant data stores.

Claims

exact text as granted — not AI-modified
1 - 118 . (canceled) 
     
     
         119 . A method for adding a new tenant to a multi-tenant data protection application, the method comprising:
 (a) maintaining, at a database server,
 (i) a master database containing configuration data for the plurality of tenants, and 
 (ii) a plurality of tenant databases, each tenant database being associated with one of the plurality of tenants and containing tenant-specific information related to data to be protected for that tenant; 
   (b) maintaining, by one or more data protection engines, a plurality of redundant tenant data stores, each redundant tenant data store containing a copy of data to be protected for that tenant, whereby the plurality of redundant tenant data stores provide tenant-specific data redundancy;   (c) allocating a portion of shared resources to a new tenant;   (d) storing user data for the new tenant in the master database; and   (e) creating a new tenant database for the new tenant.   
     
     
         120 . The method of  claim 119 , wherein the one or more data protection engines include a respective data protection engine for each one of the tenant data protection stores. 
     
     
         121 . The method of  claim 120 , wherein each of the data protection engines is loaded on a separate data protection computer. 
     
     
         122 . The method of  claim 119 , wherein the database server comprises a plurality of physical machines. 
     
     
         123 . The method of  claim 119 , wherein the database server is a virtual machine. 
     
     
         124 . The method of  claim 119 , wherein the one or more data protection engines are running on a data protection computer. 
     
     
         125 . The method of  claim 119 , wherein each of the data protection engines is running on a respective data protection computer. 
     
     
         126 . The method of  claim 119 , wherein one or more of the data protection engines is running on a virtual machine. 
     
     
         127 . A method for changing the operational state of a tenant in a multi-tenant data protection application, the method comprising:
 (a) maintaining, at a database server,
 (i) a master database containing configuration data for the plurality of tenants, and 
 (ii) a plurality of tenant databases, each tenant database being associated with one of the plurality of tenants and containing tenant-specific information related to data to be protected for that tenant; 
   (b) maintaining, by one or more data protection engines, a plurality of redundant tenant data stores, each redundant tenant data store containing a copy of data to be protected for that tenant, whereby the plurality of redundant tenant data stores provide tenant-specific data redundancy;   (c) determining that a first tenant is currently in a running operational state;   (d) closing the tenant database for the first tenant; and   (e) storing information associated with a new operational state for the first tenant.   
     
     
         128 . The method of  claim 127 , wherein the one or more data protection engines include a respective data protection engine for each one of the tenant data protection stores. 
     
     
         129 . The method of  claim 128 , wherein each of the data protection engines is loaded on a separate data protection computer. 
     
     
         130 . The method of  claim 127 , wherein the database server comprises a plurality of physical machines. 
     
     
         131 . The method of  claim 127 , wherein the database server is a virtual machine. 
     
     
         132 . The method of  claim 127 , wherein the one or more data protection engines are running on a data protection computer. 
     
     
         133 . The method of  claim 127 , wherein each of the data protection engines is running on a respective data protection computer. 
     
     
         134 . The method of  claim 127 , wherein one or more of the data protection engines is running on a virtual machine. 
     
     
         135 - 149 . (canceled)

Join the waitlist — get patent alerts

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

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