# US 2021/0240660 A1 · Utilizing a tablespace to export from a foreign database recovery environment

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0240660 A1
- Document ID: US20210240660A1
- Status: Published application
- Kind: A1
- Application number: 16/776,981
- Filed: 2020-01-30
- Published: 2021-08-05
- Earliest claimed: 2020-01-30
- Assignees: Rubrik, Inc.
- Applicants: Rubrik, Inc.
- Inventors: Snehal Arvind Khandkar; Yongbing Guo; Udbhav Prasad
- Web page: https://patentgrep.com/patent/US20210240660A1

## CPC

- G06F 16/128: {Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16)}
- G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)}
- G06F 11/1451: {by selection of backup contents}
- G06F 11/1461: {Backup scheduling policy}
- G06F 11/1464: {for networked environments}
- G06F 11/1469: {Backup restoration techniques}
- G06F 11/2028: {eliminating a faulty processor or activating a spare}
- G06F 11/2038: {with a single idle spare processing component}
- G06F 11/2048: {where the redundant components share neither address space nor persistent storage}
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- G06F 11/2097: {maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups)}
- G06F 16/113: {Details of archiving (lifecycle management in storage systems G06F3/0649; point-in-time backing up or restoration of persistent data G06F11/1446)}
- G06F 16/1734: {Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs}
- G06F 16/1824: {implemented using Network-attached Storage [NAS] architecture (distributed or networked storage systems G06F3/067; protocols for distributed storage of data in a network H04L67/1097)}
- G06F 16/2282: {Tablespace storage structures; Management thereof}
- G06F 16/24573: {using data annotations, e.g. user-defined metadata}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/25: Integrating or interfacing systems involving database management systems
- G06F 2201/815: Virtual
- G06F 2201/835: Timestamp
- G06F 2201/84: Using snapshots, i.e. a logical point-in-time copy of the data
- G06F 2201/87: Monitoring of transactions
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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.

## Claims

### Claim 1

A system comprising:
at least one processor and memory having instructions that, when executed, cause the at least one processor to perform operations comprising:
receiving a database from a source host operating in a native database recovery environment, the database being received at a backup host operating in a foreign database recovery environment, the foreign database recovery environment utilizing foreign snapshot files and foreign incremental files for restoring the database;
receiving export information at the backup host, the export information including a tablespace identifier and a point-in-time that identifies a tablespace including file information for export from the backup host to the source host operating in the native database recovery environment;
initiating a job, on the backup host, responsive to receiving the export information, the job executing to cause the at least one processor to perform operations further comprising:
generating script information based on the export information, the script information including scripts including logic for execution on the source host to recover the tablespace, at the point-in-time, in the database on the source host in the native database recovery environment;
creating one or more directories on the backup host based on the export information;
materializing the file information on the backup host, the file information including snapshots of the database and incremental changes to the database, the file information to facilitate creation of an auxiliary database on the source host; and
communicating the file information and the script information, via the directories, and over a network, to the source host, the directories and the script information enabling the source host to recover the tablespace, at the point-in-time, in the database on the source host in the native database recovery environment.

### Claim 2 (depends on 1)

The system of claim 1, wherein the tablespace further includes tablespace metadata information including metadata for the tablespace.

### Claim 3 (depends on 2)

The system of claim 2, wherein the generating the script information includes initializing plug-in value information in a first template based on the export information.

### Claim 4 (depends on 1)

The system of claim 1, wherein the file information includes native snapshot files including the snapshots of the database and native incremental files including incremental changes to an image of the database, and a native control file including metadata for the database, wherein the file information includes table information for populating a table, wherein the database includes a wholesale distribution database, wherein the tablespace includes a shipping table, and wherein the shipping table includes a plurality of rows, each including shipping information.

### Claim 5 (depends on 4)

The system of claim 4, wherein the materializing the file information includes:
selecting the foreign snapshot files and the foreign incremental files based on the point-in-time; and
materializing the file information based on the foreign snapshot files and the foreign incremental files.

### Claim 6 (depends on 1)

The system of claim 1, wherein the communicating the file information, the script information, and tablespace metadata information, via the directories to the source host includes utilizing a network file system protocol to communicate the file information, the script information, and tablespace metadata information, via the directories, to the source host.

### Claim 7 (depends on 1)

The system of claim 1, wherein the scripts include logic to:
mount the directories on the source host;
open the auxiliary database on the source host;
restore the tablespace in the auxiliary database based on native snapshot files and the tablespace identifier, the auxiliary database including tablespace metadata information;
recover the tablespace in the auxiliary database based on native incremental files, the recovery including application of the incremental changes to the auxiliary database to recover the tablespace in the auxiliary database to the point-in-time that was selected;
export the tablespace metadata information from the auxiliary database;
recover the tablespace in the database, including:
import the tablespace metadata information to the database;
restore the tablespace in the database based on the native snapshot files and the tablespace identifier;
recover the tablespace in the database based on the native incremental files and the tablespace identifier, the recovery including application of the incremental changes to the database to recover the tablespace to the point-in-time that was selected; and
unmount the directories.

### Claim 8 (depends on 1)

The system of claim 1, wherein the database is a standalone database and the backup host includes a first node including a backup node.

### Claim 9 (depends on 1)

The system of claim 1, wherein the backup host comprises a plurality of nodes that stores a cluster database.

### Claim 10

A method comprising:
receiving a database from a source host operating in a native database recovery environment, the database being received at a backup host operating in a foreign database recovery environment, the foreign database recovery environment utilizing foreign snapshot files and foreign incremental files for restoring the database;
receiving export information at the backup host, the export information including a tablespace identifier and a point-in-time that identifies a tablespace including file information for export from the backup host to the source host operating in the native database recovery environment, the receiving the export information being performed by at least one processor;
initiating a job, on the backup host, responsive to receiving the export information, the job executing to perform operations further comprising:
generating script information based on the export information, the script information including scripts including logic for execution on the source host to recover the tablespace, at the point-in-time, in the database on the source host in the native database recovery environment;
creating one or more directories on the backup host based on the export information;
materializing the file information on the backup host, the file information including snapshots of the database and incremental changes to the database, the file information to facilitate creation of an auxiliary database on the source host; and
communicating the file information and the script information, via the directories, and over a network, to the source host, the directories and the script information enabling the source host to recover the tablespace, at the point-in-time, in the database on the source host in the native database recovery environment.

### Claim 11 (depends on 10)

The method of claim 10, wherein the tablespace further includes tablespace metadata information including metadata for the tablespace.

### Claim 12 (depends on 11)

The method of claim 11, wherein the generating the script information includes initializing plug-in value information in a first template based on the export information.

### Claim 13 (depends on 10)

The method of claim 10, wherein the file information includes native snapshot files including the snapshots of the database and native incremental files including incremental changes to an image of the database, and a native control file including metadata for the database, wherein the file information includes table information for populating a table, wherein the database includes a wholesale distribution database, wherein the tablespace includes a shipping table, and wherein the shipping table includes a plurality of rows, each including shipping information.

### Claim 14 (depends on 13)

The method of claim 13, wherein the materializing the file information includes:
selecting the foreign snapshot files and the foreign incremental files based on the point-in-time; and
materializing the file information based on the foreign snapshot files and the foreign incremental files.

### Claim 15 (depends on 10)

The method of claim 10, wherein the communicating the file information and the script information and the tablespace metadata information, via the directories, to the source host includes utilizing a network file system protocol to communicate the file information and the script information and tablespace metadata information, via the directories, to the source host.

### Claim 16 (depends on 10)

The method of claim 10, wherein the scripts include logic to:
mount the directories on the source host;
open the auxiliary database on the source host;
restore the tablespace in the auxiliary database based on native snapshot files and the tablespace identifier, the auxiliary database including tablespace metadata information;
recover the tablespace in the auxiliary database based on native incremental files, the recovery including application of the incremental changes to the auxiliary database to recover the tablespace in the auxiliary database to the point-in-time that was selected;
export the tablespace metadata information from the auxiliary database;
recover the tablespace in the database, including:
import the tablespace metadata information to the database;
restore the tablespace in the database based on the native snapshot files and the tablespace identifier;
recover the tablespace in the database based on the native incremental files and the tablespace identifier, the recovery including application of the incremental changes to the database to recover the tablespace to the point-in-time that was selected; and
unmount the directories.

### Claim 17 (depends on 10)

The method of claim 10, wherein the database is a standalone database and the backup host includes a first node including a backup node.

### Claim 18 (depends on 10)

The method of claim 10, wherein the backup host comprises a plurality of nodes that stores a cluster database.

### Claim 19

A machine-storage medium and staring a set of instructions that, when executed by a processor, causes a machine to perform operations comprising:
receiving a database from a source host operating in a native database recovery environment, the database being received at a backup host operating in a foreign database recovery environment, the foreign database recovery environment utilizing foreign snapshot files and foreign incremental files for restoring the database;
receiving export information at the backup host, the export information including a tablespace identifier and a point-in-time that identifies a tablespace including file information for export from the backup host to the source host operating in the native database recovery environment;
initiating a job, on the backup host, responsive to receiving the export information, the job executing to perform operations further comprising:
generating script information based on the export information, the script information including scripts including logic for execution on the source host to recover the tablespace, at the point-in-time, in the database on the source host in the native database recovery environment;
creating one or more directories on the backup host based on the export information;
materializing the file information on the backup host, the file information including snapshots of the database and incremental changes to the database, the file information to facilitate creation of an auxiliary database on the source host; and
communicating the file information and the script information, via the directories, and over a network, to the source host, the directories and the script information enabling the source host to recover the tablespace, at the point-in-time, in the database on the source host in the native database recovery environment.

### Claim 20 (depends on 19)

The machine-storage medium of claim 19, wherein the tablespace includes tablespace metadata information including metadata for the tablespace.