Backup management for synchronized databases

A data backup server may obtain, for a set of databases that includes a primary database and a set of standby databases configured to be synchronized with the primary database. The data backup server may identify, based on the role information, a data backup group that includes a subset of the databases. In some examples, the first database may be included in the data backup group based on being a primary database, the one or more second databases may be included in the data backup group based at least in part on being standby databases of a first type, and the one or more third databases may be excluded from the data backup group based on being standby databases of a second type. The data backup server may then perform a backup procedure based on generating a snapshot of a database within the data backup group.

FIELD OF TECHNOLOGY

The present disclosure relates generally to database systems and data processing, and more specifically to backup management for synchronized databases.

BACKGROUND

A data management system (DMS) may be employed to manage data associated with one or more computing systems. The data may be generated, stored, or otherwise used by the one or more computing systems, examples of which may include servers, databases, virtual machines, cloud computing systems, file systems (e.g., network-attached storage (NAS) systems), or other data storage or processing systems. The DMS may provide data backup, data recovery, data classification, or other types of data management services for data of the one or more computing systems. Improved data management may offer improved performance with respect to reliability, speed, efficiency, scalability, security, or ease-of-use, among other possible aspects of performance.

DETAILED DESCRIPTION

A data synchronization group (e.g., a data guard group) may include a primary database and a set of standby databases, where the standby databases are configured to be synchronized with the primary database (e.g., based on receiving transaction log information associated with the primary database). The databases within the data synchronization group may be geographically distributed. A database assuming a role of a primary database may be based on role information assigned to that particular database. In some instances, a particular database that acts as the primary database may vary over time (e.g., due to failover or switchover events). That is, a database that is at one time a standby database may at some later time become the primary database, and vice versa. Multiple types of standby databases may exist (e.g., physical standby databases and logical standby databases) in a data synchronization group. In some examples, a server may back up one or more databases by generating snapshots. However, snapshots obtained from standby databases of a first type (e.g., physical standby databases) and the primary database may be interchangeable for recovery purposes (e.g., the primary database may be recoverable based on a snapshot of a physical standby database, or a physical standby database may be recoverable based on a snapshot of the primary database), while snapshots obtained from standby databases of another type (e.g., logical standby databases, standby databases of other types that are not physical standby databases) may not be interchangeable for recovery purposes with snapshots obtained from the primary database.

One or more aspects of the present disclosure provide for automatically identifying, for a data synchronization group, a data backup group that includes the primary database and the first type of standby databases of the data synchronization group and that excludes a second type of standby databases of the data synchronization group. Herein, a first type of standby database may refer to any standby database that is to be included in the data backup group—e.g., based on a snapshot for a standby database of the first type being interchangeable for recovery purposes with snapshots obtained from a primary database—and a second type of standby database may refer to any standby database that is to be excluded from the data backup group. For example, a physical standby database may be an example of a first type of database, while other types of standby databases (e.g., logical standby databases, snapshot standby databases, far sync standby databases) may be (e.g., collectively or individually) a second type of standby database.

In some examples, a server (e.g., backup management system) may query one or more database hosts for a set of databases of a data synchronization group. The backup management system may identify a set of databases that including a primary database and a plurality of standby databases configured to be synchronized with the primary database. The backup management system may obtain a role information for the set of databases. The role information may indicate a first database as the primary database, one or more second databases as standby databases of the first type, and one or more third databases as standby databases of the second type. The backup management system may monitor the roles of the databases within the data synchronization group (e.g., through periodic or other repeated querying) and update the membership of the data backup group accordingly. That is, the membership of the data backup group may be updated over time in accordance with updates to the roles of the databases within the data synchronization group.

The backup management system may generate a snapshot for the data synchronization group based on any database within the data backup group and may identify the database used for the snapshot based on a user-configurable policy. For example, a user may configure the backup management system to take snapshots of the primary database (i.e., whichever database is the primary database at the time of the snapshot), or of a physical standby database (e.g., to avoid burdening the host of the primary database), or of a particular database regardless of its current role (e.g., the database with the most powerful host). Such user-configurable policies may account for possible contingencies within the data synchronization group, such as failovers and switchovers. Additional aspects of the present disclosure provide for maintaining logs so that the backup management system may use incremental snapshots without sacrificing recoverability even when a contingency within the data synchronization group causes a change in which database is used for snapshots, to maintaining metadata indicating the particular database from which a given snapshot was taken, and improving the efficiency with which transaction logs may be archived for the data synchronization group (e.g., by deleting the logs from all members once a snapshot is taken for the group.

Aspects of the disclosure are initially described in the context of an environment supporting an on-demand database service. Aspects of the disclosure are further illustrated by and described with reference to a system diagram and a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to backup management for synchronized databases.

FIG.1illustrates an example of a computing environment100for cloud computing that supports backup management for synchronized databases in accordance with various aspects of the present disclosure. The computing environment100may include a computing system105, a data management system (DMS)110, and one or more computing devices115, which may be in communication with one another via a network120. The computing system105may generate, store, process, modify, or otherwise use associated data, and the DMS110may provide one or more data management services for the computing system105. For example, the DMS110may provide a data backup service, a data recovery service, a data classification service, a data transfer or replication service, one or more other data management services, or any combination thereof for data associated with the computing system105.

The network120may allow the one or more computing devices115, the computing system105, and the DMS110to communicate (e.g., exchange information) with one another. The network120may include aspects of one or more wired networks (e.g., the Internet), one or more wireless networks (e.g., cellular networks), or any combination thereof. The network120may include aspects of one or more public networks or private networks, as well as secured or unsecured networks, or any combination thereof. The network120also may include any quantity of communications links and any quantity of hubs, bridges, routers, switches, ports or other physical or logical network components.

A computing device115may be used to input information to or receive information from the computing system105, the DMS110, or both. For example, a user of the computing device115may provide user inputs via the computing device115, which may result in commands, data, or any combination thereof being communicated via the network120to the computing system105, the DMS110, or both. Additionally or alternatively, a computing device115may output (e.g., display) data or other information received from the computing system105, the DMS110, or both. A user of a computing device115may, for example, use the computing device115to interact with one or more user interfaces (e.g., graphical user interfaces (GUIs)) to operate or otherwise interact with the computing system105, the DMS110, or both. Though one computing device115is shown inFIG.1, it is to be understood that the computing environment100may include any quantity of computing devices115.

A computing device115may be a stationary device (e.g., a desktop computer or access point) or a mobile device (e.g., a laptop computer, tablet computer, or cellular phone). In some examples, a computing device115may be a commercial computing device, such as a server or collection of servers. And in some examples, a computing device115may be a virtual device (e.g., a virtual machine). Though shown as a separate device in the example computing environment ofFIG.1, it is to be understood that in some cases a computing device115may be included in (e.g., may be a component of) the computing system105or the DMS110.

The computing system105may include one or more servers125and may provide (e.g., to the one or more computing devices115) local or remote access to applications, databases, or files stored within the computing system105. The computing system105may further include one or more data storage devices130. Though one server125and one data storage device130are shown inFIG.1, it is to be understood that the computing system105may include any quantity of servers125and any quantity of data storage devices130, which may be in communication with one another and collectively perform one or more functions ascribed herein to the server125and data storage device130.

A data storage device130may include one or more hardware storage devices operable to store data, such as one or more hard disk drives (HDDs), magnetic tape drives, solid-state drives (SSDs), storage area network (SAN) storage devices, or network-attached storage (NAS) devices. In some cases, a data storage device130may comprise a tiered data storage infrastructure (or a portion of a tiered data storage infrastructure). A tiered data storage infrastructure may allow for the movement of data across different tiers of the data storage infrastructure between higher-cost, higher-performance storage devices (e.g., SSDs and HDDs) and relatively lower-cost, lower-performance storage devices (e.g., magnetic tape drives). In some examples, a data storage device130may be a database (e.g., a relational database), and a server125may host (e.g., provide a database management system for) the database.

A server125may allow a client (e.g., a computing device115) to download information or files (e.g., executable, text, application, audio, image, or video files) from the computing system105, to upload such information or files to the computing system105, or to perform a search query related to particular information stored by the computing system105. In some examples, a server125may act as an application server or a file server. In general, a server125may refer to one or more hardware devices that act as the host in a client-server relationship or a software process that shares a resource with or performs work for one or more clients.

A server125may include a network interface140, processor145, memory150, disk155, and computing system manager160. The network interface140may enable the server125to connect to and exchange information via the network120(e.g., using one or more network protocols). The network interface140may include one or more wireless network interfaces, one or more wired network interfaces, or any combination thereof. The processor145may execute computer-readable instructions stored in the memory150in order to cause the server125to perform functions ascribed herein to the server125. The processor145may include one or more processing units, such as one or more central processing units (CPUs), one or more graphics processing units (GPUs), or any combination thereof. The memory150may comprise one or more types of memory (e.g., random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), read-only memory ((ROM), electrically erasable programmable read-only memory (EEPROM), Flash, etc.). Disk155may include one or more HDDs, one or more SSDs, or any combination thereof. Memory150and disk155may comprise hardware storage devices. The computing system manager160may manage the computing system105or aspects thereof (e.g., based on instructions stored in the memory150and executed by the processor145) to perform functions ascribed herein to the computing system105. In some examples, the network interface140, processor145, memory150, and disk155may be included in a hardware layer of a server125, and the computing system manager160may be included in a software layer of the server125. In some cases, the computing system manager160may be distributed across (e.g., implemented by) multiple servers125within the computing system105.

In some examples, the computing system105or aspects thereof may be implemented within one or more cloud computing environments, which may alternatively be referred to as cloud environments. Cloud computing may refer to Internet-based computing, wherein shared resources, software, and/or information may be provided to one or more computing devices on-demand via the Internet. A cloud environment may be provided by a cloud platform, where the cloud platform may include physical hardware components (e.g., servers) and software components (e.g., operating system) that implement the cloud environment. A cloud environment may implement the computing system105or aspects thereof through Software-as-a-Service (SaaS) or Infrastructure-as-a-Service (IaaS) services provided by the cloud environment. SaaS may refer to a software distribution model in which applications are hosted by a service provider and made available to one or more client devices over a network (e.g., to one or more computing devices115over the network120). IaaS may refer to a service in which physical computing resources are used to instantiate one or more virtual machines, the resources of which are made available to one or more client devices over a network (e.g., to one or more computing devices115over the network120).

In some examples, the computing system105or aspects thereof may implement or be implemented by one or more virtual machines. The one or more virtual machines may run various applications, such as a database server, an application server, or a web server. For example, a server125may be used to host (e.g., create, manage) one or more virtual machines, and the computing system manager160may manage a virtualized infrastructure within the computing system105and perform management operations associated with the virtualized infrastructure. The computing system manager160may manage the provisioning of virtual machines running within the virtualized infrastructure and provide an interface to a computing device115interacting with the virtualized infrastructure. For example, the computing system manager160may be or include a hypervisor and may perform various virtual machine-related tasks, such as cloning virtual machines, creating new virtual machines, monitoring the state of virtual machines, moving virtual machines between physical hosts for load balancing purposes, and facilitating backups of virtual machines. In some examples, the virtual machines, the hypervisor, or both, may virtualize and make available resources of the disk155, the memory, the processor145, the network interface140, the data storage device130, or any combination thereof in support of running the various applications. Storage resources (e.g., the disk155, the memory150, or the data storage device130) that are virtualized may be accessed by applications as a virtual disk.

The DMS110may provide one or more data management services for data associated with the computing system105and may include DMS manager190and any quantity of storage nodes185. The DMS manager190may manage operation of the DMS110, including the storage nodes185. Though illustrated as a separate entity within the DMS110, the DMS manager190may in some cases be implemented (e.g., as a software application) by one or more of the storage nodes185. In some examples, the storage nodes185may be included in a hardware layer of the DMS110, and the DMS manager190may be included in a software layer of the DMS110. In the example illustrated inFIG.1, the DMS110is separate from the computing system105but in communication with the computing system105via the network120. It is to be understood, however, that in some examples at least some aspects of the DMS110may be located within computing system105. For example, one or more servers125, one or more data storage devices130, and at least some aspects of the DMS110may be implemented within the same cloud environment or within the same data center.

Storage nodes185of the DMS110may include respective network interfaces165, processors170, memories175, and disks180. The network interfaces165may enable the storage nodes185to connect to one another, to the network120, or both. A network interface165may include one or more wireless network interfaces, one or more wired network interfaces, or any combination thereof. The processor170of a storage node185may execute computer-readable instructions stored in the memory175of the storage node185in order to cause the storage node185to perform processes described herein as performed by the storage node185. A processor170may include one or more processing units, such as one or more CPUs, one or more GPUs, or any combination thereof. The memory150may comprise one or more types of memory (e.g., RAM, SRAM, DRAM, ROM, EEPROM, Flash, etc.). A disk180may include one or more HDDs, one or more SDDs, or any combination thereof. Memories175and disks180may comprise hardware storage devices. Collectively, the storage nodes185may in some cases be referred to as a storage cluster or as a cluster of storage nodes185.

The DMS110may provide a backup and recovery service for the computing system105. For example, the DMS110may manage the extraction and storage of snapshots135associated with different point-in-time versions of one or more target computing objects within the computing system105. A snapshot135of a computing object (e.g., a virtual machine, a database, a filesystem, a virtual disk, a virtual desktop, or other type of computing system or storage system) may be a file (or set of files) that represents a state of the computing object (e.g., the data thereof) as of a particular point in time. A snapshot135may also be used to restore (e.g., recover) the corresponding computing object as of the particular point in time corresponding to the snapshot135. A computing object of which a snapshot135may be generated may be referred to as snappable. Snapshots135may be generated at different times (e.g., periodically or on some other scheduled or configured basis) in order to represent the state of the computing system105or aspects thereof as of those different times. In some examples, a snapshot135may include metadata that defines a state of the computing object as of a particular point in time. For example, a snapshot135may include metadata associated with (e.g., that defines a state of) some or all data blocks included in (e.g., stored by or otherwise included in) the computing object. Snapshots135(e.g., collectively) may capture changes in the data blocks over time. Snapshots135generated for the target computing objects within the computing system105may be stored in one or more storage locations (e.g., the disk155, memory150, the data storage device130) of the computing system105, in the alternative or in addition to being stored within the DMS110, as described herein.

To obtain a snapshot135of a target computing object associated with the computing system105(e.g., of the entirety of the computing system105or some portion thereof, such as one or more databases, virtual machines, or filesystems within the computing system105), the DMS manager190may transmit a snapshot request to the computing system manager160. In response to the snapshot request, the computing system manager160may set the target computing object into a frozen state (e.g., a read-only state). Setting the target computing object into a frozen state may allow a point-in-time snapshot135of the target computing object to be stored or transferred.

In some examples, the computing system105may generate the snapshot135based on the frozen state of the computing object. For example, the computing system105may execute an agent of the DMS110(e.g., the agent may be software installed at and executed by one or more servers125), and the agent may cause the computing system105to generate the snapshot135and transfer the snapshot to the DMS110in response to the request from the DMS110. In some examples, the computing system manager160may cause the computing system105to transfer, to the DMS110, data that represents the frozen state of the target computing object, and the DMS110may generate a snapshot135of the target computing object based on the corresponding data received from the computing system105.

Once the DMS110receives, generates, or otherwise obtains a snapshot135, the DMS110may store the snapshot135at one or more of the storage nodes185. The DMS110may store a snapshot135at multiple storage nodes185, for example, for improved reliability. Additionally or alternatively, snapshots135may be stored in some other location connected with the network120. For example, the DMS110may store more recent snapshots135at the storage nodes185, and the DMS110may transfer less recent snapshots135via the network120to a cloud environment (which may include or be separate from the computing system105) for storage at the cloud environment, a magnetic tape storage device, or another storage system separate from the DMS110.

Updates made to a target computing object that has been set into a frozen state may be written by the computing system105to a separate file (e.g., an update file) or other entity within the computing system105while the target computing object is in the frozen state. After the snapshot135(or associated data) of the target computing object has been transferred to the DMS110, the computing system manager160may release the target computing object from the frozen state, and any corresponding updates written to the separate file or other entity may be merged into the target computing object.

In response to a restore command (e.g., from a computing device115or the computing system105), the DMS110may restore a target version (e.g., corresponding to a particular point in time) of a computing object based on a corresponding snapshot135of the computing object. In some examples, the corresponding snapshot135may be used to restore the target version based on data of the computing object as stored at the computing system105(e.g., based on information included in the corresponding snapshot135and other information stored at the computing system105, the computing object may be restored to its state as of the particular point in time). Additionally or alternatively, the corresponding snapshot135may be used to restore the data of the target version based on data of the computing object as included in one or more backup copies of the computing object (e.g., file-level backup copies or image-level backup copies). Such backup copies of the computing object may be generated in conjunction with or according to a separate schedule than the snapshots135. For example, the target version of the computing object may be restored based on the information in a snapshot135and based on information included in a backup copy of the target object generated prior to the time corresponding to the target version. Backup copies of the computing object may be stored at the DMS110(e.g., in the storage nodes185) or in some other location connected with the network120(e.g., in a cloud environment, which in some cases may be separate from the computing system105).

In some examples, the DMS110may restore the target version of the computing object and transfer the data of the restored computing object to the computing system105. And in some examples, the DMS110may transfer one or more snapshots135to the computing system105, and restoration of the target version of the computing object may occur at the computing system105(e.g., as managed by an agent of the DMS110, where the agent may be installed and operate at the computing system105).

In response to a mount command (e.g., from a computing device115or the computing system105), the DMS110may instantiate data associated with a point-in-time version of a computing object based on a snapshot135corresponding to the computing object (e.g., along with data included in a backup copy of the computing object) and the point-in-time. The DMS110may then allow the computing system105to read or modify the instantiated data (e.g., without transferring the instantiated data to the computing system). In some examples, the DMS110may instantiate (e.g., virtually mount) some or all of the data associated with the point-in-time version of the computing object for access by the computing system105, the DMS110, or the computing device115.

In some examples, the DMS110may store different types of snapshots, including for the same computing object. For example, the DMS110may store both base snapshots135and incremental snapshots135. A base snapshot135may represent the entirety of the state of the corresponding computing object as of a point in time corresponding to the base snapshot135. An incremental snapshot135may represent the changes to the state—which may be referred to as the delta—of the corresponding computing object that have occurred between an earlier or later point in time corresponding to another snapshot135(e.g., another base snapshot135or incremental snapshot135) of the computing object and the incremental snapshot135. In some cases, some incremental snapshots135may be forward-incremental snapshots135and other incremental snapshots135may be reverse-incremental snapshots135. To generate a full snapshot135of a computing object using a forward-incremental snapshot135, the information of the forward-incremental snapshot135may be combined with (e.g., applied to) the information of an earlier base snapshot135of the computing object along with the information of any intervening forward-incremental snapshots135, where the earlier base snapshot135may include a base snapshot135and one or more reverse-incremental or forward-incremental snapshots135. To generate a full snapshot135of a computing object using a reverse-incremental snapshot135, the information of the reverse-incremental snapshot135may be combined with (e.g., applied to) the information of a later base snapshot135of the computing object along with the information of any intervening reverse-incremental snapshots135.

In some examples, the DMS110may provide a data classification service, a malware detection service, a data transfer or replication service, backup verification service, or any combination thereof, among other possible data management services for data associated with the computing system105. For example, the DMS110may analyze data included in one or more computing objects of the computing system105, metadata for one or more computing objects of the computing system105, or any combination thereof, and based on such analysis, the DMS110may identify locations within the computing system105that include data of one or more target data types (e.g., sensitive data, such as data subject to privacy regulations or otherwise of particular interest) and output related information (e.g., for display to a user via a computing device115). Additionally or alternatively, the DMS110may detect whether aspects of the computing system105have been impacted by malware (e.g., ransomware). Additionally or alternatively, the DMS110may relocate data or create copies of data based on using one or more snapshots135to restore the associated computing object within its original location or at a new location (e.g., a new location within a different computing system105). Additionally or alternatively, the DMS110may analyze backup data to ensure that the underlying data (e.g., user data or metadata) has not been corrupted. The DMS110may perform such data classification, malware detection, data transfer or replication, or backup verification, for example, based on data included in snapshots135or backup copies of the computing system105, rather than live contents of the computing system105, which may beneficially avoid adversely.

According to one or more aspects, the computing system105may support a single primary database and multiple standby databases. The standby databases may include two or more types of standby databases, such as, for example, physical standby databases, logical standby databases, snapshot standby databases, far sync standby databases, or any combination thereof. The databases supported by the computing system105may be geographically distributed. The members of the set of databases maintained by the computing system105may remain in sync using log information. In some examples, the DMS110may provide for a backup service for the databases maintained or otherwise supported by the computing system105. However, the backup architecture of such databases may be predefined by the computing system105and a customers may not be able to synchronize backup from any of the member databases based on role or location.

Techniques depicted herein provide for a method for backup management for synchronized databases. In some cases, a set of databases managed by the computing system105may include a primary database instance and one or more standby instances which are kept in sync with the primary database instance. The DMS110may create a data backup group that includes a subset of the databases managed by the computing system105. For instance, the DMS110may identify that a primary and standby instance refer to the same database. Accordingly, when discovering databases for backup, the DMS110may discover a primary and standby instance as belonging to a single snapshot. Additionally or alternatively, the DMS110may implement the techniques depicted herein to run backups from both primary and standby databases. In some examples, a customer may have an ability to set a preference for which instance to run the backup on. For instance, a customer may indicate that the DMS110perform a backup procedure for a particular database of the set of databases (irrespective of the role for that database).

The DMS110may identify a set of databases managed by the computing system105. The set of databases may include a primary database and a set of standby databases configured to be synchronized with the primary database. The DMS110may then obtain, for the set of databases, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type. In some cases, standby databases of any type other than the first type (e.g., standby databases of any type other that the physical standby type) may be considered to be “of the second type.” In some examples, the DMS110may then identify a data backup group. The DMS110may include the first database in the data backup group based on determining that the first database is the primary database. The DMS110may include the one or more second databases in the data backup group based on determining that the one or more second databases are standby databases of the first type. In some examples, the DMS110may exclude the one or more third databases from the data backup group based on determining that the one or more second databases are standby databases of the second type.

Once a group is created, a customer may choose to take a backup from any of the member databases (of the data backup group) or based on role information for that member database. In the example depicted herein, the customer may choose to take a snapshot from the first database and the one or more second databases. In some cases, a customer can choose to take backups from the database that currently has the primary role or from a particular database irrespective of role. In some instances, the DMS110may track role information for the set of databases managed by the computing system105to detect the current role of the various database members in real time (as the roles can change during failover or switchover operations).

FIG.2illustrates an example of a system200that supports backup management for synchronized databases in accordance with aspects of the present disclosure. The system200includes a user device205, a data storage infrastructure210and a data manager215(e.g., data backup management system). The user device205may be an example of a device described with reference toFIG.1. The user device205may also be an example of a cloud client. A cloud client may access data sources using a network connection. The network may implement transfer control protocol and internet protocol (TCP/IP), such as the Internet, or may implement other network protocols. The user device205may be an example of a user device, such as a server, a smartphone, or a laptop. In other examples, a user device205may be a desktop computer, a tablet, a sensor, or another computing device or system capable of generating, analyzing, transmitting, or receiving communications. In some examples, the user device205may be operated by a user that is part of a business, an enterprise, a non-profit, a startup, or any other organization type.

The data storage infrastructure210may include a first database225-a, a second database225-b, a third database225-c, and a fourth database225-d. Although not depicted herein, the data storage infrastructure210may include more than four databases225. The databases225may be geographically separated from each other. In some examples, the databases225may include primary databases and standby databases. As depicted in the example ofFIG.2, the data storage infrastructure210may include a cloud platform220. The cloud platform220may offer storage and computing services to the user device205. In some cases, the data storage infrastructure210may be an example of a storage system. In some examples, the data manager215may provide backup and additional data management for the data storage infrastructure. The data manager215may serve multiple users with a single instance of software. However, other types of systems may be implemented, including—but not limited to—client-server systems, mobile device systems, and mobile network systems. The data manager215may be an example of an integrated data management and storage system. The data manager215may include an application server235. The application server235may represent a unified storage system even though numerous storage nodes may be connected together and the number of connected storage nodes may change over time as storage nodes are added to or removed. The data manager215may also be an example of a cloud-based storage and an on-demand computing platform.

As depicted herein, the system200may support an integrated data management and storage system and may be configured to manage the automated storage, backup, deduplication, replication, recovery, and archival of data within and across physical and virtual computing environments. The system200including an integrated data management and storage system may provide a unified primary and secondary storage system with built-in data management that may be used as both a backup storage system and a “live” primary storage system for primary workloads. In some cases, the integrated data management and storage system may manage dynamic versions when performing data storage. In some examples, the system200may provide backup of data (e.g., one or more files) using parallelized workloads, where the data may reside on virtual machines and/or real machines (e.g., a hardware server, a laptop, a tablet computer, a smartphone, or a mobile computing device).

According to aspects depicted herein, the system200supports backup management for multiple databases225(e.g., databases running in a clustered setup). In some examples, the data manager215may obtain role information for the set of databases225. In some examples, the role information may indicate a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type. In some examples, backups of datafiles and archived redo logs taken from a physical standby database may be fully interchangeable with primary backups. In other words, the data manager215may restore a backup of a physical standby datafile to the primary database, and may restore a backup of a primary datafile to the physical standby database. Thus, the data manager215may identify physical standbys and primary databases as being part of a new entity—a data backup group for the purpose of backup and recovery.

In the example ofFIG.2, the data manager215may determine that Node1is the primary database, Node2and Node3are physical standby databases and Node4is a logical standby database. Based on the role information, the data manager215may identify a data backup group for performing a backup procedure. The first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based at on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type. Returning to theFIG.2, the data manager215may include Node1, Node2and Node3in the data backup group and may exclude Node4from the data backup group. The data manager215may then perform a backup procedure for the set of databases (all databases manager by the cloud platform220) based on generating a snapshot of a database within the data backup group. That is, the data manager215may perform a backup procedure for Node1, Node2, Node3and Node4by generating a snapshot of a database (either Node1, Node2or Node3) within the data backup group. In some examples, the data manager215may choose a database for generating a snapshot based on one or more rules.

A user may transmit a request including a backup instruction270. The data storage infrastructure210may include or otherwise support change of role information for the databases. In such a setup, utilizing the techniques depicted herein, the system200may manage backup for the databases even when their role changes. In some examples, the data manager215may identify a change in the role information for the set of databases225. In some cases, the change in the role information may indicate that a role for at least one database of the one or more third databases has changed from standby database of the second type to standby database of the first type. For example, the data manager215may determine that Node4has changed from being a logical standby database to being a physical standby database. Based on the change in role information, the data manager215may include Node4in the data backup group. The updated data backup group in this example may include Node1, Node2, Node3and Node4.

In some examples, the system200may support performing a backup procedure according to one or more rules (e.g., backup instructions270). The data manager215may identify one or more rules for selecting the database within the data backup group for the backup procedure. The data manager215may then select the database for the backup procedure based on the one or more rules, where a snapshot of the database may be generated as part of the backup procedure based on the database being selected. For example, a customer using the user device205may indicate that the data manager215is to back up a primary database from the data backup group. Thus, if the role information changes over time, the data manager215may track such role information to identify the primary database and may generate a snapshot from the newly designated primary database (i.e., the database designated as a primary database after change in role information). Additionally or alternatively, the data manager215may receive backup instructions270indicating that the data manager215is to back up a particular database from the data backup group irrespective of the role information.

According to aspects depicted herein, the data manager215may identify a change in the role information for the set of databases. For example, the data manager215may identify that Node2has been designated the new primary database (e.g., due to failover or switch of databases). In such cases, the data manager215may identify a second database (e.g., Node2) within the data backup group for generating a second snapshot based on one or more rules and the change in the role information for the set of databases. That is, if the rules suggest that the data manager215is to generate a snapshot from the primary database, the data manager215may select Node2to generate a snapshot based on identifying that Node2is the new primary database. The data manager215may then perform the backup procedure for the set of databases based on generating a second snapshot of the second database (Node2) within the data backup group.

Additionally or alternatively, one or more rules (e.g., backup instructions270) may indicate that the backup procedure for the set of databases includes generating a snapshot of the first database (e.g., Node1) irrespective of the role information for the first database. In such cases, even if the data manager215determines that Node2has been designated as the new primary database, the data manager215may continue to generate a snapshot from Node1.

The system200may support managing the archived logs for the data storage infrastructure210after the databases are backed up. The data manager215may delete the archived logs on the data storage infrastructure210after they are backed up. Since there can be a delay in importing the archived logs from primary to standby databases, the primary databases may include a host log retention configuration. The data manager215may thus determine a conclusion of the backup procedure for the set of databases based on generating the snapshot of the database within the data backup group. The data manager215may then delete one or more archived logs for the subset of databases included in the data backup group based on determining the conclusion of the backup procedure. The data manager215may take log backups from either the primary database or one of the standby databases. In some examples, the data manager215may delete the archived logs on the node from which the logs were backed up. The data manager251may also automatically manage the archived logs on all the member nodes of the data backup group.

In some examples, the data manager215may store a log backup for the database within the data backup group. For example, the data manager15may store the log backup in the metadata store230. The data manager215may store one copy of log backups even when data manager215switches to back up from another member. Thus, the metadata store230maintains one recoverable chain for the data backup group. In some examples, the application server235may retrieve240the stored logs from the metadata store230to identify what time ranges are recoverable by backups. During a failover, the data manager215may identify a timestamp associated with the latest snapshot. Based on the stored log information, the data manager215may capture an incremental snapshot from the timestamp associated with the latest snapshot (instead of taking a full back up). For instance, the data manager215may identify a change in the role information for the set of databases. The data manager215may identify a switch over or may identify that a new database has been designated as the primary database. In such cases, the data manager215may generate a second snapshot of a second database within the data backup group based on the change in the role information. The second snapshot may include an incremental snapshot based on continuing to store the log backup for the database. The data manager215may generate a second log backup for the second database. In such instances, the log backup for the database may be for a first set of transactions and the second log backup for the second database may be for a second set of transactions that are subsequent to the first set of transactions. Thus, the log management implemented by the data manager215not only deletes logs on the server from which they were backed up but also from other members of the data backup group.

FIG.3illustrates an example of a process flow300that supports backup management for synchronized databases in accordance with aspects of the present disclosure. The process flow300includes a data management platform305and a data storage infrastructure310. The data management platform305may include an application server and a metadata storage as described with respect toFIG.2. The data storage infrastructure310may include multiple databases as described with respect toFIG.2. Although a single entity is depicted as data management platform305, it may be understood that components of the data management platform305may be located in different locations.

At315, the data management platform305may obtain, for a set of databases that comprises a primary database and a plurality of standby databases configured to be synchronized with the primary database, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type. In some examples, the standby databases of the first type may include physical standby databases and the standby databases of the second type may include logical standby databases, snapshot standby databases, far sync standby databases, or any combination thereof. The set of databases may be located in two or more geographically distributed locations.

At320, the data management platform305may identify, based on the role information for the set of databases, a data backup group that includes a subset of the databases. In some examples, the first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type.

At325, the data management platform305may identify a change in the role information for the set of databases. In some examples, the change in the role information indicates that a role for at least one database of the one or more third databases has changed from standby database of the second type to standby database of the first type.

At330, the data management platform305may identify an updated data backup group based on the change in the role information for the set of databases. In some examples, the at least one database of the one or more third databases is included in the updated data backup group based on being standby database of the first type. At335, the data management platform305may store a log backup for the database within the data backup group.

At340, the data management platform305may perform a backup procedure for the set of databases based on generating a snapshot of a database within the data backup group. In some examples, the backup procedure may include a backup of datafiles and log files of the database within the data backup group. The snapshot may include a full snapshot or an incremental snapshot. In some examples, a single snapshot of a single database is generated as part of the backup procedure for the set of databases, the single snapshot including the snapshot of the database.

At345, the data management platform305may determine a conclusion of the backup procedure for the set of databases based on generating the snapshot of the database within the data backup group. The data management platform305may then delete one or more archived logs for the subset of databases included in the data backup group based on determining the conclusion of the backup procedure.

FIG.4shows a block diagram400of a system405that supports backup management for synchronized databases in accordance with aspects of the present disclosure. In some examples, the system405may be an example of aspects of one or more components described with reference toFIG.1, such as a DMS110. The system405may include an input interface410, an output interface415, and a data backup component420. The system405may also include one or more processors. Each of these components may be in communication with one another (e.g., via one or more buses, communications links, communications interfaces, or any combination thereof).

The input interface410may manage input signaling for the system405. For example, the input interface410may receive input signaling (e.g., messages, packets, data, instructions, commands, or any other form of encoded information) from other systems or devices. The input interface410may send signaling corresponding to (e.g., representative of or otherwise based on) such input signaling to other components of the system405for processing. For example, the input interface410may transmit such corresponding signaling to the data backup component420to support backup management for synchronized databases. In some cases, the input interface410may be a component of a network interface515as described with reference toFIG.5.

The output interface815may manage output signaling for the system805. For example, the output interface815may receive signaling from other components of the system805, such as the data backup component820, and may transmit such output signaling corresponding to (e.g., representative of or otherwise based on) such signaling to other systems or devices. In some cases, the output interface815may be a component of a network interface1015as described with reference toFIG.10.

For example, the data backup component420may include a role information component425, a data backup group identification component430, a backup procedure component435, or any combination thereof. In some examples, the data backup component420, or various components thereof, may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the input interface810, the output interface815, or both. For example, the data backup component820may receive information from the input interface810, send information to the output interface815, or be integrated in combination with the input interface810, the output interface815, or both to receive information, transmit information, or perform various other operations as described herein.

The data backup component420may support data backup in accordance with examples as disclosed herein. The role information component425may be configured as or otherwise support a means for obtaining, for a set of databases that includes a primary database and a set of multiple standby databases configured to be synchronized with the primary database, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type. The data backup group identification component430may be configured as or otherwise support a means for identifying, based on the role information for the set of databases, a data backup group that includes a subset of the databases, where the first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type. The backup procedure component435may be configured as or otherwise support a means for performing a backup procedure for the set of databases based on generating a snapshot of a database within the data backup group.

FIG.5shows a block diagram500of a data backup component520that supports backup management for synchronized databases in accordance with aspects of the present disclosure. The data backup component520may be an example of aspects of a data backup component420as described herein. The data backup component520, or various components thereof, may be an example of means for performing various aspects of backup management for synchronized databases as described herein. For example, the data backup component520may include a role information component525, a data backup group identification component530, a backup procedure component535, a rule identification component540, a log component545, a metadata component550, a database identification component555, an input component560, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses, communications links, communications interfaces, or any combination thereof).

The data backup component520may support data backup in accordance with examples as disclosed herein. The role information component525may be configured as or otherwise support a means for obtaining, for a set of databases that includes a primary database and a set of multiple standby databases configured to be synchronized with the primary database, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type. The data backup group identification component530may be configured as or otherwise support a means for identifying, based on the role information for the set of databases, a data backup group that includes a subset of the databases, where the first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type. The backup procedure component535may be configured as or otherwise support a means for performing a backup procedure for the set of databases based on generating a snapshot of a database within the data backup group.

In some examples, the role information component525may be configured as or otherwise support a means for identifying a change in the role information for the set of databases, where the change in the role information indicates that a role for at least one database of the one or more third databases has changed from standby database of the second type to standby database of the first type. In some examples, the data backup group identification component530may be configured as or otherwise support a means for identifying an updated data backup group based on the change in the role information for the set of databases, where the at least one database of the one or more third databases is included in the updated data backup group based on being standby database of the first type.

In some examples, the rule identification component540may be configured as or otherwise support a means for identifying one or more rules for selecting the database within the data backup group for the backup procedure. In some examples, the database identification component555may be configured as or otherwise support a means for selecting the database for the backup procedure based at least in part on the one or more rules, wherein the snapshot of the database is generated (e.g., as part of the backup procedure for the set of databases) based at least in part on the database being selected for the backup procedure.

In some examples, the role information component525may be configured as or otherwise support a means for identifying a change in the role information for the set of databases. In some examples, the database identification component555may be configured as or otherwise support a means for selecting, based on the one or more rules and the change in the role information for the set of databases, a second database within the data backup group for generating a second snapshot as part of a second backup procedure for the set of databases. In some examples, the backup procedure component535may be configured as or otherwise support a means for performing the second backup procedure for the set of databases based on generating the second snapshot of the second database.

In some examples, the input component560may be configured as or otherwise support a means for receiving, from a user device, an input indicating the one or more rules for selecting the database within the data backup group for the backup procedure. In some examples, the one or more rules indicate that the backup procedure for the set of databases includes generating a snapshot of the primary database.

In some examples, the one or more rules indicate that the backup procedure for the set of databases includes generating a snapshot of the first database irrespective of the role information for the first database.

In some examples, the backup procedure component535may be configured as or otherwise support a means for determining a conclusion of the backup procedure for the set of databases based on generating the snapshot of the database within the data backup group. In some examples, the backup procedure component535may be configured as or otherwise support a means for deleting one or more archived logs for the subset of databases included in the data backup group based on determining the conclusion of the backup procedure.

In some examples, the log component545may be configured as or otherwise support a means for storing a log backup for the database within the data backup group. In some examples, the role information component525may be configured as or otherwise support a means for identifying a change in the role information for the set of databases. In some examples, the backup procedure component535may be configured as or otherwise support a means for generating a second snapshot of a second database within the data backup group based on the change in the role information, where the second snapshot is an incremental snapshot based on continuing to store the log backup for the database.

In some examples, the log component545may be configured as or otherwise support a means for generating a second log backup for the second database, where the log backup for the database is for a first set of transactions and the second log backup for the second database is for a second set of transactions that are subsequent to the first set of transactions.

In some examples, the metadata component550may be configured as or otherwise support a means for storing metadata associated with the database based on performing the backup procedure for the set of databases. In some examples, the set of databases are located in two or more geographically distributed locations.

In some examples, the backup procedure includes a backup of datafiles and log files of the database within the data backup group. In some examples, the snapshot includes a full snapshot or an incremental snapshot.

In some examples, the standby databases of the first type include physical standby databases and the standby databases of the second type include logical standby databases, snapshot standby databases, far sync standby databases, or any combination thereof. In some examples, a single snapshot of a single database is generated as part of the backup procedure for the set of databases, the single snapshot including the snapshot of the database.

FIG.6shows a diagram of a system605that supports backup management for synchronized databases in accordance with aspects of the present disclosure. The system605may be an example of or include aspects of a system405as described herein. The system605may include components for data management, including components such as a data backup component610, a network interface615, memory620, processor625, and storage630. These components may be in electronic communication or otherwise coupled with each other (e.g., operatively, communicatively, functionally, electronically, electrically; via one or more buses, communications links, communications interfaces, or any combination thereof). Additionally, the components of the system605may comprise corresponding physical components or may be implemented as corresponding virtual components (e.g., components of one or more virtual machines). In some examples, the system605may be an example of aspects of one or more components described with reference toFIG.1, such as a DMS110.

The network interface615may enable the system605to exchange information (e.g., input information635, output information640, or both) with other systems or devices (not shown). For example, the network interface615may enable the system605to connect to a network (e.g., a network120as described herein). The network interface615may include one or more wireless network interfaces, one or more wired network interfaces, or any combination thereof. In some examples, the network interface615may be an example of may be an example of aspects of one or more components described with reference toFIG.1, such as one or more network interfaces165.

Memory620may include RAM, ROM, or both. The memory620may store computer-readable, computer-executable software including instructions that, when executed, cause the processor625to perform various functions described herein. In some cases, the memory620may contain, among other things, a basic input/output system (BIOS), which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some cases, the memory620may be an example of aspects of one or more components described with reference toFIG.1, such as one or more memories175.

The processor625may include an intelligent hardware device, (e.g., a general-purpose processor, a digital signal processor (DSP), a CPU, a microcontroller, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). The processor625may be configured to execute computer-readable instructions stored in a memory620to perform various functions (e.g., functions or tasks supporting backup management for synchronized databases). Though a single processor625is depicted in the example ofFIG.6, it is to be understood that the system605may include any quantity of one or more of processors625and that a group of processors625may collectively perform one or more functions ascribed herein to a processor, such as the processor625. In some cases, the processor625may be an example of aspects of one or more components described with reference toFIG.1, such as one or more processors170.

Storage630may be configured to store data that is generated, processed, stored, or otherwise used by the system605. In some cases, the storage630may include one or more HDDs, one or more SDDs, or both. In some examples, the storage630may be an example of a single database, a distributed database, multiple distributed databases, a data store, a data lake, or an emergency backup database. In some examples, the storage630may be an example of one or more components described with reference toFIG.1, such as one or more network disks180.

The data backup component610may support data backup in accordance with examples as disclosed herein. For example, the data backup component610may be configured as or otherwise support a means for obtaining, for a set of databases that includes a primary database and a set of multiple standby databases configured to be synchronized with the primary database, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type. The data backup component610may be configured as or otherwise support a means for identifying, based on the role information for the set of databases, a data backup group that includes a subset of the databases, where the first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type. The data backup component610may be configured as or otherwise support a means for performing a backup procedure for the set of databases based on generating a snapshot of a database within the data backup group.

FIG.7shows a flowchart illustrating a method700that supports backup management for synchronized databases in accordance with aspects of the present disclosure. The operations of the method700may be implemented by a system or its components as described herein. For example, the operations of the method700may be performed by a DMS as described with reference toFIGS.1through6. In some examples, a DMS may execute a set of instructions to control the functional elements of the DMS to perform the described functions. Additionally, or alternatively, the DMS may perform aspects of the described functions using special-purpose hardware.

At705, the method may include obtaining, for a set of databases that includes a primary database and a set of multiple standby databases configured to be synchronized with the primary database, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type. The operations of705may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of705may be performed by a role information component525as described with reference toFIG.5.

At710, the method may include identifying, based on the role information for the set of databases, a data backup group that includes a subset of the databases, where the first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type. The operations of710may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of710may be performed by a data backup group identification component530as described with reference toFIG.5.

At715, the method may include performing a backup procedure for the set of databases based on generating a snapshot of a database within the data backup group. The operations of715may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of715may be performed by a backup procedure component535as described with reference toFIG.5.

FIG.8shows a flowchart illustrating a method800that supports backup management for synchronized databases in accordance with aspects of the present disclosure. The operations of the method800may be implemented by a system or its components as described herein. For example, the operations of the method800may be performed by a DMS as described with reference toFIGS.1through6. In some examples, a DMS may execute a set of instructions to control the functional elements of the DMS to perform the described functions. Additionally, or alternatively, the DMS may perform aspects of the described functions using special-purpose hardware.

At805, the method may include obtaining, for a set of databases that includes a primary database and a set of multiple standby databases configured to be synchronized with the primary database, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type. The operations of805may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of805may be performed by a role information component525as described with reference toFIG.5.

At810, the method may include identifying, based on the role information for the set of databases, a data backup group that includes a subset of the databases, where the first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type. The operations of810may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of810may be performed by a data backup group identification component530as described with reference toFIG.5.

At815, the method may include performing a backup procedure for the set of databases based on generating a snapshot of a database within the data backup group. The operations of815may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of815may be performed by a backup procedure component535as described with reference toFIG.5.

At820, the method may include identifying a change in the role information for the set of databases, where the change in the role information indicates that a role for at least one database of the one or more third databases has changed from standby database of the second type to standby database of the first type. The operations of820may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of820may be performed by a role information component525as described with reference toFIG.5.

At825, the method may include identifying an updated data backup group based on the change in the role information for the set of databases, where the at least one database of the one or more third databases is included in the updated data backup group based on being standby database of the first type. The operations of825may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of825may be performed by a data backup group identification component530as described with reference toFIG.5.

FIG.9shows a flowchart illustrating a method900that supports backup management for synchronized databases in accordance with aspects of the present disclosure. The operations of the method900may be implemented by a system or its components as described herein. For example, the operations of the method900may be performed by a DMS as described with reference toFIGS.1through6. In some examples, a DMS may execute a set of instructions to control the functional elements of the DMS to perform the described functions. Additionally, or alternatively, the DMS may perform aspects of the described functions using special-purpose hardware.

At905, the method may include obtaining, for a set of databases that includes a primary database and a set of multiple standby databases configured to be synchronized with the primary database, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type. The operations of905may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of905may be performed by a role information component525as described with reference toFIG.5.

At910, the method may include identifying, based on the role information for the set of databases, a data backup group that includes a subset of the databases, where the first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type. The operations of910may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of910may be performed by a data backup group identification component530as described with reference toFIG.5.

