User configuration synchronization method and device for network attached storage server group, and medium

Abstract

The invention provides a user configuration synchronization method and device for a network attached storage server group, and a medium. In the method, when a synchronization server receives a user new establishment request sent by a user terminal, the user new establishment request is forwarded to a main NAS server in an NAS server group. And the main NAS server performs new user processing according to the user new request, completes user configuration, generates a user configuration file, and sends the user configuration file to the synchronization server. And the synchronization server sends the user configuration file to each slave NAS server in the NAS server group. And the slave NAS server performs user configuration according to the user configuration file. According to the scheme, the master NAS server sends the user configuration file to the synchronization server, and the synchronization server sends the user configuration file to each slave NAS server, so that the user configuration synchronization of the NAS server group is realized, manual creation is not needed, and the synchronization efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a user configuration synchronization method, device and medium for a network-attached storage server group. Background Technology

[0002] Network Attached Storage (NAS) servers are network devices specifically designed for data storage and sharing, allowing multiple users to access stored data simultaneously over a network. To achieve higher access efficiency, multiple NAS servers are typically deployed in different regions, forming a NAS server group. Each NAS server stores the same data, and users can access the NAS server closest to them. Furthermore, to ensure that every user can access all NAS servers, the user configuration on each NAS server must be identical.

[0003] In existing technologies, when creating a new user on a NAS server, the user configuration synchronization is usually achieved by having staff create a new user on each NAS server based on the same user creation information, and then each NAS server processes the new user to achieve user configuration.

[0004] In summary, the existing user configuration synchronization method for NAS server groups requires manual creation of new configurations for each NAS server, resulting in low synchronization efficiency. Summary of the Invention

[0005] The user configuration synchronization method, device, and medium for network attached storage server groups provided in this application are intended to solve the problem of low synchronization efficiency caused by the need for manual creation of each NAS server to achieve user configuration synchronization in the prior art.

[0006] In a first aspect, embodiments of this application provide a user configuration synchronization method for a network-attached storage server group, applied to a synchronization server, comprising:

[0007] When a user terminal sends a new user request, the user request is sent to the primary network attached storage server in the network attached storage server group. The user request includes username, password and user permission data.

[0008] Receive a user configuration file sent by the main network additional storage server, the user configuration file including the username, the password and the user permission data;

[0009] The user profile is sent to each of the network attached storage servers in the network attached storage server group.

[0010] In one possible implementation, the method further includes:

[0011] Calculate the target hash value of the user profile;

[0012] The target hash value is sent to each network-attached storage server.

[0013] In one possible implementation, the method further includes:

[0014] Receive synchronization failure messages sent from the network-attached storage server;

[0015] Update the synchronization failure count corresponding to the network attached storage server;

[0016] Calculate the synchronization duration based on the number of synchronization failures;

[0017] After the synchronization duration at the current moment, the user profile is sent to the network-attached storage server.

[0018] In one possible implementation, the method further includes:

[0019] When a user deletion request is received from a user terminal, the user deletion request is sent to each network attached storage server in the network attached storage server group, and the user deletion request includes the username to be deleted.

[0020] In one possible implementation, the method further includes:

[0021] When a user permission update request is received from a user terminal, the user permission update request is sent to each network attached storage server in the network attached storage server group. The user permission update request includes the username to be updated and the target user permission data.

[0022] Secondly, embodiments of this application provide a user configuration synchronization method for a network attached storage server group, applied to the primary network attached storage server in the network attached storage server group, comprising:

[0023] Receive a user creation request sent by the synchronization server, the user creation request including username, password and user permission data;

[0024] The system processes the user creation request to create a new user, completes the user configuration, and generates a user configuration file, which includes the username, the password, and the user permission data.

[0025] The user configuration file is sent to the synchronization server.

[0026] In one possible implementation, the method further includes:

[0027] Receive a user deletion request sent by the synchronization server, the user deletion request including the username to be deleted;

[0028] Clear the user configuration corresponding to the username to be deleted.

[0029] In one possible implementation, the method further includes:

[0030] Receive a user permission update request sent by the synchronization server, the user permission update request including the username to be updated and the target user permission data;

[0031] Update the user permission data in the user configuration corresponding to the updated username to the target user permission data.

[0032] Thirdly, embodiments of this application provide a user configuration synchronization method for a network attached storage server group, applied to slave network attached storage servers in the network attached storage server group, including:

[0033] Receive a user configuration file sent by the synchronization server, the user configuration file including username, password and user permission data;

[0034] Configure the user according to the user profile.

[0035] In one possible implementation, before configuring the user according to the user profile, the method further includes:

[0036] Receive the target hash value sent by the synchronization server;

[0037] Calculate the hash value to be compared in the user configuration file;

[0038] The step of configuring users according to the user configuration file includes:

[0039] If the hash value to be compared is the same as the target hash value, then the user configuration is performed according to the user configuration file.

[0040] In one possible implementation, the method further includes:

[0041] If the hash value to be compared is different from the target hash value, a synchronization failure message is sent to the synchronization server.

[0042] In one possible implementation, the method further includes:

[0043] Receive a user deletion request sent by the synchronization server, the user deletion request including the username to be deleted;

[0044] Clear the user configuration corresponding to the username to be deleted.

[0045] In one possible implementation, the method further includes:

[0046] Receive a user permission update request sent by the synchronization server, the user permission update request including the username to be updated and the target user permission data;

[0047] Update the user permission data in the user configuration corresponding to the updated username to the target user permission data.

[0048] Fourthly, embodiments of this application provide a user configuration synchronization device for a network-attached storage server group, comprising:

[0049] The sending module is used to send a user creation request sent by a user terminal to the main network additional storage server in the network additional storage server group when it receives the user creation request. The user creation request includes username, password and user permission data.

[0050] A receiving module is used to receive a user configuration file sent by the main network additional storage server, the user configuration file including the username, the password and the user permission data;

[0051] The sending module is used to send the user configuration file to each of the network attached storage servers in the network attached storage server group.

[0052] Fifthly, embodiments of this application provide a user configuration synchronization device for a network-attached storage server group, comprising:

[0053] The receiving module is used to receive user creation requests sent by the synchronization server. The user creation request includes username, password and user permission data.

[0054] The processing module is used to process the user's new user request, complete the user configuration, and generate a user configuration file, which includes the username, the password, and the user permission data.

[0055] The sending module is used to send the user configuration file to the synchronization server.

[0056] Sixthly, embodiments of this application provide a user configuration synchronization device for a network-attached storage server group, comprising:

[0057] The receiving module is used to receive the user configuration file sent by the synchronization server. The user configuration file includes the username, password and user permission data.

[0058] The configuration module is used to configure users based on the user configuration file.

[0059] Seventhly, embodiments of this application provide a server, including:

[0060] Processor, memory, communication interface;

[0061] The memory is used to store the executable instructions of the processor;

[0062] The processor is configured to execute the user configuration synchronization method for the network-attached storage server group as described in any one of the first, second, or third aspects by executing the executable instructions.

[0063] Eighthly, embodiments of this application provide a readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the user configuration synchronization method for a network-attached storage server group as described in any one of the first, second, or third aspects.

[0064] Ninthly, embodiments of this application provide a computer program product, including a computer program, which, when executed by a processor, is used to implement the user configuration synchronization method for a network-attached storage server group as described in any one of the first, second, or third aspects.

[0065] The user configuration synchronization method, device, and medium for a network attached storage (NAS) server group provided in this application embodiment involve a synchronization server forwarding a user creation request received from a user terminal to the master NAS server in the NAS server group. The master NAS server processes the user creation request, completes the user configuration, generates a user configuration file, and sends the user configuration file to the synchronization server. The synchronization server then sends the user configuration file to each slave NAS server in the NAS server group. The slave NAS servers configure their users according to the user configuration file. This solution achieves user configuration synchronization for the NAS server group by having the master NAS server send the user configuration file to the synchronization server, and the synchronization server then sends the user configuration file to each slave NAS server, eliminating the need for manual creation and improving synchronization efficiency. Attached Figure Description

[0066] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0067] Figure 1 A schematic diagram illustrating an application scenario for configuring synchronization methods for users of the network-attached storage server group provided in this application;

[0068] Figure 2 A flowchart illustrating an embodiment of the user configuration synchronization method for the network attached storage server group provided in this application;

[0069] Figure 3 A flowchart illustrating Embodiment 2 of the user configuration synchronization method for the network attached storage server group provided in this application;

[0070] Figure 4 A flowchart illustrating Embodiment 3 of the user configuration synchronization method for the network attached storage server group provided in this application;

[0071] Figure 5 A flowchart illustrating Embodiment 4 of the user configuration synchronization method for the network attached storage server group provided in this application;

[0072] Figure 6 A schematic diagram of the structure of an embodiment of the user configuration synchronization device for the network-attached storage server group provided in this application;

[0073] Figure 7 A schematic diagram of the second embodiment of the user configuration synchronization device for the network-attached storage server group provided in this application;

[0074] Figure 8 A schematic diagram of the structure of a third embodiment of the user configuration synchronization device for the network-attached storage server group provided in this application;

[0075] Figure 9 This is a schematic diagram of the structure of a server provided in this application.

[0076] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0077] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0078] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0079] With the continuous development of technology, data sharing can be achieved through Network Attached Storage (NAS) servers. A NAS server is a network device specifically designed for data storage and sharing, allowing multiple users to access stored data simultaneously over the network. To achieve higher access efficiency, multiple NAS servers are typically deployed in different regions, forming a NAS server group. Each NAS server stores the same data, and users can access the NAS server closest to them. Furthermore, to ensure that users in different locations can access data from the NAS—that is, to ensure that every user can access all NAS servers—the user configuration of each NAS server must be identical.

