Delphix Corporation

Oracle International Corporation

Hubert Ken Sun

Michael James Stewart

Wei-Ming Hu

Mark Dilman

Balasubrahmanyam Kuchibhotla

Matthew Allan Ahrens

Matthew Benjamin Amdur

Kevin S Neel

Kant C Patel

Feroz Alam Khan

Leonid Novak

Bhaskar Mathur

Eric Noah Schrock

Christopher G Siden

Lakshminaray Chidambaran

Saravanakumar Ramasubramanian

Henrik Mattsson

Kyle Cackett

Margaret Susairaj

Margaret Susairai

Information from source databases is retrieved and stored on a database storage system. Multiple point-in-time copies are obtained for each database. A source database may contain partitions comprising sets of database tables. A partition is imported into a virtual database created. The database storage system validates the partition before importing, by checking whether the partition includes database tables that refer to database tables outside the partition. A partition imported in a virtual database may be rewinded to an older state or refreshed to a more recent state. Multiple partitions may be included in a virtual database and the state of each partition modified independent of the state of the remaining virtual database including the other partitions. Multiple versions of the same partition corresponding to different points in time are incorporated in the same virtual database, thereby allowing a query to process different versions of the same database table.

Virtual partitions in virtual databases

A storage system performs transformations of data stored as source snapshots to obtain transformed snapshots. The storage system stores relations between source snapshots, for example, parent child relationships. The storage system analyzes relationships between source snapshots to determine relationships between transformed snapshots. The storage system creates a transformed snapshot based on a source snapshot. The storage system traverses the graph representing source snapshots to identify ancestor or descendants of the source snapshots that were previously transformed. The storage system determines the transformed snapshots corresponding to the ancestor and descendant source snapshots and relates them to the newly created transformed snapshot.

Managing transformed snapshots in a storage system

A database storage system creates secure snapshots or virtual databases based on a source database that stores sensitive information. The database storage system applies a masking function to the sensitive data and stores the masked data in the secure snapshot. The database storage system creates secure snapshots that share masked database blocks with other secure snapshots. The database storage system shares masked database blocks by storing information identifying a previously created masked database block for a new secure snapshot. If a masked database block for the new secure snapshot is different from the previously created masked database block, the database storage system stores metadata including the difference between the two masked database blocks. The database storage system allows sharing any transformed database blocks across snapshot, if the transformed database blocks are obtained by applying a transformation function to data of the source database.

Creating secure virtual databases storing masked data

A storage system executes transform scripts to transform data stored in a source snapshot to obtain transformed snapshot. A transform script may be used to upgrade data stored in a snapshot from a version of an application to a newer version of the application. The storage system stores intermediate snapshots during execution of a transform scripts. The storage system reuses data stored during execution of transform scripts to optimize execution of newer transform scripts. For example, the storage system identifies a previously executed transform script having a matching prefix of transform operations and reuses an intermediate snapshot obtained by executing the matching prefix. The storage system processes the intermediate snapshot by executing the remaining transform operations of the new transform script.

Managing transformations of snapshots in a storage system

A source storage system replicates snapshots stored on the source storage system to a target storage system. The source storage system stores a plurality of snapshots. The source storage system also stores parent child relationships between snapshots. The source storage system allows child snapshots of a parent snapshot to be modified independent of each other. The source storage system determines changed blocks of a snapshot compared to a previously transmitted snapshot and sends only the changed blocks to the target storage system. The source storage system determines the changed blocks of a snapshot compared to a previously replicated snapshot based on time of creation of a common ancestor of two snapshots. The source storage system transmits a data block of a snapshot if either the data block or a corresponding data block of the previously replicated snapshot was modified after the creation of the common ancestor snapshot.

Replicating snapshots from a source storage system to a target storage system

A database storage system allows users to modify the state of a virtual database. The database storage system provides a respective virtual database (VDB) at a respective destination, the respective VDB having a first timeflow stored in a respective container. A user can send a request to rewind a VDB. The request identifies timeflow of the VDB and a state of the VDB associated with a timeflow. The database storage system modifies the virtual database to refer to database blocks associated with a snapshot of the VDB associated with the identified timeflow. The database storage system maintains a new timeflow for the modified VDB. The database storage system also allows the virtual database to be refreshed to a state of a source database. The source database can be a database stored in an external system or a virtual database stored within the database storage system.

Virtual database rewind

Techniques are provided to allow users to define a global service that is offered across multiple replicated databases. Database clients connect to and use a global service just as they do with regular services on a single database today. Upon receiving a connection request, a collection of components, referred to collectively as the Global Data Service framework (GDS framework), automatically chooses the best database server instances to which to connect a client. Once those connections have been established, the clients determine which database server instance, of those database server instances to which they are connected, to send requests to based, at least in part, on advisory messages sent to the clients by the GDS framework.

Providing services across systems that manage distributed replicas

A computer is programmed to execute a diagnostic procedure either on a pre-set schedule or asynchronously in response to an event, such as an error message, or a user command. When executed, the diagnostic procedure automatically checks for integrity of one or more portions of data in the computer, to identify any failure(s). In some embodiments, the failure(s) may be displayed to a human, after revalidation to exclude any failure that no longer exists.

Growing community of inventors

Menlo Park, CA, United States of America

Hubert Ken Sun