CN110109777A - A kind of VM incremental backup method realized in the case of CBT corrupted data - Google Patents
A kind of VM incremental backup method realized in the case of CBT corrupted data Download PDFInfo
- Publication number
- CN110109777A CN110109777A CN201910588179.XA CN201910588179A CN110109777A CN 110109777 A CN110109777 A CN 110109777A CN 201910588179 A CN201910588179 A CN 201910588179A CN 110109777 A CN110109777 A CN 110109777A
- Authority
- CN
- China
- Prior art keywords
- backup
- disk
- cbt
- data
- virtual machine
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/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
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45587—Isolation or security of virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Techniques For Improving Reliability Of Storages (AREA)
Abstract
The invention discloses the VM incremental backup methods in the case of realization CBT corrupted data, including step b1: when getting disk CBT abnormality, when full backup, changeID parameter is " * ", all Significant Change blocks for working as front disk are obtained, are directly purchased size by vSphereSDK acquisition current backup disk；Step b2: purchasing size according to magnetic disk of virtual machine, read entire disk sector, back up all sector datas, generates one in backup storage and purchases virtual disk files vmdk1 of the same size with magnetic disk of virtual machine；Virtual machine may have multiple disks, then generate multiple backup disk files, and record changeID caused by the snapshot of full backup at this time；Step b3: the data in magnetic disk since being obtained from Last Backup according to the recorded changeID of Last Backup changes block, carries out increment synthetic backup；Step b4: lasting incremental backup repeats step b3.Compared with prior art, it in disk CBT corrupted data, does not need to shut down resetting CBT, can realize lasting full dose, incremental backup according to the backup strategy being previously set.
Description
Technical field
The invention belongs to computer virtualized technology field, in particular to a kind of VM realized in the case of CBT corrupted data
Incremental backup method.
Background technique
Currently, with the increasingly maturation of virtualization technology, more and more enterprises and organization all will be using deployment
On the virtual machine of virtual platform, such as the vSphere virtual platform of VMware company, then how to protect these deployment
Application data on virtual platform are just at one of most concerned problem of these enterprises and organization.
Market is backed up in order to cater to so huge virtual-machine data, and many backup software manufacturers all realize pair in succession
The backup and recovery function of the virtual machine of vSphere virtual platform.But how to be realized as third-party software vendor
The backup of vSphere virtual machine and restore function, convenient feasible method be exactly call directly VMware company exclusively for
The backup of vSphere virtual machine and a set of VDDK interface that offer is provided (for vSphere4.0 and later version).
The principle for restoring VMware virtual machine by VADP interface is as follows: when full backup VMware virtual machine,
It needs, according to vSphereSDK interface queryChangedDiskAreas, to obtain for needing the virtual machine backed up to do a snapshot
The valid data block for needing to back up is got, and generates the changeID of a current full backup.When full backup success, note
The changeID of current full backup under record has been arrived since full backup by the way that the changeID is available, virtually next time
Machine is all to generate the data block changed, i.e. incremental data, incremental data can be synthesized to full backup number by certain mode
In.Each incremental backup can also generate a changeID, next incremental backup according to the changeID of last time incremental backup,
The later virtual machine delta data library of last time incremental backup can be only obtained from.And so on, complete for after from for the first time, it can begin
Incremental backup and synthetic operation are carried out, eventually to reduce client's production environment server stress.
Due to backup software manufacturer call be VMware company provide vSphere interface, then backup software manufacturer
It is restricted based on some functions that vSphere interface is realized also nature because of vSphere interface the reason of itself.In certain feelings
Under condition, cbt data can damage (such as situations such as abnormal power-down), when causing full backup, queryChangedDiskAreas
Interface is obtained less than effective Backup Data block.Cause full backup that can not carry out, subsequent incremental backup can not also be based on full dose
Backup carries out.(it is VMware that VMware data block, which modifies tracking technique (Changed Block Tracking, CBT),
VStorageAPI for Data Protection(VADP) important component, be VMware simplified and improve Vmware
Make great efforts achievement in the part of virtual machine backup efficiency.)
Traditional magnetic disk CBT abnormal problem, the resetting solution provided according to VM manufacturer need interrupting service, shut down setting, generation
Valence is larger, specific steps a1: closing the virtual machine for needing to back up；Step a2: choosing virtual machine, and right click [edits setting],
Pop up and select [option] button in dialog box, then select [routine] option, then click [configuration parameter], by the attribute of ctk by
True is changed to false(it is noted here that all xxxxxx.ctkEnabled will be changed to false, and might have more here
It is a), then click [determination]；Step a3: virtual machine is opened；Step a4: it into the file of virtual machine storage data, deletes
Except *-ctk.vmdk file；Step a5: virtual machine is closed；Step a6: according to top-operation 3 again by ctk attribute by false
It is changed to true；Step a7: virtual machine is opened, then just can be carried out backup.If but not shutting down resetting, it can not just pass through factory
Quotient VADP solution obtains Backup Data, can not back up to outgoing interface.
Summary of the invention
Goal of the invention: the present invention in view of the problems of the existing technology, provide it is a kind of realize CBT corrupted data in the case of
VM incremental backup method.
Technical solution: to achieve the above object, realize that the VM in the case of CBT corrupted data continues the present invention provides a kind of
Incremental backup method, comprising the following steps:
Step b1: when getting disk CBT abnormality, (when full backup, changeID parameter is " * ", obtains current magnetic
All Significant Change blocks of disk), directly purchased size by vSphereSDK acquisition current backup disk；VM manufacturer provides standby
Part scheme interface；
Step b2: it purchases size according to magnetic disk of virtual machine, reads entire disk sector, back up all sector datas, deposited in backup
Storage generates one and purchases virtual disk files vmdk1 of the same size with magnetic disk of virtual machine；Virtual machine may have multiple disks, then
Multiple backup disk files are generated, and record changeID caused by the snapshot of full backup at this time;
Step b3: the data in magnetic disk since being obtained from Last Backup according to the recorded changeID of Last Backup changes block, carries out
Incremental backup;(the VADP backup scenario that VM manufacturer releases, vSphere are originated from 4.1 versions, are based on CBT technology, support increment
Backup, backs up for the first time, backs up entire disk, only backs up the data block changed based on Last Backup every time later.)
Specific method is to find Last Backup virtual disk files vmdk1 in backup storage, is obtained from last time according to changeID
Since backup, virtual machine generates the data block of variation and the initial sector position of these data blocks.According to these data blocks
Data block (i.e. delta file) covering of variation is written in file vmdk1, obtained backup file by initial sector position,
The incremental data that Backup Data and Last Backup before then including are generated to the time between this backup.
Step b4: lasting incremental backup repeats step b3.
The utility model has the advantages that compared with prior art, in disk CBT corrupted data, do not need to shut down resetting CBT, it can
To realize lasting full dose, incremental backup according to the backup strategy being previously set.
Detailed description of the invention
Fig. 1 is a large amount of small data file backup flow charts provided by the invention.
Specific embodiment
Further explanation is done to the present invention with reference to the accompanying drawing.
Show in conjunction with such as Fig. 1, a kind of method improving a large amount of small data file backup efficiency provided by the invention, including following
Step:
A kind of VM incremental backup method realized in the case of CBT corrupted data, comprising the following steps:
Step b1: when getting disk CBT abnormality, when full backup, changeID parameter is " * ", obtains current magnetic
All Significant Change blocks of disk are directly purchased size by vSphereSDK acquisition current backup disk；
CBT abnormal state is generally caused by reasons such as abnormal power-downs, and it is as follows that vSphere interface obtains data block information error information
It is shown: Error caused by file/xxxx/xxxxx/xxxx.vmdk. at this time normally backup process can not continue it is standby
Part, according to the scheme that virtual manufacturer provides, needs to shut down resetting virtual machine setting, then carry out a full backup, it later can be into
Row incremental backup；
Step b2: generating the mistake when if it is incremental backup, leads to backup failure, and backing up herein will to switch to full dose standby automatically
Part.This programme will acquire disk and purchase size, directly from 0 sector initial position, read until the last one sector terminates, standby
The entire disk file of part, and record the changeID of this time backup.(difference for being different from original vendor scheme is, does not pass through
Step b1 obtains valid data block, then will not proceed to 1 step, and causing to report an error causes backup to be interrupted.)
Step b3: the newest changeID according to obtained in step b2, it reuses vSphere interface and is obtained from step 2 backup
To come the current time, the data block of produced variation, and the data block of variation is synthesized in the file of last backup, because
Backup for step 2 is effective, the delta data block between changeID recording step b2 to step b3 of generation, the number
According to be it is effective, step 1 mistake will not be caused, lead to backup failure.
Step b4: lasting incremental backup repeats step b3.
The above is only a preferred embodiment of the present invention, it should be pointed out that: for the ordinary skill people of the art
For member, various improvements and modifications may be made without departing from the principle of the present invention, these improvements and modifications are also answered
It is considered as protection scope of the present invention.
Claims (2)
1. a kind of VM incremental backup method realized in the case of CBT corrupted data, is essentially characterized in that: including following step
It is rapid:
Step b1: when getting disk CBT abnormality, when full backup, changeID parameter is " * ", obtains current magnetic
All Significant Change blocks of disk are directly purchased size by vSphereSDK acquisition current backup disk；
Step b2: it purchases size according to magnetic disk of virtual machine, reads entire disk sector, back up all sector datas, deposited in backup
Storage generates one and purchases virtual disk files vmdk1 of the same size with magnetic disk of virtual machine；When virtual machine there are multiple disks, then give birth to
At multiple backup disk files, and record changeID caused by the snapshot of full backup at this time；
Step b3: the data in magnetic disk since being obtained from Last Backup according to the recorded changeID of Last Backup changes block, carries out
Increment synthetic backup；
Step b4: lasting incremental backup repeats step b3.
2. a kind of VM incremental backup method based in the case of realization CBT corrupted data described in claim 1, basic
Be characterized in that: the step b3 specific method is to find Last Backup virtual disk files vmdk1 in backup storage, according to
Since changeID is obtained from Last Backup, virtual machine generates the data block of variation and the initial sector position of these data blocks
It sets, according to the initial sector position of these data blocks, the data block covering of variation is written in file vmdk1, what is obtained is standby
Part file, the then incremental data that Backup Data and Last Backup before including are generated to the time between this backup.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910588179.XA CN110109777A (en) | 2019-07-02 | 2019-07-02 | A kind of VM incremental backup method realized in the case of CBT corrupted data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910588179.XA CN110109777A (en) | 2019-07-02 | 2019-07-02 | A kind of VM incremental backup method realized in the case of CBT corrupted data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110109777A true CN110109777A (en) | 2019-08-09 |
Family
ID=67495953
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910588179.XA Pending CN110109777A (en) | 2019-07-02 | 2019-07-02 | A kind of VM incremental backup method realized in the case of CBT corrupted data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110109777A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112882859A (en) * | 2021-02-07 | 2021-06-01 | 上海英方软件股份有限公司 | Virtual machine synthetic backup method and system |
| CN114780299A (en) * | 2022-06-17 | 2022-07-22 | 南京云信达科技有限公司 | BMR backup system and method based on disk CBT |
| CN115344423A (en) * | 2022-08-01 | 2022-11-15 | 和元达信息科技有限公司 | Backup method, mount recovery method, server and computer-readable storage medium |
| CN116560914A (en) * | 2023-07-10 | 2023-08-08 | 成都云祺科技有限公司 | Incremental backup method, system and storage medium under virtual machine CBT failure |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103034566A (en) * | 2012-12-06 | 2013-04-10 | 华为技术有限公司 | Method and device for restoring virtual machine |
| CN104461783A (en) * | 2014-12-10 | 2015-03-25 | 上海爱数软件有限公司 | Virtual machine backup method by tracking sector data change |
| US20160070623A1 (en) * | 2014-09-04 | 2016-03-10 | International Business Machines Corporation | Hypervisor agnostic interchangeable backup recovery and file level recovery from virtual disks |
| CN107025149A (en) * | 2017-03-04 | 2017-08-08 | 郑州云海信息技术有限公司 | Virtual machine backup/restoration system and method |
| CN107133131A (en) * | 2017-05-31 | 2017-09-05 | 广州鼎甲计算机科技有限公司 | A kind of virtual machine synthesized backup method based on VMware |
-
2019
- 2019-07-02 CN CN201910588179.XA patent/CN110109777A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103034566A (en) * | 2012-12-06 | 2013-04-10 | 华为技术有限公司 | Method and device for restoring virtual machine |
| US20160070623A1 (en) * | 2014-09-04 | 2016-03-10 | International Business Machines Corporation | Hypervisor agnostic interchangeable backup recovery and file level recovery from virtual disks |
| CN104461783A (en) * | 2014-12-10 | 2015-03-25 | 上海爱数软件有限公司 | Virtual machine backup method by tracking sector data change |
| CN107025149A (en) * | 2017-03-04 | 2017-08-08 | 郑州云海信息技术有限公司 | Virtual machine backup/restoration system and method |
| CN107133131A (en) * | 2017-05-31 | 2017-09-05 | 广州鼎甲计算机科技有限公司 | A kind of virtual machine synthesized backup method based on VMware |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112882859A (en) * | 2021-02-07 | 2021-06-01 | 上海英方软件股份有限公司 | Virtual machine synthetic backup method and system |
| CN114780299A (en) * | 2022-06-17 | 2022-07-22 | 南京云信达科技有限公司 | BMR backup system and method based on disk CBT |
| CN115344423A (en) * | 2022-08-01 | 2022-11-15 | 和元达信息科技有限公司 | Backup method, mount recovery method, server and computer-readable storage medium |
| CN115344423B (en) * | 2022-08-01 | 2023-07-04 | 和元达信息科技有限公司 | Backup method, mount recovery method, server, and computer-readable storage medium |
| CN116560914A (en) * | 2023-07-10 | 2023-08-08 | 成都云祺科技有限公司 | Incremental backup method, system and storage medium under virtual machine CBT failure |
| CN116560914B (en) * | 2023-07-10 | 2023-10-13 | 成都云祺科技有限公司 | Incremental backup method, system and storage medium under virtual machine CBT failure |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110109777A (en) | A kind of VM incremental backup method realized in the case of CBT corrupted data | |
| US10210073B1 (en) | Real time debugging of production replicated data with data obfuscation in a storage system | |
| US8468501B2 (en) | Partial recording of a computer program execution for replay | |
| US8117168B1 (en) | Methods and systems for creating and managing backups using virtual disks | |
| US8510271B1 (en) | Application and file system data virtualization from image backup | |
| US9348827B1 (en) | File-based snapshots for block-based backups | |
| US7669020B1 (en) | Host-based backup for virtual machines | |
| US4748561A (en) | Method of protecting computer software | |
| US10235252B1 (en) | Retroactive log retrieval service | |
| CN103019890B (en) | Block-level disk data protection system and method thereof | |
| US20080307019A1 (en) | Manipulating Electronic Backups | |
| US20120131456A1 (en) | Capture and Playback for GUI-Based Tasks | |
| CN106951345A (en) | A kind of conformance test method and device of magnetic disk of virtual machine data | |
| CN106062742A (en) | Systems and methods for improving snapshot performance | |
| CN101770410A (en) | System restore method, virtual machine managing device and system based on client operating system | |
| CN110187998A (en) | The application disaster tolerance system and method stored based on virtual platform and ceph | |
| US20190243725A1 (en) | Protection of infrastructure-as-a-service workloads in public cloud | |
| US20120246628A1 (en) | Firmware updating system and method | |
| CN103761168B (en) | It is a kind of that the method for carrying backup virtual machine is wrapping with based on nfs | |
| CN104102556A (en) | Disk data backup and recovering method of virtual machine | |
| US20130110785A1 (en) | System and method for backing up test data | |
| CN114245892A (en) | Data race analysis based on altering function internal loading during time travel debugging | |
| JP2007141231A (en) | Method, system and computer program for data backup | |
| CN106126427A (en) | A kind of method and system of fast quick-recovery test | |
| CN108804257A (en) | SOT state of termination detection method, device, terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190809 |
|
| RJ01 | Rejection of invention patent application after publication |