DATABASE POINT-IN-TIME RESTORE AND AS-OF QUERY
    1.
    发明申请
    DATABASE POINT-IN-TIME RESTORE AND AS-OF QUERY 有权
    DATABASE POINT-IN-TIME RESTORE和AS-OF QUERY

    公开(公告)号:US20130212068A1

    公开(公告)日:2013-08-15

    申请号:US13370125

    申请日:2012-02-09

    IPC分类号: G06F7/00

    CPC分类号: G06F17/30144 G06F17/30088

    摘要: A database is queried as of any wall-clock time within a retention period, via undo that uses database snapshots and a list of page level modifications. The snapshot is user-identified, automatically generated, or extracted from a backup. The list is maintained in a transaction log by persisting page content before a page is re-used, persisting deleted rows before they are moved, persisting compensation log record undo information, and/or logging a full page. To rewind an entire database, the undo scans the transaction log in reverse LSN order and undoes all page modifications. Undo reverses reallocated pages, table truncation, and/or table deletion, as well as page-level modifications of a schema, metadata values, and/or system tables. An as-of query is handled using as-of page(s) from a sparse page file. If the sparse page file does not already contain the responsive page(s), they are created and added to it.

    摘要翻译: 通过使用数据库快照和页面级修改列表的撤销,在保留期内的任何挂钟时间查询数据库。 快照是用户标识,自动生成或从备份中提取的。 该列表通过在重新使用页面之前持久页面内容来维护事务日志,在删除的行移动之前保留已删除的行,持久化补偿日志记录撤消信息和/或记录完整页面。 要倒退整个数据库,undo以反向LSN顺序扫描事务日志,并撤消所有页面修改。 撤消反转重新分配的页面,表截断和/或表删除,以及模式,元数据值和/或系统表的页面级修改。 使用从稀疏页面文件中的页面处理一个查询。 如果稀疏页面文件尚未包含响应页面,则会创建它们并将其添加到其中。

    Serialization of file system item(s) and associated entity(ies)
    2.
    发明授权
    Serialization of file system item(s) and associated entity(ies) 有权
    文件系统项目和关联实体的序列化

    公开(公告)号:US07676481B2

    公开(公告)日:2010-03-09

    申请号:US11121284

    申请日:2005-05-03

    IPC分类号: G06F17/00 G06F17/30

    摘要: A system and method for serialization and/or de-serialization of file system item(s) and associated entity(ies)is provided. A file system “item” comprises a core class which can include property(ies). Through serialization, a consistent copy of the item and associated entity(ies), such as fragment(s), link(s) with other item(s) and/or extension(s),if any, can be captured. The serialization system includes an identification component that identities entity(ies) associated with an item and a serialization component that serializes the item and associated entity(ies). The serialization component can further serialize a header that includes information associated with the item and associated entity(ies). The header can facilitate random access to the item and associated entity(ies). The serialization system can expose application program interface(s) (API's) that facilitate the copying, moving and/or transfer of an item and its associated entity(ies) from one location to another location.

    摘要翻译: 提供了一种用于文件系统项目和关联实体的序列化和/或解串行化的系统和方法。 文件系统“项目”包括可以包括属性的核心类。 通过序列化,可以捕获项目和关联实体(例如片段,与其他项目和/或扩展)的链接(如果有的话)的一致副本。 序列化系统包括识别组件,其与项目相关联的身份实体和串行化项目和关联实体的序列化组件。 序列化组件可以进一步序列化包括与项目和关联实体相关联的信息的报头。 标题可以促进对项目和关联实体的随机访问。 序列化系统可以公开应用程序接口(API),其便于将项目及其相关联的实体从一个位置复制,移动和/或传送到另一个位置。

    Managing database recovery time
    4.
    发明授权
    Managing database recovery time 有权
    管理数据库恢复时间

    公开(公告)号:US08370310B2

    公开(公告)日:2013-02-05

    申请号:US13041091

    申请日:2011-03-04

    IPC分类号: G06F15/16 G06F17/20

    摘要: Managing database recovery time. A method includes receiving user input specifying a target recovery time for a database. The method further includes determining an amount of time to read a data page of the database from persistent storage. The method further includes determining an amount of time to process a log record of the database to apply changes specified in the log record to a data page. The method further includes determining a number of dirty pages that presently would be read in recovery if a database failure occurred. The method further includes determining a number of log records that would be processed in recovery if a database failure occurred. The method further includes adjusting at least one of the number of dirty pages that presently would be read in recovery or the number of log records that would be processed in recovery to meet the specified target recovery time.

    摘要翻译: 管理数据库恢复时间。 一种方法包括接收指定数据库的目标恢复时间的用户输入。 该方法还包括确定从持久存储器读取数据库的数据页面的时间量。 该方法还包括确定处理数据库的日志记录的时间量以将在日志记录中指定的改变应用于数据页。 该方法还包括确定在发生数据库故障时当前将在恢复中读取的脏页数。 该方法还包括确定在发生数据库故障时将在恢复中处理的日志记录的数量。 该方法还包括调整目前将在恢复中读取的脏页数的数目或将在恢复中处理以满足指定的目标恢复时间的日志记录的数目中的至少一个。

    MANAGING DATABASE RECOVERY TIME
    5.
    发明申请
    MANAGING DATABASE RECOVERY TIME 有权
    管理数据库恢复时间

    公开(公告)号:US20120226668A1

    公开(公告)日:2012-09-06

    申请号:US13041091

    申请日:2011-03-04

    IPC分类号: G06F17/30

    摘要: Managing database recovery time. A method includes receiving user input specifying a target recovery time for a database. The method further includes determining an amount of time to read a data page of the database from persistent storage. The method further includes determining an amount of time to process a log record of the database to apply changes specified in the log record to a data page. The method further includes determining a number of dirty pages that presently would be read in recovery if a database failure occurred. The method further includes determining a number of log records that would be processed in recovery if a database failure occurred. The method further includes adjusting at least one of the number of dirty pages that presently would be read in recovery or the number of log records that would be processed in recovery to meet the specified target recovery time.

    摘要翻译: 管理数据库恢复时间。 一种方法包括接收指定数据库的目标恢复时间的用户输入。 该方法还包括确定从持久存储器读取数据库的数据页面的时间量。 该方法还包括确定处理数据库的日志记录的时间量以将在日志记录中指定的改变应用于数据页。 该方法还包括确定在发生数据库故障时当前将在恢复中读取的脏页数。 该方法还包括确定在发生数据库故障时将在恢复中处理的日志记录的数量。 该方法还包括调整目前将在恢复中读取的脏页数的数目或将在恢复中处理以满足指定的目标恢复时间的日志记录的数目中的至少一个。

    Tracking redo completion at a page level
    6.
    发明授权
    Tracking redo completion at a page level 有权
    在页面级跟踪重做完成

    公开(公告)号:US08818960B2

    公开(公告)日:2014-08-26

    申请号:US13051970

    申请日:2011-03-18

    IPC分类号: G06F7/00

    摘要: Embodiments are directed to implementing a transitional redo phase to allow pre-redo phase data access and to determining which data pages including unprocessed transactions are to be processed during a transitional redo phase. In an embodiment, a computer system initiates an analysis phase of a database recovery that scans a database transaction log and builds a dirty page table that includes pages corresponding to unprocessed data transactions. The computer system determines from the dirty page table which pages are to be processed during the transitional redo phase, before the final redo phase. The computer system processes the determined pages during the transitional redo phase, before the final redo phase is reached and, upon completion of the system transaction undo phase, makes available those pages that were processed during the transitional redo phase, as well as those database pages that are not scheduled for processing during the final redo phase.

    摘要翻译: 实施例涉及实现过渡重做阶段,以允许重做前相位数据访问,并确定在过渡重做阶段期间处理包括未处理事务的数据页面。 在一个实施例中,计算机系统启动扫描数据库事务日志的数据库恢复的分析阶段,并构建包含与未处理的数据事务相对应的页面的脏页表。 计算机系统从脏页表确定在过渡重做阶段期间在最后重做阶段之前要处理的页面。 计算机系统在过渡重做阶段期间处理确定的页面,在达到最后的重做阶段之前,并且在完成系统事务撤销阶段后,使得在过渡重做阶段期间处理的那些页面以及那些数据库页面 这些计划在最后重做阶段没有计划进行处理。

    Consistent Database Recovery Across Constituent Segments
    7.
    发明申请
    Consistent Database Recovery Across Constituent Segments 有权
    跨组成部分的数据库恢复一致

    公开(公告)号:US20130151494A1

    公开(公告)日:2013-06-13

    申请号:US13315363

    申请日:2011-12-09

    IPC分类号: G06F17/30

    CPC分类号: G06F11/1471 G06F17/30289

    摘要: A distributed database transaction coordination manager's outcome store may be unavailable to resolve in-doubt transactions locally, e.g., after an unclean detach, during an outcomes store restore, or during a logical database restore. To facilitate transactional consistency, AGEs and values based on them are used. Some code avoids reformatting any closed physical portion for reuse based on the segment's most recently received minimum of persisted AGEs. Some code commits any in-doubt transactions that appear on an aggregate list and aborts any not on the aggregate list. Some code writes each segment's transaction commit records to persistent storage until the segment's persisted-AGE is not less than a common-restore-AGE, and some code resolves any in-doubt transactions based on a harvested outcomes list. Outcomes may reside in a log or a persisted transactions table. A restore checkpoint may include harvested outcomes. Segments may reside on cloud nodes and/or in a shared nothing database system.

    摘要翻译: 分布式数据库事务协调管理器的结果存储可能不可用于在结果存储恢复期间或在逻辑数据库恢复期间在本地例如在不清洁的分离之后解决无疑的事务。 为了促进事务一致性,使用AGEs和基于它们的值。 一些代码避免重新格式化任何封闭的物理部分,以便根据片段最近接收的持久AGE的最小值进行重新使用。 一些代码提交出现在聚合列表上的任何无疑的事务,并且中止不在聚合列表上的任何事务。 一些代码将每个段的事务提交记录写入永久存储,直到段的持久AGE不小于common-restore-AGE,并且一些代码基于收获的结果列表来解决任何无疑的事务。 成果可能驻留在日志或持久化事务表中。 恢复检查点可能包括收获结果。 分段可能驻留在云节点和/或共享无数据库系统中。

    Database point-in-time restore and as-of query
    9.
    发明授权
    Database point-in-time restore and as-of query 有权
    数据库时间点恢复和查询

    公开(公告)号:US08527462B1

    公开(公告)日:2013-09-03

    申请号:US13370125

    申请日:2012-02-09

    IPC分类号: G06F17/30

    CPC分类号: G06F17/30144 G06F17/30088

    摘要: A database is queried as of any wall-clock time within a retention period, via undo that uses database snapshots and a list of page level modifications. The snapshot is user-identified, automatically generated, or extracted from a backup. The list is maintained in a transaction log by persisting page content before a page is re-used, persisting deleted rows before they are moved, persisting compensation log record undo information, and/or logging a full page. To rewind an entire database, the undo scans the transaction log in reverse LSN order and undoes all page modifications. Undo reverses reallocated pages, table truncation, and/or table deletion, as well as page-level modifications of a schema, metadata values, and/or system tables. An as-of query is handled using as-of page(s) from a sparse page file. If the sparse page file does not already contain the responsive page(s), they are created and added to it.

    摘要翻译: 通过使用数据库快照和页面级修改列表的撤销,在保留期内的任何挂钟时间查询数据库。 快照是用户标识,自动生成或从备份中提取的。 该列表通过在重新使用页面之前持久页面内容来维护事务日志,在删除的行移动之前保留已删除的行,持久化补偿日志记录撤销信息和/或记录完整页面。 要倒退整个数据库,undo以反向LSN顺序扫描事务日志,并撤消所有页面修改。 撤消反转重新分配的页面,表截断和/或表删除,以及模式,元数据值和/或系统表的页面级修改。 使用从稀疏页面文件中的页面处理一个查询。 如果稀疏页面文件尚未包含响应页面,则会创建它们并将其添加到其中。