[0080] In existing technologies, the synchronization of user configurations when creating new users on a NAS server typically involves staff manually creating new users on each NAS server using the same user creation information, and then processing the new user on each NAS server to complete the user configuration. Because this requires manual creation on each NAS server, it leads to low synchronization efficiency.

[0081] To address the problems existing in the prior art, the inventors, during their research on user configuration synchronization methods for NAS server groups, discovered that to improve synchronization efficiency, a synchronization server can be used to uniformly manage each NAS server in the NAS server group. When the synchronization server receives a user creation request from a user terminal, it forwards it to the master NAS server in the NAS server group. The master NAS server processes the user creation request, completes the user configuration, generates a user configuration file, and sends the user configuration file to the synchronization server. The synchronization server then sends the user configuration file to each slave NAS server in the NAS server group. The slave NAS servers configure their users according to the user configuration file, thus achieving user configuration synchronization for the NAS server group. Based on the above inventive concept, the user configuration synchronization scheme for NAS server groups described in this application was designed.

[0082] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0083] For example, Figure 1 An illustration of an application scenario for configuring synchronization methods for users of the network-attached storage server group provided in this application, such as... Figure 1 As shown, the application scenario may include: user terminal 11, synchronization server 12, master NAS server 13 and multiple slave NAS servers (only two slave NAS servers are shown in the figure, namely slave NAS server 14 and slave NAS server 15).

[0084] The NAS server group has only one master NAS server, and the others are slave NAS servers.

[0085] exist Figure 1 In the application scenario shown, the user needs to create a new user on each NAS server in the NAS server group. The user terminal 11 sends a user creation request to the synchronization server 12. The user creation request includes the username, password and user permission data.

[0086] When synchronization server 12 receives a user creation request, it sends the request to the primary NAS server 13. The primary NAS server 13 processes the user creation request, completes the user configuration, and generates a user configuration file, which includes the username, password, and user permission data. The primary NAS server 13 then sends the user configuration file to synchronization server 12.

[0087] After receiving the user configuration file, synchronization server 12 sends it to each slave NAS server. Figure 1 In the process, synchronization server 12 sends user configuration files to slave NAS server 14 and slave NAS server 15.

[0088] User configuration is synchronized between NAS server 14 and NAS server 15 based on user configuration files.

[0089] It should be noted that, Figure 1 This is merely a schematic diagram illustrating one application scenario provided by an embodiment of this application. This embodiment does not necessarily represent... Figure 1 The document does not limit the actual form of the various devices included, nor does it specify the form of the devices. Figure 1 The interaction methods between devices are limited, and can be set according to actual needs in the specific application of the solution.

[0090] The technical solution of this application will now be described in detail through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0091] Figure 2 This is a flowchart illustrating an embodiment of the user configuration synchronization method for a network attached storage server group provided in this application. This embodiment describes the implementation of user configuration synchronization for a NAS server group via a synchronization server. The method in this embodiment can be implemented through software, hardware, or a combination of both. Figure 2 As shown, the user configuration synchronization method for this network-attached storage server group specifically includes the following steps:

[0092] S201: When the synchronization server receives a user creation request from a user terminal, it sends the user creation request to the primary network attached storage server in the network attached storage server group.

[0093] When a user needs to create a new user on each NAS server in the NAS server group, they can enter the username, password, and user permission data on the web interface displayed on the user terminal. After clicking the "Create" button, the user terminal sends a user creation request to the synchronization server. The user creation request includes the username, password, and user permission data.

[0094] In this step, after the user terminal sends a new user request to the synchronization server, the synchronization server can receive the new user request. Then, in order to realize the user configuration synchronization, it needs to send the new user request to the master NAS server in the NAS server group.

[0095] It should be noted that user permission data includes access permission data and quota permissions. Access permission data is used to represent the range of data that a user can access on the NAS server, while quota permissions are used to represent the upper limit of storage space that a user can use.

[0096] S202: After receiving a user creation request from the synchronization server, the main network attached storage server processes the user creation request, completes the user configuration, and generates a user configuration file.

[0097] In this step, after the synchronization server sends the user creation request to the primary NAS server, the primary NAS server can receive the user creation request and then process the user creation based on the username, password and user permission data in the user creation request. Once the user creation is completed, the user configuration is completed. In order to synchronize the user configuration with the slave NAS servers in the NAS server group, a user configuration file needs to be generated based on the user configuration. The user configuration file includes the username, password and user permission data.

[0098] The main NAS server creates new users based on usernames, passwords, and permission data. User configuration may include: username settings, password settings, user group assignments, file access permissions, quota permissions, network access configurations, access speed configurations, and home directory settings. This application embodiment does not limit user configuration; it can be determined according to actual circumstances.

[0099] It should be noted that after the main NAS server completes the user configuration, it can establish a correspondence between the user configuration and the username for subsequent use.

[0100] S203: The primary network supplemental storage server sends the user profile to the synchronization server.

[0101] In this step, after the primary NAS server generates the user configuration file, it sends the user configuration file to the synchronization server.

