Abstract: In one or more embodiments, a cloud operation reservation system is provided through which cloud operations may be scheduled and managed. The cloud operation reservation system includes logic for defining a set of time windows that are available to perform one or more cloud operations on cloud targets and presenting the set of time windows to one or more tenants of a cloud service. Tenants may browse the presented set of time windows and submit reservation requests to update and/or perform other operations on cloud targets. In response to receiving, a request to reserve one or more slots in a particular time window, the cloud operation reservation system schedules one or more cloud operations to be performed on a cloud target that is available to at least one tenant.

Abstract: In one or more embodiments, a cloud operation reservation system is provided through which cloud operations may be scheduled and managed. The cloud operation reservation system includes logic for defining a set of time windows that are available to perform one or more cloud operations on cloud targets and presenting the set of time windows to one or more tenants of a cloud service. Tenants may browse the presented set of time windows and submit reservation requests to update and/or perform other operations on cloud targets. In response to receiving, a request to reserve one or more slots in a particular time window, the cloud operation reservation system schedules one or more cloud operations to be performed on a cloud target that is available to at least one tenant.

Abstract: A system and method include receiving, by a database engine of a database system associated with a virtual computing system, a user request via a dashboard for provisioning a source database with the database system, receiving, by the database engine via the dashboard, selection of a database engine type, and receiving, by the database engine via the dashboard, selection of a Service Level Agreement (“SLA”) and a protection schedule. The system and method also include provisioning, by the database engine, the source database based upon the database engine type, creating, by the database engine, an instance of a database protection system based upon the SLA and the protection schedule, including associating the instance of the database protection system with the source database, and displaying, by the database engine, the source database within the dashboard.

Abstract: A system and method include receiving, by a database engine of a database system associated with a virtual computing system, a user request via a dashboard for provisioning a source database with the database system, receiving, by the database engine via the dashboard, selection of a database engine type, and receiving, by the database engine via the dashboard, selection of a Service Level Agreement (“SLA”) and a protection schedule. The system and method also include provisioning, by the database engine, the source database based upon the database engine type, creating, by the database engine, an instance of a database protection system based upon the SLA and the protection schedule, including associating the instance of the database protection system with the source database, and displaying, by the database engine, the source database within the dashboard.

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.

Abstract: Techniques are described for standardizing configuration levels across a plurality of software deployments. In one embodiment, a standardization management system generates, based on a plurality of software deployments that have different source components, an end state definition that identifies a recommended standard set of source components for the plurality of software deployments. Based on the end state definition that identifies the recommended standard set of source components for the plurality of software deployments, the standardization management system generates an image that includes the standard set of source components for the plurality of software deployments. The image may be used to update software deployments that are part of the plurality of software deployments and do not include the standard set of source components.

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.

Abstract: A system and method include receiving, by a database engine of a database system associated with a virtual computing system, a user request via a dashboard for provisioning a source database with the database system, receiving, by the database engine via the dashboard, selection of a database engine type, and receiving, by the database engine via the dashboard, selection of a Service Level Agreement (“SLA”) and a protection schedule. The system and method also include provisioning, by the database engine, the source database based upon the database engine type, creating, by the database engine, an instance of a database protection system based upon the SLA and the protection schedule, including associating the instance of the database protection system with the source database, and displaying, by the database engine, the source database within the dashboard.

Abstract: A system and method include associating, by a database system of a virtual computing system, a protection schedule with each source database provisioned in the database system, the protection schedule defining a frequency of capturing snapshots and a frequency of capturing transactional logs, capturing, by the database system for each of the source databases, snapshots and transactional logs based upon the frequency of capturing snapshots and the frequency of capturing transactional logs, respectively, and receiving, by the database system, a request identifying a point in time for creating a cloned database from a first source database. The system and method also include retrieving, by the database system, the snapshots and the transactional logs corresponding to the point in time and creating, by the database system, the cloned database by combining data in storage locations identified in the transactional logs and the data in remaining storage locations identified in the snapshots.

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.

Abstract: In one or more embodiments, a cloud operation reservation system is provided through which cloud operations may be scheduled and managed. The cloud operation reservation system includes logic for defining a set of time windows that are available to perform one or more cloud operations on cloud targets and presenting the set of time windows to one or more tenants of a cloud service. Tenants may browse the presented set of time windows and submit reservation requests to update and/or perform other operations on cloud targets. In response to receiving, a request to reserve one or more slots in a particular time window, the cloud operation reservation system schedules one or more cloud operations to be performed on a cloud target that is available to at least one tenant.

Abstract: In one or more embodiments, a cloud operation reservation system is provided through which cloud operations may be scheduled and managed. The cloud operation reservation system includes logic for defining a set of time windows that are available to perform one or more cloud operations on cloud targets and presenting the set of time windows to one or more tenants of a cloud service. Tenants may browse the presented set of time windows and submit reservation requests to update and/or perform other operations on cloud targets. In response to receiving, a request to reserve one or more slots in a particular time window, the cloud operation reservation system schedules one or more cloud operations to be performed on a cloud target that is available to at least one tenant.

Abstract: In one or more embodiments, a system defines a plurality of waves for performing a set of scheduled operations on a set of cloud targets within a particular time window, where the plurality of waves includes a first wave for performing scheduled operations on a first subset of cloud target and a second wave for performing scheduled operations on a second subset of cloud targets. During the first wave, a first subset of scheduled operations within the particular time window are performed on two or more target resources from the first subset of target resources. The system determines a rate of success for performing the first subset of scheduled operations on the two or more target resources from the first subset of target resources. If the rate of success does not satisfy the threshold, then the system delays or cancels operations from subsequent waves including the second subset of operations.

Abstract: In one or more embodiments, a system comprises logic for aggregating and analyzing cloud targets based on a variety of attributes. Responsive at least to receiving a selection of one or more attributes, the system: (a) aggregates, from a plurality of cloud targets, a set of cloud targets that includes a first cloud target supporting at least a first cloud service for a first tenant and a second cloud target supporting at least a second cloud service for a second tenant; (b) presents, through a display interface, the set of cloud targets that includes the first cloud target and the second cloud target; and (c) receiving, through the display interface, a second selection of an action to perform on at least one cloud target in the set of cloud targets. Responsive at least to the second selection, the system performs the action on at least one cloud target.

Abstract: Techniques are described for standardizing configuration levels across a plurality of software deployments. In one embodiment, a standardization management system generates, based on a plurality of software deployments that have different source components, an end state definition that identifies a recommended standard set of source components for the plurality of software deployments. Based on the end state definition that identifies the recommended standard set of source components for the plurality of software deployments, the standardization management system generates an image that includes the standard set of source components for the plurality of software deployments. The image may be used to update software deployments that are part of the plurality of software deployments and do not include the standard set of source components.

Abstract: Techniques are described for managing updates across one or more targets using standard software images. In one embodiment, a first version of a software application is deployed on a set of one or more targets. A software binary is then generated for an updated version of the software application. The software binary for the updated version of the software application is deployed to the set of one or more targets. While the software binary for the updated version of the software application is deployed, the previous version of the software application remains active on a particular target. The updated version of the software application is activated, using the software binary, on the particular target.

Abstract: Techniques are described for standardizing configuration levels across a plurality of software deployments. In one embodiment, a standardization management system generates, based on a plurality of software deployments that have different source components, an end state definition that identifies a recommended standard set of source components for the plurality of software deployments. Based on the end state definition that identifies the recommended standard set of source components for the plurality of software deployments, the standardization management system generates an image that includes the standard set of source components for the plurality of software deployments. The image may be used to update software deployments that are part of the plurality of software deployments and do not include the standard set of source components.

Abstract: Techniques are described for standardizing configuration levels across a plurality of software deployments. In one embodiment, a standardization management system generates, based on a plurality of software deployments that have different source components, an end state definition that identifies a recommended standard set of source components for the plurality of software deployments. Based on the end state definition that identifies the recommended standard set of source components for the plurality of software deployments, the standardization management system generates an image that includes the standard set of source components for the plurality of software deployments. The image may be used to update software deployments that are part of the plurality of software deployments and do not include the standard set of source components.

Abstract: Disclosed are a system, method, and computer program product for a unified system for implementing clones. The unified system includes the appropriate infrastructure to create, maintain, and administer clones and supporting data sources in the computing environment. In addition, a user interface is provided that is capable of visually displaying relationships and lineages of sources and clones in the system. The user interface provides functionality to select any given object, and to trace its parent-child relationships to highlight its related parent and/or child source/clone.