WO2021104383A1 - 数据备份的方法和装置、设备和存储介质 - Google Patents

数据备份的方法和装置、设备和存储介质 Download PDF

Info

Publication number
WO2021104383A1
WO2021104383A1 PCT/CN2020/131845 CN2020131845W WO2021104383A1 WO 2021104383 A1 WO2021104383 A1 WO 2021104383A1 CN 2020131845 W CN2020131845 W CN 2020131845W WO 2021104383 A1 WO2021104383 A1 WO 2021104383A1
Authority
WO
WIPO (PCT)
Prior art keywords
backup
time
data
backed
strategy
Prior art date
Application number
PCT/CN2020/131845
Other languages
English (en)
French (fr)
Inventor
胡岩岩
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2021104383A1 publication Critical patent/WO2021104383A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1448Management of the data involved in backup or backup restore
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects

Definitions

  • This application relates to the field of computer technology, for example, to a method and device, equipment, and storage medium for data backup.
  • data backup is an important means to prevent data loss and improve data security.
  • the data backup function of a virtual machine is indispensable. For example, when the virtual machine's disk is abnormally damaged, disk data is lost, and/or user misoperations, the backup data can be used to The data of the virtual machine is restored.
  • the data backup strategy is usually set by the user based on experience. However, the traditional method will lead to unreasonable backup policy settings, which in turn leads to a lower success rate of data backup and a longer time for data backup.
  • This application provides a method and device, equipment and storage medium for data backup.
  • Provide a data backup method including:
  • the device runs on one of the at least one host device, and a backup terminal is installed on each of the at least one host device;
  • the backup strategy at the current backup moment of the device to be backed up is determined, so The backup strategy includes at least one of the disk file merging direction and the disk file merging depth of the device to be backed up;
  • an instruction for backing up the device to be backed up is sent to a backup terminal in one of the at least one host device.
  • a device for data backup including:
  • the first acquisition module is configured to acquire the data increment of the current backup time of the device to be backed up relative to the previous backup time, the data volume at the current backup time and the data volume at the previous backup time, and the data volume of at least one host device at the current backup time
  • the amount of resources; the device to be backed up runs on one of the at least one host device, and a backup terminal is installed on each of the at least one host device;
  • the first determining module is configured to determine the current device to be backed up based on the data increment, the amount of data at the current backup moment, the amount of data at the last backup moment, and the resource amount of the at least one host device at the current backup moment.
  • the first sending module is configured to send an instruction for backing up the device to be backed up to a backup terminal in one of the at least one host device according to the backup strategy.
  • a computer device including a memory and a processor, the memory stores a computer program, and the processor implements the data backup method provided in the embodiment of the present application when the processor executes the computer program.
  • a storage medium is also provided, the storage medium stores a computer program, and when the computer program is executed by a processor, the method for data backup provided in the embodiment of the present application is implemented.
  • FIG. 1 is a system architecture diagram of the application of the data backup method provided by an embodiment of the application
  • FIG. 2 is a schematic flowchart of a data backup method provided by an embodiment of the application
  • FIG. 3 is a schematic diagram of changes in the qcow2 external snapshot disk file chain of a virtual machine during data backup provided by an embodiment of the application;
  • FIG. 4 is a schematic diagram of another flow of a data backup method provided by an embodiment of the application.
  • FIG. 5 is a schematic flowchart of another data backup method provided by an embodiment of the application.
  • FIG. 6 is a schematic diagram of a backup strategy of a virtual machine provided by an embodiment of the application.
  • FIG. 7 is a schematic structural diagram of a data backup device provided by an embodiment of the application.
  • FIG. 8 is a schematic structural diagram of a computer device provided by an embodiment of the application.
  • the data backup method provided in the embodiment of the present application may be adapted to the system shown in FIG. 1, and the system may include a data backup strategy generating device 10 and a system to be backed up 11.
  • the system to be backed up 11 includes a device to be backed up 110 and a host device 111.
  • the device to be backed up 110 runs on the host device 111, and the host device 111 is installed with a backup client.
  • the above-mentioned data backup strategy generating device 10 is set to generate a backup strategy, and the backup client obtains the data of the device 110 to be backed up from the storage library (the storage library may be a disk array) through the backup proxy interface on the host device 111 based on the generated backup strategy.
  • the data is sent to the backup server to implement the data backup of the device 110 to be backed up.
  • the execution body of the following method embodiments may be a data backup device, and the device may be implemented as part or all of the computer equipment through software, hardware, or a combination of software and hardware.
  • the following method embodiments are described with an example in which the execution subject is a computer device.
  • FIG. 2 is a schematic flowchart of a data backup method provided by an embodiment of the application. This embodiment relates to the process of how a computer device determines a backup strategy based on the operating information of the device to be backed up and the host device. As shown in Figure 2, the method may include:
  • the computer device can learn the current backup time and the last backup time of the device to be backed up through the basic backup strategy set in the backup server.
  • the backup server may obtain the basic backup strategy through the backup-related content set by the user, and may also obtain the basic backup strategy through the strategy output by the data backup strategy generating device.
  • the method for obtaining the basic backup strategy is not limited in this embodiment.
  • the basic backup strategy may include the start time of the data backup of the device to be backed up, and whether the data backup is a full backup or an incremental backup, etc.
  • Full backup refers to the backup of all data in the disk of the device to be backed up.
  • Incremental backup refers to the backup of incremental data in the disk of the device to be backed up.
  • the incremental data is the disk of the device to be backed up after the last backup. Data added, deleted and/or modified in the
  • the aforementioned data increment refers to the amount of data change of the device to be backed up at the current backup time relative to the previous backup time, including the amount of data added, deleted, and/or modified in the disk of the device to be backed up.
  • the above-mentioned data volume at the current time is related to whether the device to be backed up performs full backup or incremental backup.
  • the data volume at the current time is the data volume of all data in the disk of the device to be backed up.
  • the amount of data at the current time is the amount of data change in the disk of the device to be backed up at the previous backup time.
  • the above-mentioned data volume at the previous backup time refers to the total data volume in the disk of the device to be backed up at the previous backup time.
  • the resource amount of the host device at the current backup time includes the occupancy status of the central processing unit (CPU) and the memory occupancy status of the host device at the current backup time.
  • the above-mentioned backup terminal is the backup client. Since the backup client is installed on the host device, the CPU and memory resources of the host device will be occupied during the backup process. Therefore, the host device needs to be considered in the process of generating the backup strategy.
  • the resource occupancy status at the current backup time is the backup client.
  • the backup strategy includes at least one of the disk file merging direction and the disk file merging depth of the device to be backed up.
  • the aforementioned device to be backed up may be a virtual machine.
  • the format of the disk file of the device to be backed up may be a quick emulator copy-on-write2 (qcow2) format or a raw format.
  • qcow2 quick emulator copy-on-write2
  • the device to be backed up is backed up at this time.
  • the disk file chain will become longer and longer, which will affect the disk read and write speed of the device to be backed up. Reduce the success rate of data backup.
  • redundant disk file nodes need to be merged to shorten the length of the disk file chain.
  • the original node of the virtual machine disk is vm-baseRW, which is a virtual machine running node, and its attribute is Read and Write (RW).
  • vm-baseRO is the node that needs full backup (the first backup of the virtual machine must be a full backup).
  • the backup task request comes again, and an additional node vm-snap2RW is still needed to be used as the virtual machine running node, and the original vm-snap1RW becomes a read-only node vm-snap1RO.
  • vm -snap1RO is the node that has changed incrementally since the first full backup. If it is a full backup at this time, copy vm-baseRO and vm-snap1RO to the backup repository. If it is an incremental backup at this time, only copy vm- snap1RO to the backup repository, so that after each backup, a file node will be added. As the number of backups increases, the file node chain will become longer and longer.
  • the above-mentioned merging direction of the disk files of the device to be backed up includes upward merging or downward merging.
  • upward merging refers to merging the data in the vm-snap1RO node into the vm-baseRO node
  • down Merging is to merge the data in the vm-baseRO node into the vm-snap1RO node.
  • the above-mentioned merging depth of disk files of the device to be backed up refers to timely merging or delayed merging.
  • the computer device may determine the disk file merging direction of the device to be backed up based on the comparison result between the data increment of the device to be backed up at the current backup time relative to the previous backup time and the data volume at the current backup time.
  • the process of the computer device determining the merging direction of the disk files of the device to be backed up may be: when the data increment does not exceed the amount of data at the last backup time, determining the merging of the disk files of the device to be backed up The direction is upward merging; when the data increment exceeds the amount of data at the last backup time, it is determined that the merging direction of the disk files of the device to be backed up is downward merging.
  • the data in the vm-baseRO node when the amount of data in the vm-snap1RO node is greater than the amount of data in the vm-baseRO node, the data in the vm-baseRO node can be merged down to the vm-snap1RO node; when the vm -The amount of data in the snap1RO node is less than or equal to the amount of data in the vm-baseRO node, and the data in the vm-snap1RO node can be merged upwards into the vm-baseRO node.
  • the computer device can determine the disk file consolidation depth of the device to be backed up based on the amount of data at the current backup moment of the device to be backed up. For example, the data volume of the device to be backed up at the current backup time exceeds the preset threshold, the disk file merge depth of the device to be backed up is delayed merge, the data volume of the device to be backed up at the current backup time does not exceed the preset threshold, and the disk file of the device to be backed up The depth of merger is timely merger.
  • the backup strategy also includes the selection of the target host device; in the case of multiple host devices, the computer device can be based on the data volume at the current backup time and the multiple host devices at the current backup time.
  • the amount of resources, the target host device is determined from the plurality of host devices, so as to execute the current backup task of the device to be backed up through the backup terminal in the target host device.
  • the preset threshold when the data volume of the device to be backed up at the current backup time is greater than the preset threshold, you can select a target host device that has a large amount of resources and is idle to serve the backup task of the device to be backed up; when the data volume of the device to be backed up at the current backup time is not When the preset threshold is exceeded, a target host device with a small amount of resources and not too busy can be selected to serve the backup task of the device to be backed up.
  • the computer device sends an instruction for the backup device to be backed up to the backup terminal in the target host device, so that the backup terminal can use the resources provided by the target host device to obtain the waiting information from the storage library through the backup proxy interface.
  • the data of the device is backed up, and the obtained data is sent to the backup storage library in the backup server, thereby completing the data backup of the device to be backed up.
  • the computer device can determine based on the acquired data increment, the data volume at the current backup time, the data volume at the previous backup time, and the resource volume of at least one host device at the current backup time
  • the backup terminal in the host device sends an instruction for the backup device to be backed up.
  • the backup strategy is determined based on the actual operating information of the device to be backed up and the host device, rather than a strategy formulated artificially, that is, the backup strategy determined in this application matches the actual operating information of the device to be backed up and the host device, avoiding In order to improve the success rate of data backup, it also reduces the duration of data backup.
  • the aforementioned backup strategy also includes a backup rate limit.
  • the above S102 may include: obtaining the network bandwidth utilization rate of the system to be backed up where the device to be backed up is located at the current backup time; according to the data increment, the amount of data at the current backup time, and the data at the previous backup time.
  • the amount of resources, the resource amount of the host device at the current backup moment, and the network bandwidth utilization rate of the system to be backed up at the current backup moment determine the backup strategy of the device to be backed up at the current backup moment.
  • the computer device can determine a backup speed limit strategy for the device to be backed up based on the network bandwidth utilization rate of the system to be backed up at the current backup moment.
  • the backup rate limit strategy can be 30MB/S, 50MB/S, or 100MB/S for data backup, or other rates.
  • the backup rate is limited, and when the obtained network bandwidth utilization is lower than the preset threshold, the backup rate can be appropriately increased.
  • the aforementioned system to be backed up may be a virtualized data center.
  • the computer device can also determine the backup strategy based on the network bandwidth utilization at the current backup time, so that the backup rate can be automatically and flexibly adjusted based on the network bandwidth utilization during the backup process, thereby avoiding transmission channel congestion and improving data backup.
  • the success rate can be also determined based on the network bandwidth utilization at the current backup time, so that the backup rate can be automatically and flexibly adjusted based on the network bandwidth utilization during the backup process, thereby avoiding transmission channel congestion and improving data backup. The success rate.
  • the basic backup strategy of the device to be backed up can be obtained through a data backup strategy generating device.
  • the basic backup strategy can include the start time of the data backup of the device to be backed up, and whether the data backup is a full backup or an incremental backup.
  • the following embodiment describes the process of determining the basic backup strategy of the device to be backed up. Based on the above embodiment, optionally, before the above S101, as shown in FIG. 4, the method may further include:
  • the generation period of the backup strategy can be set according to the actual situation.
  • the computer device When the generation time of the backup strategy arrives, the computer device generates the basic backup strategy for the device to be backed up.
  • the above-mentioned data volume at the time of generation refers to the total amount of data in the disk of the device to be backed up at the time of generation.
  • the above data increment within the preset time refers to the amount of data change in the disk of the device to be backed up within the preset time since the last backup, including data added, deleted and/or modified in the disk of the device to be backed up The amount of change.
  • the aforementioned resource amount at the time of generation refers to the CPU occupancy and memory occupancy of the host device at the time of generation.
  • the data increment within the preset time, the amount of resources at the time of generation, and the network bandwidth utilization rate at the time of generation determine the The basic backup strategy of the device to be backed up, where the basic backup strategy includes the start time of the backup and the selection of either full backup or incremental backup.
  • the basic backup strategy may also include a backup period, etc.
  • the computer device may determine the basic backup strategy of the device to be backed up based on the following recommended algorithm.
  • the computer device determines whether to perform full backup or incremental backup for the device to be backed up based on the data increment within the preset time of the device to be backed up and the data volume of the device to be backed up at the time of generation. For example, when the data increment of the device to be backed up within the preset time is less than the preset proportion of the data volume of the device to be backed up at the time of generation, the computer device determines to perform an incremental backup of the device to be backed up.
  • the aforementioned preset ratio may be one thousandth.
  • the computer device can recommend to back up the device to be backed up once a week, and during non-peak hours Segment for backup.
  • the preset threshold can be 100MB
  • the computer device can recommend backing up the device to be backed up once a day, and the backup time can be determined segment.
  • the computer The device determines that the device to be backed up is fully backed up.
  • the computer device can output the devices to be backed up that can be backed up during the time period according to the network bandwidth utilization rate at the time of generation, and determine the corresponding backup based on the amount of data to be backed up at the time of generation and the network bandwidth utilization rate at the time of generation. rate.
  • the generation time can be the current backup time.
  • the foregoing S202 may be: according to the amount of data at the time of generation, the data increment within the preset time, the amount of resources at the time of generation, and the amount of resources at the time of generation.
  • a preset recommendation algorithm is used to determine the backup strategy set to be recommended; combined with the historical backup strategy set by the user, a target backup strategy is selected from the backup strategy set to be recommended as the basic backup strategy.
  • the computer device can generate a basic backup strategy for the device to be backed up based on the operating information of the device to be backed up and the host device at the time the backup strategy is generated, and the network bandwidth utilization rate at the time of generation, so that the generated basic backup strategy Matching with the operating status of the production system where the device to be backed up and the host device are located, the generated basic backup strategy is more reasonable than the artificially formulated basic backup strategy, thereby further improving the success rate of data backup.
  • the method further includes: sending an instruction for merging disk files to the device to be backed up according to the backup strategy.
  • the device to be backed up merges the disk file nodes according to the disk file merging direction and the disk file merging depth in the backup strategy.
  • the computer device can send an instruction for merging disk files to the device to be backed up based on the backup strategy, so that after the current backup task ends, the device to be backed up will follow the disk file merging direction and the disk file merging direction in the backup strategy.
  • File merging depth, merging disk file nodes thereby improving the disk read and write speed of the device to be backed up, and also further improving the success rate of data backup.
  • the method may include:
  • the basic backup strategy of the virtual machine includes the start time of the backup and the selection of one of the full backup and the incremental backup.
  • S304 Determine the sub-backup strategy of the virtual machine at the current backup time according to the data increment, the data volume at the current backup time, the data volume at the last backup time, and the resource volume of the at least one host device at the current backup time.
  • the sub-backup strategy includes at least one of the disk file merging direction of the virtual machine, the disk file merging depth, and the selection of the target host device.
  • the above S304 may include: obtaining the network bandwidth utilization of the system to be backed up where the virtual machine is located at the current backup time; according to the data increment, the data volume at the current backup time, and the data volume at the previous backup time , The resource amount of the at least one host device at the current backup time and the network bandwidth utilization rate of the virtualized data center at the current backup time, determine the sub-backup policy at the current backup time of the virtual machine, and the sub-backup policy also Including backup speed limit.
  • a basic backup strategy can be generated for each virtual machine in the virtualized data center, and multiple sub-backup strategies can be generated for each virtual machine.
  • the sub-backup strategy is used to expand the basic backup strategy, and the sub-backup strategy includes virtual At least one of the merging direction of the disk files of the computer, the depth of disk file merging, the selection of the target host device, and the backup speed limit.
  • the virtualized data center includes multiple virtual machines, and the computer equipment determines a basic backup strategy for each virtual machine (the basic backup strategy is the basic strategy in Figure 6). In this way, virtual machine 1, virtual machine 2...
  • Virtual machine m is bound to basic backup strategy 1 (strategy 1 in Figure 6), virtual machine m+1, virtual machine m+2...Virtual machine q is bound to basic backup strategy 2 (strategy 2 in Figure 6), virtual machine t+1, virtual machine t+2...Virtual machine w is bound to a basic backup strategy n (strategy n in Figure 6).
  • basic backup strategy 1 the basic backup strategy 1
  • virtual machine m+1, virtual machine m+2...Virtual machine q is bound to basic backup strategy 2 (strategy 2 in Figure 6)
  • virtual machine t+1, virtual machine t+2...Virtual machine w is bound to a basic backup strategy n (strategy n in Figure 6).
  • virtual machine 1 is bound to sub-backup policies ab, ba, ca, and db
  • virtual machine 2 is bound to sub-backup policies aa, bb, ca, and da, etc.
  • virtual machine m is bound Sub-backup strategies aa, ba, cb, and dc, etc.
  • virtual machine m+1 binds sub-backup strategies ab, bb, ca, and da, etc.
  • virtual machine m+2 binds sub-backup strategies aa, ba, ca, and db, etc.
  • Virtual machine q is bound to child backup policies ab, ba, ca, and db
  • virtual machine t+1 is bound to child backup policies aa, bb, ca, and db
  • virtual machine t+2 is bound to child backup policies ab, ba, cb and dc, etc.
  • the virtual machine w binds sub-backup strategies aa, ba, ca, da, etc.
  • the sub-backup strategy includes qcow2 file node chain merging mode (aa: upward merge, ab: downward merge), qcow2 file chain depth control (ba: timely merge, bb: delayed merge), target host device selection (ca: resource bandwidth Large allocation, cb: small allocation of resource bandwidth) (ie the selection of task processing nodes in Figure 6), backup speed limit strategy (da: speed limit 30MB/S, db: speed limit 50MB/S, dc: speed limit 100MB/ S).
  • S305 According to the basic backup strategy and the sub-backup strategy, send an instruction for backing up the virtual machine to the backup terminal in the target host device.
  • an instruction for backing up the virtual machine is sent to the backup terminal in the target host device, so that the backup terminal can use the resources of the target host device to perform operations on the virtual machine based on the basic backup strategy and the sub-backup strategy.
  • Data is backed up.
  • the device to be backed up merges the disk file nodes according to the disk file merging direction and the disk file merging depth in the sub-backup strategy.
  • the computer device can automatically set a basic backup strategy for the device to be backed up, and based on the basic backup strategy and the actual operation information of the device to be backed up and the host device, set a sub-backup strategy for the device to be backed up, so that the In the process, data is backed up based on the above-determined basic backup strategy and sub-backup strategy, which avoids the irrationality of artificially formulated backup strategies, thereby increasing the success rate of data backup and reducing the duration of data backup.
  • FIG. 7 is a schematic structural diagram of a data backup device provided by an embodiment of the application. As shown in FIG. 7, the device may include: a first acquiring module 20, a first determining module 21, and a first sending module 22.
  • the first acquiring module 20 is configured to acquire the data increment of the current backup time of the device to be backed up relative to the last backup time, the data volume at the current backup time and the data volume at the last backup time, and the data volume of at least one host device at the current backup time.
  • the amount of resources; the device to be backed up runs on one of the at least one host device, and a backup terminal is installed on each of the at least one host device; the first determining module 21 is set to be based on the data increment, The amount of data at the current backup moment, the amount of data at the last backup moment, and the resource amount of the at least one host device at the current backup moment determine the backup strategy of the device to be backed up at the current backup moment, and the backup strategy includes the backup strategy.
  • the first sending module 22 is configured to send a message to the backup terminal in one of the at least one host device according to the backup strategy An instruction to back up the device to be backed up.
  • the data backup device provided by the embodiment of the application can determine the data to be backed up based on the acquired data increment, the data volume at the current backup time, the data volume at the last backup time, and the resource volume of at least one host device at the current backup time.
  • the backup strategy at the current backup moment of the device, the backup strategy includes at least one of the disk file merging direction and the disk file merging depth of the device to be backed up, and based on the determined backup strategy, the backup strategy is sent to one of the at least one host device
  • the backup terminal in the device sends an instruction for backing up the device to be backed up.
  • the backup strategy is determined based on the actual operating information of the device to be backed up and the host device, rather than a strategy formulated artificially, that is, the backup strategy determined in this application matches the actual operating information of the device to be backed up and the host device, avoiding In order to improve the success rate of data backup, it also reduces the duration of data backup.
  • the backup strategy further includes a backup rate limit; the first determining module 21 is configured to obtain the network bandwidth of the system to be backed up where the device to be backed up is located at the current backup moment Utilization rate; according to the data increment, the data volume at the current backup time, the data volume at the last backup time, the resource volume of the at least one host device at the current backup time, and the network of the system to be backed up at the current backup time The bandwidth utilization rate determines the backup strategy at the current backup moment of the device to be backed up.
  • the device further includes: a second acquiring module and a second determining module.
  • the second acquisition module is configured to acquire, in the first acquisition module 20, the data increment of the current backup time of the device to be backed up relative to the previous backup time, the data volume at the current backup time, and the data volume at the previous backup time, and the At least one host device obtains the amount of data of the device to be backed up at the time of generation, the data increment of the device to be backed up within a preset time when the generation time of the backup strategy arrives before the amount of resources at the current backup time, The resource amount of the at least one host device at the generation time and the network bandwidth utilization rate of the system to be backed up where the device to be backed up is located at the generation time; the second determining module is set to, according to the data amount at the generation time, The data increment within the preset time, the amount of resources at the time of generation, and the network bandwidth utilization at the time of generation are determined by a preset recommendation algorithm to determine the basic backup strategy of the device to be backed up, and the basic The backup strategy includes the start time of the backup and the choice of either
  • the second determining module is set to be based on the amount of data at the generation time, the data increment within the preset time, the amount of resources at the generation time, and the generation
  • the network bandwidth utilization at all times is determined by the preset recommendation algorithm to determine the backup strategy set to be recommended; combined with the historical backup strategy set by the user, a target backup strategy is selected from the backup strategy set to be recommended as the basic backup strategy .
  • the first determining module 21 is set to When the data increment does not exceed the data amount at the last backup time, it is determined that the merging direction of the disk files of the device to be backed up is upward merge; when the data increment exceeds the data amount at the last backup time, It is determined that the merging direction of the disk files of the device to be backed up is downward merging.
  • the backup strategy further includes the selection of the target host device; the first determining module 21 is set to be based on the current backup time when the number of host devices is multiple The data volume of the multiple host devices and the resource volume of the multiple host devices at the current backup moment, the target host device is determined from the multiple host devices, so that the backup terminal in the target host device executes the localization of the device to be backed up Backup tasks.
  • the device further includes: a second sending module.
  • the second sending module is configured to send an instruction for merging disk files to the device to be backed up according to the backup strategy.
  • the system to be backed up is a virtualized data center, and the device to be backed up is a virtual machine.
  • a computer device in one embodiment, is provided, and its internal structure diagram may be as shown in FIG. 8.
  • the computer equipment includes a processor, a memory, a network interface, and a database connected through a system bus.
  • the processor of the computer device is used to provide calculation and control capabilities.
  • the memory of the computer device includes a non-volatile storage medium and an internal memory.
  • the non-volatile storage medium stores an operating system, a computer program, and a database.
  • the internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium.
  • the database of the computer equipment is set to store the data during the data backup process.
  • the network interface of the computer device is set to communicate with an external terminal through a network connection.
  • the computer program is executed by the processor to realize a data backup method.
  • FIG. 8 is only a block diagram of part of the structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied.
  • the computer equipment may include More or fewer components are shown in the figure, or some components are combined, or have different component arrangements.
  • a computer device including a memory and a processor, and a computer program is stored in the memory.
  • the processor executes the computer program, the following steps are implemented: Obtain the current backup time of the device to be backed up relative to the previous backup time The data increment at the current backup time, the data volume at the last backup time, and the resource volume of at least one host device at the current backup time; the device to be backed up runs on one of the at least one host device A backup terminal is installed on each of the at least one host device; according to the data increment, the amount of data at the current backup moment, the amount of data at the last backup moment, and the resource of the at least one host device at the current backup moment Determine the backup strategy at the current backup moment of the device to be backed up, where the backup strategy includes at least one of the disk file merging direction and the disk file merging depth of the device to be backed up; The backup terminal in one of the at least one host device sends an instruction for backing up the device to be backed up.
  • the backup strategy further includes a backup rate limit; when the processor executes the computer program, the following steps are also implemented: obtain the network bandwidth utilization rate of the system to be backed up where the device to be backed up is located at the current backup moment; The data increment, the data volume at the current backup time, the data volume at the last backup time, the resource volume of the at least one host device at the current backup time, and the network bandwidth utilization rate of the system to be backed up at the current backup time are determined The backup strategy at the current backup moment of the device to be backed up.
  • the processor further implements the following steps when executing the computer program: when the generation time of the backup strategy arrives, obtain the amount of data of the device to be backed up at the time of generation, and the amount of data of the device to be backed up within a preset time.
  • the processor further implements the following steps when executing the computer program: according to the amount of data at the time of generation, the data increment within the preset time, the amount of resources at the time of generation, and the amount of resources at the time of generation.
  • a preset recommendation algorithm is used to determine the backup strategy set to be recommended; combined with the historical backup strategy set by the user, a target backup strategy is selected from the backup strategy set to be recommended as the basic backup strategy.
  • the processor when the backup strategy includes the merging direction of the disk files of the device to be backed up and the selection of the target host device, the processor further implements the following steps when executing the computer program: when the data increment does not exceed When the amount of data at the last backup moment is determined, the merging direction of the disk files of the device to be backed up is determined to be upward merge; when the data increment exceeds the amount of data at the last backup moment, it is determined that the to-be-backed up The merging direction of the device's disk files is downward merging.
  • the backup strategy further includes the selection of the target host device; in the case of multiple host devices, according to the data volume at the current backup time and the resources of the multiple host devices at the current backup time
  • the target host device is determined from the plurality of host devices, so as to execute the current backup task of the device to be backed up through the backup terminal in the target host device.
  • the processor further implements the following step when executing the computer program: according to the backup strategy, sending an instruction for merging disk files to the device to be backed up.
  • system to be backed up is a virtualized data center
  • device to be backed up is a virtual machine
  • a computer-readable storage medium on which a computer program is stored.
  • the computer program is executed by a processor, the following steps are implemented: Obtain the data increase of the device to be backed up at the current backup time relative to the previous backup time.
  • the amount of data at the current backup moment and the amount of data at the last backup moment, and the amount of resources of at least one host device at the current backup moment; the device to be backed up runs on one of the at least one host device, the A backup terminal is installed on each of the at least one host device; determining according to the data increment, the amount of data at the current backup moment, the amount of data at the last backup moment, and the resource amount of the at least one host device at the current backup moment
  • the backup terminal in one of the host devices in the device sends an instruction for backing up the device to be backed up.
  • the backup strategy further includes a backup rate limit; when the computer program is executed by the processor, the following steps are also implemented: obtain the network bandwidth utilization rate of the system to be backed up where the device to be backed up is located at the current backup time; The data increment, the data volume at the current backup time, the data volume at the last backup time, the resource volume of the at least one host device at the current backup time, and the network bandwidth utilization rate of the system to be backed up at the current backup time, Determine the backup strategy at the current backup moment of the device to be backed up.
  • the following steps are also implemented: when the generation time of the backup strategy arrives, obtain the data volume of the device to be backed up at the generation time, and the device to be backed up within a preset time The data increment of the at least one host device at the time of generation, and the network bandwidth utilization of the system to be backed up where the device to be backed up is located at the time of generation; according to the amount of data at the time of generation, the amount of resources According to the data increment within the preset time, the amount of resources at the time of generation, and the network bandwidth utilization at the time of generation, the basic backup strategy of the device to be backed up is determined through a preset recommendation algorithm, and the basic backup The strategy includes the start time of the backup and the choice of either full backup or incremental backup.
  • the following steps are further implemented: according to the amount of data at the time of generation, the data increment within the preset time, the amount of resources at the time of generation, and the time of generation
  • the network bandwidth utilization rate of the network is determined by a preset recommendation algorithm to determine the backup strategy set to be recommended; combined with the historical backup strategy set by the user, a target backup strategy is selected from the backup strategy set to be recommended as the basic backup strategy.
  • the computer program when the backup strategy includes the merging direction of the disk files of the device to be backed up and the selection of the target host device, the computer program is executed by the processor and further implements the following steps: when the data increment is not When the data volume exceeds the last backup time, it is determined that the merging direction of the disk files of the device to be backed up is upward merge; when the data increment exceeds the data volume at the previous backup time, it is determined that The merging direction of the disk files of the backup device is downward merging.
  • the backup strategy further includes the selection of the target host device; in the case of multiple host devices, according to the data volume at the current backup time and the resources of the multiple host devices at the current backup time
  • the target host device is determined from the plurality of host devices, so as to execute the current backup task of the device to be backed up through the backup terminal in the target host device.
  • the following steps are further implemented: according to the backup strategy, an instruction for merging disk files is sent to the device to be backed up.
  • system to be backed up is a virtualized data center
  • device to be backed up is a virtual machine
  • the data backup device, computer equipment, and storage medium provided in the foregoing embodiments can perform the data backup method provided in any embodiment of the present application.
  • the data backup method provided in any embodiment of this application.
  • Computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages Source code or object code.
  • ISA Instruction Set Architecture
  • the block diagram of any logic flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions.
  • the computer program can be stored on the memory.
  • the memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as but not limited to read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disc (CD)), etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field Programmable Gate Array, FPGA), and processors based on multi-core processor architecture.
  • DSP digital signal processors
  • ASICs application specific integrated circuits
  • FPGA Field Programmable Gate Array

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)

Abstract

一种数据备份的方法、装置、设备和存储介质,该方法包括:获取待备份设备当前备份时刻相对于上一备份时刻的数据增量、当前备份时刻的数据量和上一备份时刻的数据量,以及至少一个主机设备在当前备份时刻的资源量(S101);根据数据增量、当前备份时刻的数据量、上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定待备份设备当前备份时刻备份策略,备份策略包括待备份设备磁盘文件合并方向和磁盘文件合并深度中的至少一种(S102);根据备份策略,向所述至少一个主机设备中的一个主机设备中的备份终端发送用于对待备份设备进行备份的指示(S103)。

Description

数据备份的方法和装置、设备和存储介质
本申请要求在2019年11月26日提交中国专利局、申请号为201911175589.8的中国专利申请的优先权,该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域,例如涉及一种数据备份的方法和装置、设备和存储介质。
背景技术
众所周知,数据备份是一种防止数据丢失,提高数据安全的重要手段。以虚拟化数据中心的数据备份为例,虚拟机的数据备份功能是必不可少的,例如,在虚拟机的磁盘发生异常损坏、磁盘数据丢失和/或用户误操作时,能够使用备份数据对虚拟机的数据进行恢复。传统技术中,数据的备份策略通常由用户根据经验进行设置。但是,传统方式会导致备份策略设置不合理,进而导致数据备份的成功率较低,且数据备份所耗时间较长。
发明内容
本申请提供用于一种数据备份的方法和装置、设备和存储介质。
提供一种数据备份的方法,包括:
获取待备份设备当前备份时刻相对于上一备份时刻的数据增量、当前备份时刻的数据量和上一备份时刻的数据量,以及至少一个主机设备在当前备份时刻的资源量;所述待备份设备在所述至少一个主机设备中的一个上运行,所述至少一个主机设备的每一个上安装有备份终端;
根据所述数据增量、当前备份时刻的数据量、上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定所述待备份设备当前备份时刻的备份策略,所述备份策略包括所述待备份设备的磁盘文件合并方向和磁盘文件合并深度中的至少一种;
根据所述备份策略,向所述至少一个主机设备中的一个主机设备中的备份终端发送用于对所述待备份设备进行备份的指示。
还提供一种数据备份的装置,包括:
第一获取模块,设置为获取待备份设备当前备份时刻相对于上一备份时刻 的数据增量、当前备份时刻的数据量和上一备份时刻的数据量,以及至少一个主机设备在当前备份时刻的资源量;所述待备份设备在所述至少一个主机设备中的一个上运行,所述至少一个主机设备的每一个上安装有备份终端;
第一确定模块,设置为根据所述数据增量、当前备份时刻的数据量、上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定所述待备份设备当前备份时刻的备份策略,所述备份策略包括所述待备份设备的磁盘文件合并方向和磁盘文件合并深度中的至少一种;
第一发送模块,设置为根据所述备份策略,向所述至少一个主机设备中的一个主机设备中的备份终端发送用于对所述待备份设备进行备份的指示。
还提供一种计算机设备,包括存储器和处理器,所述存储器存储有计算机程序,所述处理器执行所述计算机程序时实现本申请实施例提供的数据备份的方法。
还提供一种存储介质,所述存储介质存储有计算机程序,所述计算机程序被处理器执行时实现本申请实施例提供的数据备份的方法。
附图说明
图1为本申请实施例提供的数据备份的方法应用的系统架构图;
图2为本申请实施例提供的数据备份的方法的一种流程示意图;
图3为本申请实施例提供的数据备份时虚拟机的qcow2外置快照磁盘文件链的变化示意图;
图4为本申请实施例提供的数据备份的方法的另一种流程示意图;
图5为本申请实施例提供的数据备份的方法的又一种流程示意图;
图6为本申请实施例提供的虚拟机的备份策略示意图;
图7为本申请实施例提供的数据备份的装置的结构示意图;
图8为本申请实施例提供的计算机设备的结构示意图。
具体实施方式
本申请实施例提供的数据备份的方法,可以适应于如图1所示的系统,该系统可以包括数据备份策略的生成装置10和待备份系统11。待备份系统11中包括待备份设备110和主机设备111,待备份设备110运行在主机设备111上,主机设备111上安装有备份客户端。上述数据备份策略的生成装置10设置为生成备份策略,备份客户端基于生成的备份策略通过主机设备111上的备份代理 接口从存储库(该存储库可以为磁盘阵列)中获取待备份设备110的数据,发送给备份服务器,以实现对待备份设备110的数据备份。
下文中将结合附图对本申请的实施例进行说明。需要说明的是,在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互任意组合。
需要说明的是,下述方法实施例的执行主体可以是数据备份的装置,该装置可以通过软件、硬件或者软硬件结合的方式实现成为计算机设备的部分或者全部。下述方法实施例以执行主体是计算机设备为例进行说明。
图2为本申请实施例提供的数据备份的方法的一种流程示意图。本实施例涉及的是计算机设备如何根据待备份设备和主机设备的运行信息,确定备份策略的过程。如图2所示,该方法可以包括:
S101、获取待备份设备当前备份时刻相对于上一备份时刻的数据增量、当前备份时刻的数据量和上一备份时刻的数据量,以及至少一个主机设备在当前备份时刻的资源量;所述待备份设备在所述至少一个主机设备中的一个上运行,所述至少一个主机设备的每一个上安装有备份终端。
计算机设备可以通过备份服务器中设置的基础备份策略获知待备份设备的当前备份时刻以及上一备份时刻。备份服务器可以通过用户设置的备份相关内容获取基础备份策略,还可以通过数据备份策略的生成装置输出的策略获取基础备份策略,本实施例对基础备份策略的获取方式不做限定。基础备份策略可以包括待备份设备的数据备份的开始时间,以及数据备份是全量备份还是增量备份等。全量备份是指对待备份设备的磁盘中的所有数据进行备份,增量备份是指对待备份设备的磁盘中的增量数据进行备份,增量数据为上次备份之后,所述待备份设备的磁盘中增加、删除和/或修改的数据。
上述数据增量是指待备份设备在当前备份时刻相对于上一备份时刻的数据变化量,包括待备份设备的磁盘中增加、删除和/或修改的数据的变化量。上述当前时刻的数据量与对待备份设备进行全量备份还是增量备份相关,当当前备份时刻对待备份设备进行全量备份时,上述当前时刻的数据量为待备份设备的磁盘中的全部数据的数据量,当当前备份时刻对待备份设备进行增量备份时,上述当前时刻的数据量为相对于上一备份时刻待备份设备的磁盘中的数据变化量。上述上一备份时刻的数据量是指在上一备份时刻待备份设备的磁盘中的全部数据量。上述主机设备在当前备份时刻的资源量包括在当前备份时刻主机设备的中央处理器(Central Processing Unit,CPU)占用情况、内存占用情况等。上述备份终端即为备份客户端,由于备份客户端安装在主机设备上,这样,在备份过程中会占用主机设备的CPU以及内存等资源,因此,在生成备份策略的过程中,需要考虑主机设备在当前备份时刻的资源占用情况。
S102、根据所述数据增量、当前备份时刻的数据量、上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定所述待备份设备当前备份时刻的备份策略,所述备份策略包括所述待备份设备的磁盘文件合并方向和磁盘文件合并深度中的至少一种。
上述待备份设备可以为虚拟机。待备份设备的磁盘文件的格式可以为快速模拟器写时拷贝2(quick emulator copy-on-write2,qcow2)格式或raw格式。当待备份设备的磁盘采用qcow2外置快照时,此时对待备份设备进行数据备份,随着备份次数的增加,磁盘文件链会越来越长,影响待备份设备的磁盘读写速度,也会降低数据备份的成功率,此时需要对冗余的磁盘文件节点做合并处理从而缩短磁盘文件链的长度。以下以待备份设备为虚拟机(Virtual Machine,VM)为例,介绍虚拟机磁盘采用qcow2外置快照进行数据备份时,磁盘文件链的变化情况。如图3所示,虚拟机磁盘原始节点为vm-baseRW,该节点为虚拟机运行节点,其属性是可读可写(Read and Write,RW)。当需要对正在运行的虚拟机进行备份时,需要拉出来一个额外的节点vm-snap1RW作为虚拟机运行节点,而原来的vm-baseRW则变为只读(Read-Only,RO)节点vm-baseRO,此时vm-baseRO即为需要全量备份的节点(虚拟机首次备份一定是一次全量备份)。当虚拟机运行一段时间后,备份任务请求再次到来,仍然需要拉出来一个额外的节点vm-snap2RW作为虚拟机运行节点,而原来的vm-snap1RW则变为只读节点vm-snap1RO,此时vm-snap1RO即为较第一次全量备份后增量变化的节点,如果此时是全量备份则拷贝vm-baseRO和vm-snap1RO至备份存储库,如果此时是增量备份则只需拷贝vm-snap1RO至备份存储库,这样,每次备份后都会增加一个文件节点,随着备份次数的增加,文件节点链会越来越长。
上述待备份设备的磁盘文件合并方向包括向上合并或向下合并,继续以图3所示的例子为例,向上合并是指将vm-snap1RO节点中的数据合并到vm-baseRO节点中,向下合并是将vm-baseRO节点中的数据合并到vm-snap1RO节点中。上述待备份设备的磁盘文件合并深度是指及时合并或延时合并。
计算机设备可以基于待备份设备当前备份时刻相对于上一备份时刻的数据增量与当前备份时刻的数据量之间的比较结果,确定待备份设备的磁盘文件合并方向。可选的,计算机设备确定待备份设备的磁盘文件合并方向的过程可以为:当所述数据增量不超过所述上一备份时刻的数据量时,确定所述待备份设备的磁盘文件的合并方向为向上合并;当所述数据增量超过所述上一备份时刻的数据量时,确定所述待备份设备的磁盘文件的合并方向为向下合并。继续以图3中的例子为例,当vm-snap1RO节点中的数据量大于vm-baseRO节点中的数据量,可以将vm-baseRO节点中的数据向下合并到vm-snap1RO节点中;当vm-snap1RO节点中的数据量小于或等于vm-baseRO节点中的数据量,可以将 vm-snap1RO节点中的数据向上合并到vm-baseRO节点中。
另外,计算机设备可以基于待备份设备当前备份时刻的数据量,确定待备份设备的磁盘文件合并深度。例如,待备份设备当前备份时刻的数据量超过预设阈值,待备份设备的磁盘文件合并深度为延时合并,待备份设备当前备份时刻的数据量不超过预设阈值,待备份设备的磁盘文件合并深度为及时合并。
可选的,备份策略还包括目标主机设备的选择;在主机设备的数量为多个的情况下,计算机设备可以根据所述当前备份时刻的数据量和所述多个主机设备在当前备份时刻的资源量,从所述多个主机设备中确定目标主机设备,以通过所述目标主机设备中的备份终端执行所述待备份设备的本次备份任务。例如,当待备份设备当前备份时刻的数据量大于预设阈值时,可以选择资源量大,且空闲的目标主机设备为待备份设备的备份任务服务;当待备份设备当前备份时刻的数据量不超过预设阈值时,可以选择资源量较小,且不太繁忙的目标主机设备为待备份设备的备份任务服务。
S103、根据所述备份策略,向所述至少一个主机设备中的一个主机设备中的备份终端发送用于对所述待备份设备进行备份的指示。
计算机设备根据上述确定出的备份策略,向目标主机设备中的备份终端发送用于对待备份设备进行备份的指示,以使备份终端利用目标主机设备提供的资源通过备份代理接口从存储库中获取待备份设备的数据,并将获取的数据发送至备份服务器中的备份存储库中,从而完成对待备份设备的数据备份。
本申请实施例提供的数据备份的方法,计算机设备能够基于获取到的数据增量、当前备份时刻的数据量、上一备份时刻的数据量以及至少一个主机设备在当前备份时刻的资源量,确定待备份设备当前备份时刻的备份策略,备份策略包括待备份设备的磁盘文件合并方向和磁盘文件合并深度中的至少一种,并基于确定出的备份策略,向所述至少一个主机设备中的一个主机设备中的备份终端发送用于对待备份设备进行备份的指示。由于备份策略是基于待备份设备和主机设备的实际运行信息确定出的,而非人为制定的策略,即本申请所确定出的备份策略与待备份设备和主机设备的实际运行信息相匹配,避免了人为制定的备份策略的不合理性,从而提高了数据备份的成功率,同时也降低了数据备份的时长。
在实际应用中,受限于数据传输的带宽,为了避免由于传输过程中的数据量超过带宽上限,从而造成拥塞,进而降低数据备份的成功率的技术问题,即为了进一步提高数据备份的成功率,可选的,上述备份策略还包括备份限速。针对此情况,上述S102可以包括:获取所述待备份设备所在的待备份系统在当前备份时刻的网络带宽利用率;根据所述数据增量、当前备份时刻的数据量、 上一备份时刻的数据量、主机设备在当前备份时刻的资源量以及所述待备份系统在当前备份时刻的网络带宽利用率,确定所述待备份设备当前备份时刻的备份策略。
计算机设备可以基于待备份系统在当前备份时刻的网络带宽利用率,为待备份设备确定备份限速策略。例如,备份限速策略可以为以30MB/S、50MB/S或100MB/S的速率进行数据备份,也可以为其它速率。在实际备份过程中,在获取的网络带宽利用率达到预设的阈值的情况下,限制备份速率,在获取的网络带宽利用率低于预设的阈值的情况下,可以适当提高备份速率。可选的,上述待备份系统可以为虚拟化数据中心。
在本实施例中,计算机设备还可以根据当前备份时刻的网络带宽利用率确定备份策略,使得备份过程中可以基于网络带宽利用率自动灵活地调整备份速率,从而避免传输通道拥塞,进而提高数据备份的成功率。
在实际应用中,待备份设备的基础备份策略可以通过数据备份策略的生成装置得到,基础备份策略可以包括待备份设备的数据备份的开始时间,以及数据备份是全量备份还是增量备份等。下述实施例介绍待备份设备的基础备份策略的确定过程,在上述实施例的基础上,可选的,在上述S101之前,如图4所示,该方法还可以包括:
S201、当备份策略的生成时刻到达时,获取待备份设备在所述生成时刻的数据量、所述待备份设备在预设时间内的数据增量、所述至少一个主机设备在所述生成时刻的资源量以及所述待备份设备所在的待备份系统在所述生成时刻的网络带宽利用率。
可以根据实际情况设置备份策略的生成周期,当备份策略的生成时刻到达时,计算机设备为待备份设备生成基础备份策略。上述生成时刻的数据量是指在生成时刻,待备份设备的磁盘中的全部数据量。上述在预设时间内的数据增量是指自上一次备份之后,在预设时间内待备份设备的磁盘中的数据变化量,包括待备份设备的磁盘中增加、删除和/或修改的数据的变化量。上述生成时刻的资源量是指在生成时刻主机设备的CPU占用情况、内存占用情况等。
S202、根据所述生成时刻的数据量、所述预设时间内的数据增量、所述生成时刻的资源量以及所述生成时刻的网络带宽利用率,通过预设的推荐算法,确定所述待备份设备的基础备份策略,所述基础备份策略包括备份的开始时间和对全量备份与增量备份二者之一的选择。
基础备份策略还可以包括备份周期等,计算机设备可以基于以下推荐算法确定待备份设备的基础备份策略。
计算机设备基于待备份设备预设时间内的数据增量与待备份设备在生成时刻的数据量,确定对待备份设备进行全量备份还是进行增量备份。例如,当待备份设备在预设时间内的数据增量小于待备份设备在生成时刻的数据量的预设比例时,计算机设备确定对待备份设备进行增量备份。可选的,上述预设比例可以为千分之一。当待备份设备磁盘中的每周数据变化量小于预设阈值(可选的,该预设阈值可以为100MB)时,计算机设备可以推荐对该待备份设备每周备份一次,且在非繁忙时间段进行备份。当待备份设备磁盘中的每周数据变化量大于预设阈值(可选的,该预设阈值可以为1TB)时,计算机设备可以推荐对该待备份设备每天备份一次,且可以确定备份的时间段。当待备份设备的磁盘在预设时间段内的数据增量大于待备份设备的磁盘中总的数据量的预设比例(可选的,该预设比例可以为二分之一)时,计算机设备确定对待备份设备进行全量备份。计算机设备可以根据生成时刻的网络带宽利用率输出在该时间段可以进行备份的待备份设备,同时根据待备份设备在生成时刻的待备份数据量以及生成时刻的网络带宽利用率,确定相应的备份速率。生成时刻可以为当前备份时刻。
也可以采用其它推荐算法确定待备份设备的基础备份策略,本实施例在此不再赘述。
在上述实施例的基础上,可选的,上述S202可以为:根据所述生成时刻的数据量、所述预设时间内的数据增量、所述生成时刻的资源量以及所述生成时刻的网络带宽利用率,通过预设的推荐算法,确定待推荐的备份策略集;结合用户设置的历史备份策略,从所述待推荐的备份策略集中选择一个目标备份策略作为所述基础备份策略。
在本实施例中,计算机设备可以基于备份策略生成时刻的待备份设备和主机设备的运行信息、以及生成时刻的网络带宽利用率,为待备份设备生成基础备份策略,使得所生成的基础备份策略与待备份设备和主机设备所在的生产系统的运行状态相匹配,相比人为制定的基础备份策略,所生成的基础备份策略更合理,从而进一步提高了数据备份的成功率。
在上述实施例的基础上,可选的,该方法还包括:根据所述备份策略,向所述待备份设备发送用于磁盘文件合并的指示。
在当前备份任务结束之后,待备份设备根据备份策略中的磁盘文件合并方向以及磁盘文件的合并深度,对磁盘文件节点进行合并。
在本实施例中,由于计算机设备可以基于备份策略,向待备份设备发送用于磁盘文件合并的指示,以使在当前备份任务结束之后,待备份设备根据备份策略中的磁盘文件合并方向以及磁盘文件的合并深度,对磁盘文件节点进行合 并,从而提高了待备份设备的磁盘读写速度,同时也进一步提高了数据备份的成功率。
为了便于本领域技术人员的理解,以下以待备份设备为虚拟机,待备份系统为虚拟化数据中心为例进行介绍,如图5所示,该方法可以包括:
S301、当备份策略的生成时刻到达时,获取虚拟机在所述生成时刻的数据量、所述虚拟机在预设时间内的数据增量、所述至少一个主机设备在所述生成时刻的资源量以及所述虚拟机所在的虚拟化数据中心在所述生成时刻的网络带宽利用率。
S302、根据所述生成时刻的数据量、所述预设时间内的数据增量、所述生成时刻的资源量以及所述生成时刻的网络带宽利用率,通过预设的推荐算法,确定所述虚拟机的基础备份策略,所述基础备份策略包括备份的开始时间和对全量备份与增量备份二者之一的选择。
S303、获取虚拟机当前备份时刻相对于上一备份时刻的数据增量、当前备份时刻的数据量和上一备份时刻的数据量,以及至少一个主机设备在当前备份时刻的资源量;所述虚拟机在所述至少一个主机设备中的一个上运行,所述至少一个主机设备的每一个上安装有备份终端。
S304、根据所述数据增量、当前备份时刻的数据量、上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定所述虚拟机当前备份时刻的子备份策略,所述子备份策略包括所述虚拟机的磁盘文件合并方向、磁盘文件合并深度以及目标主机设备的选择中的至少一种。
可选的,上述S304可以包括:获取所述虚拟机所在的待备份系统在当前备份时刻的网络带宽利用率;根据所述数据增量、当前备份时刻的数据量、上一备份时刻的数据量、所述至少一个主机设备在当前备份时刻的资源量以及所述虚拟化数据中心在当前备份时刻的网络带宽利用率,确定所述虚拟机当前备份时刻的子备份策略,所述子备份策略还包括备份限速。
通过上述过程,可以为虚拟化数据中心中的每个虚拟机生成基础备份策略,同时又为每个虚拟机生成多个子备份策略,子备份策略用于扩展基础备份策略,且子备份策略包括虚拟机的磁盘文件合并方向、磁盘文件合并深度、目标主机设备的选择以及备份限速中的至少一种。如图6所示,虚拟化数据中心包括多个虚拟机,计算机设备为每个虚拟机确定基础备份策略(基础备份策略即图6中的基础策略),这样,虚拟机1、虚拟机2…虚拟机m绑定基础备份策略1(图6中的策略1),虚拟机m+1、虚拟机m+2…虚拟机q绑定基础备份策略2(图6中的策略2),虚拟机t+1、虚拟机t+2…虚拟机w绑定基础备份策略n(图6 中的策略n),通过对基础备份策略进行扩展后,为每个虚拟机又绑定了多个子备份策略(如图6中的子策略),如虚拟机1绑定子备份策略ab、ba、ca以及db等,虚拟机2绑定子备份策略aa、bb、ca以及da等,虚拟机m绑定子备份策略aa、ba、cb以及dc等,虚拟机m+1绑定子备份策略ab、bb、ca以及da等,虚拟机m+2绑定子备份策略aa、ba、ca以及db等,虚拟机q绑定子备份策略ab、ba、ca以及db等,虚拟机t+1绑定子备份策略aa、bb、ca以及db等,虚拟机t+2绑定子备份策略ab、ba、cb以及dc等,虚拟机w绑定子备份策略aa、ba、ca以及da等。子备份策略包括qcow2文件节点链合并方式(aa:向上合并,ab:向下合并),qcow2文件链深度控制(ba:及时合并,bb:延迟合并),目标主机设备的选择(ca:资源带宽分配大,cb:资源带宽分配小)(即图6中的任务处理节点的选择),备份限速策略(da:限速30MB/S,db:限速50MB/S,dc:限速100MB/S)。
S305、根据基础备份策略和子备份策略,向目标主机设备中的备份终端发送用于对所述虚拟机进行备份的指示。
根据上述基础备份策略和子备份策略,向目标主机设备中的备份终端发送用于对虚拟机进行备份的指示,以使备份终端利用目标主机设备的资源,基于基础备份策略和子备份策略对虚拟机的数据进行备份。
S306、根据子备份策略,向所述虚拟机发送用于磁盘文件合并的指示。
在当前备份任务结束之后,待备份设备根据子备份策略中的磁盘文件合并方向以及磁盘文件的合并深度,对磁盘文件节点进行合并。
需要说明的是,未在上述S301-S306中的详尽的技术细节可以参照上述实施例中的描述,本实施例在此不再赘述。
在本实施例中,计算机设备可以自动地为待备份设备设置基础备份策略,并基于基础备份策略以及待备份设备和主机设备的实际运行信息,为待备份设备设置子备份策略,使得在实际备份过程中,基于上述确定的基础备份策略和子备份策略进行数据备份,避免了人为制定的备份策略的不合理性,从而提高了数据备份的成功率,同时也降低了数据备份的时长。
图7为本申请实施例提供的数据备份的装置的结构示意图。如图7所示,该装置可以包括:第一获取模块20、第一确定模块21和第一发送模块22。
第一获取模块20设置为获取待备份设备当前备份时刻相对于上一备份时刻的数据增量、当前备份时刻的数据量和上一备份时刻的数据量,以及至少一个主机设备在当前备份时刻的资源量;所述待备份设备在所述至少一个主机设备中的一个上运行,所述至少一个主机设备的每一个上安装有备份终端;第一确 定模块21设置为根据所述数据增量、当前备份时刻的数据量、上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定所述待备份设备当前备份时刻的备份策略,所述备份策略包括所述待备份设备的磁盘文件合并方向和磁盘文件合并深度中的至少一种;第一发送模块22设置为根据所述备份策略,向所述至少一个主机设备中的一个主机设备中的备份终端发送用于对所述待备份设备进行备份的指示。
本申请实施例提供的数据备份的装置,能够基于获取到的数据增量、当前备份时刻的数据量、上一备份时刻的数据量以及至少一个主机设备在当前备份时刻的资源量,确定待备份设备当前备份时刻的备份策略,备份策略包括待备份设备的磁盘文件合并方向和磁盘文件合并深度中的至少一种,并基于确定出的备份策略,向所述至少一个主机设备中的一个主机设备中的备份终端发送用于对待备份设备进行备份的指示。由于备份策略是基于待备份设备和主机设备的实际运行信息确定出的,而非人为制定的策略,即本申请所确定出的备份策略与待备份设备和主机设备的实际运行信息相匹配,避免了人为制定的备份策略的不合理性,从而提高了数据备份的成功率,同时也降低了数据备份的时长。
在上述实施例的基础上,可选的,所述备份策略还包括备份限速;所述第一确定模块21是设置为获取所述待备份设备所在的待备份系统在当前备份时刻的网络带宽利用率;根据所述数据增量、当前备份时刻的数据量、上一备份时刻的数据量、所述至少一个主机设备在当前备份时刻的资源量以及所述待备份系统在当前备份时刻的网络带宽利用率,确定所述待备份设备当前备份时刻的备份策略。
在上述实施例的基础上,可选的,该装置还包括:第二获取模块和第二确定模块。
第二获取模块设置为在所述第一获取模块20获取待备份设备当前备份时刻相对于上一备份时刻的数据增量、当前备份时刻的数据量和上一备份时刻的数据量,以及所述至少一个主机设备在当前备份时刻的资源量之前,当备份策略的生成时刻到达时,获取待备份设备在所述生成时刻的数据量、所述待备份设备在预设时间内的数据增量、所述至少一个主机设备在所述生成时刻的资源量以及所述待备份设备所在待备份系统在所述生成时刻的网络带宽利用率;第二确定模块设置为根据所述生成时刻的数据量、所述预设时间内的数据增量、所述生成时刻的资源量以及所述生成时刻的网络带宽利用率,通过预设的推荐算法,确定所述待备份设备的基础备份策略,所述基础备份策略包括备份的开始时间和对全量备份与增量备份二者之一的选择。
在上述实施例的基础上,可选的,第二确定模块是设置为根据所述生成时 刻的数据量、所述预设时间内的数据增量、所述生成时刻的资源量以及所述生成时刻的网络带宽利用率,通过预设的推荐算法,确定待推荐的备份策略集;结合用户设置的历史备份策略,从所述待推荐的备份策略集中选择一个目标备份策略作为所述基础备份策略。
在上述实施例的基础上,可选的,当所述备份策略包括所述待备份设备的磁盘文件的合并方向和目标主机设备的选择时,所述第一确定模块21是设置为当所述数据增量不超过所述上一备份时刻的数据量时,确定所述待备份设备的磁盘文件的合并方向为向上合并;当所述数据增量超过所述上一备份时刻的数据量时,确定所述待备份设备的磁盘文件的合并方向为向下合并。
在上述实施例的基础上,可选的,备份策略还包括目标主机设备的选择;所述第一确定模块21是设置为在主机设备的数量为多个的情况下,根据所述当前备份时刻的数据量和所述多个主机设备在当前备份时刻的资源量,从所述多个主机设备中确定目标主机设备,以通过所述目标主机设备中的备份终端执行所述待备份设备的本次备份任务。
在上述实施例的基础上,可选的,该装置还包括:第二发送模块。
第二发送模块设置为根据所述备份策略,向所述待备份设备发送用于磁盘文件合并的指示。
在上述实施例的基础上,可选的,所述待备份系统为虚拟化数据中心,所述待备份设备为虚拟机。
在一个实施例中,提供了一种计算机设备,其内部结构图可以如图8所示。该计算机设备包括通过系统总线连接的处理器、存储器、网络接口和数据库。该计算机设备的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统、计算机程序和数据库。该内存储器为非易失性存储介质中的操作系统和计算机程序的运行提供环境。该计算机设备的数据库设置为存储数据备份过程中的数据。该计算机设备的网络接口设置为与外部的终端通过网络连接通信。该计算机程序被处理器执行时以实现一种数据备份的方法。
本领域技术人员可以理解,图8中示出的结构,仅仅是与本申请方案相关的部分结构的框图,并不构成对本申请方案所应用于其上的计算机设备的限定,计算机设备可以包括比图中所示更多或更少的部件,或者组合某些部件,或者具有不同的部件布置。
在一个实施例中,提供了一种计算机设备,包括存储器和处理器,存储器中存储有计算机程序,该处理器执行计算机程序时实现以下步骤:获取待备份 设备当前备份时刻相对于上一备份时刻的数据增量、当前备份时刻的数据量和上一备份时刻的数据量,以及至少一个主机设备在当前备份时刻的资源量;所述待备份设备在所述至少一个主机设备中的一个上运行,所述至少一个主机设备的每一个上安装有备份终端;根据所述数据增量、当前备份时刻的数据量、上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定所述待备份设备当前备份时刻的备份策略,所述备份策略包括所述待备份设备的磁盘文件合并方向和磁盘文件合并深度中的至少一种;根据所述备份策略,向所述至少一个主机设备中的一个主机设备中的备份终端发送用于对所述待备份设备进行备份的指示。
在一个实施例中,所述备份策略还包括备份限速;处理器执行计算机程序时还实现以下步骤:获取所述待备份设备所在的待备份系统在当前备份时刻的网络带宽利用率;根据所述数据增量、当前备份时刻的数据量、上一备份时刻的数据量、所述至少一个主机设备在当前备份时刻的资源量以及所述待备份系统在当前备份时刻的网络带宽利用率,确定所述待备份设备当前备份时刻的备份策略。
在一个实施例中,处理器执行计算机程序时还实现以下步骤:当备份策略的生成时刻到达时,获取待备份设备在所述生成时刻的数据量、所述待备份设备在预设时间内的数据增量、所述至少一个主机设备在所述生成时刻的资源量以及所述待备份设备所在待备份系统在所述生成时刻的网络带宽利用率;根据所述生成时刻的数据量、所述预设时间内的数据增量、所述生成时刻的资源量以及所述生成时刻的网络带宽利用率,通过预设的推荐算法,确定所述待备份设备的基础备份策略,所述基础备份策略包括备份的开始时间和对全量备份与增量备份二者之一的选择。
在一个实施例中,处理器执行计算机程序时还实现以下步骤:根据所述生成时刻的数据量、所述预设时间内的数据增量、所述生成时刻的资源量以及所述生成时刻的网络带宽利用率,通过预设的推荐算法,确定待推荐的备份策略集;结合用户设置的历史备份策略,从所述待推荐的备份策略集中选择一个目标备份策略作为所述基础备份策略。
在一个实施例中,当所述备份策略包括所述待备份设备的磁盘文件的合并方向和目标主机设备的选择时,处理器执行计算机程序时还实现以下步骤:当所述数据增量不超过所述上一备份时刻的数据量时,确定所述待备份设备的磁盘文件的合并方向为向上合并;当所述数据增量超过所述上一备份时刻的数据量时,确定所述待备份设备的磁盘文件的合并方向为向下合并。
在一个实施例中,备份策略还包括目标主机设备的选择;在主机设备的数 量为多个的情况下,根据所述当前备份时刻的数据量和所述多个主机设备在当前备份时刻的资源量,从所述多个主机设备中确定目标主机设备,以通过所述目标主机设备中的备份终端执行所述待备份设备的本次备份任务。
在一个实施例中,处理器执行计算机程序时还实现以下步骤:根据所述备份策略,向所述待备份设备发送用于磁盘文件合并的指示。
可选的,所述待备份系统为虚拟化数据中心,所述待备份设备为虚拟机。
在一个实施例中,提供了一种计算机可读存储介质,其上存储有计算机程序,计算机程序被处理器执行时实现以下步骤:获取待备份设备当前备份时刻相对于上一备份时刻的数据增量、当前备份时刻的数据量和上一备份时刻的数据量,以及至少一个主机设备在当前备份时刻的资源量;所述待备份设备在所述至少一个主机设备中的一个上运行,所述至少一个主机设备的每一个上安装有备份终端;根据所述数据增量、当前备份时刻的数据量、上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定所述待备份设备当前备份时刻的备份策略,所述备份策略包括所述待备份设备的磁盘文件合并方向和磁盘文件合并深度中的至少一种;根据所述备份策略,向所述至少一个主机设备中的一个主机设备中的备份终端发送用于对所述待备份设备进行备份的指示。
在一个实施例中,所述备份策略还包括备份限速;计算机程序被处理器执行时还实现以下步骤:获取所述待备份设备所在的待备份系统在当前备份时刻的网络带宽利用率;根据所述数据增量、当前备份时刻的数据量、上一备份时刻的数据量、所述至少一个主机设备在当前备份时刻的资源量以及所述待备份系统在当前备份时刻的网络带宽利用率,确定所述待备份设备当前备份时刻的备份策略。
在一个实施例中,计算机程序被处理器执行时还实现以下步骤:当备份策略的生成时刻到达时,获取待备份设备在所述生成时刻的数据量、所述待备份设备在预设时间内的数据增量、所述至少一个主机设备在所述生成时刻的资源量以及所述待备份设备所在待备份系统在所述生成时刻的网络带宽利用率;根据所述生成时刻的数据量、所述预设时间内的数据增量、所述生成时刻的资源量以及所述生成时刻的网络带宽利用率,通过预设的推荐算法,确定所述待备份设备的基础备份策略,所述基础备份策略包括备份的开始时间和对全量备份与增量备份二者之一的选择。
在一个实施例中,计算机程序被处理器执行时还实现以下步骤:根据所述生成时刻的数据量、所述预设时间内的数据增量、所述生成时刻的资源量以及所述生成时刻的网络带宽利用率,通过预设的推荐算法,确定待推荐的备份策 略集;结合用户设置的历史备份策略,从所述待推荐的备份策略集中选择一个目标备份策略作为所述基础备份策略。
在一个实施例中,当所述备份策略包括所述待备份设备的磁盘文件的合并方向和目标主机设备的选择时,计算机程序被处理器执行时还实现以下步骤:当所述数据增量不超过所述上一备份时刻的数据量时,确定所述待备份设备的磁盘文件的合并方向为向上合并;当所述数据增量超过所述上一备份时刻的数据量时,确定所述待备份设备的磁盘文件的合并方向为向下合并。
在一个实施例中,备份策略还包括目标主机设备的选择;在主机设备的数量为多个的情况下,根据所述当前备份时刻的数据量和所述多个主机设备在当前备份时刻的资源量,从所述多个主机设备中确定目标主机设备,以通过所述目标主机设备中的备份终端执行所述待备份设备的本次备份任务。
在一个实施例中,计算机程序被处理器执行时还实现以下步骤:根据所述备份策略,向所述待备份设备发送用于磁盘文件合并的指示。
可选的,所述待备份系统为虚拟化数据中心,所述待备份设备为虚拟机。
上述实施例中提供的数据备份的装置、计算机设备以及存储介质可执行本申请任意实施例所提供的数据备份的方法。未在上述实施例中详尽描述的技术细节,可参见本申请任意实施例所提供的数据备份的方法。
以上所述,仅为本申请的示例性实施例而已,并非用于限定本申请的保护范围。
本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如,一些方面可以被实现在硬件中,而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中,尽管本申请不限于此。
本申请的实施例可以通过数据备份装置的数据处理器执行计算机程序指令来实现,例如在处理器实体中,或者通过硬件,或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture,ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤,或者可以表示相互连接的逻辑电路、模块和功能,或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现,例如但不限于只读存储器(Read-Only Memory,ROM)、随机访问存储器(Random Access Memory,RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc, DVD)或光盘(Compact Disc,CD))等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型,例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processor,DSP)、专用集成电路(Application Specific Integrated Circuit,ASIC)、可编程逻辑器件(Field Programmable Gate Array,FPGA)以及基于多核处理器架构的处理器。

Claims (11)

  1. 一种数据备份的方法,包括:
    获取待备份设备当前备份时刻相对于上一备份时刻的数据增量、当前备份时刻的数据量和上一备份时刻的数据量,以及至少一个主机设备在当前备份时刻的资源量;所述待备份设备在所述至少一个主机设备中的一个上运行,所述至少一个主机设备的每一个上安装有备份终端;
    根据所述数据增量、所述当前备份时刻的数据量、所述上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定所述待备份设备在当前备份时刻的备份策略,所述备份策略包括所述待备份设备的磁盘文件合并方向和磁盘文件合并深度中的至少一种;
    根据所述备份策略,向所述至少一个主机设备中的一个主机设备中的备份终端发送用于对所述待备份设备进行备份的指示。
  2. 根据权利要求1所述的方法,其中,所述备份策略还包括备份限速;
    所述根据所述数据增量、所述当前备份时刻的数据量、所述上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定所述待备份设备在当前备份时刻的备份策略,包括:
    获取所述待备份设备所在的待备份系统在当前备份时刻的网络带宽利用率;
    根据所述数据增量、所述当前备份时刻的数据量、所述上一备份时刻的数据量、所述至少一个主机设备在当前备份时刻的资源量以及所述待备份系统在当前备份时刻的网络带宽利用率,确定所述待备份设备当前备份时刻的备份策略。
  3. 根据权利要求1所述的方法,其中,在所述获取待备份设备当前备份时刻相对于上一备份时刻的数据增量、当前备份时刻的数据量和上一备份时刻的数据量,以及至少一个主机设备在当前备份时刻的资源量之前,还包括:
    当备份策略的生成时刻到达时,获取所述待备份设备在所述生成时刻的数据量、所述待备份设备在预设时间内的数据增量、所述至少一个主机设备在所述生成时刻的资源量以及所述待备份设备所在的待备份系统在所述生成时刻的网络带宽利用率;
    根据所述生成时刻的数据量、所述预设时间内的数据增量、所述生成时刻的资源量以及所述生成时刻的网络带宽利用率,通过预设的推荐算法,确定所述待备份设备的基础备份策略,所述基础备份策略包括备份的开始时间和对全量备份与增量备份二者之一的选择。
  4. 根据权利要求3所述的方法,其中,所述根据所述生成时刻的数据量、所述预设时间内的数据增量、所述生成时刻的资源量以及所述生成时刻的网络带宽利用率,通过预设的推荐算法,确定所述待备份设备的基础备份策略,包括:
    根据所述生成时刻的数据量、所述预设时间内的数据增量、所述生成时刻的资源量以及所述生成时刻的网络带宽利用率,通过预设的推荐算法,确定待推荐的备份策略集;
    结合用户设置的历史备份策略,从所述待推荐的备份策略集中选择一个目标备份策略作为所述基础备份策略。
  5. 根据权利要求1至4中任一项所述的方法,其中,在所述备份策略包括所述待备份设备的磁盘文件的合并方向的情况下,所述根据所述数据增量、所述当前备份时刻的数据量、所述上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定所述待备份设备当前备份时刻的备份策略,包括:
    在所述数据增量不超过所述上一备份时刻的数据量的情况下,确定所述待备份设备的磁盘文件的合并方向为向上合并;
    在所述数据增量超过所述上一备份时刻的数据量的情况下,确定所述待备份设备的磁盘文件的合并方向为向下合并。
  6. 根据权利要求1至4中任一项所述的方法,其中,所述备份策略还包括:目标主机设备的选择;
    所述根据所述数据增量、所述当前备份时刻的数据量、所述上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定所述待备份设备当前备份时刻的备份策略,包括:
    在所述主机设备的数量为多个的情况下,根据所述当前备份时刻的数据量和所述多个主机设备在当前备份时刻的资源量,从所述多个主机设备中确定所述目标主机设备,以通过所述目标主机设备中的备份终端执行所述待备份设备的本次备份任务。
  7. 根据权利要求1至4中任一项所述的方法,还包括:
    根据所述备份策略,向所述待备份设备发送用于磁盘文件合并的指示。
  8. 根据权利要求2至4中任一项所述的方法,其中,所述待备份系统为虚拟化数据中心,所述待备份设备为虚拟机。
  9. 一种数据备份的装置,包括:
    第一获取模块,设置为获取待备份设备当前备份时刻相对于上一备份时刻的数据增量、当前备份时刻的数据量和上一备份时刻的数据量,以及至少一个主机设备在当前备份时刻的资源量,所述待备份设备在所述至少一个主机设备中的一个上运行,所述至少一个主机设备的每一个上安装有备份终端;
    第一确定模块,设置为根据所述数据增量、所述当前备份时刻的数据量、所述上一备份时刻的数据量以及所述至少一个主机设备在当前备份时刻的资源量,确定所述待备份设备当前备份时刻的备份策略,所述备份策略包括所述待备份设备的磁盘文件合并方向和磁盘文件合并深度中的至少一种;
    第一发送模块,设置为根据所述备份策略,向所述至少一个主机设备中的一个主机设备中的备份终端发送用于对所述待备份设备进行备份的指示。
  10. 一种计算机设备,包括存储器和处理器,所述存储器存储有计算机程序,所述处理器执行所述计算机程序时实现权利要求1-8中任一项所述方法。
  11. 一种存储介质,存储有计算机程序,所述计算机程序被处理器执行时实现权利要求1-8中任一项所述的方法。
PCT/CN2020/131845 2019-11-26 2020-11-26 数据备份的方法和装置、设备和存储介质 WO2021104383A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911175589.8A CN112948169A (zh) 2019-11-26 2019-11-26 数据备份的方法、装置、设备和存储介质
CN201911175589.8 2019-11-26

Publications (1)

Publication Number Publication Date
WO2021104383A1 true WO2021104383A1 (zh) 2021-06-03

Family

ID=76130014

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/131845 WO2021104383A1 (zh) 2019-11-26 2020-11-26 数据备份的方法和装置、设备和存储介质

Country Status (2)

Country Link
CN (1) CN112948169A (zh)
WO (1) WO2021104383A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113918385B (zh) * 2021-10-14 2022-06-24 江苏安超云软件有限公司 虚拟机在线增量备份恢复的方法、装置、电子设备及介质
CN114721882B (zh) * 2022-06-10 2022-09-30 建信金融科技有限责任公司 数据备份方法、装置、电子设备及存储介质
CN114943021B (zh) * 2022-07-20 2022-11-08 之江实验室 一种tb级增量数据筛选方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106802840A (zh) * 2017-01-19 2017-06-06 郑州云海信息技术有限公司 一种虚拟机备份、恢复方法及装置
CN107133131A (zh) * 2017-05-31 2017-09-05 广州鼎甲计算机科技有限公司 一种基于VMware的虚拟机合成备份方法
CN109558215A (zh) * 2018-12-10 2019-04-02 深圳市木浪云数据有限公司 虚拟机的备份方法、恢复方法、装置及备份服务器集群
US20190243719A1 (en) * 2018-02-02 2019-08-08 EMC IP Holding Company LLC Virtual Machine Backup with Efficient Checkpoint Handling

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106802840A (zh) * 2017-01-19 2017-06-06 郑州云海信息技术有限公司 一种虚拟机备份、恢复方法及装置
CN107133131A (zh) * 2017-05-31 2017-09-05 广州鼎甲计算机科技有限公司 一种基于VMware的虚拟机合成备份方法
US20190243719A1 (en) * 2018-02-02 2019-08-08 EMC IP Holding Company LLC Virtual Machine Backup with Efficient Checkpoint Handling
CN109558215A (zh) * 2018-12-10 2019-04-02 深圳市木浪云数据有限公司 虚拟机的备份方法、恢复方法、装置及备份服务器集群

Also Published As

Publication number Publication date
CN112948169A (zh) 2021-06-11

Similar Documents

Publication Publication Date Title
WO2021104383A1 (zh) 数据备份的方法和装置、设备和存储介质
US20200404032A1 (en) Streaming Application Upgrading Method, Master Node, and Stream Computing System
US9442954B2 (en) Method and apparatus for achieving optimal resource allocation dynamically in a distributed computing environment
US11099752B1 (en) Application performance in replication environments
US10261853B1 (en) Dynamic replication error retry and recovery
JP6799652B2 (ja) 情報を処理するための方法及び装置
US10831741B2 (en) Log-shipping data replication with early log record fetching
US9354907B1 (en) Optimized restore of virtual machine and virtual disk data
WO2012056596A1 (ja) 計算機システム及び処理制御方法
US20140006735A1 (en) Space reservation in a deduplication system
WO2018058944A1 (zh) 一种删除级联快照的方法及装置
US10620871B1 (en) Storage scheme for a distributed storage system
WO2019061352A1 (zh) 数据加载方法及装置
US20070294568A1 (en) Storage system and method of managing data using the same
US10467106B2 (en) Data processing method, data processing system, and non-transitory computer program product for controlling a workload delay time
EP3311272B1 (en) A method of live migration
WO2016045428A1 (zh) 一种创建虚拟机的方法和创建虚拟机的装置
US11023159B2 (en) Method for fast recovering of data on a failed storage device
WO2021082465A1 (zh) 一种保证数据一致性的方法及相关设备
US10845997B2 (en) Job manager for deploying a bundled application
WO2016095760A1 (zh) 数据动态重分布的方法、数据节点、名字节点及系统
WO2021174698A1 (zh) 虚拟机快照创建方法、装置、存储介质及计算机设备
CN111078127B (zh) 数据迁移方法、系统及装置
US8621260B1 (en) Site-level sub-cluster dependencies
CN110569112B (zh) 日志数据写入方法及对象存储守护装置

Legal Events

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

Ref document number: 20892764

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20892764

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 22.02.2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20892764

Country of ref document: EP

Kind code of ref document: A1