Methods, systems, and computer-readable storage media for receiving a capture file, the capture file holding data representative of a workload executed in a source database system, processing the capture file to provide a replay file, the replay file being in a format that is executable by a replayer to replay the workload in a target database system, the workload including a set of requests represented within the replay file, providing a set of tags associated with the replay file, the set of tags including one or more tags, each tag associated with a request in the set of requests, and during replay of the workload in the target database system: pausing replay of the workload in response to a tag, executing a request associated with the tag, providing replay results specific to the request, and selectively resuming replay of the workload in the target database system.

A computer program product, system, and computer implemented method for rapid database restoration using a database restore and recovery process that leverages one or more sparse data files and/or blocks by restoring one or more sparse data files and/or blocks and providing a mechanism to redirect requests to the one or more sparse data files and/or blocks to a backup copy of the actual data files and/or blocks and a process to populate the one or more sparse data files and/or blocks while the database is operational for servicing user requests. The approach includes the creation and population of one or more sparse data files and/or blocks, a redirection mechanism to service read operations where necessary, and a process to restore the data to one or more sparse data files and/or blocks over time, while the database maintains operability.

Techniques for providing direct access to backup data can include: receiving a selection of a backup of a file system, wherein the backup is stored on a backup system connected to a data storage system; creating, in accordance with said selection of the backup, a remote copy of the backup, wherein the remote copy is stored on the backup system; generating a proxy file system for the remote copy on the backup system, wherein the proxy file system is mapped by the data storage system to the remote copy on the backup system; and providing a host with direct access to the remote copy using the proxy file system.

Techniques are provided for incrementally restoring a virtual machine hosted by a computing environment. In response to receiving an indication that the virtual machine is to be incrementally restored, a snapshot of the virtual machine may be created while the virtual machine is shut down into an off state. The snapshot is transmitted to a storage environment as a common snapshot. The snapshot and the common snapshot are common snapshots comprising a same representation of the virtual machine. The common snapshot and a prior snapshot of the virtual machine are evaluated to identify a data difference of the virtual machine between the common snapshot and the prior snapshot. An incremental restore is performed of the virtual machine by transmitting the data difference from the storage environment to the computing environment to restore the virtual machine to a state represented by the prior snapshot.

Each of one or more commit cycles may be associated with a predicted number of updates. A statistics collection time for a database table can be determined by estimating a sum of predicted updates included in one or more commit cycles. Whether the estimated sum of predicted updates is greater than a first threshold may be determined. In addition, a progress point for a first one of the commit cycles can be determined. A time to collect statistics may be selected based on the progress point of the first commit cycle.

A point-in-time clone may be created for a database. A request to create the point-in-time clone may be received. The clone may be provided with access to a storage for the database that stores a history of modifications to the database applicable to return data of the database according to a state of the data at the specified point in time. The clone may then be updated so that the updates made to the clone are stored for subsequent access by the clone.

Provided are a database information backup method and recovery method, an electronic device, and a computer-readable storage medium. The backup method includes the following steps: a server receives a backup task instruction and mounts a storage volume to a client; the client receives the mounted storage volume and determines whether the backup task instruction is a full backup, and if so, the client starts a CDP thread, the client starts a VSS to create a volume shadow copy; the client determines whether the backup task instruction is a full backup, and if so, the client backs up valid data in the volume shadow copy, otherwise, the client backs up corresponding data in the volume shadow copy; the server creates a storage volume snapshot and a time point; and the server unloads a mapping mounted by the storage volume.

A first forwarding VM may execute in a first availability zone and have a first IP address. Similarly, a second forwarding VM may execute in a second availability zone and have a second IP address. The first and second IP addresses may be recorded with a cloud DNS web service of a cloud provider such that both receive requests from applications directed to a particular DNS name acting as a single endpoint. A service cluster may include a master VM node and a standby VM node. An IPtable in each forwarding VM may forward a request having a port value to a cluster port value associated with the master VM node. Upon a failure of the master VM node, the current standby VM node may be promoted to execute in master mode and the IPtables may be updated to now forward requests having the port value to a cluster port value associated with the newly promoted master VM node (which was previously the standby VM node).

Techniques are disclosed relating to maintaining a high availability (HA) database. In some embodiments, a computer system receives, from a plurality of host computers, a plurality of requests to access data stored in a database implemented using a plurality of clusters. In some embodiments, the computer system responds to the plurality of requests by accessing data stored in an active cluster. The computer system may then determine, based on the responding, health information for ones of the plurality of clusters, wherein the health information is generated based on real-time traffic for the database. In some embodiments, the computer system determines, based on the health information, whether to switch from accessing the active cluster to accessing a backup cluster. In some embodiments, the computer system stores, in respective clusters of the database, a changeover decision generated based on the determining.

Systems and methods to utilize a tablespace to export to a native database recovery environment are described. The system receives file information and script information at a source host that operates in a native database recovery environment. The file information and the script information are received from a backup host that utilizes foreign snapshot files and foreign incremental files for storing the file information. The file information includes native snapshot files and native incremental files. The script information includes one or more scripts that execute, at the source host, to perform operations comprising: mounting the directories; opening an auxiliary database; restoring a tablespace in the auxiliary database; recovering the tablespace in the auxiliary database based on the native incremental files; exporting the tablespace metadata information from the auxiliary database; recovering the tablespace in the database based on the tablespace metadata information; and unmounting the directories.