[0102] S204: After receiving the user profile from the primary network attached storage server, the synchronization server sends the user profile to each slave network attached storage server in the network attached storage server group.

[0103] In this step, after the master NAS server sends the user configuration file to the synchronization server, the synchronization server can obtain the user configuration file and then send the user configuration file to each slave NAS server in the NAS server group in order to achieve user configuration synchronization.

[0104] It should be noted that the synchronization server stores the device identifier of the master NAS server and the device identifier of each slave NAS server. The device identifiers of the master NAS server and the slave NAS server are stored in different ways. Therefore, the synchronization server can distinguish the device identifiers of the master NAS server and the slave NAS server, and thus send user creation requests to the master NAS server and user configuration files to the slave NAS server.

[0105] The storage method for the device identifiers of the primary NAS server and the secondary NAS server can be as follows: the device identifier of the primary NAS server is stored carrying a primary NAS server tag, while the device identifier of the secondary NAS server is stored without any tag. Alternatively, the device identifier of the primary NAS server is stored without any tag, while the device identifier of the secondary NAS server is stored carrying a secondary NAS server tag. Another option is that the device identifiers of the primary and secondary NAS servers are stored on different paths. This application does not limit the storage method for the device identifiers of the primary and secondary NAS servers; it can be determined according to the actual situation.

[0106] S205: After receiving the user configuration file sent by the synchronization server from the network attached storage server, configure the user according to the user configuration file.

[0107] In this step, after the synchronization server sends the user configuration file to the slave NAS server, the slave NAS server receives the user configuration file, which includes the username, password, and user permission data. The slave NAS server then configures the user based on the user configuration file, without needing to create a new user.

[0108] Since the user configuration file is generated by the primary NAS server based on its own user configuration, the secondary NAS server can configure its users according to this user configuration file, making the user configuration on the secondary NAS server exactly the same as the user configuration on the primary NAS server.

[0109] It should be noted that after completing the user configuration from the NAS server, a correspondence can be established between the user configuration and the username for subsequent use.

[0110] The user configuration synchronization method for a network attached storage (NAS) server group provided in this embodiment involves a synchronization server forwarding a user creation request received from a user terminal to the primary NAS server in the NAS server group. The primary NAS server processes the user creation request, completes the user configuration, generates a user configuration file, and sends the user configuration file to the synchronization server. The synchronization server then sends the user configuration file to each secondary NAS server in the NAS server group. The secondary NAS servers configure their users according to the user configuration file. This solution achieves user configuration synchronization for the NAS server group by having the primary NAS server send the user configuration file to the synchronization server, and the synchronization server then sends the user configuration file to each secondary NAS server. This eliminates the need for manual creation, improving synchronization efficiency and success rate.

[0111] Furthermore, NAS servers generate user identifiers and other information during user creation. Even when using the same username, password, and user permission data, different NAS servers will generate different user identifiers, resulting in inconsistent user configurations. This solution ensures identical user configurations by configuring users on the NAS server based on the configuration file generated by the main NAS server.

[0112] Figure 3 This is a flowchart illustrating a second embodiment of the user configuration synchronization method for a network attached storage server group provided in this application. Based on the above embodiments, this embodiment further describes the process where the synchronization server sends a user configuration file to the slave NAS server, then generates a target hash value for the user configuration file and sends it to the NAS server, and the slave NAS server determines whether to perform user configuration based on the target hash value. Figure 3 As shown, the user configuration synchronization method for this network-attached storage server group specifically includes the following steps:

[0113] S301: The synchronization server calculates the target hash value of the user configuration file.

[0114] In this step, to ensure the accuracy of user configuration from the NAS server, the synchronization server calculates the target hash value of the user configuration file using a preset hash function after sending the user configuration data to each slave NAS server.

[0115] It should be noted that the preset hash function can be: MD5 (Message-Digest Algorithm 5) function, SHA-256 (Secure Hash Algorithm 256) function, CRC32 (Cyclic Redundancy Check 32) function, etc. This application embodiment does not limit the preset hash function, and it can be determined according to the actual situation.

[0116] S302: The synchronization server sends the target hash value to each network-attached storage server.

[0117] In this step, after the synchronization server generates the target hash value, it sends the target hash value to each slave NAS server so that the slave NAS servers can subsequently verify the user configuration file.

[0118] S303: After receiving the target hash value sent by the synchronization server from the network attached storage server, calculate the hash value to be compared in the user profile.

[0119] In this step, after the synchronization server sends the target hash value to the slave NAS server, the slave NAS server can obtain the target hash value. In order to verify whether there is any data anomaly in the user configuration file, it is necessary to use a preset hash function to calculate the hash value to be compared in the user configuration file.

[0120] In one implementation, the synchronization server can encrypt the user configuration file and send it to the slave NAS server. The slave NAS server decrypts the encrypted user configuration file and then calculates the hash value of the user configuration file to be compared.

[0121] S304: Determine from the network attached storage server whether the hash value to be compared is the same as the target hash value; if the hash value to be compared is the same as the target hash value, proceed to step S305; if the hash value to be compared is not the same as the target hash value, proceed to step S306.

