CN111913916A - File recombination method and equipment - Google Patents
File recombination method and equipment Download PDFInfo
- Publication number
- CN111913916A CN111913916A CN202010647779.1A CN202010647779A CN111913916A CN 111913916 A CN111913916 A CN 111913916A CN 202010647779 A CN202010647779 A CN 202010647779A CN 111913916 A CN111913916 A CN 111913916A
- Authority
- CN
- China
- Prior art keywords
- file
- source file
- service data
- target
- updating
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/162—Delete operations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Human Computer Interaction (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method and a device for file reorganization, which are applied to a service server, wherein the method comprises the following steps: responding to a file recombination instruction, acquiring a current source file to perform mirror image backup on the source file to obtain a static source file; acquiring a target file obtained after business data in the static source file are recombined, and a mapping file generated according to the positions of the business data in the static source file and the target file; responding to a file updating instruction, and acquiring an updating log for recording the change information of the current source file relative to the static source file; and correspondingly updating the service data in the target file according to the update log and the mapping file, and replacing the current source file with the updated target file when the update is determined to be completed. The method and the device for file reorganization provided by the invention solve the problems that the existing file reorganization method needs a long halt execution window and has low file reorganization efficiency.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and equipment for file reorganization.
Background
At present, in order to improve the service quality of services, the core servers of some service systems need to provide services to the outside continuously, so that the down-time maintenance time windows of the core servers are less and less. However, due to some condition limitations of the operating system and the application program of the server, maintenance operation needs to be performed on the database file of the server periodically.
At present, the upper limit of the records of partial physical files specified by an application program is 10 hundred million, the upper limit of the records of the physical files specified by an operating system is 42 hundred million, and the database files which are about to reach the upper limit need to be filed, namely, the data meeting certain conditions are transferred to other database files. A large amount of deleted data spaces can be formed in the archiving process, and the deleted data spaces cannot be automatically released, so that the deleted data spaces are released by performing recombination operation after the archiving is finished, and the data storage space is reasonably utilized. In addition, some businesses frequently write and delete database files, and also form a large amount of deleted data space for physical files, and also need to perform reassembly operations.
The method has the advantages that the method can improve the file access efficiency, shorten the data response time, avoid the hard limit of application software and an operating system, and reduce the risk of system operation and maintenance by recombining the super-large data files. The currently adopted management method of RGZPFM (reorganization Physical File Member) can realize the reorganization of database files. The method can automatically release all deleted data spaces and rearrange data, thereby effectively reducing the storage utilization rate, improving the data access efficiency and having higher stability and reliability. However, when a physical file with a large data volume, for example, a physical file with a data record number of approximately 10 hundred million and a total capacity of approximately 700GB, is rebuilt, an actual time for the rebuilding generally exceeds 2 hours, so that the efficiency of the file rebuilding is very low, and a long shutdown maintenance window needs to be applied, which may cause stress on operation and maintenance. In addition, once submitted, the file reorganization command in the RGZPFM method is handed to the operating system to complete all actions, so the transparency of the overall process and progress of file reorganization is low.
At present, the files to be recombined can be moved into the memory before the files are recombined, so that the data reading time in the recombination process is reduced, but the system memory capacity in the real environment is limited, and the capacity of some physical files can far exceed the size of the actual memory of the system, so that the method can have great influence on the performance of the system.
In summary, the existing method for file reorganization has a problem that a longer shutdown window is needed to execute the reorganization method, which results in low file reorganization efficiency, and therefore, a file reorganization method that more effectively shortens the shutdown reorganization time and improves the reorganization efficiency is needed to be provided.
Disclosure of Invention
The invention provides a method and equipment for file reorganization, which are used for solving the problems that the existing file reorganization method needs a long halt execution window and has low file reorganization efficiency.
According to a first aspect of the embodiments of the present invention, a method for reorganizing a file is provided, which is applied to a service server, and the method includes:
responding to a file recombination instruction, acquiring a current source file to perform mirror image backup on the source file to obtain a static source file;
acquiring a target file obtained after business data in the static source file are recombined, and a mapping file generated according to the positions of the business data in the static source file and the target file;
responding to a file updating instruction, and acquiring an updating log for recording the change information of the current source file relative to the static source file;
and correspondingly updating the service data in the target file according to the update log and the mapping file, and replacing the current source file with the updated target file when the update is determined to be completed.
Optionally, obtaining a current source file to perform mirror backup on the source file to obtain a static source file, including:
acquiring a current source file, and carrying out mirror image backup on the source file locally to obtain a static source file;
before the target file and the mapping file are obtained, the method further comprises the following steps:
and reconstructing the service data in the static source file to obtain a target file, and generating a mapping file according to the positions of the service data in the static source file and the target file.
Optionally, obtaining a current source file to perform mirror backup on the source file to obtain a static source file, including:
acquiring a current source file and sending the current source file to a backup server, and carrying out mirror image backup on the source file by the backup server to obtain a static source file;
acquiring the target file and the mapping file, including:
and acquiring a target file sent by the backup server after the business data in the static source file are recombined, and a mapping file sent according to the positions of the business data in the static source file and the target file.
Optionally, the replacing the current source file with the updated target file includes:
and after the current source file is cached and backed up, replacing the current source file by using the updated target file, and deleting the cached source file after the replacement is finished.
Optionally, the reconstructing the service data in the static source file to obtain a target file, and generating a mapping file according to the positions of the service data in the static source file and the target file includes:
establishing a target file with the same name and structure attribute as the static source file;
and reading the service data in the static source file one by one, copying the service data to the target file when the currently read service data is determined to be non-empty recorded service data, and writing the data record number of the service data in the static source file and the corresponding data record number in the target file into a corresponding mapping file.
Optionally, the correspondingly updating the service data in the target file according to the update log and the mapping file includes:
determining the data content updated by the service data updating operation and the data position of the service data updating operation in the current source file according to the updating log;
and determining the data position of the service data updating operation in the target file according to the mapping file, and executing the service data updating operation according to the data content.
Optionally, determining that the update is completed includes:
determining that the number of the non-empty recorded service data in the target file is the same as that of the non-empty recorded service data in the source file, and determining that the updating is completed; or
Determining that the latest time information corresponding to the service data in the target file and the source file is the same, and determining that updating is completed; or
And when the target file is determined to be consistent with the service data content in the source file, determining to finish updating.
According to a second aspect of the embodiments of the present invention, there is provided an apparatus for reorganizing a file, including:
the file acquisition module is used for responding to a file recombination instruction and acquiring a current source file so as to carry out mirror image backup on the source file to obtain a static source file;
the file recombination module is used for acquiring a target file obtained by recombining the service data in the static source file and a mapping file generated according to the positions of the service data in the static source file and the target file;
the log obtaining module is used for responding to a file updating instruction and obtaining an updating log for recording the change information of the current source file relative to the static source file;
and the file updating module is used for correspondingly updating the service data in the target file according to the updating log and the mapping file, and replacing the current source file with the updated target file when the updating is determined to be completed.
Optionally, the obtaining a current source file by the file obtaining module to perform mirror image backup on the source file to obtain a static source file includes:
acquiring a current source file, and carrying out mirror image backup on the source file locally to obtain a static source file;
before the file reorganization module obtains the target file and the mapping file, the file reorganization module is further configured to:
and reconstructing the service data in the static source file to obtain a target file, and generating a mapping file according to the positions of the service data in the static source file and the target file.
Optionally, the obtaining a current source file by the file obtaining module to perform mirror image backup on the source file to obtain a static source file includes:
acquiring a current source file and sending the current source file to a backup server, and carrying out mirror image backup on the source file by the backup server to obtain a static source file;
the file reorganization module obtains the target file and the mapping file, and comprises the following steps:
and acquiring a target file sent by the backup server after the business data in the static source file are recombined, and a mapping file sent according to the positions of the business data in the static source file and the target file.
Optionally, the file updating module replaces the current source file with the updated target file, including:
and after the current source file is cached and backed up, replacing the current source file by using the updated target file, and deleting the cached source file after the replacement is finished.
Optionally, the file restructuring module restructures the service data in the static source file to obtain a target file, and generates a mapping file according to the position of the service data in the static source file and the target file, including:
establishing a target file with the same name and structure attribute as the static source file;
and reading the service data in the static source file one by one, copying the service data to the target file when the currently read service data is determined to be non-empty recorded service data, and writing the data record number of the service data in the static source file and the corresponding data record number in the target file into a corresponding mapping file.
Optionally, the file updating module performs corresponding updating on the service data in the target file according to the update log and the mapping file, and includes:
determining the data content updated by the service data updating operation and the data position of the service data updating operation in the current source file according to the updating log;
and determining the data position of the service data updating operation in the target file according to the mapping file, and executing the service data updating operation according to the data content.
Optionally, the determining, by the file update module, that the update is completed includes:
determining that the number of the non-empty recorded service data in the target file is the same as that of the non-empty recorded service data in the source file, and determining that the updating is completed; or
Determining that the latest time information corresponding to the service data in the target file and the source file is the same, and determining that updating is completed; or
And when the target file is determined to be consistent with the service data content in the source file, determining to finish updating.
According to a third aspect of the embodiments of the present invention, there is provided an apparatus for file reorganization, including: a memory and a processor; wherein:
the memory is used for storing programs;
the processor is used for executing the program in the memory and comprises the following steps:
responding to a file recombination instruction, acquiring a current source file to perform mirror image backup on the source file to obtain a static source file;
acquiring a target file obtained after business data in the static source file are recombined, and a mapping file generated according to the positions of the business data in the static source file and the target file;
responding to a file updating instruction, and acquiring an updating log for recording the change information of the current source file relative to the static source file;
and correspondingly updating the service data in the target file according to the update log and the mapping file, and replacing the current source file with the updated target file when the update is determined to be completed.
Optionally, the obtaining, by the processor, a current source file to perform mirror backup on the source file to obtain a static source file includes:
acquiring a current source file, and carrying out mirror image backup on the source file locally to obtain a static source file;
before the processor acquires the target file and the mapping file, the processor is further configured to:
and reconstructing the service data in the static source file to obtain a target file, and generating a mapping file according to the positions of the service data in the static source file and the target file.
Optionally, the obtaining, by the processor, a current source file to perform mirror backup on the source file to obtain a static source file includes:
acquiring a current source file and sending the current source file to a backup server, and carrying out mirror image backup on the source file by the backup server to obtain a static source file;
the processor obtaining the target file and the mapping file comprises:
and acquiring a target file sent by the backup server after the business data in the static source file are recombined, and a mapping file sent according to the positions of the business data in the static source file and the target file.
Optionally, the processor replaces the current source file with the updated target file, including:
and after the current source file is cached and backed up, replacing the current source file by using the updated target file, and deleting the cached source file after the replacement is finished.
Optionally, the reconstructing the service data in the static source file by the processor to obtain a target file, and generating a mapping file according to the positions of the service data in the static source file and the target file includes:
establishing a target file with the same name and structure attribute as the static source file;
and reading the service data in the static source file one by one, copying the service data to the target file when the currently read service data is determined to be non-empty recorded service data, and writing the data record number of the service data in the static source file and the corresponding data record number in the target file into a corresponding mapping file.
Optionally, the processor correspondingly updates the service data in the target file according to the update log and the mapping file, including:
determining the data content updated by the service data updating operation and the data position of the service data updating operation in the current source file according to the updating log;
and determining the data position of the service data updating operation in the target file according to the mapping file, and executing the service data updating operation according to the data content.
Optionally, the processor determining that the update is completed includes:
determining that the number of the non-empty recorded service data in the target file is the same as that of the non-empty recorded service data in the source file, and determining that the updating is completed; or
Determining that the latest time information corresponding to the service data in the target file and the source file is the same, and determining that updating is completed; or
And when the target file is determined to be consistent with the service data content in the source file, determining to finish updating.
According to a fourth aspect of the embodiments of the present invention, there is provided a chip, the chip is coupled to a memory in a device, so that the chip invokes, when running, program instructions stored in the memory, to implement the above aspects of the embodiments of the present application and any method that may be designed according to the aspects.
According to a fifth aspect of the embodiments of the present invention, there is provided a computer-readable storage medium storing program instructions which, when executed on a computer, cause the computer to perform the method of any of the possible designs to which the above aspects and aspects relate.
According to a sixth aspect of the embodiments of the present invention, there is provided a computer program product, which, when run on an electronic device, causes the electronic device to perform a method of implementing the above aspects of the embodiments of the present application and any possible design related to the aspects.
The method and the equipment for recombining the files have the following beneficial effects that:
the method and the device for recombining the files provided by the invention have the advantages that the corresponding static source file is obtained by carrying out mirror image backup on the current source file, then the static source file is recombined to obtain the target file, when the files are updated, the business data in the target file are correspondingly updated according to the update log for recording the change information of the current source file relative to the static source file and the mapping file for reflecting the positions of the business data in the static source file and the target file, and after the update is finished, the current source file is replaced by the target file, so that the recombination of the current source file can be realized without influencing the business operation of the current source file. The method solves the problems that the existing file reorganization method needs to stop the execution window for a long time and has low file reorganization efficiency.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic diagram of a method for reorganizing a file according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a method for generating a target file and a mapping file according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a method for updating a target file according to an embodiment of the present invention;
FIG. 4 is a diagram illustrating a method for updating a source file according to an embodiment of the present invention;
FIG. 5 is a flowchart illustrating a method for reorganizing files according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of an apparatus for reorganizing a file according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a file reorganization device provided in an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
For convenience of understanding, terms referred to in the embodiments of the present invention are explained below:
snapshot: is a fully available copy of a given data set, the copy comprising an image of the corresponding data at some point in time (the point in time at which the copy began); the snapshot may be a copy of the data it represents or a copy of the data.
Example 1
The embodiment of the invention provides a file reorganization method which is applied to a service server. As shown in fig. 1, the method includes:
step S101, responding to a file recombination instruction, acquiring a current source file to perform mirror image backup on the source file to obtain a static source file;
the method provided by the embodiment of the invention is applied to a scene that a business server providing business service for a user recombines physical files, wherein the physical files are files actually storing business data, namely files specifically corresponding to storage media such as a magnetic disk. In the process of providing business services by the business server, generation, deletion, modification and the like of various business data are all carried out in a physical file. Therefore, there may be a record of empty service data in the physical file, and the service data originally stored in the storage space corresponding to the record of the empty service data is archived or deleted, so that the service data does not actually exist in the physical file and becomes empty service data, but the storage space corresponding to the record of the empty service data is not deleted, so that the physical file needs to be reorganized, the record of the empty service data therein is deleted, and the corresponding storage space is released.
In the embodiment of the invention, when the file recombination is carried out, the service server responds to the file recombination instruction to obtain the current source file. The file reorganization instruction is a file reorganization instruction input by a user and received through a user interface. When the current source file is the source file to be recombined at the moment obtained when the business server receives the file recombination instruction, the business data in the source file can be changed with the operation of the business data subsequently.
After the business server acquires the current source file, the acquired source file is subjected to mirror image backup by adopting any one of the following modes to obtain a static source file:
mode 1
And the service server locally performs mirror image backup on the source file to obtain a static source file.
Specifically, after the service server acquires the current source file, the service server performs mirror image backup on the source file to obtain a static source file, and the service data in the static source file is the service data in the source file to be recombined at that moment and cannot be changed later. The mirror backup results in a complete copy of the file.
As an optional implementation manner, the service server obtains a static source file corresponding to a current source file through a snapshot. The current source file can be copied through the snapshot to obtain a static source file which has the same content as the source file but is completely independent, and any operation on the static source file cannot influence the current source file.
Mode 2
The method comprises the steps that a business server acquires a current source file and sends the current source file to a backup server, and the backup server performs mirror image backup on the source file to obtain a static source file.
Specifically, after the service server acquires a current source file, the source file is sent to the backup server, and after the backup server receives the source file, the backup server performs mirror image backup on the source file to obtain a static source file and sends the static source file to the service server. The backup server is used for recombining the source file, so that the workload of recombining the source file by the service server is avoided, the influence on the service of the service server is reduced to the greatest extent, particularly, when the data volume in the source file is very large, the service server only executes the step of sending the source file, the source file is recombined and sent to the backup server, and the burden of the service server can be greatly reduced.
As an alternative embodiment, the backup server obtains a static source file corresponding to the current source file through a snapshot.
When the backup server obtains the static source file, the same method as the method 1 is adopted, and the description is not repeated here.
In the embodiment of the invention, the functions of the service server and the backup server can be respectively realized on different hardware devices, and can also be integrated on one hardware device. When the functions of the backup server are integrated into one hardware device, the service server may complete a complete file reorganization process in this embodiment, or the service server and the backup server may be respectively used as two independent partitions on the same hardware device without affecting each other, and the service server and the backup server may respectively complete their functions.
Step S102, obtaining a target file obtained by recombining the service data in the static source file and a mapping file generated according to the positions of the service data in the static source file and the target file;
in the embodiment of the present invention, when the service server performs mirror image backup on the acquired source file to obtain the static source file in the manner 1, the service server recombines the service data in the static source file to obtain the target file, and generates the mapping file according to the positions of the service data in the static source file and the target file.
In the embodiment of the present invention, when the service server performs mirror image backup on the acquired source file to obtain the static source file in the manner 2, the backup server recombines the service data in the static source file to obtain the target file, generates the mapping file according to the positions of the service data in the static source file and the target file, and sends the obtained target file and the mapping file to the service server. Therefore, what the service server obtains is the target file sent by the backup server after recombining the service data in the static source file, and the mapping file sent according to the positions of the service data in the static source file and the target file.
The service server and the backup server adopt the same method to obtain a target file after recombining the service data in the static source file, and generate a mapping file according to the positions of the service data in the static source file and the target file. The details will be described below.
Establishing a target file with the same name and structure attribute as the static source file; and reading the service data in the static source file one by one, copying the service data to the target file when the currently read service data is determined to be non-empty recorded service data, and writing the data record number of the service data in the static source file and the corresponding data record number in the target file into a corresponding mapping file.
Referring to fig. 2, a schematic diagram of a method for generating a target file and a mapping file according to an embodiment of the present invention is provided. As shown in the figure, assuming that the storage location of the static source file is a source LIB (Library ), when obtaining the target file and the corresponding mapping file according to the static source file, the following steps are adopted:
step 1, establishing a new LIB for storing a target file;
step 2, establishing a target file with the same name and structure attribute as the static source file in the new LIB by copying, wherein the target file does not contain any service data and is an empty file;
step 3, establishing a mapping file containing two fields in the new LIB, wherein the two fields respectively represent a data record number of the service data in the static source file and a corresponding data record number in the target file, and the data record number can be a row number RRN;
step 4, reading the service data in the static source file one by one, directly skipping null recording, writing the service data into a target file for non-null recording, simultaneously acquiring the data record number of the service data in the static source file and the corresponding data record number in the target file, and writing the service data into a mapping file;
and 5, after all the business data recorded in the static source file in a non-empty mode are written into the target file, correspondingly updating the logic file and the index of the static source file according to the position of the business data in the target file, and then associating the logic file and the index with the target file, wherein the logic file and the index are used for determining the position information of the business data in the static source file, such as a data recording number and the like.
After obtaining the target File and the mapping File corresponding to the static source File according to the above steps, the backup server sends the target File and the mapping File to the service server, and then sends the created new LIB for storing the target File and the mapping File to the service server in the form of an auxiliary storage medium such as a tape or a Save File.
Step S103, responding to a file updating instruction, and acquiring an updating log for recording the change information of the current source file relative to the static source file;
in the embodiment of the present invention, when the service server or the backup server obtains the target file and the corresponding mapping file according to the static source file, a certain operation time is required, so that a certain time interval exists between the time when the service server receives the file reorganization instruction and the time when the service server receives the file update instruction, and in the time interval, the service data in the static source file does not change, and the source file to be reorganized in the service server may change along with the operation on the service data.
In the embodiment of the invention, the file updating instruction is a file updating instruction received by the service server through a user interface, or a file updating instruction triggered after the service server obtains the target file and the mapping file, or a file updating instruction triggered after the service server receives the target file and the mapping file sent by the backup server.
The service server responds to the file updating instruction, acquires a current source file, and acquires the source file to be recombined at the moment when the service server receives the file updating instruction, wherein the change condition of the source file can be determined according to the related log file of the service server relative to the source file to be recombined acquired when the service server receives the file recombining instruction.
Therefore, when the service server receives the file updating instruction, the service server acquires an updating log for recording the change information of the current source file relative to the static source file, and determines the change condition of the current source file relative to the static source file according to the updating log. If the current source file is unchanged relative to the static source file, the file may not be updated.
The static source file and the source file to be recombined at the moment are the same as each other, and therefore, the current source file recorded in the service server when the file update instruction is received is an update log of the change information of the current source file relative to the static source file when the file update instruction is received.
And step S104, correspondingly updating the service data in the target file according to the update log and the mapping file, and replacing the current source file with the updated target file when the update is determined to be completed.
After the service server acquires the update log, determining the data content updated by the service data update operation and the data position of the service data update operation in the current source file according to the update log; and then determining the data position of the service data updating operation in the target file according to the mapping file, and executing the service data updating operation according to the data content. The service data updating operation comprises any one or any combination of the following operations:
writing new service data operation of new data in a source file;
deleting the service data in the source file;
and modifying the business data in the source file.
Fig. 3 is a schematic diagram of a method for updating a target file according to an embodiment of the present invention. As shown in the figure, assuming that the storage location of the current source file to be recombined in the service server is the source LIB, when the service server updates the obtained target file according to the source file, the update log and the mapping file, the following steps are adopted:
step 1, acquiring an update log, and reading service data update operation and updated data content in the update log one by one from a set point;
the set point is a log data point in the updated log corresponding to the moment when the service server receives the file reorganization instruction, and the log data after the log data point is the log data from the moment when the service server receives the file reorganization instruction to the current moment.
Step 2, when determining that the service data updating operation and the updated data content corresponding to the current source file are read, determining the data position of the service data updating operation in the current source file and the data record number of the operated service data in the source file according to the log data;
step 3, according to the data record number of the operated service data in the source file, and according to the corresponding relation of the data record number recorded in the mapping file, determining the data record number corresponding to the service data in the target file, and obtaining the data position of the service data updating operation in the target file;
and 4, performing the same updating operation on the service data in the target file according to the updating operation on the service data in the current source file.
When new data is written in the source file, the service data updating operation in the source file is to correspondingly write the new data in the target file and write the data record number of the new data in the current source file and the target file in the mapping file; when the service data in the source file is updated to delete the service data in the source file, deleting the corresponding service data in the target file; and the service data updating operation in the source file is to modify the service data in the source file, and the corresponding service data in the target file is modified in the same way.
In the embodiment of the present invention, when the service server determines that the update is completed, the current source file is cached and backed up, the current source file is replaced by the updated target file, and the cached source file is deleted after the replacement is completed. Wherein, whether the updating is completed is determined by any one of the following modes:
1) determining that the number of the non-empty recorded service data in the target file is the same as that of the non-empty recorded service data in the source file, and determining that the updating is completed;
2) determining that the latest time information corresponding to the service data in the target file and the source file is the same, and determining that updating is completed;
3) and when the target file is determined to be consistent with the service data content in the source file, determining to finish updating.
The target file and the service data in the source file have the same content, and the same data processing method may be adopted to respectively perform the same data processing on the specific service data in the target file and the specific service data in the source file, so that the obtained results are the same. For example, if one type of data of the service data is premium data in a policy corresponding to the same user in the insurance service, the premium data recorded in the current source file and the target file may be summed respectively, and when the summation result is determined to be consistent, the target file is considered to be consistent with the content of the service data in the source file, and it is determined that the update is completed, otherwise, it is determined that the update is not completed.
Fig. 4 is a schematic diagram of a method for updating a source file according to an embodiment of the present invention. As shown in the figure, assuming that the storage location of the current source file is a source LIB, the storage location of the obtained target file is a new LIB, when the service server determines that the update of the target file is completed, that is, when the log data in the update log is read to the current time, and the service data has no update time window, it is determined that the source file is updated, the current source file (including the logic file and the index) is first moved to the corresponding backup LIB, and then the target file (including the logic file and the index) is moved to the source LIB as the current source file. And the service server completes file reorganization to obtain a source file which does not include empty records after reorganization.
The method for reconstructing the file provided by the embodiment of the invention obtains the corresponding static source file by performing mirror image backup on the current source file, then performs file reconstruction on the static source file to obtain the target file, performs corresponding update on the target file according to the current source file at the corresponding moment after the static source file is reconstructed relative to the change condition of the static source file when the file is updated, and replaces the current source file by using the target file after the update is completed, so that the reconstruction of the current source file can be realized without affecting the business operation of the current source file. The method solves the problems that the existing file reorganization method needs to stop the execution window for a long time and has low file reorganization efficiency.
Example 2
Referring to fig. 5, a schematic flowchart of a method for performing file reassembly by a service server and a backup server according to an embodiment of the present invention is shown, where the method includes:
step S501, a service server responds to a file recombination instruction, and acquires a current source file to perform mirror image backup on the source file to obtain a static source file;
step S502, the business server sends the static source file to the backup server by a data migration method;
step S503, the backup server receives the static source file sent by the service server, recombines the service data in the static source file to obtain a target file, and generates a mapping file according to the positions of the service data in the static source file and the target file;
step S504, the backup server sends the target file and the mapping file to a service server;
step S505, the business server receives the target file and the mapping file sent by the backup server, responds to the file updating instruction, and acquires an updating log for recording the change information of the current source file relative to the static source file;
step S506, the service server correspondingly updates the service data in the target file according to the update log and the mapping file, and replaces the current source file with the updated target file when the update is determined to be completed.
The method comprises the steps of constructing a business service environment through a business server, providing business service for a user, constructing a backup environment of the business server through the backup service, recombining a source file in the backup server to obtain a target file, recording a data record number corresponding relation between the source file and business data in the target file in the recombining process, setting a log point according to update log data and file recombining related time points at the business server, updating the target file according to the update log, leveling data differences, finally performing file switching, replacing a current source file in the business server with the updated target file, compressing the file switching time to the shortest, and realizing online file recombining. The method solves the problems that the existing file reorganization method needs to stop the execution window for a long time and has low file reorganization efficiency.
For specific implementation of the above steps in this embodiment, reference may be made to the specific embodiment of the file reorganization method, and repeated details are not described again.
Example 3
A method of reorganizing a file according to the present invention is described above, and an apparatus for performing the method of reorganizing a file is described below.
Referring to fig. 6, an embodiment of the present invention provides a file reorganization apparatus, including:
the file obtaining module 601 is configured to, in response to a file reorganizing instruction, obtain a current source file to perform mirror image backup on the source file to obtain a static source file;
a file reorganization module 602, configured to obtain a target file obtained by reorganizing the service data in the static source file, and a mapping file generated according to positions of the service data in the static source file and the target file;
a log obtaining module 603, configured to, in response to a file update instruction, obtain an update log that records change information of a current source file relative to the static source file;
the file updating module 604 is configured to perform corresponding updating on the service data in the target file according to the update log and the mapping file, and replace the current source file with the updated target file when it is determined that the updating is completed.
Optionally, the obtaining a current source file by the file obtaining module to perform mirror image backup on the source file to obtain a static source file includes:
acquiring a current source file, and carrying out mirror image backup on the source file locally to obtain a static source file;
before the file reorganization module obtains the target file and the mapping file, the file reorganization module is further configured to:
and reconstructing the service data in the static source file to obtain a target file, and generating a mapping file according to the positions of the service data in the static source file and the target file.
Optionally, the obtaining a current source file by the file obtaining module to perform mirror image backup on the source file to obtain a static source file includes:
acquiring a current source file and sending the current source file to a backup server, and carrying out mirror image backup on the source file by the backup server to obtain a static source file;
the file reorganization module obtains the target file and the mapping file, and comprises the following steps:
and acquiring a target file sent by the backup server after the business data in the static source file are recombined, and a mapping file sent according to the positions of the business data in the static source file and the target file.
Optionally, the file updating module replaces the current source file with the updated target file, including:
and after the current source file is cached and backed up, replacing the current source file by using the updated target file, and deleting the cached source file after the replacement is finished.
Optionally, the file restructuring module restructures the service data in the static source file to obtain a target file, and generates a mapping file according to the position of the service data in the static source file and the target file, including:
establishing a target file with the same name and structure attribute as the static source file;
and reading the service data in the static source file one by one, copying the service data to the target file when the currently read service data is determined to be non-empty recorded service data, and writing the data record number of the service data in the static source file and the corresponding data record number in the target file into a corresponding mapping file.
Optionally, the file updating module performs corresponding updating on the service data in the target file according to the update log and the mapping file, and includes:
determining the data content updated by the service data updating operation and the data position of the service data updating operation in the current source file according to the updating log;
and determining the data position of the service data updating operation in the target file according to the mapping file, and executing the service data updating operation according to the data content.
Optionally, the determining, by the file update module, that the update is completed includes:
determining that the number of the non-empty recorded service data in the target file is the same as that of the non-empty recorded service data in the source file, and determining that the updating is completed; or
Determining that the latest time information corresponding to the service data in the target file and the source file is the same, and determining that updating is completed; or
And when the target file is determined to be consistent with the service data content in the source file, determining to finish updating.
The above describes the apparatus for reorganizing files in the embodiment of the present application from the perspective of the modular functional entity, and the following describes the apparatus for reorganizing files in the embodiment of the present application from the perspective of hardware processing.
Example 4
Referring to fig. 7, another embodiment of the apparatus for reorganizing documents in the embodiment of the present application includes:
a processor 701, a memory 702, a transceiver 709, and a bus system 711;
the memory is used for storing programs;
the processor is used for executing the program in the memory and comprises the following steps:
responding to a file recombination instruction, acquiring a current source file to perform mirror image backup on the source file to obtain a static source file;
acquiring a target file obtained after business data in the static source file are recombined, and a mapping file generated according to the positions of the business data in the static source file and the target file;
responding to a file updating instruction, and acquiring an updating log for recording the change information of the current source file relative to the static source file;
and correspondingly updating the service data in the target file according to the update log and the mapping file, and replacing the current source file with the updated target file when the update is determined to be completed.
Fig. 7 is a schematic structural diagram of a device for reorganizing files according to an embodiment of the present invention, where the device 700 may have a relatively large difference due to different configurations or performances, and may include one or more processors (CPU) 701 (e.g., one or more processors) and a memory 702, and one or more storage media 703 (e.g., one or more mass storage devices) for storing applications 704 or data 706. Memory 702 and storage medium 703 may be, among other things, transient storage or persistent storage. The program stored in the storage medium 703 may include one or more modules (not shown), and each module may include a series of instructions operating on the information processing apparatus. Further, the processor 701 may be configured to communicate with the storage medium 703 to execute a series of instruction operations in the storage medium 703 on the device 700.
The apparatus 700 may also include one or more power supplies 710, one or more wired or wireless network interfaces 707, one or more input-output interfaces 708, and/or one or more operating systems 705, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc.
Optionally, the obtaining, by the processor, a current source file to perform mirror backup on the source file to obtain a static source file includes:
acquiring a current source file, and carrying out mirror image backup on the source file locally to obtain a static source file;
before the processor acquires the target file and the mapping file, the processor is further configured to:
and reconstructing the service data in the static source file to obtain a target file, and generating a mapping file according to the positions of the service data in the static source file and the target file.
Optionally, the obtaining, by the processor, a current source file to perform mirror backup on the source file to obtain a static source file includes:
acquiring a current source file and sending the current source file to a backup server, and carrying out mirror image backup on the source file by the backup server to obtain a static source file;
the processor obtaining the target file and the mapping file comprises:
and acquiring a target file sent by the backup server after the business data in the static source file are recombined, and a mapping file sent according to the positions of the business data in the static source file and the target file.
Optionally, the processor replaces the current source file with the updated target file, including:
and after the current source file is cached and backed up, replacing the current source file by using the updated target file, and deleting the cached source file after the replacement is finished.
Optionally, the reconstructing the service data in the static source file by the processor to obtain a target file, and generating a mapping file according to the positions of the service data in the static source file and the target file includes:
establishing a target file with the same name and structure attribute as the static source file;
and reading the service data in the static source file one by one, copying the service data to the target file when the currently read service data is determined to be non-empty recorded service data, and writing the data record number of the service data in the static source file and the corresponding data record number in the target file into a corresponding mapping file.
Optionally, the processor correspondingly updates the service data in the target file according to the update log and the mapping file, including:
determining the data content updated by the service data updating operation and the data position of the service data updating operation in the current source file according to the updating log;
and determining the data position of the service data updating operation in the target file according to the mapping file, and executing the service data updating operation according to the data content.
Optionally, the processor determining that the update is completed includes:
determining that the number of the non-empty recorded service data in the target file is the same as that of the non-empty recorded service data in the source file, and determining that the updating is completed; or
Determining that the latest time information corresponding to the service data in the target file and the source file is the same, and determining that updating is completed; or
And when the target file is determined to be consistent with the service data content in the source file, determining to finish updating.
The embodiment of the present invention also provides a computer-readable storage medium, which includes instructions, when the computer-readable storage medium runs on a computer, the computer is caused to execute the method for reorganizing files provided in the above embodiment.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses and modules may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and in actual implementation, there may be other divisions, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may be stored in a computer readable storage medium.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.
The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
The technical solutions provided by the present application are introduced in detail, and the present application applies specific examples to explain the principles and embodiments of the present application, and the descriptions of the above examples are only used to help understand the method and the core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (10)
1. A method for reorganizing files is applied to a service server, and is characterized by comprising the following steps:
responding to a file recombination instruction, acquiring a current source file to perform mirror image backup on the source file to obtain a static source file;
acquiring a target file obtained after business data in the static source file are recombined, and a mapping file generated according to the positions of the business data in the static source file and the target file;
responding to a file updating instruction, and acquiring an updating log for recording the change information of the current source file relative to the static source file;
and correspondingly updating the service data in the target file according to the update log and the mapping file, and replacing the current source file with the updated target file when the update is determined to be completed.
2. The method of claim 1, wherein obtaining a current source file for mirror backup of the source file to obtain a static source file comprises:
acquiring a current source file, and carrying out mirror image backup on the source file locally to obtain a static source file;
before the target file and the mapping file are obtained, the method further comprises the following steps:
and reconstructing the service data in the static source file to obtain a target file, and generating a mapping file according to the positions of the service data in the static source file and the target file.
3. The method of claim 1, wherein obtaining a current source file for mirror backup of the source file to obtain a static source file comprises:
acquiring a current source file and sending the current source file to a backup server, and carrying out mirror image backup on the source file by the backup server to obtain a static source file;
acquiring the target file and the mapping file, including:
and acquiring a target file sent by the backup server after the business data in the static source file are recombined, and a mapping file sent according to the positions of the business data in the static source file and the target file.
4. The method of claim 1, wherein replacing the current source file with the updated target file comprises:
and after the current source file is cached and backed up, replacing the current source file by using the updated target file, and deleting the cached source file after the replacement is finished.
5. The method according to claim 2, wherein the reconstructing the service data in the static source file to obtain a destination file, and generating a mapping file according to the positions of the service data in the static source file and the destination file comprises:
establishing a target file with the same name and structure attribute as the static source file;
and reading the service data in the static source file one by one, copying the service data to the target file when the currently read service data is determined to be non-empty recorded service data, and writing the data record number of the service data in the static source file and the corresponding data record number in the target file into a corresponding mapping file.
6. The method according to claim 1, wherein said updating the service data in the target file according to the update log and the mapping file comprises:
determining the data content updated by the service data updating operation and the data position of the service data updating operation in the current source file according to the updating log;
and determining the data position of the service data updating operation in the target file according to the mapping file, and executing the service data updating operation according to the data content.
7. The method of claim 1, wherein determining that the update is complete comprises:
determining that the number of the non-empty recorded service data in the target file is the same as that of the non-empty recorded service data in the source file, and determining that the updating is completed; or
Determining that the latest time information corresponding to the service data in the target file and the source file is the same, and determining that updating is completed; or
And when the target file is determined to be consistent with the service data content in the source file, determining to finish updating.
8. An apparatus for reorganizing a file, comprising:
the file acquisition module is used for responding to a file recombination instruction and acquiring a current source file so as to carry out mirror image backup on the source file to obtain a static source file;
the file recombination module is used for acquiring a target file obtained by recombining the service data in the static source file and a mapping file generated according to the positions of the service data in the static source file and the target file;
the log obtaining module is used for responding to a file updating instruction and obtaining an updating log for recording the change information of the current source file relative to the static source file;
and the file updating module is used for correspondingly updating the service data in the target file according to the updating log and the mapping file, and replacing the current source file with the updated target file when the updating is determined to be completed.
9. An apparatus for reorganizing a file, comprising: a memory and a processor;
wherein the memory is used for storing programs;
the processor is used for executing the program in the memory and realizing the steps of the method according to any one of claims 1 to 7.
10. A computer program medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010647779.1A CN111913916A (en) | 2020-07-07 | 2020-07-07 | File recombination method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010647779.1A CN111913916A (en) | 2020-07-07 | 2020-07-07 | File recombination method and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111913916A true CN111913916A (en) | 2020-11-10 |
Family
ID=73227700
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010647779.1A Pending CN111913916A (en) | 2020-07-07 | 2020-07-07 | File recombination method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111913916A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114780820A (en) * | 2022-04-28 | 2022-07-22 | 广州高专资讯科技有限公司 | Open source platform-based target matching system and method |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5721915A (en) * | 1994-12-30 | 1998-02-24 | International Business Machines Corporation | Interaction between application of a log and maintenance of a table that maps record identifiers during online reorganization of a database |
| CN1555527A (en) * | 2001-04-09 | 2004-12-15 | System and method for reorganizing stored data | |
| JP2006011737A (en) * | 2004-06-24 | 2006-01-12 | Nec Corp | Database reorganization device and method, data processing apparatus, and program for the same |
| CN1784677A (en) * | 2004-03-31 | 2006-06-07 | 微软公司 | System and method for a consistency check of a database backup |
| US20060212496A1 (en) * | 1999-11-15 | 2006-09-21 | William Romine | System and method for quiescing select data modification operations against an object of a database during one or more structural operations |
| US7222133B1 (en) * | 2004-02-05 | 2007-05-22 | Unisys Corporation | Method for reducing database recovery time |
| CN105468686A (en) * | 2015-11-17 | 2016-04-06 | 北京奇虎科技有限公司 | Method and device for reducing redundant data |
| CN110456984A (en) * | 2019-06-21 | 2019-11-15 | 南京壹进制信息科技有限公司 | The method that the block device of a kind of pair of Ceph storage carries out continuous data protection |
-
2020
- 2020-07-07 CN CN202010647779.1A patent/CN111913916A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5721915A (en) * | 1994-12-30 | 1998-02-24 | International Business Machines Corporation | Interaction between application of a log and maintenance of a table that maps record identifiers during online reorganization of a database |
| US20060212496A1 (en) * | 1999-11-15 | 2006-09-21 | William Romine | System and method for quiescing select data modification operations against an object of a database during one or more structural operations |
| CN1555527A (en) * | 2001-04-09 | 2004-12-15 | System and method for reorganizing stored data | |
| US7222133B1 (en) * | 2004-02-05 | 2007-05-22 | Unisys Corporation | Method for reducing database recovery time |
| CN1784677A (en) * | 2004-03-31 | 2006-06-07 | 微软公司 | System and method for a consistency check of a database backup |
| JP2006011737A (en) * | 2004-06-24 | 2006-01-12 | Nec Corp | Database reorganization device and method, data processing apparatus, and program for the same |
| CN105468686A (en) * | 2015-11-17 | 2016-04-06 | 北京奇虎科技有限公司 | Method and device for reducing redundant data |
| CN110456984A (en) * | 2019-06-21 | 2019-11-15 | 南京壹进制信息科技有限公司 | The method that the block device of a kind of pair of Ceph storage carries out continuous data protection |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114780820A (en) * | 2022-04-28 | 2022-07-22 | 广州高专资讯科技有限公司 | Open source platform-based target matching system and method |
| CN114780820B (en) * | 2022-04-28 | 2022-11-01 | 广州高专资讯科技有限公司 | Open source platform-based target matching system and method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110531940B (en) | Video file processing method and device | |
| CN105468473B (en) | Data migration method and data migration device | |
| CN107003890B (en) | Efficiently providing virtual machine reference points | |
| CN102193807B (en) | Method for upgrading image file, server and computer network system | |
| US20060047926A1 (en) | Managing multiple snapshot copies of data | |
| US11093387B1 (en) | Garbage collection based on transmission object models | |
| CN108509462B (en) | Method and device for synchronizing activity transaction table | |
| US11977532B2 (en) | Log record identification using aggregated log indexes | |
| US10628298B1 (en) | Resumable garbage collection | |
| CN103780638A (en) | Data synchronization method and system | |
| US20040199521A1 (en) | Method, system, and program for managing groups of objects when there are different group types | |
| EP1637987A2 (en) | Operation environment associating data migration method | |
| CN108319623A (en) | A kind of fast resampling method, apparatus and data-base cluster | |
| CN108369588B (en) | Database level automatic storage management | |
| US11669405B2 (en) | Leveraging metadata to manage the expiration of objects storing incremental backup data | |
| US20230267103A1 (en) | Database Schema Branching Workflow, with Support for Data, Keyspaces and VSchemas | |
| US11144233B1 (en) | Efficiently managing point-in-time copies of data within a primary storage system | |
| US11809280B2 (en) | Synchronizing expirations for incremental backup data stored on a cloud-based object storage | |
| CN111913916A (en) | File recombination method and equipment | |
| CN115982101B (en) | Machine room data migration method and device based on multi-machine room copy placement strategy | |
| CN114253950B (en) | Method and device for managing database | |
| US11544156B1 (en) | Incremental restore for volumes using object-based snapshots | |
| CN113204520A (en) | Remote sensing data rapid concurrent read-write method based on distributed file system | |
| US11675668B2 (en) | Leveraging a cloud-based object storage to efficiently manage data from a failed backup operation | |
| CN114296649B (en) | Inter-cloud service migration system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |