CN112817912B

CN112817912B - File management method, device, computer equipment and storage medium

Info

Publication number: CN112817912B
Application number: CN202110193252.0A
Authority: CN
Inventors: 罗国强
Original assignee: Ping An Technology Shenzhen Co Ltd
Current assignee: Ping An Technology Shenzhen Co Ltd
Priority date: 2021-02-20
Filing date: 2021-02-20
Publication date: 2023-05-26
Anticipated expiration: 2041-02-20
Also published as: CN112817912A

Abstract

The application relates to the field of data processing, and aims to automatically delete or restore a target file by receiving a file operation request determined by a life cycle server according to life cycle configuration information and storage space information, so that the efficiency and convenience of file management are improved. And more particularly, to a file management method, apparatus, computer device, and storage medium, the method comprising: determining storage space information and life cycle configuration information of a storage space; the life cycle configuration information and the storage space information are sent to the life cycle server, so that the life cycle server determines a target file and generates a file operation request of the target file according to the life cycle configuration information and the storage space information based on the key value database; and receiving a file operation request sent by the life cycle server, and deleting or restoring the target file according to the operation type corresponding to the file operation request. In addition, the present application relates to blockchain technology in which key-values can be stored in a database.

Description

File management method, device, computer equipment and storage medium

Technical Field

The present disclosure relates to the field of data processing, and in particular, to a file management method, apparatus, computer device, and storage medium.

Background

In many businesses, the business files of users often have certain business heat, for example, business files for opening accounts or applying insurance and settling claims are mostly frequently used in a week and a month; when the service warmth is exceeded, these service files will be rarely used, but must be saved due to regulatory requirements.

When saving the business file, the user generally stores the business file into a standard storage cluster; after a period of time, the service files need to be deleted or restored to the archive storage cluster by the user. When deleting or unloading the service file, complex processing operation causes greater processing difficulty, so that the efficiency and convenience of managing the service file by the user are reduced.

Therefore, how to improve the efficiency and convenience of managing files is a need for solving the problem.

Disclosure of Invention

The application provides a file management method, a file management device, computer equipment and a storage medium, which realize automatic deletion or transfer of a target file without manual operation by receiving a file operation request determined by a life cycle server according to life cycle configuration information and storage space information, and improve the efficiency and convenience of file management.

In a first aspect, the present application provides a file management method, including:

determining storage space information corresponding to a storage space, wherein the storage space is a container for storing files;

determining life cycle configuration information corresponding to the storage space according to the detected life cycle configuration operation on the storage space;

the life cycle configuration information and the storage space information are sent to a life cycle server, so that the life cycle server determines a target file to be processed according to the life cycle configuration information and the storage space information based on a key value database containing at least one file attribute information and generates a file operation request corresponding to the target file;

and receiving the file operation request sent by the life cycle server, and deleting or saving the target file according to the operation type corresponding to the file operation request.

In a second aspect, the present application further provides a file management apparatus, including:

the storage space information determining module is used for determining storage space information corresponding to a storage space, wherein the storage space is a container for storing files;

The life cycle determining module is used for determining life cycle configuration information corresponding to the storage space according to the detected life cycle configuration operation on the storage space;

the information sending module is used for sending the life cycle configuration information and the storage space information to a life cycle server, so that the life cycle server determines a target file to be processed according to the life cycle configuration information and the storage space information based on a key value database containing at least one file attribute information and generates a file operation request corresponding to the target file;

and the file processing module is used for receiving the file operation request sent by the life cycle server and deleting or restoring the target file according to the operation type corresponding to the file operation request.

In a third aspect, the present application also provides a computer device comprising a memory and a processor;

the memory is used for storing a computer program; the processor is configured to execute the computer program and implement the file management method as described above when the computer program is executed.

In a fourth aspect, the present application also provides a computer readable storage medium storing a computer program which, when executed by a processor, causes the processor to implement a file management method as described above.

The application discloses a file management method, a device, computer equipment and a storage medium, wherein the life cycle configuration information and the storage space information corresponding to a storage space are determined and can be sent to a life cycle server, the life cycle server determines a target file to be processed according to the life cycle configuration information and the storage space information based on a key value database containing at least one file attribute information, and generates a file operation request corresponding to the target file; by receiving the file operation request sent by the life cycle server, the target file can be automatically deleted or transferred according to the operation type corresponding to the file operation request, manual operation is not needed, and the efficiency and convenience of file management are improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic flow chart of a file management method provided in an embodiment of the present application;

FIG. 2 is a schematic flow chart of a sub-step of uploading a file provided in an embodiment of the present application;

FIG. 3 is a schematic diagram of a relationship between a space group and a storage cluster provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of interaction with a database with key values according to an embodiment of the present application;

FIG. 5 is a schematic diagram of sending a file operation request to a storage application server according to an embodiment of the present application;

FIG. 6 is a schematic flow chart of sub-steps for deleting a target file provided by an embodiment of the present application;

FIG. 7 is a schematic flow chart of sub-steps for transferring a target file provided by an embodiment of the present application;

FIG. 8 is a schematic diagram of uploading a target file in a standard storage cluster to an archive storage cluster according to an embodiment of the present application;

FIG. 9 is a schematic diagram of updating file attribute information in a database according to an embodiment of the present application;

FIG. 10 is a schematic flow chart of a sub-step of determining whether a restored target file is changed according to an embodiment of the present application;

FIG. 11 is a schematic block diagram of a document management apparatus provided in an embodiment of the present application;

Fig. 12 is a schematic block diagram of a computer device according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

The flow diagrams depicted in the figures are merely illustrative and not necessarily all of the elements and operations/steps are included or performed in the order described. For example, some operations/steps may be further divided, combined, or partially combined, so that the order of actual execution may be changed according to actual situations.

It is to be understood that the terminology used in the description of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this specification 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 also be understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.

The embodiment of the application provides a file management method, a file management device, computer equipment and a storage medium. The file management method can be applied to the storage application server, and can automatically delete or restore the target file by receiving the file operation request determined by the life cycle server according to the life cycle configuration information and the storage space information, so that manual operation is not needed, and the efficiency and convenience of file management are improved.

The storage application server and the life cycle server can be independent servers or server clusters.

Some embodiments of the present application are described in detail below with reference to the accompanying drawings. The following embodiments and features of the embodiments may be combined with each other without conflict. As shown in fig. 1, the file management method includes steps S10 to S40.

Step S10, determining storage space information corresponding to a storage space, wherein the storage space is a container for storing files.

In the embodiment of the present application, it will be described how to delete or restore a file according to its lifecycle implementation Based on an Object-Based Storage (OBS). It should be noted that, the object storage can be used for storing massive files such as pictures, audio and video, logs and the like; various terminal devices, web site programs, mobile applications may write or read data directly to the OBS.

By way of example, in an architecture of object storage, it may include, but is not limited to, a storage application server, a lifecycle server, a key-value pair database, a storage cluster, and so forth. Wherein, the key value pair database refers to a TiKV database. It should be noted that the TiKV database is an open-source distributed transaction Key-Value database; tiKV is a non-relational database, the problem that massive data cannot be cached by a relational database and a redis database can be solved, and performance is free from difference on the basis of storing trillion and trillion data. The cluster storage is to aggregate storage spaces in a plurality of storage devices into a storage pool which can provide a unified access interface and a management interface for an application server, and the application can transparently access and utilize the disks on all the storage devices through the access interface, so that the performance and the disk utilization rate of the storage devices can be fully exerted.

It should be noted that a storage space is a container in which objects (objects) of a user are stored, and all objects must be affiliated to a certain storage space. The storage space has various configuration attributes including regions, access rights, storage types and the like; the user can create different types of storage spaces to store different data according to actual requirements. The object in the storage space may refer to a file in an embodiment of the present application.

In some embodiments, determining the storage space information corresponding to the storage space may include: receiving a storage space request, wherein the storage space request comprises authority information corresponding to a storage space; and when the authority information passes the verification, creating a storage space and determining storage space information corresponding to the storage space.

In embodiments of the present application, a user may initiate a storage space request through an SDK toolkit (Software Development Kit, software development toolkit) provided by the object store or a management page of the storage application server. It will be appreciated that a user may need to request a memory space for storing a file before uploading the file.

Illustratively, the storage space request includes rights information corresponding to the storage space. It should be noted that the permission information may be automatically generated when the storage space request is initiated, and is used to indicate validity of the storage space request and whether the permission of requesting the storage space is provided.

For example, the HMAC-SHA256 algorithm may be used to verify the rights information. Note that HMAC (Hash-based Message Authentication Code, hashed message authentication code) is a key-based method of verifying message integrity. The HMAC algorithm uses hash operations to generate a message digest as output with a key and a message as input. It is understood that the HMAC algorithm that generates the hash value using the SHA-256 algorithm is referred to as the HMAC-SHA256 algorithm.

Illustratively, when a user applies for storage space through an SDK toolkit or a management page, a public key and a private key may be generated according to an asymmetric encryption algorithm; then, the user encrypts the authority information based on an HMAC-SHA256 algorithm according to the public key to obtain encrypted information; the rights information and the encryption information are then sent to a storage application server, which may decrypt and verify the encryption information based on the HMAC-SHA256 algorithm, based on the private key. The specific decryption and authentication process is not limited herein. By encrypting the rights information, the rights information can be prevented from being tampered or stolen.

For example, after the rights information is verified, a storage space (socket) for storing the file may be created and storage space information of the storage space may be determined. For example, a memory space name. Wherein the name of each memory space is globally unique.

In some embodiments, after the authority information passes the verification, the storage space information corresponding to the storage space may also be returned to the user. So that the user can upload files according to the storage space information.

By receiving the storage space request, the authority information in the storage space request can be checked, the storage space can be created, and the storage space information can be obtained.

Step S20, according to the detected life cycle configuration operation on the storage space, the life cycle configuration information corresponding to the storage space is determined.

It should be noted that, after the storage application server creates the storage space, the user may configure the lifecycle configuration information for each storage space. Wherein, the life cycle configuration information only acts on all files in the corresponding storage space.

It will be appreciated that lifecycle configuration information is used to represent the lifecycle of a file. For example, when the life cycle of a file satisfies a preset condition, the file is deleted or restored.

For example, when a user needs to delete a file in a storage space by configuring a lifecycle, the lifecycle configuration information may include: files are deleted before a preset preservation period, files with preset prefixes are deleted before a preset preservation period, and the like. The preset preservation period may include, but is not limited to, 1 month, 3 months, 6 months, etc. The preset prefix may include, but is not limited to, a test prefix, a stg prefix, and the like.