[0122] In this step, after calculating the hash value to be compared from the NAS server, it is determined whether the hash value to be compared is the same as the target hash value in order to determine whether there is any data anomaly in the user configuration file.

[0123] S305: Configure users from the network attached storage server based on user profiles.

[0124] In this step, if the NAS server determines that the hash value to be compared is the same as the target hash value, it means that there is no data anomaly in the user configuration file, and then the user configuration is performed according to the user configuration file.

[0125] S306: Send a synchronization failure message from the network attached storage server to the synchronization server.

[0126] In this step, if the NAS server determines that the hash value to be compared is different from the target hash value, it indicates that there is a data anomaly in the user configuration file. In this case, a synchronization failure message is sent to the synchronization server, and user configuration is not performed.

[0127] S307: After receiving a synchronization failure message from the network attached storage server, the synchronization server updates the corresponding synchronization failure count from the network attached storage server.

[0128] In this step, after the NAS server sends a synchronization failure message to the synchronization server, the synchronization server can obtain the synchronization failure message sent by the NAS server. In order for the NAS server to perform user configuration synchronization, it needs to send the user configuration file again.

[0129] Since the data anomalies in the user configuration file may be due to network congestion or other network issues, it is necessary to resend the user configuration file after a period of time to avoid network anomalies causing data anomalies in the user configuration file again. Therefore, in order to determine when to resend the user configuration file, it is necessary to first update the synchronization failure count corresponding to the NAS server, that is, to increment the synchronization failure count corresponding to the NAS server by one.

[0130] S308: The synchronization server calculates the synchronization duration based on the number of synchronization failures.

[0131] In this step, after the server obtains the number of synchronization failures, it calculates the synchronization duration based on the number of failures.

[0132] According to the preset formula Calculate the synchronization duration, where T represents the synchronization duration. This indicates the preset maximum duration. q represents the preset baseline duration, k represents the number of synchronization failures, and q represents a random number generated within the preset duration.

[0133] It should be noted that the upper limit of the preset duration can be 5 seconds, 10 seconds, 20 seconds, etc., the preset base duration can be 100 milliseconds, 500 milliseconds, 1 second, 3 seconds, etc., and the preset duration range can be -30~30 milliseconds, -100~1000 milliseconds, -300~300 milliseconds, etc. This application embodiment does not limit the upper limit of the preset duration, the preset base duration, and the preset duration range, which can be determined according to the actual situation.

[0134] S309: The synchronization server will send the user profile to the network-attached storage server after the synchronization duration at the current moment.

[0135] In this step, after the synchronization server calculates the synchronization duration, it sends the user configuration file to the slave NAS server after the synchronization duration at the current moment, and the slave NAS server can receive the user configuration file.

[0136] The process of steps S301-S309 is repeated until the NAS server configures the user according to the user configuration file.

[0137] In one implementation, after calculating the number of synchronization failures, the synchronization server can determine whether the number of failures is less than a preset threshold. If the number of failures is less than the preset threshold, the synchronization duration is calculated based on the number of failures. If the number of failures equals the preset threshold, a synchronization failure message is output, which includes the device identifier of the slave NAS server.

[0138] It should be noted that the preset number of times threshold can be 3, 5, 10, 20, etc. This application embodiment does not limit the preset number of times threshold, and it can be determined according to the actual situation.

[0139] In one implementation, after obtaining the target hash value, the synchronization server encrypts the target hash value to obtain a signature value, and then sends the signature value to the slave NAS server. The slave NAS server decrypts the signature value to obtain the signature decryption hash value; then calculates the hash value to be compared in the user configuration file, and determines whether the comparison hash value is the same as the signature decryption hash value; if the comparison hash value is the same as the signature decryption hash value, then step S305 is executed; if the comparison hash value is not the same as the signature decryption hash value, then step S306 is executed.

[0140] The user configuration synchronization method for network attached storage server groups provided in this embodiment verifies the user configuration file by using the target hash value of the user configuration file sent by the synchronization server and the hash value of the user configuration file to be compared calculated by the NAS server itself. User configuration is performed only after successful verification, ensuring that the user configurations of the slave NAS server and the master NAS server are identical. If verification fails, the synchronization server resends the user configuration file at synchronization intervals, improving the success rate of user configuration synchronization.

[0141] Figure 4 This is a flowchart illustrating a third embodiment of the user configuration synchronization method for a network attached storage server group provided in this application. Based on the above embodiments, this embodiment uses both the primary NAS server and the secondary NAS server in the NAS server group as NAS servers, and describes the process of clearing user configuration synchronization on the NAS servers. Figure 4 As shown, the user configuration synchronization method for this network-attached storage server group specifically includes the following steps:

[0142] S401: When the synchronization server receives a user deletion request from a user terminal, it sends the user deletion request to each network attached storage server in the network attached storage server group.

[0143] When you need to clear the user configuration of a user on each NAS server in the NAS server group, the user can enter the username to be deleted on the web interface displayed on the user terminal, and after clicking the delete button, the user terminal sends a user deletion request to the synchronization server. The user deletion request includes the username to be deleted.

[0144] In this step, when the synchronization server receives a user deletion request from a user terminal, it sends the user deletion request to each NAS server in the NAS server group in order to achieve user configuration synchronization.

[0145] S402: After receiving a user deletion request from the synchronization server, the network attached storage server clears the user configuration corresponding to the username to be deleted.

[0146] In this step, after the synchronization server sends the user deletion request to the NAS server, the NAS server can receive the user deletion request, and then find the user configuration corresponding to the username to be deleted based on the username in the request, and clear the user configuration.

[0147] It should be noted that the NAS server can be either a primary NAS server or a secondary NAS server.

[0148] In one implementation, the NAS server first determines whether a user configuration corresponding to the username to be deleted is found. If a user configuration corresponding to the username to be deleted is found, the user configuration is cleared. If no user configuration corresponding to the username to be deleted is found, the user deletion request is discarded.

[0149] The user configuration synchronization method for the network attached storage server group provided in this embodiment achieves clearing user configuration synchronization by sending user deletion requests to each NAS server in the NAS server group through the synchronization server, thereby improving synchronization efficiency.

[0150] Figure 5 This is a flowchart illustrating Embodiment 4 of the user configuration synchronization method for a network attached storage server group provided in this application. Based on the above embodiments, this embodiment uses both the primary NAS server and the secondary NAS server in the NAS server group as NAS servers, and describes the situation where user permission synchronization is updated on the NAS servers. For example... Figure 5 As shown, the user configuration synchronization method for this network-attached storage server group specifically includes the following steps:

[0151] S501: When the synchronization server receives a user rights update request from a user terminal, it sends the user rights update request to each network attached storage server in the network attached storage server group.

[0152] When it is necessary to update the user permissions of a user on each NAS server in the NAS server group, the user can enter the username to be updated and the target user permission data on the web interface displayed on the user terminal. After clicking the update button, the user terminal sends a user permission update request to the synchronization server. The user permission update request includes the username to be updated and the target user permission data.

[0153] In this step, when the synchronization server receives a user permission update request from a user terminal, it sends the user permission update request to each NAS server in the NAS server group in order to achieve user configuration synchronization.

[0154] S502: After receiving a user permission update request from the synchronization server, the network attached storage server will update the user permission data in the user configuration corresponding to the username to the target user's permission data.

[0155] In this step, after the synchronization server sends the user permission update request to the NAS server, the NAS server can receive the user permission update request, and then find the user configuration corresponding to the username to be updated based on the username in the request, and update the user permission data of the user configuration to the target user permission data.

[0156] It should be noted that the NAS server can be either a primary NAS server or a secondary NAS server.

[0157] The user configuration synchronization method for the network attached storage server group provided in this embodiment achieves user permission update synchronization by sending user permission update requests to each NAS server in the NAS server group through a synchronization server, thereby improving synchronization efficiency.

[0158] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0159] Figure 6 A schematic diagram of an embodiment of the user configuration synchronization device for the network-attached storage server group provided in this application; this device can be integrated into the synchronization server in the above method embodiments, or it can be implemented through the synchronization server in the above method embodiments. Figure 6 As shown, the user configuration synchronization device 60 of the network-attached storage server group includes:

[0160] When receiving a user creation request from a user terminal, the sending module 61 sends the user creation request to the main network additional storage server in the network additional storage server group. The user creation request includes username, password and user permission data.

[0161] Receiving module 62 is used to receive a user configuration file sent by the main network additional storage server, the user configuration file including the username, the password and the user permission data;

[0162] The sending module 61 is used to send the user configuration file to each of the network attached storage servers in the network attached storage server group.

[0163] Furthermore, the user configuration synchronization device 60 of the network-attached storage server group also includes a processing module 63 for calculating the target hash value of the user configuration file;

[0164] The sending module 61 is also used to send the target hash value to each network-attached storage server.

[0165] Furthermore, the receiving module 62 is also configured to receive a synchronization failure message sent from the network attached storage server;

[0166] The processing module 63 is further configured to:

[0167] Update the synchronization failure count corresponding to the network attached storage server;

[0168] Calculate the synchronization duration based on the number of synchronization failures;

[0169] The sending module 61 is further configured to send the user configuration file to the network attached storage server after the synchronization duration at the current time.

[0170] Furthermore, the sending module 61 is also configured to, upon receiving a user deletion request sent by a user terminal, send the user deletion request to each network attached storage server in the network attached storage server group, wherein the user deletion request includes the username to be deleted.

[0171] Furthermore, the sending module 61 is also configured to, upon receiving a user permission update request sent by a user terminal, send the user permission update request to each network attached storage server in the network attached storage server group, wherein the user permission update request includes the username to be updated and the target user permission data.

[0172] The user configuration synchronization device for the network-attached storage server group provided in this embodiment is used to execute the technical solution of the synchronization server in any of the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0173] Figure 7 This is a schematic diagram of the second embodiment of the user configuration synchronization device for the network attached storage server group provided in this application; this device can be integrated into the main NAS server in the above method embodiments, or it can be implemented through the main NAS server in the above method embodiments. Figure 7 As shown, the user configuration synchronization device 70 of the network-attached storage server group includes:

[0174] The receiving module 71 is used to receive a user creation request sent by the synchronization server, wherein the user creation request includes username, password and user permission data;

[0175] Processing module 72 is used to process the new user according to the user's new user request, complete the user configuration and generate a user configuration file, the user configuration file including the username, the password and the user permission data;

[0176] The sending module 73 is used to send the user configuration file to the synchronization server.

[0177] Furthermore, the receiving module 71 is also configured to receive a user deletion request sent by the synchronization server, the user deletion request including the username to be deleted;

[0178] The processing module 72 is also used to clear the user configuration corresponding to the username to be deleted.

[0179] Furthermore, the receiving module 71 is also used to receive a user permission update request sent by the synchronization server, the user permission update request including the username to be updated and the target user permission data;

[0180] The processing module 72 is further configured to update the user permission data in the user configuration corresponding to the updated username to the target user permission data.

[0181] The user configuration synchronization device for the network attached storage server group provided in this embodiment is used to execute the technical solution of the main NAS server in any of the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0182] Figure 8This is a schematic diagram of the structure of a third embodiment of the user configuration synchronization device for the network attached storage server group provided in this application; this device can be integrated into the slave NAS server in the above method embodiments, or it can be implemented through the slave NAS server in the above method embodiments. Figure 8 As shown, the user configuration synchronization device 80 of the network-attached storage server group includes:

[0183] Receiving module 81 is used to receive a user configuration file sent by the synchronization server, the user configuration file including username, password and user permission data;

[0184] Configuration module 82 is used to configure users according to the user configuration file.

[0185] Furthermore, the receiving module 81 is also used to receive the target hash value sent by the synchronization server;

[0186] Processing module 83 is used to calculate the hash value to be compared in the user configuration file;

[0187] The configuration module 82 is specifically used to perform user configuration according to the user configuration file if the hash value to be compared is the same as the target hash value.

[0188] The sending module 84 is used to send a synchronization failure message to the synchronization server if the hash value to be compared is not the same as the target hash value.

[0189] Furthermore, the receiving module 81 is also configured to receive a user deletion request sent by the synchronization server, the user deletion request including the username to be deleted;

[0190] The configuration module 82 is also used to clear the user configuration corresponding to the username to be deleted.

[0191] Furthermore, the receiving module 81 is also used to receive a user permission update request sent by the synchronization server, the user permission update request including the username to be updated and the target user permission data;

[0192] The configuration module 82 is further configured to update the user permission data in the user configuration corresponding to the updated username to the target user permission data.

[0193] The user configuration synchronization device for the network attached storage server group provided in this embodiment is used to execute the technical solution from the NAS server in any of the aforementioned method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0194] Figure 9 This is a schematic diagram of the structure of a server provided in this application. Figure 9As shown, the server 90 includes:

[0195] Processor 91, memory 92, and communication interface 93;

[0196] The memory 92 is used to store the executable instructions of the processor 91;

[0197] The processor 91 is configured to execute the technical solutions of the synchronization server, master NAS server, or slave NAS server in any of the foregoing method embodiments by executing the executable instructions.

[0198] Optionally, the memory 92 can be either standalone or integrated with the processor 91.

[0199] Optionally, when the memory 92 is a device independent of the processor 91, the server 90 may further include:

[0200] Bus 94, memory 92 and communication interface 93 are connected to processor 91 through bus 94 and complete communication with each other. Communication interface 93 is used to communicate with other devices.

[0201] Optionally, the communication interface 93 can be implemented using a transceiver. The communication interface is used to enable communication between the database access device and other devices (e.g., clients, read-write databases, and read-only databases). The memory may include random access memory (RAM) and may also include non-volatile memory, such as at least one disk drive.

[0202] Bus 94 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, only one thick line is used in the diagram, but this does not indicate that there is only one bus or one type of bus.

[0203] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be 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, or discrete hardware components.

[0204] This server is used to execute the technical solutions of synchronization server, master NAS server or slave NAS server in any of the aforementioned method embodiments. The implementation principle and technical effect are similar, and will not be described again here.

[0205] This application also provides a readable storage medium storing a computer program thereon, which, when executed by a processor, implements the technical solutions of the synchronization server, master NAS server, or slave NAS server in any of the foregoing method embodiments.

[0206] This application also provides a computer program product, including a computer program, which, when executed by a processor, is used to implement the technical solutions of the synchronization server, master NAS server, or slave NAS server in any of the foregoing method embodiments.

