CN114579368A - Backup management method for continuous data protection, computer equipment and storage medium - Google Patents
Backup management method for continuous data protection, computer equipment and storage medium Download PDFInfo
- Publication number
- CN114579368A CN114579368A CN202210490833.5A CN202210490833A CN114579368A CN 114579368 A CN114579368 A CN 114579368A CN 202210490833 A CN202210490833 A CN 202210490833A CN 114579368 A CN114579368 A CN 114579368A
- Authority
- CN
- China
- Prior art keywords
- backup
- files
- file
- determining
- target
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
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 application discloses a backup management method for continuous data protection, computer equipment and a storage medium, wherein the method comprises the following steps: if the backup storage space corresponding to the CDP overflows, determining a plurality of target files in a plurality of backup files in the backup storage space; acquiring data importance levels and backup time points of a plurality of target files; determining an importance value of the target file according to the data importance level and the backup time point; determining files to be deleted in the plurality of target files according to the importance value; and deleting the files to be deleted so as to increase the residual storage capacity of the backup storage space. According to the embodiment of the application, when the backup storage space overflows, part of the backup files are deleted to increase the residual storage capacity and improve the stability of CDP backup, and the backup files are deleted according to the important grades and the backup time points of the backup files, so that the backup files are more reasonably deleted, and the important data are prevented from being deleted by mistake.
Description
Technical Field
The present application relates to the field of persistent data protection technologies, and in particular, to a backup management method, a computer device, and a storage medium for persistent data protection.
Background
CDP (Continuous Data Protection) is a Continuous Protection technique for files. The system manager does not need to pay attention to the data backup process, but simply selects the data backup time point to be restored after a disaster happens, so that the rapid data restoration technology can be realized. CDP can provide fine recoverable objects for an unlimited number of variable recovery points, enabling data recovery at any point in time in the past.
Because CDP will continuously monitor and backup data changes, a lot of backup data will be generated during CDP backup, which occupies too much backup storage space, and finally leads to the overflow of backup storage space. When the backup storage space overflows, the backup service may make a fault, for example, a backup failure or a loss of backed-up data occurs, which reduces the stability of CDP backup.
Disclosure of Invention
The embodiment of the application provides a backup management method, computer equipment and a storage medium for continuous data protection, and aims to improve the stability of CDP backup.
In one aspect, the present application provides a backup management method for persistent data protection, including:
after data backup is completed by adopting continuous data protection, acquiring the residual storage capacity of a backup storage space corresponding to the continuous data protection;
judging whether the backup storage space overflows or not according to the residual storage capacity;
if the backup storage space overflows, determining a plurality of target files in a plurality of backup files in the backup storage space;
acquiring data importance levels and backup time points of a plurality of target files;
determining an importance value of the target file according to the data importance level and the backup time point;
determining files to be deleted in the plurality of target files according to the importance value;
and deleting the file to be deleted so as to increase the residual storage capacity of the backup storage space.
In some embodiments, the step of determining a plurality of target files from the plurality of backup files in the backup storage space includes:
obtaining backup source objects corresponding to a plurality of backup files;
determining the number of backup files of each backup source object;
taking the backup source objects with the number of the backup files larger than the preset number as target backup source objects;
and taking the backup file corresponding to the target backup source object as the target file in the plurality of backup files.
In some embodiments, the step of determining the importance value of the target file according to the importance level of the data and the backup time point includes:
acquiring an importance score corresponding to the data importance level;
determining a time difference between a current time point and the backup time point;
acquiring a time score corresponding to the difference interval where the time difference is located;
and determining the importance value of the target file according to the importance score and the time score.
In some embodiments, the step of determining a file to be deleted in the plurality of target files according to the importance value includes:
according to the importance degree value, sequencing the target files from small to large;
acquiring a preset number of first backup files ranked at the top in the sequencing result;
and determining files to be deleted in the plurality of target files according to the first backup file.
In some embodiments, the step of determining a file to be deleted from the plurality of target files according to the first backup file comprises:
acquiring a first backup source object corresponding to the first backup file and a backup time point of the first backup file;
determining a second backup file with a backup time point later than that of the first backup file in a plurality of backup files corresponding to the first backup source object;
taking the first backup file and the second backup file as the files to be deleted;
after the step of deleting the file to be deleted to increase the remaining storage capacity of the backup storage space, the method further includes:
when a backup recovery request is received, determining a third backup source object and a backup recovery time point corresponding to the backup recovery request;
acquiring a plurality of third backup files corresponding to the third backup source object in the backup storage space and having backup time points earlier than the backup recovery time points;
and sequentially adopting the plurality of third backup files to perform data recovery according to the sequence of the backup time points of the plurality of third backup files.
In some embodiments, the determining, in the plurality of backup files corresponding to the first backup source object, a second backup file having a backup time point later than that of the first backup file includes:
determining backup types of a plurality of backup files corresponding to the first backup source object, wherein the backup types comprise incremental backup and full backup;
determining a third backup file with a backup time point later than that of the first backup file in a plurality of backup files corresponding to the first backup source object and having full backup types;
and determining a second backup file with a backup time point between the backup time point of the first backup file and the backup time point of the third backup file in the plurality of backup files corresponding to the first backup source object.
In some embodiments, the step of obtaining the importance levels of the data of a plurality of the target files comprises:
acquiring a backup source object corresponding to the target file;
determining the file type of the backup source object;
and taking the data importance level corresponding to the file type as the data importance level of the target file.
In some embodiments, the step of determining a plurality of target files from the plurality of backup files in the backup storage space includes:
obtaining backup source objects corresponding to a plurality of backup files;
determining the backup change frequency of the backup source object according to the backup time points of a plurality of backup files corresponding to the backup source object;
when the backup change frequency is smaller than a preset frequency, taking a backup source object corresponding to the backup change frequency as a target backup source object;
and taking the backup file corresponding to the target backup source object as the target file in the plurality of backup files.
On the other hand, an embodiment of the present application provides a backup management device for continuous data protection, including:
the acquisition module is used for acquiring the residual storage capacity of the backup storage space corresponding to the continuous data protection after the data backup is finished by adopting the continuous data protection;
the judging module is used for judging whether the backup storage space overflows or not according to the residual storage capacity;
the determining module is used for determining a plurality of target files in a plurality of backup files in the backup storage space if the backup storage space overflows; acquiring data importance levels and backup time points of a plurality of target files; determining an importance value of the target file according to the data importance level and the backup time point; determining files to be deleted in the plurality of target files according to the importance value;
and the deleting module is used for deleting the file to be deleted so as to increase the residual storage capacity of the backup storage space.
In another aspect, the present application further provides a computer device, including:
one or more processors;
a memory; and
one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor to implement the steps of any of the persistent data protected backup management methods.
In another aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is loaded by a processor to execute the steps in any one of the backup management methods for persistent data protection.
The backup management method, the computer device and the storage medium for continuous data protection provided by the embodiment of the application comprise the following steps: if the backup storage space corresponding to the CDP overflows, determining a plurality of target files in a plurality of backup files in the backup storage space; acquiring data importance levels and backup time points of a plurality of target files; determining an importance value of the target file according to the data importance level and the backup time point; determining a file to be deleted in a plurality of target files according to the importance value; and deleting the files to be deleted so as to increase the residual storage capacity of the backup storage space. According to the embodiment of the application, when the backup storage space overflows, part of the backup files are deleted to increase the residual storage capacity and improve the stability of CDP backup, and the backup files are deleted according to the important grades and the backup time points of the backup files, so that the backup files are more reasonably deleted, and the important data are prevented from being deleted by mistake.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a flowchart illustrating an embodiment of a backup management method for persistent data protection provided in an embodiment of the present application;
FIG. 2 is a flowchart illustrating another embodiment of a backup management method for persistent data protection provided in an embodiment of the present application;
FIG. 3 is a flowchart illustrating a backup management method for persistent data protection according to yet another embodiment of the present application;
fig. 4 is a schematic structural diagram of an embodiment of a backup management apparatus for persistent data protection according to an embodiment of the present application;
fig. 5 is a schematic terminal structure diagram of an embodiment of a computer device provided in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the description of the present application, it is to be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", and the like indicate orientations or positional relationships based on those shown in the drawings, and are used merely for convenience of description and for simplicity of description, and do not indicate or imply that the referenced device or element must have a particular orientation, be constructed in a particular orientation, and be operated, and thus should not be considered as limiting the present application. Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, features defined as "first", "second", may explicitly or implicitly include one or more of the described features. In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.
In this application, the word "exemplary" is used to mean "serving as an example, instance, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The following description is presented to enable any person skilled in the art to make and use the application. In the following description, details are set forth for the purpose of explanation. It will be apparent to one of ordinary skill in the art that the present application may be practiced without these specific details. In other instances, well-known structures and processes are not set forth in detail in order to avoid obscuring the description of the present application with unnecessary detail. Thus, the present application is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
It should be noted that, because the system in the embodiment of the present application is executed in a computer device, processing objects of each computer device all exist in the form of data or information, for example, time, which is substantially time information, and it is understood that, in the subsequent embodiments, if size, number, position, and the like are mentioned, corresponding data exist so as to be processed by the computer device, and details are not described herein.
Embodiments of the present application provide a backup management method, a computer device, and a storage medium for persistent data protection, which are described in detail below.
Referring to fig. 1, in an embodiment, a backup management method for persistent data protection is applied to a computer device at a user side or a server side, and includes:
101. after data backup is completed by adopting continuous data protection, acquiring the residual storage capacity of a backup storage space corresponding to the continuous data protection;
in this embodiment, after the data backup is completed by using the persistent data protection, the computer device at the user end or the server end may obtain the remaining storage capacity of the backup storage space corresponding to the persistent data protection, so that the computer device at the user end or the server end realizes the backup management of the persistent data protection.
In some embodiments, the user side is provided with a JAVA-based File modification Listener adapter (File Alteration Listener adapter) for continuously listening to specified files and/or folders. When the file modification listener adapter monitors that a specified file or a certain file in a specified folder has changes such as addition, modification, deletion and the like, a corresponding backup file can be automatically generated according to the changed Data, and the backup file is sent to a database of a server or other file systems for storage, so that Data backup based on CDP (Continuous Data Protection) is realized. Wherein, the user at the user end can manually set the files or folders which are continuously monitored. CDP technology captures all file access operations in real time by embedding a file filter driver in the operating system core layer. For the files or folders which need CDP continuous backup protection, when the rewriting operation is monitored, the file data change part and the current System Time Stamp (System Time Stamp) are automatically backed up to the server in advance. Theoretically, any change in the file data is automatically recorded. After the CDP technology is adopted to complete data backup each time, the residual storage capacity of the server backup storage space corresponding to the CDP can be obtained so as to detect whether the latest book backup causes the overflow phenomenon of the backup storage space.
102. Judging whether the backup storage space overflows or not according to the residual storage capacity;
in this embodiment, a capacity threshold may be set, and if the remaining storage capacity is greater than or equal to the capacity threshold, it is determined that the backup storage space is overflowed. And if the residual storage capacity is smaller than the capacity threshold, judging that the backup storage space does not overflow. The capacity threshold may be manually set in advance, and is generally less than or equal to the maximum storage capacity of the backup storage space, for example, the capacity threshold may be set to 90% of the maximum storage capacity.
103. If the backup storage space overflows, determining a plurality of target files in a plurality of backup files in the backup storage space;
in this embodiment, the backup storage space is used to store backup files of the backup source object, where the backup source object refers to a local file at the user end, such as a file or a folder that the user end needs to continuously monitor, and the backup file is a full backup or an incremental backup of the backup source object. If the backup storage space overflows, a plurality of target files can be determined in a plurality of backup files in the backup storage space, and then the files to be deleted are determined. And when the backup storage space is not overflowed, the backup storage space is not processed.
In some embodiments, in the step of determining a plurality of target files from a plurality of backup files in the backup storage space, a backup source object corresponding to each backup file may be determined to count the number of backup files of each backup source object, where each change of the backup source object obtains a corresponding backup file through the CDP. If the number of the backup files of the backup source object is larger than the preset number, the number of times of changing the backup source object is more, so that the backup source object can be used as a target backup source object, and the backup files corresponding to the target backup source object are all used as target files.
In some embodiments, in the step of determining a plurality of target files in a plurality of backup files in the backup storage space, a backup source object corresponding to each backup file may be determined, so as to count the backup change frequency of each backup source object. If the backup change frequency of the backup source object is less than the preset frequency, the change frequency of the backup source object is low, and the change backup requirement of the backup source object is low, so that the backup source object can be used as a target backup source object, and backup files corresponding to the target backup source object are all used as target files. In some embodiments, when determining the change frequency of the backup source object, the backup time points of the backup files corresponding to the backup source object may be obtained, the backup time span may be determined according to the backup time points of the backup files, and the ratio of the time span to the number of the backup files is used as the change frequency of the backup, for example, the time span between the backup files may be determined to be 30 days according to the backup time points of the backup files, and the change frequency of the backup may be 0.3 day/time if there are 100 backup files in total in the 30 days. In some embodiments, when determining the backup change frequency of the backup source object, the number of backup files corresponding to the backup source object in a past preset time period may be obtained, and a ratio of the preset time period to the number of backup files is used as the backup change frequency, for example, the preset time period is 10 days in the past, and the number of backup files corresponding to the backup source object in the 10 days is 50, so that the backup change frequency is 0.2 day/time.
104. Acquiring data importance levels and backup time points of a plurality of target files;
in this embodiment, each backup file in the backup storage space corresponds to a data importance level, such as a primary level, a secondary level, a tertiary level, and the like. The backup time point is a storage time point when the backup file is stored in the backup storage space or a change time point of the corresponding backup source object.
In some embodiments, when the data importance level of the target file is obtained, the backup source object corresponding to the target file may be obtained, the file type to which the backup source object belongs is determined, and the data importance level corresponding to the file type is used as the data importance level of the corresponding target file. Each backup source object corresponds to a file type, and each file type is preset with a corresponding data importance level, for example, the file type may be txt, doc, JPEG, exe, or the like, or may be a text file type, a video file format type, an audio file format type, a picture file format type, an executable file format type, or the like. Different data importance levels can be set for different file types according to actual requirements in advance, for example, the data importance level corresponding to the text file type is set as a first level, and the data importance level corresponding to the executable file format type is set as a second level.
105. Determining an importance value of the target file according to the data importance level and the backup time point;
in the present embodiment, the different data importance levels are set in advance with corresponding importance scores. Generally, as the importance level of the data is higher, the corresponding importance score is also higher, e.g., the importance score for the secondary is greater than the importance score for the primary.
In some embodiments, when calculating the importance value of the target file, the importance score corresponding to the data importance level of the target file may be obtained, a time difference between the current time point and the backup time point of the target file may be determined, a difference interval where the time difference is located may be determined, and a time score corresponding to the difference interval where the time difference is located may be obtained. And determining the importance value of the target file according to the importance score and the time score. Generally, the larger the difference value in the difference value interval is, the higher the time score corresponding to the difference value interval is, that is, the farther the backup time point is from the current time point, the higher the corresponding time score is, so as to avoid deleting the file backup which is changed by the user recently.
In some embodiments, when determining the importance value of the target document according to the importance score and the time score, the importance score and the time score may be weighted and summed according to a preset weight to obtain the importance value of the target document, for example, a weight of 0.6 may be set for the importance score, and a weight of 0.4 may be set for the time score.
106. Determining files to be deleted in the plurality of target files according to the importance value;
107. and deleting the file to be deleted so as to increase the residual storage capacity of the backup storage space.
In this embodiment, the files to be deleted in the plurality of target files may be screened out according to the size of the importance value. In some embodiments, the importance value may be compared with a preset threshold, and a target file with the importance value smaller than the preset threshold may be used as a file to be deleted. In some embodiments, at least one of the target files with a lower importance value may be used as the file to be deleted.
In the technical scheme disclosed in this embodiment, when the backup storage space overflows, part of the backup files are deleted to increase the remaining storage capacity and improve the stability of CDP backup, and the backup files are deleted according to the importance levels of the backup files and the backup time points, so that the deletion of the backup files is more reasonable to avoid mistakenly deleting important data.
In another embodiment, as shown in fig. 2, step 106 includes, based on the embodiment shown in fig. 1:
201. according to the importance degree value, sequencing the target files from small to large;
202. acquiring a preset number of first backup files ranked at the top in the sequencing result;
203. and determining files to be deleted in the plurality of target files according to the first backup file.
In this embodiment, for a plurality of target files, sorting is performed from small to large according to the importance value, and a sorting result is obtained. And considering the importance of the first backup files with the preset number which are ranked at the top in the sorting result to be lower. The preset number may be set in advance according to actual requirements, for example, all the top 5 target files in the sorting result may be used as the first backup files.
In some embodiments, the first backup file may be directly used as the file to be deleted, or the file to be deleted may be further determined according to the first backup file. For example, the size of the storage space occupied by each first backup file may be obtained, and at least one first backup file occupying a larger storage space may be used as the file to be deleted.
In the technical scheme disclosed in this embodiment, a plurality of target files are sorted from small to large according to the importance value to determine at least one target file with a low importance, and further determine a file to be deleted, thereby realizing the determination of an unimportant backup file.
In yet another embodiment, as shown in fig. 3, on the basis of the embodiment shown in fig. 2, step 203 comprises:
301. acquiring a first backup source object corresponding to the first backup file and a backup time point of the first backup file;
302. determining a second backup file with a backup time point later than that of the first backup file in a plurality of backup files corresponding to the first backup source object;
303. taking the first backup file and the second backup file as the files to be deleted;
in this embodiment, since the CDP backup is performed continuously based on the change of the backup source object, the subsequent backup file is generally performed based on the previous backup file, so that when determining the file to be deleted in the plurality of target files according to the first backup file, the first backup source object corresponding to the first backup file and the backup time point of the first backup file may be obtained, and at least one second backup file whose backup time point is later than the backup time point of the first backup file is determined in all backup files corresponding to the first backup source object. It is understood that the second backup file is the same as the backup source object of the first backup file, and the second backup file is a later backup file of the first backup file. And the first backup file and the second backup file are both used as files to be deleted, so that useless second backup files are prevented from remaining after the first backup file is deleted, and the residual storage capacity of the backup storage space is further increased.
In some embodiments, when determining the second backup file, a distinction may also be made between incremental backup files and full backup files to make deletion of backup files more accurate. Specifically, the backup types of a plurality of backup files corresponding to the first backup source object may be determined, where the backup types include incremental backup and full backup. And determining a third backup file with a backup time point later than that of the first backup file in the plurality of backup files corresponding to the first backup source object and with the backup types of full backup, namely determining that the third backup file is the full backup file later than the first backup file. In a plurality of backup files corresponding to the first backup source object, a second backup file with a backup time point between the backup time point of the first backup file and the backup time point of the third backup file is determined, and the second backup file at the moment is an incremental backup file and/or a full backup file between the backup time points of the first backup file and the third backup file, so that the second backup file at the moment can be used as a file to be deleted to avoid a useless second backup file remaining after the first backup file is deleted. In some embodiments, when determining the third backup file, a backup file, of the plurality of backup files corresponding to the first backup source object and having the backup type of full backup, whose backup time point is later than the backup time point of the first backup file and whose backup time point is closest to the backup time point of the first backup file may be used as the third backup file. Of course, the backup file whose backup time point is later than the backup time point of the first backup file and whose backup time point is closer to the backup time point of the first backup file may also be used as the third backup file.
After step 107, the method further comprises:
401. when a backup recovery request is received, determining a third backup source object and a backup recovery time point corresponding to the backup recovery request;
402. acquiring a plurality of third backup files corresponding to the third backup source object in the backup storage space and having backup time points earlier than the backup recovery time points;
403. and sequentially adopting the plurality of third backup files to perform data recovery according to the sequence of the backup time points of the plurality of third backup files.
In this embodiment, when a backup restoration request triggered by a user is received, it indicates that a backup source object needs to be restored according to a backup file of a server, so that a third backup source object and a backup restoration time point corresponding to the backup restoration request can be determined, and a plurality of third backup files corresponding to the third backup source object and having a backup time point earlier than the backup restoration time point are determined in a plurality of backup files in a backup storage space, where when the backup files are stored in the backup storage space, the backup files and identification information of the corresponding backup source object are stored in an associated manner to determine a corresponding relationship between the backup files and the backup source object. Since the change of the backup source object is performed based on the time sequence, when data recovery is performed, the data recovery is performed by sequentially using the plurality of third backup files according to the sequence between the backup time points of the plurality of third backup files, for example, data recovery may be performed sequentially from the first backup file to the third backup file at the backup recovery time point.
In the technical scheme disclosed in this embodiment, when determining a file to be deleted according to a first backup file, the first backup file and a second backup file that belongs to the same backup source object as the first backup file and has a backup time point later than that of the first backup file are both used as files to be deleted, so that the deletion of the backup files is more reasonable.
In order to better implement the backup management method for persistent data protection in the embodiment of the present application, on the basis of the backup management method for persistent data protection, an embodiment of the present application further provides a backup management device for persistent data protection, as shown in fig. 4, the backup management device 4000 for persistent data protection includes an obtaining module 4001, a judging module 4002, a determining module 4003, and a deleting module 4004, and the following concrete steps are performed:
the obtaining module 4001 is configured to obtain a remaining storage capacity of a backup storage space corresponding to persistent data protection after data backup is completed by the persistent data protection;
a judging module 4002, configured to judge whether the backup storage space overflows according to the remaining storage capacity;
a determining module 4003, configured to determine, if the backup storage space overflows, a plurality of target files from a plurality of backup files in the backup storage space; acquiring data importance levels and backup time points of a plurality of target files; determining an importance value of the target file according to the data importance level and the backup time point; determining files to be deleted in the plurality of target files according to the importance value;
and the deleting module 4004 is configured to delete a file to be deleted, so as to increase the remaining storage capacity of the backup storage space.
The embodiment of the present application further provides a computer device, which integrates any one of the backup management apparatuses for continuous data protection provided in the embodiment of the present application. Fig. 5 is a schematic diagram showing a structure of a computer device according to an embodiment of the present application, specifically:
the computer device may include components such as a processor 501 of one or more processing cores, memory 502 of one or more computer-readable storage media, a power supply 503, and an input unit 504. Those skilled in the art will appreciate that the computer device configuration shown in FIG. 5 is not intended to constitute a limitation of computer devices and may include more or fewer components than those shown, or some of the components may be combined, or a different arrangement of components. Wherein:
the processor 501 is a control center of the computer device, connects various parts of the entire computer device by using various interfaces and lines, and performs various functions of the computer device and processes data by running or executing software programs and/or modules stored in the memory 502 and calling data stored in the memory 502, thereby monitoring the computer device as a whole. Alternatively, processor 501 may include one or more processing cores; preferably, the processor 501 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 501.
The memory 502 may be used to store software programs and modules, and the processor 501 executes various functional applications and data processing by operating the software programs and modules stored in the memory 502. The memory 502 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data created according to use of the computer device, and the like. Further, the memory 502 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 502 may also include a memory controller to provide the processor 501 with access to the memory 502.
The computer device further comprises a power supply 503 for supplying power to the various components, and preferably, the power supply 503 may be logically connected to the processor 501 through a power management system, so that functions of managing charging, discharging, power consumption, and the like are realized through the power management system. The power supply 503 may also include any component of one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.
The computer device may also include an input unit 504, and the input unit 504 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
Although not shown, the computer device may further include a display unit and the like, which are not described in detail herein. Specifically, in this embodiment, the processor 501 in the computer device loads the executable file corresponding to the process of one or more application programs into the memory 502 according to the following instructions, and the processor 501 runs the application programs stored in the memory 502, so as to implement various functions as follows:
after data backup is completed by adopting continuous data protection, acquiring the residual storage capacity of a backup storage space corresponding to the continuous data protection;
judging whether the backup storage space overflows or not according to the residual storage capacity;
if the backup storage space overflows, determining a plurality of target files in a plurality of backup files in the backup storage space;
acquiring data importance levels and backup time points of a plurality of target files;
determining an importance value of the target file according to the data importance level and the backup time point;
determining a file to be deleted in a plurality of target files according to the importance value;
and deleting the files to be deleted so as to increase the residual storage capacity of the backup storage space.
It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.
To this end, an embodiment of the present application provides a computer-readable storage medium, which may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like. The backup management system comprises a backup management module, a backup management module and a storage module, wherein the backup management module is used for storing a backup management program of the backup management module, and the storage module is used for storing a backup management program of the backup management module. For example, the computer program may be loaded by a processor to perform the steps of:
after data backup is completed by adopting continuous data protection, acquiring the residual storage capacity of a backup storage space corresponding to the continuous data protection;
judging whether the backup storage space overflows or not according to the residual storage capacity;
if the backup storage space overflows, determining a plurality of target files in a plurality of backup files in the backup storage space;
acquiring data importance levels and backup time points of a plurality of target files;
determining an importance value of the target file according to the data importance level and the backup time point;
determining a file to be deleted in a plurality of target files according to the importance value;
and deleting the files to be deleted so as to increase the residual storage capacity of the backup storage space.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and parts that are not described in detail in a certain embodiment may refer to the above detailed descriptions of other embodiments, and are not described herein again.
In a specific implementation, each unit or structure may be implemented as an independent entity, or may be combined arbitrarily to be implemented as one or several entities, and the specific implementation of each unit or structure may refer to the foregoing method embodiment, which is not described herein again.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
The backup management method, the computer device, and the storage medium for continuous data protection provided in the embodiments of the present application are described in detail above, and a specific example is applied in the present application to explain the principle and the implementation of the present application, and the description of the above embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, the specific implementation manner and the application scope may be changed, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A backup management method for persistent data protection, comprising:
after data backup is completed by adopting continuous data protection, acquiring the residual storage capacity of a backup storage space corresponding to the continuous data protection;
judging whether the backup storage space overflows or not according to the residual storage capacity;
if the backup storage space overflows, determining a plurality of target files in a plurality of backup files in the backup storage space;
acquiring data importance levels and backup time points of a plurality of target files;
determining an importance value of the target file according to the data importance level and the backup time point;
determining files to be deleted in the plurality of target files according to the importance value;
and deleting the file to be deleted so as to increase the residual storage capacity of the backup storage space.
2. The method for managing backup of persistent data protection as claimed in claim 1, wherein said step of determining a plurality of target files among a plurality of backup files in said backup storage space comprises:
obtaining backup source objects corresponding to a plurality of backup files;
determining the number of backup files of each backup source object;
taking the backup source objects with the number of the backup files larger than the preset number as target backup source objects;
and taking the backup file corresponding to the target backup source object as the target file in the plurality of backup files.
3. The backup management method for continuous data protection according to claim 1, wherein the step of determining the importance value of the target file according to the importance level of the data and the backup time point comprises:
acquiring an importance score corresponding to the data importance level;
determining a time difference between a current time point and the backup time point;
acquiring a time score corresponding to the difference interval where the time difference is located;
and determining the importance value of the target file according to the importance score and the time score.
4. The backup management method for continuous data protection according to claim 1, wherein the step of determining a file to be deleted from the plurality of target files according to the importance value comprises:
according to the importance degree value, sequencing the target files from small to large;
acquiring a preset number of first backup files ranked at the top in the sequencing result;
and determining files to be deleted in the plurality of target files according to the first backup file.
5. The backup management method for continuous data protection according to claim 4, wherein the step of determining a file to be deleted from among the plurality of target files based on the first backup file comprises:
acquiring a first backup source object corresponding to the first backup file and a backup time point of the first backup file;
determining a second backup file with a backup time point later than that of the first backup file in a plurality of backup files corresponding to the first backup source object;
taking the first backup file and the second backup file as the files to be deleted;
after the step of deleting the file to be deleted to increase the remaining storage capacity of the backup storage space, the method further includes:
when a backup recovery request is received, determining a third backup source object and a backup recovery time point corresponding to the backup recovery request;
acquiring a plurality of third backup files corresponding to the third backup source object in the backup storage space and having backup time points earlier than the backup recovery time points;
and sequentially adopting the plurality of third backup files to perform data recovery according to the sequence of the backup time points of the plurality of third backup files.
6. The backup management method for persistent data protection according to claim 5, wherein the step of determining, among the plurality of backup files corresponding to the first backup source object, a second backup file having a backup time point later than the backup time point of the first backup file comprises:
determining backup types of a plurality of backup files corresponding to the first backup source object, wherein the backup types comprise incremental backup and full backup;
determining a third backup file with a backup time point later than that of the first backup file in a plurality of backup files corresponding to the first backup source object and having full backup types;
and determining a second backup file with a backup time point between the backup time point of the first backup file and the backup time point of the third backup file in the plurality of backup files corresponding to the first backup source object.
7. A method for backup management for persistent data protection as claimed in claim 1, wherein said step of obtaining data importance levels of a plurality of said target files comprises:
obtaining a backup source object corresponding to the target file;
determining the file type of the backup source object;
and taking the data importance level corresponding to the file type as the data importance level of the target file.
8. The method for managing backup of persistent data protection as claimed in claim 1, wherein said step of determining a plurality of target files among a plurality of backup files in said backup storage space comprises:
obtaining backup source objects corresponding to a plurality of backup files;
determining the backup change frequency of the backup source object according to the backup time points of a plurality of backup files corresponding to the backup source object;
when the backup change frequency is smaller than a preset frequency, taking a backup source object corresponding to the backup change frequency as a target backup source object;
and taking the backup file corresponding to the target backup source object as the target file in the plurality of backup files.
9. A computer device, characterized in that the computer device comprises:
one or more processors;
a memory; and
one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor to implement the steps in the backup management method for persistent data protection of any of claims 1 to 8.
10. A computer-readable storage medium, having stored thereon a computer program which is loaded by a processor to perform the steps of the backup management method for persistent data protection according to any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210490833.5A CN114579368B (en) | 2022-05-07 | 2022-05-07 | Backup management method for continuous data protection, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210490833.5A CN114579368B (en) | 2022-05-07 | 2022-05-07 | Backup management method for continuous data protection, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114579368A true CN114579368A (en) | 2022-06-03 |
| CN114579368B CN114579368B (en) | 2022-08-02 |
Family
ID=81769361
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210490833.5A Active CN114579368B (en) | 2022-05-07 | 2022-05-07 | Backup management method for continuous data protection, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114579368B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115906170A (en) * | 2022-12-02 | 2023-04-04 | 杨磊 | Safety protection method and AI system applied to storage cluster |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7971091B1 (en) * | 2006-05-02 | 2011-06-28 | Emc Corporation | Network configuration backup and restore operations using continuous data protection |
| WO2014000613A1 (en) * | 2012-06-25 | 2014-01-03 | 腾讯科技（深圳）有限公司 | System repair method and device, and storage medium |
| CN110851415A (en) * | 2019-11-13 | 2020-02-28 | 广州小鹏汽车科技有限公司 | Log data processing method and device of vehicle-mounted system |
| CN112269681A (en) * | 2020-10-16 | 2021-01-26 | 苏州浪潮智能科技有限公司 | Method, device and equipment for continuously protecting virtual machine data |
| CN112306744A (en) * | 2019-07-26 | 2021-02-02 | 浙江宇视科技有限公司 | Log storage backup method, device, server and medium |
-
2022
- 2022-05-07 CN CN202210490833.5A patent/CN114579368B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7971091B1 (en) * | 2006-05-02 | 2011-06-28 | Emc Corporation | Network configuration backup and restore operations using continuous data protection |
| WO2014000613A1 (en) * | 2012-06-25 | 2014-01-03 | 腾讯科技（深圳）有限公司 | System repair method and device, and storage medium |
| CN112306744A (en) * | 2019-07-26 | 2021-02-02 | 浙江宇视科技有限公司 | Log storage backup method, device, server and medium |
| CN110851415A (en) * | 2019-11-13 | 2020-02-28 | 广州小鹏汽车科技有限公司 | Log data processing method and device of vehicle-mounted system |
| CN112269681A (en) * | 2020-10-16 | 2021-01-26 | 苏州浪潮智能科技有限公司 | Method, device and equipment for continuously protecting virtual machine data |
Non-Patent Citations (1)
| Title |
|---|
| 丁宏等: "基于差量备份的文件级持续数据保护", 《信息工程大学学报》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115906170A (en) * | 2022-12-02 | 2023-04-04 | 杨磊 | Safety protection method and AI system applied to storage cluster |
| CN115906170B (en) * | 2022-12-02 | 2023-12-15 | 北京金安道大数据科技有限公司 | Security protection method and AI system applied to storage cluster |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114579368B (en) | 2022-08-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7610511B2 (en) | Journal migration method and data recovery management method | |
| US20070078972A1 (en) | Computer-readable recording medium with system managing program recorded therein, system managing method and system managing apparatus | |
| US7480644B2 (en) | Systems methods, and software for distributed loading of databases | |
| JP4304194B2 (en) | File system management apparatus and method | |
| US20170083535A1 (en) | Managing sequential data store | |
| CN109614045B (en) | Metadata dropping method and device and related equipment | |
| CN114579368B (en) | Backup management method for continuous data protection, computer equipment and storage medium | |
| CN110162429A (en) | System repair, server and storage medium | |
| US20080215843A1 (en) | Storage area management method for a storage system | |
| JP6828253B2 (en) | Backup control device, backup control method and program | |
| US8972352B1 (en) | Probe based backup | |
| CN112433888A (en) | Data processing method and device, storage medium and electronic equipment | |
| CN114201341B (en) | Automatic data backup system, method and device based on cloud platform | |
| CN103440179B (en) | The continuous store method of storage device configurations information | |
| US8589354B1 (en) | Probe based group selection | |
| CN115408342A (en) | File processing method and device and electronic equipment | |
| US7984144B2 (en) | Computer system and a method for managing logical volumes | |
| CN114490432A (en) | Memory processing method and device, electronic equipment and computer readable storage medium | |
| CN114579369A (en) | Data backup method, computer equipment and storage medium | |
| CN110658989B (en) | System and method for backup storage garbage collection | |
| CN109189738A (en) | Choosing method, the apparatus and system of main OSD in a kind of distributed file system | |
| WO2024051738A1 (en) | Data writing method and apparatus, and electronic device and storage medium | |
| CN117170942B (en) | Database backup method based on file system snapshot and related equipment | |
| JP2008234264A (en) | Load balancing device for file server, program for load balancing, and load balancing method | |
| US20210326301A1 (en) | Managing objects in data storage equipment |
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 | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 430070 No. 1, 2 and 10, floors 1-3, building A7, Rongke Zhigu industrial project phase I, No. 555, Wenhua Avenue, Hongshan District, Wuhan City, Hubei Province Patentee after: Wuhan Barda Technology Co.,Ltd. Address before: 430070 No. 1, 2 and 10, floors 1-3, building A7, Rongke Zhigu industrial project phase I, No. 555, Wenhua Avenue, Hongshan District, Wuhan City, Hubei Province Patentee before: Wuhan Sitong Information Service Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder |