CN109992449A - Backup image management system, method, equipment and medium - Google Patents
Backup image management system, method, equipment and medium Download PDFInfo
- Publication number
- CN109992449A CN109992449A CN201711494862.4A CN201711494862A CN109992449A CN 109992449 A CN109992449 A CN 109992449A CN 201711494862 A CN201711494862 A CN 201711494862A CN 109992449 A CN109992449 A CN 109992449A
- Authority
- CN
- China
- Prior art keywords
- kickboard
- backup
- image file
- file
- backup image
- 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.)
- Granted
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
-
- 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/1479—Generic software techniques for error detection or fault masking
- G06F11/1482—Generic software techniques for error detection or fault masking by means of middleware or OS functionality
- G06F11/1484—Generic software techniques for error detection or fault masking by means of middleware or OS functionality involving virtual machines
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention proposes backup image management system, method, equipment and the media of starting virtual machine not recovered after a kind of backup.More parts of backup images of virtual machine by being put into dedicated emergency recovery platform by the system, after virtual machine breaks down, it is directly mounted to virtualized server by the virtual machine backup image that dedicated emergency restores platform, the virtual machine backup image that dedicated emergency restores platform is redirected to by virtualized server storage, then virtual machine is created, open virtual machine, to achieve the purpose that emergency recovery starts virtual machine in a short time, use tradition than relatively time-consuming recovery process after avoiding failure, the reliability of virtual platform is ensured, availability and continuity.The speed that this method " can find " multiple historical time copies of virtual machine and restore than tradition greatly promotes, and physical error can only be repaired, cannot repair the problem of logic error and recovery time by overcoming backup in the prior art.
Description
Technical field
The invention belongs to starting virtual machines not recovered after data backup restoration technical field more particularly to a kind of backup
Backup image management system, method, equipment and medium.
Background technique
Under the form that IT cost is continuously improved, virtualization more attracts people's attention because of its advantage with save the cost.
It is universal with server virtualization technology, not only increase the resource utilization of data center, reduce the consumption of the energy, also for
Data administrator brings efficient and convenient management experience.
Server virtualization is that system virtualization is applied on server, can be by a server virtual at multiple void
Quasi- server carry out using.More and more important service systems are deployed to virtual platform now, so virtual platform
Reliability, availability be directly related to the continuity of business.
There are two main classes for current guarantee virtual platform reliability, availability and successional technological means: first is that logical
Cross virtual platform High Availabitity guaranteeing business continuity.When separate unit VME operating system or host's physical host of virtual machine
When failure, virtual machine moves to B physical host by A physical host switching at runtime.It is equivalent to traditional Two-channel switching.If it is across
In the case where website, virtual machine is with by A being switched to B.This means it is more efficient ensure business continuance, can very quickly
Completion switching, can be completed probably within a few minutes switch.Its Shortcomings is can only to repair physical error, Bu Nengxiu
Multiple logic error.When VME operating system or virtual machine host's physical host failure, virtual function is completed to automatically switch,
But the logic error done inside VME operating system, such as: file is accidentally deleted, the appearance such as leaky patch has been stamped
When, even if it is manual virtual machine is moved to B physical host by A physical host switching at runtime it is of no avail because this
It covers " two-shipper " and uses shared disk.Second is that ensuring the continuity of business by the means of Backup and Restore.Pass through various backup softwares
Virtual machine is backed up to disk, and when physical fault or logic error occurs in virtual machine, we pass through standby perhaps tape
Part software restores previous virtual machine backup, to ensure the continuity of business.Because there is the standby of multiple timing nodes
Part, it is possible to multiple logical nodes are restored to, logic error can be effectively repaired.Its Shortcomings is, because using passing
The Backup and Restore means of system, recovery time are centainly greater than BACKUP TIME.Usual recovery time is equal to or more than the 1.2 of BACKUP TIME
Times.That is if one VME operating system of backup spends a hour, the time restored is at least more than being equal to
1.2 hours.Business continuance compares the first means and has a greatly reduced quality on Saving in time costs.
In conclusion the Backup and Restore time longer technical problem of fictitious host computer exists in the prior art.
Summary of the invention
In order to overcome prior art disadvantage, the present invention provides a kind of backup image of not recovered starting virtual machine after backup
Management system, method, equipment and medium.By the way that more parts of backup images of virtual machine are put into dedicated emergency recovery platform.When
After virtual machine breaks down, directly mounted by the virtual machine backup image that dedicated emergency restores platform to virtualized server, by
Virtualized server storage is redirected to the virtual machine backup image that dedicated emergency restores platform, then creates virtual machine, opens
Virtual machine.To achieve the purpose that emergency recovery starts virtual machine in a short time.It avoids after breaking down using traditional
Than relatively time-consuming recovery process.This method " can find " multiple historical time copies of virtual machine and restore than tradition
Speed greatly promote.
The technical solution adopted by the invention is as follows:
In a first aspect, the embodiment of the invention provides a kind of backup image management of starting virtual machine not recovered after backup
System, it is characterised in that: the system operates on emergency recovery platform, including memory space division module, backup storage ginseng
Several and kickboard rule setting module, kickboard management module, virtual machine backup module, backup image writing module and backup virtual machine
Emergency starting module, wherein
Memory space division module, for the memory space of the emergency recovery platform to be divided into caching and kickboard two
Point；
Backup storage parameter and kickboard rule setting module restore region for the setting of backup image write sequence, kickboard
It divides, backup strategy setting, kickboard rule setting, and checks that backup image retains situation；
Kickboard management module, for updating kickboard rule, kickboard record file and kickboard inspection and kickboard access；
Virtual machine backup module generates snapshot in backup, to store for the snapshot interface using virtualization
The stamper file of the data being newly written, virtual machine remains unchanged, and snapshot is executed after the completion of backup and is deleted, the data in snapshot are returned
It is written in stamper file；
Backup image writing module, for the emergency recovery platform will to be transferred in the backup image file of virtual machine,
The emergency recovery platform is controlled caching is written in backup image file and judges backup image file according to the kickboard rule
Storage；
Backup virtual machine emergency starting module utilizes the institute, emergency recovery area in kickboard when breaking down for virtual machine
Virtual machine is directly opened to exist side by side by the nearest backup image file retained to be used；
The emergency recovery platform draws the memory space on emergency recovery platform using memory space division module
Point, the emergency recovery platform generates virtual machine snapshot using virtual machine backup module；The emergency recovery platform utilizes backup
Memory space is written in the snapshot that mirror image writing module generates virtual machine backup module；It is described to answer when virtual machine breaks down
Anxious recovery platform is straight the nearest backup image file retained in memory space by backup virtual machine emergency starting module
It takes out and uses.
Further, the backup storage parameter and kickboard rule setting module specifically include:
Submodule is written in backup image: spatial cache is preferentially written in the backup image file for being arranged all；
Kickboard divides submodule: big without dividing space for kickboard to be divided into emergency recovery area, traditional recovery district
It is small；
Submodule is arranged in backup strategy: for backup image file or backup image file group to be included in different backup plans
Slightly, different backup image frequency of your backups and retention periods is arranged in different backup strategies；
Kickboard rule setting submodule, for each backup image text in limitation emergency recovery area respectively, traditional recovery district
Part or backup image file group the space occupied size and reservation number, emergency recovery area only retains backup image several times recently
File, history backup image file will be migrated into traditional recovery district, Free up Memory after backup image file expiration, be returned to floating
Plate；
Backup image file checking submodule: the reservation whether each backup image file has reached requirement is inspected periodically
Time removes expired backup image file if having expired.
Further, the kickboard management module, specifically includes:
Backup implementation sub-module: virtualization backup procedure is executed for realizing backup management system；
Backup image file judging submodule: for judging the size of backup image file and cache residual space: if standby
Part image file is less than or equal to cache remaining size, then caching is written in backup image file, otherwise, waited in line；
Backup image file cache submodule: it is cached for backup image file to be written；
Kickboard judging submodule: for being judged according to backup storage parameter and kickboard rule, if kickboard records file
The backup image file number COPY2 retained in the emergency recovery area of middle record is less than or equal to defined in kickboard rule file
The backup image file number COPY1 that should retain in emergency recovery area, and the emergency recovery area recorded in kickboard record file is
Occupied space size SIZE2 be less than or equal to kickboard rule file defined in emergency recovery area can occupied space size SIZE1, then
Continue for kickboard Spatial Residual size to be compared with backup image file size in caching, if backup image file is big in caching
It is small to be less than or equal to kickboard remaining space size, then from the kickboard space for marking backup image size in caching in kickboard space, hand over
Emergency recovery area is given, and emergency recovery area is written into the backup image file in caching, if the backup image file in caching is big
It is small to be greater than kickboard remaining space size, it indicates that kickboard remaining space is insufficient, then alerts insufficient space；
If COPY2≤COPY1 and SIZE2≤SIZE1 have any one it is invalid, by the oldest mirror image in emergency recovery area text
Part is migrated to traditional recovery district, is judged according to backup storage parameter and kickboard rule, if recorded in kickboard record file
It is answered in tradition recovery district defined in the backup image file number COPY4≤kickboard rule file retained in traditional recovery district
The backup image file number COPY3 of reservation, and kickboard records the traditional recovery district recorded in file occupied space size
Tradition recovery district defined in SIZE4≤kickboard rule file can occupied space size SIZE3 set up simultaneously, then by kickboard residue
Space size is compared with the oldest mirror image size in emergency recovery area, if the oldest mirror image size in emergency recovery area is less than or equal to kickboard
Remaining space size then carries out the division of kickboard space, and the kickboard of the oldest mirror image size in emergency recovery area is marked from kickboard space
Space gives and answers the multiple area of tradition, and the oldest image file in emergency recovery area is migrated traditional recovery district into kickboard, and
Free up Memory alerts insufficient space if kickboard remaining space is insufficient to the emergency recovery area of kickboard；
If COPY4≤COPY3, SIZE4≤SIZE3 has that any bar is invalid, then alerts retention periods limitation；
Mirror transference submodule: for marking off the space of the oldest image file size in emergency recovery area from kickboard space
Traditional recovery district is given, and the oldest image file in emergency recovery area is migrated into traditional recovery district into kickboard, and discharge
Space to kickboard space；
Kickboard space size judging submodule: for carrying out image file size in kickboard remaining space size and caching
Compare, if image file size is less than or equal to kickboard remaining space size in caching, mirror image in caching is marked off in kickboard
Give emergency recovery area in the space of size；
Submodule is written in image file: emergency recovery area is written for the image file in caching.
Further, backup virtual machine emergency starting module is specifically used in the system:
Backup image file needed for positioning, by the backup image file with Network File System NFS read-only mode carry
On virtualized server into the emergency recovery platform to match with backup source, so that the backup image file is virtual as this
Change the NFS data source of server；
Using the snapshot mechanism of virtualization, snapshot is created in production inventory, namely restores log, to store new write-in
Data, and the backup image file in emergency recovery platform is remained unchanged as the stamper file of virtual machine, i.e., openable void
Quasi- machine.
Second aspect, the embodiment of the invention provides a kind of backup image management of starting virtual machine not recovered after backup
Method, which comprises the following steps:
(1) memory space of entire emergency recovery platform is divided into caching and kickboard two parts；
(2) backup image write sequence is set, divides kickboard recovery region, setting backup strategy, setting kickboard rule；
And check that backup image retains situation；
(3) more new management kickboard rule file, kickboard record file and kickboard inspection and kickboard access；
(4) using the snapshot interface of virtualization, snapshot is generated in backup, to store the data being newly written, and
The stamper file of virtual machine remains unchanged, and snapshot is executed after the completion of backup and is deleted, the write back data in snapshot is entered stamper file
In；
(5) it will be transferred to the emergency recovery platform in the backup image file of virtual machine, it is flat controls the emergency recovery
Backup image file is written platform caches and judges how backup image file stores according to kickboard rule；
(6) when virtual machine breaks down, the nearest backup image retained using the emergency recovery area in kickboard is literary
Part directly opens and uses virtual machine.
Further, backup image write sequence is set in the method, divides kickboard recovery region, setting backup plan
Slightly, setting kickboard rule；And check that backup image retains situation, specifically includes the following steps:
(1) all backup images are set, emergency recovery platform caching is preferentially written；
(2) kickboard is divided into emergency recovery area, traditional recovery district, without dividing space size；
(3) backup strategy is set, backup image file or backup image file group are included in different backup strategies, it is different
Backup strategy different backup image frequency of your backups and retention periods are set；
(4) setting kickboard rule limits emergency recovery area, each backup image file or backup in traditional recovery district respectively
Image file group the space occupied size and reservation number, emergency recovery area only retain backup image several times recently, and history is standby
Part mirror image will be migrated into traditional recovery district, and Free up Memory after image file is expired is returned to kickboard；
(5) inspect periodically whether each backup image file has reached the retention time of requirement, if having expired, incited somebody to action
The backup image file of phase is removed.
Further, the update kickboard rule, kickboard record file and kickboard inspection and kickboard access, it is specific to wrap
Include following steps:
(1) execute backup: backup management system executes virtualization backup procedure；
(2) judge the size of backup image file and caching: if backup image file is less than or equal to cache size, carrying out
Step (3)；Otherwise wait in line, return step (1)；
(3) it backup image file write-in caching: is cached for backup image file to be written；
(4) kickboard judges: judged according to backup storage parameter and kickboard rule, if COPY2≤COPY1, SIZE2≤
SIZE1 is set up simultaneously, thens follow the steps (5), if there is a condition to be unsatisfactory for, is thened follow the steps (a)；
Wherein, COPY1 is the image file number that should retain in emergency recovery area defined in kickboard rule file；
COPY2 is the image file number retained in the emergency recovery area recorded in kickboard record file；SIZE1 is kickboard rule text
It emergency recovery area defined in part can occupied space size；SIZE2 is that the emergency recovery area recorded in kickboard record file has accounted for
Use space size；
(a) the oldest image file in emergency recovery area is migrated to traditional recovery district, and executes step (b)；
(b) kickboard judges: judged according to backup storage parameter and kickboard rule, if COPY4≤COPY3, SIZE4≤
SIZE3 is set up simultaneously, is thened follow the steps (c), if there is a condition to be unsatisfactory for, alerts retention period limitation, and it is poly- to return to step
(1)；
Wherein, COPY3 is the image file number that should retain in tradition recovery district defined in kickboard rule file；
COPY4 is the image file number retained in the traditional recovery district recorded in kickboard record file；SIZE3 is kickboard rule text
It tradition recovery district defined in part can occupied space size；SIZE4 is that the traditional recovery district recorded in kickboard record file has accounted for
Use space size；
(c) kickboard space size judges: kickboard space size is compared with the oldest mirror image size in emergency recovery area, if
The oldest image file size in emergency recovery area is less than or equal to kickboard Spatial Residual size, thens follow the steps (d), otherwise, indicates slow
Insufficient space is deposited, is alerted, and return step (1)；
(d) it divides kickboard space: marking off the space of the oldest image file size in emergency recovery area in kickboard, give biography
System recovery district, continues to execute step (e)；
(e) the oldest image file in emergency recovery area is migrated into traditional recovery district into kickboard, and Free up Memory is extremely
Kickboard space is given, step (5) are continued to execute；
(5) kickboard space size judges: kickboard space size being compared with image file size in caching, if caching
Middle image file size is less than or equal to kickboard Spatial Residual size, thens follow the steps (6), otherwise, indicates inadequate buffer space, accuses
It is alert, and return step (1)；
(6) it divides kickboard space: marking off the space of image file size in caching in kickboard, give emergency recovery
Area continues to execute step (7)；
(7) emergency recovery area is written into the image file in caching.
Further, kickboard rule includes: emergency recovery area, traditional recovery district in kickboard record file in the method
Middle backup image file, which has retained number, should retain number less than or equal to the backup image file being arranged in kickboard rule file；It is floating
Occupied space is occupied less than equal to what is be arranged in kickboard rule file for emergency recovery area, traditional recovery district in plate record file
Space.
Further, described when virtual machine breaks down, retained using the emergency recovery area in kickboard nearest
Virtual machine is directly opened and is used by backup image file, is specifically included::
(1) the backup image file needed for positioning, by the backup image file with Network File System NFS read-only mode extension
It is loaded on the virtualized server in the emergency recovery platform to match with backup source, so that the backup image file is as the void
The NFS data source of quasi-ization server；
(2) using the snapshot mechanism of virtualization, snapshot is created in production inventory, namely restores log, it is new to store
The data of write-in, and the backup image file in emergency recovery platform is remained unchanged as the stamper file of virtual machine, can be beaten
Open virtual machine.
Further, the method further include: using the on-line storage migrating technology of virtualization, by backup image file
It is copied to production inventory, the Network File System NFS of backup image file is unloaded after the completion of migration, and will restore newly to write in log
The data entered are synchronized to the virtual machine stamper in production inventory, complete solidification.
The third aspect, the embodiment of the invention provides a kind of backup image management of starting virtual machine not recovered after backup
Equipment characterized by comprising at least one processor, the meter of at least one processor and storage in the memory
Calculation machine program instruction is realized when the computer program instructions are executed by the processor such as second aspect in above-described embodiment
Method.
Fourth aspect, the embodiment of the invention provides a kind of computer readable storage mediums, are stored thereon with computer journey
The method such as second aspect in above-described embodiment is realized in sequence instruction when the computer program instructions are executed by processor.
The beneficial effects of the present invention are: virtual machine emergency recovery platform simultaneously and is deposited emergency recovery area and conventional backup and is restored
Area, using kickboard mechanism, the dynamic equilibrium space hold that two regions are automated allows user more can be according to reality
Demand flexibly automates adjustresources distribution, avoids the excessive use of resource.Not only inheriting can by virtual platform height
With the high-timeliness of guaranteeing business continuity, while compensating for the means by Backup and Restore, it is ensured that virtualization service it is continuous
The characteristics of property poor in timeliness, while multiple historical events node copies of virtual machine can also be restored, it is an aging performance function
Property the virtual machine that balances very much include means.It solves not recovered direct emergency starting after virtual machine backs up and uses virtual machine
The problem of, the mirror image support virtual machine backed up can be utilized with obstructed over recovery after completing virtual machine and completing backup
Starting, exempts to have kept away recovery process, greatly shortens the virtual machine service recovery time under extreme case.
Detailed description of the invention
In order to illustrate the technical solution of the embodiments of the present invention more clearly, will make below to required in the embodiment of the present invention
Attached drawing is briefly described, for those of ordinary skill in the art, without creative efforts, also
Other drawings may be obtained according to these drawings without any creative labor.
Fig. 1 shows the structural schematic diagram of backup image management system；
Fig. 2 shows the backup image schematic diagrames of starting virtual machine not recovered after backup；
Fig. 3 shows kickboard management process schematic diagram；
Fig. 4 shows kickboard management flow chart；
Fig. 5 shows kickboard management realization figure；
Fig. 6 shows backup image transition graph；
Fig. 7 shows backup image migration schematic diagram；
Fig. 8 shows new backup image write-in schematic diagram；
Fig. 9 shows emergency recovery area backup image carry；
Figure 10 shows the snapshot opening figure of virtual machine；
Figure 11 shows the migration solidification figure of virtual machine；
Figure 12 shows the realization of mirror image management equipment.
Specific embodiment
The feature and exemplary embodiment of various aspects of the invention is described more fully below, in order to make mesh of the invention
, technical solution and advantage be more clearly understood, with reference to the accompanying drawings and embodiments, the present invention is further retouched in detail
It states.It should be understood that specific embodiment described herein is only configured to explain the present invention, it is not configured as limiting the present invention.
To those skilled in the art, the present invention can be real in the case where not needing some details in these details
It applies.Below the description of embodiment is used for the purpose of better understanding the present invention to provide by showing example of the invention.
It should be noted that, in this document, relational terms such as first and second and the like are used merely to a reality
Body or operation are distinguished with another entity or operation, are deposited without necessarily requiring or implying between these entities or operation
In any actual relationship or order or sequence.Moreover, the terms "include", "comprise" or its any other variant are intended to
Non-exclusive inclusion, so that the process, method, article or equipment including a series of elements is not only wanted including those
Element, but also including other elements that are not explicitly listed, or further include for this process, method, article or equipment
Intrinsic element.In the absence of more restrictions, the element limited by sentence " including ... ", it is not excluded that including
There is also other identical elements in the process, method, article or equipment of the element.
A kind of specific embodiment of the backup image management system of not recovered starting virtual machine after backup is given below.Such as
Shown in Fig. 1, the system is operated on emergency recovery platform, including memory space division module, backup storage parameter and kickboard
Rule setting module, kickboard management module, virtual machine backup module, backup image writing module and backup virtual machine emergency starting
Module, wherein
Memory space division module, for the memory space of the emergency recovery platform to be divided into caching and kickboard two
Point；
Backup storage parameter and kickboard rule setting module restore region for the setting of backup image write sequence, kickboard
It divides, backup strategy setting, kickboard rule setting, and checks that backup image retains situation；
Kickboard management module, for updating kickboard rule, kickboard record file and kickboard inspection and kickboard access；
Virtual machine backup module generates snapshot in backup, to store for the snapshot interface using virtualization
The stamper file of the data being newly written, virtual machine remains unchanged, and snapshot is executed after the completion of backup and is deleted, the data in snapshot are returned
It is written in stamper file；
Backup image writing module, for the emergency recovery platform will to be transferred in the backup image file of virtual machine,
The emergency recovery platform is controlled caching is written in backup image file and judges backup image file according to the kickboard rule
Storage；
Backup virtual machine emergency starting module utilizes the institute, emergency recovery area in kickboard when breaking down for virtual machine
Virtual machine is directly opened to exist side by side by the nearest backup image file retained to be used；
The emergency recovery platform draws the memory space on emergency recovery platform using memory space division module
Point, the emergency recovery platform generates virtual machine snapshot using virtual machine backup module；The emergency recovery platform utilizes backup
Memory space is written in the snapshot that mirror image writing module generates virtual machine backup module；It is described to answer when virtual machine breaks down
Anxious recovery platform is straight the nearest backup image file retained in memory space by backup virtual machine emergency starting module
It takes out and uses.
Further, the backup storage parameter and kickboard rule setting module specifically include:
Submodule is written in backup image: spatial cache is preferentially written in the backup image file for being arranged all；
Kickboard divides submodule: big without dividing space for kickboard to be divided into emergency recovery area, traditional recovery district
It is small；
Submodule is arranged in backup strategy: for backup image file or backup image file group to be included in different backup plans
Slightly, different backup image frequency of your backups and retention periods is arranged in different backup strategies；
Kickboard rule setting submodule, for each backup image text in limitation emergency recovery area respectively, traditional recovery district
Part or backup image file group the space occupied size and reservation number, emergency recovery area only retains backup image several times recently
File, history backup image file will be migrated into traditional recovery district, Free up Memory after backup image file expiration, be returned to floating
Plate；
Backup image file checking submodule: the reservation whether each backup image file has reached requirement is inspected periodically
Time removes expired backup image file if having expired.
Further, the kickboard management module, specifically includes:
Backup implementation sub-module: virtualization backup procedure is executed for realizing backup management system；
Backup image file judging submodule: for judging the size of backup image file and cache residual space: if standby
Part image file is less than or equal to cache remaining size, then caching is written in backup image file, otherwise, waited in line；
Backup image file cache submodule: it is cached for backup image file to be written；
Kickboard judging submodule: for being judged according to backup storage parameter and kickboard rule, if kickboard records file
The backup image file number COPY2 retained in the emergency recovery area of middle record is less than or equal to defined in kickboard rule file
The backup image file number COPY1 that should retain in emergency recovery area, and the emergency recovery area recorded in kickboard record file is
Occupied space size SIZE2 be less than or equal to kickboard rule file defined in emergency recovery area can occupied space size SIZE1, then
Continue for kickboard Spatial Residual size to be compared with backup image file size in caching, if backup image file is big in caching
It is small to be less than or equal to kickboard remaining space size, then from the kickboard space for marking backup image size in caching in kickboard space, hand over
Emergency recovery area is given, and emergency recovery area is written into the backup image file in caching, if the backup image file in caching is big
It is small to be greater than kickboard remaining space size, it indicates that kickboard remaining space is insufficient, then alerts insufficient space；
If COPY2≤COPY1 and SIZE2≤SIZE1 have any one it is invalid, by the oldest mirror image in emergency recovery area text
Part is migrated to traditional recovery district, is judged according to backup storage parameter and kickboard rule, if recorded in kickboard record file
It is answered in tradition recovery district defined in the backup image file number COPY4≤kickboard rule file retained in traditional recovery district
The backup image file number COPY3 of reservation, and kickboard records the traditional recovery district recorded in file occupied space size
Tradition recovery district defined in SIZE4≤kickboard rule file can occupied space size SIZE3 set up simultaneously, then by kickboard residue
Space size is compared with the oldest mirror image size in emergency recovery area, if the oldest mirror image size in emergency recovery area is less than or equal to kickboard
Remaining space size then carries out the division of kickboard space, and the kickboard of the oldest mirror image size in emergency recovery area is marked from kickboard space
Space gives and answers the multiple area of tradition, and the oldest image file in emergency recovery area is migrated traditional recovery district into kickboard, and
Free up Memory alerts insufficient space if kickboard remaining space is insufficient to the emergency recovery area of kickboard；
If COPY4≤COPY3, SIZE4≤SIZE3 have appoint between one it is invalid, then alert retention periods limitation；
Mirror transference submodule: for marking off the space of the oldest image file size in emergency recovery area from kickboard space
Traditional recovery district is given, and the oldest image file in emergency recovery area is migrated into traditional recovery district into kickboard, and discharge
Space to kickboard space；
Kickboard space size judging submodule: for carrying out image file size in kickboard Spatial Residual size and caching
Compare, if image file size is less than or equal to kickboard remaining space size in caching, mirror image in caching is marked off in kickboard
Give emergency recovery area in the space of size；
Submodule is written in image file: emergency recovery area is written for the image file in caching.
Further, backup virtual machine emergency starting module is specifically used in the system:
Backup image file needed for positioning, by the backup image file with Network File System NFS read-only mode carry
It should be use up on the virtualized server restored in platform to what backup source matched, so that the backup image file is virtual as this
Change the NFS data source of server；
Using the snapshot mechanism of virtualization, snapshot is created in production inventory, namely restores log, to store new write-in
Data, and the backup image file in emergency recovery platform is remained unchanged as the stamper file of virtual machine, i.e., openable void
Quasi- machine.
A kind of specific embodiment of the backup image management method of not recovered starting virtual machine after backup, packet is given below
Include following steps:
The memory space of entire emergency recovery platform is divided into caching and kickboard two parts.
Backup image write sequence is set, divides kickboard recovery region, setting backup strategy, setting kickboard rule；And it examines
It looks into backup image and retains situation.
More new management kickboard rule file, kickboard record file and kickboard inspection and kickboard access.
Using the snapshot interface of virtualization, snapshot is generated in backup, to store the data being newly written, and it is virtual
The stamper file of machine remains unchanged, and snapshot is executed after the completion of backup and is deleted, the write back data in snapshot is entered in stamper file.
It will be transferred to emergency recovery platform in the backup image file of virtual machine, emergency recovery platform is written into caching simultaneously
Judge how backup image file stores according to kickboard rule.
It, will using the nearest backup image file that the emergency recovery area in kickboard is retained when virtual machine breaks down
Virtual machine directly opens and uses.
As shown in Fig. 2, the memory space of entire emergency recovery platform is cut into two part of caching and kickboard, institute by the present invention
Buffer area is preferentially written in some backup images, recycles kickboard administrative skill to divide and kickboard is divided into emergency recovery area and tradition
The recovery district functional areas Liang Kuai realize that the balance of entire memory space uses.Wherein, emergency recovery area, for meet an urgent need pull-up when work
It for the memory space of virtual machine, does not need separately to prepare excessive memory space, shortens and restore time；Traditional recovery district,
For the reservation of history virtual machine copy, to be restored under non-emergency demand (such as the inquiry of historical data etc.), complete
After completing backup at virtual machine, the direct carry of the backup image of storage is supported into virtual machine as its stamper to virtual platform
It directly initiates, avoids recovery process, and be after actuation cured to the virtual machine using the storage shift function of virtualization
In production inventory.Using kickboard rule between emergency recovery area and traditional recovery district, the automation dynamic equilibrium in space is carried out.
For kickboard management process as shown in figure 3, formulating kickboard rule by backup management, kickboard inspection compares kickboard rule and sky
Between/number, kickboard division is carried out after judgement or is fed back to backup management.It carries out: being arranged all standby in the following ways
Spatial cache is preferentially written in part image file；Kickboard is divided into emergency recovery area, traditional recovery district, it is big without dividing space
It is small；Backup image file or backup image file group are included in different backup strategies, different backup strategies is arranged different
Backup image frequency of your backups and retention periods；Each backup image file or backup in limitation emergency recovery area, traditional recovery district
Image file group the space occupied size and reservation number, emergency recovery area only retains backup image file several times recently, goes through
History backup image file will be migrated into traditional recovery district；Free up Memory after backup image file expiration is returned to kickboard；Periodically
Check whether each backup image file has reached the retention time of requirement, if having expired, by expired backup image text
Part is removed, and feedback information, alarm.
Specifically, the establishment for carrying out kickboard rule file according to actual needs by administrator utilizes this file management kickboard
Using rule, defining some backup image file or backup image file group respectively can in emergency recovery area and traditional recovery district
With the space occupied capacity and file number；Backup image in traditional recovery district does not limit reservation number, only limits space and holds
Amount, its expired checkout time is limited by the retention periods of backup strategy.After the storage for completing backup image, information will be stored
Charge to kickboard record file.Each backup image file or backup image file group will be recorded in this file currently in emergency recovery
Used spatial content in area and traditional recovery district, file number.The separation of rule file and record file is stored, convenient for obtaining
Or change kickboard rule, avoid frequently writing into for rule file, and record file manual maintenance come band difficult management and
Maloperation risk.For all changes of utilization rate, and the change in kickboard space will be recorded in file in kickboard and registered.?
When backup image is written, emergency recovery platform will carry out kickboard inspection, comparison kickboard record file and kickboard rule file, to sentence
How disconnected backup image will be stored in backup storage.Kickboard access: it is distributed as required to desired zone.
Specifically, kickboard management includes the following steps, as shown in Figure 4:
(1) execute backup: backup management system executes virtualization backup procedure；
(2) judge the size of backup image file and caching: if backup image file is less than or equal to cache size, carrying out
Step (3)；Otherwise wait in line, return step (1)；
(3) it backup image file write-in caching: is cached for backup image file to be written；
(4) kickboard judges: judged according to backup storage parameter and kickboard rule, if COPY2≤COPY1, SIZE2≤
SIZE1 is set up simultaneously, thens follow the steps (5), if there is a condition to be unsatisfactory for, is thened follow the steps (a)；
Wherein, COPY1 is the image file number that should retain in emergency recovery area defined in kickboard rule file；
COPY2 is the image file number retained in the emergency recovery area recorded in kickboard record file；SIZE1 is kickboard rule text
It emergency recovery area defined in part can occupied space size；SIZE2 is that the emergency recovery area recorded in kickboard record file has accounted for
Use space size；
(a) the oldest image file in emergency recovery area is migrated to traditional recovery district, and executes step (b)；
(b) kickboard judges: judged according to backup storage parameter and kickboard rule, if COPY4≤COPY3, SIZE4≤
SIZE3 is set up simultaneously, is thened follow the steps (c), if there is a condition to be unsatisfactory for, alerts retention period limitation, and it is poly- to return to step
(1)；
Wherein, COPY3 is the image file number that should retain in tradition recovery district defined in kickboard rule file；
COPY4 is the image file number retained in the traditional recovery district recorded in kickboard record file；SIZE3 is kickboard rule text
It tradition recovery district defined in part can occupied space size；SIZE4 is that the traditional recovery district recorded in kickboard record file has accounted for
Use space size；
(c) kickboard space size judges: kickboard space size is compared with the oldest mirror image size in emergency recovery area, if
The oldest image file size in emergency recovery area is less than or equal to kickboard Spatial Residual size, thens follow the steps (d), otherwise, indicates slow
Insufficient space is deposited, is alerted, and return step (1)；
(d) it divides kickboard space: marking off the space of the oldest image file size in emergency recovery area in kickboard, give biography
System recovery district, continues to execute step (e)；
(e) the oldest image file in emergency recovery area is migrated into traditional recovery district into kickboard, and Free up Memory is extremely
Kickboard space is given, step (5) are continued to execute；
(5) kickboard space size judges: kickboard space size being compared with image file size in caching, if caching
Middle image file size is less than or equal to kickboard Spatial Residual size, thens follow the steps (6), otherwise, indicates inadequate buffer space, accuses
It is alert, and return step (1)；
(6) it divides kickboard space: marking off the space of image file size in caching in kickboard, give emergency recovery
Area continues to execute step (7)；
(7) emergency recovery area is written into the image file in caching.
Kickboard administrative mechanism of the invention enables the emergency recovery area of kickboard and traditional recovery district to be automatically performed storage
The utilization rate of the distribution according to need in space, memory space is higher, and usage mode is more flexible, while avoiding single virtual machine or void
Quasi- excessive use of the unit to resource.The specific implementation mechanism of kickboard management is as shown in figure 5, upper layer is kickboard rule file and floats
Plate records file, and lower layer is specific mirror image.Arrow expression compares in the content of connection.
For example, comparing to the mirror image of emergency recovery district: there are c-5, two mirror images of c-6 in current emergency recovery area, therefore floats
It is 2 that plate, which records the copy in file, and the total size of two mirror images is 0.5+0.4=0.9 (XX indicates the data specifically backed up).?
Copy=2 corresponding less than or equal to kickboard rule file, and size=1.5.On the state of Fig. 5, in a new backup
When mirror image c-7 is written, it is temporarily put into buffer area.According to kickboard rule and mechanism, it is onesize that kickboard space c-5 has been divided into
Space give traditional recovery district, and backup image c-5 oldest in emergency recovery area has been moved into traditional recovery district.Due to c-
5 have moved, therefore the occupied space c-5 in emergency recovery area is discharged, and give back kickboard.It updates kickboard and records file.Its is standby
Part mirror transference process is as shown in Figure 6.The backup image of Fig. 7 migrates the signal based on Fig. 6.As shown in figure 8, when one it is new standby
When part mirror image c-7 has been stored in caching, according to the life cycle setting and kickboard rule of backup storage, by kickboard space divided with
C-7 gives in an equal amount of space emergency recovery area, and backup image c-7 in caching is migrated to traditional recovery district, updates kickboard
Record file.Emergency recovery area is written in new backup image, and a backup image oldest in emergency recovery area is migrated to biography
System recovery district.The write-in of new backup image is as shown in Figure 8.Its specific kickboard setting and implementation are as follows:
The signal of kickboard rule file:
| VM/VM group | Region | Number should be retained | It can occupied space (TB) |
| VMx | Emergency recovery area | 2 | 1.5 |
| VMx | Traditional recovery district | ∞ (is not limited) | 3 |
Kickboard records file signal:
| VM/VM group | Region | Number is retained | Occupied space (TB) |
| VMx | Emergency recovery area | 2 | 0.9 |
| VMx | Traditional recovery district | 4 | 1.9 |
Emergency recovery platform executes kickboard inspection:
(a1) emergency recovery Qu Zhongyi remains with 2 parts of data, needs to migrate to traditional recovery district；
(b1) size (by taking its size is 0.5TB as an example) of backup image 5 oldest in emergency recovery area is checked, tradition is extensive
Backup image in multiple area is not up to the retention periods that backup strategy defines, and does not discharge, traditional recovery district has occupied
1.9TB。
(c1) kickboard inspection determines that traditional recovery district needs [1.9 (occupancy)+0.5 (variable)] TB < 3TB (rule limitation)
Space, then from kickboard divide 0.5TB the variable space into traditional recovery district, complete mirror transference；In the process, if
+ variable > rule limitation has been occupied, then has prevented the migration of backup image, and to backup management feeder alert.
(d1) after completing mirror transference, the spare space of 0.5TB is returned to kickboard by space of meeting an urgent need, as shown in fig. 6, kickboard
Record file change；
(e1) kickboard inspection determines that emergency recovery area needs [0.4 (occupancy)+0.7 (variable)] TB < 1.5TB (rule limit
System) space, then from kickboard divide 0.7TB the variable space into emergency recovery area, complete mirror image write-in, as shown in Figure 8；
In the process, if having occupied+variable > rule limitation, the write-in of backup image is prevented, and to backup management feeder alert.
(f1) after completing mirror image write-in, kickboard records file change:
When virtual machine breaks down, the nearest backup image that emergency recovery area is retained can use virtual machine is straight
It takes to open to exist side by side and use.
Not recovered direct emergency starting and the technology using virtual machine after virtual machine backup of the invention, can complete
After virtual machine completes backup, it can exempt to have kept away and restore using the starting of the mirror image support virtual machine backed up with obstructed over recovery
Journey greatly shortens the virtual machine service recovery time under extreme case.As shown in figs. 9-10, realize that process is as follows:
(A1) positioning needed for backup image (backup image 6), by the mirror image with NFS read-only mode carry to and backup source
On the virtualized server to match, so that memory space and virtual file of the backup image as the virtualized server,
As shown in Figure 9；
(A2) using the snapshot mechanism of virtualization, snapshot (restoring log) is created in production inventory, is newly write to store
The data entered, and the backup image in emergency recovery platform is remained unchanged as the stamper file of virtual machine, i.e., it is openable virtual
Machine, as shown in Figure 10.
(A3) using the on-line storage migrating technology of virtualization, backup image is copied into production inventory, after the completion of migration
The NFS of backup image is unloaded, and the data for restoring newly to be written in log are synchronized to the virtual machine stamper in production inventory, is completed
Solidification, as shown in figure 11.
Figure 12 shows the hardware structural diagram of mirror image management equipment provided in an embodiment of the present invention.
Mirror image management equipment may include processor 401 and the memory 402 for being stored with computer program instructions.
Specifically, above-mentioned processor 401 may include central processing unit (CPU) or specific integrated circuit
(Application Specific Integrated Circuit, ASIC), or may be configured to implement implementation of the present invention
One or more integrated circuits of example.
Memory 402 may include the mass storage for data or instruction.For example it rather than limits, memory
402 may include hard disk drive (Hard Disk Drive, HDD), floppy disk drive, flash memory, CD, magneto-optic disk, tape or logical
With the combination of universal serial bus (Universal Serial Bus, USB) driver or two or more the above.It is closing
In the case where suitable, memory 402 may include the medium of removable or non-removable (or fixed).In a suitable case, it stores
Device 402 can be inside or outside data processing equipment.In a particular embodiment, memory 402 is nonvolatile solid state storage
Device.In a particular embodiment, memory 402 includes read-only memory (ROM).In a suitable case, which can be mask
ROM, programming ROM (PROM), erasable PROM (EPROM), the electric erasable PROM (EEPROM), electrically-alterable ROM of programming
(EAROM) or the combination of flash memory or two or more the above.
Processor 401 is by reading and executing the computer program instructions stored in memory 402, to realize above-mentioned implementation
Any one backup image management method in example.
In one example, mirror image management equipment may also include communication interface 403 and bus 410.Wherein, such as Figure 12 institute
Show, processor 401, memory 402, communication interface 403 connect by bus 410 and complete mutual communication.
Communication interface 403 is mainly used for realizing in the embodiment of the present invention between each module, device, unit and/or equipment
Communication.
Bus 410 includes hardware, software or both, and the component of mirror image management equipment is coupled to each other together.Citing comes
It says rather than limits, bus may include accelerated graphics port (AGP) or other graphics bus, enhance Industry Standard Architecture (EISA) always
Line, front side bus (FSB), super transmission (HT) interconnection, the interconnection of Industry Standard Architecture (ISA) bus, infinite bandwidth, low pin count
(LPC) bus, memory bus, micro- channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express
(PCI-X) bus, Serial Advanced Technology Attachment (SATA) bus, Video Electronics Standards Association part (VLB) bus or other conjunctions
The combination of suitable bus or two or more the above.In a suitable case, bus 410 may include one or more
Bus.Although specific bus has been described and illustrated in the embodiment of the present invention, the present invention considers any suitable bus or interconnection.
The mirror image management equipment can execute the mirror image management method in the embodiment of the present invention, retouch to realize in conjunction with Fig. 4
The mirror image management method stated.
In addition, the embodiment of the present invention can provide a kind of computer-readable in conjunction with the mirror image management method in above-described embodiment
Storage medium is realized.Computer program instructions are stored on the computer readable storage medium；The computer program instructions quilt
Processor realizes any one mirror image management method in above-described embodiment when executing.
It should be clear that the invention is not limited to specific configuration described above and shown in figure and processing.
For brevity, it is omitted here the detailed description to known method.In the above-described embodiments, several tools have been described and illustrated
The step of body, is as example.But method process of the invention is not limited to described and illustrated specific steps, this field
Technical staff can be variously modified, modification and addition after understanding spirit of the invention, or suitable between changing the step
Sequence.
Functional block shown in structures described above block diagram can be implemented as hardware, software, firmware or their group
It closes.When realizing in hardware, it may, for example, be electronic circuit, specific integrated circuit (ASIC), firmware appropriate, insert
Part, function card etc..When being realized with software mode, element of the invention is used to execute program or the generation of required task
Code section.Perhaps code segment can store in machine readable media program or the data-signal by carrying in carrier wave is passing
Defeated medium or communication links are sent." machine readable media " may include any medium for capableing of storage or transmission information.
The example of machine readable media includes electronic circuit, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), soft
Disk, CD-ROM, CD, hard disk, fiber medium, radio frequency (RF) link, etc..Code segment can be via such as internet, inline
The computer network of net etc. is downloaded.
It should also be noted that, the exemplary embodiment referred in the present invention, is retouched based on a series of step or device
State certain methods or system.But the present invention is not limited to the sequence of above-mentioned steps, that is to say, that can be according in embodiment
The sequence referred to executes step, may also be distinct from that the sequence in embodiment or several steps are performed simultaneously.
The above description is merely a specific embodiment, it is apparent to those skilled in the art that,
For convenience of description and succinctly, the system, module of foregoing description and the specific work process of unit can refer to preceding method
Corresponding process in embodiment, details are not described herein.It should be understood that scope of protection of the present invention is not limited thereto, it is any to be familiar with
Those skilled in the art in the technical scope disclosed by the present invention, can readily occur in various equivalent modifications or substitutions,
These modifications or substitutions should be covered by the protection scope of the present invention.
Claims (12)
1. the backup image management system of not recovered starting virtual machine after a kind of backup, it is characterised in that: the system operation
On emergency recovery platform, including memory space division module, backup storage parameter and kickboard rule setting module, kickboard management
Module, virtual machine backup module, backup image writing module and backup virtual machine emergency starting module, wherein
Memory space division module, for the memory space of the emergency recovery platform to be divided into caching and kickboard two parts；
Backup storage parameter and kickboard rule setting module, for the setting of backup image write sequence, kickboard restore region division,
Backup strategy setting, kickboard rule setting, and check that backup image retains situation；
Kickboard management module, for updating kickboard rule, kickboard record file and kickboard inspection and kickboard access；
Virtual machine backup module generates snapshot in backup, newly writes to store for the snapshot interface using virtualization
The stamper file of the data entered, virtual machine remains unchanged, and snapshot is executed after the completion of backup and is deleted, the write back data in snapshot is entered
In stamper file；
Backup image writing module is controlled for will be transferred to the emergency recovery platform in the backup image file of virtual machine
Backup image file is written caching and judges that backup image file stores according to the kickboard rule by the emergency recovery platform；
Backup virtual machine emergency starting module is retained when breaking down for virtual machine using the emergency recovery area in kickboard
Nearest backup image file virtual machine directly opened to exist side by side use；
The emergency recovery platform divides the memory space on emergency recovery platform using memory space division module, institute
It states emergency recovery platform and generates virtual machine snapshot using virtual machine backup module；The emergency recovery platform is write using backup image
Enter the snapshot that module generates virtual machine backup module and memory space is written；When virtual machine breaks down, the emergency recovery
Platform is directly opened the nearest backup image file retained in memory space by backup virtual machine emergency starting module
And it uses.
2. the system as claimed in claim 1, it is characterised in that: the backup storage parameter and kickboard rule setting module are specific
Include:
Submodule is written in backup image: spatial cache is preferentially written in the backup image file for being arranged all；
Kickboard divides submodule: for kickboard to be divided into emergency recovery area, traditional recovery district, without dividing space size；
Submodule is arranged in backup strategy: for backup image file or backup image file group to be included in different backup strategies,
Different backup image frequency of your backups and retention periods is arranged in different backup strategies；
Kickboard rule setting submodule, for limiting emergency recovery area respectively, in traditional recovery district each backup image file or
Backup image file group the space occupied size and reservation number, emergency recovery area only retain backup image text several times recently
Part, history backup image file will be migrated into traditional recovery district, Free up Memory after backup image file expiration, be returned to floating
Plate；
Backup image file checking submodule: when inspecting periodically each backup image file and whether having reached the reservation of requirement
Between, if having expired, expired backup image file is removed.
3. the system as claimed in claim 1, it is characterised in that: the kickboard management module specifically includes:
Backup implementation sub-module: virtualization backup procedure is executed for realizing backup management system；
Backup image file judging submodule: for judging the size of backup image file and cache residual space: if backup mirror
Picture file is less than or equal to cache remaining size, then caching is written in backup image file, otherwise, waited in line；
Backup image file cache submodule: it is cached for backup image file to be written；
Kickboard judging submodule: for being judged according to backup storage parameter and kickboard rule, if remembering in kickboard record file
The backup image file number COPY2 retained in the emergency recovery area of record is less than or equal to emergency defined in kickboard rule file
The backup image file number COPY1 that should retain in recovery district, and the emergency recovery area recorded in kickboard record file has occupied
Space size SIZE2 be less than or equal to kickboard rule file defined in emergency recovery area can occupied space size SIZE1, then continue
Kickboard Spatial Residual size is compared with backup image file size in caching, if backup image file size is small in caching
In being equal to kickboard remaining space size, then from the kickboard space for marking backup image size in caching in kickboard space, gives and answer
Anxious recovery district, and emergency recovery area is written into the backup image file in caching, if the backup image file size in caching is big
In kickboard remaining space size, indicates that kickboard remaining space is insufficient, then alert insufficient space；
If COPY2≤COPY1 and SIZE2≤SIZE1 have any one it is invalid, the oldest image file in emergency recovery area is moved
Traditional recovery district is moved to, is judged according to backup storage parameter and kickboard rule, if the tradition recorded in kickboard record file
It should retain in tradition recovery district defined in the backup image file number COPY4≤kickboard rule file retained in recovery district
Backup image file number COPY3, and in kickboard record file traditional recovery district for recording occupied space size SIZE4≤
Tradition recovery district defined in kickboard rule file can occupied space size SIZE3 set up simultaneously, then it is kickboard remaining space is big
It is small to be compared with the oldest mirror image size in emergency recovery area, if the oldest mirror image size in emergency recovery area is less than or equal to the remaining sky of kickboard
Between size, then carry out the division of kickboard space, the kickboard space of the oldest mirror image size in emergency recovery area marked from kickboard space, hand over
Traditional recovery district into kickboard is migrated to traditional recovery district, and by the oldest image file in emergency recovery area, and discharges sky
Between to the emergency recovery area of kickboard, if kickboard remaining space is insufficient, alert insufficient space；
If COPY4≤COPY3, SIZE4≤SIZE3 has that any bar is invalid, then alerts retention periods limitation；
Mirror transference submodule: it gives in the space for marking off the oldest image file size in emergency recovery area from kickboard space
Traditional recovery district, and the oldest image file in emergency recovery area is migrated into traditional recovery district into kickboard, and Free up Memory
To kickboard space；
Kickboard space size judging submodule: for comparing kickboard Spatial Residual size and image file size in caching
Compared with, if caching in image file size be less than or equal to kickboard remaining space size, marked off in kickboard caching in mirror image it is big
Give emergency recovery area in small space；
Submodule is written in image file: emergency recovery area is written for the image file in caching.
4. the system as claimed in claim 1, it is characterised in that: the backup virtual machine emergency starting module is specifically used for:
Backup image file needed for positioning, by required backup image file with Network File System NFS read-only mode carry
On virtualized server into the emergency recovery platform to match with backup source, so that required backup image file is as institute
State the NFS data source of virtualized server；
Using the snapshot mechanism of virtualization, snapshot is created in production inventory, to store the data being newly written, and emergency recovery
Backup image file in platform is remained unchanged as the stamper file of virtual machine.
5. the backup image management method of not recovered starting virtual machine after a kind of backup, which comprises the following steps:
(1) memory space of entire emergency recovery platform is divided into caching and kickboard two parts；
(2) backup image write sequence is set, divides kickboard recovery region, setting backup strategy, setting kickboard rule；And it examines
It looks into backup image and retains situation；
(3) kickboard rule file, kickboard record file and kickboard inspection and kickboard access are updated；
(4) using the snapshot interface of virtualization, snapshot is generated in backup, to store the data being newly written, and it is virtual
The stamper file of machine remains unchanged, and snapshot is executed after the completion of backup and is deleted, the write back data in snapshot is entered in stamper file；
(5) it will be transferred to the emergency recovery platform in the backup image file of virtual machine, controlling the emergency recovery platform will
The write-in of backup image file caches and judges how backup image file stores according to kickboard rule；
It (six), will using the nearest backup image file that the emergency recovery area in kickboard is retained when virtual machine breaks down
Virtual machine directly opens and uses.
6. method as claimed in claim 5, it is characterised in that: the setting backup image write sequence divides kickboard recovery
Region, setting backup strategy, setting kickboard rule；And check that backup image retains situation, specifically includes the following steps:
(1) all backup images are set, emergency recovery platform caching is preferentially written；
(2) kickboard is divided into emergency recovery area, traditional recovery district, without dividing space size；
(3) backup strategy is set, backup image file or backup image file group are included in different backup strategies, different is standby
Part strategy setting different backup image frequency of your backups and retention periods；
(4) setting kickboard rule limits emergency recovery area, each backup image file or backup image in traditional recovery district respectively
File group the space occupied size and reservation number, emergency recovery area only retains backup image several times recently, history backup mirror
As that will migrate into traditional recovery district, Free up Memory after image file is expired is returned to kickboard；
(5) inspect periodically whether each backup image file has reached the retention time of requirement, it, will be expired if having expired
Backup image file is removed.
7. method as claimed in claim 5, it is characterised in that: the update kickboard rule, kickboard record file and kickboard
It checks and kickboard accesses, specifically includes the following steps:
(1) execute backup: backup management system executes virtualization backup procedure；
(2) judge the size of backup image file and caching: if backup image file is less than or equal to cache size, carrying out step
(3)；Otherwise wait in line, return step (1)；
(3) it backup image file write-in caching: is cached for backup image file to be written；
(4) kickboard judges: judged according to backup storage parameter and kickboard rule, if COPY2≤COPY1, SIZE2≤
SIZE1 is set up simultaneously, thens follow the steps (5), if there is a condition to be unsatisfactory for, is thened follow the steps (a)；
Wherein, COPY1 is the image file number that should retain in emergency recovery area defined in kickboard rule file；COPY2 is
The image file number retained in the emergency recovery area recorded in kickboard record file；SIZE1 is fixed in kickboard rule file
The emergency recovery area of justice can occupied space size；SIZE2 is that kickboard records the emergency recovery area recorded in file occupied space
Size；
(a) the oldest image file in emergency recovery area is migrated to traditional recovery district, and executes step (b)；
(b) kickboard judges: judged according to backup storage parameter and kickboard rule, if COPY4≤COPY3, SIZE4≤
SIZE3 is set up simultaneously, is thened follow the steps (c), if there is a condition to be unsatisfactory for, alerts retention period limitation, and it is poly- to return to step
(1)；
Wherein, COPY3 is the image file number that should retain in tradition recovery district defined in kickboard rule file；COPY4 is
The image file number retained in the traditional recovery district recorded in kickboard record file；SIZE3 is fixed in kickboard rule file
Traditional recovery district of justice can occupied space size；SIZE4 is that kickboard records the traditional recovery district recorded in file occupied space
Size；
(c) kickboard space size judges: kickboard space size being compared with the oldest mirror image size in emergency recovery area, if emergency
The oldest image file size in recovery district is less than or equal to kickboard Spatial Residual size, thens follow the steps (d), otherwise, indicates that caching is empty
Between insufficient, alarm, and return step (1)；
(d) it divides kickboard space: marking off the space of the oldest image file size in emergency recovery area in kickboard, it is extensive to give tradition
Multiple area, continues to execute step (e)；
(e) the oldest image file in emergency recovery area is migrated into traditional recovery district into kickboard, and Free up Memory is floating to giving
Plate space continues to execute step (5)；
(5) kickboard space size judges: kickboard space size being compared with image file size in caching, if mirror in caching
Picture file size is less than or equal to kickboard Spatial Residual size, thens follow the steps (6), otherwise, indicates inadequate buffer space, alerts,
And return step (1)；
(6) it divides kickboard space: marking off the space of image file size in caching in kickboard, give emergency recovery area, after
It is continuous to execute step (7)；
(7) emergency recovery area is written into the image file in caching.
8. method as claimed in claim 5, it is characterised in that: kickboard rule include: kickboard record file in emergency recovery area,
Backup image file has retained number and has answered less than or equal to the backup image file being arranged in kickboard rule file in traditional recovery district
Retain number；Kickboard records emergency recovery area in file, occupied space is less than equal in kickboard rule file for traditional recovery district
What is be arranged can occupied space.
9. method as claimed in claim 5, it is characterised in that: it is described when virtual machine breaks down, utilize answering in kickboard
Virtual machine is directly opened and is used by the nearest backup image file that anxious recovery district is retained, and is specifically included:
(1) the backup image file needed for positioning, extremely with Network File System NFS read-only mode carry by the backup image file
On the virtualized server in emergency recovery platform to match with backup source, so that the backup image file is as the virtualization
The NFS data source of server；
(2) using the snapshot mechanism of virtualization, snapshot is created in production inventory, namely restores log, to store new write-in
Data, and the backup image file in emergency recovery platform is remained unchanged as the stamper file of virtual machine, i.e., openable void
Quasi- machine.
10. method as claimed in claim 5, which is characterized in that the method also includes:
Using the on-line storage migrating technology of virtualization, backup image file is copied to production inventory, is unloaded after the completion of migration
The Network File System NFS of backup image file, and the data that are newly written in log will be restored and be synchronized to the void in production inventory
Quasi- machine stamper, completes solidification.
11. the backup image management equipment of not recovered starting virtual machine after a kind of backup characterized by comprising at least one
A processor, the computer program instructions of at least one processor and storage in the memory, when the computer journey
The method as described in any one of claim 5-10 is realized in sequence instruction when being executed by the processor.
12. a kind of computer readable storage medium, is stored thereon with computer program instructions, which is characterized in that when the calculating
The method as described in any one of claim 5-10 is realized when machine program instruction is executed by processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711494862.4A CN109992449B (en) | 2017-12-31 | 2017-12-31 | Backup image management system, method, device and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711494862.4A CN109992449B (en) | 2017-12-31 | 2017-12-31 | Backup image management system, method, device and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109992449A true CN109992449A (en) | 2019-07-09 |
| CN109992449B CN109992449B (en) | 2023-04-11 |
Family
ID=67110758
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711494862.4A Active CN109992449B (en) | 2017-12-31 | 2017-12-31 | Backup image management system, method, device and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109992449B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113010474A (en) * | 2021-03-16 | 2021-06-22 | 中国联合网络通信集团有限公司 | File management method, instant messaging method and storage server |
| WO2021237645A1 (en) * | 2020-05-29 | 2021-12-02 | 深圳市欢太科技有限公司 | Method and apparatus for updating mirroring, and electronic device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103678036A (en) * | 2013-11-15 | 2014-03-26 | 上海爱数软件有限公司 | Backup method based on virtual machine operation information data finding |
| CN103902407A (en) * | 2012-12-31 | 2014-07-02 | 华为技术有限公司 | Virtual machine recovery method and server |
| CN104407938A (en) * | 2014-11-21 | 2015-03-11 | 上海爱数软件有限公司 | Recovery method for various granularities after mirror-image-level backup of virtual machine |
| CN106681858A (en) * | 2015-11-10 | 2017-05-17 | 中国电信股份有限公司 | Virtual machine data disaster tolerance method and management device |
-
2017
- 2017-12-31 CN CN201711494862.4A patent/CN109992449B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103902407A (en) * | 2012-12-31 | 2014-07-02 | 华为技术有限公司 | Virtual machine recovery method and server |
| CN103678036A (en) * | 2013-11-15 | 2014-03-26 | 上海爱数软件有限公司 | Backup method based on virtual machine operation information data finding |
| CN104407938A (en) * | 2014-11-21 | 2015-03-11 | 上海爱数软件有限公司 | Recovery method for various granularities after mirror-image-level backup of virtual machine |
| CN106681858A (en) * | 2015-11-10 | 2017-05-17 | 中国电信股份有限公司 | Virtual machine data disaster tolerance method and management device |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021237645A1 (en) * | 2020-05-29 | 2021-12-02 | 深圳市欢太科技有限公司 | Method and apparatus for updating mirroring, and electronic device and storage medium |
| CN113010474A (en) * | 2021-03-16 | 2021-06-22 | 中国联合网络通信集团有限公司 | File management method, instant messaging method and storage server |
| CN113010474B (en) * | 2021-03-16 | 2023-10-24 | 中国联合网络通信集团有限公司 | File management method, instant messaging method and storage server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109992449B (en) | 2023-04-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103164254B (en) | For maintaining the conforming method and system of memory storage in mirror image virtual environment | |
| EP2288975B1 (en) | Method for optimizing cleaning of maps in flashcopy cascades containing incremental maps | |
| CN106095620B (en) | A kind of development approach of built-in Linux partition holding | |
| CN108153849B (en) | Database table segmentation method, device, system and medium | |
| US9635109B2 (en) | Enhancing reliability of a storage system by strategic replica placement and migration | |
| CN111324303B (en) | SSD garbage recycling method, SSD garbage recycling device, computer equipment and storage medium | |
| CN109086425B (en) | Data processing method and device for database | |
| CN106155943B (en) | A kind of method and device of the power down protection of dual control storage equipment | |
| CN104735107A (en) | Recovery method and device for data copies in distributed storage system | |
| CN104462612A (en) | Method and device for monitoring database information | |
| CN104216802B (en) | Memory database recovery method and device | |
| CN108959526A (en) | Blog management method and log management apparatus | |
| US20110209134A1 (en) | Information processing apparatus | |
| CN100456255C (en) | Device and method for fetching snapshot data | |
| CN109992449A (en) | Backup image management system, method, equipment and medium | |
| CN104424115B (en) | Recover method, storage device and the electronic equipment of the preset state of electronic equipment | |
| CN107341072A (en) | A kind of data back up method and device | |
| CN112363815A (en) | Redis cluster processing method and device, electronic equipment and computer readable storage medium | |
| US9459676B2 (en) | Data storage device control with power hazard mode | |
| CN103677879B (en) | Software installation method and corresponding software mounting device | |
| CN108573049A (en) | Data processing method and distributed storage devices | |
| CN115268767A (en) | Data processing method and device | |
| US11977490B2 (en) | Method for executing a transaction | |
| CN115543225B (en) | Data processing method, system, device, computer storage medium and electronic equipment | |
| US11947827B2 (en) | Synchronizing a stale component of a distributed object using a delta component during maintenance |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |