WO2005008382A2 - Methods and apparatus for building a complete data protection scheme - Google Patents

Methods and apparatus for building a complete data protection scheme Download PDF

Info

Publication number
WO2005008382A2
WO2005008382A2 PCT/US2004/021519 US2004021519W WO2005008382A2 WO 2005008382 A2 WO2005008382 A2 WO 2005008382A2 US 2004021519 W US2004021519 W US 2004021519W WO 2005008382 A2 WO2005008382 A2 WO 2005008382A2
Authority
WO
WIPO (PCT)
Prior art keywords
policy
data
data protection
replication
user interface
Prior art date
Application number
PCT/US2004/021519
Other languages
French (fr)
Other versions
WO2005008382A3 (en
Inventor
Stephen H. Zalewski
Aida Mcarthur
Original Assignee
Softek Storage Solutions Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Softek Storage Solutions Corporation filed Critical Softek Storage Solutions Corporation
Priority to JP2006518828A priority Critical patent/JP4582485B2/en
Publication of WO2005008382A2 publication Critical patent/WO2005008382A2/en
Publication of WO2005008382A3 publication Critical patent/WO2005008382A3/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/1435—Saving, restoring, recovering or retrying at system level using file system or storage system metadata
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1461—Backup scheduling policy
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/84—Using snapshots, i.e. a logical point-in-time copy of the data

Definitions

  • the present invention pertains to a method and apparatus for building a complete data protection scheme. More particularly, the present invention pertains to the time instantiation of data protection and replication policies in order to - facilitate data management and recovery.
  • a physical disruption occurs when a data storage medium, such as a disk, physically fails. Examples include when disk crashes occur and other events in which data stored on the data storage medium becomes physically inaccessible.
  • a logical disruption occurs when the data on a data storage medium becomes corrupted, through computer viruses or human error, for example. As a result, the data in the data storage medium is still physically accessible, but some of the data contains errors and other problems.
  • a method and apparatus for building a complete data protection scheme are disclosed.
  • a primary set of data stored in a memory may be protected from physical and logical failures using a replication policy, which may replicate the primary set of data at various points in the data set's history.
  • a graphical user interface may illustrate for a user the logical source volume(s), physical failure policy, logical failure policy, replication occurrence policy, replication technology, scheduling policy and time instantiation of data protection and replication policies to facilitate data management and recovery.
  • Fig. 1 illustrates a diagram of a possible data protection process according to an embodiment of the present invention.
  • FIG. 2 illustrates a flowchart of a possible process for creating an integrated set of data protection and replication policies in order to facilitate data management and recovery.
  • FIG. 3 illustrates a flowchart of a possible process for modifying an integrated set of data protection and replication policies to facilitate data management and recovery according to an embodiment of the present invention.
  • Fig. 4 illustrates a possible GUI capable of time instantiating data protection and replication policies to facilitate data management and recovery according to an embodiment of the present invention.
  • a method and apparatus for building a complete data protection scheme are disclosed.
  • a primary set of data stored in a memory may be protected from physical and logical failures using a replication policy, which may replicate the primary set of data at various points in the data set's history.
  • a graphical user interface may illustrate for a user the time instantiation of data protection and replication policies to facilitate data management and recovery.
  • IT infrastructure
  • logical disruptions that can be solved by a snapshot or a point-in-time (hereinafter, "PIT") copy for instances such as application errors, user errors, and viruses.
  • PIT point-in-time
  • Snapshot technologies provide logical PIT copies of volumes of files. Snapshot-capable volume controllers or file systems configure a new volume but point to the same location as the original. No data is moved and the copy is created within seconds. The PIT copy of the data can then be used as the source of a backup to tape, or maintained as is as a disk backup. Since snapshots do not handle physical disruptions, both snapshots and mirrors play a synergistic role in replication planning. Recognizing that each data loss factor has unique characteristics, this method and apparatus can solve the majority of cases using a general technique, bringing simplicity to storage environments, while increasing data availability and reliability.
  • FIG. 1 illustrates a diagram of one possible embodiment of the data protection system 100.
  • An application server 105 stores a set of source data 110.
  • the server 105 also creates a set of mirror data 115 that matches the set of source data 110.
  • Mirroring is the process of copying data continuously in real time to create a physical copy of the volume.
  • a second set of mirror data 120 is also created from the first set of mirror data 115.
  • a snapshot 125 of the set of mirror data 115 and the source data 110 is taken to record the state of the data at various points in time. Snapshot technologies provide logical PIT copies of the volumes or files containing the set of source data 110. Snapshot-capable volume controllers or file systems configure a new volume but point to the same location as the original source data 110.
  • Fig. 2 illustrates in a flowchart one possible embodiment of a process for creating an integrated set of data protection and replication policies in order to facilitate data management and recovery.
  • the process begins and at step 2010, the storage controller 125 enumerates a source volume 110 by storing a primary set of data in a data storage medium or memory.
  • This memory may include a hard disk drive, a removable disk drive, a tape, an EEPROM, or other memory storage devices.
  • the storage controller 125 determines a physical error policy, for example, one or more mirrors of source data stored locally to protect from any physical damage to the source data, as depicted in Fig. 1.
  • the storage controller 125 determines a logical error policy, for example, any number of PIT replications of source data stored in a variety of memory storage mediums, each data replication spanning a particular time period.
  • the storage controller 125 assigns a replication technology, by using default parameters or setting specific parameters, for example.
  • the storage controller 125 leverages traditional scheduling methodology to specify scheduling parameters such as frequency, execution range, and specific time.
  • the storage controller 125 monitors and recovers data by executing the replication policy and monitoring the condition of the mirror 115 to determine whether a disruption has occurred. A disruption may be a physical or logical error, for example. If a disruption has not occurred, storage controller 125 again performs step 2060. If a disruption has occurred, control passes to step 2070. In step 2070, a storage controller 125 implements the appropriate error policy to correct the disruption. In step 2080, the process ends.
  • Fig. 3 illustrates in a flowchart one possible embodiment of a process for modifying an integrated set of data protection and replication policies in accordance with user input in order to facilitate data management and recovery.
  • a storage controller 125 enumerates a source volume 110 by storing a primary set of data in a data storage medium or memory.
  • this memory may include a hard disk drive, a removable disk drive, a tape, an EEPROM, or other memory storage devices.
  • the storage controller 125 displays a graphical user interface.
  • the storage controller 125 determines whether any input has been received from the user modifying a policy.
  • the policies to be modified may include a physical error policy, a logical error policy, a scheduling policy, or any other type of data protection or data replication policy.
  • the user may modify a policy by means of an input device such as a mouse, keyboard, pointing device, touch screen, stylus, joystick, game pad, track ball, light pen, microphone, or speech recognition device. If the user does not provide such input, the storage controller 125 repeats the determination at step 3030. If the user does provide input to modify a policy, the storage controller 125 proceeds to step 3040, wherein the storage controller 125 modifies the policy in accordance with user input. In step 3050, the process ends. [0019] Fig.
  • a block represents each replication of the primary set of data.
  • Block 410 represents a partial or complete replication of the primary set of data with respect to a particular data set 420.
  • the number of blocks for a particular data set may be changed, causing more or less replications to occur over a given time period.
  • the type of blocks may also be changed to indicate the type of replication to be performed, be it a full copy or only a partial set of the data.
  • Source 430 is protected from disruption by primary mirror 440 and secondary mirror 450. Drop-down menus, cursor activated fields, lookup boxes, and other interfaces known in the art may be added to allow the user to control performance of the protection process. Other constraints may be placed on the complete data protection scheme as required by the user.
  • the method of this invention may be implemented using a programmed processor.
  • the method can also be implemented on a general-purpose or a special purpose computer, a programmed microprocessor or microcontroller, peripheral integrated circuit elements, an application-specific integrated circuit (ASIC) or other integrated circuits, hardware/electronic logic circuits, such as a discrete element circuit, a programmable logic device, such as a PLD, PLA, FPGA, or PAL, or the like.
  • ASIC application-specific integrated circuit

Abstract

A method and apparatus for building a complete data protection scheme. A primary set of data may be protected from physical and logical failures using a replication policy, which may replicate the primary set of data at various points in the data set’s history. A graphical user interface may illustrate for a user the logical source volume(s), physical failure policy, logical failure policy, replication occurrence policy, replication technology, scheduling policy and time instantiation of data protection and replication policies to facilitate data management and recovery.

Description

METHOD AND APPARATUS FOR BUILDING A COMPLETE DATA PROTECTION SCHEME
CROSS REFERENCETO RELATEDAPPLICATIONS
[0001] This application is related by common inventorship and subject matter to co-filed and co-pending applications Serial No. 10/616,131 filed 8 July 2003 titled "Methods and Apparatus for Determining Replication Schema Against Logical Data Disruptions", Serial No. 10/616,079 filed 8 July 2003 titled "Method and Apparatus for Protecting Data Against any Category of Disruptions" and Serial No. 10/617,203 filed 8 July 2003 titled "Method and Apparatus for Creating a Storage Pool by Dynamically Mapping Replication Schema to Provisioned Storage Volumes". Each of the aforementioned applications is incorporated herein by reference in its entirety.
TECHNICAL FIELD OF THE INVENTION
[0002] The present invention pertains to a method and apparatus for building a complete data protection scheme. More particularly, the present invention pertains to the time instantiation of data protection and replication policies in order to - facilitate data management and recovery.
BACKGROUND INFORMATION
[0003] There are many methods of backing up a set of data to protect against disruptions. As is known in the art, the traditional backup strategy has three different phases - synchronization, physical backup, and resynchronization. The data being stored needs to be protected against both physical and logical disruptions. A physical disruption occurs when a data storage medium, such as a disk, physically fails. Examples include when disk crashes occur and other events in which data stored on the data storage medium becomes physically inaccessible. A logical disruption occurs when the data on a data storage medium becomes corrupted, through computer viruses or human error, for example. As a result, the data in the data storage medium is still physically accessible, but some of the data contains errors and other problems. [0004] While conventional data methods exist to protect and recover data, they are difficult and cumbersome to use.
SUMMARY OF THE INVENTION
[0005] A method and apparatus for building a complete data protection scheme are disclosed. A primary set of data stored in a memory may be protected from physical and logical failures using a replication policy, which may replicate the primary set of data at various points in the data set's history. A graphical user interface may illustrate for a user the logical source volume(s), physical failure policy, logical failure policy, replication occurrence policy, replication technology, scheduling policy and time instantiation of data protection and replication policies to facilitate data management and recovery.
BRIEF DESCRIPTION OF THE DRAWINGS
[0006] The invention is described in detail with reference to the following drawings wherein like numerals reference like elements, and wherein: [0007] Fig. 1 illustrates a diagram of a possible data protection process according to an embodiment of the present invention.
[0008] Fig. 2 illustrates a flowchart of a possible process for creating an integrated set of data protection and replication policies in order to facilitate data management and recovery.
[0009] Fig. 3 illustrates a flowchart of a possible process for modifying an integrated set of data protection and replication policies to facilitate data management and recovery according to an embodiment of the present invention. [0010] Fig. 4 illustrates a possible GUI capable of time instantiating data protection and replication policies to facilitate data management and recovery according to an embodiment of the present invention.
DETAILED DESCRIPTION OF THE DRAWINGS
[0011] A method and apparatus for building a complete data protection scheme are disclosed. A primary set of data stored in a memory may be protected from physical and logical failures using a replication policy, which may replicate the primary set of data at various points in the data set's history. A graphical user interface may illustrate for a user the time instantiation of data protection and replication policies to facilitate data management and recovery. [0012] In order to recover data, an information technology (hereinafter,
"IT") department must not only protect data from hardware failure, but also from human errors and such. Overall, the disruptions can be classified into two broad categories: "physical" disruptions, that can be solved by mirrors to address hardware failures; and "logical" disruptions that can be solved by a snapshot or a point-in-time (hereinafter, "PIT") copy for instances such as application errors, user errors, and viruses. This classification focuses on the particular type of disruptions in relation to the particular type of replication technologies to be used. The classification also acknowledges the fundamental difference between the dynamic and static nature of mirrors and PIT copies. Although physical and logical disruptions have to be managed differently, the invention described herein manages both disruption types as part of a single solution.
[0013] Strategies for resolving the effects of physical disruptions call for following established industry practices, such as setting up several layers of mirrors and the use of failover system technologies. Mirroring is the process of copying data continuously in real time to create a physical copy of the volume. Mirrors contribute as a main tool for physical replication planning, but they are ineffective for resolving logical disruptions.
[0014] Strategies for handling logical disruptions include using snapshot techniques to generate periodic PIT replications to assist in rolling back to previous stable states. Snapshot technologies provide logical PIT copies of volumes of files. Snapshot-capable volume controllers or file systems configure a new volume but point to the same location as the original. No data is moved and the copy is created within seconds. The PIT copy of the data can then be used as the source of a backup to tape, or maintained as is as a disk backup. Since snapshots do not handle physical disruptions, both snapshots and mirrors play a synergistic role in replication planning. Recognizing that each data loss factor has unique characteristics, this method and apparatus can solve the majority of cases using a general technique, bringing simplicity to storage environments, while increasing data availability and reliability. More importantly, physical and logical disruptions are treated equally as part of a complete data protection plan. [0015] This technique offers a high degree of confidence in the ability to restore the data. It results in very appropriate strategies for physical and logical failures, and a very cost-effective use of storage. In addition, this approach supports much more flexibility in evaluating the scope of storage replication technologies that are available and appropriate for the specific application server. [0016] Fig. 1 illustrates a diagram of one possible embodiment of the data protection system 100. An application server 105 stores a set of source data 110. The server 105 also creates a set of mirror data 115 that matches the set of source data 110. Mirroring is the process of copying data continuously in real time to create a physical copy of the volume. Mirroring often does not end unless specifically stopped. A second set of mirror data 120 is also created from the first set of mirror data 115. A snapshot 125 of the set of mirror data 115 and the source data 110 is taken to record the state of the data at various points in time. Snapshot technologies provide logical PIT copies of the volumes or files containing the set of source data 110. Snapshot-capable volume controllers or file systems configure a new volume but point to the same location as the original source data 110. A storage controller 130, running a recovery application, then recovers any missing data 135.
[0017] Fig. 2 illustrates in a flowchart one possible embodiment of a process for creating an integrated set of data protection and replication policies in order to facilitate data management and recovery. At step 2000, the process begins and at step 2010, the storage controller 125 enumerates a source volume 110 by storing a primary set of data in a data storage medium or memory. This memory may include a hard disk drive, a removable disk drive, a tape, an EEPROM, or other memory storage devices. In step 2020, the storage controller 125 determines a physical error policy, for example, one or more mirrors of source data stored locally to protect from any physical damage to the source data, as depicted in Fig. 1. In step 2030, the storage controller 125 determines a logical error policy, for example, any number of PIT replications of source data stored in a variety of memory storage mediums, each data replication spanning a particular time period. In step 2040, the storage controller 125 assigns a replication technology, by using default parameters or setting specific parameters, for example. In step 2050, the storage controller 125 leverages traditional scheduling methodology to specify scheduling parameters such as frequency, execution range, and specific time. In step 2060, the storage controller 125 monitors and recovers data by executing the replication policy and monitoring the condition of the mirror 115 to determine whether a disruption has occurred. A disruption may be a physical or logical error, for example. If a disruption has not occurred, storage controller 125 again performs step 2060. If a disruption has occurred, control passes to step 2070. In step 2070, a storage controller 125 implements the appropriate error policy to correct the disruption. In step 2080, the process ends.
[0018] Fig. 3 illustrates in a flowchart one possible embodiment of a process for modifying an integrated set of data protection and replication policies in accordance with user input in order to facilitate data management and recovery. At step 3000, the process begins and at step 3010, a storage controller 125 enumerates a source volume 110 by storing a primary set of data in a data storage medium or memory. As discussed above, this memory may include a hard disk drive, a removable disk drive, a tape, an EEPROM, or other memory storage devices. In step 3020, the storage controller 125 displays a graphical user interface. In step 3030, the storage controller 125 determines whether any input has been received from the user modifying a policy. The policies to be modified may include a physical error policy, a logical error policy, a scheduling policy, or any other type of data protection or data replication policy. The user may modify a policy by means of an input device such as a mouse, keyboard, pointing device, touch screen, stylus, joystick, game pad, track ball, light pen, microphone, or speech recognition device. If the user does not provide such input, the storage controller 125 repeats the determination at step 3030. If the user does provide input to modify a policy, the storage controller 125 proceeds to step 3040, wherein the storage controller 125 modifies the policy in accordance with user input. In step 3050, the process ends. [0019] Fig. 4 illustrates one embodiment of a GUI 400 capable of time instantiating data protection and replication policies to facilitate data management and recovery. In this GUI, a block represents each replication of the primary set of data. Block 410 represents a partial or complete replication of the primary set of data with respect to a particular data set 420. The number of blocks for a particular data set may be changed, causing more or less replications to occur over a given time period. The type of blocks may also be changed to indicate the type of replication to be performed, be it a full copy or only a partial set of the data. Source 430 is protected from disruption by primary mirror 440 and secondary mirror 450. Drop-down menus, cursor activated fields, lookup boxes, and other interfaces known in the art may be added to allow the user to control performance of the protection process. Other constraints may be placed on the complete data protection scheme as required by the user.
[0020] As shown in Fig. 1, the method of this invention may be implemented using a programmed processor. However, the method can also be implemented on a general-purpose or a special purpose computer, a programmed microprocessor or microcontroller, peripheral integrated circuit elements, an application-specific integrated circuit (ASIC) or other integrated circuits, hardware/electronic logic circuits, such as a discrete element circuit, a programmable logic device, such as a PLD, PLA, FPGA, or PAL, or the like.
[0021] While the invention has been described with reference to the above embodiments, it is to be understood that these embodiments are purely exemplary in nature. Thus, the invention is not restricted to the particular forms shown in the foregoing embodiments. Various modifications and alterations can be made thereto without departing from the spirit and scope of the invention.

