公开(公告)号：WO2007139647A1

公开(公告)日：2007-12-06

申请号：PCT/US2007/010304

申请日：2007-04-26

Applicant: MICROSOFT CORPORATION

Inventor： VALIYAPARAMBIL, Manoj K. ,  SAHASRANAMAN, Vivek ,  BADAMI, Vinay S. ,  ALI, Abid ,  SINGLA, Amit ,  ANAND, Karandeep Singh ,  FRIES, Robert M.

IPC: G06F12/16 ,  G06F15/16

CPC classification number: G06F11/1464 ,  G06F11/1451 ,  G06F11/1458 ,  G06F11/1469 ,  G06F11/1471 ,  G06F2201/84 ,  Y10S707/99955

Abstract: Data can be protected at a production server in a virtually continuous fashion, without necessarily imposing severe constraints on the source application(s). For example, a production server can create an application-consistent backup of one or more volumes, the backups corresponding to a first instance in time. A volume filter driver can monitor data changes using an in-memory bitmap, while a log file and/or update sequence number journal can keep track of which files have been modified. The volume updates are also consistent for an instance (later) in time. At the next replication cycle, such as every few minutes (however configured), the volume filter driver passes each in-memory bitmap to the physical disk on the production server. The production server then sends the updates to the backup server, which thus stores application-consistent backups for the volume for multiple instances of time.

Abstract translation: 可以在生产服务器上以几乎连续的方式保护数据，而不必对源应用程序施加严格的约束。 例如，生产服务器可以创建一个或多个卷的应用程序一致性备份，备份与时间对应的第一个实例。 卷过滤器驱动程序可以使用内存中位图来监视数据更改，而日志文件和/或更新序列号日志可以跟踪哪些文件已被修改。 对于一个实例（稍后）的时间，卷更新也是一致的。 在下一个复制周期（例如每隔几分钟配置一次），卷过滤器驱动程序将每个内存中的位图传递到生产服务器上的物理磁盘。 然后，生产服务器将更新发送到备份服务器，从而存储多个时间实例的卷的应用程序一致性备份。

公开(公告)号：EP2033100B1

公开(公告)日：2013-05-29

申请号：EP07776394.4

申请日：2007-04-26

Applicant: Microsoft Corporation

Inventor： VALIYAPARAMBIL, Manoj K. ,  SAHASRANAMAN, Vivek ,  BADAMI, Vinay S. ,  ALI, Abid ,  SINGLA, Amit ,  ANAND, Karandeep Singh ,  FRIES, Robert M.

IPC: G06F11/14

CPC classification number: G06F11/1464 ,  G06F11/1451 ,  G06F11/1458 ,  G06F11/1469 ,  G06F11/1471 ,  G06F2201/84 ,  Y10S707/99955

Abstract: Data can be protected at a production server in a virtually continuous fashion, without necessarily imposing severe constraints on the source application(s). For example, a production server can create an application-consistent backup of one or more volumes, the backups corresponding to a first instance in time. A volume filter driver can monitor data changes in each volume using an in-memory bitmap, while a log file and/or update sequence number journal can keep track of which files have been added to or updated. The volume updates are also consistent for an instance (later) in time. At the next replication cycle, such as every few minutes (however configured), the volume filter driver passes each in-memory bitmap to the physical disk on the production server. The production server then sends the updates to the backup server, which thus stores application-consistent backups for the volume for multiple instances of time.

公开(公告)号：EP2033100A1

公开(公告)日：2009-03-11

申请号：EP07776394.4

申请日：2007-04-26

Applicant: Microsoft Corporation

Inventor： VALIYAPARAMBIL, Manoj K. ,  SAHASRANAMAN, Vivek ,  BADAMI, Vinay S. ,  ALI, Abid ,  SINGLA, Amit ,  ANAND, Karandeep Singh ,  FRIES, Robert M.

IPC: G06F12/16 ,  G06F15/16

CPC classification number: G06F11/1464 ,  G06F11/1451 ,  G06F11/1458 ,  G06F11/1469 ,  G06F11/1471 ,  G06F2201/84 ,  Y10S707/99955

Abstract: Data can be protected at a production server in a virtually continuous fashion, without necessarily imposing severe constraints on the source application(s). For example, a production server can create an application-consistent backup of one or more volumes, the backups corresponding to a first instance in time. A volume filter driver can monitor data changes using an in-memory bitmap, while a log file and/or update sequence number journal can keep track of which files have been modified. The volume updates are also consistent for an instance (later) in time. At the next replication cycle, such as every few minutes (however configured), the volume filter driver passes each in-memory bitmap to the physical disk on the production server. The production server then sends the updates to the backup server, which thus stores application-consistent backups for the volume for multiple instances of time.