Data destruction method and device

Abstract

The invention discloses a data destruction method and device, and relates to the technical field of data destruction. A data destruction task is sent to a target execution agent end; therefore, the target execution agent end can be instructed to destroy the data corresponding to the preset proportion according to the preset proportion, and whether destruction of the target logic storage unit is completed or not is further judged according to the data destruction progress of the destruction progress event. According to the method, event interaction between the control end and the execution agent end can be generated once after the target execution agent end destroys the data with the preset proportion, and compared with an original frequent interaction mode that interaction is performed once after each data block is destroyed, the event interaction amount of the control end and the execution agent end can be greatly reduced, and the interaction efficiency of the control end and the execution agent end is improved. The problem that core communication resources are occupied due to frequent interaction in the data destruction process is avoided, occupation of system communication resources is reduced, and normal operation of other functions of the system is guaranteed.

Description

Technical Field

[0001] This application relates to the technical field of data destruction, and particularly to a data destruction method and apparatus. Background Art

[0002] To securely and thoroughly destroy the data in a storage server has become a key link in ensuring security during the entire data life cycle management. Currently, when a centralized storage server performs data destruction, the logical storage unit (Logical Unit Number, LUN) is used as the basic destruction object. The LUN is divided into storage extents, and each extent is further refined into data sections with a unit of 256 KB; when performing destruction, the overwrite method is often used to overwrite each data section one by one to destroy the data of the entire LUN.

[0003] However, when the existing data destruction scheme is executed, the control end and the agent execution end will interact once after each data section is destroyed. Taking the destruction of a 100 GB capacity LUN once as an example, after each destruction of the data in a 256 KB section, the agent execution end needs to send an event to the control end to feedback the destruction situation to the control end, resulting in the event sending volume as high as 100 GB / 256 KB = 409,600 times; such a high-frequency event interaction will continuously occupy the system communication resources, and the functions of each module in the system rely on a unified communication mechanism. When the number of destroyed LUNs increases, the communication resources are over-consumed, which is extremely likely to cause the system performance to decline, resulting in operation jams or even risks of system crashes, seriously restricting the efficiency and stability of data destruction. Summary of the Invention

[0004] This application provides a data destruction method and apparatus to at least solve the problem of over-consumption of communication resources during data destruction in related technologies.

[0005] This application provides a data destruction method applied to the control end in a storage server, including: Receiving a destruction instruction for a target logical storage unit; In response to the destruction instruction, sending a data destruction task to a target execution agent; the data destruction task is used to instruct the target execution agent to destroy data with a preset proportion in the target logical storage unit; When receiving a destruction progress event sent by the target execution agent, determining whether all the data in the target logical storage unit has been completely destroyed; the destruction progress event is sent after the target execution agent completes the destruction of data with a preset proportion; If so, sending a destruction completion notice to the target execution agent; If not, repeat sending the data destruction task to the execution agent until all the data in the target logical storage unit is completely destroyed.

[0006] This application provides another data destruction method, which is applied to the target execution agent in a storage server and includes: Receiving a data destruction task sent by a control end; the data destruction task is used to destroy data with a preset proportion in the target logical storage unit; In response to the data destruction task, destroying the data in the target logical storage unit, and generating a destruction progress event when the destroyed data reaches the preset proportion; Sending the destruction progress event to the control end, so that when the control end receives the destruction progress event sent by the target execution agent, it can determine whether all the data in the target logical storage unit has been completely destroyed.

[0007] This application also provides a data destruction device, including: An instruction receiving module, configured to receive a destruction instruction for a target logical storage unit; A task sending module, configured to send a data destruction task to a target execution agent in response to the destruction instruction; the data destruction task is used to instruct the target execution agent to destroy data with a preset proportion in the target logical storage unit; A progress judgment module, configured to receive the destruction progress event sent by the target execution agent, and determine whether all the data in the target logical storage unit has been completely destroyed according to the data destruction progress carried by the destruction progress event; The task sending module is further configured to determine that the destruction of the target logical storage unit is completed when all the data in the target logical storage unit is completely destroyed, and send a destruction completion notice to the target execution agent; The task sending module is further configured to repeat sending the data destruction task to the execution agent when all the data in the target logical storage unit is not completely destroyed until all the data in the target logical storage unit is completely destroyed.

[0008] This application also provides another data destruction device, including: A task receiving module, configured to receive a data destruction task sent by a control end; the data destruction task is used to instruct to destroy data with a preset proportion in the target logical storage unit; A data destruction module, configured to destroy the data in the target logical storage unit in response to the data destruction task, and generate a destruction progress event when the destroyed data reaches the preset proportion; An event sending module, configured to send the destruction progress event to the control end, so that when the control end receives the destruction progress event sent by the target execution agent, it determines whether all the data of the target logical storage unit has been completely destroyed. The present application also provides an electronic device, including: a memory, configured to store a computer program; a processor, configured to implement the steps of any of the above data destruction methods when executing the computer program.

[0009] The present application also provides a computer-readable storage medium, in which a computer program is stored, and when the computer program is executed by a processor, the steps of any of the above data destruction methods are implemented.

[0010] The present application also provides a computer program product, including a computer program, and when the computer program is executed by a processor, the steps of any of the above data destruction methods are implemented.

[0011] In the present application, a data destruction task is sent to the target execution agent; further, the target execution agent can be instructed to destroy the corresponding data of a preset proportion according to the preset proportion size, and through the data destruction progress of the destruction progress event, it is further determined whether the destruction of the target logical storage unit is completed. Therefore, after the target execution agent destroys the data of the preset proportion size, an event interaction between the control end and the execution agent will be generated only once. Compared with the original frequent interaction mode in which an interaction occurs every time a 256KB data block is destroyed, the event interaction amount between the control end and the execution agent can be greatly reduced, avoiding the problem of occupying core communication resources due to frequent interaction during the data destruction process, reducing the system communication resource occupancy, and ensuring the normal operation of other functions of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] In order to more clearly illustrate the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application, and those of ordinary skill in the art can obtain other drawings based on these drawings without creative efforts.

[0013] Figure 1 It is one of the flow diagrams of a data destruction method provided by an embodiment of the present application; Figure 2 It is another flow diagram of a data destruction method provided by an embodiment of the present application; Figure 3 It is a third flow diagram of a data destruction method provided by an embodiment of the present application; Figure 4 It is a fourth flow diagram of a data destruction method provided by an embodiment of the present application; Figure 5Schematic diagram of the interaction process between the control end and the target execution agent end of a data destruction method provided by an embodiment of the present application; Figure 6 One of the structural schematic diagrams of a data destruction device provided by an embodiment of the present application; Figure 7 Another structural schematic diagram of a data destruction device provided by an embodiment of the present application. Detailed implementation manners

[0014] Next, the technical solutions in the embodiments of the present application will be clearly and completely described with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0015] It should be noted that in the description of the present application, the terms "include", "comprise" or any other variation thereof are intended to cover a non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. The terms "first", "second", etc. in the present application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0016] In order to enable those skilled in the art of the present technology to better understand the solution of the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific implementation manners.

[0017] Combined with the storage system architecture on which the execution of the data destruction method depends, the storage system architecture includes a control layer and an execution agent layer; when the storage system receives a user destruction instruction and generates a destruction instruction for the target logical storage unit according to the user destruction instruction, since each target logical storage unit is equipped with a corresponding control end, therefore, it is necessary to send the destruction instruction for the target logical storage unit to the corresponding control end in the control layer; then the control end parses the instruction to determine the target execution agent end for executing the subsequent data destruction task, and sends a data destruction task to the target execution agent end in the execution agent layer, instructing the target execution agent end to perform data destruction.

[0018] It should be noted that the control end can be a Control State Machine (CSM), which is the control center of the storage server and is used to manage the configuration and status information of each component in the system. In this application, it is used to control the execution of the data destruction process, receive the start stimulus sent by the destruction control state machine, and control the destruction progress of the logical storage unit. The execution agent end can be an Execution Agent State Machine (EAS), which is the execution module for data destruction in the storage server; it receives the data destruction task sent by the control end and organizes the data destruction process; during the interaction between the control end and the target execution agent end, when the control end needs the execution agent end to execute the data destruction task, it activates the Callgate, so that the execution agent end obtains the data destruction task by listening to the Callgate instruction channel and then executes the data destruction task; when the execution agent end feeds back the data progress or other interaction information to the control end, it feeds back the information to the control end through the Baseevent; furthermore, the control end obtains the information fed back by the execution agent end by listening to the Baseevent channel.

[0019] An embodiment of the present application provides a data destruction method. The method will be described in detail in combination with the execution process of the data destruction method. Refer to Figure 1 As shown, it is a schematic flowchart of the control end in the storage server provided by the present application. The specific steps are as follows: S101. Receive a destruction instruction for the target logical storage unit.

[0020] The data destruction method provided by the embodiment of the present application is centered around the target logical storage unit, and the control end and the execution agent end in the storage server cooperate with each other to complete the destruction operation of the target logical storage unit.

[0021] The destruction instruction for the target logical storage unit can be generated by the administrator of the storage system, the upper-layer service system or the compliance audit system and sent to the control end corresponding to the current target logical storage unit. After parsing the instruction, the control end sends a data destruction task to the target execution agent end to instruct the target execution agent end to destroy the data of a preset proportion size of the target logical storage unit according to the data destruction task.

[0022] Specifically, on the storage device, after the hard disks form a redundant independent disk array group, these redundant independent disk array groups usually need to be divided into logical storage units and allocated to the server, and the logical units in the storage device are usually described by the Logical Unit Number (LUN).

[0023] For the convenience of refined data management, the logical storage unit is further divided into storage extents as the basic units for data allocation and management. Each storage extent is further refined into data blocks (Sections) with a unit of 256 KB, which form the smallest granularity for data management operations.

[0024] S102. In response to a destruction instruction, send a data destruction task to the target execution agent.

[0025] Among them, data destruction is used to task the target execution agent to destroy data with a preset proportion in the target logical storage unit.

