会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 2. 发明授权
    • Pausable backups of file system items
    • 文件系统项目的可靠备份
    • US07590668B2
    • 2009-09-15
    • US11106838
    • 2005-04-15
    • Vishal KathuriaMartin J. SleemanRobin Dhananjay DhamankarHanumantha Rao Kodavalla
    • Vishal KathuriaMartin J. SleemanRobin Dhananjay DhamankarHanumantha Rao Kodavalla
    • G06F12/00
    • G06F11/1461G06F2201/84Y10S707/99953
    • The subject invention relates to systems and methods that enable pausing and/or resuming a backup of file system items. The items are backed up in an order based on a unique property associated with each of the items. When the backup is paused, the unique property associated with a last backed up item prior to the pause is stored. Additionally, a timestamp associated with a snapshot from which the backup was taken can be stored with the unique property. Upon being resumed, the backup can continue from the paused location via utilizing the stored unique property. The backup can be resumed either employing an original snapshot associated with a time prior to the pause or a second snapshot related to a subsequent time. The subject invention can perform an initial backup of file system items and/or an incremental backup of such items. Additionally, the subject invention can support backing up a file system at disparate levels of granularity such as, for example, an item level.
    • 本发明涉及能够暂停和/或恢复文件系统项目的备份的系统和方法。 这些项目根据与每个项目相关联的唯一属性的顺序进行备份。 当备份暂停时,存储与暂停之前的最后备份项目相关联的唯一属性。 此外,与备份所采用的快照关联的时间戳可以与唯一属性一起存储。 恢复后,可以通过利用存储的独特属性从暂停的位置继续备份。 可以恢复备份,使用与暂停之前的时间相关联的原始快照或与随后的时间相关的第二快照。 本发明可以执行文件系统项目的初始备份和/或这些项目的增量备份。 另外,本发明可以支持以不同的粒度级别备份文件系统,例如项目级别。
    • 3. 发明授权
    • Serialization of file system item(s) and associated entity(ies)
    • 文件系统项目和关联实体的序列化
    • US07676481B2
    • 2010-03-09
    • US11121284
    • 2005-05-03
    • Vishal KathuriaHanumantha Rao KodavallaMartin J. SleemanRobin Dhananjay Dhamankar
    • Vishal KathuriaHanumantha Rao KodavallaMartin J. SleemanRobin Dhananjay Dhamankar
    • G06F17/00G06F17/30
    • G06F9/4493G06F11/1448Y10S707/99942
    • 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),其便于将项目及其相关联的实体从一个位置复制,移动和/或传送到另一个位置。
    • 6. 发明授权
    • Managing database recovery time
    • 管理数据库恢复时间
    • US08370310B2
    • 2013-02-05
    • US13041091
    • 2011-03-04
    • Robin Dhananjay DhamankarHanumantha Rao Kodavalla
    • Robin Dhananjay DhamankarHanumantha Rao Kodavalla
    • G06F15/16G06F17/20
    • G06F17/30303G06F11/1471G06F2201/80
    • 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.
    • 管理数据库恢复时间。 一种方法包括接收指定数据库的目标恢复时间的用户输入。 该方法还包括确定从持久存储器读取数据库的数据页面的时间量。 该方法还包括确定处理数据库的日志记录的时间量以将在日志记录中指定的改变应用于数据页。 该方法还包括确定在发生数据库故障时当前将在恢复中读取的脏页数。 该方法还包括确定在发生数据库故障时将在恢复中处理的日志记录的数量。 该方法还包括调整目前将在恢复中读取的脏页数的数目或将在恢复中处理以满足指定的目标恢复时间的日志记录的数目中的至少一个。
    • 7. 发明申请
    • MANAGING DATABASE RECOVERY TIME
    • 管理数据库恢复时间
    • US20120226668A1
    • 2012-09-06
    • US13041091
    • 2011-03-04
    • Robin Dhananjay DhamankarHanumantha Rao Kodavalla
    • Robin Dhananjay DhamankarHanumantha Rao Kodavalla
    • G06F17/30
    • G06F17/30303G06F11/1471G06F2201/80
    • 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.
    • 管理数据库恢复时间。 一种方法包括接收指定数据库的目标恢复时间的用户输入。 该方法还包括确定从持久存储器读取数据库的数据页面的时间量。 该方法还包括确定处理数据库的日志记录的时间量以将在日志记录中指定的改变应用于数据页。 该方法还包括确定在发生数据库故障时当前将在恢复中读取的脏页数。 该方法还包括确定在发生数据库故障时将在恢复中处理的日志记录的数量。 该方法还包括调整目前将在恢复中读取的脏页数的数目或将在恢复中处理以满足指定的目标恢复时间的日志记录的数目中的至少一个。
    • 8. 发明授权
    • Tracking redo completion at a page level
    • 在页面级跟踪重做完成
    • US08818960B2
    • 2014-08-26
    • US13051970
    • 2011-03-18
    • Robin Dhananjay DhamankarHanumantha Rao Kodavalla
    • Robin Dhananjay DhamankarHanumantha Rao Kodavalla
    • G06F7/00
    • G06F11/1469G06F17/30306G06F17/30477
    • 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.
    • 实施例涉及实现过渡重做阶段,以允许重做前相位数据访问,并确定在过渡重做阶段期间处理包括未处理事务的数据页面。 在一个实施例中,计算机系统启动扫描数据库事务日志的数据库恢复的分析阶段,并构建包含与未处理的数据事务相对应的页面的脏页表。 计算机系统从脏页表确定在过渡重做阶段期间在最后重做阶段之前要处理的页面。 计算机系统在过渡重做阶段期间处理确定的页面,在达到最后的重做阶段之前,并且在完成系统事务撤销阶段后,使得在过渡重做阶段期间处理的那些页面以及那些数据库页面 这些计划在最后重做阶段没有计划进行处理。
    • 9. 发明申请
    • TRACKING REDO COMPLETION AT A PAGE LEVEL
    • 在页面级跟踪重做完成
    • US20120239628A1
    • 2012-09-20
    • US13051970
    • 2011-03-18
    • Robin Dhananjay DhamankarHanumantha Rao Kodavalla
    • Robin Dhananjay DhamankarHanumantha Rao Kodavalla
    • G06F7/00
    • G06F11/1469G06F17/30306G06F17/30477
    • 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.
    • 实施例涉及实现过渡重做阶段,以允许重做前相位数据访问,并确定在过渡重做阶段期间处理包括未处理事务的数据页面。 在一个实施例中,计算机系统启动扫描数据库事务日志的数据库恢复的分析阶段,并构建包含与未处理的数据事务相对应的页面的脏页表。 计算机系统从脏页表确定在过渡重做阶段期间在最后重做阶段之前要处理的页面。 计算机系统在过渡重做阶段期间处理确定的页面,在达到最后的重做阶段之前,并且在完成系统事务撤销阶段后,使得在过渡重做阶段期间处理的那些页面以及那些数据库页面 这些计划在最后重做阶段没有计划进行处理。
    • 10. 发明申请
    • 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
    • Tomas TaliusRobin Dhananjay DhamankarHanumantha R. Kodavalla
    • Tomas TaliusRobin Dhananjay DhamankarHanumantha R. Kodavalla
    • G06F7/00
    • G06F17/30144G06F17/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顺序扫描事务日志,并撤消所有页面修改。 撤消反转重新分配的页面,表截断和/或表删除,以及模式,元数据值和/或系统表的页面级修改。 使用从稀疏页面文件中的页面处理一个查询。 如果稀疏页面文件尚未包含响应页面,则会创建它们并将其添加到其中。