[0207] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0208] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for synchronizing user configurations for a network-attached storage server group, characterized in that, Applied to synchronization servers, including: When a user terminal sends a new user request, the user request is sent to the primary network attached storage server in the network attached storage server group. The user request includes username, password and user permission data. Receive a user configuration file sent by the main network additional storage server, the user configuration file including the username, the password and the user permission data; The user profile is sent to each of the network attached storage servers in the network attached storage server group.

2. The method according to claim 1, characterized in that, The method further includes: Calculate the target hash value of the user profile; The target hash value is sent to each network-attached storage server.

3. The method according to claim 2, characterized in that, The method further includes: Receive synchronization failure messages sent from the network-attached storage server; Update the synchronization failure count corresponding to the network attached storage server; Calculate the synchronization duration based on the number of synchronization failures; After the synchronization duration at the current moment, the user profile is sent to the network-attached storage server.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: When a user deletion request is received from a user terminal, the user deletion request is sent to each network attached storage server in the network attached storage server group, and the user deletion request includes the username to be deleted.

5. The method according to any one of claims 1 to 3, characterized in that, The method further includes: When a user permission update request is received from a user terminal, the user permission update request is sent to each network attached storage server in the network attached storage server group. The user permission update request includes the username to be updated and the target user permission data.

6. A method for synchronizing user configurations for a network-attached storage server group, characterized in that, The primary network-attached storage server used in a network-attached storage server group includes: Receive a user creation request sent by the synchronization server, the user creation request including username, password and user permission data; The system processes the user creation request to create a new user, completes the user configuration, and generates a user configuration file, which includes the username, the password, and the user permission data. The user configuration file is sent to the synchronization server.

7. The method according to claim 6, characterized in that, The method further includes: Receive a user deletion request sent by the synchronization server, the user deletion request including the username to be deleted; Clear the user configuration corresponding to the username to be deleted.

8. The method according to claim 6, characterized in that, The method further includes: Receive a user permission update request sent by the synchronization server, the user permission update request including the username to be updated and the target user permission data; Update the user permission data in the user configuration corresponding to the updated username to the target user permission data.

9. A method for synchronizing user configurations for a network-attached storage server group, characterized in that, The network-attached storage servers used in a network-attached storage server group include: Receive a user configuration file sent by the synchronization server, the user configuration file including username, password and user permission data; Configure the user according to the user profile.

10. The method according to claim 9, characterized in that, Before configuring the user according to the user configuration file, the method further includes: Receive the target hash value sent by the synchronization server; Calculate the hash value to be compared in the user configuration file; The step of configuring users according to the user configuration file includes: If the hash value to be compared is the same as the target hash value, then the user configuration is performed according to the user configuration file.

11. The method according to claim 10, characterized in that, The method further includes: If the hash value to be compared is different from the target hash value, a synchronization failure message is sent to the synchronization server.

12. The method according to any one of claims 9 to 11, characterized in that, The method further includes: Receive a user deletion request sent by the synchronization server, the user deletion request including the username to be deleted; Clear the user configuration corresponding to the username to be deleted.

13. The method according to any one of claims 9 to 11, characterized in that, The method further includes: Receive a user permission update request sent by the synchronization server, the user permission update request including the username to be updated and the target user permission data; Update the user permission data in the user configuration corresponding to the updated username to the target user permission data.

14. A user configuration synchronization device for a network-attached storage server group, characterized in that, include: The sending module is used to send a user creation request sent by a user terminal to the main network additional storage server in the network additional storage server group when it receives the user creation request. The user creation request includes username, password and user permission data. A receiving module is used to receive a user configuration file sent by the main network additional storage server, the user configuration file including the username, the password and the user permission data; The sending module is used to send the user configuration file to each of the network attached storage servers in the network attached storage server group.

15. A user configuration synchronization device for a network-attached storage server group, characterized in that, include: The receiving module is used to receive user creation requests sent by the synchronization server. The user creation request includes username, password and user permission data. The processing module is used to process the user's new user request, complete the user configuration, and generate a user configuration file, which includes the username, the password, and the user permission data. The sending module is used to send the user configuration file to the synchronization server.

16. A user configuration synchronization device for a network-attached storage server group, characterized in that, include: The receiving module is used to receive the user configuration file sent by the synchronization server. The user configuration file includes the username, password and user permission data. The configuration module is used to configure users based on the user configuration file.

17. A server, characterized in that, include: Processor, memory, communication interface; The memory is used to store the executable instructions of the processor; The processor is configured to execute the user configuration synchronization method for the network-attached storage server group as described in any one of claims 1 to 5, any one of claims 6 to 8, or any one of claims 9 to 13 by executing the executable instructions.

18. A readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the user configuration synchronization method for a network-attached storage server group as described in any one of claims 1 to 5, any one of claims 6 to 8, or any one of claims 9 to 13.

19. A computer program product, characterized in that, Includes a computer program, which, when executed by a processor, is used to implement the user configuration synchronization method for a network-attached storage server group as described in any one of claims 1 to 5, any one of claims 6 to 8, or any one of claims 9 to 13.

Images