Claims

CLAIMSWhat is claimed is:
1. A method comprising: storing a set of data on a data storage medium; displaying a graphical user interface to a user, wherein the graphical user interface is a graphical representation of a data protection policy and a replication policy; and providing the user with an ability to modify the data protection policy and the replication policy through the graphical user interface.
2. The method of claim 1, further comprising modifying the data protection policy based on input received from the user through the graphical user interface.
3. The method of claim 1 , further comprising modifying the replication policy based on input received from the user through the graphical user interface.
4. The method of claim 1, wherein the graphical user interface displays a logical source volume.
5. The method of claim 1, wherein the data protection policy is a physical failure policy.
6. The method of claim 1, wherein the data protection policy is a logical failure policy.
7. The method of claim 1, wherein the replication policy is a scheduling policy.
8. set of instructions residing in a storage medium, the set of instructions capable of being executed by a controller to implement a method for processing data, the method comprising: storing a set of data on a data storage medium; displaying a graphical user interface to a user, wherein the graphical user interface is a graphical representation of a data protection policy and a replication policy; and providing the user with an ability to modify the data protection policy and the replication policy through the graphical user interface.
9. The set of instructions of claim 8, wherein the method further comprises modifying the data protection policy based on input received from the user through the graphical user interface.
10. The set of instructions of claim 8, wherein the method further comprises modifying the replication policy based on input received from the user through the graphical user interface.
11. The set of instructions of claim 8, wherein the graphical user interface displays a logical source volume.
12. The set of instructions of claim 8, wherein the data protection policy is a physical failure policy.
13. The set of instructions of claim 8, wherein the data protection policy is a logical failure policy.
14. The set of instructions of claim 8, wherein the replication policy is a scheduling policy.
15. A processing system comprising: a memory that stores a set of data; a controller that enacts a data protection policy and a replication policy to protect the set of data against disruptions; a display that shows to a user a graphical user interface providing a graphical representation of the data protection policy and the replication policy; and an input device that provides the user with the ability to modify the data protection policy and the replication policy through the graphical user interface.
16. The processing system of claim 15, wherein the graphical user interface displays a logical source volume.
17. The processing system of claim 15, wherein the data protection policy is a physical failure policy.
18. The processing system of claim 15, wherein the data protection policy is a logical failure policy.
19. The processing system of claim 15, wherein the replication policy is a scheduling policy.
20. The processing system of claim 15, wherein the input device includes at least one of a mouse, keyboard, pointing device, touch screen, stylus, joystick, game pad, track ball, light pen, microphone, and speech recognition device.
PCT/US2004/021519 2003-07-08 2004-07-01 Methods and apparatus for building a complete data protection scheme WO2005008382A2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2006518828A JP4582485B2 (en) 2003-07-08 2004-07-01 Method and apparatus for building a complete data protection scheme

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/616,819 US20050010529A1 (en) 2003-07-08 2003-07-08 Method and apparatus for building a complete data protection scheme
US10/616,819 2003-07-08

Publications (2)

Publication Number Publication Date
WO2005008382A2 true WO2005008382A2 (en) 2005-01-27
WO2005008382A3 WO2005008382A3 (en) 2005-04-14

Family

ID=33564850

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2004/021519 WO2005008382A2 (en) 2003-07-08 2004-07-01 Methods and apparatus for building a complete data protection scheme

Country Status (3)

Country Link
US (1) US20050010529A1 (en)
JP (1) JP4582485B2 (en)
WO (1) WO2005008382A2 (en)

Families Citing this family (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7454529B2 (en) * 2002-08-02 2008-11-18 Netapp, Inc. Protectable data storage system and a method of protecting and/or managing a data storage system
US7437387B2 (en) * 2002-08-30 2008-10-14 Netapp, Inc. Method and system for providing a file system overlay
US7882081B2 (en) * 2002-08-30 2011-02-01 Netapp, Inc. Optimized disk repository for the storage and retrieval of mostly sequential data
US7567993B2 (en) * 2002-12-09 2009-07-28 Netapp, Inc. Method and system for creating and using removable disk based copies of backup data
US8024172B2 (en) * 2002-12-09 2011-09-20 Netapp, Inc. Method and system for emulating tape libraries
US6973369B2 (en) * 2003-03-12 2005-12-06 Alacritus, Inc. System and method for virtual vaulting
US7437492B2 (en) * 2003-05-14 2008-10-14 Netapp, Inc Method and system for data compression and compression estimation in a virtual tape library environment
US7032126B2 (en) * 2003-07-08 2006-04-18 Softek Storage Solutions Corporation Method and apparatus for creating a storage pool by dynamically mapping replication schema to provisioned storage volumes
US7315965B2 (en) * 2004-02-04 2008-01-01 Network Appliance, Inc. Method and system for storing data using a continuous data protection system
US7325159B2 (en) * 2004-02-04 2008-01-29 Network Appliance, Inc. Method and system for data recovery in a continuous data protection system
US7904679B2 (en) * 2004-02-04 2011-03-08 Netapp, Inc. Method and apparatus for managing backup data
US7720817B2 (en) * 2004-02-04 2010-05-18 Netapp, Inc. Method and system for browsing objects on a protected volume in a continuous data protection system
US20050182910A1 (en) * 2004-02-04 2005-08-18 Alacritus, Inc. Method and system for adding redundancy to a continuous data protection system
US7783606B2 (en) * 2004-02-04 2010-08-24 Netapp, Inc. Method and system for remote data recovery
US7559088B2 (en) * 2004-02-04 2009-07-07 Netapp, Inc. Method and apparatus for deleting data upon expiration
US7406488B2 (en) * 2004-02-04 2008-07-29 Netapp Method and system for maintaining data in a continuous data protection system
US7426617B2 (en) 2004-02-04 2008-09-16 Network Appliance, Inc. Method and system for synchronizing volumes in a continuous data protection system
US7490103B2 (en) * 2004-02-04 2009-02-10 Netapp, Inc. Method and system for backing up data
US7325019B2 (en) * 2004-03-12 2008-01-29 Network Appliance, Inc. Managing data replication policies
US7395352B1 (en) * 2004-03-12 2008-07-01 Netapp, Inc. Managing data replication relationships
US8028135B1 (en) 2004-09-01 2011-09-27 Netapp, Inc. Method and apparatus for maintaining compliant storage
US7689767B2 (en) * 2004-09-30 2010-03-30 Symantec Operating Corporation Method to detect and suggest corrective actions when performance and availability rules are violated in an environment deploying virtualization at multiple levels
US7774610B2 (en) * 2004-12-14 2010-08-10 Netapp, Inc. Method and apparatus for verifiably migrating WORM data
US7581118B2 (en) * 2004-12-14 2009-08-25 Netapp, Inc. Disk sanitization using encryption
US7401198B2 (en) * 2005-10-06 2008-07-15 Netapp Maximizing storage system throughput by measuring system performance metrics
US7592264B2 (en) * 2005-11-23 2009-09-22 Fsi International, Inc. Process for removing material from substrates
US7752401B2 (en) 2006-01-25 2010-07-06 Netapp, Inc. Method and apparatus to automatically commit files to WORM status
US7650533B1 (en) 2006-04-20 2010-01-19 Netapp, Inc. Method and system for performing a restoration in a continuous data protection system
US7613750B2 (en) * 2006-05-29 2009-11-03 Microsoft Corporation Creating frequent application-consistent backups efficiently
US7899850B2 (en) * 2008-02-22 2011-03-01 Bycast, Inc. Relational objects for the optimized management of fixed-content storage systems
US8898267B2 (en) * 2009-01-19 2014-11-25 Netapp, Inc. Modifying information lifecycle management rules in a distributed system
US8793223B1 (en) * 2009-02-09 2014-07-29 Netapp, Inc. Online data consistency checking in a network storage system with optional committal of remedial changes
US8261033B1 (en) 2009-06-04 2012-09-04 Bycast Inc. Time optimized secure traceable migration of massive quantities of data in a distributed storage system
US10089148B1 (en) * 2011-06-30 2018-10-02 EMC IP Holding Company LLC Method and apparatus for policy-based replication
US9736007B1 (en) * 2011-12-29 2017-08-15 EMC IP Holding Company LLC Method and apparatus for automated data protection with IT infrastructure visibility
US9355120B1 (en) 2012-03-02 2016-05-31 Netapp, Inc. Systems and methods for managing files in a content storage system

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040039594A1 (en) * 2002-01-09 2004-02-26 Innerpresence Networks, Inc. Systems and methods for dynamically generating licenses in a rights management system
US20040088382A1 (en) * 2002-09-10 2004-05-06 Therrien David G. Method and apparatus for server share migration and server recovery using hierarchical storage management
US20040117407A1 (en) * 2002-12-16 2004-06-17 Manoj Kumar Resource and data administration technologies for IT non-experts

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6466980B1 (en) * 1999-06-17 2002-10-15 International Business Machines Corporation System and method for capacity shaping in an internet environment
JP2002140239A (en) * 2000-08-17 2002-05-17 Masahiro Mizuno Information management system, information management method and system controller
JP3653002B2 (en) * 2001-04-17 2005-05-25 三菱電機株式会社 How to distribute and set policy definitions

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040039594A1 (en) * 2002-01-09 2004-02-26 Innerpresence Networks, Inc. Systems and methods for dynamically generating licenses in a rights management system
US20040088382A1 (en) * 2002-09-10 2004-05-06 Therrien David G. Method and apparatus for server share migration and server recovery using hierarchical storage management
US20040117407A1 (en) * 2002-12-16 2004-06-17 Manoj Kumar Resource and data administration technologies for IT non-experts

Also Published As

Publication number Publication date
WO2005008382A3 (en) 2005-04-14
JP4582485B2 (en) 2010-11-17
JP2007527568A (en) 2007-09-27
US20050010529A1 (en) 2005-01-13

Similar Documents

Publication Publication Date Title
US20050010529A1 (en) Method and apparatus for building a complete data protection scheme
US7032126B2 (en) Method and apparatus for creating a storage pool by dynamically mapping replication schema to provisioned storage volumes
US20050010588A1 (en) Method and apparatus for determining replication schema against logical data disruptions
US7181646B2 (en) Mapping apparatus for backup and restoration of multi-generation recovered snapshots
US7302540B1 (en) Virtual tape storage system having snapshot virtual tape library for disaster recovery testing
US9208038B2 (en) Detection of logical corruption in persistent storage and automatic recovery therefrom
US8046547B1 (en) Storage system snapshots for continuous file protection
US9009527B2 (en) Recovering a volume table and data sets from a corrupted volume
JP4827564B2 (en) How to display the copy pair status
EP1594070A2 (en) Consistency checking for a database management system
EP2425344B1 (en) Method and system for system recovery using change tracking
GB2367656A (en) Self-repairing operating system for computer entities
CN104520820A (en) Function evaluation using lightweight process snapshots
US9128627B1 (en) Method and system for virtual machine backup
US7222143B2 (en) Safely restoring previously un-backed up data during system restore of a failing system
US20050010731A1 (en) Method and apparatus for protecting data against any category of disruptions
US10613923B2 (en) Recovering log-structured filesystems from physical replicas
US9734022B1 (en) Identifying virtual machines and errors for snapshots
KR101600694B1 (en) Tape backup data verifying method
US9524217B1 (en) Federated restores of availability groups
JP2002312212A (en) File system
JPH08185347A (en) Method for retracting/restoring file
JPS62106538A (en) Control system for allocation of using area of auxiliary memory device

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2006518828

Country of ref document: JP

122 Ep: pct application non-entry in european phase