At915, the method may include identifying one or more rules for selecting a database within the data backup group for generating a snapshot as part of a backup procedure for the set of databases. The operations of915may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of915may be performed by a rule identification component540as described with reference toFIG.5.

At920, the method may include performing the backup procedure for the set of databases based on generating the snapshot of the database. The operations of920may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of920may be performed by a backup procedure component535as described with reference toFIG.5.

At925, the method may include identifying a change in the role information for the set of databases. The operations of925may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of925may be performed by a role information component525as described with reference toFIG.5.

At930, the method may include selecting, based on the one or more rules and the change in the role information for the set of databases, a second database within the data backup group for generating a second snapshot as part of a second backup procedure for the set of databases. The operations of930may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of930may be performed by a database identification component555as described with reference toFIG.5.

At935, the method may include performing the second backup procedure for the set of databases based on generating the second snapshot of the second database within the data backup group. The operations of935may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of935may be performed by a backup procedure component535as described with reference toFIG.5.

FIG.10shows a flowchart illustrating a method1000that supports backup management for synchronized databases in accordance with aspects of the present disclosure. The operations of the method1000may be implemented by a system or its components as described herein. For example, the operations of the method1000may be performed by a DMS as described with reference toFIGS.1through6. In some examples, a DMS may execute a set of instructions to control the functional elements of the DMS to perform the described functions. Additionally, or alternatively, the DMS may perform aspects of the described functions using special-purpose hardware.

At1005, the method may include obtaining, for a set of databases that includes a primary database and a set of multiple standby databases configured to be synchronized with the primary database, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type. The operations of1005may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1005may be performed by a role information component525as described with reference toFIG.5.

At1010, the method may include identifying, based on the role information for the set of databases, a data backup group that includes a subset of the databases, where the first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type. The operations of1010may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1010may be performed by a data backup group identification component530as described with reference toFIG.5.

At1015, the method may include performing a backup procedure for the set of databases based on generating a snapshot of a database within the data backup group. The operations of1015may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1015may be performed by a backup procedure component535as described with reference toFIG.5.

At1020, the method may include determining a conclusion of the backup procedure for the set of databases based on generating the snapshot of the database within the data backup group. The operations of1020may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1020may be performed by a backup procedure component535as described with reference toFIG.5.

At1025, the method may include deleting one or more archived logs for the subset of databases included in the data backup group based on determining the conclusion of the backup procedure. The operations of1025may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of1025may be performed by a backup procedure component535as described with reference toFIG.5.

A method for data backup is described. The method may include obtaining, for a set of databases that includes a primary database and a set of multiple standby databases configured to be synchronized with the primary database, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type, identifying, based on the role information for the set of databases, a data backup group that includes a subset of the databases, where the first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type, and performing a backup procedure for the set of databases based on generating a snapshot of a database within the data backup group.

An apparatus for data backup is described. The apparatus may include at least one processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the at least one processor to cause the apparatus to obtain, for a set of databases that includes a primary database and a set of multiple standby databases configured to be synchronized with the primary database, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type, identify, based on the role information for the set of databases, a data backup group that includes a subset of the databases, where the first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type, and perform a backup procedure for the set of databases based on generating a snapshot of a database within the data backup group.

Another apparatus for data backup is described. The apparatus may include means for obtaining, for a set of databases that includes a primary database and a set of multiple standby databases configured to be synchronized with the primary database, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type, means for identifying, based on the role information for the set of databases, a data backup group that includes a subset of the databases, where the first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type, and means for performing a backup procedure for the set of databases based on generating a snapshot of a database within the data backup group.

A non-transitory computer-readable medium storing code for data backup is described. The code may include instructions executable by at least one processor to obtain, for a set of databases that includes a primary database and a set of multiple standby databases configured to be synchronized with the primary database, role information that indicates a first database as the primary database, one or more second databases as standby databases of a first type, and one or more third databases as standby databases of a second type, identify, based on the role information for the set of databases, a data backup group that includes a subset of the databases, where the first database is included in the data backup group based on being the primary database, the one or more second databases are included in the data backup group based on being standby databases of the first type, and the one or more third databases are excluded from the data backup group based on being standby databases of the second type, and perform a backup procedure for the set of databases based on generating a snapshot of a database within the data backup group.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying a change in the role information for the set of databases, where the change in the role information indicates that a role for at least one database of the one or more third databases may have changed from standby database of the second type to standby database of the first type and identifying an updated data backup group based on the change in the role information for the set of databases, where the at least one database of the one or more third databases may be included in the updated data backup group based on being standby database of the first type.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying one or more rules for selecting the database within the data backup group for the backup procedure, and selecting the database for the backup procedure based at least in part on the one or more rules, where the snapshot of the database is generated based at least in part on the database being selected for the backup procedure.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying a change in the role information for the set of databases, selecting, based on the one or more rules and the change in the role information for the set of databases, a second database within the data backup group for generating a second snapshot as part of a second backup procedure for the set of databases, and performing the second backup procedure for the set of databases based on generating the second snapshot of the second database.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from a user device, an input indicating the one or more rules for selecting the database within the data backup group for the backup procedure.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the one or more rules indicate that the backup procedure for the set of databases includes generating a snapshot of the primary database.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the one or more rules indicate that the backup procedure for the set of databases includes generating a snapshot of the first database irrespective of the role information for the first database.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining a conclusion of the backup procedure for the set of databases based on generating the snapshot of the database within the data backup group and deleting one or more archived logs for the subset of databases included in the data backup group based on determining the conclusion of the backup procedure.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for storing a log backup for the database within the data backup group, identifying a change in the role information for the set of databases, and generating a second snapshot of a second database within the data backup group based on the change in the role information, where the second snapshot may be an incremental snapshot based on continuing to store the log backup for the database.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for generating a second log backup for the second database, where the log backup for the database may be for a first set of transactions and the second log backup for the second database may be for a second set of transactions that may be subsequent to the first set of transactions.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for storing metadata associated with the database based on performing the backup procedure for the set of databases.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the set of databases may be located in two or more geographically distributed locations. In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the backup procedure includes a backup of datafiles and log files of the database within the data backup group.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the snapshot includes a full snapshot or an incremental snapshot. In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the standby databases of the first type include physical standby databases and the standby databases of the second type include logical standby databases, snapshot standby databases, far sync standby databases, or any combination thereof.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, a single snapshot of a single database may be generated as part of the backup procedure for the set of databases, the single snapshot including the snapshot of the database.