WO2017211099A1 - Procédé et appareil de sauvegarde de données - Google Patents

Procédé et appareil de sauvegarde de données Download PDF

Info

Publication number
WO2017211099A1
WO2017211099A1 PCT/CN2017/075489 CN2017075489W WO2017211099A1 WO 2017211099 A1 WO2017211099 A1 WO 2017211099A1 CN 2017075489 W CN2017075489 W CN 2017075489W WO 2017211099 A1 WO2017211099 A1 WO 2017211099A1
Authority
WO
WIPO (PCT)
Prior art keywords
backup
storage device
application
data
disk
Prior art date
Application number
PCT/CN2017/075489
Other languages
English (en)
Chinese (zh)
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 华为技术有限公司
Publication of WO2017211099A1 publication Critical patent/WO2017211099A1/fr

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21Design, administration or maintenance of databases
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/80Database-specific techniques

Definitions

  • the present invention relates to the field of computers, and in particular, to a data backup method and apparatus.
  • IT systems in enterprise data centers may cause unplanned downtime due to natural disasters such as fires, floods, earthquakes, etc., resulting in business interruptions, or business interruptions due to human factors such as misuse, software errors, and virus intrusions. Once the business is interrupted, it will cause unpredictable losses to the enterprise. As a result, more and more companies are realizing the need to build their own disaster recovery sites to prevent unknown disasters.
  • the application data consistency refers to the application having The caching mechanism, so the data stored in the storage device is not the complete data for the application, and the data backup needs to ensure that the cached data for the application and the data on the storage device are backed up. Otherwise, in the event of a disaster, although the data has been backed up to the disaster recovery site, the backup data does not guarantee the consistency of the application data, which is very difficult or even unrecoverable for service recovery.
  • the database has a caching mechanism inside, part of the data in the database is written to the disk, and some of it is stored in its own cache space.
  • the database cache space after the system is out of plan.
  • the saved data will be lost, and only the data in the disk can be recovered. This will result in inconsistent data before the system is shut down and after the system is restarted, which may make the database service recovery difficult and even cause the database to fail to restart.
  • all the data in the database must be backed up to the disaster recovery site.
  • the data written to the disk and the data stored in the cache space are backed up to the disaster recovery site to ensure the consistency of the application data.
  • the self-built disaster recovery system needs to freeze the application IO before the data is backed up, and flush the dirty data cached in the application to the storage device to ensure the consistency of the application data and enable the service to be restored.
  • the technical principles of application data consistency backup for different applications are basically similar. As shown in Figure 1, the application that needs to perform data backup is a database, and the backup device that performs data backup is a storage array. The application data is described below with reference to Figure 1. Typical process of backup:
  • S101 The management server sends a startup data backup protection command to the host agent.
  • S102 The host agent notifies the database to submit the cached dirty data to the corresponding storage device and freezes the database IO.
  • Freezing the database IO means stopping the write operation to the database.
  • S103 The management server sends a startup data backup command to the storage array to perform data backup on each storage device that stores the database data.
  • the data can be backed up by remote replication, snapshot, clone, etc. of the storage array.
  • the storage array uses the backup mode for data backup, the state of the database needs to be judged, and it is determined that the dirty data has been submitted to the corresponding data.
  • the storage device freezes the database IO, the data backup for each storage device that holds the database data is started.
  • S105 The host agent notifies the database to restore the database IO.
  • Restoring the database IO restores the write operation to the database.
  • the above steps can ensure that the data backed up to the disaster recovery site meets the requirements of application data consistency, and the service can be restored when the data is used for service recovery.
  • the purpose of the embodiments of the present invention is to provide a data backup method and device, which solves the problem of high complexity when the backup device performs data backup for each application in the system.
  • a data backup method including:
  • the disk IO corresponding to each storage device is restored.
  • the backup device does not need to care about the specific backup pre-processing and backup post-processing of the upper-layer application, and only needs to connect to the host agent through the standard southbound interface, thereby reducing the backup complexity. , improve backup efficiency.
  • the application that needs to perform data backup is determined, including:
  • the backup pre-processing is to notify the application to store the cached dirty data to the corresponding storage device and/or to notify the application to process the transaction being executed.
  • the disk IO corresponding to each of the at least one storage device is frozen, include:
  • the received IO command for each storage device is discarded.
  • the embodiments of the present invention propose various ways of freezing the disk IO, which increases the flexibility of freezing the disk IO.
  • the method further includes:
  • the method further includes:
  • the data backup timer is cleared.
  • the data backup timer can freeze the disk IO for too long, which affects the system operation.
  • the method further includes:
  • the IO commands cached in the IO queue of each storage device are sequentially taken out and submitted to the corresponding storage device; or,
  • the method further includes:
  • the backup end notification message is used to notify the third-party system whether the data backup for the application is successful.
  • a data backup device includes:
  • a backup control module for determining an application that needs to perform data backup
  • An application driver module configured to determine at least one storage device that stores data of the application
  • a disk drive module configured to freeze a disk IO corresponding to each of the at least one storage device
  • a backup driver module configured to notify the backup device to perform a data backup for the storage device for each of the at least one storage device
  • the disk drive module is further configured to restore the disk IO corresponding to each storage device after determining that the backup device completes the data backup for the application.
  • the backup control module when determining an application that needs to perform data backup, is specifically configured to:
  • the backup control module is further configured to:
  • the application driving module is further used to
  • the backup pre-processing is to notify the application to store the cached dirty data to the corresponding storage device and/or notify the application to process the transaction being executed.
  • the disk drive module when the disk IO corresponding to each of the at least one storage device is frozen, the disk drive module is specifically configured to:
  • the received IO command for each storage device is discarded.
  • the disk drive module is further configured to:
  • the disk drive module is further configured to:
  • the data backup timer is cleared.
  • the disk drive module is further configured to:
  • the IO commands cached in the IO queue of each storage device are sequentially taken out and submitted to the corresponding storage device;
  • the backup control module is further configured to:
  • a backup end notification message is sent to the third-party system, and the backup end notification message is used to notify the third-party system whether the data backup for the application is successful.
  • an embodiment of the present invention provides a data backup device, including:
  • a memory for storing instructions
  • a processor coupled to the memory and the transceiver, for executing the instructions to perform the following steps when executing the instructions:
  • the disk IO corresponding to each storage device is restored.
  • the embodiment of the present invention provides a data backup method, the method includes: determining an application that needs to perform data backup, and storing at least one storage device of the application data; and freezing the disk IO corresponding to each storage device in the at least one storage device, To ensure that the application data is consistent; the backup device is configured to perform data backup for the application for each storage device in the at least one storage device, and the backup device does not need to care about the specific backup pre-processing and backup post-processing of the upper-layer application at this time, and only needs to pass
  • the standard southbound interface is connected to the host agent; after determining that the backup device completes the data backup for the application, the disk IO corresponding to each storage device is restored. Therefore, the backup complexity is reduced and the backup efficiency is improved.
  • FIG. 3 is a schematic structural diagram of a Host agent according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a data backup apparatus according to an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a data backup device according to an embodiment of the present invention.
  • an embodiment of the present invention provides a data backup method, including:
  • the Host agent determines an application that needs to perform data backup, and at least one storage device that stores data of the application.
  • the Host agent freezes the disk IO corresponding to each storage device in at least one storage device.
  • S220 The host agent notifies the backup device to perform data backup for the application for each of the at least one storage device.
  • the backup device here can be a storage array or a backup server.
  • the Host agent receives an application registration message sent by a third-party system, and the application registration message is used to indicate an application that needs to perform data backup.
  • the application registration message contains the database instance name and password.
  • the third party system here can be the management server in FIG.
  • the Host agent After the Host agent determines the application that needs to perform data backup, it begins to perform environment preparation for the application, that is, further determines at least one storage device that stores data of the application. For example, a database application has multiple types of data, and various types of data are stored in different storage devices.
  • the Host agent receives the third party before freezing the disk IO corresponding to each storage device in the at least one storage device.
  • a startup data backup message sent by the system the message is used to trigger the host agent to send an instruction to the storage device to perform data backup for the application.
  • the backup pre-processing is to notify the application to store the cached dirty data to the corresponding storage device and/or notify the application that the processing is being executed. Business.
  • the content of the backup pre-processing is different. Some applications only need to store the cached dirty data to the corresponding storage device. Some applications need to process the transaction being executed, including ending the currently executing transaction or waiting for the current The executed transaction is completed, etc.
  • the backup pre-processing here is triggered by the Host agent, and the backup device does not need to care about the backup pre-processing content of each application.
  • the host agent freezes the disk IO corresponding to each storage device in the at least one storage device, but is not limited to the following two methods:
  • the first way the host agent caches the received IO command for each storage device to the IO queue of the corresponding storage device.
  • the host agent After recovering the disk IO corresponding to each storage device in the above manner, the host agent sequentially takes out the IO commands cached in the IO queue of each storage device and submits them to the corresponding storage device.
  • the second way The host agent discards the received IO commands for each storage device.
  • the backup device when the backup device receives the data backup instruction for the application, the backup device backs up the data for the application to the disaster recovery site.
  • the backup device when the backup device is a storage array, the storage array can back up the data by remote copying tasks, or by creating snapshots, or by launching clones, or by specific backup software.
  • the Host agent After performing S220, that is, after notifying the backup device to perform data backup for the application for each of the at least one storage device, the Host agent starts a data backup timer.
  • the data backup timer is cleared.
  • the host agent determines that there is a storage device that does not complete the data backup for the application in at least one storage device, and then restores the disk IO corresponding to each storage device, so as to prevent the disk IO from being frozen for a long time to run on the system. Have an impact.
  • the Host agent after executing S230, notifies the application to perform backup post processing, and the backup post processing corresponds to the backup preprocessing.
  • the content of backup post-processing is different for different applications. For example, if the backup pre-processing performed by the application is to store the cached dirty data to the corresponding storage device, the backup post-processing is not required. If the backup pre-processing performed by the application is to block the commit transaction, the backup post-processing performed by the application is the resume transaction commit.
  • the host agent after recovering the disk IO corresponding to each storage device, the host agent sends a backup end notification message to the third-party system, and the backup end notification message is used to notify the third-party system whether the data backup for the application is successful.
  • the host agent is divided into four modules in FIG. 3, and the backup control module (BackupController) interfaces with a third-party system through a standard northbound interface, and is used for communication with a third-party system, and the application driver module is used.
  • the backup driver module (BackupDriver) for determining at least one storage device storing data of the application, and notifying each application to perform backup pre-processing (for example, notifying that OracleDriver and DB2Driver respectively perform backup pre-processing as shown in FIG. 4), disk drive module (DiskDriver) ) Used to freeze disk IO and recover disk IO.
  • the backup driver module (BackupDriver) is used to interface with the backup device through the standard southbound interface.
  • Figure 4 shows the specific process of data backup for Oracle and DB2, including:
  • S401 The third-party system sends an application registration message to the Host agent, where the password includes the application name of Oracle and Oracle and the passwords of the application names DB2 and DB2.
  • the third-party system registers the application message that needs to be backed up by the standard to the BackupController through the standard northbound interface.
  • the Host agent receives the application registration message, and determines, according to the application registration message, that the application that needs to perform data backup is Oracle and DB2.
  • the host agent prepares an application environment for the Oracle and the DB2, and determines at least one storage device corresponding to the Oracle and at least one storage device corresponding to the DB2.
  • the host agent obtains at least one storage device corresponding to Oracle from the Oracle according to the application registration message.
  • S404 The third-party system sends a startup data backup message to the host agent.
  • S405 The Host agent receives the startup data backup message, and notifies Oracle and DB2 to perform backup pre-processing.
  • Oracle needs to set the database to hot standby mode.
  • the host agent freezes the disk IO corresponding to each storage device in the at least one storage device corresponding to the Oracle device, and the disk IO corresponding to each storage device in the at least one storage device corresponding to the DB2.
  • DiskDriver DiskDriver
  • the host agent notifies the backup device to perform data backup for Oracle corresponding to at least one storage device corresponding to the Oracle, and notifies the backup device to perform data backup for the DB2 by using at least one storage device corresponding to the DB2.
  • BackupDriver notifies the backup device to perform data backup through the standard southbound interface, and does not need to care about the specific backup pre-processing and backup post-processing of the upper-layer application.
  • the backup device here is a storage array or a backup server.
  • the backup server performs data backup for Oracle for at least one storage device corresponding to Oracle, and performs data backup for DB2 for at least one storage device corresponding to DB2.
  • the host agent determines, when the data backup for Oracle is completed, restores the disk IO corresponding to each storage device in the at least one storage device corresponding to the Oracle, and determines that at least one storage device corresponding to the Oracle is restored when the data backup for the DB2 is completed. Disk IO corresponding to each storage device.
  • S411 The Host agent notifies the Oracle and DB2 data backups to complete.
  • S412 Oracle and DB2 perform backup post processing separately.
  • S413 The Host agent sends a backup end notification message to the third-party system to notify the third-party system that the data backup for Oracle and DB2 is successful.
  • the embodiment of the present invention further provides a data backup device, which includes the host agent in the embodiment shown in FIG. 2, which can be used to execute the method embodiment corresponding to FIG. 2, and thus the present invention is implemented.
  • a data backup device which includes the host agent in the embodiment shown in FIG. 2, which can be used to execute the method embodiment corresponding to FIG. 2, and thus the present invention is implemented.
  • the data backup device provided in the example, refer to the implementation manner of the method, and the repeated description is not repeated.
  • an embodiment of the present invention provides a data backup device 50, including:
  • the backup control module 51 is configured to determine an application that needs to perform data backup
  • An application driver module 52 configured to determine at least one storage device that stores data of the application
  • the disk drive module 53 is configured to freeze the disk IO corresponding to each of the at least one storage device
  • the backup driver module 54 is configured to notify the backup device to perform data backup for the storage device for each of the at least one storage device;
  • the disk drive module 53 is further configured to restore the disk IO corresponding to each storage device after determining that the backup device completes the data backup for the application.
  • the backup control module 51 when determining an application that needs to perform data backup, is specifically configured to:
  • the backup control module 51 is further configured to:
  • the application driving module 52 is further used to
  • the backup pre-processing is to notify the application to store the cached dirty data to the corresponding storage device and/or notify the application to process the transaction being executed.
  • the disk drive module 53 when the disk IO corresponding to each of the at least one storage device is frozen, the disk drive module 53 is specifically configured to:
  • the received IO command for each storage device is discarded.
  • the disk drive module 53 is further configured to:
  • the disk drive module 53 is further configured to:
  • the data backup timer is cleared.
  • the disk drive module 53 is further configured to:
  • the IO commands cached in the IO queue of each storage device are sequentially taken out and submitted to the corresponding storage device;
  • the backup control module 51 is further configured to:
  • a backup end notification message is sent to the third-party system, and the backup end notification message is used to notify the third-party system whether the data backup for the application is successful.
  • the data backup device is also provided in the embodiment of the present invention, and the device can be used to perform the method embodiment corresponding to the foregoing FIG. 2, and therefore, the implementation manner of the data backup device provided by the embodiment of the present invention can be referred to The implementation of the method, the repetition will not be repeated.
  • an embodiment of the present invention provides a data backup device, including:
  • a memory 62 for storing instructions
  • the processor 63 is respectively connected to the memory 62 and the transceiver 61 for executing the instructions to perform the following steps when executing the instructions:
  • the disk IO corresponding to each storage device is restored.
  • connection manner between the parts shown in FIG. 6 is only one possible example. It may also be that the transceiver 61 and the memory 63 are both connected to the processor 62, and between the transceiver 61 and the memory 63. There is no connection, or it can be other possible connections.
  • the host agent ensures the application data consistency by freezing the disk IO mode, and the backup device only needs to connect to the host agent through the standard southbound interface. Pay attention to the specific backup pre-processing and backup post-processing of the upper application, which reduces the backup complexity and improves the backup efficiency.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

L'invention concerne un procédé et un appareil de sauvegarde de données. Le procédé comprend les étapes consistant à : déterminer une application nécessitant une sauvegarde de données et déterminer au moins un dispositif de stockage qui stocke les données de l'application (S200) ; figer les E/S de disque correspondant à chacun desdits au moins un dispositif de stockage (S210) ; pour chacun desdits au moins un dispositif de stockage, ordonner à un dispositif de sauvegarde d'effectuer une sauvegarde de données pour l'application (S220) ; et après avoir déterminé que le dispositif de sauvegarde a terminé la sauvegarde de données pour l'application, restaurer les E/S de disque correspondant à chaque dispositif de stockage (S230). Dans la présente invention, un agent hôte assure la cohérence des données d'application en figeant les E/S de disque. Il suffit d'interfacer le dispositif de sauvegarde avec l'agent hôte par l'intermédiaire d'une interface sud standard, et le dispositif de sauvegarde n'a pas besoin d'effectuer d'actions de pré-traitement de sauvegarde et de post-traitement de sauvegarde particulières pour une application de couche supérieure, ce qui réduit la complexité et améliore l'efficacité de la sauvegarde de données.
PCT/CN2017/075489 2016-06-06 2017-03-02 Procédé et appareil de sauvegarde de données WO2017211099A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610394932.8A CN106055433B (zh) 2016-06-06 2016-06-06 一种数据备份方法及装置
CN201610394932.8 2016-06-06

Publications (1)

Publication Number Publication Date
WO2017211099A1 true WO2017211099A1 (fr) 2017-12-14

Family

ID=57170537

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/075489 WO2017211099A1 (fr) 2016-06-06 2017-03-02 Procédé et appareil de sauvegarde de données

Country Status (2)

Country Link
CN (1) CN106055433B (fr)
WO (1) WO2017211099A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109284205A (zh) * 2018-09-21 2019-01-29 平安科技(深圳)有限公司 快照备份方法、装置、计算机设备及存储介质
CN109376033A (zh) * 2018-09-21 2019-02-22 平安科技(深圳)有限公司 快照备份方法、装置、计算机设备及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106055433B (zh) * 2016-06-06 2019-02-26 华为技术有限公司 一种数据备份方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1873622A (zh) * 2006-04-20 2006-12-06 北京艾德斯科技有限公司 San环境下数据备份、复制和恢复的方法及其装置
CN101256528A (zh) * 2008-03-20 2008-09-03 中国科学院计算技术研究所 支持零备份窗口的磁盘级数据备份系统和方法
CN101414277A (zh) * 2008-11-06 2009-04-22 清华大学 一种基于虚拟机的按需增量恢复容灾系统及方法
CN102402471A (zh) * 2011-12-23 2012-04-04 创新科软件技术(深圳)有限公司 基于存储阵列快照功能的数据实时备份方法及系统
CN106055433A (zh) * 2016-06-06 2016-10-26 华为技术有限公司 一种数据备份方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7844577B2 (en) * 2002-07-15 2010-11-30 Symantec Corporation System and method for maintaining a backup storage system for a computer system
US8930527B2 (en) * 2009-05-26 2015-01-06 Oracle International Corporation High availability enabler
JP5521816B2 (ja) * 2010-06-18 2014-06-18 富士通株式会社 記憶装置、制御装置および記憶装置の制御方法
US9317375B1 (en) * 2012-03-30 2016-04-19 Lenovoemc Limited Managing cache backup and restore for continuous data replication and protection
US9276838B2 (en) * 2012-10-05 2016-03-01 Futurewei Technologies, Inc. Software defined network virtualization utilizing service specific topology abstraction and interface
JP6452834B2 (ja) * 2014-11-06 2019-01-16 華為技術有限公司Huawei Technologies Co.,Ltd. 情報送信方法、管理対象システム、および管理システム

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1873622A (zh) * 2006-04-20 2006-12-06 北京艾德斯科技有限公司 San环境下数据备份、复制和恢复的方法及其装置
CN101256528A (zh) * 2008-03-20 2008-09-03 中国科学院计算技术研究所 支持零备份窗口的磁盘级数据备份系统和方法
CN101414277A (zh) * 2008-11-06 2009-04-22 清华大学 一种基于虚拟机的按需增量恢复容灾系统及方法
CN102402471A (zh) * 2011-12-23 2012-04-04 创新科软件技术(深圳)有限公司 基于存储阵列快照功能的数据实时备份方法及系统
CN106055433A (zh) * 2016-06-06 2016-10-26 华为技术有限公司 一种数据备份方法及装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109284205A (zh) * 2018-09-21 2019-01-29 平安科技(深圳)有限公司 快照备份方法、装置、计算机设备及存储介质
CN109376033A (zh) * 2018-09-21 2019-02-22 平安科技(深圳)有限公司 快照备份方法、装置、计算机设备及存储介质
CN109284205B (zh) * 2018-09-21 2023-04-07 平安科技(深圳)有限公司 快照备份方法、装置、计算机设备及存储介质
CN109376033B (zh) * 2018-09-21 2023-04-07 平安科技(深圳)有限公司 快照备份方法、装置、计算机设备及存储介质

