WO2017132790A1 - 数据恢复方法及存储设备 - Google Patents

数据恢复方法及存储设备 Download PDF

Info

Publication number
WO2017132790A1
WO2017132790A1 PCT/CN2016/073038 CN2016073038W WO2017132790A1 WO 2017132790 A1 WO2017132790 A1 WO 2017132790A1 CN 2016073038 W CN2016073038 W CN 2016073038W WO 2017132790 A1 WO2017132790 A1 WO 2017132790A1
Authority
WO
WIPO (PCT)
Prior art keywords
snapshot
data block
file
physical address
volume
Prior art date
Application number
PCT/CN2016/073038
Other languages
English (en)
French (fr)
Inventor
伏高顶
江勇
母子安
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201680003255.0A priority Critical patent/CN108351821B/zh
Priority to EP16847617.4A priority patent/EP3223158B1/en
Priority to PCT/CN2016/073038 priority patent/WO2017132790A1/zh
Priority to US15/491,473 priority patent/US20170220427A1/en
Publication of WO2017132790A1 publication Critical patent/WO2017132790A1/zh

Links

Images

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/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/1469—Backup restoration techniques
    • 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/1448—Management of the data involved in backup or backup restore
    • 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/1464—Management of the backup or restore process for networked environments
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/11—File system administration, e.g. details of archiving or snapshots
    • G06F16/128—Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0604—Improving or facilitating administration, e.g. storage management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0638—Organizing or formatting or addressing of data
    • G06F3/064—Management of blocks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
    • G06F3/0659—Command handling arrangements, e.g. command buffers, queues, command scheduling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0683—Plurality of storage devices
    • 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 relates to the field of storage, and in particular, to a data recovery method and a storage device.
  • the role of snapshots is mainly to enable online data backup and recovery.
  • fast data recovery can be performed to restore the data to a snapshot time point.
  • the conventional storage array snapshot technology records the mapping relationship between the original data in the source volume (the LUN being backed up) and the physical address of the original data through a bitmap mapping table, as shown in FIG. 1 .
  • the storage array creates a snapshot volume in another LUN.
  • the snapshot volume includes a bitmap mapping table and a resource volume.
  • the bitmap mapping table is used to record the original data and the original data in the source volume.
  • the storage array when performing a snapshot, records the physical address of the data block No. 0 in the source volume to the data block No. 7 in the bitmap mapping table.
  • the original data d in the source volume is first moved into the resource volume, and then the bitmap mapping table is established.
  • the invention provides a data recovery method and a storage device, which only recovers some files in a source volume.
  • a first aspect of the present invention provides a data recovery method, the recovery method being applied to a storage device, the storage device including a source volume, the source volume including a plurality of data blocks.
  • the server snapshots the source volume at the first snapshot time to obtain a snapshot volume, where the snapshot volume is used to record the first physical address corresponding to each data block included in the source volume at the first snapshot time point. If the data block in the source volume is modified before the second snapshot time point, the modified data block in the source volume is transferred to the resource volume for storage, and in the first snapshot, the modified data block is created.
  • the data recovery method specifically includes:
  • the server needs to obtain the first physical address of the data block included in the file to be restored.
  • the storage device After receiving the first physical address of the data block included in the to-be-recovered file sent by the server, the storage device searches for the recovery snapshot according to the first physical address of the data block included in the to-be-recovered file, and then records according to the recovery snapshot. Obtaining a correspondence between a first physical address of the modified data block and a second physical address of the modified data block in the resource volume, and acquiring a second physical of the modified data block in the to-be-recovered file in the resource volume Address, the recovery snapshot is a snapshot volume used to recover the file to be restored;
  • the storage device restores the to-be-recovered file in the source volume according to the second physical address of the modified data block in the to-be-recovered file in the resource volume.
  • the storing, according to the second physical address of the modified data block in the to-be-recovered file, in the resource volume specifically: the storage device is in the resource according to the modified data block in the to-be-recovered file.
  • the second physical address in the volume finds the modified data block in the resource volume, and then recovers the to-be-recovered file in the source volume by using the modified data block.
  • the specific implementation manner of the first physical address of the data block included in the file to be restored is obtained by the server as follows:
  • the server determines the file to be restored according to the input of the user
  • the server sends the identifier of the file to be restored to the production host to obtain the first physical address of the data block included in the file to be restored in the production host.
  • the method for obtaining the first physical address by the production host after receiving the identifier of the file to be restored sent by the server includes the following:
  • the production host queries the metadata of the file system to which the file to be restored belongs according to the identifier of the file to be restored;
  • the production host queries the first physical address of the data block included in the file to be restored according to the metadata of the file system;
  • the production host sends the first physical address of the data block included in the file to be restored to the server.
  • the server can send the acquired first physical address of the data block included in the to-be-recovered file to the storage device.
  • the specific implementation manner of the first physical address of the data block included in the file to be restored is as follows:
  • the server determines the identity of the standby host and the recovery snapshot identifier according to the input of the user;
  • the server sends the identifier of the standby host and the recovery snapshot to the storage device;
  • the storage device receives the identifier and recovery snapshot of the standby host sent by the server, and restores the The complex snapshot is mapped to the alternate host;
  • the server mounts the file system on the recovery snapshot to the standby host, and obtains a file list of the backup file on the recovery snapshot through the standby host;
  • the server determines the file to be restored according to the file list of the backup file, and sends the identifier of the file to be restored to the standby host to obtain the first physical address of the data block included in the file to be restored.
  • the method for the standby host to obtain the first physical address specifically includes the following:
  • the standby host queries the metadata of the file system to which the file to be restored belongs according to the identifier of the file to be restored;
  • the standby host queries the first physical address of the data block included in the file to be restored according to the metadata of the file system;
  • the standby host sends the first physical address of the data block included in the file to be restored to the server.
  • the server sends the acquired first physical address of the data block included in the to-be-recovered file to the storage device.
  • a second aspect of the present invention provides a storage device, including a receiving unit and a processing unit, where the receiving unit is configured to receive a first physical address of a data block included in a file to be restored sent by a server;
  • the processing unit is configured to search for a recovery snapshot according to the first physical address of the data block included in the to-be-recovered file, according to the first physical address of the modified data block recorded in the recovery snapshot and the modified data block. Corresponding relationship of the second physical address in the resource volume, acquiring a second physical address of the modified data block in the to-be-recovered file in the resource volume, where the recovery snapshot is a snapshot volume for recovering the to-be-recovered file, and then And recovering the to-be-recovered file in the source volume according to the second physical address of the modified data block in the to-be-recovered file in the resource volume.
  • the storage device includes multiple snapshot volumes obtained by snapshotting at multiple snapshot time points, and the recovery snapshot is one of the multiple snapshot volumes, and the multiple snapshot volumes are
  • the method for determining the recovery snapshot is that the receiving unit receives the identifier of the recovery snapshot sent by the server, and the processing unit determines the recovery snapshot from the plurality of snapshot volumes according to the identifier of the recovery snapshot.
  • the recovery snapshot needs to be mounted to the standby host to obtain the file.
  • the first physical address of the data block included in the recovery file is taken, and the specific implementation manner is as follows:
  • the processing unit mapping the recovery snapshot to the standby host, so that the standby host acquires the first data block included in the to-be-recovered file according to the recovery snapshot a physical address, and the first physical address of the data block included in the file to be restored is sent to the server.
  • the processing unit is configured to recover the to-be-recovered file in the source volume according to the second physical address of the modified data block in the to-be-recovered file, in a specific manner.
  • the processing unit finds the modified data block in the resource volume according to the second physical address of the modified data block in the to-be-recovered file in the resource volume; and then recovers the source volume in the source volume by using the modified data block The file to be restored.
  • Another aspect of the present invention also provides a storage device comprising: a processor and a memory, wherein the memory is for storing an instruction for executing the instruction, the instruction causing the storage when executed by the processor The device performs the first aspect of the data recovery method.
  • the embodiment of the present invention has the following advantages: if the user needs to perform data recovery on a part of the source volume used by the production host to be modified or deleted, the user only needs to select on the server.
  • the server obtains the first physical address of the data block included in the file to be restored, and sends the data to the storage device according to the identifier of the to-be-recovered file, and the storage device is configured according to the data block included in the file to be restored.
  • a physical address lookup restores the snapshot, acquires the modified data block recorded in the resource volume in the recovery snapshot, and then recovers the to-be-recovered file in the source volume according to the modified data block recorded in the resource volume.
  • the present invention can perform specified recovery on selected files that need to be restored (for example, some damaged files) without copying all the data in the snapshot volume to the source volume as a whole, it will not be updated without being destroyed. File coverage can also greatly improve the efficiency of data recovery.
  • FIG. 1 is a schematic diagram of data recovery of a snapshot provided by the present invention
  • FIG. 2 is another schematic diagram of data recovery of a snapshot provided by the present invention.
  • FIG. 3 is a schematic diagram of a scenario deployment of a data recovery method provided by the present invention.
  • FIG. 4 is a schematic flow chart of an embodiment of a data recovery method provided by the present invention.
  • FIG. 5 is a schematic flowchart diagram of another embodiment of a data recovery method according to the present invention.
  • FIG. 6 is another schematic diagram of data recovery performed by a snapshot provided by the present invention.
  • FIG. 7 is another schematic diagram of data recovery performed by a snapshot provided by the present invention.
  • FIG. 8 is another schematic diagram of data recovery performed by a snapshot provided by the present invention.
  • FIG. 9 is another schematic diagram of data recovery performed by a snapshot provided by the present invention.
  • FIG. 10 is a schematic structural diagram of an embodiment of a storage device according to the present invention.
  • FIG. 11 is a schematic structural diagram of another embodiment of a storage device according to the present invention.
  • the physical entities included in FIG. 3 are mainly hosts, storage devices, and servers; for convenience of explanation, the related devices are matched in FIG.
  • Figure 3 includes a production host (or a service host) running the service, and the other is a backup host of the production host. When the production host fails or needs maintenance, the standby host can be enabled.
  • Figure 1 also includes the storage device and server.
  • the server (such as the Disaster Recovery Manager (DRM) server) is mainly responsible for centralized management of data disaster recovery, such as managing all production hosts that need to be disaster tolerant and the storage arrays/devices used by the production hosts, and can be
  • the time strategy (such as hourly/daily, etc.) generates a snapshot for the storage space (ie, the source volume) corresponding to the logical unit number (LUN) used by the production host; in the production host and the standby host in Figure 1,
  • the service agent agent needs to be deployed to enable the production host and the standby host to have the following functions: collect physical address information of files on the production host on the storage array/device.
  • the server in Figure 3 communicates with the production host/standby host through a LAN LAN and communicates through a Representational State Transfer (REST) interface.
  • the production host, the standby host, and the storage array/device are connected through the storage area network SAN and use the storage LUN provided by the storage array/device.
  • the server Before performing data recovery, it is assumed that the server has managed the storage array/device, service host (for example, production host, backup host), and the server has obtained the files on the production host (such as data files, control files, and the service agent through the production agent in the production host. Information about the log file, etc., and the source volume storing the file, and generating a storage snapshot volume for the source volume storing the file according to a certain time policy (such as hourly), completing the file on the production host (such as a data file) , backup of control files, log files, etc.).
  • service host for example, production host, backup host
  • the server has obtained the files on the production host (such as data files, control files, and the service agent through the production agent in the production host.
  • the server snapshots the source volume at a first snapshot time point to obtain a snapshot volume, and the obtained snapshot volume records that each data block included in the source volume is in the first snapshot time point.
  • the first physical address in the source volume If the data block in the source volume is modified before the next snapshot time point of the first snapshot time point, that is, before the second snapshot time point, the modified data block in the source volume is transferred to the resource by the server.
  • the volume is stored, and the server establishes, in the first snapshot, a correspondence between a first physical address of the modified data block and a second physical address of the modified data block in the resource volume.
  • the deleted or modified partial file may be restored by using data in the snapshot volume.
  • the method for restoring the modified partial file by using a snapshot and the partial file of the source volume being deleted in the case where a part of the file in the source volume is modified is respectively deleted by the snapshot.
  • the methods for recovering some files are introduced separately.
  • FIG. 4 a schematic flowchart of a method for restoring the modified partial file by using a snapshot in a case where a part of the file in the source volume is modified.
  • the recovery method includes the following steps:
  • the server determines the file to be restored according to the input of the user.
  • the user needs to log in to the server and select the file to be restored. For example, according to the information of the files in the production host saved on the server (such as the name or path of the file), select the files that need to be restored.
  • the server sends an identifier (ID) of the file to be restored to a production host.
  • ID identifier
  • the server sends the identifier of the file to be restored to the production host to obtain a first physical address of the data block included in the file to be restored in the production host, where the first physical address is The address of the file to be restored in the source volume. details as follows:
  • the server sends the ID of the file to be restored to the production host through the REST interface, and the production host queries the first physical address of the data block included in the file to be restored through the agent agent deployed therein, and the The first physical address is sent to the server, and the method for the production host to obtain the first physical address includes the following steps 103-105:
  • the production host queries the metadata of the file system to which the file to be restored belongs according to the identifier of the file to be restored.
  • the production host queries, according to the metadata of the file system, a first physical address of the data block included in the file to be restored.
  • the production host sends a first physical address of the data block included in the file to be restored to the server.
  • the server sends the acquired first physical address of the data block included in the to-be-recovered file to the storage device.
  • the server receives an ID of a recovery snapshot input by a user, and sends the ID of the recovery snapshot to the storage device.
  • the server sends the first physical address of the data block included in the to-be-recovered file and the ID of the recovery snapshot to the storage device through the REST interface.
  • step 107 may be performed after the step 106 is performed, or may be performed before the step 106 is performed, or may be sent to the storage device when the first physical address of the data block included in the file to be restored is sent to the storage device. And sending the ID of the recovery snapshot to the storage device, where the execution order of steps 106 and 107 is not limited.
  • the step 107 may not be performed.
  • the storage device receives a first physical address and a recovery snapshot ID of the data block included in the to-be-recovered file sent by the server.
  • step 108 the storage device only receives the first physical address of the data block included in the file to be restored sent by the server.
  • the storage device determines the recovery snapshot in multiple snapshot volumes in the storage device according to the received ID of the recovery snapshot.
  • this step may not be performed. Because there is only one snapshot volume in the storage device, it may be determined that the unique snapshot volume in the storage device is a recovery snapshot.
  • the storage device searches for a recovery snapshot according to the first physical address of the data block included in the to-be-recovered file, and according to the first physical address of the modified data block recorded in the recovery snapshot and the modified data. Obtaining a second physical address of the modified data block in the to-be-recovered file in the resource volume, where the recovery snapshot is used to restore the to-be-recovered The snapshot volume of the file.
  • the storage device recovers the to-be-recovered file in a source volume according to a second physical address in the resource volume of the modified data block in the to-be-recovered file.
  • the recovering the to-be-recovered file in the source volume according to the second physical address of the modified data block in the to-be-recovered file in the resource volume specifically includes:
  • a flowchart of a method for recovering data in a scenario in which a part of files in a source volume used by a production host is deleted includes the following steps:
  • the server determines an identifier of the standby host and a recovery snapshot identifier according to the input of the user.
  • the user needs to log in to the server, select the ID of the standby host, and restore the snapshot for recovering the file to be restored.
  • the first physical address of the deleted file does not exist in the file system of the production host, but when the server takes a snapshot of the source volume, the source volume is The file system including the first physical address of each file is also stored in the snapshot volume. Therefore, in order to obtain the physical address of the deleted file to be restored, the user needs to input the identifier of the standby host and the recovery snapshot identifier to pass the standby host. And recovering the snapshot to obtain the first physical address of the deleted file to be restored.
  • the server sends the identifier of the standby host and the recovery snapshot to the storage device.
  • the storage device receives an identifier and a recovery snapshot of the standby host sent by the server, and maps the recovery snapshot to the standby host.
  • the storage device determines the alternate host according to the identifier of the standby host, and receives the restored snapshot. Map to the alternate host so that the standby host reads and writes the recovery snapshot.
  • the server mounts the file system on the recovery snapshot to the standby host, and obtains, by using the standby host, a file list of the backup file on the recovery snapshot.
  • the server is notified by the REST interface to be deployed on the standby host, and the standby host mounts the file system on the recovery snapshot to a specified mount point on the backup host through a proxy agent deployed therein (for example, under the Windows operating system) On the D and E disks, /opt/data1, /opt/data2 under the Linux operating system).
  • a proxy agent deployed therein for example, under the Windows operating system
  • the standby host mounts the file system on the recovery snapshot to a specified mount point on the backup host through a proxy agent deployed therein (for example, under the Windows operating system) On the D and E disks, /opt/data1, /opt/data2 under the Linux operating system).
  • the server determines, according to a user input, a file to be restored in the file list of the backup file, and sends the identifier of the file to be restored to the standby host.
  • the user needs to log in to the server, and select a file to be restored from the file list of the backup file.
  • the server sends the identifier of the file to be restored to the standby host through the REST interface, and the standby host deploys the agent through the REST interface.
  • the agent queries the first physical address of the data block that is included in the to-be-recovered file, and sends the first physical address to the server.
  • the method for the standby host to obtain the first physical address includes the following step 206. ⁇ 208:
  • the backup host queries the metadata of the file system to which the file to be restored belongs according to the identifier of the file to be restored.
  • the standby host queries, according to the metadata of the file system, a first physical address of the data block included in the file to be restored.
  • the standby host sends a first physical address of the data block included in the file to be restored to the server.
  • Steps 209-213 are recovery of the file to be restored after the storage device receives the first physical address of the included data block of the file to be restored, and the method for restoring the file and the recovery of the modified file described in FIG. The method is the same as steps 106 and 108-111, and details are not described herein again.
  • the server may notify the standby host to uninstall the file system on the recovery snapshot from the standby host through the REST interface, and release the recovery snapshot from the standby host. Map to reduce the resource usage of the standby host while avoiding misuse of the data on the recovery snapshot.
  • the server After obtaining the first physical address of the data block included in the file to be restored, the server sends the first physical address of the data block included in the file to be restored, and the storage device sends the first physical address of the data block included in the file to be restored.
  • Finding a recovery snapshot acquiring a modified data block recorded in the resource volume in the recovery snapshot, and then restoring the to-be-recovered file in the source volume according to the modified data block recorded in the resource volume.
  • the present invention can perform specified recovery on selected files that need to be restored (for example, some damaged files) without copying all the data in the snapshot volume to the source volume as a whole, it will not be updated without being destroyed. File coverage can also greatly improve the efficiency of data recovery.
  • This scenario is described by using the snapshot to restore the modified part of the file in the case where the partial file in the source volume is modified.
  • the description may be corresponding to the description.
  • DB Server (English: Database Server, Chinese: Database Server) runs Oracle (Oracle is a relational database management system of Oracle, here is only an example of the application scenario) database, in the illustration
  • the database has two data files, DateFile1 and DateFile2, and is stored on the stored LUN1, the source volume.
  • the starting physical address of the corresponding data block of DateFile1 on LUN1 is 0, the ending physical address is 3, and the stored data is assumed to be 1, 2, 3, and 4; the starting physical address of the corresponding data block of DateFile2 on LUN1.
  • the end physical address is 7, and the stored data is assumed to be 5, 6, 7, and 8 respectively; the process of data corruption and recovery is demonstrated in the figure, and the specific process in combination with the present invention is as follows:
  • the server creates a storage snapshot Snapshot1 for LUN1 at 8:00 am, as shown in Figure 7, when the snapshot time arrives at 8:00, Snapshot1 is created for the data corresponding to DateFile1 and DateFile2 on LUN1;
  • DataFile1 is artificially damaged.
  • data 1 and 2 corresponding to the physical address of the data block on LUN1 being 0 to 1 are modified (as shown in FIG. 6 and FIG. 8 data 1).
  • 2 is modified to a, b);
  • the continuation of DataFile2 is updated, for example, the data on the physical address 4 in the source volume of Figure 8 is updated to A;
  • Data recovery of DataFile1 is selected. As shown in Fig. 6, 9:00 am, the state after the data recovery is completed.
  • the specific recovery process is as follows: Snapshot1 is selected as the recovery snapshot for restoring DataFile1, and the server determines the file to be restored DataFile1 according to the input of the user to obtain the physical address of the data block included in the DataFile1 (the physical address corresponding to the data 1 to 4 in FIG. 6 The address is 0 to 3 in Fig. 8).
  • the server After obtaining the physical address of the data block included in the DataFile1, the server sends the physical address of the data block included in the DataFile1 and the ID of the Snapshot1 to the storage device. After receiving the physical address of the data block included in the DataFile1 and the ID of the Snapshot1 sent by the server, the storage device first determines the recovery snapshot Snapshot1 corresponding to the ID of the Snapshot1, and then according to the physical address of the modified data block recorded in the Snapshot1 ( The correspondence between the physical address 0 to 1 in the bitmap mapping table shown in FIG. 8 and the physical address of the modified data block in the resource volume (the physical address of the data 1 and 2 in the resource volume shown in FIG. 8) is obtained.
  • the physical address of the modified data block in the file DataFile1 to be restored in the resource volume finds the data block corresponding to the data 1, 2 in the resource volume according to the physical address of the data 1, 2 in the resource volume shown in FIG. 8, and copy the data 1, 2 to the DataFile1 and modify it on the LUN1 in the source volume.
  • the data block corresponding to data 1, 2 As shown in FIG. 9, at 9:00 am, the data 1, 2 in the resource volume has been copied to the data block in which DataFile1 is modified on LUN1. Therefore, the data recovery method can perform data recovery on the modified DataFile1 without affecting the data written on the DataFile2 after the snapshot time point, and the prior art restores DataFile1 and DataFile2 by means of the overall copy.
  • the data 1 to 4 corresponding to the physical address of the data block on the LUN 1 is 0 to 3, and the data is deleted. Therefore, to recover data from DataFile1, you need to restore data 1 to 4 in the source volume.
  • the difference from the above example is that, since the file of DataFile1 is deleted, in order to obtain the physical address of the deleted file of DataFile1, the user needs to input the identifier of the standby host and the recovery snapshot identifier to obtain the obtained host through the backup host and the recovery snapshot. Delete the physical address of the file to be restored DataFile1.
  • the process of subsequent data recovery refer to the above examples, and details are not described herein.
  • the storage device provided by the present invention includes:
  • the receiving unit 301 is configured to receive a first physical address of the data block that is included in the to-be-recovered file sent by the server, where the server obtains the first physical address of the to-be-recovered file in the source volume, where the method is the same as that in the method embodiment. No longer.
  • the processing unit 302 is configured to search for a recovery snapshot according to the first physical address of the data block included in the to-be-recovered file, according to the first physical address of the modified data block recorded in the recovery snapshot, and the modified data block. Obtaining, in the corresponding relationship of the second physical address in the resource volume, a second physical address of the modified data block in the to-be-recovered file in the resource volume, where the recovery snapshot is used to restore the to-be-recovered Restore the snapshot volume of the file;
  • the storage device includes multiple snapshot volumes obtained by taking snapshots at multiple snapshot time points.
  • the storage device includes multiple snapshot volumes
  • the receiving unit 301 is further configured to receive an identifier of the recovery snapshot sent by the server;
  • the processing unit 302 is further configured to determine the recovery snapshot from the plurality of snapshot volumes according to the identifier of the recovery snapshot.
  • the receiving unit 301 is further configured to receive an identifier of the standby host sent by the server;
  • the processing unit 302 is further configured to map the recovery snapshot to the standby host, so that the standby host acquires a first physical address of a data block included in the file to be restored according to the recovery snapshot, and The first physical address of the data block included in the file to be restored is sent to the server.
  • the processing unit 302 is configured to recover the to-be-recovered file in the source volume according to the second physical address in the resource volume of the modified data block in the to-be-recovered file, specifically :
  • the processing unit 302 is configured to find the modified data block in the resource volume according to a second physical address in the resource volume of the modified data block in the to-be-recovered file, and then use the The modified data block restores the file to be recovered in the source volume.
  • FIG. 10 illustrates the specific structure of the storage device from the perspective of the functional unit.
  • the specific structure of the storage device is described from the hardware point of view below with reference to the embodiment shown in FIG.
  • the organization structure of the storage device provided by the present invention includes a processor 401 and a memory. 402, which may further include a bus 403 and a communication interface 404.
  • the processor 401, the memory 402, and the communication interface 403 can implement communication connection with each other through the bus 404, and can also implement communication by other means such as wireless transmission.
  • the memory 402 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviation: RAM); the memory 402 may also include a non-volatile memory (English: non-volatile memory) ), such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive , abbreviation: SSD); the memory 402 may also include a combination of the above types of memory.
  • Program code for implementing the present invention may be stored in memory 402 and executed by processor 401.
  • Memory 402 stores the following elements, executable modules or data structures, or subsets thereof, or their extended sets:
  • Operation instructions include various operation instructions for implementing various operations.
  • Operating system Includes a variety of system programs for implementing various basic services and handling hardware-based tasks.
  • the storage device may have more or less components than those shown in FIG. 11, may combine two or more components, or may have different component configurations or settings, and each component may include Hardware, software, or a combination of hardware and software implementations of one or more signal processing and/or application specific integrated circuits.
  • the processor 401 is configured to perform steps 108-111 of FIG.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another The system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种数据恢复方法及存储设备，用于提高数据恢复效率。所述方法包括：接收服务器发送的待恢复文件包括的数据块的第一物理地址(108)；根据待恢复文件所包括的数据块的第一物理地址查找恢复快照，根据恢复快照中记录的被修改数据块的第一物理地址与被修改数据块在资源卷中的第二物理地址的对应关系，获取待恢复文件中的被修改数据块在资源卷中的第二物理地址，所述恢复快照为用于恢复待恢复文件的快照卷(110)；根据待恢复文件中的被修改数据块在资源卷中的第二物理地址，在源卷中恢复待恢复文件(111)。

Description

数据恢复方法及存储设备 技术领域
本发明涉及存储领域，特别涉及一种数据恢复方法及存储设备。
背景技术
随着云计算、大数据等技术逐渐被企业认可，越来越多的企业正在构建自己的云数据中心为用户提供服务，以抢占市场先机，赢得客户的青睐，但构建数据中心必然面临的一大课题是如何保障用户的数据安全可靠。数据中心中的服务器常常会因火灾、洪水、地震等自然灾害导致计划外停机，造成业务中断；也会因为人为因素，如误操作、软件错误、病毒入侵导致业务中断。而一旦业务中断，将会给企业造成难以预估的损失。
为了保证业务的顺利开展，提出了快照技术。快照的作用主要是能够进行在线数据备份与恢复。当存储设备发生应用故障或者文件损坏时可以进行快速的数据恢复，将数据恢复至某个快照时间点的状态。传统的存储阵列快照技术是通过位图映射表的方式来记录源卷(被备份的LUN)中原数据和该原数据的物理地址的映射关系，如图1所示。当快照时间点到来时，存储阵列会在另外一个LUN中创建一个快照卷，所述快照卷包括位图映射表及资源卷，所述位图映射表用于记录源卷中原数据和该原数据的物理地址的映射关系，在对源卷进行快照后，若源卷中的数据被修改，则源卷中被修改的原数据被记录在所述资源卷中，并建立所述位图映射表中所述原数据的物理地址与资源卷中存储所述原数据的地址之间的映射关系。如图1所示，在进行快照时，存储阵列在位图映射表中记录源卷中的0号数据块到7号数据块的物理地址。在快照后，如图2所示，当需要将源卷中的原数据块d更新为s时，首先将源卷中的原数据d移动到资源卷中，然后建立位图映射表中所述原数据的物理地址与资源卷中存储所述原数据的物理地址的映射关系，然后将更新数据s写入到源卷中。同理，在将源卷中的数据c更新为t时，可以将原数据c记录在资源卷中，当源卷中的数据有损坏时，需要恢复到快照点的数据时，可通过快照数据的回滚实现，即将快照卷中的资源卷中记录的原数据块迁移至源卷中相应的位置，从而将源卷中 的数据恢复至快照时间点的数据。如图2所示，需要将数据回滚至快照时间点时，因源卷上的其他块的数据没有变化，仅需将资源卷中记录的原数据d和c拷贝至源卷位置3和2即可。
但由于人为误操作或病毒入侵仅仅是源卷中的部分文件被破坏，例如只有块2中的数据被破坏，如果采用上述快照数据的回滚方式实现数据的恢复，会将源卷中所有文件的数据恢复至快照时间点，即将块2及块3中的数据都恢复为快照时间点的数据d及c。然而该快照时间点之后被更改的数据如果没有被破坏，并不需要被恢复，即快照点后写入块3的数据s不需要被恢复，如果采用现有的恢复方式，不但无法只对被破坏的文件进行恢复，而且资源卷中记录的数据都要被迁移至源卷，恢复效率低下。
发明内容
本发明提供了一种数据恢复方法及存储设备，只对源卷中的部分文件进行恢复。
本发明第一方面提供了一种数据恢复方法，该恢复方法应用于存储设备，该存储设备包括源卷，该源卷包括多个数据块。服务器在第一快照时间点对该源卷进行快照得到快照卷，该快照卷用于记录该源卷所包括的每个数据块在该第一快照时间点所对应的第一物理地址。若在第二快照时间点之前该源卷中的数据块被修改，该源卷中的被修改数据块被转移到资源卷进行存储，并在该第一快照中，建立被修改数据块的第一物理地址与被修改数据块在该资源卷中的第二物理地址的对应关系，该第二快照时间点为该第一快照时间点的下一个快照时间点。该数据恢复方法具体包括：
首先，服务器需要获取待恢复文件所包括的数据块的第一物理地址。
而存储设备在接收到服务器发送的待恢复文件所包括的数据块的第一物理地址后，根据该待恢复文件所包括的数据块的第一物理地址查找恢复快照，然后根据该恢复快照中记录的被修改数据块的第一物理地址与该被修改数据块在该资源卷中的第二物理地址的对应关系，获取该待恢复文件中的被修改数据块在该资源卷中的第二物理地址，该恢复快照为用于恢复该待恢复文件的快照卷；
最后存储设备根据该待恢复文件中的被修改数据块在该资源卷中的第二物理地址，在该源卷中恢复该待恢复文件。
可选地，所述存储设备根据该待恢复文件中的被修改数据块在该资源卷中的第二物理地址，具体包括：该存储设备根据该待恢复文件中的被修改数据块在该资源卷中的第二物理地址在该资源卷中找到该被修改数据块，然后用该被修改数据块在该源卷中恢复该待恢复文件。
通过上述方法能够对选定的需要恢复的文件(例如某些损坏的文件)进行指定恢复，而不需将快照卷中所有数据整体拷贝至源卷，因此，不会对没有被破坏的文件进行覆盖，也能够大幅提高数据恢复的效率。
在生产主机所使用的源卷中的部分文件的数据被修改的场景下，该服务器获取待恢复文件所包括的数据块的第一物理地址的具体实现方式如下：
服务器根据用户的输入确定待恢复文件；
该服务器将该待恢复文件的标识发送给生产主机，以获取生产主机中待恢复文件所包括的数据块的第一物理地址。
该生产主机在收到服务器发送的待恢复文件的标识后获取该第一物理地址的方法具体包括如下：
生产主机根据该待恢复文件的标识查询该待恢复文件所属文件系统的元数据；
该生产主机根据该文件系统的元数据查询该待恢复文件所包括的数据块的第一物理地址；
该生产主机将该待恢复文件所包括的数据块的第一物理地址发送给该服务器。
如此，该服务器即可将所获取到的该待恢复文件所包括的数据块的第一物理地址发送给存储设备。
在生产主机所使用的源卷中的部分文件被删除的场景下，该服务器获取待恢复文件所包括的数据块的第一物理地址的具体实现方式如下：
服务器根据用户的输入确定备用主机的标识和恢复快照标识；
该服务器将该备用主机的标识和恢复快照发送给存储设备；
该存储设备接收该服务器发送的该备用主机的标识和恢复快照，并将该恢 复快照映射至该备用主机；
该服务器将该恢复快照上的文件系统挂载到该备用主机上，并通过该备用主机获取该恢复快照上备份文件的文件列表；
该服务器根据该备份文件的文件列表确定待恢复文件并将该待恢复文件的标识发送给备用主机，以获取待恢复文件所包括的数据块的第一物理地址。
该备用主机获取该第一物理地址的方法具体包括如下：
备用主机根据该待恢复文件的标识查询该待恢复文件所属文件系统的元数据；
该备用主机根据该文件系统的元数据查询该待恢复文件所包括的数据块的第一物理地址；
该备用主机将该待恢复文件所包括的数据块的第一物理地址发送给该服务器。
至此，该服务器将获取到的该待恢复文件所包括的数据块的第一物理地址发送给存储设备。
本发明的第二方面提供了一种存储设备，该存储设备包括接收单元及处理单元，所述接收单元用于接收服务器发送的待恢复文件所包括的数据块的第一物理地址；
所述处理单元，用于根据该待恢复文件所包括的数据块的第一物理地址查找恢复快照，根据该恢复快照中记录的被修改数据块的第一物理地址与该被修改数据块在该资源卷中的第二物理地址的对应关系，获取该待恢复文件中的被修改数据块在该资源卷中的第二物理地址，该恢复快照为用于恢复该待恢复文件的快照卷，然后根据该待恢复文件中的被修改数据块在该资源卷中的第二物理地址，在该源卷中恢复该待恢复文件。
在一个可能的设计中，该存储设备包括在多个快照时间点进行快照得到的多个快照卷，该恢复快照为该多个快照卷中的其中一个快照卷，则在所述多个快照卷中确定所述恢复快照的方法为，所述接收单元接收该服务器发送的该恢复快照的标识，所述处理单元根据该恢复快照的标识从该多个快照卷中确定该恢复快照。
在所述待恢复文件为删除文件时，需要将恢复快照挂载至备用主机才能获 取待恢复文件所包括数据块的第一物理地址，具体实现方式为：
所述接收单元接收该服务器发送的备用主机的标识；所述处理单元将该恢复快照映射至该备用主机，以使该备用主机根据该恢复快照获取该待恢复文件所包括的数据块的第一物理地址，并将该待恢复文件所包括的数据块的第一物理地址发送至该服务器。
在一个可能的设计中，该处理单元用于根据该待恢复文件中的被修改数据块在该资源卷中的第二物理地址，在该源卷中恢复该待恢复文件，具体方式为
该处理单元根据该待恢复文件中的被修改数据块在该资源卷中的第二物理地址在该资源卷中找到该被修改数据块；然后用该被修改数据块在该源卷中恢复该待恢复文件。
本发明另一方面还提供了一种存储设备，包括：处理器以及存储器，其中，该存储器用于存储指令，该处理器用于执行该指令，该指令在被该处理器执行时，使该存储设备执行第一方面的数据恢复方法。
从以上技术方案可以看出，本发明实施例具有以下优点：如果用户需要对生产主机所使用的源卷中数据被修改的或者被删除的部分文件进行数据恢复，用户只需在服务器上选择待恢复文件，该服务器通过该待恢复文件的标识获取待恢复文件所包括的数据块的第一物理地址后，发送给存储设备，而存储设备则根据所述待恢复文件所包括的数据块的第一物理地址查找恢复快照，获取所述恢复快照中的被记录在资源卷中的被修改数据块，然后根据记录在资源卷中的被修改数据块在源卷中恢复所述待恢复文件。由于本发明能够对选定的需要恢复的文件(例如某些损坏的文件)进行指定恢复，而不需将快照卷中所有数据整体拷贝至源卷，因此，不会对没有被破坏的已更新文件进行覆盖，也能够大幅提高数据恢复的效率。
附图说明
图1为本发明所提供的快照进行数据恢复的一个示意图；
图2为本发明所提供的快照进行数据恢复的另一个示意图；
图3为本发明所提供的数据恢复方法的一个场景部署示意图；
图4为本发明所提供的数据恢复方法的一个实施例流程示意图；
图5为本发明所提供的数据恢复方法的另一实施例流程示意图；
图6为本发明所提供的快照进行数据恢复的另一个示意图；
图7为本发明所提供的快照进行数据恢复的另一个示意图；
图8为本发明所提供的快照进行数据恢复的另一个示意图；
图9为本发明所提供的快照进行数据恢复的另一个示意图；
图10为本发明所提供的存储设备的一个实施例结构示意图；
图11为本发明所提供的存储设备的另一实施例结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，下面所描述的实施例仅仅是本发明一部分实施例，而非全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
如图3所示，为实现本发明数据恢复方法的一种可能的场景部署，图3中包括的物理实体主要为主机、存储设备、服务器；为便于说明，图3中对相关设备进行了符合该场景的命名，但并非对设备的相应功能做出限制，在实际部署中对设备的数量也不做限制。图3中包括一个运行业务的生产主机(或者叫业务主机)，另一个为该生产主机的备用主机，当生产主机故障或需要维护时，可以启用所述备用主机，图1还包括存储设备以及服务器。该服务器(例如灾难恢复管理(Disaster Recovery Manager，DRM)服务器)主要负责数据灾难恢复的集中管理，如管理所有需要进行容灾的生产主机以及生产主机所使用的存储阵列/设备，并且可以按照一定的时间策略(如每小时/每天等)为生产主机所使用的逻辑单元号(Logical Unit Number，LUN)对应的存储空间(即源卷)生成快照；图1中的生产主机和备用主机中，需要部署业务代理Agent使生产主机和备用主机具备如下功能：收集生产主机上的文件在存储阵列/设备上的物理地址信息。图3中的服务器与生产主机/备用主机之间通过局域网LAN联通，并通过表述性状态传递(Representational State Transfer，REST)接口进行通信。生产主机、备用主机以及存储阵列/设备之间通过存储区域网络SAN连通，并使用存储阵列/设备提供的存储LUN。
在进行数据恢复前假定服务器已经将存储阵列/设备、业务主机(例如生产主机、备用主机)进行管理，服务器已经通过生产主机中的业务代理获取生产主机上的文件(如数据文件、控制文件、日志文件等)的信息及存储所述文件的源卷，并按照一定的时间策略(如每小时)对存储所述文件的源卷生成存储快照卷，完成对生产主机上的文件(如数据文件、控制文件、日志文件等)的备份。
假设所述服务器在第一快照时间点对所述源卷进行快照得到快照卷，所得到的快照卷中记录了所述源卷所包括的每个数据块在所述第一快照时间点在所述源卷中的第一物理地址。若在所述第一快照时间点的下一个快照时间点即第二快照时间点之前所述源卷中的数据块被修改，所述源卷中的被修改数据块被所述服务器转移到资源卷进行存储，所述服务器在所述第一快照中建立所述被修改数据块的第一物理地址与所述被修改数据块在所述资源卷中的第二物理地址的对应关系。
在本发明的技术方案中，在所述源卷中的部分文件被删除或者部分文件的数据被修改之后，可通过快照卷中的数据对所述被删除或者被修改的部分文件进行恢复。
为便于理解，下面分别对源卷中部分文件被修改的情况下通过快照对所述被修改的部分文件进行恢复的方法及源卷中部分文件被删除的情况下通过快照对所述被删除的部分文件进行恢复的方法分别介绍。
如图4所示，为对源卷中部分文件被修改的情况下通过快照对所述被修改的部分文件进行恢复的方法流程示意图。所述恢复方法包括以下步骤：
101、服务器根据用户的输入确定待恢复文件。
该步骤中，用户需要登录该服务器，选择待恢复文件。例如根据服务器上保存的生产主机中文件的信息(如文件的名称或路径)，选择所需要恢复的文件。
102、所述服务器将所述待恢复文件的标识(Identifier,ID)发送给生产主机。
该步骤中，该服务器将所述待恢复文件的标识发送给生产主机，以获取生产主机中待恢复文件所包括的数据块的第一物理地址，所述第一物理地址即为 所述待恢复文件在所述源卷中的地址。具体如下：
该服务器将该待恢复文件的ID通过REST接口下发给该生产主机，所述生产主机通过其中部署的代理Agent查询所述待恢复文件所包括的数据块的第一物理地址，并将所述第一物理地址发送给所述服务器，所述生产主机获取所述第一物理地址的方法具体包括如下步骤103～105：
103、生产主机根据所述待恢复文件的标识查询所述待恢复文件所属文件系统的元数据。
104、所述生产主机根据所述文件系统的元数据查询所述待恢复文件所包括的数据块的第一物理地址。
105、所述生产主机将所述待恢复文件所包括的数据块的第一物理地址发送给所述服务器。
106、所述服务器将获取到的所述待恢复文件所包括的数据块的第一物理地址发送给存储设备。
107、所述服务器接收用户输入的恢复快照的ID，并将所述恢复快照的ID发送给所述存储设备。
具体的，该服务器通过REST接口将所述待恢复文件所包括的数据块的第一物理地址及所述恢复快照的ID发送给存储设备。
需要说明的是，步骤107可以在步骤106执行完之后执行，也可以在步骤106执行完之前执行，也可以在所述待恢复文件所包括的数据块的第一物理地址发送给存储设备时，一并将所述恢复快照的ID发送给所述存储设备，在这里不对步骤106及107的执行顺序做限制。
另外，如果所述服务器只做了一次快照，即存储设备中只存在一个快照卷，则也可以不执行所述步骤107。
108、存储设备接收所述服务器发送的所述待恢复文件所包括的数据块的第一物理地址及恢复快照ID。
需要说明的是，在服务器不执行所述步骤107时，则在步骤108中，存储设备只接收服务器发送的所述待恢复文件所包括的数据块的第一物理地址。
109、存储设备根据所接收的恢复快照的ID在所述存储设备中的多个快照卷中确定所述恢复快照。
同样，在服务器不执行所述步骤107时，此步骤也可以不执行，因为存储设备中只有一个快照卷，则可确定存储设备中的唯一的快照卷为恢复快照。
110、所述存储设备根据所述待恢复文件所包括的数据块的第一物理地址查找恢复快照，并根据所述恢复快照中记录的被修改数据块的第一物理地址与所述被修改数据块在资源卷中的第二物理地址的对应关系，获取所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址，所述恢复快照为用于恢复所述待恢复文件的快照卷。
111、所述存储设备根据所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址，在源卷中恢复所述待恢复文件。
可选的，所述根据所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址，在所述源卷中恢复所述待恢复文件具体包括：
根据所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址在所述资源卷中找到所述被修改数据块；
用所述被修改数据块在所述源卷中恢复所述待恢复文件。
如图5所示，为对生产主机所使用的源卷中的部分文件被删除的场景下的数据进行恢复的方法的流程图，所述方法包括以下步骤：
201、服务器根据用户的输入确定备用主机的标识和恢复快照标识。
该步骤中，用户需要登录该服务器，选择备用主机的ID和用来恢复待恢复文件的恢复快照。
需要说明的是，在源卷中的文件被删除后，在生产主机的文件系统中，所删除文件的第一物理地址也不存在，但是在服务器对源卷进行快照时，会把源卷中的包括各文件的第一物理地址的文件系统也存储至快照卷中，所以为了获取待恢复的被删除文件的物理地址，需要用户输入备用主机的标识和恢复快照标识，以通过所述备用主机及恢复快照获取被删除的待恢复文件的第一物理地址。
202、所述服务器将所述备用主机的标识和恢复快照发送给存储设备。
203、所述存储设备接收所述服务器发送的所述备用主机的标识和恢复快照，并将所述恢复快照映射至所述备用主机。
该存储设备根据该备用主机的标识确定备用主机，并将接收到的恢复快照 映射至该备用主机，以便该备用主机对该恢复快照进行读写。
204、所述服务器将所述恢复快照上的文件系统挂载到所述备用主机上，并通过所述备用主机获取所述恢复快照上备份文件的文件列表。
具体的，该服务器通过REST接口通知部署在该备用主机，该备用主机通过其中部署的代理Agent将该恢复快照上的文件系统挂载到该备用主机上的指定挂载点(例如Windows操作系统下的D、E盘上，Linux操作系统下的/opt/data1、/opt/data2上)。从而获取该恢复快照上备份文件的文件列表。
205、所述服务器根据用户的输入在所述备份文件的文件列表确定待恢复文件并将所述待恢复文件的标识发送给备用主机。
该步骤中，用户需要登录该服务器，从备份文件的文件列表中选择待恢复的文件，该服务器将确定的该待恢复文件的标识通过REST接口发送给备用主机，该备用主机通过其中部署的代理Agent查询所述待恢复文件所包括的数据块的第一物理地址，并将所述第一物理地址发送给所述服务器，所述备用主机获取所述第一物理地址的方法具体包括如下步骤206～208：
206、备用主机根据所述待恢复文件的标识查询所述待恢复文件所属文件系统的元数据。
207、所述备用主机根据所述文件系统的元数据查询所述待恢复文件所包括的数据块的第一物理地址。
208、所述备用主机将所述待恢复文件所包括的数据块的第一物理地址发送给所述服务器。
步骤209-213为存储设备在接收到所述待恢复文件的所包括的数据块的第一物理地址后，对待恢复文件的恢复，恢复文件的方法与图4中描述的对被修改文件的恢复方法即步骤106、108-111相同，在此不再赘述。
可选的，在步骤214中待恢复文件恢复完成后，该服务器可通过REST接口通知备用主机将该恢复快照上的文件系统从该备用主机上卸载，并将该恢复快照从该备用主机上解除映射，以减少对备用主机的资源占用，同时避免误操作破坏该恢复快照上的数据。
本发明实施例中，如果用户需要对生产主机所使用的源卷中数据被修改的或者被删除的部分文件进行数据恢复，用户只需在服务器上选择待恢复文件， 该服务器通过该待恢复文件的标识获取待恢复文件所包括的数据块的第一物理地址后，发送给存储设备，而存储设备则根据所述待恢复文件所包括的数据块的第一物理地址查找恢复快照，获取所述恢复快照中的被记录在资源卷中的被修改数据块，然后根据记录在资源卷中的被修改数据块在源卷中恢复所述待恢复文件。由于本发明能够对选定的需要恢复的文件(例如某些损坏的文件)进行指定恢复，而不需将快照卷中所有数据整体拷贝至源卷，因此，不会对没有被破坏的已更新文件进行覆盖，也能够大幅提高数据恢复的效率。
为便于理解，下面以一具体应用场景对本发明实施例中的数据恢复方法进行具体描述：
本场景对源卷中部分文件被修改的情况下通过快照对所述被修改的部分文件进行恢复为例进行说明，对于部分文件被删除的场景可对应参考本说明。
如图6所示，DB Server(英文：Database Server，中文：数据库服务器)上运行Oracle(Oracle为甲骨文公司的一款关系数据库管理系统，此处仅作为应用场景的举例说明)数据库，图示中该数据库有2个数据文件DateFile1与DateFile2，且存放在存储的LUN1，即源卷上。假设DateFile1在LUN1上对应的数据块的起始物理地址为0，结束物理地址为3，假定存放的数据分别为1、2、3、4；DateFile2在LUN1上对应的数据块的起始物理地址为4，结束物理地址为7，假定存放的数据分别为5、6、7、8；图中演示了数据损坏与恢复的过程，结合本发明的具体流程如下：
例如服务器上午8：00为LUN1创建了一个存储快照Snapshot1，如图7所示，快照时间点8:00到来时为LUN1上DateFile1与DateFile2对应的数据创建的Snapshot1；
结合图6及图8，上午8：30，DataFile1被人为损坏，例如对应在LUN1上的数据块的物理地址为0～1上的数据1、2被修改(如图6、图8中数据1、2被修改为a、b)；DataFile2上的继续被更新，例如图8源卷中物理地址4上的数据被更新为A；
如果DataFile2上的继续被更新的数据为有用数据，那么只需对损坏的DataFile1进行数据恢复即可，借助本发明技术方案，选定对DataFile1进行数据恢复。如图6所示，上午9：00，为数据恢复完成后的状态。具体恢复过程如下： 选定Snapshot1作为用来恢复DataFile1的恢复快照，服务器根据用户的输入确定待恢复文件DataFile1，以获取该DataFile1所包括的数据块的物理地址(图6中数据1～4对应的物理地址，该物理地址在图8中为0～3)。服务器在获取到该DataFile1所包括的数据块的物理地址后，将该DataFile1所包括的数据块的物理地址及Snapshot1的ID发送给存储设备。该存储设备接收到该服务器发送的该DataFile1所包括的数据块的物理地址及Snapshot1的ID后，首先确定Snapshot1的ID对应的恢复快照Snapshot1，然后根据Snapshot1中记录的被修改数据块的物理地址(图8所示位图映射表中物理地址0～1)与所述被修改数据块在资源卷中的物理地址(图8所示资源卷中数据1、2的物理地址)的对应关系，获取待恢复文件DataFile1中的被修改数据块在所述资源卷中的物理地址。根据图8所示资源卷中数据1、2的物理地址在该资源卷中找到数据1、2对应的数据块，并在源卷中将该数据1、2拷贝至DataFile1在LUN1上被修改的数据1、2所对应的数据块中。如图9所示，上午9：00，资源卷中的数据1、2已拷贝至DataFile1在LUN1上数据被修改的数据块中。因此，通过该数据恢复的方法，可以对被修改的DataFile1进行数据恢复，且不影响在快照时间点后DataFile2上写入的数据，而现有技术通过整体拷贝的方式会将DataFile1和DataFile2均恢复至源卷，因此在这种情况下，通过本发明提供的数据恢复方法进行数据恢复时，不需将快照卷中所有数据整体拷贝至源卷，因此，不会对没有被破坏的文件进行覆盖，也能够大幅提高数据恢复的效率。
对源卷中的部分文件被删除的场景下也可参考上述实例，例如，如果上述DataFile1被删除，则对应在LUN1上的数据块的物理地址为0～3上的数据1～4被删除，因此，对DataFile1进行数据恢复，则需要恢复源卷中的数据1～4。与上述实例的不同之处在于，由于DataFile1的文件被删除，为了获取DataFile1的被删除文件的物理地址，需要用户输入备用主机的标识和恢复快照标识，以通过所述备用主机及恢复快照获取被删除的待恢复文件DataFile1的物理地址。后续数据恢复的过程则可参考上述实例，此处不再赘述。
以上对本发明所提供的数据恢复方法进行了说明，下面将从装置的角度对本发明所涉及的相关装置的结构进行说明，请参阅图10，本发明所提供的存储设备包括：
接收单元301，用于接收服务器发送的待恢复文件所包括的数据块的第一物理地址；服务器获取待恢复文件在源卷中的第一物理地址的方式与方法实施例中的相同，在此不再赘述。
处理单元302，用于根据所述待恢复文件所包括的数据块的第一物理地址查找恢复快照，根据所述恢复快照中记录的被修改数据块的第一物理地址与所述被修改数据块在所述资源卷中的第二物理地址的对应关系，获取所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址，所述恢复快照为用于恢复所述待恢复文件的快照卷；
以及，根据所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址，在所述源卷中恢复所述待恢复文件。
可选的，所述存储设备包括在多个快照时间点进行快照得到的多个快照卷。在所述存储设备包括多个快照卷时，
所述接收单元301还用于接收所述服务器发送的所述恢复快照的标识；
所述处理单元302还用于，根据所述恢复快照的标识从所述多个快照卷中确定所述恢复快照。
可选的，在所述待恢复文件为删除文件时，所述接收单元301还用于接收所述服务器发送的备用主机的标识；
所述处理单元302还用于将所述恢复快照映射至所述备用主机，以使所述备用主机根据所述恢复快照获取所述待恢复文件所包括的数据块的第一物理地址，并将所述待恢复文件所包括的数据块的第一物理地址发送至所述服务器。
可选的，所述处理单元302用于根据所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址，在所述源卷中恢复所述待恢复文件，具体为：
所述处理单元302，用于根据所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址在所述资源卷中找到所述被修改数据块，然后用所述被修改数据块在所述源卷中恢复所述待恢复文件。
图10所示的实施例从功能单元的角度对存储设备的具体结构进行了说明，以下结合图11所示的实施例从硬件角度对存储设备的具体结构进行说明：
如图11所示，本发明提供的存储设备的组织结构包括处理器401、存储器 402，还可以包括总线403、通信接口404。
其中，处理器401、存储器402和通信接口403可以通过总线404实现彼此之间的通信连接，也可以通过无线传输等其他手段实现通信。
存储器402可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器402也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器402还可以包括上述种类的存储器的组合。用于实现本发明的程序代码可以保存在存储器402中，并由处理器401来执行。
存储器402存储了如下的元素，可执行模块或者数据结构，或者它们的子集，或者它们的扩展集:
操作指令：包括各种操作指令，用于实现各种操作。
操作系统：包括各种系统程序，用于实现各种基础业务以及处理基于硬件的任务。
本发明实施例涉及的存储设备可以具有比图11所示出的更多或更少的部件，可以组合两个或更多个部件，或者可以具有不同的部件配置或设置，各个部件可以在包括一个或多个信号处理和/或专用集成电路在内的硬件、软件或硬件和软件的组合实现。
本发明实施例中，所述处理器401用于执行图4步骤108～111。
上述装置的相关描述可以对应参阅方法实施例部分的相关描述和效果进行理解，本处不做过多赘述。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个 系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，以上实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (9)

  1. 一种数据恢复方法，应用于存储设备，其特征在于，所述存储设备包括源卷，所述源卷包括多个数据块，在第一快照时间点对所述源卷进行快照得到快照卷，所述快照卷用于记录所述源卷所包括的每个数据块在所述第一快照时间点所对应的第一物理地址，若在第二快照时间点之前所述源卷中的数据块被修改，所述源卷中的被修改数据块被转移到资源卷进行存储，并在所述第一快照中，建立所述被修改数据块的第一物理地址与所述被修改数据块在所述资源卷中的第二物理地址的对应关系，所述第二快照时间点为所述第一快照时间点的下一个快照时间点；
    所述方法包括：
    接收服务器发送的待恢复文件所包括的数据块的第一物理地址；
    根据所述待恢复文件所包括的数据块的第一物理地址查找恢复快照，根据所述恢复快照中记录的被修改数据块的第一物理地址与所述被修改数据块在所述资源卷中的第二物理地址的对应关系，获取所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址，所述恢复快照为用于恢复所述待恢复文件的快照卷；
    根据所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址，在所述源卷中恢复所述待恢复文件。
  2. 根据权利要求1所述的方法，其特征在于，所述存储设备包括在多个快照时间点进行快照得到的多个快照卷，所述方法还包括：
    接收所述服务器发送的所述恢复快照的标识；
    根据所述恢复快照的标识从所述多个快照卷中确定所述恢复快照。
  3. 根据权利要求1或2所述的方法，其特征在于，在所述接收服务器发送的所述待恢复文件所包括的每个数据块的第一物理地址之前，所述方法还包括：
    接收所述服务器发送的备用主机的标识；
    将所述恢复快照映射至所述备用主机，以使所述备用主机根据所述恢复快照获取所述待恢复文件所包括的数据块的第一物理地址，并将所述待恢复文件所包括的数据块的第一物理地址发送至所述服务器。
  4. 根据权利要求1至3任意一项所述的方法，其特征在于，所述根据所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址，在所述源卷中恢复所述待恢复文件具体包括：
    根据所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址在所述资源卷中找到所述被修改数据块；
    用所述被修改数据块在所述源卷中恢复所述待恢复文件。
  5. 一种存储设备，其特征在于，所述存储设备包括源卷，所述源卷包括多个数据块，在第一快照时间点对所述源卷进行快照得到快照卷，所述快照卷用于记录所述源卷所包括的每个数据块在所述第一快照时间点所对应的第一物理地址，若在第二快照时间点之前所述源卷中的数据块被修改，所述源卷中的被修改数据块被转移到资源卷进行存储，并在所述第一快照中，建立所述被修改数据块的第一物理地址与所述被修改数据块在所述资源卷中的第二物理地址的对应关系，所述第二快照时间点为所述第一快照时间点的下一个快照时间点；所述存储设备包括：
    接收单元，用于接收服务器发送的待恢复文件所包括的数据块的第一物理地址；
    处理单元，用于根据所述待恢复文件所包括的数据块的第一物理地址查找恢复快照，根据所述恢复快照中记录的被修改数据块的第一物理地址与所述被修改数据块在所述资源卷中的第二物理地址的对应关系，获取所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址，所述恢复快照为用于恢复所述待恢复文件的快照卷；
    以及，根据所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址，在所述源卷中恢复所述待恢复文件。
  6. 根据权利要求5所述的存储设备，其特征在于，所述存储设备包括在多个快照时间点进行快照得到的多个快照卷，
    所述接收单元还用于，接收所述服务器发送的所述恢复快照的标识；
    所述处理单元还用于，根据所述恢复快照的标识从所述多个快照卷中确定所述恢复快照。
  7. 根据权利要求5或6所述的存储设备，其特征在于，
    所述接收单元还用于，接收所述服务器发送的备用主机的标识；
    所述处理单元还用于，将所述恢复快照映射至所述备用主机，以使所述备用主机根据所述恢复快照获取所述待恢复文件所包括的数据块的第一物理地址，并将所述待恢复文件所包括的数据块的第一物理地址发送至所述服务器。
  8. 根据权利要求5至7任意一项所述的存储设备，其特征在于，所述处理单元用于根据所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址，在所述源卷中恢复所述待恢复文件，具体为：
    所述处理单元，用于根据所述待恢复文件中的被修改数据块在所述资源卷中的第二物理地址在所述资源卷中找到所述被修改数据块；
    以及，用所述被修改数据块在所述源卷中恢复所述待恢复文件。
  9. 一种存储设备，包括：处理器以及存储器，其特征在于，所述存储器用于存储指令，所述处理器用于执行所述指令，所述指令在被所述处理器执行时，使所述存储设备执行如权利要求1至4中任一项所述的方法。
PCT/CN2016/073038 2016-02-01 2016-02-01 数据恢复方法及存储设备 WO2017132790A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
CN201680003255.0A CN108351821B (zh) 2016-02-01 2016-02-01 数据恢复方法及存储设备
EP16847617.4A EP3223158B1 (en) 2016-02-01 2016-02-01 Data recovery method and storage system
PCT/CN2016/073038 WO2017132790A1 (zh) 2016-02-01 2016-02-01 数据恢复方法及存储设备
US15/491,473 US20170220427A1 (en) 2016-02-01 2017-04-19 Data Recovery Method and Storage Device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/073038 WO2017132790A1 (zh) 2016-02-01 2016-02-01 数据恢复方法及存储设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/491,473 Continuation US20170220427A1 (en) 2016-02-01 2017-04-19 Data Recovery Method and Storage Device

Publications (1)

Publication Number Publication Date
WO2017132790A1 true WO2017132790A1 (zh) 2017-08-10

Family

ID=59386686

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/073038 WO2017132790A1 (zh) 2016-02-01 2016-02-01 数据恢复方法及存储设备

Country Status (4)

Country Link
US (1) US20170220427A1 (zh)
EP (1) EP3223158B1 (zh)
CN (1) CN108351821B (zh)
WO (1) WO2017132790A1 (zh)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10417098B2 (en) * 2016-06-28 2019-09-17 International Business Machines Corporation File level access to block level incremental backups of a virtual disk
US11120133B2 (en) * 2017-11-07 2021-09-14 Spinbackup Inc. Ransomware protection for cloud storage systems
CN109241061B (zh) * 2018-09-14 2022-02-11 上海新炬网络信息技术股份有限公司 用于Oracle数据库Truncate操作的保护方法
CN109491832A (zh) * 2018-09-26 2019-03-19 华为技术有限公司 数据容灾方法与站点
CN109905316B (zh) * 2019-02-28 2022-06-03 努比亚技术有限公司 一种信息恢复的方法、终端及计算机可读存储介质
US11343282B2 (en) * 2019-10-18 2022-05-24 EMC IP Holding Company LLC Storage and data protection as a service in a cloud native environment
CN110941511B (zh) * 2019-11-21 2023-03-21 深信服科技股份有限公司 一种快照合并方法、装置、设备及存储介质
US11392436B2 (en) 2020-04-01 2022-07-19 Western Digital Technologies, Inc. Advanced file recovery method for flash memory
CN112925643B (zh) * 2021-02-26 2024-01-12 北京百度网讯科技有限公司 数据处理方法、装置以及存储引擎装置
US11886226B2 (en) 2021-11-29 2024-01-30 Rubrik, Inc. Consolidating snapshots using partitioned patch files
US20230350764A1 (en) * 2022-04-28 2023-11-02 Rubrik, Inc. Backup data consolidation

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101419564A (zh) * 2008-12-11 2009-04-29 杭州华三通信技术有限公司 一种采用快照恢复数据的方法和装置
CN101520743A (zh) * 2009-04-17 2009-09-02 杭州华三通信技术有限公司 基于写时拷贝的数据存储方法、系统及设备
EP2105835A2 (en) * 2008-03-26 2009-09-30 Symantec Corporation Using volume snapshots to prevent file corruption in failed restore operations
CN103678039A (zh) * 2013-12-05 2014-03-26 华为技术有限公司 数据恢复方法及设备

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6957362B2 (en) * 2002-08-06 2005-10-18 Emc Corporation Instantaneous restoration of a production copy from a snapshot copy in a data storage system
AU2003282361A1 (en) * 2002-11-20 2004-06-15 Filesx Ltd. Fast backup storage and fast recovery of data (fbsrd)
CA2548542C (en) * 2003-11-13 2011-08-09 Commvault Systems, Inc. System and method for performing a snapshot and for restoring data
JP4456909B2 (ja) * 2004-03-29 2010-04-28 株式会社日立製作所 バックアップ方法、ストレージシステム及びそのプログラム
CN1866806B (zh) * 2005-12-22 2011-11-02 华为技术有限公司 共享格状网恢复的实现方法
CN1873622A (zh) * 2006-04-20 2006-12-06 北京艾德斯科技有限公司 San环境下数据备份、复制和恢复的方法及其装置
CN100464307C (zh) * 2006-05-26 2009-02-25 任永坚 一种实现数据备份和恢复的方法及系统
US8200638B1 (en) * 2008-04-30 2012-06-12 Netapp, Inc. Individual file restore from block-level incremental backups by using client-server backup protocol
WO2010065271A2 (en) * 2008-11-25 2010-06-10 Board Of Governors For Higher Education, State Of Rhode Island And Providence Plantations Systems and methods for providing continuous file protection at block level
US8645647B2 (en) * 2009-09-02 2014-02-04 International Business Machines Corporation Data storage snapshot with reduced copy-on-write
US8595191B2 (en) * 2009-12-31 2013-11-26 Commvault Systems, Inc. Systems and methods for performing data management operations using snapshots
US9244779B2 (en) * 2010-09-30 2016-01-26 Commvault Systems, Inc. Data recovery operations, such as recovery from modified network data management protocol data
US9015526B2 (en) * 2012-10-05 2015-04-21 Hitachi, Ltd. Restoring method and computer system
CN103617097B (zh) * 2013-11-19 2017-07-07 华为技术有限公司 文件恢复方法及装置
US20170097785A1 (en) * 2015-10-01 2017-04-06 Hewlett Packard Enterprise Development Lp Data block snapshots

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2105835A2 (en) * 2008-03-26 2009-09-30 Symantec Corporation Using volume snapshots to prevent file corruption in failed restore operations
CN101419564A (zh) * 2008-12-11 2009-04-29 杭州华三通信技术有限公司 一种采用快照恢复数据的方法和装置
CN101520743A (zh) * 2009-04-17 2009-09-02 杭州华三通信技术有限公司 基于写时拷贝的数据存储方法、系统及设备
CN103678039A (zh) * 2013-12-05 2014-03-26 华为技术有限公司 数据恢复方法及设备

Also Published As

Publication number Publication date
US20170220427A1 (en) 2017-08-03
EP3223158B1 (en) 2020-04-22
EP3223158A4 (en) 2018-05-23
CN108351821A (zh) 2018-07-31
CN108351821B (zh) 2022-03-29
EP3223158A1 (en) 2017-09-27

Similar Documents

Publication Publication Date Title
WO2017132790A1 (zh) 数据恢复方法及存储设备
US11429305B2 (en) Performing backup operations using replicas
US10831608B2 (en) Systems and methods for performing data management operations using snapshots
US9940205B2 (en) Virtual point in time access between snapshots
US9250824B2 (en) Backing up method, device, and system for virtual machine
US9256605B1 (en) Reading and writing to an unexposed device
US10146637B1 (en) Intelligent snapshot rollbacks
US9483367B1 (en) Data recovery in distributed storage environments
CA2613359A1 (en) System and method for high performance enterprise data protection
US7584339B1 (en) Remote backup and restore operations for ISB protocol systems
US9733869B1 (en) Provisioning a slave for data storage using metadata with updated references
US10452680B1 (en) Catch-up replication with log peer
WO2023046042A1 (zh) 一种数据备份方法和数据库集群
US9928246B1 (en) Managing snapshots of data
US10484179B1 (en) Data consistency in an encrypted replication environment
US7587565B1 (en) Generating automated and scheduled SAN copy sessions for ISB protocol systems
CN112380050A (zh) 一种利用快照在系统备份中的方法
US11899540B2 (en) Regenerating a chain of backups
US11467929B2 (en) Reducing failover time between data nodes
CN110413370B (zh) 用于实现依赖原始设备映射盘的虚拟机的数据备份的方法和系统
US11880283B2 (en) Backup copy validation as a workflow
US11934275B2 (en) Backup copy validation as an embedded object
US11899538B2 (en) Storage integrated differential block based backup
US11782799B2 (en) Using bitmaps to validate data
US20230205641A1 (en) Disaster recovery drills based on checksum validations

Legal Events

Date Code Title Description
REEP Request for entry into the european phase

Ref document number: 2016847617

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2016847617

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE