Abstract: 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.

Abstract: Systems and methods for an extended recovery of an exported database are described. The method includes communicating a database from a source host operating in a native database recovery environment, the database being communicated to a backup host operating in a foreign database recovery environment, the native database recovery environment including native snapshot files and native incremental files for storing the database, the foreign database recovery environment including foreign snapshot files and foreign incremental files for storing the database. The method further includes receiving file information and script information, at the source host, the file information including the native snapshot files and the native incremental files, the script to perform operations for causing a recovering of the database in the foreign database recovery environment based on the changes to the database in the foreign database recovery environment after the point-in-time.

Abstract: Techniques for data management are described. A request to mount a version of a database based on data stored at a computing system may be received. Based on receiving the request, a container at the computing that is configured to support operating the version of the database may be configured. Based on creating the container, a database request for the version of the database may be received at the container. In response to the database request, the container may access a set of data stored at the computing system, the set of data being associated with the version of the database. The container may output a response to the database request based on accessing the set of data.

Abstract: Techniques for data management are described. A request to mount a version of a database based on data stored at a computing system may be received. Based on receiving the request, a container at the computing that is configured to support operating the version of the database may be configured. Based on creating the container, a database request for the version of the database may be received at the container. In response to the database request, the container may access a set of data stored at the computing system, the set of data being associated with the version of the database. The container may output a response to the database request based on accessing the set of data.

Abstract: Methods, systems, and techniques for analyzing a web browser extension are disclosed. A method of analyzing a web browser extension comprises: obtaining source code of the web browser extension; analyzing the source code to determine a risk posed by the web browser extension; and generating an indication of risk posed by the web browser extension based on the analysis of the source code.

Abstract: Techniques for data management are described. A request to mount a version of a database based on data stored at a computing system may be received. Based on receiving the request, a container at the computing that is configured to support operating the version of the database may be configured. Based on creating the container, a database request for the version of the database may be received at the container. In response to the database request, the container may access a set of data stored at the computing system, the set of data being associated with the version of the database. The container may output a response to the database request based on accessing the set of data.

Abstract: A data management platform may receive, from a user of a data management platform, a first job request to perform a backup of data from a data source to a database managed by the user. In some examples, the database may be configured as a set of database instances running on a set of computing nodes of a computing cluster. The data management platform may store a backup load indication that indicates which computing node is assigned to perform the backup of the data based on receiving the first job request. The data management platform may receive one or more second job requests subsequent to receiving the first job request and may determine a backup load for one or more computing nodes of the set of computing nodes. The data management platform may then assign one or more target computing nodes for performing the one or more second job requests.

Abstract: 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.

Abstract: Systems and methods for utilizing tablespace to export from a foreign database recovery environment are described. The system includes a backup host that operates in a foreign database recovery environment and receives a database from a source host operating in a native database recovery environment. The backup host receives export information including a tablespace identifier and a point-in-time. The tablespace includes file information for export from the backup host to the source host. A job is initiated on the backup host to generate script information (including logic for execution on the source host to recover the tablespace, at the point-in-time, in the database on the source host), create directories on the backup host, materialize file information including snapshots of the database and incremental changes to the database, and communicate the file information and the script information, via the directories, to the source host.

Abstract: 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.

Abstract: A database can be instantly recovered by a cluster mapped to the database. Nodes of the cluster are mapped over channels to directories of the database. Scripts are generated from one or more templates that specify the order and values to be executed to perform a database job, such as database recovery. To recover the database, a template is executed that generates and populates scripts, which are processed on the host of the database to recover the database in a nearly instant manner without transferring data files.

Abstract: Systems and methods to export a database to a native database recovery, environment are described. The system includes a native database recovery environment that includes a target host. The target host receives file information and script information, over a network, via directories from a backup host. The backup host utilizes foreign snapshot files and foreign incremental files to store the file information in the foreign database recovery environment. The file information includes native snapshot files and native incremental files. The script information includes scripts that are executed by the target host in the native database recovery environment. The target host executes the scripts to mount the directories, open the database, restore the database, recover the database to a point-in-time, and unmount the directories.

Abstract: A database can be instantly cloned from a source device to a target device by a cluster mapped to a database to be cloned. Nodes of the cluster are mapped over channels to directories of the database. Scripts are generated from one or more templates that specify the order and values to be executed to perform a database job, such as cloning the database to the target device using the mappings. To clone the database, a template can be executed that generates and populates scripts, which can be executed on the target device to provide a functioning cloned database using the mapped cluster.

Abstract: Systems and methods for an extended recovery of an exported database are described. The method includes communicating a database from a source host operating in a native database recovery environment, the database being communicated to a backup host operating in a foreign database recovery environment, the native database recovery environment including native snapshot files and native incremental files for storing the database, the foreign database recovery environment including foreign snapshot files and foreign incremental files for storing the database. The method further includes receiving file information and script information, at the source host, the file information including the native snapshot files and the native incremental files, the script to perform operations for causing a recovering of the database in the foreign database recovery environment based on the changes to the database in the foreign database recovery environment after the point-in-time.

Abstract: Systems and methods to export a database from a foreign database recovery environment are described. The system includes the foreign database recovery environment that includes a backup host that receives the database from a source host operating in a native database recovery environment. The backup host utilizes foreign snapshot files and foreign incremental files for restoring the database. The backup host receives export information. The export information includes a target host, a point-in-time, and a database name identifying the database for export from the backup host to the target host. The backup host initiates a job that generates script information, creates directories, materializes file information, and communicates the script information and the file information, via the directories, to the target host.

Abstract: Systems and methods to optimize utilization of a tablespace for export from a native database recovery environment are described. The system receives a database from a source host, operating in a native database recovery environment, at a backup host operating in a foreign database recovery environment. The foreign database recovery environment utilizes foreign snapshot files and foreign incremental files for storing the database. The system receives a tablespace identifier that identifies a tablespace and a point-in-time that identifies file information for export from the backup host to the source host. The backup host initiates a job to generate script information; create directories; materialize the file information; utilize an auxiliary database to generate tablespace metadata information; and communicate the tablespace metadata information and the script information and the file information, via the directories, and over a network, to the source host, to enable the source host to recover the tablespace.

Abstract: A database can be backed up and recovered by a cluster mapped to the database. Nodes of the cluster are mapped over channels to directories of the database. Scripts are generated from one or more templates that specify the order and values to be executed to perform a database job, such as database backup or recovery. To initiate a given database job, a template can be executed that generates and populates scripts, which are processed on the host of the database to perform the database job in a nearly instant manner using the mapped nodes of the cluster.

Abstract: Systems and methods extending recovery of a database exported to a native database recovery environment are described. The system includes a native database recovery environment including a source host that communicates a database from a source to a backup host operating in a foreign database recovery environment. The backup host utilizes foreign snapshot files and foreign incremental files for storing the database in the foreign database recovery environment. The source host receives file information and script information, via directories, over the network, from the backup host. The file information includes native snapshot files and native incremental files.

Abstract: Systems and methods to export a database from a foreign database recovery environment are described. The system includes the foreign database recovery environment that includes a backup host that receives the database from a source host operating in a native database recovery environment. The backup host utilizes foreign snapshot files and foreign incremental files for restoring the database. The backup host receives export information. The export information includes a target host, a point-in-time, and a database name identifying the database for export from the backup host to the target host. The backup host initiates a job that generates script information, creates directories, materializes file information, and communicates the script information and the file information, via the directories, to the target host.

Abstract: Systems and methods to optimize utilization of a tablespace for export from a native database recovery environment are described. The system receives a database from a source host, operating in a native database recovery environment, at a backup host operating in a foreign database recovery environment. The foreign database recovery environment utilizes foreign snapshot files and foreign incremental files for storing the database. The system receives a tablespace identifier that identifies a tablespace and a point-in-time that identifies file information for export from the backup host to the source host. The backup host initiates a job to generate script information; create directories; materialize the file information; utilize an auxiliary database to generate tablespace metadata information; and communicate the tablespace metadata information and the script information and the file information, via the directories, and over a network, to the source host, to enable the source host to recover the tablespace.