For example, when a user needs to restore files in a storage space by configuring a lifecycle, the lifecycle configuration information may include: file transfer before preset preservation time, file transfer before preset prefix, etc. The transfer refers to migration of files in the standard storage or the performance type storage to the archive storage.

In some embodiments, the lifecycle configuration information may also be persisted PG (PostgreSQL) in the database after the corresponding lifecycle configuration information for the storage space is determined.

Persistence refers to a mechanism for saving data (e.g., objects in memory) to a permanently-storable storage device. Persistence can be applied to scenarios where objects in memory are stored in databases, disk files, and XML data files.

By determining the lifecycle configuration information corresponding to the storage space according to the detected lifecycle configuration operation, the subsequent lifecycle server can manage the files in the storage space according to the lifecycle configuration information.

And step S30, the life cycle configuration information and the storage space information are sent to a life cycle server, so that the life cycle server determines a target file to be processed according to the life cycle configuration information and the storage space information based on a key value database containing at least one file attribute information, and generates a file operation request corresponding to the target file.

It should be noted that, before sending the lifecycle configuration information and the storage space information to the lifecycle server, the user may upload the file to the storage space. For example, after the storage application server creates the storage space, the user may upload the file to be uploaded to the storage cluster corresponding to the storage space. It will be appreciated that storage space is a logical concept and that files are actually stored in the storage clusters.

Referring to fig. 2, fig. 2 is a schematic flowchart of a sub-step of uploading a file provided in an embodiment of the present application, and may specifically include the following steps S301 to S304.

Step S301, a file upload request is received, where the file upload request includes uploading file and storage space information.

For example, after obtaining the storage space information corresponding to the storage space, the user may generate a file upload request according to the storage space information. For example, a user initiates a file upload request through an SDK toolkit or a management page to upload an upload file into a storage cluster.

And step S302, determining a target storage cluster of the uploaded file according to the storage space information after the storage space information passes the verification.

In this embodiment of the present application, after receiving the file upload request, the storage application server may verify the storage space information in the file upload request. For example, the HMAC-SHA256 algorithm may be used to verify the memory space information. The specific verification process is not limited herein. By checking the storage space information in the file upload request, it can be determined whether the file upload request is legal.

In some embodiments, when the storage space information passes the verification, a target storage cluster of the uploaded file is determined according to the storage space information. Wherein the storage space information may include a storage space name.

For example, the target storage cluster of the uploading file is determined according to the storage space information, and the target space group corresponding to the uploading file can be determined according to the storage space name in the storage space information based on a preset corresponding relation between the storage space name and the space group; and determining the target storage cluster of the uploading file according to the weight information corresponding to each storage cluster in the target space group.

It should be noted that there is a virtual concept of the Zonecroup (space group) on the storage application server, where a mapping relationship exists between the Zonecroup and the socket (storage space), and the mapping relationship is stored in the PG database. Meanwhile, the mapping relation between Zonecroup and the storage clusters is also stored in the PG database. And loading the two mapping relations into a cache when the storage application server is started, then, periodically inquiring the mapping relation in the PG database, and updating the cache information of the storage application server.

Referring to fig. 3, fig. 3 is a schematic diagram illustrating a relationship between a space group and a storage cluster according to an embodiment of the present application. As shown in fig. 3, a storage space corresponds to a Zonegroup, where the Zonegroup and storage cluster are many-to-many, e.g., a Zonegroup may have one or more storage clusters.

In the embodiment of the application, when a user uploads a file, a storage application server only needs to determine a target space group according to the mapping relation between the socket-Zonecroup; and then determining the target storage cluster of the uploaded file according to the weight information corresponding to each storage cluster in the target space group. Illustratively, the weight information corresponding to each storage cluster in the target space group is shown in table 1.

TABLE 1

Zoegroup name	Storing cluster numbers	Write weights
			zn1	$001	100
zn1	$002	80
			zn1	$003	80

For example, the target storage cluster may be determined according to the weight probability corresponding to each storage cluster. The weight probability is defined as follows:

in table 1, the weight probability for storage cluster $001 is 38.46%, the weight probability for storage cluster $002 is 30.77%, and the weight probability for storage cluster $003 is 30.77%. For example, the storage cluster with the highest weight probability may be determined as the target storage cluster of the uploading file.

The target storage cluster for uploading the file can be conveniently and rapidly determined according to the storage space information, and the efficiency of uploading the file is improved.

And step S303, storing the uploading file to the target storage cluster.

For example, after determining the target storage cluster, the upload file may be stored into the target storage cluster.

And step S304, determining file attribute information of the uploaded file in the target storage cluster, and storing the file attribute information into the key value database in a key value pair mode.

Illustratively, file attribute information of the uploaded file is determined. Such as the type, size, name, check value, etc. of the uploaded file. The check value of the uploaded file may be generated by the HMAC-MD5 algorithm, but may be any other algorithm, which is not limited herein. It will be appreciated that the HMAC algorithm that generates the message digest using the MD5 algorithm is referred to as the HMAC-MD5 algorithm.

Illustratively, after determining the file attribute information of the uploaded file, the file attribute information is stored to the key-value database in the form of key-value pairs.

By determining the file attribute information of the uploaded file and storing the file attribute information in the form of key value pairs to the key value database, the file can be checked according to the file attribute information in the key value database when the file is deleted or transferred later.

In some embodiments, the lifecycle configuration information and the storage space information may be sent to the lifecycle server, so that the lifecycle server determines a target file to be processed according to the lifecycle configuration information and the storage space information and generates a file operation request corresponding to the target file based on the key value containing at least one file attribute information.

For example, if the lifecycle server is restarted, the lifecycle server may actively request the lifecycle configuration information and the storage space information from the storage application server.

In the embodiment of the application, after receiving the lifecycle configuration information and the storage space information, the lifecycle server may start a timing task, determine a target file to be processed according to the storage space information and the lifecycle configuration information, and generate a file operation.

In some embodiments, the lifecycle server determines a target file to be processed and generates a file operation according to the storage space information and the lifecycle configuration information, which may include: determining corresponding file attribute information according to a storage space name in the storage space information based on a key value database containing at least one file attribute information, wherein the file attribute information at least comprises the storage space name; and determining the file corresponding to the file attribute information as a target file to be processed according to the life cycle configuration information and the current time.

Referring to fig. 4, fig. 4 is a schematic diagram illustrating interaction with a database by a key according to an embodiment of the present application. As shown in fig. 4, the key value stores a plurality of file attribute information in the database. After uploading the file to the storage cluster, the storage application server may store the file attribute information of the file in the key-value pair form into the key-value database.

In some embodiments, to further ensure privacy and security of the database with the key, the database may also be stored in a blockchain node.

By way of example, the file attribute information may be expressed as: key, yyyymmddhhmiss/socket/object; value $ XXX|fileinfo; wherein yyyymmddhhmiss represents time of year, month, day, minute, and second; socket represents a storage space name; object represents the identification number of the file; XXX represents the name of a storage cluster; fileinfo indicates the type, size, name, check value, etc. of the file. For example, file attribute information: key 20190106100811/btest/ofile1; value $006|png_4121232_name1. Wherein btest is the storage space name; the ofile1 is the identification number of the file and is used for identifying different files.

For example, when the storage space name is btest, the lifecycle server may query the file attribute information corresponding to the storage space name btest in the database for the key value. For example, the inquired file attribute information is key 20190106100811/btest/file 1; value $006|png_4121232_name1.

By determining the corresponding file attribute information according to the storage space names in the storage space information based on the key values and the database, the life cycle server improves the information inquiry performance and further improves the file management efficiency.

In some embodiments, the lifecycle server may determine the file corresponding to the file attribute information as the target file to be processed according to the lifecycle configuration information and the current time.

For example, if the lifecycle configuration information is "files are deleted before 1 month", all files before 1 month may be determined as target files according to the current time and the time in the file attribute information. For example, if the current time is 2021, 1, 7, then all files before 2020, 12, 7 are determined to be target files.

For example, if the life cycle configuration information is "the file of the prefix test is deleted before 1 month", all files of the prefix test before 1 month may be determined as the target files according to the current time and the time in the file attribute information.

By determining the target file corresponding to the file attribute information according to the life cycle configuration information and the current time, the target file conforming to the preset life cycle can be determined conveniently.

In some embodiments, after determining the target file to be processed, the lifecycle server may generate a file operation request corresponding to the target file.

For example, before generating the file operation request corresponding to the target file, the method may further include: and determining operation type information in the life cycle configuration information, and determining the operation type corresponding to the target file according to the operation type information.

For example, when determining the operation type information in the life cycle configuration information, word segmentation processing can be performed on the life cycle configuration information based on a preset word segmentation model to obtain a plurality of phrases corresponding to the life cycle configuration information; and then, based on a target phrase in a preset phrase template, matching a plurality of phrases corresponding to the life cycle configuration information, and determining the successfully matched phrases as operation type information.

The preset word segmentation model may include, but is not limited to, a BI_LSTM-CRF neural network model, a hidden Markov model, a support vector machine model, a dictionary-based word segmentation model, and the like.

For example, the target phrase in the preset phrase template may include "delete" and "dump". The operation type information may be "delete" and "dump".

Illustratively, the operation type corresponding to the target file is determined according to the operation type information. For example, if the operation type information is "delete", it may be determined that the operation type corresponding to the target file is a delete operation; if the operation type information is "transfer" then it can be determined that the operation type corresponding to the target file is a transfer operation.

In some embodiments, when a file operation request corresponding to the target file is generated, an operation type may be added to the file operation request.

Referring to fig. 5, fig. 5 is a schematic diagram of sending a file operation request to a storage application server according to an embodiment of the present application. As shown in fig. 5, after generating a file operation request corresponding to the target file, the lifecycle server may send the file operation request to the storage application server.

The life cycle server generates a file operation request corresponding to the target file according to the file attribute information of the operation type corresponding to the target file, and can send the file operation request to the storage application server, so that the storage application server deletes or saves the target file according to the operation type in the file operation request, and the efficiency and convenience of file management are improved.

And S40, receiving the file operation request sent by the life cycle server, and deleting or restoring the target file according to the operation type corresponding to the file operation request.

In some embodiments, before deleting or restoring the target file according to the operation type corresponding to the file operation request, the method may further include: determining first file attribute information corresponding to a target file in a storage cluster; determining locking information according to the storage space information and the first file attribute information; and locking the file request according to the locking information, wherein the file request comprises a newly added file uploading request or other file operation requests.

It will be appreciated that the target file is stored in the storage cluster; the first file attribute information refers to file attribute information corresponding to the target file in the storage cluster.

Before deleting or restoring the target file, if the user uploads a file with the same identification number as the target file and the file is stored in the storage cluster corresponding to the target file, the uploaded file is simultaneously deleted or restored when the target file is deleted or restored. Since the uploaded file does not meet the requirement of deletion or transfer, misoperation can occur. In order to avoid misoperation, when deleting or transferring the target file according to the file operation request, the newly added file request needs to be locked until the current file operation request is completed.

By determining the locking information according to the storage space information of the target file and the first file attribute information and locking the newly added file uploading request or the file operation request according to the locking information, misoperation on files which do not meet the deleting or transferring requirements can be avoided.

Illustratively, the first file attribute information includes an identification number of the target file. In some embodiments, when determining the locking information according to the storage space information of the target file and the first file attribute information, the storage space name and the identification number may be encrypted according to an HMAC-MD5 algorithm, and the obtained encrypted information is determined as the locking information. Of course, the storage space name and the identification number may be encrypted according to other algorithms, which is not limited herein. It will be appreciated that the storage space names corresponding to different storage spaces are unique, but the same identification number may appear in different storage spaces, so that by combining the storage space names with the identification numbers, the obtained locking information can determine a unique target file.

For example, the newly added file upload request or file operation request may be locked according to the locking information, for example, blocking waiting is performed on the newly added file upload request or file operation request, and the locking is released after the current file operation request is completed.

In the embodiment of the application, after receiving the file operation request sent by the lifecycle server, the operation type corresponding to the file operation request may be determined. The operation type may be deletion or transfer.

The target file is deleted or transferred according to the operation type corresponding to the file operation request, so that the target file is automatically deleted or transferred without manual processing, and the efficiency and convenience of file management are improved.

Referring to fig. 6, fig. 6 is a schematic flowchart of a sub-step of deleting a target file provided in an embodiment of the present application, which may specifically include the following steps S401 to S403.

And S401, when the operation type is deletion, determining a first check value corresponding to the target file according to the first file attribute information.

For example, when the operation type is deletion, a first check value corresponding to the target file may be determined according to the first file attribute information. Wherein the first file attribute information includes a first check value. In the embodiment of the present application, the first check value may be calculated based on the HMAC-MD5 algorithm for the target file.

Step S402, determining a second check value corresponding to the target file according to the second file attribute information of the target file in the key value pair database.

It should be noted that, after the target file is uploaded to the storage cluster, the attribute information of the target file may be stored in the key value database. Accordingly, the file attribute information of the target file in the key value database can be determined as the second file attribute information. Since the second file attribute information includes the check value corresponding to the target file, the check value in the second file attribute information can be determined as the second check value.

Step S403, comparing the second check value with the first check value, and if the second check value is the same as the first check value, deleting the target file.

Illustratively, the second check value is compared to the first check value to determine whether the target file in the storage cluster has changed.

By determining a first check value corresponding to the target file, determining a second check value of the target file in the database in the key value, and comparing the second check value with the first check value, whether the target file changes can be determined.

For example, if the second check value is the same as the first check value, it indicates that the target file is not changed after being uploaded to the storage cluster, so that the target file may be deleted. After deleting the target file, releasing the lock for the newly added file uploading request or file operation request.

In some embodiments, after comparing the second check value with the first check value, it may further include: and if the second check value is different from the first check value, updating the second file attribute information in the database according to the key value according to the first file attribute information.

If the second check value is different from the first check value, the target file may be updated after the target file is uploaded to the storage cluster, and thus the target file cannot be deleted.

In this embodiment of the present application, after the target file is updated, the key value needs to be updated to the corresponding second file attribute information in the database according to the first file attribute information corresponding to the target file currently.

Illustratively, the first file attribute information may be expressed as: key 20210106100811/btest/ofile1; value $006|jpg_5468421_name2_etag1. The second file attribute information of the target file in the key value pair database can be expressed as: key 20190106100811/btest/ofile1; value $006|png_4121232_name1_etag2. Wherein etag1 represents a first check value; etag2 represents a second check value. The key value can be used for obtaining second file attribute information 'key: 20190106100811/btest/ofile 1' in the database; value $006|png_4121232_name1_etag2 "replaced by" key 20210106100811/btest/ofile1; value $ 006|jpg_5468421_name2_etag1).

The key value is updated to the corresponding second file attribute information in the database according to the first file attribute information of the target file, so that the second file attribute information stored in the database and the first file attribute information in the storage cluster can be kept consistent by the key value.

In the embodiment of the application, after updating the second file attribute information in the database according to the first file attribute information of the target file, the lock may be released for the newly added file upload request or file operation request.

Referring to fig. 7, fig. 7 is a schematic flowchart of a sub-step of transferring a target file according to an embodiment of the present application, which may specifically include the following steps S404 to S406.

And step S404, when the operation type is the transfer, determining a first storage time corresponding to the target file in the standard storage cluster according to the first file attribute information.

In the embodiment of the application, when storing the file, the file may be stored according to a storage type of standard storage. In the object store OBS, the storage type may include standard storage, low frequency access, archive storage, and archive storage.

It can be understood that the storage type is a file stored in a standard way, and the file is correspondingly stored in a standard storage cluster.

Illustratively, the first file attribute information includes a first storage time. The first storage time refers to a time when the target file is stored in the standard storage cluster, and may be stored in the standard storage cluster.

Step S405, determining a second storage time corresponding to the target file according to the second file attribute information of the target file in the key value pair database.

For example, second file attribute information of the target file in the key value database may be acquired, and then a second storage time may be determined according to the second file attribute information. It should be noted that, the second storage time refers to a time when the target file is stored in the standard storage cluster, and after the target file is stored in the standard storage cluster, the second storage time may be stored in the key value database.

Step S406, comparing the second storage time with the first storage time, and if the second storage time is the same as the first storage time, uploading the target file in the standard storage cluster to an archive storage cluster.

Exemplary, if the first file attribute information in the standard storage cluster is key 20210106100811/btest/ofile1; value: g00a|jpg_5468421_name2_etag1, and key value is key:20210106100811/btest/ofile1 for the second file attribute information in the database; value: g00a|jpg_5468421_name2_etag1, then the second storage time can be determined to be the same as the first storage time.

Referring to fig. 8, fig. 8 is a schematic diagram of uploading a target file in a standard storage cluster to an archive storage cluster according to an embodiment of the present application. As shown in fig. 8, if the second storage time is the same as the first storage time, the target file in the standard storage cluster is uploaded to the archive storage cluster. The specific uploading process is not limited herein.

By determining the first storage time of the target file corresponding to the standard storage cluster and the second storage time of the target file in the database according to the key value, and comparing the second storage time with the first storage time, whether the target file is updated or not can be determined.

In some embodiments, after comparing the second storage time with the first storage time, it may further include: and if the second storage time is different from the first storage time, updating the second file attribute information in the database according to the key value according to the first file attribute information. Exemplary, as shown in fig. 9, fig. 9 is a schematic diagram of updating file attribute information in a database according to a key value according to file attribute information provided in an embodiment of the present application.

For example, if the second storage time is 20210106100811 and the first storage time is 20210106110812, it may be determined that the second storage time is not the same as the first storage time. At this time, first file attribute information corresponding to the target file in the standard storage cluster, for example, key 20210106100811/btest/file 1; value: g00a|jpg_5468421_name2_etag1; then, the key value is used for obtaining second file attribute information key 20210106110812/btest/ofile1 in the database; value, G00 A|jpg_5468421_name2_etag2.

In this embodiment of the present application, after uploading the target file in the standard storage cluster to the archive storage cluster, it is further required to determine whether the target files before and after the transfer are the same file. Thus, the target file can be prevented from being tampered in the process of transferring.

Referring to fig. 10, fig. 10 is a schematic flowchart of a sub-step of determining whether a restored target file is changed according to an embodiment of the present application, and may specifically include the following steps S407 to S409.

Step S407, determining a third check value corresponding to the target file in the archive storage cluster.

Illustratively, a third check value corresponding to the target file in the archive storage cluster is calculated according to the HMAC-MD5 algorithm. Wherein the third check value may be denoted etag3.

And step 408, deleting the target file in the archive storage cluster if the first check value is different from the third check value.

It should be noted that, when the first check value etag1 is different from the third check value etag3, it is noted that the target file may be tampered during the archiving process, and therefore, the target file in the archive storage cluster needs to be deleted.

And step 409, if the first check value is the same as the third check value, determining third file attribute information corresponding to the target file in the archive storage cluster, and updating the second file attribute information in the database according to the key value according to the third file attribute information.

Illustratively, when the first check value etag1 is the same as the third check value etag3, it is stated that the target file in the standard storage cluster remains consistent with the target file in the archive storage cluster. At this time, the database needs to be updated according to the third file attribute information corresponding to the archive storage cluster of the target file, as shown in fig. 10.

For example, determining third file attribute information corresponding to the target file in the archive storage cluster, for example, key 20210106100811/btest/file 1; value: g00a|jpg_5468421_name2_etag3; the file attribute information of the target file in the key value database is key 20210106100811/btest/ofile1; value: G00A|jpg_5468421_name2_etag2. For example, 20210106100811/btest/ofile1 may be selected according to the third file attribute information key; value: G00A|jpg_5468421_Name2_etag3 key-value pair second file attribute information key in database: 20210106100811/btest/ofile1; value: G00A|jpg_5468421_name2_etag2.

In some embodiments, when the first check value is determined to be the same as the third check value, the target file in the standard storage cluster is deleted.

In some embodiments, after updating the second file attribute information in the database according to the third file attribute information, the lock may also be released for the newly added file upload request or file operation request.

And comparing the first check value corresponding to the standard storage cluster of the target file with the third check value corresponding to the archive storage cluster of the target file, so as to determine whether the restored target file is changed.

According to the file management method provided by the embodiment, the authority information in the storage space request can be checked by receiving the storage space request, so that the storage space is created and the storage space information is obtained; the follow-up life cycle server can manage files in the storage space according to the life cycle configuration information by determining the life cycle configuration information corresponding to the storage space according to the detected life cycle configuration operation; the target storage cluster for uploading the file can be conveniently and rapidly determined according to the storage space information, so that the efficiency of uploading the file is improved; the file attribute information of the uploaded file is determined, and the file attribute information is stored in the key value database in the form of key value pairs, so that the file can be checked according to the file attribute information in the key value database when the file is deleted or transferred later; by determining locking information according to the storage space information of the target file and the first file attribute information and locking the newly added file uploading request or the file operation request according to the locking information, misoperation on files which do not meet the deletion or transfer requirements can be avoided; the target file is deleted or transferred according to the operation type corresponding to the file operation request, so that the target file is automatically deleted or transferred without manual processing, and the efficiency and convenience of file management are improved; whether the target file changes or not can be determined by determining a first check value corresponding to the target file and a second check value of the target file in the database in the key value and comparing the second check value with the first check value; updating the corresponding second file attribute information in the database by the key value according to the first file attribute information of the target file, so that the second file attribute information stored in the database by the key value is consistent with the first file attribute information in the storage cluster; determining whether the target file is updated or not by determining a first storage time corresponding to the target file in the standard storage cluster and a second storage time of the target file in the database according to the key value and comparing the second storage time with the first storage time; and comparing the first check value corresponding to the standard storage cluster of the target file with the third check value corresponding to the archive storage cluster of the target file, so as to determine whether the restored target file is changed.

Referring to fig. 11, fig. 11 is a schematic block diagram of a file management apparatus 1000 according to an embodiment of the present application, where the file management apparatus is configured to execute a file management method corresponding to a storage application server. Wherein the file management apparatus may be configured in a storage application server.

As shown in fig. 11, the file management apparatus 1000 includes: a storage space information determination module 1001, a life cycle determination module 1002, an information transmission module 1003, and a file processing module 1004.

The storage space information determining module 1001 is configured to determine storage space information corresponding to a storage space, where the storage space is a container for storing a file.

The lifecycle determining module 1002 is configured to determine lifecycle configuration information corresponding to the storage space according to the detected lifecycle configuration operation on the storage space.

And an information sending module 1003, configured to send the lifecycle configuration information and the storage space information to a lifecycle server, so that the lifecycle server determines a target file to be processed according to the lifecycle configuration information and the storage space information and generates a file operation request corresponding to the target file based on a key value database containing at least one file attribute information.

The file processing module 1004 is configured to receive the file operation request sent by the lifecycle server, and delete or restore the target file according to an operation type corresponding to the file operation request.

It should be noted that, for convenience and brevity of description, the specific working process of the apparatus and each module described above may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.

The apparatus described above may be implemented in the form of a computer program which is executable on a computer device as shown in fig. 12.

Referring to fig. 12, fig. 12 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device may be a server or a terminal.

Referring to fig. 12, the computer device includes a processor and a memory connected by a system bus, wherein the memory may include a non-volatile storage medium and an internal memory.

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

The internal memory provides an environment for the execution of a computer program in a non-volatile storage medium that, when executed by a processor, causes the processor to perform any of a number of file management methods.

It should be appreciated that the processor may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field-programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. Wherein the general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

Wherein in one embodiment the processor is configured to run a computer program stored in the memory to implement the steps of:

determining storage space information corresponding to a storage space, wherein the storage space is a container for storing files; determining life cycle configuration information corresponding to the storage space according to the detected life cycle configuration operation on the storage space; the life cycle configuration information and the storage space information are sent to a life cycle server, so that the life cycle server determines a target file to be processed according to the life cycle configuration information and the storage space information based on a key value database containing at least one file attribute information and generates a file operation request corresponding to the target file; and receiving the file operation request sent by the life cycle server, and deleting or saving the target file according to the operation type corresponding to the file operation request.

In one embodiment, the processor is configured to, in implementing determining storage space information corresponding to the storage space, implement:

receiving a storage space request, wherein the storage space request comprises authority information corresponding to the storage space; and when the authority information passes the verification, creating the storage space and determining storage space information corresponding to the storage space.

In one embodiment, the processor is further configured to, prior to implementing the sending of the lifecycle configuration information and the storage space information to a lifecycle server, implement:

receiving a file uploading request, wherein the file uploading request comprises uploading file and storage space information; when the storage space information passes the verification, determining a target storage cluster of the uploaded file according to the storage space information; storing the uploading file to the target storage cluster; and determining file attribute information of the uploaded file in the target storage cluster, and storing the file attribute information into the key value database in the form of key value pairs.

In one embodiment, before implementing deleting or transferring the target file according to the operation type corresponding to the file operation request, the processor is further configured to implement:

Determining first file attribute information corresponding to the target file in a storage cluster; determining locking information according to the storage space information and the first file attribute information; and locking the file request according to the locking information, wherein the file request comprises a newly added file uploading request or other file operation requests.

In one embodiment, the first file attribute information includes a first check value and a first storage time, and the storage cluster includes a standard storage cluster; the processor is used for deleting or saving the target file according to the operation type corresponding to the file operation request, and is used for realizing the following steps:

when the operation type is deleting, determining a first check value corresponding to the target file according to the first file attribute information; determining a second check value corresponding to the target file according to second file attribute information of the target file in the key value pair database; comparing the second check value with the first check value, and deleting the target file if the second check value is the same as the first check value; when the operation type is the transfer, determining a first storage time corresponding to the target file in the standard storage cluster according to the first file attribute information; determining a second storage time corresponding to the target file according to the second file attribute information of the target file in the key value pair database; and comparing the second storage time with the first storage time, and uploading the target file in the standard storage cluster to an archiving storage cluster if the second storage time is the same as the first storage time.

In one embodiment, the processor, after implementing comparing the second check value with the first check value, is further configured to implement:

and if the second check value is different from the first check value, updating the second file attribute information in the database according to the key value according to the first file attribute information.

In one embodiment, the processor, after implementing comparing the second storage time with the first storage time, is further configured to implement:

and if the second storage time is different from the first storage time, updating the second file attribute information in the database according to the key value according to the first file attribute information.

In one embodiment, the processor, after implementing uploading the target file in the standard storage cluster into an archive storage cluster, is further to implement:

determining a third check value corresponding to the target file in the archiving storage cluster; if the first check value is different from the third check value, deleting the target file in the archiving storage cluster; and if the first check value is the same as the third check value, determining third file attribute information corresponding to the target file in the archive storage cluster, and updating the second file attribute information in the database according to the key value according to the third file attribute information.

Embodiments of the present application further provide a computer readable storage medium, where the computer readable storage medium stores a computer program, where the computer program includes program instructions, and the processor executes the program instructions to implement any one of the file management methods provided in the embodiments of the present application.

The computer readable storage medium may be an internal storage unit of the computer device according to the foregoing embodiment, for example, a hard disk or a memory of the computer device. The computer readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a secure digital Card (Secure Digital Card, SD Card), a Flash memory Card (Flash Card), etc. which are provided on the computer device.

Further, the computer-readable storage medium may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created from the use of blockchain nodes, and the like.

The blockchain referred to in the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm and the like. The Blockchain (Blockchain), which is essentially a decentralised database, is a string of data blocks that are generated by cryptographic means in association, each data block containing a batch of information of network transactions for verifying the validity of the information (anti-counterfeiting) and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, an application services layer, and the like.

While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of file management comprising:

determining first file attribute information corresponding to the target file in a storage cluster, wherein the first file attribute information comprises a first check value and a first storage time, and the storage cluster comprises a standard storage cluster;

Receiving the file operation request sent by the life cycle server, and deleting or saving the target file according to the operation type corresponding to the file operation request;

when the operation type is deleting, determining a first check value corresponding to the target file according to the first file attribute information; determining a second check value corresponding to the target file according to second file attribute information of the target file in the key value pair database; comparing the second check value with the first check value, and deleting the target file if the second check value is the same as the first check value; or (b)

When the operation type is the transfer, determining a first storage time corresponding to the target file in the standard storage cluster according to the first file attribute information; determining a second storage time corresponding to the target file according to the second file attribute information of the target file in the key value pair database; and comparing the second storage time with the first storage time, and uploading the target file in the standard storage cluster to an archiving storage cluster if the second storage time is the same as the first storage time.

2. The method for managing files according to claim 1, wherein the determining storage space information corresponding to the storage space includes:

receiving a storage space request, wherein the storage space request comprises authority information corresponding to the storage space;

and when the authority information passes the verification, creating the storage space and determining storage space information corresponding to the storage space.

3. The file management method according to claim 1, wherein before said sending said lifecycle configuration information and said storage space information to a lifecycle server, further comprising:

receiving a file uploading request, wherein the file uploading request comprises uploading file and storage space information;

when the storage space information passes the verification, determining a target storage cluster of the uploaded file according to the storage space information;

storing the uploading file to the target storage cluster;

and determining file attribute information of the uploaded file in the target storage cluster, and storing the file attribute information into the key value database in the form of key value pairs.

4. The method of claim 1, wherein before deleting or restoring the target file according to the operation type corresponding to the file operation request, further comprises:

Determining locking information according to the storage space information and the first file attribute information;

and locking the file request according to the locking information, wherein the file request comprises a newly added file uploading request or other file operation requests.

5. The method of claim 1, further comprising, after comparing the second check value with the first check value:

if the second check value is different from the first check value, updating the second file attribute information in the database according to the key value according to the first file attribute information;

after comparing the second storage time with the first storage time, the method further comprises:

6. The method of claim 1, wherein after uploading the target file in the standard storage cluster to an archive storage cluster, further comprising:

determining a third check value corresponding to the target file in the archiving storage cluster;

If the first check value is different from the third check value, deleting the target file in the archiving storage cluster;

and if the first check value is the same as the third check value, determining third file attribute information corresponding to the target file in the archive storage cluster, and updating the second file attribute information in the database according to the key value according to the third file attribute information.

7. A document management apparatus, comprising:

The file processing module is used for determining first file attribute information corresponding to the target file in a storage cluster, wherein the first file attribute information comprises a first check value and a first storage time, and the storage cluster comprises a standard storage cluster;

the file processing module is used for receiving the file operation request sent by the life cycle server and deleting or saving the target file according to the operation type corresponding to the file operation request;

the file processing module is further configured to determine a first check value corresponding to the target file according to the first file attribute information when the operation type is delete; determining a second check value corresponding to the target file according to second file attribute information of the target file in the key value pair database; comparing the second check value with the first check value, and deleting the target file if the second check value is the same as the first check value; or when the operation type is the transfer, determining a first storage time corresponding to the target file in the standard storage cluster according to the first file attribute information; determining a second storage time corresponding to the target file according to the second file attribute information of the target file in the key value pair database; and comparing the second storage time with the first storage time, and uploading the target file in the standard storage cluster to an archiving storage cluster if the second storage time is the same as the first storage time.

8. A computer device, the computer device comprising a memory and a processor;

the memory is used for storing a computer program;

the processor being configured to execute the computer program and to implement the file management method according to any one of claims 1 to 6 when the computer program is executed.

9. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, causes the processor to implement the file management method according to any one of claims 1 to 6.