CN107301018A - A kind of WORM technology application processes on cluster-based storage - Google Patents

Abstract

The present invention relates to a kind of WORM technology application processes on cluster-based storage, comprise the following steps：Step S1：Worm opening and closing are realized by changing the parameter in clustered node CIFS/NFS configuration files；Step S2：For share directory, WORM grace periods, WORM time-out times are set；Step S3：CIFS/NFS services are restarted under file system makes the grace period of setting and time-out time come into force；Step S4：Written document request is carried out in client, if this document is in WORM guard modes, mistake is returned to；Otherwise, interval of this operating distance last time to this document write operation time is calculated, and enters step S5；Step S5：If interval in step S4 is less than the WORM grace periods, file system is forwarded the request to, otherwise, file enters WORM guard modes, its attribute is set to read-only, and user's write operation is considered as going beyond one's commission, and mistake is returned to client.

Description

A WORM technology application method on cluster storage

technical field

The invention belongs to the field of computers, and in particular relates to a WORM technology application method on cluster storage.

Background technique

With the development of the times, cluster storage systems are more and more widely used. Cluster storage aggregates the storage space in multiple storage devices into a storage pool that can provide a unified access interface and management interface for application servers. Applications can use this The access interface transparently accesses and utilizes the disks on all storage devices, which can give full play to the performance and disk utilization of storage devices. Data will be stored and read from multiple storage devices according to certain rules to obtain higher concurrent access performance. Cluster storage is a file-level storage system. Therefore, it is often called cluster NAS, and CIFS and NFS based on standard protocols are widely used in cluster storage.

Worm (Write Once Read Many) technology means that data is written into the storage medium once, and can be read out multiple times, but modification or deletion is not allowed, providing the most secure guarantee for important data. Provides pure real data management and is suitable for applications where file information must be 100% unchanged. At first, only optical discs were eligible, and read-only optical discs have natural worm characteristics. With the deepening of applications, especially the requirements of regulatory compliance in recent years, worm technology has developed rapidly. Disks, tapes, MO, UDO and other readable and writable storage media The worm can also be controlled by hardware and software.

Currently applied worm technologies include optical disc technology, magnetic tape technology, and magnetic disk technology. For magnetic disk technology, with the improvement of disk capacity and the reduction of cost, non-erasable and non-rewritable disks have been realized on disks. Worm storage has also been used in many applications. The worm storage volume is created through the disk array cabinet management software. Once the data is stored in the worm storage volume, under the control of the disk cabinet software, even the creator of the file or the system administrator cannot change it within the specified time limit. Deleting or even renaming archived data, only deliberate destruction of the disk can result in data deletion or alteration. Data storage uses RAID technology, which provides high performance and high reliability. At present, there are two main systems for implementing worms on the disk, one is based on the file system, and the other is the content storage system.

With the rapid development of information technology, a large number of data files are continuously produced, and people's security requirements for data files have been greatly increased. In many application fields, the generated files must not be modified and must be stored for a long time. In the prior art The Worm design for cluster storage is not implemented; the Worm design for cluster storage cannot be realized, which limits the application space of cluster storage. This is the weak point of prior art.

Therefore, aiming at the above-mentioned defects in the prior art, it is very necessary to provide and design a WORM technology application method on cluster storage to solve the above-mentioned technical problems.

Contents of the invention

The object of the present invention is to provide and design a WORM technology application method on cluster storage to solve the above-mentioned technical problems in view of the above-mentioned defects in the prior art.

To achieve the above object, the present invention provides the following technical solutions:

A method for applying WORM technology on cluster storage, comprising the following steps:

Step S1: realize the opening and closing of the worm by changing the parameters in the CIFS/NFS configuration file of the cluster node;

Step S2: Set the WORM grace period and WORM timeout period for the shared directory;

Step S3: Restart the CIFS/NFS service under the file system to make the set grace period and timeout period take effect;

Step S4: Make a file write request on the client, receive the file write operation request from the client, identify the file to be operated, and return an error if the file is already under WORM protection; otherwise, calculate the distance between this operation and the last time The interval of the file writing operation time, and enter step S5;

Step S5: If the interval in step S4 is less than the WORM grace period, forward the request to the file system, if the interval is greater than or equal to the grace period, the file enters the WORM protection state immediately, its attribute is set to read-only, and the user writes It is regarded as exceeding authority and returns an error to the client;

Step S6: Manually set the submission protection, so that the file directly enters the protection period, and removes the file write permission or sets it as read-only.

Preferably, in step S1, the recycle bin function is opened by adding the vfsobjects=worm field in the CIFS/NFS shared configuration file of the file system; when there is no such field, the worm function is closed, and in the closed state, the file authority is General file system permission status.

Preferably, in step S2, after the worm function is enabled, a grace period and a timeout parameter are added to the CIFS/NFS shared configuration file to set the protection period of the shared directory (that is, the file can only be read but not written).

As preferably, in step S3, restart the CIFS/NFS service under the file system to make the grace period and the timeout period of the setting take effect; WORM grace period: from the last time the file is written, until the grace period, if there is no such For the write operation of the file, when the file is accessed again, the file enters the WORM protection state, that is, it is set to the read-only state; WORM timeout time: after the file enters the WORM protection state, any user can only read its content, and has no right to It performs any modification or deletion operation. After the timeout period is reached, the WORM protection status becomes invalid, and the file read-only status becomes invalid. At this time, the user is allowed to modify, delete, and read various file operations on the file.

As a preference, in said step S4, when writing to the file through the client, the file under the WORM directory does not perform operations such as writing operations and modifying WORM attributes within the set automatic submission protection time, and the file will automatically enter the protected state .

In this technical solution, in addition to automatically submitting the protection by setting the grace period and timeout time, the file system can also submit the protection manually: use chmod -w filename on the Linux client to remove the file write permission, and on the Windows client: right-click the file , check "Read-only"; the files will immediately enter the protected state, and ordinary users cannot modify these files. Files in the "protected state" can be deleted with privileges using the super administrator account.

The beneficial effect of the present invention is that, for a general file system, after a large number of data files are generated, they cannot be modified within a certain period of time, so that the files enter the protection period, and operations such as deletion and modification can be performed on the files after the protection period exceeds , It cannot meet the business of hospitals and banks that the files will not be modified for a period of time. After adding the worm function to the cluster storage, it can meet this demand, and provide data security, expand the business scope and improve market competitiveness.

It can be seen that, compared with the prior art, the present invention has outstanding substantive features and remarkable progress, and the beneficial effects of its implementation are also obvious.

detailed description

The present invention is described in detail below through specific examples, and the following examples are explanations of the present invention, but the present invention is not limited to the following embodiments.

A kind of WORM technology application method on the cluster storage that the present embodiment provides, is characterized in that, comprises the following steps:

Step S1: realize the opening and closing of the worm by changing the parameters in the CIFS/NFS configuration file of the cluster node;

Step S2: Set the WORM grace period and WORM timeout period for the shared directory;

Step S3: Restart the CIFS/NFS service under the file system to make the set grace period and timeout period take effect;

Step S4: Make a file write request on the client, receive the file write operation request from the client, identify the file to be operated, and return an error if the file is already under WORM protection; otherwise, calculate the distance between this operation and the last time The interval of the file writing operation time, and enter step S5;

Step S5: If the interval in step S4 is less than the WORM grace period, forward the request to the file system, if the interval is greater than or equal to the grace period, the file enters the WORM protection state immediately, its attribute is set to read-only, and the user writes It is regarded as exceeding authority and returns an error to the client;

Step S6: Manually set the submission protection, so that the file directly enters the protection period, and removes the file write permission or sets it as read-only.

In this embodiment, in step S1, the recycle bin function is enabled by adding the vfsobjects=worm field in the CIFS/NFS shared configuration file of the file system; when there is no such field, the worm function is closed, and in the closed state, the file Permissions are general file system permission status.

In step S2, after enabling the worm function, add grace period and timeout parameters to the CIFS/NFS shared configuration file to set the protection period of the shared directory (that is, the file can only be read but not written).

In step S3, restart the CIFS/NFS service under the file system to make the set grace period and timeout time effective; WORM grace period: count from the last time the file is written until the grace period, if there is no more writing to the file Operation, when the file is accessed again, the file enters the WORM protection state, that is, it is set to a read-only state; WORM timeout time: After the file enters the WORM protection state, any user can only read its content, and has no right to do anything to it For modification or deletion operations, after the timeout period is reached, the WORM protection status becomes invalid, and the read-only status of the file becomes invalid. At this time, the user is allowed to modify, delete, and read various file operations on the file.

In the step S4, when the client writes to the file, the file under the WORM directory will automatically enter the protected state if no write operation or modification of the WORM attribute is performed within the set automatic submission protection time.

The above disclosure is only a preferred embodiment of the present invention, but the present invention is not limited thereto, any non-creative changes that those skilled in the art can think of, and some improvements and modifications made without departing from the principle of the present invention , should fall within the protection scope of the present invention.

Claims (5)

1. a WORM technology application method on cluster storage, is characterized in that, comprises the following steps: Step S1: realize the opening and closing of the worm by changing the parameters in the CIFS/NFS configuration file of the cluster node; Step S2: Set the WORM grace period and WORM timeout period for the shared directory; Step S3: Restart the CIFS/NFS service under the file system to make the set grace period and timeout period take effect; Step S4: Make a file write request on the client, receive the file write operation request from the client, identify the file to be operated, and return an error if the file is already under WORM protection; otherwise, calculate the distance between this operation and the last time The interval of the file writing operation time, and enter step S5; Step S5: If the interval in step S4 is less than the WORM grace period, forward the request to the file system, if the interval is greater than or equal to the grace period, the file enters the WORM protection state immediately, its attribute is set to read-only, and the user writes It is regarded as exceeding authority and returns an error to the client; Step S6: Manually set the submission protection, so that the file directly enters the protection period, and removes the file write permission or sets it as read-only. 2. A method for applying WORM technology on cluster storage according to claim 1, characterized in that, in step S1, recovery is enabled by adding the vfs objects=worm field in the CIFS/NFS shared configuration file of the file system Station function; when there is no such field, the worm function is closed, and in the closed state, the file permission is the general file system permission status. 3. A method for applying WORM technology on cluster storage according to claim 1 or 2, characterized in that, in step S2, a grace period and a timeout period are added to the CIFS/NFS shared configuration file after the worm function is enabled parameter to set the protection period of the shared directory. 4. A kind of WORM technology application method on cluster storage according to claim 3, it is characterized in that, in step S3, restart CIFS/NFS service under file system and make the grace period of setting and overtime take effect; WORM wide Deadline: From the last time the file is written to the grace period, if there is no write operation on the file, when the file is accessed again, the file enters the WORM protection state, that is, it is set to the read-only state; WORM timeout Time: After the file enters the WORM protection state, any user can only read its content, but has no right to modify or delete it. After the timeout expires, the WORM protection state becomes invalid, and the file read-only state becomes invalid. Users modify, delete, and read various file operations on files. 5. A kind of WORM technology application method on cluster storage according to claim 4, it is characterized in that, in described step S4, when writing to file by client, the file under WORM directory, in the setting If there is no write operation or modification of WORM attributes within the automatic commit protection time, the file will automatically enter the protected state.