[0026] After receiving the destruction instruction, the control end determines the target execution agent for executing the current data destruction task among multiple execution agents. After determining the target execution agent, the data destruction task is sent to the target execution agent, so that the target execution agent destroys the data with a preset proportion in the target logical storage unit according to the indication of the data destruction task.

[0027] Specifically, the destruction instruction is an instruction for completely destroying the data in the target logical storage unit. Furthermore, regarding all the data in the target logical storage unit as 100%, when the preset proportion is 1%, the data destruction task instructs the target agent execution end to destroy 1% of the data in the target logical storage unit.

[0028] It should be noted that the preset proportion can be set according to the actual situation, and the present application does not make specific limitations.

[0029] S103. When receiving the destruction progress event sent by the target execution agent, determine whether all the data in the target logical storage unit has been completely destroyed.

[0030] Among them, the destruction progress event is sent after the target execution agent completes the destruction of data with a preset proportion.

[0031] In the embodiment of the present application, after receiving the data destruction task, the target agent immediately destroys the data with a preset proportion. After completing the destruction of the data with a preset proportion, it will timely feedback the destruction situation to the control end, that is, send a destruction progress event to the control end. After receiving the destruction progress event sent by the target execution agent, the control end determines whether all the data in the target logical storage unit has been completely destroyed.

[0032] Exemplarily, when the total data volume size of the target logical storage unit is 100G and the preset proportion size is 1%, the target execution agent needs to destroy 1G of data in the target logical storage unit. Calculated based on each data block in the target logical storage unit storing 256KB of data, 4096 data blocks need to be destroyed each time, thus meeting the requirements of this data destruction task. After the data of these 4096 data blocks is destroyed, a destruction progress event will be sent to the control end. Compared with the method of sending a destruction progress event to the control end every time a data block is destroyed, the number of times of sending the destruction progress event is greatly reduced, reducing the occupation of communication resources.

[0033] When the control end receives this destruction progress event, it needs to determine whether all the data of the target logical storage unit has been destroyed after the destruction of the data of the preset proportion size this time, that is, to measure whether the overall destruction of the target logical storage unit is completed, providing a basis for subsequent decision-making.

[0034] After the above S103 (when receiving the destruction progress event sent by the target execution agent, determine whether all the data of the target logical storage unit has been destroyed) is executed, if all the data of the target logical storage unit has been destroyed, execute the following S104; if all the data of the target logical storage unit has not been destroyed, then execute the following S105: S104. Send a destruction completion notice to the target execution agent.

[0035] When it is confirmed that the overall destruction progress of the target logical storage unit reaches 100%, that is, all the data of the target logical storage unit has been destroyed, a destruction completion notice can be sent to the target execution agent to notify the target execution agent that all the data of the target logical storage unit has been destroyed and there is no need to perform data destruction anymore. At this time, the target execution agent can stop the data destruction operation and release resources.

[0036] S105. Repeatedly send a data destruction task to the execution agent until all the data of the target logical storage unit has been destroyed.

[0037] When it is confirmed that the overall destruction progress of the target logical storage unit has not reached 100%, data destruction operations still need to be continued. Then the control end continues to send a data destruction task to the target execution agent, and still destroys the data of the target logical storage unit according to the preset proportion size until it is confirmed that all the data of the target logical storage unit has been destroyed, that is, the overall destruction progress reaches 100%.

[0038] This application sends a data destruction task to the target execution agent; thereby, it can instruct the target execution agent to destroy the corresponding data of a preset proportion size according to the preset proportion size, and further determine whether the destruction of the target logical storage unit is completed through the data destruction progress of the destruction progress event. Therefore, after the target execution agent destroys the data of the preset proportion size, this application will generate an event interaction between the control end and the execution agent only once. Compared with the original frequent interaction mode of interacting once for every 256KB data block destroyed, it can greatly reduce the event interaction volume between the control end and the execution agent, avoid the problem of occupying core communication resources due to frequent interaction during the data destruction process, reduce the system communication resource occupancy, and ensure the normal operation of other functions of the system.

[0039] As an extension and refinement of the above embodiments, referring to Figure 2 As shown, when receiving the destruction progress event sent by the target execution agent in S103, the specific implementation process of determining whether all the data of the target logical storage unit has been completely destroyed can be refined into the following S201 to S203: S201. Obtain the cumulative number of received destruction progress events.

[0040] Specifically, the control end is also provided with a corresponding event listening mechanism. Through the event listening mechanism, the destruction progress events sent by the target execution agent can be captured in real time. After the target execution agent completes the destruction of the data of the preset proportion size each time, it will send 1 destruction progress event. Then, through the event listening mechanism, the cumulative number of destruction progress events is counted.

[0041] S202. Based on the cumulative number, calculate the overall destruction progress corresponding to the target logical storage unit in combination with the preset proportion size.

[0042] Furthermore, the overall destruction progress can be calculated according to the cumulative number of destruction progress events and the preset proportion size; for example, the overall data size of the target logical storage unit is 1G. When the preset proportion size is 1% and the cumulative number is 100 times, it means that the destruction progress of the target logical storage unit has reached 100%.

[0043] S203. According to the overall destruction progress, determine whether all the data of the target logical storage unit has been completely destroyed.

[0044] Combined with the above embodiments, when the cumulative number is 100 times, it means that the destruction progress of the target logical storage unit has reached 100%, then all the data of the target logical storage unit has been completely destroyed. On the contrary, if the destruction progress of the target logical storage unit has not reached 100%, then all the data of the target logical storage unit has not been completely destroyed.

[0045] The above refinement steps can quantify the number of events, convert the number of events into the overall destruction progress in combination with the preset proportion, and then determine whether all destruction is completed; achieve the precision and lightness of the data destruction process; based on the number of events, calculate the accurate progress in combination with the preset proportion, and while reducing the interaction overhead, accurately obtain the overall destruction progress.

[0046] As an extension and refinement of the above embodiments, the present application also provides a schematic diagram of the interaction process of a data destruction method. Refer to Figure 3 As shown, it is a schematic diagram of the process of the target execution agent in the storage server provided by the present application. The specific steps are as follows: S301. Receive the data destruction task sent by the control end.

[0047] Among them, data destruction is used to task to indicate the destruction of data with a preset proportion in the target logical storage unit.

[0048] In the embodiment of the present application, after the control end responds to the destruction instruction, it sends a data destruction task to the target execution agent. The data destruction task will carry the logical storage unit number of the target logical storage unit, and then accurately locate the target logical storage unit according to the logical storage unit number to carry out subsequent data destruction operations on the target logical storage unit, and then destroy the data with a preset proportion in the target logical storage unit in combination with the instructions in the data destruction task.

[0049] Specifically, when the total amount of data in the target logical storage unit is 100G and the preset proportion is 1%, at this time, the target execution agent needs to destroy 1G of data in the target logical storage unit. Since, when destroying the data in the target logical storage unit, multiple data blocks in the storage expansion block in the target logical storage unit are destroyed one by one; then, when 1G of data in the target logical storage unit needs to be destroyed, based on each data block being a 256KB data block, 4096 data blocks need to be destroyed this time; and then the target execution agent destroys 4096 data blocks in the target logical storage unit one by one.

[0050] S302. In response to the data destruction task, destroy the data in the target logical storage unit, and generate a destruction progress event when the destroyed data reaches the preset proportion.

[0051] In the embodiment of the present application, after the target execution agent receives the data destruction task, it will immediately respond to the data destruction task and start destroying the data in the target logical storage unit until the destroyed data reaches the preset proportion and then pause, and generate a destruction progress event to feedback to the control end that the target agent execution end has completed the destruction of the data with the preset proportion.

[0052] Combined with the embodiment in S301 above, that is, after the target execution agent destroys 4096 data blocks in the target logical storage unit, a destruction progress event is generated.

[0053] S303. Send the destruction progress event to the control end, so that when the control end receives the destruction progress event sent by the target execution agent, it can determine whether all the data in the target logical storage unit has been destroyed.

[0054] After generating the destruction progress event, it is necessary to immediately send the destruction progress event to the control end, so that after the control end receives the destruction progress event, it can determine whether all the data in the target logical storage unit has been destroyed, providing a basis for whether data destruction needs to continue in the future.

[0055] In the embodiment of the present application, from the perspective of the target execution agent, by receiving the data destruction task sent by the control end, the task objectives and scope are clarified, and the precise orientation of the data destruction operation is realized. Through the data destruction task, the target execution agent is instructed to perform data destruction according to a preset proportion. After the data of the preset proportion is destroyed, a destruction progress event is generated again and sent to the control end; thus, it is avoided to send a destruction progress event to the control end every time a data block is destroyed, greatly reducing the amount of destruction progress events sent and reducing the occupation of communication resources.

[0056] As an extension and refinement of the above embodiment, referring to Figure 4 As shown, the specific process of destroying the data in the target logical storage unit in response to the data destruction task in S202 above and generating a destruction progress event when the destroyed data reaches a preset proportion can be refined into the following steps: S401. In response to the data destruction task, determine multiple data blocks corresponding to the target logical storage unit.

[0057] Specifically, the target execution agent first locates multiple storage expansion blocks corresponding to the logical storage unit number through the logical storage unit number, and then obtains the data blocks corresponding to the multiple storage expansion blocks to clarify the specific objects to be subjected to data destruction in the future, that is, multiple data blocks.

[0058] S402. Generate a data block overwrite instruction for any one of the multiple data blocks.

[0059] In some embodiments, the data in the data block is stored in the form of binary numbers 1 and 0; meaningless and irregular new data (such as all 0s, all 1s, or random numbers, etc.) is used to overwrite the original binary content of the data block through data block overwriting; thereby destroying the physical traces (magnetic signals, electronic potentials, etc.) of the original data in the data block, making it impossible to restore the original combination of the data block through technical means, and achieving the purpose of data destruction.

[0060] It should be noted that, in order to ensure the complete destruction of the data in the data block, it is necessary to perform multiple data overwrites on the same data block, that is, after destroying the data of the entire target logical storage unit once using the data destruction method of the above embodiments of the present application, the merchant destruction process can be repeated multiple times to perform multiple overwrites on the data blocks of the target logical storage unit; for example, it is necessary to perform 3 destructions on the target logical storage unit. For the first time, all 0s are used to overwrite the data block during data block overwriting, for the second time, all 1s are used to overwrite the data block during data block overwriting, and for the third time, random numbers are used to overwrite the data block during data block overwriting; through the above multiple overwriting methods, the original data of the data blocks of the target logical storage unit is completely destroyed, improving the security of the data.

[0061] S403. In response to the data block overwriting instruction, overwrite the data in the data block, and after the data block is overwritten, determine whether the destroyed data reaches a preset proportion size.

[0062] It should be noted that when overwriting the data in the data block, the target execution agent mainly organizes the overwriting process of multiple data blocks. Since overwriting the data in the data block belongs to data I / O (input / output) operations, its essence is to modify the original data on the data block through I / O operations; then during data block overwriting, it can be executed by the lower-level module responsible for I / O operations. Specifically, after a certain data block is overwritten, the lower-level module responsible for I / O operations will feedback a completion message to the target execution agent, and then the target execution agent will determine whether the destroyed data reaches a preset proportion size.

[0063] Specifically, the specific steps for determining whether the destroyed data reaches a preset proportion size can refer to the following Step 1 and Step 2: Step 1. After the data block is overwritten, increment the data block overwrite count by one to obtain the total data block overwrite count.

[0064] In the embodiments of the present application, a data block overwrite count is set for the data block overwriting process. Whenever a data block is overwritten, the data block overwrite count is incremented by one, and finally the total data block overwrite count is calculated.

[0065] Step 2: Determine whether the destroyed data reaches the preset proportion according to the total number of data block overwrites.

[0066] Furthermore, after each overwrite is completed, according to the total number of data block overwrites and considering that each data block stores 256 KB of data, calculate whether the currently destroyed data reaches the preset proportion.

[0067] It should be noted that it is possible that the data in the last data block of a storage expansion block is less than 256 KB. When overwriting, only the valid data in this data block needs to be overwritten. However, when subsequently counting the total number of data block overwrites, this data block is still regarded as a complete data block for calculation.

[0068] Exemplarily, when the total data volume of the target logical storage unit is 100 G and the preset proportion is 1%, when the total number of data block overwrites by the target execution agent is 100, calculating based on each data block storing 256 KB of data, the total amount of data destroyed at this time is 25600 KB, which is approximately 0.024 G. Then it does not meet the requirement of the preset proportion of 1%, and the destruction of the next data block needs to be continued until 1% of the data, that is, 1 G of data, is destroyed. That is, 4096 data blocks need to be destroyed.

[0069] After the above S403 (determine whether the destroyed data reaches the preset proportion) is executed, if the destroyed data reaches the preset proportion, execute S404 as follows; if the destroyed data does not reach the preset proportion, then execute S405 as follows: S404: Generate a destruction progress event.

[0070] When the proportion of the destroyed data volume reaches the preset proportion, the target execution agent can generate a destruction progress event, and then feedback to the control end that it has completed the data destruction work of the preset proportion, so as to drive the control end to make a decision on whether to continue the destruction accordingly.

[0071] S405: Repeat generating a data block overwrite instruction for any one of multiple data blocks until the destroyed data reaches the preset proportion.

[0072] When the proportion of the destroyed data volume has not reached the preset proportion, the target execution agent continues to perform the destruction operation of the next data block, and repeats the steps of S402 - S403 until the destroyed data reaches the preset proportion.

[0073] In the embodiment of the present application, it is described that after the target execution agent receives the data destruction task, taking data blocks as the operation unit, each data block is operated one by one to destroy the data in the data block. Furthermore, the progress is counted every time a data block overwriting is completed. After judging whether the destroyed data reaches the preset proportion size through the relationship between the size of the destroyed data and the proportion size of the data, a destruction progress event is generated, and then a feedback is sent to the control end once. Compared with the original frequent interaction mode where every 256KB data block is interacted once during the data destruction process, the event interaction amount between the control end and the execution agent can be greatly reduced, avoiding the problem of occupying core communication resources due to frequent interaction during the data destruction process, reducing the occupation of system communication resources, and ensuring the normal operation of other functions of the system.

[0074] As an extension and refinement of the above embodiment, the present application also provides a schematic diagram of the interaction process of a data destruction method. Referring to Figure 5 as shown, it is a schematic diagram of the interaction process between the control end and the target execution agent in the storage server provided by the present application. The specific steps are as follows: S501. The control end receives a destruction instruction for the target logical storage unit.

[0075] S502. In response to the destruction instruction for the target logical storage unit, the control end determines the target execution agent from multiple execution agents and sends a data destruction task to the target execution agent.

[0076] Among them, the data destruction task is used to instruct the target execution agent to destroy the data with a preset proportion size in the target logical storage unit; the target execution agent is any one of the multiple execution agents in the initial waiting-to-be-used state.

[0077] Specifically, when an execution agent is in the initial waiting-to-be-used state, it means that it is not occupied by other tasks, that is, there is no ongoing destruction process for this execution agent; furthermore, according to the states of multiple execution agents, the execution agent in the initial waiting-to-be-used state can be used as the target execution agent.

[0078] In the embodiment of the present application, after determining the target execution agent from multiple execution agents, the control end changes its execution state from waiting for an assigned agent to the state of executing destruction.

[0079] Specifically, after determining the target execution agent, the control end itself needs to change its state, that is, switch from waiting for an assigned agent to the state of executing destruction; furthermore, it announces to other modules in the storage system that the current control end has entered the destruction process to avoid being occupied by other services.

[0080] S503. The target execution agent receives the data destruction task sent by the control end.

[0081] Among them, data destruction is used for the task to indicate the destruction of data with a preset proportion in the target logical storage unit.

[0082] S504. In response to the data destruction task, the target execution agent destroys the data in the target logical storage unit, and generates a destruction progress event when the destroyed data reaches the preset proportion.

[0083] S505. The target execution agent sends the destruction progress event to the control end, so that when the control end receives the destruction progress event sent by the target execution agent, it judges whether all the data in the target logical storage unit has been completely destroyed.

[0084] S506. When the control end receives the destruction progress event sent by the target execution agent, it judges whether all the data in the target logical storage unit has been completely destroyed.

[0085] Among them, the destruction progress event is sent after the target execution agent completes the destruction of data with the preset proportion.

[0086] After the above S506 (when the control end receives the destruction progress event sent by the target execution agent, it judges whether all the data in the target logical storage unit has been completely destroyed) is executed, if all the data in the target logical storage unit has been completely destroyed, execute the following S507; if not all the data in the target logical storage unit has been completely destroyed, then execute the following S508: S507. The control end sends a destruction completion notice to the target execution agent.

[0087] Specifically, after the control end sends the destruction completion notice to the target execution agent, the method further includes the following steps: Step A. After sending the destruction completion notice to the target execution agent, the execution status of the control end is switched from the execution destruction status to the stop destruction status.

[0088] After the control end confirms through progress judgment that the destruction progress of the target logical storage unit reaches 100%, it determines that the data destruction has been completed. At this time, the control end itself will switch the execution status from the execution destruction status to the stop destruction status to mark that the current destruction task for the target logical storage unit has been completely completed and subsequent cleanup operations can be carried out.

[0089] Step B. The target agent receives the destruction completion notice sent by the control end, and in response to the destruction completion notice, the target execution agent switches the execution status from the task - in - progress status to the initial standby state and sends an agent status change completion event to the control end.

[0090] Specifically, when the target execution agent receives the destruction completion notice and learns that the control end has declared that the destruction task for the target logical storage unit has been completely ended, the target execution agent can then enter the status reset process, that is, switch the execution status from the task-executing status to the initial waiting-for-use status to prepare for undertaking new tasks; this avoids the target execution agent continuously waiting for instructions and causing resource waste.

[0091] Step C: The control end receives the agent status change completion event sent by the target execution agent.

[0092] The control end receives the agent status change completion event sent by the target execution agent through the event listening mechanism, and thus can confirm that the target execution agent has been switched to the initial waiting-for-use status.

[0093] Step D: Based on the agent status change completion event, the control end updates the execution status from the stop-destruction status to the initial waiting-for-use status.

[0094] Since the control end confirms that the target execution agent has been switched to the initial waiting-for-use status according to the status change completion event sent by the target execution agent, the control end itself can then switch the execution status from the stop-destruction status to the initial waiting-for-use status to mark that it can undertake new destruction tasks, so that the entire destruction process forms a complete closed loop from start to finish.

[0095] The embodiments of the present application illustrate that the control end and the agent verify the status change through event interaction, prevent the system status inconsistency caused by unilateral status misjudgment, ensure that both parties' cognitions of the task completion status are strictly synchronized, and facilitate the subsequent development of other services.

[0096] S508: The control end repeatedly sends the data destruction task to the execution agent until all the data in the target logical storage unit is completely destroyed.

[0097] Through the description of the above implementation manners, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases, the former is a better implementation manner.

[0098] The embodiments of the present application also provide a data destruction device, which corresponds one by one to the method claims. Figure 6 Shown in the following is a schematic structural diagram of a data destruction device 600 provided by the present disclosure. Figure 6 As shown, the device 600 in this embodiment includes: An instruction receiving module 61, configured to receive the destruction instruction of the target logical storage unit; A task sending module 62, configured to send a data destruction task to a target execution agent in response to the destruction instruction; the data destruction task is used to instruct the target execution agent to destroy data with a preset proportion in the target logical storage unit. A progress judgment module 63, configured to receive a destruction progress event sent by the target execution agent, and determine whether all the data in the target logical storage unit has been completely destroyed according to the data destruction progress carried in the destruction progress event. The task sending module 62 is further configured to determine that the destruction of the target logical storage unit has been completed when all the data in the target logical storage unit has been completely destroyed, and send a destruction completion notice to the target execution agent. The task sending module 62 is further configured to repeatedly send the data destruction task to the execution agent when all the data in the target logical storage unit has not been completely destroyed until all the data in the target logical storage unit has been completely destroyed.

[0099] As an optional implementation manner of an embodiment of the present application, the progress judgment module 63 is specifically configured to obtain the cumulative number of received destruction progress events; based on the cumulative number, calculate the overall destruction progress corresponding to the target logical storage unit in combination with the preset proportion; and determine whether all the data in the target logical storage unit has been completely destroyed according to the overall destruction progress.

[0100] As an optional implementation manner of an embodiment of the present application, the data destruction device further includes a processing module, specifically configured to determine the target execution agent from multiple execution agents in response to the destruction instruction for the target logical storage unit; the target execution agent is any execution agent in an initial to-be-used state among the multiple execution agents.

[0101] As an optional implementation manner of an embodiment of the present application, after the processing module determines the target execution agent from multiple execution agents, the control end switches the execution state from a to-be-allocated agent to an execution destruction state.

[0102] As an optional implementation manner of an embodiment of the present application, after the processing module sends a destruction completion notice to the target execution agent, the execution state of the control end switches from an execution destruction state to a stop destruction state; receive an agent state change completion event sent by the target execution agent; and update the execution state from the stop destruction state to an initial to-be-used state based on the agent state change completion event.

[0103] For the description of the features in the embodiment corresponding to the data destruction device, reference may be made to the relevant description of the embodiment corresponding to the data destruction method, which will not be elaborated here one by one.

[0104] An embodiment of the present application further provides another data destruction device, which corresponds one-to-one to the method claims. Figure 7 As shown in the structural schematic diagram of another data destruction device 700 provided by the present disclosure, Figure 7 As shown, the device 700 of this embodiment includes: A task receiving module 71, configured to receive a data destruction task sent by a control end; the data destruction is used to task-indicate the destruction of data with a preset proportion size in a target logical storage unit; A data destruction module 72, configured to respond to the data destruction task, destroy the data in the target logical storage unit, and generate a destruction progress event when the destroyed data reaches the preset proportion size; An event sending module 73, configured to send the destruction progress event to the control end, so that when the control end receives the destruction progress event sent by the target execution agent end, it determines whether all the data in the target logical storage unit has been completely destroyed.

[0105] As an optional implementation manner of an embodiment of the present application, the data destruction module 72 is specifically configured to respond to the data destruction task, determine a plurality of data blocks corresponding to the target logical storage unit; for any one of the plurality of data blocks, generate a data block overwrite instruction; respond to the data block overwrite instruction, overwrite the data in the data block, and after the data block is overwritten, determine whether the destroyed data reaches the preset proportion size; if so, generate a destruction progress event.

[0106] As an optional implementation manner of an embodiment of the present application, the data destruction module 72 is specifically configured to, if not, repeat generating the data block overwrite instruction for any one of the plurality of data blocks until the destroyed data reaches the preset proportion size.

[0107] As an optional implementation manner of an embodiment of the present application, the data destruction module 72 is specifically configured to, after the data block is overwritten, increment the data block overwrite count by one to obtain the total data block overwrite count; and determine whether the destroyed data reaches the preset proportion size according to the total data block overwrite count.

[0108] As an optional implementation manner of an embodiment of the present application, the task receiving module 71 is further configured to receive a destruction completion notice sent by the control end, and in response to the destruction completion notice, the target execution agent end switches the execution state from the task-executing state to the initial waiting-for-use state, and sends an agent state change completion event to the control end.

[0109] For the description of the features in the corresponding embodiments of the data destruction device, reference may be made to the relevant descriptions in the corresponding embodiments of the data destruction method, which will not be elaborated here one by one.

[0110] An embodiment of the present application further provides an electronic device, including a memory and a processor. A computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any of the above-described embodiments of the data destruction method.

[0111] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps in any of the above-described embodiments of the data destruction method when running.

[0112] In an exemplary embodiment, the above computer-readable storage medium may include, but is not limited to: USB flash drives, read-only memories (ROM for short), random access memories (RAM for short), mobile hard disks, magnetic disks, or optical discs, etc., various media that can store computer programs.

[0113] An embodiment of the present application further provides a computer program product. The above computer program product includes a computer program, and when the computer program is executed by a processor, it implements the steps in any of the above-described embodiments of the data destruction method.

[0114] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium. The non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the steps in any of the above-described embodiments of the data destruction method.

[0115] Those skilled in the art can further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0116] The above has introduced in detail a data destruction method and apparatus provided by the present application. Specific examples are used herein to elaborate on the principle and implementation manner of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the protection scope of the claims of the present application.

Claims

1. A data destruction method, characterized in that, Applied to the control end in a storage server, including: Receiving a destruction instruction for a target logical storage unit; In response to the destruction instruction, sending a data destruction task to the target execution agent; the data destruction task is used to instruct the target execution agent to destroy data with a preset proportion size in the target logical storage unit; When receiving the destruction progress event sent by the target execution agent, determining whether all the data in the target logical storage unit has been completely destroyed; the destruction progress event is sent after the target execution agent completes the destruction of data with a preset proportion size; If so, sending a destruction completion notice to the target execution agent; If not, repeatedly sending the data destruction task to the execution agent until all the data in the target logical storage unit has been completely destroyed.

2. The data destruction method according to claim 1, wherein When receiving the destruction progress event sent by the target execution agent, determining whether all the data in the target logical storage unit has been completely destroyed; includes: Obtaining the cumulative number of received destruction progress events; Based on the cumulative number, calculating the overall destruction progress corresponding to the target logical storage unit in combination with the preset proportion size; According to the overall destruction progress, determining whether all the data in the target logical storage unit has been completely destroyed.

3. The data destruction method according to claim 1, wherein The method further includes: In response to the destruction instruction for the target logical storage unit, determining the target execution agent from multiple execution agents; the target execution agent is any one of the multiple execution agents in an initial waiting-to-be-used state.

4. The data destruction method according to claim 3, wherein The method further includes: After determining the target execution agent from multiple execution agents, the control end switches its execution state from waiting-for-allocation agent to executing destruction state.

5. The data destruction method according to claim 1, wherein The method further includes: After sending the destruction completion notice to the target execution agent, the execution state of the control end switches from the executing destruction state to the stopping destruction state; Receiving the agent state change completion event sent by the target execution agent; Based on the agent state change completion event, updating the execution state from the stopping destruction state to the initial waiting-to-be-used state.

6. A data destruction method, characterized in that, Applied to the target execution agent in a storage server, including: Receiving the data destruction task sent by the control end; the data destruction task is used to instruct the destruction of data with a preset proportion size in the target logical storage unit; In response to the data destruction task, destroying the data in the target logical storage unit, and generating a destruction progress event when the destroyed data reaches the preset proportion size; Sending the destruction progress event to the control end, so that the control end determines whether all the data in the target logical storage unit has been completely destroyed when receiving the destruction progress event sent by the target execution agent.

7. The data destruction method according to claim 6, wherein In response to the data destruction task, destroying the data in the target logical storage unit, and generating a destruction progress event when the destroyed data reaches the preset proportion size; includes: In response to the data destruction task, determining multiple data blocks corresponding to the target logical storage unit; Generate a data block overwrite instruction for any one of the multiple data blocks; In response to the data block overwrite instruction, overwrite the data in the data block, and after the data block is overwritten, determine whether the destroyed data reaches the preset proportion size; If so, generate a destruction progress event.

8. The data destruction method according to claim 7, characterized in that, After determining whether the destroyed data reaches the preset proportion size, the method further includes: If not, repeat generating the data block overwrite instruction for any one of the multiple data blocks until the destroyed data reaches the preset proportion size.

9. The data destruction method according to claim 7, wherein The determining whether the destroyed data reaches the preset proportion size after the data block is overwritten; includes: After the data block is overwritten, increment the data block overwrite count by one and obtain the total data block overwrite count; Based on the total data block overwrite count, determine whether the destroyed data reaches the preset proportion size.

10. The data destruction method according to claim 6, wherein The method further includes: Receive the destruction completion notification sent by the control end, and in response to the destruction completion notification, the target execution agent changes the execution state from the task execution state to the initial waiting-for-use state and sends an agent state change completion event to the control end.

11. A data destruction device, characterized in that, Includes: An instruction receiving module, configured to receive a destruction instruction of a target logical storage unit; A task sending module, configured to send a data destruction task to a target execution agent in response to the destruction instruction; the data destruction task is used to instruct the target execution agent to destroy a preset proportion size of data in the target logical storage unit; A progress judgment module, configured to receive a destruction progress event sent by the target execution agent, and determine whether all the data in the target logical storage unit is completely destroyed according to the data destruction progress carried by the destruction progress event; The task sending module is further configured to determine that the destruction of the target logical storage unit is completed when all the data in the target logical storage unit is completely destroyed, and send a destruction completion notification to the target execution agent; The task sending module is further configured to, when all the data in the target logical storage unit is not completely destroyed, repeatedly send the data destruction task to the execution agent until all the data in the target logical storage unit is completely destroyed.

12. A data destruction device, characterized in that, Includes: A task receiving module, configured to receive a data destruction task sent by a control end; the data destruction task is used to instruct to destroy a preset proportion size of data in a target logical storage unit; A data destruction module, configured to destroy the data in the target logical storage unit in response to the data destruction task, and generate a destruction progress event when the destroyed data reaches the preset proportion size; An event sending module, configured to send the destruction progress event to the control end, so that the control end determines whether all the data in the target logical storage unit is completely destroyed when receiving the destruction progress event sent by the target execution agent.

13. An electronic device, characterized in that, Includes: A memory, configured to store a computer program; A processor, configured to implement the steps of the data destruction method according to any one of claims 1 to 5 or any one of claims 6 to 10 when executing the computer program.

14. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, wherein when the computer program is executed by a processor, the steps of the data destruction method according to any one of claims 1 to 5 or any one of claims 6 to 10 are implemented.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, the steps of the data destruction method according to any one of claims 1 to 5 or any one of claims 6 to 10 are implemented.

Images