Also Published As

Publication number Publication date
CN106055433B (zh) 2019-02-26
CN106055433A (zh) 2016-10-26

Similar Documents

Publication Publication Date Title
US11243847B2 (en) Managing remote data replication
US11068370B2 (en) Systems and methods for instantiation of virtual machines from backups
US7594138B2 (en) System and method of error recovery for backup applications
US8788768B2 (en) Maintaining mirror and storage system copies of volumes at multiple remote sites
US8566281B2 (en) Method for implementing multi-array consistency groups using a write queuing mechanism
US9940067B2 (en) Performing a data write on a storage device
US9563655B2 (en) Zero and near-zero data loss database backup and recovery
US8874508B1 (en) Systems and methods for enabling database disaster recovery using replicated volumes
US8407435B2 (en) Efficiently creating a snapshot of a large consistency group using multiple commands including a snapshot preparation command
WO2017211099A1 (fr) Procédé et appareil de sauvegarde de données
WO2012059393A1 (fr) Récupération à distance à points de contrôle et journaux d'intention
US20140201149A1 (en) Consistent bookmark
US20240095021A1 (en) Quiescent operation of non-disruptive update of a data management system
CN112486729A (zh) 基于非易失性存储器的操作验证的安全数据提交扫描的调整

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17809540

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17809540

Country of ref document: EP

Kind code of ref document: A1