JP4430456B2 - Network storage system, user management server and user management server program - Google Patents

Description

  The present invention relates to a technology for updating data stored in a storage device in a network storage system in which a computer terminal acquires data necessary for use of the computer terminal from the storage device via a network.

  Conventionally, it is possible to store data such as an operating system (hereinafter referred to as OS) or application software necessary for the operation of a computer terminal in a storage device installed outside the computer terminal and obtain it via a network. A network storage system is known (see Patent Document 1).

  In the invention according to Patent Document 1, since data necessary for use of a computer terminal can be stored in a storage device without being stored in a hard disk built in each computer terminal, a new version of an OS or application software can be stored. It is expected that network storage system administrators, etc., will perform batch storage data update processing such as computer virus removal and computer virus removal without depending on the voluntary implementation of each computer terminal user. it can.

  Further, although the technical field to which the invention belongs differs in that the data update target is a database rather than a storage device (file system), for example, the invention described in Patent Document 2 is known as a database update method.

The invention according to Patent Document 2 is triggered by the fact that a database having the same contents is separately created by copying the contents of the database to be updated, the copy destination database is updated, and the search service by the copy source database is terminated. In this method, the database is opened to the database user.
JP 2002-123400 A Japanese Patent No. 2506475

  In the conventional system corresponding to Patent Document 1, a problem occurs when the storage apparatus is connected to one or more computer terminals (hereinafter, PCs) at the time of updating data stored in the storage apparatus. . The problem is caused by the fact that the OS of the PC and the OS of the server responsible for storage update (hereinafter referred to as storage management server) access the same storage device, and is as follows.

  When the storage management server updates the data stored in the storage device, the data update is unpredictable for the OS of the PC connected to the same storage device. In this state, when the PC reads the data at the update location, there is a possibility that the operation of the OS of the PC or application software that operates on the OS becomes abnormal. In addition, if the PC writes data in the same location in this state, the data stored in the storage device may be destroyed.

  Here, a problem similar to the above also exists in a system in which a PC and a database are connected via a network and a user can search a database using the PC. This problem has been solved by the invention described in Patent Document 2, but the invention cannot be applied to a network storage system as it is.

  The present invention has been made to solve the above-described problem, and updates of data stored in a storage apparatus connected to a PC are abnormal in an OS or application software activated on the PC. An object of the present invention is to realize a network storage system that can be implemented while preventing the operation and destruction of data stored in the storage device.

The present invention for solving the above-described problems is an invention relating to a network storage system in which a PC is connected to a storage apparatus via a network and can acquire data necessary for the operation of the PC. A user management server having a function of authenticating a user who wants to connect to the server, managing identification information of the storage device corresponding to the user, and notifying the PC of the identification information of the storage device corresponding to the user whose authentication is normal. Further, the storage device to be updated is accessed, the data stored in the storage device is copied to another storage device, the data is updated to the copy destination storage device, and the copy source storage device is updated. For the users who are to be connected, a storage management server having a function of changing registration of the user management server is provided so that all users will be connected to the copy destination storage device in the future. The PC by the user between the time when the authentication by the server is normal and the identification information of the storage device to be used by the user is notified to the PC and the time when the notification of disconnection from the storage device is received from the PC Recognizing that the connection to the storage device is still And it performs the same processing for over The. When an inquiry is received from the storage management server or other device, a list of users and PCs connected to the storage device is searched and returned .

In the present invention, the data of the storage device to be updated is copied to another storage device without directly updating the data to the storage device to be updated, and the data is updated to the copy destination storage device. Accordingly, it is possible to prevent an abnormal operation of the PC due to an unexpected data update for the PC connected to the copy source storage apparatus. Further, it is possible to promptly notify the user connected to the update target (copy source) storage device that the data in the storage device is updated.

Another invention for solving the above-mentioned problems is that the storage management server in the above invention manages all users who are to be connected to the copy source storage device so that they will be connected to the copy destination storage device in the future. instead of registering changes of server, user, so that it can connect by selecting one of the copy source storage apparatus or a copying destination storage device, characterized by having a function to change the management information of the user management server The user management server receives the notification that the authentication by the user management server is normal and the identification information of the storage device to be used by the user is notified to the PC and the connection with the storage device is disconnected from the PC. It is recognized that the connection of the PC to the storage device by the user continues between the time points. And performs a similar process for other users. When an inquiry is received from the storage management server or other device, a list of users and PCs connected to the storage device is searched and returned .

In this invention, the data of the storage device to be updated is copied to another storage device without updating the data directly to the storage device to be updated, and the data is updated to the copy destination storage device. Since the user can select and connect either the copy source storage device or the copy destination storage device, it is possible to prevent abnormal operation of the PC due to unexpected data update. The latest data can be selectively used. Further, it is possible to promptly notify the user connected to the update target (copy source) storage device that the data in the storage device is updated.

Still another invention for solving the above-mentioned problems is that, in addition to the configuration of the above-mentioned invention , after the data update of the storage device is completed, a list of users and PCs connected to the copy source storage device is retrieved, and the copy source storage device If one or more connected PCs exist, the PC is notified that the update of the storage device has been completed.

  According to the present invention, a user who is connected to the update target (copy source) storage device can be notified immediately that the data update of the storage device has been completed. Reconnection to the copy destination storage device can be performed, and use of the PC with the latest data can be resumed.

Another inventions for solving the above problems, in addition to the above structure, the user management server, identification information of the authentication result storage device users should use became normal before notifying on your PC, the storage If the device is the copy source storage device, check whether the corresponding copy destination storage device is being updated, and if the copy destination storage device is being updated, notify the PC to that effect, The received PC displays on the display device of the PC to confirm to the user whether or not to connect to the copy source storage device, and the user displays the input device of the PC. When an input indicating that the user wishes to connect to the copy source storage apparatus is made, the PC and the copy source storage apparatus are connected.

  According to the present invention, a storage device that is being updated (notifying a user who intends to connect a PC to a writable storage device in advance that the data in the storage device is being updated) Writing to the copy source storage apparatus) is avoided while relying on the user's own judgment. As a result, a system that avoids meaningless writing to the copy source storage device that will eventually be discarded, and cancels data update to the copy source storage device if there is a write to the copy source storage device (a later-described first process). 11), the data update can be completed early without stopping the data update by the user's writing.

In another invention for solving the above-mentioned problem, in addition to the configuration of the above invention , before copying data from the copy source storage device to the copy destination storage device, the storage management server inquires about the user connected to the copy source storage device, A data update start notification is displayed on the display device of the PC being used by the user.

  In this invention, the storage device (copying) after the update is started is notified in advance to the user who is connected to the PC, particularly to the writable storage device, that the data in the storage device is updated. The original storage device is avoided while leaving the user's self-determination. As a result, a system that avoids meaningless writing to the copy source storage device that will eventually be discarded, and cancels data update to the copy source storage device if there is a write to the copy source storage device (a later-described first process). 11), the data update can be completed early without stopping the data update by the user's writing.

Another invention for solving the above-mentioned problem is that, in addition to the configuration of the above-mentioned invention , the PC temporarily stores data acquired from the storage device (hereinafter, the stored data is referred to as read cache data), After that, if the data requested to be read from the PC is in the read cache data, the data is returned to the PC without accessing the storage device, while the PC requests to write to the storage device. And a cache device for temporarily storing the data without immediately writing it to the storage device (hereinafter, the stored data is referred to as write cache data) and writing the data to the storage device later. To do.

  In the present invention, if the data requested to be read from the PC is in the read cache data, the data in the read cache data is transferred to the PC without making a read request to the storage apparatus. The data requested to be written by the PC is once written in the cache device. Therefore, the access performance to the storage device as seen from the PC can be improved.

Another invention for solving the above-described problem is that, in addition to the configuration of the above-described invention , if there is no computer connected to the copy source storage apparatus as a result of searching for the PC connected to the copy source storage apparatus, The read cache data read from the copy source storage apparatus and the write cache data to be written to the copy destination storage apparatus remaining in the apparatus are erased.

  In this invention, the cache data storage device (memory, hard disk, etc.) provided in the cache device is saved by deleting from the cache device the cache data related to the copy source storage device that is no longer used after the data update is completed. Furthermore, it is possible to prevent abnormal operation of the PC due to misuse of the remaining cache data.

Another invention for solving the above-mentioned problem is that, in addition to the configuration of the above-mentioned invention , before the data copying, the read cache data corresponding to the copy source storage device existing in the cache device is deleted, or from the copy source storage device. The data read out and temporarily stored in the PC (hereinafter referred to as OS read cache data) is deleted.

  In the present invention, before the data update to the copy source storage apparatus, the read cache data and the OS read cache data read from the storage apparatus are erased, so that the PC stores the read cache data and the OS read cache data. Misuse and prevent the PC from operating abnormally.

Another invention for solving the above-mentioned problem is that, in addition to the configuration of the above-mentioned invention , before the data copying, the write cache data corresponding to the copy source storage device existing in the cache device is stored in the storage device or before that. In addition, data (hereinafter referred to as OS write cache data) that is temporarily stored in the PC and finally stored in the storage device is transferred to the cache device.

  In the present invention, before the data update to the copy source storage device, the write cache data or the OS write cache data to be written to the storage device is written to the storage device and then the data is copied. Data can be updated while reliably reflecting in the storage device.

Another invention for solving the above-described problem is that, in addition to the configuration of the above invention , if the cache device detects a write request to the copy source storage device during data update from the PC, the data for the corresponding copy destination storage device is stored. It has a function of canceling the update, and this function is activated when the data update of the storage device is started, and is released when the data update of the storage device is completed.

  In this invention, the update of data in the copy destination storage device is stopped when a write request to the copy source storage device is detected, and the subsequent processing is also stopped. Therefore, the user reflects the data written by the user in the storage device. Therefore, the use of the storage device can be continued.

  According to the present invention, data update processing is not directly performed on a storage device in which data to be updated is stored, but the data to be updated is actually copied to another storage device. Then, data update processing is performed on the copy destination storage apparatus. Since there is no PC connected to the copy destination storage apparatus, problems such as abnormal operation of the OS and application software of the PC and storage data destruction due to write contention are solved.

  In addition, when a write request is made to the copy source storage device by the PC while the storage device data is being updated, the write request is accepted, the update of the copy destination storage device is stopped, and the PC is continued. Since the use of the copy source storage device can be permitted, the storage data can be updated without impairing the convenience of the user using the PC.

  Further, it is not necessary to update the data in the storage device while aiming at a time zone (for example, at night) when there is no PC connected to the storage device, or while confirming the presence or absence of the PC connected to the storage device. As a result, security threats (existence of security holes and PC viruses in the OS) caused by data stored in the storage device can be solved efficiently and quickly.

  Hereinafter, a network storage system according to an embodiment of the present invention will be described with reference to the drawings.

[First Embodiment]
Figure 1 is a Ru overall view showing a network storage system according to the first embodiment of the present invention.

  In FIG. 1, one or more PCs (PC 1 to 3), a DHCP (Dynamic Host Configuration Protocol) server 4, a TFTP (Trivial File Transfer Protocol) server 5, a cache device 6, a user management server 7, a storage management server 8, 1 Two or more storage devices 10 to 30 are connected via a TCP / IP (Transmission Control Protocol / Internet Protocol) network 40. Each device is assigned an IP address, and communication by TCP / IP is possible between the devices.

  Each storage apparatus 10-30 has one or more targets (101-103) for storing data, and the target has one or more logical units (hereinafter, LU), and each LU 11 -33 are assigned users (multiple users may be assigned to one LU or not all users may be assigned), and data necessary for the user to operate the PC (for example, , OS, application software, etc.).

  In addition, iSCSI (Internet Small Computer System Interface) is assumed as a communication protocol between each of the PCs 1 to 3 and the cache device 6 and between the cache device 6 and each of the storage devices 10 to 30, but can be transferred by TCP / IP. The IP storage access protocol is not limited to iSCSI.

  Here, instead of connecting the storage apparatuses 10 to 30 to the TCP / IP network 40, a storage router can be connected. A storage device having a communication function using a storage access protocol other than iSCSI, such as a fiber channel (hereinafter referred to as FC), is connected to the storage router via a network separate from the TCP / IP network 40. , Protocol conversion is performed between iSCSI and FC, etc., and communication between the cache device 6 and each storage device is relayed.

  In FIG. 1, even if all or part of the storage devices 10 to 30 are replaced with the storage router, the storage router operates without any problem. However, in the following description, it is assumed that the storage router is not used as expressed in FIG. 1.

  FIG. 2 is a block diagram illustrating a configuration example of the user management server and the storage management server according to the first embodiment of this invention. The user management server 7 includes a transmission / reception unit 71 that transmits / receives data to / from an external device, a user authentication unit 72 that performs user authentication, an LU allocation management unit 73 that manages LU allocation for each user, and a user name. The LU assignment management table 74 in which the corresponding password and assigned LU are recorded, the LU connected user management unit 75 for managing user information connected to the LU, the LU identification information corresponding to each LU, the connected user and PC Are stored in the LU connected user management table 76.

  The storage management server 8 includes a transmission / reception unit 81 for transmitting / receiving data to / from an external device, a data update necessity recognition unit 82 for recognizing the necessity for data update, and an LU for each storage device prior to data update. A data copy instructing unit 83 for instructing copying of data therein, a data updating unit 84 for updating data, an LU state managing unit 85 for managing the LU state, an LU state management table 86 for recording the state of each LU, An LU connection state inquiry unit 87 that inquires the user management server 7 about the LU connection state, an update end notification unit 88 that notifies each PC of the end of data update, and a cache data deletion instruction unit 89 that instructs the deletion of cache data. .

  3 and 4 are diagrams showing an example of a management table held in the user management server 7. FIG. 3 shows a data configuration example of the LU allocation management table 74. The LU assignment management table 74 manages the corresponding password and logical unit (LU) ID for each user name. The LUID is a code for identifying the LU. If the code is given, the corresponding unique LU is determined.

  FIG. 4 shows a data configuration example of the LU connected user management table 76. The LU connected user management table 76 is a table for managing the LU ID, the corresponding LU identification information, and the list of connected users and PCs for each LU. That is, as shown in FIG. 4A, LU identification information and connected user management information are recorded corresponding to each LUID. In the connected user management information field, information on a set of a user name and a PC connected to the LU is recorded.

  As shown in FIG. 4B, the LU identification information includes the IP address and port number of the storage device to which the LU belongs, the ID of the target to which the LU belongs in the storage device, and the LU identification in the target. This is a combination of logical unit numbers (hereinafter referred to as LUN). Alternatively, a combination of a target name to which the LU belongs and a LUN may be used. In the following description, this combination is simply referred to as “LU identification information” unless otherwise required.

  According to the LU allocation management table 74 shown in FIG. 3 and the LU connected user management table 76 shown in FIG. 4, for example, the users A, D, and E are connected to the LU with LUID = 0, that is, the LU 11. , Users B and C are connected to LUID = 1 (LU12) and LUID = 2 (LU21), respectively. Further, user A is connected from PC1 to LU11 (LUID = 0) and user E is connected from PC5, while user B is connected from PC2 to LU12 (LUID = 1).

  FIG. 5 is a diagram showing a data configuration example of the LU state management table 86 held by the storage management server 8. The LU status management table 86 manages the IDID, the corresponding LU identification information, and the update status of the LU for each LU. There are four types of LU status to be managed: “available”, “updating”, “update completed”, and “empty”, for example.

  The “usable” state is a state in which a PC is connected to the LU and normal access such as data reading and writing is possible.

  The “Updating” status indicates that data is being copied to another LU (copy destination LU) or the data in the copy destination LU has been updated for the purpose of updating the data stored in the LU (copy source LU). It is in a state.

  The “update complete” state is a state in which the data update of the copy destination LU has been completed, but there is still a PC connected to the copy source LU, and it is not possible to shift to the following “empty” state.

  The “empty” state is an unused state and may be selected as a copy destination LU when data is updated. The copy destination LU in the “updating” state is also “empty”.

  The LUID need not be the same as the LUID managed by the user management server 7 (see FIGS. 3 and 4). In FIG. 5, it is the same for simplification of explanation.

  FIG. 6 is a diagram illustrating a processing sequence from when the power of the PC 1 is turned on until the PC 1 transmits an authentication request to the user management server 7. In FIG. 6, reference numeral 200 denotes a user A of the PC 1. Hereinafter, a description will be given according to (A) to (H) shown in FIG.

  (A) When the power of the PC 1 is turned on, (B) the PC 1 transmits a DHCP request to the DHCP server 4 and (C) receives the DHCP response, the PC 1 receives the IP address in the TCP / IP network 40. To win. (D) Further, in the DHCP response, the IP address of the TFTP server 5 and the bootstrap file name to be downloaded from the TFTP server 5 are also described, and the PC 1 receiving the DHCP response sends it to the designated TFTP server 5. A bootstrap file acquisition request is sent, (E) a designated bootstrap file is downloaded from the TFTP server 5, (F) is expanded in a RAM (Random Access Memory) in its own PC 1, and executed (bootstrap activation).

  In the bootstrap file, the user A 200 inputs a user name and password, and a user authentication function for transmitting an authentication request based on the input result to the user management server 7. Includes at least a program having an iSCSI initiator function for connecting a PC. As a result of the execution of the program having the former function, (G) a user name and password are input from the user A200, and (H) an authentication request based on the user name and password input by the user A200 as shown in FIG. Can be transmitted to the user management server 7.

  Here, it should be noted that there are two aspects of the PC 1 in the network storage system. One is a case where the PC 1 does not have a built-in disk device (so-called diskless PC), and even the OS required to start the PC 1 is stored in the storage device. In this case, there is no data in the PC 1 immediately after the power is turned on, and the bootstrap file does not exist even if an attempt is made to connect to the storage device in order to acquire data. In this case, bootstrap file acquisition processing as shown in FIG. 6 is required.

  The second case is a case where the PC 1 has a built-in disk device and data necessary for the operation of the PC 1 is stored separately in the built-in disk device of the PC 1 and a storage device. For example, the minimum data necessary for the operation of the PC 1 (such as an OS) and common data (such as word processor and spreadsheet software application programs used by everyone) are stored in the internal disk device, and individual data of the user A 200 This is a case where (a document file or the like) is stored in the storage device (and vice versa).

  In this case, since the program having the user authentication function and the iSCSI initiator function can be stored in the built-in disk device of the PC, the bootstrap file acquisition process as shown in FIG. 6 becomes unnecessary. Therefore, the TFTP server 5 in FIG. 1 is also unnecessary, and if each PC holds an IP address in a fixed manner, the DHCP server 4 is also unnecessary.

  The network storage system of the present invention operates without questioning whether each PC is the former or the latter. However, in the following description, it is assumed that the former case (each PC is a diskless PC) is assumed. To do. In FIG. 7 and subsequent figures, the description of the communication process between the PC 1 and the DHCP server 4 or the TFTP server 5 is omitted in the diagrams showing the processing sequences, and (A) to (G) surrounded by the dotted lines in FIG. ) Is simply described as “activation”.

  FIG. 7 is a diagram showing a processing sequence when the PC 1 is connected to the storage apparatus 10 in the network storage system of FIG. Hereinafter, a description will be given according to (A) to (I) shown in FIG.

  (A) For example, the user A 200 who uses the PC 1 and tries to acquire necessary data by connecting to the storage apparatus 10 activates the PC 1. After the PC 1 is activated, a user name and password are input to the PC 1, and (B) the PC 1 sends an input user name and password to the user management server 7 to make an authentication request.

  (C) The user management server 7 confirms the validity of the password, and if the password is valid, searches for the LU assigned to the user A200. Here, the LU 11 is searched. (D) The user management server 7 records that the user A is connected from the PC 1 to the LU 11 of the LU connection user management table 76, and (E) notifies the identification information of the LU 11 as an authentication response.

  (F) Receiving the notification of LU identification information, the PC 1 connects its own PC 1 to the LU via the TCP / IP network 40. Thereafter, the user A 200 can freely access the data stored in the LU 11 using the PC 1.

  (G) If connection to the LU 11 becomes unnecessary for the user A 200, the user A 200 operates the PC 1 to disconnect the connection to the LU 11. (H) At this time, the PC 1 transmits a disconnection notification to the user management server 7. (I) The user management server 7 recognizes that the LU 11 in the storage apparatus 10 is disconnecting for the user A200. The in-connection information of user A in the LU connection user management table 76 is deleted.

Regarding (H) and (I), for example, if the PC 1 suddenly terminates abnormally due to a failure or an erroneous operation, a disconnection notification may not be transmitted to the user management server 7. As a handling method in this case, for example, the following method can be used.
(i) Even if PC1 terminates abnormally, leave it as it is and treat it as connected. Next time, when the PC 1 authenticates to the user management server 7, a warning is issued and disconnection is confirmed.
(ii) The user management server 7 periodically checks whether the connected PC 1 is activated or not activated, and determines that the connection is broken when it is detected that it is not activated. .

  FIG. 8 is a diagram showing a processing sequence when the data stored in the LU 11 needs to be updated when the PC 1 and the LU 11 are connected. Hereinafter, a description will be given according to (A) to (H) shown in FIG.

  (A) When the storage management server 8 recognizes the necessity of data update, (B) selects an empty LU 11 ′ having a data capacity equal to or greater than the total amount of data stored in the LU 11, and stores the data stored in the LU 11. Are all copied to the LU 11 ′. (C) As a result, data is copied from the LU 11 to the empty LU 11 ', and (D) when copying is completed, the completion of data copying is notified.

  (E) Next, the storage management server 8 updates data to the LU 11 '. As a result, the data of the LU 11 'is updated. (F) When the data update of the LU 11 ′ is completed and the notification is received, (G) the storage management server 8 notifies the user management server 7 of the assigned LU switching, and (H) the user management server 7 Then, registration change processing for reassigning LU 11 ′ is performed for all users (including user A 200) to which LU 11 is assigned. This is done by changing the logical unit (LU) ID field of the LU assignment management table 74.

As a method for copying data from the LU 11 to the LU 11 ′ in (C), for example, the following method can be used according to the function of the storage apparatus.
(i) When using a storage device having a data copy function between LUs, copy is executed using the data copy function.
(ii) When using a storage device having a snapshot / shadow copy function, the snapshot is used to implement copying.
(iii) When using a storage device having a volume multiplexing function, use one of the synchronized volumes as the copy destination. This is a case where the copy destination LU originally exists and is used. In the case of (iii), it is only necessary to specify volume multiplexing in advance. The instruction for copying at the time of data update can be omitted.

  Any of the above methods (i) to (iii) may be used for copying data in the present embodiment. When the storage apparatus has the functions as described above, it is possible to realize efficient data copying by using the functions. Further, the method is not limited to the above methods (i) to (iii), and other methods may be used. The same applies to the other embodiments.

  Next time, when the user A 200 restarts the PC 1 or when the user who has been connected to the LU 11 and starts up the PC 1 starts up the PC, it always connects to the LU 11 ′ and starts up the PC. It becomes. Here, as an example of the reason why the data needs to be updated, the OS security patch was supplied from the OS manufacturer and it was necessary to apply it urgently, and the OS or application program needs to be upgraded. It can be mentioned that a virus was detected by computer virus inspection and that it was necessary to remove the virus, but the cause is not limited to those exemplified.

  The LU 11 'may belong to a target to which the LU 11 belongs, or may belong to a target or storage device to which the LU 11 does not belong.

  FIG. 9 is a diagram showing a processing sequence in the case where there is a user who continues to connect to the LU 11 even after the data update for the LU 11 'is completed. Hereinafter, a description will be given according to (A) to (E) shown in FIG.

  (A) After the data update for the LU 11 ′ is completed, the storage management server 8 inquires of the user management server 7 about the connection state to the LU 11. (B) The user management server 7 searches the LU connection user management table 76 and (C) returns a list of combinations of user names and PCs connected to the LU 11. For example, if the user A200 is still connected to the LU 11, the user management server 7 returns a combination of “user A, PC1”.

  (D) The storage management server 8 that has received the notification notifies the PC 1 that the update of the LU 11 has been completed. (E) Upon receiving the notification, the PC 1 prompts the user A 200 to restart the PC 1 by displaying a display screen indicating the end of the update.

  If a user or PC connected to the LU 11 exists in addition to “User A, PC 1”, the same notification is also given to the PC at the same time. The update completion notification to the user connected to the copy source storage device may be made only once immediately after the data update is completed, and then periodically until there is no user connected to the copy source storage device. May or may not be done at all. The choice depends on the management concept of the network storage system.

  FIG. 10 is a diagram showing a processing sequence when a user and a PC connected to the copy source storage apparatus LU11 no longer exist. Hereinafter, a description will be given according to (A) to (F) shown in FIG.

  (A) As in the case of FIG. 9, the storage management server 8 queries the user management server 7 for a list of combinations of users and PCs connected to the LU 11. (B) As a result, if it is found in the user management server 7 that no user or PC is connected to the LU 11, (C) the storage management server 8 is notified accordingly. (D) The storage management server 8 requests the cache device 6 to erase the read cache data read from the LU 11. (E) The cache device 6 erases the read cache data in response to the request, and (F) notifies the storage management server 8 of the completion of erasure of the read cache data.

  After erasing the read cache data, the data stored in the LU 11 that is no longer necessary may be left or erased. Which one to select depends on the concept of network storage system management. For example, if a computer virus is found in the data stored in the LU 11, the cause of the data update is that it is not desirable that the computer virus remains in the storage device 10, so the data in the LU 11 is immediately deleted. It is possible.

  The LU 11 can be used again as the copy destination of the update target data next time when data of another LU becomes the update target. If LU11 and LU11 ′ are determined as a combination of a data copy source and a data copy destination LU at the time of data update, data is copied from LU11 ′ to LU11 immediately after erasing the read cache data, and stored in LU11 ′. You may wait until the next time the need to update the data occurs. In that case, data copying in FIG. 8 is not necessary.

  FIG. 11A is a diagram illustrating an example of a user authentication processing flow of the user management server 7. When the user management server 7 receives the user name and password from the PC 1 (step S1), the user management server 7 refers to the LU assignment management table 74 to determine whether the password is valid (step S2). If the password is valid, the user and PC1 information is added to the connected user management information field of the LU connected user management table 76 (step S3), and the LU identification information assigned to the user is notified as an authentication response (step S3). Step S4). If the password is not valid in step S2, the user authentication is regarded as an error (step S5).

  FIG. 11B is a diagram illustrating an example of a connection disconnection process flow of the user management server 7. When the user management server 7 receives a disconnection notification from the PC 1 to the LU (step S11), the LU connected user management unit 75 deletes the information about the user and the PC 1 from the LU connected user management table 76 (step S11). S12).

  FIG. 12A is a diagram showing an example of an assigned LU switching process flow of the user management server 7. When the user management server 7 receives an allocation LU switching instruction from the storage management server 8 to, for example, LU 11 to LU 11 ′ (step S21), the LU allocation management unit 73 allocates, for example, LU 11 in the LU allocation management table 74. LU 11 ′ is reassigned to all users (step S22).

  FIG. 12B is a diagram illustrating an example of a search processing flow for a connected user and PC of the user management server 7. When the user management server 7 receives an inquiry about the connection status from the storage management server 8 to the LU 11 (step S31), the user management server 7 searches the LU connected user management table 76 (step S32), and the user name and PC connected to the LU 11 are searched. Is returned (step S33).

  FIG. 13 is a diagram showing an example of an update process flow of the storage management server 8. When the storage management server 8 recognizes the necessity of updating (step S41), it instructs the copying from the LU 11 to the LU 11 ', for example (step S42). When the copy completion notification from the LU 11 to the LU 11 'is received (step S43), the LU 11' is updated (step S44).

  The storage management server 8 instructs the user management server 7 to reassign the LU 11 'for all users to which the LU 11 has been assigned (step S45). In addition, the storage management server 8 inquires of the user management server 7 about the connection state to the LU 11 (step S46), and notifies the update completion of the LU 11 to the user connected to the LU 11 (step S47).

  FIG. 14 is a diagram showing an example of the cache data erasing process flow of the storage management server 8. The storage management server 8 inquires of the user management server 7 about the connection state to the LU 11 (step S51), and determines that there are no users or PCs connected to the LU 11 (step S52). A request is made to erase the read cache data read from the LU 11 (step S53), and the process is terminated.

[Second Embodiment]
Next, we describe a second embodiment of the present invention.

  The first embodiment is an example on the assumption that the LU 11 of the storage device 10 to be updated is read-only. On the other hand, when writing to the storage device to be updated is permitted, the problem cannot be avoided only by the processing described in the first embodiment. Therefore, an example suitable for the case where writing to the storage device 10 to be updated is permitted will be described in detail below.

  FIG. 15 is a block diagram illustrating a configuration example of a user management server and a storage management server according to the second embodiment of this invention. Reference numeral 100 denotes a user management server, and 110 denotes a storage management server.

  In addition to the components of the user management server 7 shown in FIG. 2, the user management server 100 includes an LU status inquiry unit 77 that queries the storage management server 110 for the LU status. In addition to the components of the storage management server 8 shown in FIG. 2, the storage management server 110 includes an update start notification unit 90 that notifies the PC 1 of the start of update based on the inquiry result of the LU connection state inquiry unit 87, and the cache device 6 A write monitoring control unit 91 that controls the write monitoring by the update monitoring unit 91 and an update cancellation instruction unit 92 that issues an LU update cancellation command to each storage device.

  FIG. 16 is a sequence diagram when the user A 200 turns on the power of the PC 1 and the PC 1 acquires and starts data stored in the storage apparatus 10. Of the processes from (A) to (H) shown in FIG. 16, the difference from the case of the first embodiment shown in FIG. 7 is that the identification information of the LU 11 assigned to the user A 200 is notified to the PC 1. Before processing, the storage management server 110 has a process of confirming whether the LU 11 is updating data (whether the LU 11 is the copy source and the corresponding copy destination LU 11 ′ is being updated). (D and E in FIG. 16). As a result of the confirmation, if the LU 11 is not being updated, the process is the same as in the first embodiment (FIG. 7).

  FIG. 17 is a diagram showing a sequence when the LU 11 is being updated as a result of the confirmation in FIG. When a notification that data is being updated is received from the user management server 100 that has received an authentication request from the PC 1, as shown in FIGS. , LU 11 is being updated as an authentication response. (G) Upon receiving this notification, the PC 1 displays on the display screen or the like provided in the PC 1 that the LU to be connected to the PC 1 is being updated, and whether or not to forcibly connect even in that case. A display confirming the intention of the user is displayed and the user is prompted to select it.

  (H) As a result, when the user A 200 inputs that the PC 1 is forcibly used, (I) a forced connection request is transmitted to the user management server 100. The subsequent processes (J) to (L) are the same as those in the first embodiment shown in FIG.

  FIG. 18 is a diagram showing a processing sequence when the data stored in the LU 11 needs to be updated when the PC 1 and the LU 11 are connected. This processing sequence shown in FIGS. 18A to 18V has many points in common with the first embodiment (FIG. 8), but has three different points.

  First, immediately after the storage management server 110 recognizes the necessity of updating the data stored in the LU 11, it queries the user management server 100 for a list of user names and PCs connected to the LU 11. This is a point of having a process of notifying the user connected to the LU 11 of the start of data update (data copying from the LU 11 to the LU 11 ′). The method is the same as that of the first embodiment (FIG. 9).

  Second, immediately after the processing, the cache device 6 shifts to a state in which a write request to the LU 11 is monitored according to an instruction from the storage management server 110. This state is a state having a function of notifying the storage management server 110 when the cache device 6 detects a write request from the PC 1 to the LU 11, and the data update is completed. As shown in (T), until a release request is received from the storage management server 110 or a write request to the LU 11 is detected for the first time after the transition to the state (described later, the OS write cache data is instructed by an instruction from the storage management server 110) Continue until writing).

  Third, in response to an instruction from the storage management server 110, the OS read cache data of the PC 1 and the read cache data of the cache device 6 are erased, and the OS write cache data of the PC 1 is transferred to the cache device 6 to transfer the cache device 6 The write cache data is temporarily stored, and the write cache data is transferred to the LU 11.

  FIG. 19 is a diagram showing a processing sequence when a write request from the PC 1 to the copy source LU 11 is detected while the copy destination LU 11 'is being updated. Hereinafter, a description will be given according to (A) to (L) shown in FIG.

  (A) A write request from the PC 1 to the copy source LU 11 is detected by the (B) cache device 6, and (C) the cache device 6 that has detected the write request stores that the LU 11 has been requested for storage management. The server 110 is notified. (D) Upon receiving the notification, the storage management server 110 stops updating the data for the LU 11 ′, (E) the cache device 6 releases the write monitoring state, and thereafter, as in (F) to (L), The PC 1 can continue to use the LU 11.

  When a user connected to the LU 11 frequently makes a write request ignoring that the LU is being updated, the update of the data stored in the LU 11 is delayed, so the concept of management of the network storage system Depending on the case, the processing of FIG. 19 may not be performed.

  Next, how a combination of a user name and a PC is added to or deleted from the connected user management information field of the LU connected user management table 76 will be described in detail. For example, the combination of “user A, PC1” in the connected user management information field is added or deleted through the following processing.

  Assume that there is no combination of “user A, PC1” in the connected user management information field of the LU connected user management table 76 shown in FIG. In this state, if the authentication request is received from the PC 1 activated by the user A and the validity of the password is confirmed as in the first embodiment of FIG. 7, the LU identification information corresponding to LUID = 0. = LU11 is returned as an authentication response. At this time, “user A, PC1” is added to the connected user management information field of the LU connected user management table 76. This process is performed in the same manner in the second embodiment shown in FIGS.

  Next, “User A, PC1” is deleted by receiving a disconnection notice from users A and PC1.

  The allocation LU switching performed in the sequence according to the first embodiment of FIG. 8 and the sequence according to the second embodiment of FIG. 18 is performed by the logical unit (LU) of the LU allocation management table 74 shown in FIG. This is done by changing only the ID field.

  9 and 10 and the sequence according to the second embodiment in FIG. 18 are used to search for users and PCs connected to a specific LU in FIG. This is done by referring to the connected user management information field of the LU connected user management table 76 shown.

  FIG. 20 and FIG. 21 are diagrams showing changes in the contents recorded in the LU status management table 86 as the data update process proceeds. In the state shown in FIG. 20A, LUID = 0, 1, 2 (LU11, 12, 21) is “usable”, and LUID = 3 (LU11 ′) is “empty”. This represents the LU state management table 86 in a state before the necessity of data update is recognized. The recorded contents of the LU status management table 86 change as follows as the update processing of data stored in the LU 11 progresses.

  When the necessity of updating the data stored in the LU 11 is recognized, the storage management server 8 or 110 selects the LU 11 ′ as a copy destination of the data stored in the LU 11. As a result, in the LU status management table 86, as shown in FIG. 20B, the LU update status information corresponding to LUID = 0 (LU11) changes to the “Updating” status.

  The “updating” state is a state where data stored in the LU 11 is copied to the LU 11 ′, or a state where copying is completed and data in the LU 11 ′ is being updated. “3” written in the LU update status information field is a logical unit (LU) ID of the LU 11 and indicates a mutual relationship in which data stored in the LU 11 is copied to the LU 11 ′. At this time, the state of the LU 11 ′ remains “empty”.

  Next, when the data update of the LU 11 'is completed, the contents of the LU state management table 86 change as shown in FIG. The LU 11 ′ is no longer required because the data update of the LU 11 ′ has been completed, but there is a possibility that a PC connected to the LU 11 still exists. Therefore, the LU 11 is set to the “update complete” state, and the storage management server 8 inquires the user management server 7 for a list of users and PCs connected to the LU 11 as shown in FIGS. 9 and 10, for example.

  As a result, if there are a user and a PC connected to the LU 11, as shown in the first embodiment of FIG. 9, an update completion notification is sent to the PC, and the status of the LU 11 is set to “update complete”. maintain. On the other hand, if there is no user and PC connected to the LU 11, the read cache data is erased as in the first embodiment of FIG. 10, and the LU status management table 86 is as shown in FIG. change.

  FIG. 22 is a diagram illustrating an example of a user authentication processing flow of the user management server 100 according to the second embodiment. When the user management server 100 receives the user name and password from the PC 1 (step S61), the user management server 100 refers to the LU assignment management table 74 to determine whether the password is valid (step S62).

  If the password is not valid, the user authentication is regarded as an error (step S68). If the password is valid, it is determined whether the LU assigned to the user (for example, LU11) is being updated (step S63). If the LU 11 is not being updated, the user and PC 1 information is added to the connected user management information item in the LU connected user management table 76 (step S66), and the LU identification information corresponding to the LU 11 assigned to the user is authenticated. Notification is made as a response (step S67).

  If the LU 11 assigned to the user is being updated in step S63, the PC 1 is notified as an authentication response that the LU 11 is being updated (step S64). If a forced connection request from the PC 1 to the LU 11 is received (step S65), the process proceeds to step S66. If no forced connection request is received, nothing is done.

  FIG. 23 is a diagram illustrating an example of an update process flow of the storage management server 110 according to the second embodiment. When the storage management server 110 recognizes the necessity for update (step S71), it queries the user management server 100 for the connection status to the LU 11 (step S72), and starts data update for the user connected to the LU 11. (Step S73). After making a write monitoring start request to the cache device 6 (step S74), the storage management server 110 requests the cache device 6 to erase cache data (step S75).

  Next, the storage management server 110 receives a completion notification for deleting cache data, etc., and then instructs, for example, copying from the LU 11 to the LU 11 ′ (step S76), and receives a copy completion notification from the LU 11 to the LU 11 ′. (Step S77), the update of the LU 11 ′ is started (Step S78).

  When the storage management server 110 receives a write request detection notification from the cache device 6 during the update of the LU 11 ', it issues an update stop instruction (step S85).

  When the update of the LU 11 'is completed (step S80), the storage management server 110 issues a write monitoring cancellation request to the cache device 6 (step S81). Thereafter, the storage management server 110 instructs the user management server 100 to reassign the LU 11 'for all users to which the LU 11 has been assigned (step S82). In addition, the storage management server 110 inquires of the user management server 100 about the connection status to the LU 11 (step S83), and notifies the user connected to the LU 11 of the update completion of the LU 11 (step S84).

[Third Embodiment]
Next, a third embodiment of the present invention will be described. In the first embodiment and the second embodiment, when the user A 200 restarts the PC 1 after updating the data in the storage apparatus 10, the PC 1 is always connected to the copy destination LU 11 ′, and the copy source It is no longer allowed to connect to LU11. However, there are cases where it is more convenient for the user A 200 to connect to the copy source LU 11 even after the PC 1 is restarted. Therefore, an embodiment suitable for this case will be described in detail as a third embodiment.

  The configurations of the user management server 100 and the storage management server 110 according to the third embodiment of the present invention are the same as the configuration example according to the second embodiment shown in FIG.

  FIG. 24 is a diagram illustrating a data configuration example of the LU allocation management table 74 provided in the user management server 100. In the third embodiment of the present invention, the LU assignment management table 74 includes data items such as a password, the ID of the first LU assigned to the user, and the ID of the second LU for each user name. The first LU is the copy destination LU at the time of the latest data update, and the second LU is the copy source LU at the time of the latest data update.

  FIG. 25 shows processing when the user A 200 restarts the PC 1 after the data update of the copy destination LU 11 ′ is completed, and the user A selects a connection to the copy source LU 11 among the copy destination LU 11 ′ and the copy source LU 11. It is the figure which showed the sequence. This is an alternative to the first half ((A) to (F) of FIG. 7) of the processing sequence shown in FIG.

  As shown in (A) to (D) of FIG. 25, the user management server 100 that has received the authentication request from the user A 200 searches the LU allocation table 74 for the LU allocated to the user A 200, and the first LU is the LU 11 If it is determined that the second LU is LU11, an authentication response with the first LU as LU11 'and the second LU as LU11 is returned to the user A200.

  (E) The PC 1 displays the display screen so that the user A selects either LU 11 ′ or LU 11 as a connection target. (F) When the user A selects the LU 11, (G) a connection request is transmitted to the user management server 100. The subsequent processing is the same as the processing of (D) to (F) in FIG.

  FIG. 26 is a diagram showing a processing sequence when inquiring to the storage management server 110 whether or not both the LU 11 ′ and LU 11 are being updated, and returning an authentication response to the PC 1, as in FIG. 16. FIGS. 26A to 26G show a case in which neither LU 11 ′ nor LU 11 is updating data. If any LU is updating data, the fact is also shown in PC1. Is displayed. Here, if the LU whose data is being updated is selected, the PC 1 transmits a forced connection instruction to the user management server 100 as in FIG.

  FIG. 27 is a diagram showing a processing sequence when the storage management server 110 changes the registration of the user management server 100 after the data update of the copy destination LU 11 ′ is completed. Unlike the cases of FIGS. 8 and 18, the user management server 100 manages two LUs, a first LU (copy destination LU at the time of the latest data update) and a second LU (copy source LU at the time of the latest data update) for each user. Will do. Therefore, the user management server 100 that has received an instruction to switch the assigned LU from the LU 11 to the LU 11 ′ changes the first LU assigned to the user to the LU 11 ′, and further changes the second LU to the LU 11. Similar processing is performed for other users to which the LU 11 is assigned as the first LU.

  FIG. 28 is a diagram showing changes in the recorded contents of the LU assignment management table 74 when an assigned LU switching instruction is received. Note that the LU connected user management table 76 when receiving the assigned LU switching instruction is in the state shown in FIG. 4, for example.

  According to the LU assignment management table 74 shown in FIG. 28A, the first LU assigned to the user A is LU11 (LUID = 0), and the second LU is LU11 '(LUID = 3).

  In this state, when an LU switching instruction from the LU 11 to the LU 11 ′ is received as shown in FIG. 27A, the contents of the LU assignment management table 74 are as shown in FIGS. 28A to 28B. To change. That is, for user A, user D, and user E who are assigned the LU 11 corresponding to the first LUID = 0 as the first LU, “3”, which is the LUID value corresponding to the LU 11 ′, is written in the first LUID field. In the 2 LUID field, “0” that is the LUID value corresponding to the LU 11 is written.

  Thereafter, when an authentication request is received from the PC 1 of the user A 200, an authentication response with the first LU as the LU 11 ′ and the second LU as the LU 11 is returned to the PC 1 as shown in FIGS. 25 and 26.

  FIG. 29 is a diagram illustrating an example of a user authentication processing flow of the user management server 100 according to the third embodiment. When the user management server 100 receives the user name and password from the PC 1 (step S91), the user management server 100 refers to the LU assignment management table 74 to determine whether the password is valid (step S92).

  If the password is not valid, the user authentication is regarded as an error (step S98). If the password is valid, for example, whether the LU 11 ′ of the first LU or the LU 11 of the second LU assigned to the user is being updated. Is determined (step S93).

  If neither LU 11 'nor LU 11 is being updated, an authentication response with the first LU as LU 11' and the second LU as LU 11 is returned to the PC 1 (step S94). When a connection request for the selected LU (for example, LU11) is received from the user (step S95), the user and PC1 information is added to the connected user management information field of the LU connected user management table 76 (step S96). The LU identification information corresponding to the LU (for example, LU11) assigned to is notified as an authentication response (step S97).

  If either LU 11 ′ or LU 11 is being updated in step S93, the fact that the first LU is LU 11 ′ and the second LU is LU 11, and the LU being updated is notified as an authentication response (step S99). Proceed to step S95.

  FIG. 30 is a diagram illustrating an example of an assigned LU switching process flow of the user management server 100 according to the third embodiment. When the user management server 100 receives the assigned LU switching instruction from the storage management server 110 (step S101), the user management server 100 changes the first LU to the LU 11 ′ for all users to which the LU 11 is assigned as the first LU in the LU assignment management table 74. The second LU is changed to LU11 (step S102).

  By the way, in the third embodiment, as shown in FIG. 21B, after the data update of the copy destination LU 11 ′ is completed, it is confirmed that there is no user connected to the copy source LU 11. It is not appropriate to immediately set the copy destination LU 11 to “empty”. This is because the state of the LU 11 becomes “empty”, which may cause the LU 11 to be used as a copy destination LU in another future data update.

  This problem can be solved by executing the following procedure and changing the trigger for setting the state of the LU 11 to “empty”.

  First, when the user management server 100 receives an LU 11 connected user inquiry, it is confirmed by referring to the LU connected user management table 76 that there is no user connected to the LU 11. The procedure so far is the same as the example shown in FIG.

  Further, by referring to the second LUID field of the LU assignment management table 74 in FIG. 28B, it is searched whether or not any LU 11 (LUID = 0) is assigned.

  As a result, when one or more users to which the LU 11 is assigned as the second LU are found (in the case of FIG. 28B, there are three users A, D and E), the state of the LU 11 is set to “empty”. Therefore, it is notified to the storage management server 110 or nothing is notified. As a result, the state of the LU 11 managed by the storage management server 110 is maintained as “update completed”, and the content of the LU state management table 86 remains as shown in FIG.

  On the contrary, if there is no user to which the LU 11 is assigned as the second LU, there is no problem even if the state of the LU 11 is “empty”. Notify the management server 110. As a result, the state of the LU 11 changes to “empty”, and the contents of the LU state management table 86 change from FIG. 21A to FIG. 21B.

[Other Embodiments]
In the first to third embodiments, there is no problem even if the role of the user management server and the storage management server is played by one server. In this case, communication between the user management server and the storage management server in FIGS. 7 to 10 and 16 to 19 is performed between a program module having a user management function and a program module having a storage management function in one server. It will be replaced by communication.

  Also, in the first to third embodiments, there is no problem even if any one storage device plays the roles of a user management server and a storage management server. In this case, communication between the user management server, storage management server, and storage device (whose roles are the user management server and storage management server) in FIGS. In this case, the communication is replaced with communication between a module having a storage function, a program module having a user management function, and a program module having a storage management function.

  Furthermore, in the first to third embodiments, there is no problem even if any one computer terminal becomes a storage management server. In this case, the OS and programs necessary for the operation of the storage management server are stored in the storage device, and the storage management server starts up after acquiring data from the storage device after the power is turned on.

  The processing performed by the user management server, storage management server, and the like according to the embodiments described above can be realized by a computer and a software program, and the program can be recorded on a computer-readable recording medium and provided. It can also be provided through a network.

1 is an overall view showing a network storage system. It is a block diagram which shows the structural example of a user management server and a storage management server. It is a figure which shows the example of a data structure of a LU allocation management table. It is a figure which shows the data structural example of a user management table during LU connection. It is a figure which shows the data structural example of LU status management table. It is a starting process sequence diagram of PC. It is a figure which shows the connection process sequence with respect to the storage apparatus of PC. It is a figure which shows the update process sequence of data. It is a figure which shows the update completion notification process sequence to PC. It is a figure which shows a read cache data erasing process sequence. It is a figure which shows an example of a user authentication processing flow and a connection cutting | disconnection processing flow. FIG. 10 is a diagram illustrating an example of an allocated LU switching process flow and a search process flow for connected users and PCs. It is a figure which shows an update process flow. It is a figure which shows an example of a cache data deletion processing flow. It is a block diagram which shows the structural example of a user management server and a storage management server. It is a figure which shows the connection process sequence with respect to the storage apparatus of PC. It is a figure which shows the connection process sequence with respect to the storage apparatus of PC. It is a figure which shows the update process sequence of data. FIG. 6 is a diagram showing a processing sequence when a write request from a PC to a copy source storage apparatus is detected. It is a figure which shows the transition of the recording content of the LU status management table accompanying the progress of the data update process. It is a figure which shows the transition of the recording content of the LU status management table accompanying the progress of the data update process. It is a figure which shows an example of a user authentication processing flow. It is a figure which shows an example of an update process flow. It is a figure which shows the example of a data structure of a LU allocation management table. It is a figure which shows the connection process sequence with respect to the storage apparatus of PC. It is a figure which shows a user authentication process sequence. It is a figure which shows an allocation LU switching process sequence. It is a figure which shows the change of the recording content of the LU allocation management table at the time of receiving allocation LU switching instruction | indication. It is a figure which shows an example of a user authentication processing flow. It is a figure which shows an example of an allocation LU switching process flow.

Explanation of symbols

1,2,3 PC
4 DHCP server 5 TFTP server 6 Cache device 7,100 User management server 8,110 Storage management server 10, 20, 30 Storage device 11, 11 ′, 12, 21, 22, 31, 32, 33 LU
40 TCP / IP network 71, 81 Transmission / reception unit 72 User authentication unit 73 LU allocation management unit 74 LU allocation management table 75 LU connected user management unit 76 LU connected user management table 77 LU status inquiry unit 82 Data update necessity recognition unit 83 Data Copy Instruction Unit 84 Data Update Unit 85 LU Status Management Unit 86 LU Status Management Table 87 LU Connection Status Inquiry Unit 88 Update End Notification Unit 89 Cache Data Erase Instruction Unit 90 Update Start Notification Unit 91 Write Monitoring Control Unit 92 Update Cancel Instruction Part 101, 102, 103 Target 200 User A

Claims (15)

In a network storage system in which a computer terminal can connect to a storage device via a network and acquire data necessary for the operation of the computer terminal.
Means for authenticating a user who intends to connect to the storage device from the computer terminal, managing identification information of the storage device corresponding to the user, and notifying the computer terminal of identification information of the storage device corresponding to the user whose authentication is normal A user management server having
Connect to the storage device to be updated, copy the data stored in the storage device to another storage device, update the data in the copy destination storage device, and connect to the copy source storage device A storage management server having means for instructing the change of the identification information of the storage device corresponding to the user managed by the user management server so that all the users who are to be connected are connected to the copy destination storage device. e,
And the user management server
Between the time when the computer terminal is notified of the identification information of the storage device corresponding to the user whose authentication is normal and the time when the disconnection between the computer terminal and the storage device can be confirmed, the computer terminal by the user is the storage device. To manage information related to the connection, and in response to an inquiry from the storage management server or other device, a list of users and computer terminals connected to the storage device, or either A network storage system characterized by comprising means for retrieving such a list and notifying the result . In a network storage system in which a computer terminal can connect to a storage device via a network and acquire data necessary for the operation of the computer terminal.
Means for authenticating a user who intends to connect to the storage device from the computer terminal, managing identification information of the storage device corresponding to the user, and notifying the computer terminal of identification information of the storage device corresponding to the user whose authentication is normal A user management server having
Connect to the storage device to be updated, copy the data stored in the storage device to another storage device, update the data in the copy destination storage device, and connect to the copy source storage device For the specified user, change the storage device identification information corresponding to the user managed by the user management server so that the user can select and connect either the copy source storage device or the copy destination storage device. Bei example a storage management server having a means for instructing,
And the user management server
Between the time when the computer terminal is notified of the identification information of the storage device corresponding to the user whose authentication is normal and the time when the disconnection between the computer terminal and the storage device can be confirmed, the computer terminal by the user is the storage device. To manage information related to the connection, and in response to an inquiry from the storage management server or other device, a list of users and computer terminals connected to the storage device, or either A network storage system characterized by comprising means for retrieving such a list and notifying the result . In the network storage system according to claim 1 or 2,
The storage management server
After the data update of the storage device is completed, a list of users and / or computer terminals connected to the copy source storage device is searched, and there is one or more computer terminals connected to the copy source storage device. If so, a network storage system comprising means for notifying the computer terminal that the update of the storage device has been completed. In a network storage system in which a computer terminal can connect to a storage device via a network and acquire data necessary for the operation of the computer terminal.
Means for authenticating a user who intends to connect to the storage device from the computer terminal, managing identification information of the storage device corresponding to the user, and notifying the computer terminal of identification information of the storage device corresponding to the user whose authentication is normal A user management server having
Connect to the storage device to be updated, copy the data stored in the storage device to another storage device, update the data in the copy destination storage device, and connect to the copy source storage device A storage management server having means for instructing a change of the identification information of the storage device corresponding to the user managed by the user management server so that all the users who are to be connected are connected to the copy destination storage device. ,
And the user management server
Before notifying the computer terminal of the identification information of the storage device corresponding to the user with normal authentication, the storage device is set as the copy source storage device, and it is checked whether the corresponding copy destination storage device is being updated. If the copy destination storage device is being updated, the computer terminal is notified of this, and a display confirming whether or not to connect to the copy source storage device is displayed on the display device of the computer terminal. Means to do,
A network storage system comprising: means for connecting the computer terminal and the copy source storage apparatus when a user input notification indicating that the user wishes to connect to the copy source storage apparatus is received from the computer terminal. In a network storage system in which a computer terminal can connect to a storage device via a network and acquire data necessary for the operation of the computer terminal.
Means for authenticating a user who intends to connect to the storage device from the computer terminal, managing identification information of the storage device corresponding to the user, and notifying the computer terminal of identification information of the storage device corresponding to the user whose authentication is normal A user management server having
Connect to the storage device to be updated, copy the data stored in the storage device to another storage device, update the data in the copy destination storage device, and connect to the copy source storage device For the specified user, change the storage device identification information corresponding to the user managed by the user management server so that the user can select and connect either the copy source storage device or the copy destination storage device. A storage management server having means for instructing
And the user management server
Before notifying the computer terminal of the identification information of the storage device corresponding to the user with normal authentication, the storage device is set as the copy source storage device, and it is checked whether the corresponding copy destination storage device is being updated. If the copy destination storage device is being updated, the computer terminal is notified of this, and a display confirming whether or not to connect to the copy source storage device is displayed on the display device of the computer terminal. Means to do,
A network storage system comprising: means for connecting a computer terminal and a copy source storage apparatus when a user input notification indicating that the user wishes to connect to the copy source storage apparatus is received from the computer terminal . The network storage system according to any one of claims 1 to 5,
The storage management server
Before copying data from the copy source storage device to the copy destination storage device, the user management server is queried for the user connected to the corresponding copy source storage device. A network storage system comprising means for notifying start of update and displaying data update start on a display device of the computer terminal. The network storage system according to any one of claims 1 to 6,
The computer terminal temporarily stores the data acquired from the storage device, and thereafter, if the data requested to be read from the computer terminal is within the temporarily stored data, do not access the storage device. The data is returned to the computer terminal, while the data requested by the computer terminal to be written to the storage device is temporarily stored without being immediately written to the storage device, and the data is later stored in the computer terminal. A network storage system comprising a cache device for writing to a storage device. The network storage system according to claim 7,
The storage management server
After the completion of the update of the copy source storage device, if there is no computer terminal connected to the copy source storage device as a result of searching for the computer terminal connected to the copy source storage device, it is temporarily stored in the cache device. A network storage system comprising means for instructing the cache device to delete data corresponding to the copy source storage device. In the network storage system according to claim 7 or 8,
The storage management server
Prior to data copying from the copy source storage device to the copy destination storage device, the data temporarily stored in the cache device and instructed to delete the data read from the corresponding copy source storage device, or A network storage system comprising means for instructing deletion of data temporarily stored in a computer terminal and read from a corresponding copy source storage apparatus. The network storage system according to any one of claims 7 to 9,
The storage management server
Prior to data copying from the copy source storage device to the copy destination storage device, the data temporarily stored in the cache device and requested to be written to the storage device is transferred from the cache device to the storage device. Or in addition to the storage process of the data in the storage device, the cache device stores the data temporarily stored in the computer terminal immediately before and stored in the storage device. A network storage system comprising means for transferring data to a network storage system. The network storage system according to any one of claims 6 to 10,
The storage management server
Before copying data from the copy source storage device to the copy destination storage device, the cache device is instructed to monitor a write request to the copy source storage device, and the write request is Means for instructing to cancel monitoring;
Means for canceling data update to the copy destination storage apparatus corresponding to the copy source storage apparatus in response to detection notification of the write request from the cache apparatus to the copy source storage apparatus at the time of monitoring the write request in the cache apparatus. A network storage system characterized by that. A user management server used in the network storage system according to any one of claims 1 to 11, comprising at least
Means for managing identification information of the storage device corresponding to the user;
Means for receiving an authentication request of a user attempting to connect to the storage device from the computer terminal;
Means for referring to identification information of the storage device corresponding to the user in response to the user authentication request and authenticating whether the user is connectable to the storage device;
Means for notifying the computer terminal of identification information of the storage device corresponding to a normal authentication user ;
Between the time when the computer terminal is notified of the identification information of the storage device corresponding to the user whose authentication is normal and the time when the disconnection between the computer terminal and the storage device can be confirmed, the computer terminal by the user is the storage device. To manage information related to the connection, and in response to an inquiry from the storage management server or other device, a list of users and computer terminals connected to the storage device, or either And a means for retrieving such a list and notifying the result . A user management server used in the network storage system according to any one of claims 1 to 11, comprising at least
Means for managing identification information of the storage device corresponding to the user;
Means for receiving an authentication request of a user attempting to connect to the storage device from the computer terminal;
Means for referring to identification information of the storage device corresponding to the user in response to the user authentication request and authenticating whether the user is connectable to the storage device;
Means for notifying the computer terminal of identification information of the storage device corresponding to a normal authentication user;
Before notifying the computer terminal of the identification information of the storage device corresponding to the user with normal authentication, the storage device is set as the copy source storage device, and it is checked whether the corresponding copy destination storage device is being updated. If the copy destination storage device is being updated, the computer terminal is notified of this, and a display confirming whether or not to connect to the copy source storage device is displayed on the display device of the computer terminal. Means to do,
Means for connecting the computer terminal and the copy source storage apparatus when a user input notification indicating that the user wishes to connect to the copy source storage apparatus is received from the computer terminal
A user management server characterized by that. A program for causing a computer of a user management server used in the network storage system according to any one of claims 1 to 11 to execute,
at least,
Means for managing identification information of the storage device corresponding to the user;
Means for receiving an authentication request of a user attempting to connect to the storage device from the computer terminal;
Means for referring to identification information of the storage device corresponding to the user in response to the user authentication request and authenticating whether the user is connectable to the storage device;
Means for notifying the computer terminal of identification information of the storage device corresponding to a normal authentication user ;
Between the time when the computer terminal is notified of the identification information of the storage device corresponding to the user whose authentication is normal and the time when the disconnection between the computer terminal and the storage device can be confirmed, the computer terminal by the user is the storage device. To manage information related to the connection, and in response to an inquiry from the storage management server or other device, a list of users and computer terminals connected to the storage device, or either As a means to search the list and notify the result ,
A program for a user management server for causing the computer to function. A program for causing a computer of a user management server used in the network storage system according to any one of claims 1 to 11 to execute,
at least,
Means for managing identification information of the storage device corresponding to the user;
Means for receiving an authentication request of a user attempting to connect to the storage device from the computer terminal;
Means for referring to identification information of the storage device corresponding to the user in response to the user authentication request and authenticating whether the user is connectable to the storage device;
Means for notifying the computer terminal of identification information of the storage device corresponding to a normal authentication user;
Before notifying the computer terminal of the identification information of the storage device corresponding to the user with normal authentication, the storage device is set as the copy source storage device, and it is checked whether the corresponding copy destination storage device is being updated. If the copy destination storage device is being updated, the computer terminal is notified of this, and a display confirming whether or not to connect to the copy source storage device is displayed on the display device of the computer terminal. Means to do,
If a user input notification indicating that the user wishes to connect to the copy source storage apparatus is received from the computer terminal, means for connecting the computer terminal and the copy source storage apparatus,
A program for a user management server for causing the computer to function.

Images