CN111290882B - Data file backup method, data file backup device and electronic equipment - Google Patents
Data file backup method, data file backup device and electronic equipment Download PDFInfo
- Publication number
- CN111290882B CN111290882B CN202010087410.XA CN202010087410A CN111290882B CN 111290882 B CN111290882 B CN 111290882B CN 202010087410 A CN202010087410 A CN 202010087410A CN 111290882 B CN111290882 B CN 111290882B
- Authority
- CN
- China
- Prior art keywords
- file
- backup
- pointing
- data
- data file
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 31
- 230000004048 modification Effects 0.000 claims description 10
- 238000012986 modification Methods 0.000 claims description 10
- 238000001514 detection method Methods 0.000 claims description 3
- 238000012545 processing Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 12
- 238000004891 communication Methods 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 238000004140 cleaning Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000003384 imaging method Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007257 malfunction Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- 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
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 present disclosure relates to a data file backup method, a data file backup apparatus, an electronic device, and a non-transitory computer readable storage medium. The data file backup method comprises the following steps: generating a pointing file based on one or more data files to be backed up in the current state, wherein the pointing file records the pointing identifier of each data file to be backed up in the current state; based on the pointing identification, detecting whether all current data files to be backed up are stored in a backup catalog; and if the newly added file which is not stored in the backup directory exists in the data file to be backed up currently, storing the newly added file in the backup directory. By setting the data files which point to the file record backup, all the backup files are stored under one backup catalog, repeated backup and repeated storage are not needed, and the space is saved.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a data file backup method, a data file backup device, an electronic device, and a non-transitory computer readable storage medium.
Background
In a file storage system, in order to prevent a data loss of a file caused by a malfunction, a storage device failure, or an unexpected disaster of the storage device, a data backup mechanism is generally used to backup the file. In the case of misoperation or disaster, the files can be restored through a backup mechanism.
In some related art, backup is performed periodically to repeat backup for many data files, resulting in waste of storage space.
Disclosure of Invention
To overcome the problems in the related art, the present disclosure provides a data file backup method, a data file backup apparatus, an electronic device, and a non-transitory computer readable storage medium.
According to a first aspect of an embodiment of the present disclosure, there is provided a data file backup method, including: generating a pointing file based on one or more data files to be backed up in the current state, wherein the pointing file records the pointing identifier of each data file to be backed up in the current state; based on the pointing identification, detecting whether each current data file to be backed up is stored in a backup catalog; and if the newly added file which is not stored in the backup directory exists in the data file to be backed up currently, storing the newly added file in the backup directory.
In one embodiment, generating the pointing file based on the one or more data files currently all to be backed up includes: based on the current moment, generating a time directory with a current time stamp, and placing the pointing file under the time directory, wherein the time directory and the backup directory are stored under the same backup destination directory.
In one embodiment, generating the pointing file based on the one or more data files currently all to be backed up includes: based on the current moment, the generated pointing file is provided with a current time stamp, wherein the pointing file with the time stamp and the backup catalog are stored under the same backup destination catalog.
In one embodiment, the newly added file includes: the data file generated based on the data modification and/or the data file generated based on the data addition.
In one embodiment, the data file is stored based on an LSM tree structure.
According to a second aspect of the embodiments of the present disclosure, there is provided a data file backup apparatus, including: the generating unit is used for generating a pointing file based on one or more data files to be backed up currently, wherein the pointing file records the pointing identifier of each data file to be backed up currently; the detection unit is used for detecting whether all current data files to be backed up are stored in the backup directory or not based on the pointing identification; and the storage unit is used for storing the newly added file under the backup catalog when the newly added file which is not stored under the backup catalog exists in the data file to be backed up currently.
In an embodiment, the generating unit is configured to: based on the current moment, generating a time directory with a current time stamp, and placing the pointing file under the time directory, wherein the time directory and the backup directory are stored under the same backup destination directory.
In an embodiment, the generating unit is configured to: based on the current moment, the generated pointing file is provided with a current time stamp, wherein the pointing file with the time stamp and the backup catalog are stored under the same backup destination catalog.
In one embodiment, the newly added file includes: the data file generated based on the data modification and/or the data file generated based on the data addition.
In one embodiment, the data file is stored based on an LSM tree structure.
According to a third aspect of embodiments of the present disclosure, there is provided an electronic device, comprising: a memory for storing instructions; and a processor for invoking the instructions stored by the memory to perform any one of the data file backup methods according to embodiments of the present disclosure.
According to a fourth aspect of embodiments of the present disclosure, there is provided a non-transitory computer-readable storage medium comprising: the non-transitory computer readable storage medium stores computer executable instructions that, when executed by a processor, perform any of the data file backup methods of the embodiments of the present disclosure.
The technical scheme provided by the embodiment of the disclosure can comprise the following beneficial effects: by setting the data files which point to the file record backup, all the backup files are stored under one backup catalog, repeated backup and repeated storage are not needed, and the space is saved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
FIG. 1 is a schematic diagram illustrating a conventional data file backup method according to an exemplary embodiment.
FIG. 2 is a schematic diagram illustrating another conventional data file backup method according to an exemplary embodiment.
FIG. 3 is a schematic diagram illustrating a method for backing up data files provided by the present disclosure according to an exemplary embodiment.
FIG. 4 is a schematic diagram illustrating an example of a data file backup method provided by the present disclosure, according to an exemplary embodiment.
FIG. 5 is a schematic diagram illustrating another example of a data file backup method provided by the present disclosure, according to an exemplary embodiment.
FIG. 6 is a schematic diagram illustrating another example of a data file backup method provided by the present disclosure, according to an exemplary embodiment.
FIG. 7 is a schematic block diagram illustrating a data file backup apparatus provided by the present disclosure in accordance with an exemplary embodiment.
Fig. 8 is a schematic block diagram of an apparatus according to an example embodiment.
Fig. 9 is a schematic block diagram of an electronic device, according to an example embodiment.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the invention. Rather, they are merely examples of apparatus and methods consistent with aspects of the invention as detailed in the accompanying claims.
It should be noted that, although the terms "first", "second", etc. are used herein to describe various modules, steps, data, etc. of the embodiments of the present invention, the terms "first", "second", etc. are merely used to distinguish between the various modules, steps, data, etc. and do not denote a particular order or importance. Indeed, the expressions "first", "second", etc. may be used entirely interchangeably.
In some related art, the database is generally implemented by storing data in files of a file system, and there are two ways of storing data in files, namely, a b+ tree and an LSM tree.
In the scheme of b+ tree, the modification database or the new database record directly modifies the existing data file, fig. 1 shows a backup schematic of the b+ tree database, namely, the backup database, that is, the backup directory, the original file a, the original file B, and the original file C, the current backup modifies the file B, and the new file D, and the backup database completed with the file a, the modified file B, the modified file C, and the file D is stored. In this way, the original file B cannot be restored because the original file B is covered by the modification.
In the LSM tree scheme, the modification database or the new database record will not modify the existing data file, but will generate a new data file, fig. 2 shows an LSM tree database backup schematic, where there are file a, file B, and file C in the backup database, the current backup modifies file B, and adds file D, then based on the current backup time, the modified file B and the new file D are separately saved, and at the same time, the original file a, file B, and file C are also backed up, LSM will carry a last modification timestamp for each record, and when reading, the LSM tree database will read the record with the time record furthest back from all the data files and return to the user. In this way, since a full-scale backup is required each time, many data files are repeatedly backed up, and thus the storage space is wasted.
In order to solve the above-mentioned problems, the present disclosure provides a data file backup method 10, as shown in fig. 3, the data file backup method 10 includes the following steps S11 to S13, and the following steps are described in detail:
step S11, generating a pointing file based on one or more data files to be backed up, wherein the pointing file records the pointing identifier of each data file to be backed up.
When a backup is needed, such as a regular backup, or when some data files are modified, added or deleted, the backup may be performed according to a user instruction. At this time, a meta file, i.e. a pointing file, is generated, where the pointing identifier includes a pointing identifier of each data file that needs to be backed up currently, where the pointing identifier may be a file name of the data file or other identifier that can uniquely point to the data file.
In one embodiment, the data file is stored based on an LSM tree structure. In the backup of the database of the LSM tree, the data file is backed up in the form of a new data file after being modified, and in the embodiment of the present disclosure, the newly added file may include: the data file generated based on the data modification may also include a data file generated based on the data addition. The pointing file can be used for checking whether the data is backed up before according to the pointing identification such as the file name or the like during backup and can be used for finding the data file under the backup directory according to the pointing file during data recovery.
In some embodiments, step S11 may further include: based on the current moment, generating a time directory with a current time stamp, and placing the pointing file under the time directory, wherein the time directory and the backup directory are stored under the same backup destination directory. In this embodiment, a time directory may be generated according to the timestamp of the current backup, and the pointing file is placed under the time directory. In other embodiments, step S11 may also include: based on the current moment, the generated pointing file is provided with a current time stamp, wherein the pointing file with the time stamp and the backup catalog are stored under the same backup destination catalog. In this embodiment, the timestamp may be directly set to the pointing file, for example, directly named according to the current time or added with a timestamp label. The two modes can be used for conveniently inquiring when the file needs to be restored.
Step S12, based on the pointing identification, detecting whether each current data file to be backed up is stored in the backup directory.
After generating the pointing file, detecting whether all data files to be backed up currently are included in the backup directory by traversing all data files in the backup directory based on the pointing identifier. For example, if the point is identified as a file name, then it is detected whether each of the file names in the point file can find the same named data file under the backup directory.
Step S13, if there is a new added file not stored in the backup directory in the current data file to be backed up, the new added file is stored in the backup directory.
After the backup directory is detected, if the current data file to be backed up has a new added file compared with the existing file under the backup directory, for example, when a new data file generated by modifying some data files or the new added data file is generated, the new added file is stored under the backup directory. If the data files to be backed up are all stored in the backup directory after the backup directory is detected, the pointing files are stored in the backup destination directory.
In some cases, based on the deletion of data, one or more data files are deleted, and then the pointing file generated at the moment when the backup is needed only includes the pointing identifier corresponding to the currently existing data file, where the number of pointing identifiers in the pointing file may be less than the number of data files in the backup directory, that is, some data files have been deleted, but the backed-up data files in the backup directory still exist. And if no new file is added after detection, storing the pointed file in the backup destination directory.
After backup, the backup catalog can periodically perform data arrangement, or perform data arrangement when the number of files in the backup library is greater than a threshold value, gradually cleaning early pointed files according to time, and cleaning the data files if the pointed files do not have pointed identifiers for one or more data files in the backup catalog after cleaning part pointed files. The data arrangement of the backup library is not limited in this disclosure.
By means of any embodiment, repeated backup can be reduced, waste of storage space of LSM database backup can be reduced, and searching can be facilitated during recovery.
Referring to fig. 4-6, fig. 4-6 illustrate changes to LSM tree database data at times t1-t3, respectively. At time t1, the LSM tree database generates a t1 directory under the backup destination directory, i.e. a real-time directory, wherein meta files, i.e. pointing files, are stored, and the pointing identifiers in the meta files include data files A1, A2 and A3, and at the same time, the backup directory, i.e. whether the three files under the data directory exist or not, is checked, if not, the data files which do not exist are copied under the data directory, wherein the data directory is also stored under the same backup destination directory. At time t2, when the data file A4 is newly added, a t2 directory is generated under the backup destination directory at time t2, wherein one meta file is stored, according to the data file to be backed up at time t2, the generated meta file content is the data file A1, the data file A2, the data file A3 and the data file A4, meanwhile, whether the four files under the data directory exist or not is checked, and if not, the files which do not exist are copied under the data directory. At time t3, modifying the data file A1 to generate a data file A5, and at time t3, generating a t3 directory under the backup destination directory, wherein meta file contents are the data file A1, the data file A2, the data file A3, the data file A4 and the data file A5, checking whether the five files under the data directory exist, and if not, copying the files which do not exist under the data directory.
Fig. 7 is a block diagram illustrating a data file backup apparatus 100 according to an exemplary embodiment. Referring to fig. 7, the data file backup apparatus 100 includes: a generating unit 110, configured to generate a pointing file based on one or more data files that are all to be backed up currently, where the pointing file records a pointing identifier of each data file to be backed up currently; the detecting unit 120 is configured to detect, based on the pointing identifier, whether all current data files to be backed up are stored in the backup directory; the storage unit 130 is configured to store, when there is a new file that is not stored in the backup directory in the current data file to be backed up, the new file in the backup directory.
In an embodiment, the generating unit 110 is configured to: based on the current moment, generating a time directory with a current time stamp, and placing the pointing file under the time directory, wherein the time directory and the backup directory are stored under the same backup destination directory.
In an embodiment, the generating unit 110 is configured to: based on the current moment, the generated pointing file is provided with a current time stamp, wherein the pointing file with the time stamp and the backup catalog are stored under the same backup destination catalog.
In one embodiment, the newly added file includes: based on modifying the generated data file and/or the newly added data file.
In one embodiment, the data file is stored based on an LSM tree structure.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
Fig. 8 is a schematic block diagram of any of the foregoing embodiment apparatus, according to an example embodiment. For example, apparatus 300 may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, exercise device, personal digital assistant, or the like.
Referring to fig. 8, the apparatus 300 may include one or more of the following components: a processing component 302, a memory 304, a power component 306, a multimedia component 308, an audio component 310, an input/output (I/O) interface 312, a sensor component 314, and a communication component 316.
The processing component 302 generally controls overall operation of the apparatus 300, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 302 may include one or more processors 320 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 302 can include one or more modules that facilitate interactions between the processing component 302 and other components. For example, the processing component 302 may include a multimedia module to facilitate interaction between the multimedia component 308 and the processing component 302.
Memory 304 is configured to store various types of data to support operations at apparatus 300. Examples of such data include instructions for any application or method operating on the device 300, contact data, phonebook data, messages, pictures, videos, and the like. The memory 304 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.
The power component 306 provides power to the various components of the device 300. The power components 306 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the device 300.
The multimedia component 308 includes a screen between the device 300 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or slide action, but also the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 308 includes a front-facing camera and/or a rear-facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the apparatus 300 is in an operational mode, such as a photographing mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
The audio component 310 is configured to output and/or input audio signals. For example, the audio component 310 includes a Microphone (MIC) configured to receive external audio signals when the device 300 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 304 or transmitted via the communication component 316. In some embodiments, audio component 310 further comprises a speaker for outputting audio signals.
The I/O interface 312 provides an interface between the processing component 302 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.
The sensor assembly 314 includes one or more sensors for providing status assessment of various aspects of the apparatus 300. For example, the sensor assembly 314 may detect the on/off state of the device 300, the relative positioning of the components, such as the display and keypad of the device 300, the sensor assembly 314 may also detect a change in position of the device 300 or a component of the device 300, the presence or absence of user contact with the device 300, the orientation or acceleration/deceleration of the device 300, and a change in temperature of the device 300. The sensor assembly 314 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. The sensor assembly 314 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 314 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 316 is configured to facilitate communication between the apparatus 300 and other devices, either wired or wireless. The device 300 may access a wireless network based on a communication standard, such as WiFi,2G or 3G, or a combination thereof. In one exemplary embodiment, the communication component 316 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 316 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 300 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.
In an exemplary embodiment, a computer-readable storage medium is also provided, such as memory 304, including instructions executable by processor 320 of apparatus 300 to perform the above-described method. For example, the computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
Fig. 9 is a block diagram of an electronic device 400, according to an example embodiment. For example, the apparatus 400 may be provided as a server. Referring to fig. 9, the apparatus 400 includes a processing component 422 that further includes one or more processors, and memory resources represented by memory 432, for storing instructions, such as applications, executable by the processing component 422. The application program stored in memory 432 may include one or more modules each corresponding to a set of instructions. Further, the processing component 422 is configured to execute instructions to perform the above-described methods.
The apparatus 400 may also include a power component 426 configured to perform power management of the apparatus 400, a wired or wireless network interface 450 configured to connect the apparatus 400 to a network, and an input output (I/O) interface 458. The apparatus 400 may operate based on an operating system stored in the memory 432, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM or the like.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
It is to be understood that the invention is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the invention is limited only by the appended claims.
Claims (10)
1. A method for backing up data files, the method comprising:
generating a pointing file based on one or more data files to be backed up currently, wherein the pointing file records the pointing identifier of each data file to be backed up currently, and the pointing identifier can be the file name of the data file or other identifiers capable of uniquely pointing to the data file;
based on the pointing identifier, detecting whether each data file to be backed up is stored in a backup catalog currently;
if the newly added file which is not stored in the backup catalog exists in the data file to be backed up currently, storing the newly added file in the backup catalog;
the generating a pointing file based on the one or more data files to be backed up currently includes:
and generating a time directory with a current time stamp based on the current time, wherein the pointing file is placed under the time directory, and the time directory and the backup directory are stored under the same backup destination directory.
2. The method of claim 1, wherein generating the pointing file based on the one or more data files currently all to be backed up comprises:
and based on the current moment, the generated pointing file is provided with a current time stamp, wherein the pointing file with the time stamp and the backup catalog are stored under the same backup destination catalog.
3. The method of claim 1, wherein the newly added file comprises: the data file generated based on the data modification and/or the data file generated based on the data addition.
4. The method of claim 1, wherein the data file is stored based on an LSM tree structure.
5. A data file backup apparatus, the apparatus comprising:
the generating unit is used for generating a pointing file based on one or more data files to be backed up currently, wherein the pointing file records the pointing identifier of each data file to be backed up currently, and the pointing identifier can be the file name of the data file or other identifiers capable of uniquely pointing to the data file;
the detection unit is used for detecting whether all the current data files to be backed up are stored in a backup catalog or not based on the pointing identification;
the storage unit is used for storing the newly added file under the backup catalog when the newly added file which is not stored under the backup catalog exists in the data file to be backed up currently;
the generating unit is used for:
and generating a time directory with a current time stamp based on the current time, wherein the pointing file is placed under the time directory, and the time directory and the backup directory are stored under the same backup destination directory.
6. The apparatus of claim 5, wherein the generating unit is configured to:
and based on the current moment, the generated pointing file is provided with a current time stamp, wherein the pointing file with the time stamp and the backup catalog are stored under the same backup destination catalog.
7. The apparatus of claim 5, wherein the newly added file comprises: the data file generated based on the data modification and/or the data file generated based on the data addition.
8. The apparatus of claim 5, wherein the data file is stored based on an LSM tree structure.
9. An electronic device, wherein the electronic device comprises:
a memory for storing instructions; and
a processor for invoking instructions stored in said memory to perform the data file backup method of any of claims 1-4.
10. A non-transitory computer readable storage medium storing computer executable instructions which, when executed by a processor, perform the data file backup method of any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010087410.XA CN111290882B (en) | 2020-02-11 | 2020-02-11 | Data file backup method, data file backup device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010087410.XA CN111290882B (en) | 2020-02-11 | 2020-02-11 | Data file backup method, data file backup device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111290882A CN111290882A (en) | 2020-06-16 |
| CN111290882B true CN111290882B (en) | 2024-02-09 |
Family
ID=71025584
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010087410.XA Active CN111290882B (en) | 2020-02-11 | 2020-02-11 | Data file backup method, data file backup device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111290882B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113157645B (en) * | 2021-04-21 | 2023-12-19 | 平安科技（深圳）有限公司 | Cluster data migration method, device, equipment and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH07230401A (en) * | 1994-02-17 | 1995-08-29 | Hitachi Ltd | Method and system for file maintenance |
| CN104156284A (en) * | 2014-08-27 | 2014-11-19 | 小米科技有限责任公司 | File backup method and device |
| CN104714859A (en) * | 2013-12-17 | 2015-06-17 | 南京壹进制信息技术有限公司 | Rapid backup and recovery method of mass files |
| WO2017028705A1 (en) * | 2015-08-18 | 2017-02-23 | 阿里巴巴集团控股有限公司 | Computer system task backup method, system state recovery method and devices thereof |
| CN107783863A (en) * | 2017-10-26 | 2018-03-09 | 南京壹进制信息技术股份有限公司 | A kind of mass file Fast back-projection algorithm backup method |
| CN107977288A (en) * | 2017-12-15 | 2018-05-01 | 安徽长泰信息安全服务有限公司 | A kind of high efficiency incremental backup system and method easy to recover |
| CN108241555A (en) * | 2016-12-26 | 2018-07-03 | 阿里巴巴集团控股有限公司 | A kind of backup of distributed data base, restoration methods, device and server |
| CN108897638A (en) * | 2018-05-31 | 2018-11-27 | 康键信息技术（深圳）有限公司 | Data back up method, device, computer equipment and storage medium |
| CN109426585A (en) * | 2017-08-22 | 2019-03-05 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus for backing up, restoring database data |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8805789B2 (en) * | 2012-09-12 | 2014-08-12 | International Business Machines Corporation | Using a metadata image of a file system and archive instance to backup data objects in the file system |
-
2020
- 2020-02-11 CN CN202010087410.XA patent/CN111290882B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH07230401A (en) * | 1994-02-17 | 1995-08-29 | Hitachi Ltd | Method and system for file maintenance |
| CN104714859A (en) * | 2013-12-17 | 2015-06-17 | 南京壹进制信息技术有限公司 | Rapid backup and recovery method of mass files |
| CN104156284A (en) * | 2014-08-27 | 2014-11-19 | 小米科技有限责任公司 | File backup method and device |
| WO2017028705A1 (en) * | 2015-08-18 | 2017-02-23 | 阿里巴巴集团控股有限公司 | Computer system task backup method, system state recovery method and devices thereof |
| CN108241555A (en) * | 2016-12-26 | 2018-07-03 | 阿里巴巴集团控股有限公司 | A kind of backup of distributed data base, restoration methods, device and server |
| CN109426585A (en) * | 2017-08-22 | 2019-03-05 | 阿里巴巴集团控股有限公司 | A kind of method and apparatus for backing up, restoring database data |
| CN107783863A (en) * | 2017-10-26 | 2018-03-09 | 南京壹进制信息技术股份有限公司 | A kind of mass file Fast back-projection algorithm backup method |
| CN107977288A (en) * | 2017-12-15 | 2018-05-01 | 安徽长泰信息安全服务有限公司 | A kind of high efficiency incremental backup system and method easy to recover |
| CN108897638A (en) * | 2018-05-31 | 2018-11-27 | 康键信息技术（深圳）有限公司 | Data back up method, device, computer equipment and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| 一种实时数据库备份恢复方法;史英杰;王远;朱恒;粟勇;;计算机应用(S1);全文 * |
| 大数据容灾备份技术挑战和增量备份解决方案;罗圣美;李明;叶郁文;;大数据(03);全文 * |
| 文件备份完整性保证***的设计与实现;耿振民;曾曙;;信息安全与通信保密(07);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111290882A (en) | 2020-06-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101789783B1 (en) | Method, apparatus, program, and recording medium for prompting call | |
| US20180167478A1 (en) | Method and apparatus for displaying notification message | |
| US20170090684A1 (en) | Method and apparatus for processing information | |
| EP3547136A1 (en) | Method and apparatus for communication between webpage and operating system | |
| CN111767006B (en) | Data processing method and device | |
| CN111427449A (en) | Interface display method, device and storage medium | |
| CN116069612A (en) | Abnormality positioning method and device and electronic equipment | |
| EP3460717A1 (en) | Method, apparatus, terminal, and computer-readable storage medium for processing fingerprints | |
| CN111290882B (en) | Data file backup method, data file backup device and electronic equipment | |
| CN107885571B (en) | Display page control method and device | |
| CN114546992A (en) | Database migration method and device, storage medium and electronic equipment | |
| CN111241134B (en) | Data processing method and device | |
| CN114003558A (en) | Data archiving method, device, equipment and storage medium | |
| CN107463414B (en) | Application installation method and device | |
| CN116361071B (en) | Backup file generation method, device, equipment and storage medium | |
| CN113946346B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN111274210B (en) | Metadata processing method and device and electronic equipment | |
| CN113934452B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN114020504B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN111625251B (en) | Method and device for processing application instance | |
| CN111880696B (en) | Encyclopedic-based data processing method and device | |
| CN117952129A (en) | User identification card fault detection method and device and readable storage medium | |
| CN116009946A (en) | Git-based code statistics method and device | |
| CN114416085A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN114116075A (en) | Page parameter acquisition method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 100085 unit C, building C, lin66, Zhufang Road, Qinghe, Haidian District, Beijing Applicant after: Beijing Xiaomi pinecone Electronic Co.,Ltd. Address before: 100085 unit C, building C, lin66, Zhufang Road, Qinghe, Haidian District, Beijing Applicant before: BEIJING PINECONE ELECTRONICS Co.,Ltd. |
|
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |