WO2024259890A1 - Procédé de sauvegarde de données, dispositif électronique, et support d'enregistrement lisible par ordinateur - Google Patents

Procédé de sauvegarde de données, dispositif électronique, et support d'enregistrement lisible par ordinateur Download PDF

Info

Publication number
WO2024259890A1
WO2024259890A1 PCT/CN2023/133236 CN2023133236W WO2024259890A1 WO 2024259890 A1 WO2024259890 A1 WO 2024259890A1 CN 2023133236 W CN2023133236 W CN 2023133236W WO 2024259890 A1 WO2024259890 A1 WO 2024259890A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
buffer
backup
hardware acceleration
buffers
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.)
Ceased
Application number
PCT/CN2023/133236
Other languages
English (en)
Chinese (zh)
Inventor
闫泳冰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
XFusion Digital Technologies Co Ltd
Original Assignee
XFusion Digital Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by XFusion Digital Technologies Co Ltd filed Critical XFusion Digital Technologies Co Ltd
Publication of WO2024259890A1 publication Critical patent/WO2024259890A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 operations
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 operations
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1456—Hardware arrangements for backup
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/172—Caching, prefetching or hoarding of files
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/182—Distributed file systems
    • G06F16/184—Distributed file systems implemented as replicated file system
    • G06F16/1844—Management specifically adapted to replicated file systems

Definitions

  • the present application relates to the field of databases, and in particular to a data backup method, an electronic device, and a computer-readable storage medium.
  • the embodiments of the present application disclose a data backup method, an electronic device, and a computer-readable storage medium, which can improve the physical backup efficiency of a database.
  • the first aspect discloses a data backup method, which can be applied to electronic devices, modules in electronic devices (e.g., chips, central processing units, etc.), and logic modules or software (such as the backup tool described below) that can implement all or part of the functions of electronic devices.
  • the electronic device may include a central processing unit, a memory, and a hardware acceleration device, and the memory may include a first buffer. The following description is based on the application to the electronic device as an example.
  • the data backup method may include: reading the first data in the first data file, and storing the first data in the first buffer, wherein the first data file is stored in a data disk corresponding to the original database directory; compressing the first data in the first buffer by the hardware acceleration device to generate backup data corresponding to the first data; and writing the backup data to the data disk corresponding to the backup directory.
  • the first data when performing a physical backup of a database, the first data may be first stored in a first buffer, and then the data may be compressed by a hardware acceleration device in units of the first buffer.
  • the performance of the hardware acceleration device may be fully utilized, thereby improving the efficiency of data compression, and further improving the efficiency of the physical backup of the database.
  • the overall power consumption of the electronic device may be reduced.
  • the reading of the first data in the first data file and the storing of the first data in the first buffer include: opening the first data file; when the first buffer does not store or is not full of the first data, reading the first data in the first data file and storing the first data in the first buffer.
  • the first buffer when the first buffer is not filled with or has not been fully filled with the first data, the first data in the first data file is read and the read first data is stored in the first buffer. In this way, it can be ensured that The first data stored in the first buffer will not be overwritten, thereby ensuring the integrity of the data and further ensuring the integrity of the backup data.
  • compressing the first data in the first buffer by using the hardware acceleration device includes: when the first buffer is full of the first data, compressing the first data in the first buffer by using the hardware acceleration device.
  • the data in the first buffer is compressed, which can maximize the performance of the hardware acceleration device, thereby increasing the speed of physical backup of the database.
  • the method may further include: after the hardware acceleration device completes compressing the first data in the first buffer, changing the state of the first buffer to an idle state.
  • a status mark can be set for the first buffer.
  • the first buffer can be used to write the first data into the first buffer.
  • the status mark of the first buffer is not idle, the first buffer cannot be used. In this way, it can be ensured that the electronic device can fully use the first buffer based on the status mark of the first buffer.
  • the method further includes: reading remaining data from the first data file, and storing the remaining data in a second buffer, where the second buffer is any other buffer in the first buffer that does not store or is not fully filled with the first data; when the hardware acceleration device completes compressing the first data in a first buffer, compressing the data in the second buffer through the hardware acceleration device.
  • storing the first data in the first buffer includes: verifying the first data; and if the verification is successful, storing the first data page in the first buffer.
  • a check can be performed first, and if the check succeeds, the read first data is stored in the first buffer, so that the storage of wrong data can be avoided and the accuracy of the backup data can be ensured.
  • the wrong data can be discarded through data check, and the data that needs to be compressed can be reduced, thereby saving the processing resources of the electronic device and reducing the overall power consumption of the electronic device.
  • the method also includes: reading first data from multiple data files under the original database directory through multiple threads, and storing the first data in different data files read into multiple buffers where the first data is not stored or is not full in the first buffers; when the third buffer is full, compressing the data in the third buffer through the hardware acceleration device, and the third buffer is any full buffer among the multiple first buffers.
  • data can be written to multiple buffers through multiple threads. In this way, it can be ensured that the hardware acceleration device of the electronic device always has a full buffer for compression, so that the performance of the hardware acceleration device can be fully utilized, and the efficiency of physical backup of the database can be further improved.
  • the electronic device includes multiple hardware acceleration devices
  • the method further includes: when there are multiple full buffers in the multiple first buffers, compressing the data in the multiple full buffers in parallel by processing the multiple hardware acceleration devices.
  • the electronic device may include multiple hardware acceleration devices.
  • the electronic device may Multiple hardware acceleration devices compress data in multiple buffers in parallel, which can further improve the efficiency of database physical backup.
  • the number of threads is determined according to the first time, the second time, and the number of hardware acceleration devices included in the electronic device; the first time is the time required to read the first data from the original database directory to fill a first buffer zone, and the second time is the time required for a hardware acceleration device to complete compressing a full first buffer zone, and for the central processor to write the corresponding backup data into the data disk corresponding to the backup directory.
  • the data of the thread to be started can be determined according to the first time, the second time, and the number of hardware acceleration devices, so that the number of threads can be matched with the processing capability of the hardware acceleration device included in the electronic device. While ensuring that the hardware acceleration device of the electronic device always has a full buffer for compression, the processor resources of the electronic device will not be excessively occupied.
  • the number of the buffers is determined based on the first time, the second time, and the number of hardware acceleration devices included in the electronic device; the first time is the time required to read the first data from the original database directory to fill a first buffer, and the second time is the time required for a hardware acceleration device to complete compressing a full first buffer, and for the central processor to write the corresponding backup data to the data disk corresponding to the backup directory.
  • the number of buffers that need to be set can be determined based on the first time, the second time, and the number of hardware acceleration devices. In this way, it can be ensured that the number of buffers is compatible with the number of threads and the processing capabilities of the hardware acceleration devices included in the electronic device, and the memory resources of the electronic device will not be excessively occupied.
  • the method further includes: during the data backup process, dynamically adjusting the number of threads and/or the number of buffers according to the first time, the second time, and the number of hardware acceleration devices included in the electronic device.
  • the first time and the second time can be variable, so the electronic device can dynamically adjust the number of buffers and the number of threads to improve the utilization efficiency of buffer resources and thread resources.
  • the dynamic adjustment of the number of buffers and the number of threads can ensure that memory resources and processor resources are not excessively occupied, and the number of buffers and the number of threads are not insufficient, and the performance of the hardware acceleration device cannot be brought into play.
  • the central processing unit includes the hardware acceleration device.
  • the hardware acceleration device can be integrated into the central processing unit, so that the communication delay between the hardware acceleration device and the central processing unit can be reduced, thereby further improving the efficiency of physical backup of the database.
  • a second aspect discloses an electronic device, the computing device comprising a processor and a memory, the processor calling a computer program stored in the memory to implement a data backup method as provided in the first aspect and any possible implementation of the first aspect.
  • the third aspect discloses a computer-readable storage medium, on which a computer program or computer instructions are stored. When the computer program or computer instructions are executed, the data backup method disclosed in the above aspects is implemented.
  • a fourth aspect discloses a chip, including a processor for executing a program stored in a memory.
  • the chip executes the data backup method disclosed in the above aspects.
  • the memory is located outside the chip.
  • a sixth aspect discloses a computer program product, which includes a computer program code.
  • the data backup method disclosed in the above aspects is executed.
  • FIG1 is a schematic diagram of the structure of an electronic device disclosed in an embodiment of the present application.
  • FIG2 is a schematic diagram of a scenario of physical backup of a database disclosed in an embodiment of the present application.
  • FIG3 is a schematic diagram of a software structure of an electronic device disclosed in an embodiment of the present application.
  • FIG4 is a schematic diagram of a scenario in which a backup tool disclosed in an embodiment of the present application performs physical backup of a database
  • FIG5 is a flow chart of a database physical backup method disclosed in an embodiment of the present application.
  • FIG6 is a flow chart of another database physical backup method disclosed in an embodiment of the present application.
  • FIG. 7 is a flow chart of another database physical backup method disclosed in an embodiment of the present application.
  • FIG8 is a flow chart of another database physical backup method disclosed in an embodiment of the present application.
  • FIG9 is a flow chart of another database physical backup method disclosed in an embodiment of the present application.
  • FIG. 10 is a flow chart of another database physical backup method disclosed in an embodiment of the present application.
  • the embodiment of the present application discloses a database physical backup method, an electronic device and a computer-readable storage medium, which can improve the efficiency of database physical backup and reduce the hard disk space occupied.
  • the technical solution in the embodiment of the present application will be clearly and completely described below in conjunction with the drawings in the embodiment of the present application.
  • a database cluster is generally a database system composed of multiple machines. One or more databases can be created on a database cluster. A machine in a database cluster is called a node.
  • Database clusters may include centralized database clusters, distributed database clusters, and the like.
  • a centralized database cluster may include a host (master node) and multiple backup machines (slave nodes), and the data stored in the host and backup machines may be the same.
  • a distributed database cluster may also include master nodes and slave nodes, each node may store a certain slice of data, and the data slices stored by multiple nodes may be spliced together into a complete data.
  • the master node in the database cluster may manage and monitor each slave node, or the database cluster may include a separate management node for managing the master node or slave nodes, which is used to manage and monitor each slave node.
  • the master node may issue data operation instructions, such as data backup instructions, to each slave node, instructing the slave node to perform data backup.
  • Hardware acceleration technology is a technology that uses hardware devices to speed up processing, such as speeding up compression, decompression, decryption, encryption, random number generation, digital signature, video encoding and decoding, etc.
  • dedicated hardware for specific processing can be designed.
  • dedicated hardware for specific processing can be designed to improve data compression efficiency.
  • these dedicated hardware for specific processing can be referred to as hardware acceleration devices.
  • hardware acceleration devices can be used to assist the central processing unit (CPU) in its work to improve overall processing efficiency.
  • computationally intensive tasks tasks with large computational requirements
  • hardware acceleration devices can be assigned to hardware acceleration devices to reduce the pressure on the CPU and increase the overall processing speed.
  • hardware acceleration devices are dedicated hardware designed for specific processing, they have lower power consumption than CPUs.
  • RISC machine for hardware acceleration technology, it can include QAT (quick assist technology) under the x86 architecture and KAE (Kunpeng accelerator engine) under the arm (advanced RISC machine) architecture.
  • QAT quick assist technology
  • KAE Kerpeng accelerator engine
  • arm advanced RISC machine
  • the physical backup of the database refers to copying one or more copies of the data files under the original database directory and storing them in other directories respectively. These directories can be called backup directories.
  • the backup set refers to a collection of database backup files, that is, one or more backup files stored in the backup directory.
  • each backup file under the backup directory can be a compressed file
  • the data files under the original database directory can correspond one to one with the backup files under the backup directory.
  • the original database directory can be the directory of the database to be backed up.
  • the physical backup of a database may include four steps: reading data, verifying, compressing, and writing to disk.
  • the database usually uses fixed-size data pages (page) to store data, such as the size of each data page can be 8 kilobytes (KB).
  • the backup tool backup software
  • the electronic device can read 8KB data pages from the data file of the database in turn. After that, the electronic device can verify the read 8KB data pages in turn and calculate their checksums.
  • the electronic device can use a compression algorithm implemented by software, such as lz4, zlib, zstd and other software compression algorithms, to compress the 8KB data pages after verification in turn. Finally, the electronic device can write the compressed data pages to the disk in turn and store them in the corresponding backup directory to generate a backup set.
  • software such as lz4, zlib, zstd and other software compression algorithms
  • each data page needs to be verified page by page, and each verified data page needs to be compressed page by page.
  • verification and compression are both computationally intensive tasks, which require a large amount of CPU resources. Any processing in verification and compression may make the CPU work at full capacity. Therefore, in the case of limited CPU resources, verification and compression are generally performed serially.
  • compression is a relatively time-consuming process, which usually accounts for 50% of the total time of physical backup, or even more.
  • hardware acceleration technology can be used in database physical backup, that is, data page compression can be performed by hardware acceleration device.
  • one or more buffers can be set, and the data pages to be compressed can be stored in the buffers first.
  • the hardware acceleration device can compress batches of data pages in units of buffers, thereby ensuring that the performance of the hardware acceleration device is fully utilized.
  • FIG. 1 is a schematic diagram of the structure of an electronic device disclosed in an embodiment of the present application.
  • the electronic device 100 may be a mobile phone terminal, a tablet computer, a laptop computer, a desktop computer, a server, etc., which is not limited in the embodiment of the present application.
  • the electronic device 100 may include: a central processing unit 101, a hardware acceleration device 102, a memory 103 and Hard disk 104
  • the CPU 101 , the hardware acceleration device 102 , the memory 103 and the hard disk 104 may be connected to each other or connected to each other via a bus 105 .
  • the hard disk 104 can be used to store the data files of the database.
  • the central processing unit 101 can be used to read the data files in the database from the hard disk and perform operations such as verification.
  • the memory 103 can be used to provide one or more buffers to temporarily store the data pages after verification.
  • the hardware acceleration device 102 can compress the batch data pages in units of buffers to obtain the compressed backup data packets.
  • the compressed backup data packets can be stored in the hard disk 104.
  • the hardware acceleration device 102 may be dedicated hardware with a data compression function to assist the central processor 101 in improving the efficiency of data compression.
  • the hardware acceleration device 102 may be a QAT acceleration card, a KAE acceleration card, and the like.
  • hard disk 104 can be a hard disk drive (HDD) or a solid state drive (SSD), etc.
  • HDD hard disk drive
  • SSD solid state drive
  • FIG1 only illustrates one central processing unit, one hardware acceleration device, one memory and one hard disk, but in actual situations, the electronic device may include two, three, four or more central processing units, hardware acceleration devices, memories and hard disks, and the embodiments of the present application are not limited to this.
  • the central processor 101 and the hardware acceleration device 102 can be independently set or integrated together, such as integrating the hardware acceleration device 102 into the central processor 101.
  • the electronic device 100 can be a node in a centralized database cluster, a node in a distributed database cluster, or other devices including a database.
  • each node (including the master node and the slave node) can automatically back up the data files in the database, or the master node or the management node can uniformly issue a backup command, and each node backs up the data files in the database after receiving the backup command.
  • the system architecture shown in Figure 1 is only an exemplary description and does not constitute a limitation.
  • the electronic device 100 may also include more or fewer components, or different component configurations, etc., which are not limited here.
  • the physical backup process of the present application is exemplarily described below in conjunction with FIG. 2 .
  • Figure 2 is a schematic diagram of a scenario of physical backup of a database disclosed in an embodiment of the present application.
  • the storage space corresponding to the original database directory of the database is the main data disk
  • the storage space corresponding to the backup directory is the backup (copy) data disk.
  • the backup directory may include a corresponding number of backup files for the number of data files included in the original database directory, that is, the data files under the original database directory may correspond one-to-one to the backup files under the backup directory.
  • the organization of the backup files under the backup directory may be the same as the organization of the data files under the original database directory.
  • the organization method here may include the adopted data structure, the relationship between the data, etc.
  • the CPU can read the data pages in the data files under the original database directory from the main data disk in sequence, and can verify the read data pages.
  • the CPU can store the verified data pages in an idle buffer.
  • buffer A is currently in an idle state, and the CPU can store the verified data pages in buffer A.
  • buffer A is full, the CPU can mark buffer A as busy.
  • the CPU can set a status tag for the buffer and set the status tag to busy.
  • the CPU can notify the hardware acceleration device to compress the data pages in buffer A to obtain a compressed backup data packet, and can The compressed backup data packet is stored in the storage space corresponding to the backup directory in the backup data disk.
  • the CPU can change the state tag of the A buffer to an idle state so that the data page to be backed up can be rewritten.
  • the busy state indicates that the buffer is full of data
  • the free state indicates that no data is stored in the buffer or that the buffer is not full of data
  • the hardware acceleration device compresses the data pages in the A buffer, while the CPU can continue to read the data pages in the data file under the original database directory from the main data disk, and store the read data pages in the buffer B.
  • the buffer B is full, the hardware acceleration device is notified to compress the data pages in the B buffer.
  • the A buffer and the B buffer can be used to alternately store the verified data pages.
  • the CPU can continue to store the verified data pages through the B buffer.
  • the B buffer is full and the A buffer is free again, it can be stored through the A buffer again. In this way, the verification and compression of the data pages can be performed in parallel, thereby improving the overall efficiency of the physical backup of the database.
  • two buffers are used to illustrate the processing flow of physical backup of the database, but the embodiment of the present application does not limit the number of buffers. For example, one buffer, three, four or more buffers may also be set.
  • the storage space corresponding to the original database directory and the backup directory can be the same hard disk, such as both being the primary data disk. In other words, the data files under the original database directory and the backup files under the backup directory can be stored in the same hard disk.
  • a very efficient compression algorithm is implemented in hardware (including various processing circuits) inside the hardware acceleration device, and the compression performance is far better than the compression algorithm implemented in software (such as lz4, zlib, zstd, etc.).
  • the hardware acceleration device has a faster compression speed and a smaller compression volume. Therefore, in the above-mentioned processing flow, the compression of data pages by the hardware acceleration device can shorten the time required for compression. At the same time, considering that the compression of data pages by the hardware acceleration device will bring communication overhead between hardware, such as the communication overhead between the CPU and the hardware acceleration device.
  • one or more buffers can be set in the embodiment of the present application. When the buffer is full, the hardware acceleration device is notified to perform compression processing on all data pages in the buffer. In this way, the communication overhead between hardware can be reduced and the computing power of the hardware acceleration device can be fully utilized.
  • the electronic device 100 may include a database 106, and the database 106 may include a backup tool 1061. That is, the backup tool 1061 may be a subprogram module in the database 106.
  • FIG. 4 is a schematic diagram of a scenario in which a backup tool disclosed in an embodiment of the present application performs a physical backup of a database.
  • the backup tool 1061 can read the data files in the database from the master data disk, perform operations such as verification, and store the verified data pages into a buffer in the memory, such as buffer A, buffer B, etc.
  • the backup tool 1061 can call the data compression API provided by the hardware acceleration device, and the data compression API will call the driver of the hardware acceleration device accordingly, and the driver of the hardware acceleration device
  • the program drives the hardware acceleration device to compress the data pages in the buffer, and a compressed backup data packet can be obtained.
  • the backup tool 1061 can store the compressed backup data packet in a backup file under the backup directory to generate a complete backup set.
  • backup tool 1061 For a more detailed description of the backup tool 1061, please refer to the relevant description in the following method embodiment, which will not be repeated here.
  • the backup tool 1061 may not be a submodule of the database 106 , but may be an independent module.
  • the software structure shown in Figure 3 is only an exemplary description and does not constitute a limitation. In other embodiments of the present application, the software structure shown in Figure 3 may include more or fewer software modules than shown in the figure.
  • FIG5 is a flow chart of a database physical backup method disclosed in an embodiment of the present application. As shown in FIG5, it is a processing flow of database physical backup under a single buffer setting.
  • the processing method can be executed by a central processing unit CPU, specifically, the processor can call a program in a backup tool to execute.
  • the processing flow may include but is not limited to the following steps:
  • the CPU opens the first data file in the original database directory.
  • the first data file may be any unbacked-up data file stored in the primary data disk and can be found through the original database directory.
  • the CPU can back up the data files in the original database directory in sequence, generate corresponding backup files, and store them in the backup data disk corresponding to the backup directory.
  • the CPU can first open any unbacked up data file in the original database directory to facilitate reading the data pages therein.
  • the CPU reads data pages from the first data file in sequence, and stores the read data pages in the first buffer in sequence.
  • the hardware acceleration device of the electronic device can compress batch data pages in units of buffers. Therefore, in the case of a single buffer, the CPU can first determine whether the first buffer is in an idle state. If the first buffer is in a non-idle state, that is, in a busy state, the CPU can wait for the first buffer to be idle. If the first buffer is in an idle state, the CPU can read the data pages from the first data file in sequence, and store the read data pages in the first buffer in sequence until the first buffer is full. It should be understood that there may be an order between the data pages in the data file, and each data page may include an identifier, such as a logical address, a data page number, etc.
  • reading the data pages in sequence from the first data file can be understood as reading in sequence in the order of the data pages, such as reading continuous data pages in sequence in the order of the logical addresses.
  • the first buffer defaults to an idle state.
  • the size of the first buffer can be N times the size of the data page, and N is an integer greater than or equal to 2.
  • N can be 8, 16, etc.
  • the size of the first buffer can be 64KB, 128KB, etc.
  • the first buffer may be a storage area opened in the memory of the electronic device, and may be used by the electronic device to temporarily store data pages that need to be compressed during a database physical backup process.
  • the number of remaining unread data pages in the first data file may be small and insufficient to fill the first buffer.
  • the remaining unread data pages in the first data file can be stored in the first buffer, and then the first buffer can be considered full.
  • the CPU before the CPU stores the read data pages into the first buffer in sequence, it may first verify the read data pages in sequence.
  • the verification here includes two situations.
  • One situation is: for each data page Calculate the check code.
  • the CPU after the CPU calculates the check code for each data page, it can store the data page and the corresponding check code together in the first buffer (such as attaching the check code to the end of the corresponding unbacked up data page), so that the accuracy of the data can be verified when restoring the data based on the backup set later.
  • Another case is: calculate the check code for each data page, and compare it with the previously calculated check code to determine whether the currently read data page is accurate.
  • the CPU calculates the check code for each data page, it can compare the currently calculated check code with the previously calculated check code for the data page (such as the check code calculated when the data page was previously stored in the main data disk). If they are the same, it indicates that the currently read unbacked up data page is correct and can be stored in the first buffer. If they are different, it indicates that the currently read unbacked up data page is wrong and this data page can be skipped, or data recovery can be performed.
  • check code is usually obtained through some kind of operation based on the original data to verify the correctness of the original data.
  • Commonly used check codes may include parity check code, Hamming check code, cyclic redundancy check (CRC) code, etc.
  • the CPU changes the state of the first buffer to a busy state, and compresses multiple data pages in the first buffer through a hardware acceleration device to obtain a corresponding backup data packet.
  • the first buffer will be full.
  • the CPU can change the state of the first buffer to a busy state.
  • the CPU can notify the hardware acceleration device to compress the data pages in the first buffer.
  • the backup data packet includes the corresponding backup data packet obtained by compressing the data pages in the first buffer by the hardware acceleration device.
  • the backup data packet corresponding to the data page in the first buffer can also be understood as the compressed data corresponding to the data page in the first buffer.
  • the CPU compressing the multiple data pages in the first buffer through the hardware acceleration device may specifically include: the CPU may call the compression API (application programming interface) provided by the hardware acceleration device, the compression API will correspondingly call the driver of the hardware acceleration device, and the driver of the hardware acceleration device will drive the hardware acceleration device to compress the multiple data pages in the first buffer.
  • the compression API application programming interface
  • the CPU calls the compression API provided by the hardware acceleration device, it may provide corresponding parameters, such as the address of the first buffer, so that the hardware acceleration device can compress the multiple data pages in the first buffer.
  • the CPU writes the corresponding backup data packet into the backup data disk corresponding to the backup directory, and changes the state of the first buffer to an idle state.
  • the hardware acceleration device can notify the CPU that the compression of the first buffer is complete. Afterwards, the CPU can compress the multiple data pages in the first buffer, and write the corresponding backup data packets obtained into the backup data disk corresponding to the backup directory. In addition, the CPU can change the state of the first buffer to an idle state so that the data pages to be backed up can be rewritten, that is, the remaining unread data pages. It should be noted that after the hardware acceleration device has compressed the data in the first buffer, the compressed backup data packets can be stored in the first buffer or in other idle buffers. For these two different situations, the time for the first buffer to change to an idle state can be different.
  • the compressed backup data packet is stored in the first buffer, it is necessary to wait for the CPU to write the backup data packet to the backup data disk corresponding to the backup directory. After the backup data packet is written to the backup data disk corresponding to the backup directory, the state of the first buffer can be changed to an idle state. If the compressed backup data packet is stored in other idle buffers, the state of the first buffer can be changed to an idle state after the hardware acceleration device has compressed the data pages of the first buffer, and there is no need to wait. The backup data package is written to the backup data disk corresponding to the backup directory.
  • the CPU determines whether the first data file has been backed up. If the first data file has not been backed up, the CPU executes step 502. If the first data file has been backed up, the CPU executes step 506.
  • the CPU After the CPU writes the backup data packets corresponding to the multiple data pages in the first data file into the backup data disk corresponding to the backup directory, it can determine whether the first data file has been backed up, that is, whether the first data file still includes data pages that have not been backed up or data pages that have not been read. If the first data file has not been backed up (the first data file still includes data pages that have not been backed up), the CPU can continue to read the data pages that have not been backed up in the first data file and execute step 502. If the first data file has been backed up (the first data file does not include data pages that have not been backed up), the CPU can continue to determine whether the original database directory still includes data files that have not been backed up and execute step 506.
  • the CPU determines whether the original database directory includes data files that have not been backed up. If the original database directory includes data files that have not been backed up, step 501 may be executed. If the original database directory does not include data files that have not been backed up, step 507 may be executed. When the first data file is backed up, the CPU may determine whether the original database directory includes data files that have not been backed up. If the original database directory includes data files that have not been backed up, the CPU may continue to open any data file that has not been backed up in the original database directory and may execute step 501. If the original database directory does not include data files that have not been backed up, that is, all data files in the original database directory have been backed up, the CPU may execute step 507.
  • the first data file is first backed up to the first backup data disk, and then the first data file is backed up to the second backup data disk. Therefore, when judging whether a first data file is an unbacked up data file, or judging whether a data page is an unbacked up data page, there may be different judgment results due to the above reasons. Based on this, in the embodiment of the present application, for the above steps 502-507, the CPU judges whether the first data file includes unbacked up data pages.
  • the unbacked up data pages refer to data pages that have not been backed up during this backup process, such as the process of steps 501-507 executed this time, and the CPU judges whether the original database directory also includes unbacked up data files, which refers to data files that have not been backed up during this backup process, such as the process of steps 501-507 executed this time.
  • backup data disk and the primary data disk may be the same physical hard disk or different physical hard disks.
  • the CPU completes the physical backup of the database and releases related resources.
  • the backup directory may include complete backup files, and the CPU may end the physical backup of the database and release related resources, such as releasing memory resources such as the first buffer.
  • step 506 can be executed first.
  • the CPU can execute step 507.
  • the CPU can execute step 501 and the following steps 502 to 505.
  • step 506 can be executed again to continue to determine whether the original database directory still includes unbacked up data files.
  • the above steps 501 to 507 It can be divided into two independent execution processes, one is responsible for writing the unbacked up data pages to the first buffer, and the other is responsible for compressing the data pages in the first buffer.
  • These two processing flows can be executed in parallel and can be associated through the state of the first buffer.
  • it can be a processing flow for writing data pages to the first buffer.
  • the CPU can detect whether the first buffer is in an idle state.
  • the CPU can continuously write unbacked up data pages to the first buffer.
  • it can be a processing flow for compressing data pages in the first buffer through a hardware acceleration device.
  • the CPU When compressing data pages in the first buffer, the CPU can detect whether the first buffer is in a busy state. When the first buffer is in a busy state, that is, when the first buffer is full, the CPU can compress the data pages in the first buffer through the hardware acceleration device, and write the compressed backup data packets into the backup data disk corresponding to the backup directory.
  • the relevant steps in Figures 6 and 7 can refer to the relevant descriptions in the above steps 501-step 507, which will not be repeated in detail here.
  • the CPU when the CPU performs physical backup of the database, it can compress batch data pages in units of buffers through the hardware acceleration device, which can greatly improve the efficiency of data compression, thereby increasing the speed of physical backup of the database.
  • FIG5 is a database physical backup process under a single buffer, but in actual situations, multiple buffers can also be used during database physical backup, so that data reading and compression can be performed in parallel, or data reading, verification and compression can be performed in parallel, thereby further improving the speed of database physical backup.
  • the following is an exemplary description of the database physical backup process under multiple buffer settings in conjunction with FIG8 and FIG9.
  • FIG8 can be a process for writing unbacked up data pages into a buffer in an idle state under a multiple buffer setting
  • FIG9 can be a process for compressing data pages in a buffer in a busy state through a hardware acceleration device under a multiple buffer setting.
  • the processing flow may be executed by a central processing unit (CPU), specifically, the processor may call a program in a backup tool to execute the processing flow, and the processing flow may include but is not limited to the following steps:
  • 801.CPU opens the first data file in the original database directory.
  • the first data file may be any unbacked-up data file stored in the primary data disk and can be found through the original database directory.
  • Step 801 is similar to step 501 , and reference may be made to the relevant description in the above step 501 .
  • the CPU reads data pages from the first data file in sequence, and stores the read data pages in the second buffer in sequence.
  • the second buffer may be any buffer in an idle state among the multiple buffers.
  • the CPU may first determine whether there is a buffer in an idle state among the multiple buffers. If there is no buffer in an idle state among the multiple buffers, the CPU may wait for the multiple buffers to be idle. If there is a buffer in an idle state among the multiple buffers, the CPU may read data pages from the first data file in sequence, and store the read data pages in the second buffer in sequence until the second buffer is full. In the initial state, the multiple buffers are in an idle state by default. It should be understood that the multiple buffers may be buffers opened from the memory space for storing the data pages to be backed up.
  • the number of remaining unread data pages in the first data file may be small and insufficient to fill the second buffer.
  • the first data file may be read from the remaining data pages. All remaining unread data pages in a data file are stored in the second buffer, and the second buffer can be considered to be full.
  • the CPU may first verify the read data pages that have not been backed up in sequence.
  • data page verification please refer to the relevant description in step 501, which will not be repeated here.
  • the CPU changes the state of the second buffer to a busy state.
  • the second buffer will be full.
  • the CPU can change the state of the second buffer to a busy state.
  • the CPU can notify the hardware acceleration device to compress the data pages in the second buffer.
  • the CPU determines whether the first data file has been backed up. If the first data file has not been backed up, the CPU executes step 802; if the first data file has been backed up, the CPU executes step 805.
  • the CPU After the CPU has filled the second buffer, it can determine whether the first data file has been backed up, that is, whether the first data file still includes data pages that have not been backed up. If the first data file has not been backed up, the CPU can continue to read the data pages that have not been backed up in the first data file and execute step 802. If the first data file has been backed up, the CPU can continue to determine whether the original database directory still includes data files that have not been backed up and execute step 805.
  • step 805 The CPU determines whether the original database directory includes any unbacked-up data files. If the original database directory includes any unbacked-up data files, step 801 may be executed. If the original database directory does not include any unbacked-up data files, step 806 may be executed.
  • the CPU may determine whether the original database directory still includes data files that have not been backed up. If the original database directory includes data files that have not been backed up, the CPU may continue to open any data file that has not been backed up in the original database directory and execute step 801. If the original database directory does not include data files that have not been backed up, that is, all data files in the original database directory have been backed up, the CPU may execute step 806.
  • the CPU completes the physical backup of the database and releases related resources.
  • the backup directory may include complete backup files, and the CPU may end the physical backup of the database and release related resources, such as releasing memory resources such as the second buffer.
  • the processing flow shown in FIG. 9 is introduced below. As shown in FIG. 9 , the processing flow may be executed by a central processing unit (CPU), and specifically may be executed by the processor calling a program in a backup tool.
  • the processing flow may include but is not limited to the following steps:
  • the CPU can obtain a corresponding backup data packet by compressing multiple data pages in the third buffer through a hardware acceleration device.
  • the third buffer may be any buffer in a busy state among the multiple buffers.
  • the CPU can continue to write the data pages to be backed up into the free buffers in the multiple buffers.
  • the CPU can notify the hardware acceleration device to compress the data pages in the buffer. Therefore, when there is a buffer in a busy state among the multiple buffers of the CPU, the CPU can compress the multiple data pages in the third buffer through the hardware acceleration device, and obtain the corresponding backup data packet.
  • the CPU can compress the multiple data pages in buffer a through the hardware acceleration device, and then compress the multiple data pages in buffer b.
  • the hardware acceleration device when there are multiple buffers in a busy state, can compress the data pages in the multiple buffers in a busy state in parallel, thereby improving the overall speed of the database physical backup.
  • the CPU when there are multiple buffers in a busy state, the CPU can respectively compress the data pages in different buffers through multiple hardware acceleration devices, thereby improving the overall speed of the database physical backup.
  • the CPU writes the corresponding backup data packet into the backup data disk corresponding to the backup directory, and changes the state of the third buffer to an idle state.
  • the hardware acceleration device can notify the CPU that the compression of the third buffer is completed. After that, the CPU can compress the multiple data pages in the third buffer and write the corresponding backup data packets obtained into the backup data disk corresponding to the backup directory. In addition, the CPU can change the state of the third buffer to an idle state so that the data pages to be backed up can be rewritten.
  • buffer a In the process of database physical backup shown in Figures 8 and 9 above, data reading, verification and compression can be performed in parallel. For example, it is assumed that buffer a, buffer b and buffer c are included, and the initial states are all idle.
  • the CPU can read the unbacked up data pages from the original database directory and verify them, and then store the verified data pages in buffer a.
  • buffer a When buffer a is full, the state of buffer a can be changed to a busy state, and the hardware acceleration device can be notified to compress the data pages in buffer a. While the hardware acceleration device is compressing the data pages in buffer a, the CPU can continue to read the unbacked up data pages from the original database directory and verify them, and then store the verified data pages in buffer b.
  • buffer b When buffer b is full, the state of buffer b can be changed to a busy state, and the hardware acceleration device can be notified to compress the data pages in buffer b. In this way, after the hardware acceleration device has compressed the data pages in buffer a, it can continue to compress the data in buffer b without waiting, thereby improving the overall efficiency of database physical backup.
  • the time required to read the unbacked-up data pages from the original database directory to fill a buffer in an idle state may be different from the time required for the hardware acceleration device to compress a buffer in a busy state and for the CPU to write the corresponding backup data packet to the data disk corresponding to the backup directory (hereinafter referred to as T2). Therefore, in order to fully utilize the processing power of the hardware acceleration device included in the electronic device, in some cases, the electronic device can start multiple threads to read the unbacked-up data pages from the original database directory in parallel (such as multiple threads respectively read the unbacked-up data pages in different data files under the original database directory), and store the read unbacked-up data pages in the buffer in the idle state.
  • the number of started threads may be determined according to the first time, the second time, and the number of hardware acceleration devices (hereinafter referred to as M).
  • the number of threads opened can be Indicates rounding up.
  • the number of full buffers can be greater than the number of compressed buffers at the same time, or the number of full buffers can be equal to the number of compressed buffers (that is, the storage of buffers and the compression of buffers are balanced), so that the hardware acceleration device of the electronic device can be maximized, and the speed of physical backup of the database can be further improved.
  • the number of buffers is also required to support.
  • the number of buffers can be determined based on the number of threads and the number of hardware acceleration devices.
  • the number of buffers can be the number of threads + the number of hardware acceleration devices, that is, In this way, it can be ensured that the number of buffers is sufficient and the multiple threads opened have corresponding
  • the idle buffer can write the data page that has not been backed up, and it can also ensure that the hardware acceleration device included in the electronic device has a busy buffer for compression processing.
  • each buffer it can store the corresponding backup data packet obtained by the hardware acceleration device compressing the data in the buffer.
  • the data page to be backed up in a buffer and the backup data packet corresponding to the data page to be backed up can be stored in the same buffer.
  • T1 is 4 seconds, which means that the time required for a thread to read the unbacked data pages from the original database directory and fill a buffer in an idle state is 4 seconds, including the time for data page verification.
  • T2 is 2 seconds, which means that the time required for a hardware acceleration device to compress a buffer in a busy state and for the CPU to write the corresponding backup data to the data disk corresponding to the backup directory is 2 seconds.
  • the number of hardware acceleration devices is 2, namely hardware acceleration device 1 and hardware acceleration device 2. At this time, it can be calculated that the number of threads is 4/2*2, which is 4 threads, namely thread 1-thread 4.
  • the number of buffers can be 4+2, which is 6 buffers, namely buffer 1-buffer 6.
  • the 6 buffers can be empty. After that, threads 1-thread 4 can write unbacked data pages to buffers 1-buffer 4 in parallel. In 4 seconds, buffers 1-buffer 4 can be filled. Afterwards, between 4s and 6s, the hardware acceleration device 1 and the hardware acceleration device 2 can compress the buffer 1 and the buffer 2 respectively, and the CPU can write the corresponding backup data packet to the data disk corresponding to the backup directory, and at the same time, the thread 1 and the thread 2 can write the unbacked data pages to the buffer 5 and the buffer 6 respectively. At 6s, the hardware acceleration device 1 and the hardware acceleration device 2 can compress the data pages in the buffer 1 and the buffer 2 respectively.
  • the hardware acceleration device 1 and the hardware acceleration device 2 can compress the buffer 3 and the buffer 4 respectively, and the CPU can write the corresponding backup data packet to the data disk corresponding to the backup directory, and at the same time, the thread 1 and the thread 2 can continue to write the unbacked data pages to the buffer 5 and the buffer 6 respectively, and the thread 3 and the thread 4 can write the unbacked data pages to the buffer 1 and the buffer 2 respectively.
  • the hardware acceleration device 1 and the hardware acceleration device 2 can compress the data pages in the buffer 3 and the buffer 4 respectively, and the CPU can write the corresponding backup data packet to the data disk corresponding to the backup directory, and at the same time, the thread 1 and the thread 2 can fill the buffer 5 and the buffer 6 respectively.
  • hardware acceleration device 1 and hardware acceleration device 2 can compress buffer 5 and buffer 6 respectively, and the CPU can write the corresponding backup data packet to the data disk corresponding to the backup directory.
  • thread 3 and thread 4 can continue to write the unbacked up data pages to buffer 1 and buffer 2 respectively, and thread 1 and thread 2 can write the unbacked up data pages to buffer 3 and buffer 4 respectively.
  • hardware acceleration device 1 and hardware acceleration device 2 can compress the data pages in buffer 5 and buffer 6 respectively, and the CPU can write the corresponding backup data packet to the data disk corresponding to the backup directory.
  • thread 3 and thread 4 can fill buffer 1 and buffer 2 respectively.
  • threads 1-thread 4 can write data pages to four idle buffers in parallel, and hardware acceleration device 1 and hardware acceleration device 2 can compress two busy buffers in parallel.
  • hardware acceleration device 1 or the hardware acceleration device 2 has finished compressing a buffer in a busy state and the CPU has written the corresponding backup data packet into the data disk corresponding to the backup directory, there will always be a buffer in a busy state for it to continue the compression process, so that the processing resources of the hardware acceleration device 1 and the hardware acceleration device 2 can be fully utilized.
  • T1 is also related to the size of the buffer, the CPU load, etc.
  • T2 is also related to the size of the buffer, the load of the hardware acceleration device, the processing power of the hardware acceleration device itself, etc.
  • the size of the buffer and the processing power of the hardware acceleration device itself are determined, if the tasks other than database physical backup occupy more CPU resources, the CPU load may be greater, which will result in the CPU resources used for database physical backup being used more. The resources are reduced, which will cause the above T1 to increase accordingly.
  • T2 will also change accordingly. The more processing resources of the hardware acceleration device are occupied by other tasks, the greater the load of the hardware acceleration device can be, and accordingly, T2 can be larger.
  • the electronic device can dynamically adjust the number of threads and the number of buffers.
  • the electronic device can dynamically monitor or predict the size of T1 and T2, and then dynamically adjust the number of threads and buffers opened when T1 or T2 changes. For example, assuming that the number of hardware acceleration devices is 2, the current T1 is 4s, and T2 is 2s. At this time, the electronic device can open 4 threads for buffer storage, and can set 6 buffers. Afterwards, if the CPU load is high, T1 can become 2s, and T2 remains unchanged. At this time, the electronic device can determine that it is more appropriate to open 2 threads and 4 buffers. Therefore, the electronic device can close 2 threads and release the resources of 2 buffers. In this way, on the basis of ensuring the efficiency of database physical backup, the occupation of CPU resources and memory resources can be reduced.
  • the electronic device dynamically adjusts the number of threads and the number of buffers, which can keep the storage of the buffer and the compression of the buffer in a balanced state, that is, in the same time, the number of full buffers and the number of compressed buffers are almost equal.
  • the performance of the hardware acceleration device can be fully utilized, and the number of buffers and threads is more appropriate, which can avoid occupying too many CPU resources and too many memory resources.
  • FIG. 10 is a flow chart of another database physical backup method disclosed in an embodiment of the present application.
  • the backup method can be executed by a central processing unit (CPU) of an electronic device.
  • the electronic device may include a central processing unit, a memory, and a hardware acceleration device.
  • the memory may include a first buffer.
  • the processing flow may include but is not limited to the following steps:
  • the CPU reads the first data in the first data file and stores the first data in the first buffer.
  • the first data file is stored in a data disk corresponding to the original database directory, such as the master data disk.
  • the first data may be an unbacked up data page in the first data file.
  • the size of the first buffer may be N times the size of the data page, where N is an integer greater than or equal to 2.
  • the CPU may first open the first data file, and then, if the first buffer is not stored in or is not full of the first data, in this case, the first buffer can continue to store data, and at this time, the CPU may read the first data in the first data file, and store the read first data in the first buffer. It should be understood that the fact that the first buffer is not stored in or is not full of the first data can be understood as the first buffer being in an idle state, and reference may be made to the relevant description in the embodiment shown in FIG. 5 above.
  • the corresponding compressed data may also be stored in the first buffer, and then the compressed data stored in the first buffer may be written to the data disk corresponding to the backup directory. Afterwards, when the compressed data stored in the first buffer is successfully written to the data disk corresponding to the backup directory, the first buffer may be regarded as an empty buffer, that is, a buffer in which the first data is not stored.
  • the CPU before the CPU stores the read first data into the first buffer, it may verify the read first data, and then, if the first data verification succeeds, the CPU stores the first data page into the first buffer.
  • the CPU compresses the first data in the first buffer through a hardware acceleration device to generate backup data corresponding to the first data.
  • the CPU compresses the first data in the first buffer through the hardware acceleration device, so that the utilization rate of the buffer space can be guaranteed.
  • the CPU can read the remaining data from the first data file, that is, read the remaining unread data pages or data pages to be backed up in the first data file, and store the remaining read data in the second buffer.
  • the second buffer can be any other buffer in the multiple first buffers that does not store or is not full of the first data.
  • the CPU can continue to read the remaining data from the first data file and store the remaining data in another first buffer, which can ensure that the CPU writes data to the buffer in parallel with the hardware acceleration device compressing the data, thereby improving the efficiency of data backup.
  • the first data can be read from multiple data files in the original database directory by multiple threads, and the first data in different data files can be stored in multiple buffers that are not stored in or are not full of the first data; when the third buffer is full, the data in the third buffer is compressed by a hardware acceleration device.
  • the third buffer can be any full buffer among the multiple first buffers.
  • first data in the above-mentioned multiple data files may be different data.
  • the CPU may process and compress the data in the multiple full buffers in parallel through multiple hardware acceleration devices.
  • the number of threads opened and the number of buffers can be determined according to the first time, the second time, and the number of hardware acceleration devices included in the electronic device.
  • the first time can be the time required to read the first data from the original database directory to fill a first buffer
  • the second time is the time required for a hardware acceleration device to complete the compression of a full first buffer and for the CPU to write the corresponding backup data into the data disk corresponding to the backup directory.
  • the hardware acceleration device of the electronic device is disposed in a processor of the electronic device, that is, the hardware acceleration device of the electronic device and the processor of the electronic device may be integrated together.
  • the CPU can dynamically adjust the number of threads and/or the number of buffers according to the first time, the second time, and the number of hardware acceleration devices included in the electronic device.
  • the CPU writes the corresponding backup data into the data disk corresponding to the backup directory.
  • the execution subject in the above steps 501-507, 601-606, 701-702, 801-806, 901-902, 1001-1003 may be other controllers or processing chips in the electronic device, such as CPLD, FPGA and other controllers, in addition to the central processing unit CPU in the electronic device.
  • FIG5, FIG6, FIG7, FIG8, FIG9 and FIG10 take the CPU as the execution subject of the interactive diagram as an example to illustrate the above-mentioned processing flow, but the present application does not limit the execution subject of the interactive diagram.
  • the CPU in Figures 6, 7, 8, 9 and 10 can also be a chip, chip system, electronic device, etc. that supports the CPU to implement the method, or it can be a logic module or software (such as the above-mentioned backup tool) that can implement all or part of the CPU functions.
  • the present application also discloses an electronic device, which includes a memory and a processor, wherein the memory is used to store a computer program or computer instruction of the electronic device, and the processor can be used to read the program or computer instruction stored in the memory and execute the method in the above method embodiment.
  • the above memory may include but is not limited to a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM) or a portable read-only memory (CD-ROM).
  • the above processor may be a CPU, a complex programmable logic device, a general processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component or any combination thereof.
  • the processor may also be a combination that realizes a computing function, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and the like.
  • the embodiment of the present application also discloses a computer-readable storage medium having instructions stored thereon, and when the instructions are executed, the method in the above method embodiment is executed.
  • the embodiment of the present application also discloses a computer program product including instructions, which, when executed, execute the method in the above method embodiment.
  • a unit can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, or a combination of hardware and software. and/or distributed between two or more computers.
  • these units can be executed from various computer-readable media having various data structures stored thereon.
  • the units can communicate through local and/or remote processes, for example, based on signals having one or more data packets (e.g., data from a second unit interacting with another unit in a local system, a distributed system, and/or a network.
  • data packets e.g., data from a second unit interacting with another unit in a local system, a distributed system, and/or a network.
  • the Internet interacts with other systems via signals).

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Sont divulgués dans les modes de réalisation de la présente demande un procédé de sauvegarde de données, un dispositif électronique, et un support de stockage lisible par ordinateur. Le procédé est appliqué à un dispositif électronique, qui comprend une unité centrale de traitement, une mémoire et un dispositif matériel d'accélération, la mémoire comprenant une première zone tampon. Le procédé consiste plus particulièrement : à lire des premières données provenant d'un premier fichier de données, et à stocker les premières données lues dans une première zone tampon, le premier fichier de données étant stocké dans un disque de données correspondant à un répertoire de base de données d'origine ; à compresser les premières données dans la première zone tampon au moyen du dispositif matériel d'accélération, de façon à générer des données de sauvegarde correspondant aux premières données ; et à écrire les données de sauvegarde dans un disque de données correspondant à un répertoire de sauvegarde. Les modes de réalisation de la présente demande peuvent améliorer l'efficacité de sauvegarde de données.
PCT/CN2023/133236 2023-06-19 2023-11-22 Procédé de sauvegarde de données, dispositif électronique, et support d'enregistrement lisible par ordinateur Ceased WO2024259890A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310729914.0 2023-06-19
CN202310729914.0A CN116954996A (zh) 2023-06-19 2023-06-19 数据备份方法、电子设备及计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2024259890A1 true WO2024259890A1 (fr) 2024-12-26

Family

ID=88445318

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/133236 Ceased WO2024259890A1 (fr) 2023-06-19 2023-11-22 Procédé de sauvegarde de données, dispositif électronique, et support d'enregistrement lisible par ordinateur

Country Status (2)

Country Link
CN (1) CN116954996A (fr)
WO (1) WO2024259890A1 (fr)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116954996A (zh) * 2023-06-19 2023-10-27 超聚变数字技术有限公司 数据备份方法、电子设备及计算机可读存储介质
CN118051378A (zh) * 2024-01-12 2024-05-17 中建材信息技术股份有限公司 一种基于日志的数据库增量备份方法
CN120276940B (zh) * 2025-06-06 2026-02-24 宁德时代润智软件科技有限公司 负载监控方法、装置、嵌入式设备、计算机设备和介质
CN121523970A (zh) * 2025-10-31 2026-02-13 北京中金国信科技有限公司 Pci-e密码卡密钥备份和恢复方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8566286B1 (en) * 2009-05-15 2013-10-22 Idera, Inc. System and method for high speed database backup using rapidly adjusted dynamic compression ratios controlled by a feedback loop
US20210109759A1 (en) * 2019-10-15 2021-04-15 EMC IP Holding Company LLC Pipelined method to improve backup and restore performance
CN116954996A (zh) * 2023-06-19 2023-10-27 超聚变数字技术有限公司 数据备份方法、电子设备及计算机可读存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8566286B1 (en) * 2009-05-15 2013-10-22 Idera, Inc. System and method for high speed database backup using rapidly adjusted dynamic compression ratios controlled by a feedback loop
US20210109759A1 (en) * 2019-10-15 2021-04-15 EMC IP Holding Company LLC Pipelined method to improve backup and restore performance
CN116954996A (zh) * 2023-06-19 2023-10-27 超聚变数字技术有限公司 数据备份方法、电子设备及计算机可读存储介质

Also Published As

Publication number Publication date
CN116954996A (zh) 2023-10-27

Similar Documents

Publication Publication Date Title
WO2024259890A1 (fr) Procédé de sauvegarde de données, dispositif électronique, et support d'enregistrement lisible par ordinateur
US20230185747A1 (en) Presentation of direct accessed storage under a logical drive model
US10877940B2 (en) Data storage with a distributed virtual array
CN103729442B (zh) 记录事务日志的方法和数据库引擎
US8856472B2 (en) Restore in cascaded copy environment
US20120079175A1 (en) Apparatus, system, and method for data transformations within a data storage device
CN115098046B (zh) 磁盘阵列初始化方法、系统、电子设备及存储介质
US10387307B2 (en) Lock-free raid implementation in multi-queue architecture
US11210024B2 (en) Optimizing read-modify-write operations to a storage device by writing a copy of the write data to a shadow block
CN112579351A (zh) 一种云硬盘备份系统
CN118244972A (zh) 一种数据存储方法、装置及系统
WO2024212783A1 (fr) Procédé et appareil d'écriture de données, disque à semi-conducteurs, dispositif électronique et support de stockage lisible non volatil
CN117992283A (zh) 云主机备份方法、装置、计算机设备及存储介质
CN113849341B (zh) 一种nas快照的性能优化方法、系统、设备及可读存储介质
CN117666931A (zh) 一种数据处理方法及相关设备
US10185573B2 (en) Caching based operating system installation
CN111290836A (zh) 虚拟机快照创建方法、装置、存储介质及计算机设备
US10942663B2 (en) Inlining data in inodes
US20210132840A1 (en) Storage management system and method
WO2024212850A1 (fr) Procédé et appareil de sauvegarde de métadonnées, dispositif électronique et support de stockage
CN119003239A (zh) 数据处理方法、装置、计算机设备和存储介质
US10860221B1 (en) Page write to non-volatile data storage with failure recovery
WO2022028208A1 (fr) Réseau redondant de cartes à disques indépendants, procédé de traitement d'instructions, et dispositif et système de stockage
CN114675995A (zh) 数据备份方法、装置和电子设备
CN120315832A (zh) 数据处理方法、装置、计算机设备及存储介质

Legal Events

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

Ref document number: 23942156

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE