CN113010107A

CN113010107A - Data storage management method and device, computer equipment and storage medium

Info

Publication number: CN113010107A
Application number: CN202110219880.1A
Authority: CN
Inventors: 肖蔓君; 甘金涛; 徐超; 李小凤
Original assignee: Shenzhen Union Memory Information System Co Ltd
Current assignee: Shenzhen Union Memory Information System Co Ltd
Priority date: 2021-02-26
Filing date: 2021-02-26
Publication date: 2021-06-22
Anticipated expiration: 2041-02-26
Also published as: CN113010107B

Abstract

The invention discloses a data storage management method, a data storage management device, computer equipment and a storage medium, wherein the method comprises the following steps: analyzing key data of an operating system to obtain key data characteristics; acquiring write data issued by a host; judging whether the write data has key data characteristics; and if the write data has the key data characteristics, judging the write data to be key data, improving the protection level of the write data and writing the data. According to the scheme, when the host issues the write-in data, the key data characteristics of the key data of the operating system are analyzed, whether the write-in data are the key data or not is determined according to the key data characteristics, if the write-in data are the key data, a protection strategy with a higher grade is adopted for storage management, data damage caused by the physical risk of the NANDflash is avoided, and the data safety is improved.

Description

Data storage management method and device, computer equipment and storage medium

Technical Field

The present invention relates to the field of data management, and more particularly, to a data storage management method, apparatus, computer device, and storage medium.

Background

The SSD, which is called Solid State Drive in english, is also called a Solid State disk, and has been widely used in various occasions, has gradually replaced the conventional HDD in the PC market at present, and provides better experience for users in terms of reliability and performance.

In the existing storage management scheme, the SSD is used as a receiving end to obtain commands formulated by various protocols issued from the host, and to complete communication interaction with the host, data transmission, and the like. At present, in the conventional practice in the industry, the SSD does not care about the data content, so for the processing that the data from the host side is treated as if all, various considerations of the NAND flash writing mode are generally performed according to the parallel performance requirement, the data security, and the like, but these considerations are irrelevant to the content.

In the use of a user, common SSD abnormal performances such as hard disk failure identification, system start failure, system blue screen and the like are mostly in direct relation with the damage or loss of key data of an operating system. Because the guidance of the key data is lost, the operating system cannot work normally, and although the user data is safe in the hard disk, the user data cannot be accessed, so that the normal use of the user is influenced.

The information disclosed in this background section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

Disclosure of Invention

In order to solve the above-mentioned drawbacks of the prior art, an object of the present invention is to provide a data storage management method, apparatus, computer device and storage medium.

In order to achieve the purpose, the technical scheme of the invention is as follows:

in a first aspect, the present invention provides a data storage management method, including the following steps:

analyzing key data of an operating system to obtain key data characteristics;

acquiring write data issued by a host;

judging whether the write data has the key data characteristics;

and if the write data has the key data characteristics, judging the write data to be key data, improving the protection level of the write data and writing the data.

In a second aspect, the present invention provides a data storage management apparatus, including:

the characteristic analysis unit is used for analyzing the key data of the operating system to obtain key data characteristics;

the data acquisition unit is used for acquiring write data issued by the host;

the data judging unit is used for analyzing whether the write data has the key data characteristics;

and the data writing unit is used for judging that the write data is the key data when the write data has the key data characteristics, improving the protection level of the write data and writing the data.

In a third aspect, the present invention provides a computer device, which includes a memory and a processor, where the memory stores a computer program thereon, and the processor implements the data storage management method as described above when executing the computer program.

In a fourth aspect, the present invention proposes a storage medium storing a computer program which, when executed by a processor, implements a data storage management method as described above.

Compared with the prior art, the invention has the beneficial effects that: the invention provides a data storage management method, a data storage management device, computer equipment and a storage medium. Specifically, when the host issues the write-in data, the data storage management method determines whether the write-in data is the key data or not according to the key data characteristics by analyzing the characteristics of the key data of the operating system, and if the write-in data is the key data, the storage management is performed by adopting a protection strategy with a higher level, so that data damage caused by the physical risk of the NAND flash is avoided, and the data security is improved.

The invention is further described below with reference to the accompanying drawings and specific embodiments.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are 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 flowchart of a data storage management method according to an embodiment of the present invention;

FIG. 2 is a sub-flow diagram of a data storage management method according to an embodiment of the present invention;

FIG. 3 is a sub-flowchart of a data storage management method according to an embodiment of the present invention;

FIG. 4 is a sub-flowchart of a data storage management method according to an embodiment of the present invention;

FIG. 5 is a schematic block diagram of a data storage management apparatus according to an embodiment of the present invention;

FIG. 6 is a schematic block diagram of a characteristic analysis unit of a data storage management device according to an embodiment of the present invention;

FIG. 7 is a schematic block diagram of a data determination unit of a data storage management device according to an embodiment of the present invention;

FIG. 8 is a schematic block diagram of a data writing unit of a data storage management device according to an embodiment of the present invention;

FIG. 9 is a schematic block diagram of a computer device provided by an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. 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.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

Fig. 1 is a schematic flowchart of a data storage management method according to an embodiment of the present invention. As shown in fig. 2, the method includes the following steps S110 to S150.

And S10, analyzing the key data of the operating system to obtain key data characteristics.

In this embodiment, although there are differences in data management manners of different operating systems, basically all operating systems store system management data (key data described below, such as a driver and a registry, but do not include user data, so as to ensure privacy and security of the user data) in a corresponding data sector, and therefore it can be further determined whether write data issued by a host is key data by determining whether a Logical Block Address (LBA) of the write data is within the data sector for storing the key data.

In the scheme, the key data of the operating system is analyzed to obtain key data characteristics, wherein the key data characteristics are the sector positions or ranges for storing the key data, and whether the write data needs to be written into the corresponding sector positions is determined by analyzing the LBA of the write data, so that whether the write data is the key data can be determined.

Referring to FIG. 2, in the present embodiment, step S10 includes steps S11-S1

And S11, acquiring the data sector managed by the operating system.

And S12, identifying the key sector position of the key data in the data sector.

And S13, resolving the key sector to obtain the position of the key guide sector.

And S14, taking the key sector position and the key guide sector position as key data characteristics.

In this embodiment, the data sector managed by the operating system is acquired, that is, the data sector storing the system boot data (key data) is analyzed, the key LBA of the system boot data is analyzed and marked, the starting process of the operating system is analyzed, the key sector containing the key data is specified, the key sector is further analyzed in a targeted manner, the position of the key boot sector stored in the key sector is further acquired, and the position of the key sector and the position of the key boot sector are used as the key data characteristics for evaluating write data.

The key boot sector position is a data sector located in another partition and used for storing system data, and the key boot sector position information is recorded in the key sector, for example, in a Windows system, LBA 0 of a general main partition is a key sector, and the key data sector of another active partition of a hard disk is also recorded in LBA 0, that is, the key boot sector.

Taking the WIN10 operating system boot process as an example, in particular, the Windows boot process generally includes the following four phases:

1) preboot: preboot is a post (power On Self test) loading firmware configuration, wherein for a hard disk such as SSD, it is checked whether a valid system is included.

2) The Windows Boot manager confirms whether a plurality of operating systems are installed, and if so, a selection menu is provided for selection;

3) the Windows OS loader loads an important driver through WinLoad.exe to start a Windows kernel, and the kernel uses the driver to communicate with hardware and executes other necessary booting operations;

4) windows NT OS Kernel obtains registry settings and other drivers, and once the read is successful, the system manager process obtains control, loads the user interface, and other software and hardware.

The loading of the files and paths in the boot process of step 3 are different according to different BIOS or UEFI, but all are performed by the LBA according to a specific rule. Taking legacy MBR (Master Boot Record) loading process as an example, after a computer is started, first accessing LBA 0 of a hard disk, and recording related information of the hard disk itself and size and position information of each partition of the hard disk in MBR 512B.

And then, a bootable "active Partition" is found from the Partition table, and then, data of a first logical sector in a main Partition (active Partition) is loaded into a memory, where the LBA sector is called a Volume Boot Record (VBR, also called a Partition Boot Record, PBR). The program location for booting the operating system is identified in the PBR, and control is then passed to the operating system within the primary partition, with the hard disk being managed by the information within the primary partition.

The specific process comprises the following steps: the PBR searches a Boot loader (Boot manager) of a bootable operating system under a root directory of the main partition, the computer loads the Boot loader, the Boot loader searches Boot configuration data in the main partition, the Boot loader sends an operating system initialization program after the selection of the corresponding operating system is completed, and the kernel, hardware, services, a desktop and the like of the operating system are continuously loaded, so that the Boot of the whole operating system is completed.

As is clear from the above process, the starting process of the operating system is managed strictly according to the data boot logic in the LBA, and different operating systems start different specific objects, but the basic process is the same.

Therefore, according to the data storage management method provided by the scheme, the data sector storing the system boot data (key data) is analyzed, the key LBA of the system boot data is analyzed and marked, the starting process of the operating system is analyzed, the included default key sector is determined, the key sector is further analyzed in a targeted manner, the position of the key boot sector stored in the key sector is further obtained, and the position of the key sector and the position of the key boot sector are used as key data characteristics for evaluating write data.

Specifically, after collecting the important key sector positions and key boot sector positions, a flag may be added to the corresponding sector (for example, a level flag is added to the mapping table), and in each subsequent module managed by the SSD FTL, the level flag carried in the mapping table may play a role in the operation of each module (such as read-write processing, GC, WL, etc.), and a higher-level protection policy may be used for storage management.

And S20, acquiring the write data issued by the host.

In this embodiment, the SSD receives a write command issued by the host and writes corresponding write data to complete data transmission, but in the conventional scheme, data from the host is treated identically, and generally various considerations of the NAND flash write-in manner are performed according to the parallel performance requirement, data security, and the like, but these considerations are irrelevant to the content, and thus, the key data cannot be protected better.

And S30, judging whether the written data has key data characteristics.

In this embodiment, after the key data features are obtained, the write data issued by the host is analyzed to determine whether the write data has the corresponding key data features, and if the write data has the key data features, the write data can be divided into key data to be stored, so as to improve the security of the key data and further improve the security of the corresponding operating system; if the key data characteristics are not available, the data are directly stored as common data, and the common data are lost, so that the operating system cannot be started, and the normal use of a user is ensured.

Referring to fig. 3, in the present embodiment, step S30 includes steps S31 and S32.

And S31, analyzing the write data and obtaining the LBA of the write data.

S32, judging whether the LBA of the write data is located in the key sector position or the key boot sector position.

In this embodiment, after receiving the write data, the LBA of the write data is analyzed, and whether the LBA of the write data is located in the key sector position or the key boot sector position is determined, and if the LBA of the write data is located in the key sector position or the key boot sector position, the LBA of the write data represents that the LBA of the write data has the key data feature, and the LBA of the write data should be stored as the key data.

And S40, if the write data has the key data characteristics, judging the write data to be key data, and increasing the protection level of the write data to write the data.

In this embodiment, after determining that the write data has the key data feature, the write data is represented as the key data, and at this time, the scheme performs data writing by using a storage policy with a higher protection level, so as to avoid data damage caused by a physical risk of the NAND flash, and ensure data security and stability of the key data.

Referring to FIG. 4, in one embodiment, step S40 includes steps S41-S43.

And S41, feeding back the write data with the key data characteristics to the SSD FTL.

And S42, adding a management label to the write data through the SSD FTL to mark the protection level of the write data.

And S43, writing data by adopting a corresponding storage strategy according to the protection level of the written data.

In this embodiment, the SSD FTL (Flash translation layer) is configured to complete the conversion from the logical address of Host to the physical address of Flash, and when writing a piece of data into Flash, the FTL records the mapping relationship from the logical address to the physical address of the written data, so that when Host wants to read the piece of data, real data is read according to the mapping. When the write data is judged to be the key data, the mechanism is fed back to the FLT, FTL management can decide the protection level of the write data, the protection level is superior to that of common user data, and a management label is added, wherein the label is used for identifying the protection level of the write data. The protection level is for critical data, and for example, the protection level can be divided into two protection levels of very important and general important, correspondingly, the relative very important priority is higher than the general important priority than the normal user data, and the resource allocation is more when the data is written when the protection level is higher. In the present embodiment, step S43 includes at least one of steps S43a, S43b, and S43 c.

And S43a, writing the write data by adopting the high-level RAID storage strategy.

S43b, creating multiple data backup for writing data at the same time and writing.

S43c, dividing the independent storage area for writing the write data.

It should be understood that the key data storage strategies or storage modes of the present solution include, but are not limited to, the above three. In practical application, multiple storage strategies can be simultaneously adopted for data writing storage, so as to improve the data security of critical data, for example, the critical data storage is simultaneously carried out by adopting S43a and S43 b.

According to the data storage management method, when the host issues the write-in data, the key data characteristics of the key data of the operating system are analyzed, whether the write-in data is the key data is determined according to the key data characteristics, if the write-in data is the key data, the storage management is performed by adopting a protection strategy with a higher grade, data damage caused by NAND flash physical risks is avoided, and data safety is improved.

FIG. 5 is a schematic block diagram of a data storage management apparatus according to an embodiment of the present invention. As shown in fig. 5, the present invention also provides a data storage management apparatus corresponding to the above data storage management method. The data storage management device comprises a unit for executing the data storage management method, and the device can be configured in a desktop computer, a tablet computer, a portable computer, and other terminals. Specifically, referring to fig. 5, the data storage management apparatus includes a feature analysis unit 10, a data acquisition unit 20, a data judgment unit 30, and a data writing unit 40.

And the characteristic analysis unit 10 is used for analyzing the key data of the operating system to obtain key data characteristics.

Referring to fig. 6, in the present embodiment, the feature analysis unit 10 includes a sector acquisition module 11, a sector identification module 12, a sector parsing module 13, and a feature acquisition module 14;

a sector obtaining module 11, configured to obtain a data sector managed by an operating system.

A sector identification module 12, configured to identify a key sector location where key data in the data sector is located.

And a sector parsing module 13, configured to parse the key sector to obtain a key boot sector position.

A feature obtaining module 14, configured to use the key sector position and the key boot sector position as key data features.

The data obtaining unit 20 is configured to obtain write data sent by a host.

And the data judging unit 30 is used for analyzing whether the written data has key data characteristics.

Referring to fig. 7, in the present embodiment, the data judging unit 30 includes a data analyzing module 31 and an address judging module 32.

And the data analysis module 31 is configured to analyze the write data and obtain the LBA of the write data.

The address determination module 32 is configured to determine whether the LBA of the write data is located in the key sector location or the key boot sector location.

And a data writing unit 40, configured to determine that the write data is the key data when the write data has the key data feature, and increase the protection level of the write data to perform data writing.

Referring to fig. 8, in the present embodiment, the data writing unit 40 includes a data feedback module 41, a data ranking module 42, and a data writing module 43.

And a data feedback module 41, configured to feed back the write data with the key data features to the SSD FTL.

And the data classification module 42 is used for adding a management tag to the write data through the SSD FTL to mark the protection level of the write data.

And the data writing module 43 is configured to write data by using a corresponding storage policy according to the protection level of the write data.

In this embodiment, the SSD FTL (Flash translation layer) is configured to complete the conversion from the logical address of Host to the physical address of Flash, and when writing a piece of data into Flash, the FTL records the mapping relationship from the logical address to the physical address of the written data, so that when Host wants to read the piece of data, real data is read according to the mapping. When the write data is judged to be the key data, the mechanism is fed back to the FLT, FTL management can decide the protection level of the write data, the protection level is superior to that of common user data, and a management label is added, wherein the label is used for identifying the protection level of the write data. The protection level is for critical data, and for example, the protection level can be divided into two protection levels of very important and general important, correspondingly, the relative very important priority is higher than the general important priority than the normal user data, and the resource allocation is more when the data is written when the protection level is higher.

The data writing module 43 can write the critical data in the following ways.

1) And writing write data by adopting a high-level RAID storage strategy.

2) And creating multiple data backups for writing data simultaneously and writing.

3) The separate memory area is divided for writing write data.

It should be understood that the key data storage strategies or storage modes of the present solution include, but are not limited to, the above three. In practical application, multiple storage strategies can be simultaneously adopted for data writing storage, so as to improve the data security of the critical data, for example, the 1 st and 2 nd storage strategies are simultaneously adopted for critical data storage.

According to the data storage management device, when the host issues the write-in data, the key data characteristics of the key data of the operating system are analyzed, whether the write-in data are the key data or not is determined according to the key data characteristics, if the write-in data are the key data, a protection strategy with a high grade is adopted for storage management, data damage caused by NAND flash physical risks is avoided, and data safety is improved.

It should be noted that, as can be clearly understood by those skilled in the art, the specific implementation processes of the data storage management apparatus and each unit may refer to the corresponding descriptions in the foregoing method embodiments, and for convenience and brevity of description, no further description is provided herein.

Referring to fig. 9, fig. 9 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device 500 may be a terminal or a server, where the terminal may be an electronic device with a communication function, such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant, and a wearable device. The server may be an independent server or a server cluster composed of a plurality of servers.

Referring to fig. 9, the computer device 500 includes a processor 502, memory, and a network interface 505 connected by a system bus 501, where the memory may include a non-volatile storage medium 503 and an internal memory 504.

The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. The computer programs 5032 include program instructions that, when executed, cause the processor 502 to perform a data storage management method.

The processor 502 is used to provide computing and control capabilities to support the operation of the overall computer device 500.

The internal memory 504 provides an environment for the operation of the computer program 5032 in the non-volatile storage medium 503, and when the computer program 5032 is executed by the processor 502, the processor 502 can be caused to execute a data storage management method.

The network interface 505 is used for network communication with other devices. Those skilled in the art will appreciate that the configuration shown in fig. 9 is a block diagram of only a portion of the configuration associated with the present application and does not constitute a limitation of the computer device 500 to which the present application may be applied, and that a particular computer device 500 may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

Wherein the processor 502 is adapted to run a computer program 5032 stored in the memory.

It should be understood that in the embodiment of the present Application, the Processor 502 may be a Central Processing Unit (CPU), and the Processor 502 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. Wherein a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will be understood by those skilled in the art that all or part of the flow of the method implementing the above embodiments may be implemented by a computer program instructing associated hardware. The computer program includes program instructions, and the computer program may be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the flow steps of the embodiments of the method described above.

Accordingly, the present invention also provides a storage medium. The storage medium may be a computer-readable storage medium.

The storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk, which can store various computer readable storage media.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative. For example, the division of each unit is only one logic function division, and there may be another division manner in actual implementation. For example, various elements or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented.

The steps in the method of the embodiment of the invention can be sequentially adjusted, combined and deleted according to actual needs. The units in the device of the embodiment of the invention can be merged, divided and deleted according to actual needs. In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a storage medium. Based on such understanding, the technical solution of the present invention essentially or partially contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a terminal, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention.

While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A data storage management method, comprising the steps of:

analyzing key data of an operating system to obtain key data characteristics;

acquiring write data issued by a host;

judging whether the write data has the key data characteristics;

2. The data storage management method of claim 1, wherein the step of analyzing the critical data of the operating system to obtain the critical data characteristics comprises,

acquiring a data sector managed by an operating system;

identifying a key sector location in the data sector where key data is located;

analyzing the key sector to obtain the position of a key guide sector;

taking the key sector location and key pilot sector location as key data features.

3. The data storage management method of claim 2, wherein the step of determining whether the write data has the critical data characteristic comprises,

analyzing the write data and obtaining the LBA of the write data;

and judging whether the LBA of the write data is located in the key sector position or the key boot sector position.

4. The data storage management method of claim 1, wherein the step of increasing the protection level of the write data and performing data writing comprises,

feeding back the write data with the key data characteristics to the SSD FTL;

adding a management label to the write data through an SSD FTL to mark the protection level of the write data;

and writing data by adopting a corresponding storage strategy according to the protection level of the write data.

5. The data storage management method of claim 4, wherein the step of writing data with a corresponding storage policy according to the protection level of the write data comprises,

writing the write data by adopting a high-level RAID storage strategy; or,

creating a plurality of data backups for the write data at the same time, and writing; or,

separate memory regions are partitioned for writing the write data.

6. A data storage management apparatus, comprising:

the data acquisition unit is used for acquiring write data issued by the host;

7. The data storage management device according to claim 6, wherein the feature analysis unit comprises a sector acquisition module, a sector identification module, a sector parsing module and a feature acquisition module;

the sector acquisition module is used for acquiring a data sector managed by an operating system;

the sector identification module is used for identifying the position of a key sector where key data in the data sector are located;

the sector analysis module is used for analyzing the key sector to obtain the position of a key guide sector;

the characteristic acquisition module is used for taking the position of the key sector and the position of the key guide sector as key data characteristics.

8. The data storage management device of claim 6, wherein the data determination unit comprises a data analysis module and an address determination module;

the data analysis module is used for analyzing the write data and obtaining the LBA of the write data;

the address judgment module is configured to judge whether the LBA of the write data is located in the key sector position or the key boot sector position.

9. A computer device, characterized in that the computer device comprises a memory on which a computer program is stored and a processor which, when executing the computer program, implements the data storage management method according to any one of claims 1 to 5.

10. A storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, can implement the data storage management method according to any one of claims 1 to 5.