User interface for database management services

Abstract

A database system associated with a plurality of source databases in a virtual computing system includes a dashboard having a main menu for providing a plurality of control functions and a body that dynamically changes based upon the plurality of control functions that are selected. The dashboard includes a homepage for displaying a plurality of cells in the body, including a first cell for displaying a list of the plurality of source databases. The main menu includes a first control function, the selection of which triggers a database provisioning service by presenting options to either create a new source database or register an existing database within the body and a second control function, the selection of which triggers a copy data management service by presenting an option to create a new cloned database.

What is claimed is: 
     
         1 . A non-transitory computer-readable media comprising computer-readable instructions stored thereon that when executed by a processor cause the processor to:
 present a dashboard to receive a user request to provision a database:   in response to receiving the user request, present one or more user interfaces to: 
 receive a first input of a database name for the database; 
 receive a second input comprising a selection of a level of a Service Level Agreement (SLA) from a plurality of levels of the SLA to protect the database; and 
 receive a third input of a protection schedule comprising a first frequency of capturing a snapshot and at least one time period for capturing the snapshot; and 
   in response to receiving the first input, the second input, and the third input, display a status of provisioning the database on the dashboard, the status of provisioning the database indicating a progress of creation of the database.   
     
     
         2 . The non-transitory computer-readable media of  claim 1 , wherein the processor further executes computer-readable instructions to receive a fourth input for a database engine via the one or more user interfaces. 
     
     
         3 . The non-transitory computer-readable media of  claim 2 , wherein the one or more user interfaces to receive the first input, the second input, and the third input are presented after the one or more user interfaces to receive the fourth input is received. 
     
     
         4 . The non-transitory computer-readable media of  claim 1 , wherein the third input further comprises a second frequency of capturing a transactional log. 
     
     
         5 . The non-transitory computer-readable media of  claim 1 , wherein the at least one time period comprises one or more of a time of day for capturing a daily snapshot, a dav of a week for capturing a weekly snapshot, a day of a month for capturing a monthly snapshot, or a group of months for capturing a quarterly snapshot. 
     
     
         6 . The non-transitory computer-readable media of  claim 1 , wherein each of the plurality of levels of the SLA defines a first duration for a continuous protection of the database, a second duration for protecting the database using a daily snapshot, a third duration for protecting the database using a weekly snapshot, a fourth duration for protecting the database using a monthly snapshot, and a fifth duration for protecting the database using a quarterly snapshot. 
     
     
         7 . The non-transitory computer-readable media of  claim 1 , wherein in addition to provisioning the database, the dashboard provides an option to create a cloned database. 
     
     
         8 . The non-transitory computer-readable media of  claim 1 , wherein the processor further executes computer-readable instructions to:
 receive another user request via the dashboard to create a cloned database of the database upon provisioning;   present one or more additional user interfaces to: 
 receive a fourth input of a date from a series of dates; and 
 receive a fifth input indicative of creating the cloned database either at a point in time or using an available snapshot; and 
   in response to receiving the fourth input and the fifth input, display a status of cloning the database on the dashboard, the status of cloning the database indicating a progress of creation of the cloned database.   
     
     
         9 . The non-transitory computer-readable media of  claim 8 , wherein the series of dates provide a visual representation indicative of a level of protection available for a particular date of the series of dates. 
     
     
         10 . A system comprising:
 a memory having computer-readable instructions stored thereon; and   a processor that executes the computer-readable instructions to: 
 present a dashboard to receive a user request to provision a database; 
 in response to receiving the user request, present one or more user interfaces to: 
 receive a first input of a database name for the database; 
 receive a second input comprising a selection of a level of a Service Level Agreement (SLA) from a plurality of levels of the SLA to protect the database; and 
 receive a third input of a protection schedule comprising a first frequency of capturing a snapshot and at least one time period for capturing the snapshot; and 
 
 in response to receiving the first input, the second input, and the third input, display a status of provisioning the database on the dashboard, the status of provisioning the database indicating a progress of creation of the database. 
   
     
     
         11 . The system of  claim 10 , wherein the processor further executes computer-readable instructions to receive a fourth input for a database engine via the one or more user interfaces. 
     
     
         12 . The system of  claim 11 , wherein the one or more user interfaces to receive the first input, the second input, and the third input are presented after the one or more user interfaces to receive the fourth input is received. 
     
     
         13 . The system of  claim 10 , wherein the third input further comprises a second frequency of capturing a transactional log. 
     
     
         14 . The system of  claim 10 , wherein the at least one time period comprises one or more of a time of day for capturing a daily snapshot, a day of a week for capturing a weekly snapshot, a day of a month for capturing a monthly snapshot, or a group of months for capturing a quarterly snapshot. 
     
     
         15 . The system of  claim 10 , wherein each of the plurality of levels of the SLA defines a first duration for a continuous protection of the database, a second duration for protecting the database using a daily snapshot, a third duration for protecting the database using a weekly snapshot, a fourth duration for protecting the database using a monthly snapshot, and a fifth duration for protecting the database using a quarterly snapshot. 
     
     
         16 . The system of  claim 10 , wherein in addition to provisioning the database, the dashboard provides an option to create a cloned database. 
     
     
         17 . The system of  claim 10 , wherein the processor further executes computer-readable instructions to:
 receive another user request via the dashboard to create a cloned database of the database upon provisioning;   present one or more additional user interfaces to: 
 receive a fourth input of a date from a series of dates; and 
 
 receive a fifth input indicative of creating the cloned database either at a point in time or using an available snapshot; and 
   in response to receiving the fourth input and the fifth input, display a status of cloning the database on the dashboard, the status of cloning the database indicating a progress of creation of the cloned database.   
     
     
         18 . The system of  claim 17 , wherein the series of dates provide a visual representation indicative of a level of protection available for a particular date of the series of dates. 
     
     
         19 . A method comprising:
 presenting, by a processor executing computer-readable instructions stored on a memory, a dashboard to receive a user request for provisioning a database;   in response to receiving the user request, presenting one or more user interfaces for: 
 receiving a first input of a database name for the database; 
 receiving a fourth second input comprising a selection of a level of a Service Level Agreement (SLA) from a plurality of levels of the SLA to protect the database; and 
 receiving a third input of a protection schedule comprising a first frequency of capturing a snapshot and at least one time period for capturing the snapshot, and 
 in response to receiving the first input, the second input, and the third input displaying, by the processor, a status of provisioning the database on the dashboard, the status of provisioning the database indicating a progress of creation of the database. 
   
     
     
         20 . The method of  claim 19 , further comprising receiving, by the processor, a fourth input for a database engine via the one or more user interfaces. 
     
     
         21 . The method of  claim 20 , wherein the one or more user interfaces to receive the first input, the second input, and the third input are presented after the one or more user interfaces to receive the fourth input is received. 
     
     
         22 . The method of  claim 19 , wherein the third user input further comprises a second frequency of capturing a transactional log. 
     
     
         23 . The method of  claim 19 , wherein the at least one time period comprises one or more of a time of day for capturing a daily snapshot, a day of a week for capturing a weekly snapshot, a day of a month for capturing a monthly snapshot, or a group of months for capturing a quarterly snapshot. 
     
     
         24 . The method of  claim 19 , wherein 
 each of the plurality of levels of the SLA defines a first duration for a continuous protection of the database, a second duration for protecting the database using a daily snapshot, a third duration for protecting the database using a weekly snapshot, a fourth duration for protecting the database using a monthly snapshot, and a fifth duration for protecting the database using a quarterly snapshot.   
     
     
         25 . The method of  claim 19 , wherein in addition to provisioning the database, the dashboard provides an option to create a cloned database. 
     
     
         26 . The method of  claim 19 , further comprising:
 receiving, by the processor, another user request via the dashboard for creating a cloned database of the database upon provisioning;   presenting, by the processor, one or more additional user interfaces for: 
 receiving a fourth input of a date from a series of dates; and 
 
 receiving a fifth input indicative of creating the cloned database either at a point in time or using an available snapshot; and 
   in response to receiving thefourth input and the fifth input, displaying, by the processor, a status of cloning the database on the dashboard, the status of cloning the database indicating a progress of creation of the cloned database.   
     
     
         27 . The method of  claim 26 , wherein the series of dates provide a visual representation indicative of a level of protection available for a particular date of the series of dates.