JP4139975B2 - Information processing apparatus, file management method, and program - Google Patents

Description

  The present invention relates to an apparatus for performing file migration between file servers.

  In recent years, with the widespread use of inexpensive and high-speed networks, servers that provide file services through the network are widely used in various information systems. A server that provides this file service is called a file server. Examples of file services include NFS and CIFS.

  The operation of the file server is performed by the system administrator so that the user can smoothly use the service provided by the file server. One of the important operations in file server operations is file migration between file servers. File migration is an act of moving a file between file servers. For example, this corresponds to a case where a file is moved for management purposes in accordance with an instruction from a system administrator.

The purpose of file migration is as follows, for example.
(1) Effective utilization of free capacity By moving files from a file server with little free capacity to a file server with large free capacity, the storage capacity of the file server is effectively utilized.
(2) Effective use of processing capacity File server processing by moving a file from a file server that receives a large amount of access to the processing capacity and has a poor response to a file server that has less access to the processing capacity Make effective use of capacity.
(3) Replace the file server Move the file from the old file server to the new file server, and replace the old file server with the new file server.

  Further, as a conventional method for performing file migration between file servers, there is a method using an apparatus (hereinafter referred to as an intermediate apparatus) existing between a client and a server.

  First, the system administrator instructs the intermediate device to perform file migration. Upon receiving the instruction, the intermediate device performs file migration between the file servers in accordance with the instruction.

  Here, “exists between the client and the server” means that it exists between the client and the server as a physical or logical communication route. That is, this means that a request from the client reaches the server via the intermediate device, and a response from the server reaches the client via the intermediate device.

The intermediate device performs file migration between the file servers along the following two steps.
(Step 1) Replication Replicate the file on the migration source file server to the migration destination file server in a consistent manner using the file access protocol. Here, the consistent state means that a series of processing for the file is completed and there is no contradiction between the data. For example, if a part of a file is duplicated in a state before the change and another part is duplicated in a state after the change, consistency may not be achieved.
(Step 2) Access switching The file server accessed by the user on the client is switched from the source to the destination.

  Further, there are the following two advantages of file migration by the intermediate device.

  (1) During “replication”, there is no need to perform server-to-server communication to ensure consistency of the duplicate. The reason for this is that processing such as file data update is performed by a request from the client to the server, so the intermediate device monitors the request and response, and temporarily shuts off to ensure consistency between copies. Because it can.

  Generally, the protocol used for server-to-server communication is different from the file service protocol used between the client and the server. In order to perform server-to-server communication, the file server has a separate protocol for server-to-server communication. Need to be. If the intermediate device performs file migration, the file server does not need to perform server-to-server communication.

  (2) “Access switching” can be performed without making the client aware of changes in server location information and file identifiers. The reason is that the “intermediate device” can perform “access switching” by changing the server location information and file identifier when transferring a request or response.

  As a conventional technique, a file migration method using the above-described intermediate device has been proposed (see Non-Patent Document 1). In Non-Patent Document 1, the NAS switch is an intermediate device.

  A conventional intermediate apparatus manages a tree structure of an integrated directory based on a public directory of a plurality of servers on a pseudo file system. Then, the intermediate device copies the file in the public directory of one of the servers to another server while maintaining the tree structure of the integrated directory tree on the pseudo file system. Next, the intermediate device changes the tree structure mapping of the pseudo file system to hide the data movement from the client and keep the integrated directory tree structure unchanged, from the user to the copy destination file. To allow access. As a result, the intermediate device relieves the capacity shortage in the storage device of the server and the overload of the file access processing in some servers.

  As data moves between servers, it is necessary to change object IDs corresponding to objects such as directories and files. The intermediate device manages the change history of the object ID before and after the data movement, and hides the operation of the data movement from the client by preventing the trouble caused by the change of the object ID in the client and the server. That is, after the intermediate device replicates data between servers, the user access is switched by changing the mapping of the tree structure.

  According to this prior art, since the intermediate device replicates data in a consistent manner, there is no need for server-to-server communication for ensuring the consistency of replicated items. In addition, since the intermediate apparatus switches the access by switching the transfer destination of the message from the user, the client is not made aware of the change of the file identifier such as the object ID accompanying the movement.

Another example of the prior art is described in Patent Document 1. In the distributed information processing system described in Patent Document 1, the server stores connection information with files on the server used by application programs on the client on a magnetic disk. Then, in response to a request from the client, the server restores the connection state between the application and the file using information in the magnetic disk.
Yamakawa, Ishikawa, Kikuchi, “NAS Switch: Development of Virtualization Integration Technology for NFS Server”, IEICE Technical Report Vol. 102, no. 275, pp13-18 Japanese Patent No. 3343949

  Normally, file migration is performed while the file server is offline. That is, it is common to temporarily stop using the file server from the client and perform file migration during that time.

  However, taking a file server offline can have a significant impact on the inside and outside of the system. If it is a company system, it may lead to a large loss for the company. In addition, in order to minimize the influence on business and the like, file migration may be performed at night or on holidays, which increases the burden on the system administrator.

  For these various reasons, it is preferable that the file migration can be performed while the file server is online. Online means that the user can use the file service of the file server. That is, the power is turned on, the communication network is connected, and various settings for the software necessary for the user to access are made.

  In an online file server, when a user accesses a file, exclusive processing is performed to prevent inconsistency in data and status. There are various types of exclusion processing depending on the file access protocol.

  As an example of exclusive processing, there is a method in which an exclusive lock is applied when a user accesses a file in an online file server. The exclusive lock prohibits access to a file by a user other than a predetermined user.

  Among them, the forced lock method is a method that is affected by the exclusive lock regardless of whether or not the user observes the exclusive lock agreement. For example, even a user who does not follow the lock agreement is denied access based on the type of exclusive lock placed on the file. Also, as an exclusive lock range, there is a range in which the entire file is locked and a partial lock such as byte range lock is available.

  Examples of the forced lock file access protocol include CIFS (Common Internet File System) and NFSv4 (Network File System Version 4).

  In some cases, a state where any user opens a file (hereinafter referred to as an open state) is managed by the file server. As an example of the open state, (1) when an exclusive lock is applied to the entire file, (2) when a partial exclusive lock is applied like a byte range lock, (3) an offset of the file pointer is managed. Cases. In the above-described CIFS and NFSv4, the open state is managed.

  In addition, as an exclusive process, a binary identifier (hereinafter referred to as a token) is passed from a file server to a user as a proof of access permission when opening a file. In the above-described CIFS, a token is used.

  In the online state where exclusive processing is performed, there are various difficulties in file migration.

  When the forced lock type exclusion process is performed, the intermediate device cannot copy the file that is exclusively locked by the user from the migration source server to the migration destination server. This is because if the file is locked exclusively by the user, the read request from the intermediate device is rejected by the source server.

  In addition, when each file server manages the open state, if the intermediate device switches access to the file from the source server to the destination server, the open state at the source server becomes invalid on the destination server. . When the open state becomes invalid, access from other users becomes possible, and data may be rewritten by access that should be prohibited. In addition, since the offset of the file pointer set on the source server is cleared, data may be written in a portion different from the range intended by the application. As described above, when the open state of the file is managed by the file server, the file may be destroyed if the intermediate device switches access from the user.

  In addition, when a token is passed from the file server to the user when opening the file, when the intermediate device switches access, the application that has passed the token from the source server accesses the destination server using that token. try to. However, the token passed from the source server becomes invalid on the destination server. Therefore, an application that tries to continue using the same token before and after the access switching receives an error, fails to access the file, and ends abnormally.

  An object of the present invention is to provide an apparatus capable of normally migrating files between online file servers.

In order to achieve the above object, an information processing apparatus of the present invention is an information processing apparatus that is routed through communication between a plurality of servers that store files and a client that accesses the server,
Open state information management means for managing the open state information of each of the files;
File replication means for switching access to the file to the replication after creating a replication of the file between the servers;
After the access to the file is switched to the copy, before the first access to the copy, the open state information management unit is queried to acquire the open state information, and the file is opened on the source server. If so, open state reproducing means for reproducing the open state on the destination server is provided.

  According to the present invention, the open state of each file is managed. When a copy of a file is created and the access from the client is switched to the copy, the open state of the file is transferred to the destination server before the first access. Because it reproduces, the information processing device can perform file migration by continuing the open state in the file access protocol in which the open state is managed. Does not cause abnormal termination.

  Embodiments of the present invention will be described in detail with reference to the drawings.

(First embodiment)
FIG. 1 is a block diagram showing the configuration of a client server system according to the first embodiment of the present invention.

  Referring to FIG. 1, the client server system according to the first embodiment includes at least one (two in FIG. 1) client 11, at least one (two in FIG. 1) server 14, and an intermediate Device 101. The client 11, the server 14, and the intermediate device 101 are each configured by a computer and connected to the network 12. The network 12 is a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), or the Internet.

  The client 11 is used by at least one user 11a, and the client 11 has at least one redirector 11b. A user represents a program using a file service or a virtual identity.

  The user 11a accesses a file stored in the server 14 via the redirector 11b. The redirector 11b redirects the access.

  The server 14 stores and manages files accessed by the clients 11 and provides file services to the clients 11. Examples of file services include NFS and CIFS.

  The intermediate device 101 is located between the client 11 that uses the file service and the server 14 that provides the file service. Requests from the client 11 to the server 14 and responses from the server 14 to the client 11 always pass through the intermediate device 101. The request from the client 11 to the server 14 is a message signal that requests some processing. The response from the server 14 to the client 11 is a message signal that responds to the request.

  As an example, the intermediate device 101 may be physically located between the client 11 and the server 14. In FIG. 1, the intermediate device 101 is not physically located between the client 11 and the server 14. However, logically, the intermediate device 101 is arranged between the client 11 and the server 14, and all requests from the client 11 to the server 14 and all responses from the server 14 to the client 11 are sent to the intermediate device 101. Via.

  As described above, the intermediate device 101 through which all requests from the client 11 to the server 14 pass is specifically a proxy server, a gateway, a transparent proxy server, a load balancer, or the like.

  For example, each client 11 may set the intermediate device 101 as a proxy server or a gateway. In order to make the intermediate device 101 a transparent proxy server, a routing rule may be set so that a packet from the client 11 to the server 14 always passes through the intermediate device 101. In order to use the intermediate device 101 as a load balancer, the intermediate device 101 may be shown to the client as a virtual server.

  FIG. 2 is a block diagram illustrating a configuration of the intermediate apparatus 101 according to the first embodiment. Referring to FIG. 2, the intermediate apparatus 101 of this embodiment includes a packet processing unit 110, a message forward unit 120, a file duplication unit 130, and an exclusive lock state information management unit 140.

  When the packet processing unit 110 receives a packet from the client 11 and the server 14 via the network 12, the packet processing unit 110 outputs a message included in the packet to the upper unit, packetizes the message output from the upper unit, and configures the network 12. To the client 11 or the server 14. Here, the message is used as a general term for requests and responses based on the file access protocol.

  When the message forwarding unit 120 receives a message from the packet processing unit 110, the message forwarding unit 120 refers to a forwarding table (not shown), checks the forwarding destination, sets it as the destination, and sends the message to the packet processing unit 110. The forwarding table is a table in which a server identifier included in a message and a message transfer destination server are mapped. The server identifier is, for example, an IP address.

  In addition, in order to manage the exclusive lock state in the exclusive lock state information management unit 140, the message forward unit 120 sends a copy of the message to the exclusive lock state information management unit 140 if the message is a request or response for the exclusive lock. send.

  In addition, during file migration, in order to enable monitoring of the update of the replicated file in the file replication means 130, the message forward means 120, if the message is an update request or response, copies the message to the file Send to the duplicating means 130. An update request is a request for processing to update file data, and an update response is a response to an update request.

  When receiving a file migration instruction from the system administrator, the file copying unit 130 starts an operation based on the instruction. The file duplicating means 130 that has started the operation duplicates the files between the servers 14. When a copy of an update request or response message is received from the message forwarding means 120 while the file is being copied, it is checked whether the copied file has an update. This is because if the copied file is updated, it is necessary to redo the copying process.

  Further, if the file to be duplicated has an exclusive lock, the file duplicating unit 130 inquires the exclusive lock state information managing unit 140 to obtain the exclusive lock state information. Then, the file duplicating means 130 makes it possible to read the file by impersonating the owner of the exclusive lock based on the owner information included in the exclusive lock state information. Here, the owner means a user or a process on the user who has placed an exclusive lock on the file. The owner can access the file with the exclusive lock.

  When the copying is completed, the file copying unit 130 rewrites the forwarding table in order to switch access from the client.

  The exclusive lock status information management unit 140 manages the exclusive lock status of each file, and updates the exclusive lock status information when receiving a copy of the exclusive lock request or response message from the message forward unit 120. The exclusive lock request is a message requesting that an exclusive lock be placed on or released from the file. The exclusive lock response is a message of a response to the exclusive lock response. The exclusive lock status information is information indicating whether or not each file has an exclusive lock, and a user or client that has applied the exclusive lock.

  Further, upon receiving an inquiry from the file copying unit 130, the exclusive lock state information management unit 140 sends the recorded exclusive lock state information.

  Next, an operation example of the client server system of this embodiment will be described. Here, it is assumed that the file copying unit 130 starts to operate based on an instruction from the system administrator. In addition, the file duplicating unit 130 allows interruption by processing of other units. If there is an interruption due to another process, the file copying unit 130 sleeps and waits for the process to end.

  Other than the file duplicating means 130, processing is started upon receipt of data input or inquiry, and interruption by other processing is not permitted during the processing.

  Further, in order to enable the cooperative operation of the message forward unit 120 and the file duplicating unit 130, the file duplicating unit 130 is provided with two flags, a migration flag and a forward blocking flag.

  The migration flag is a flag for the file duplication unit 130 to notify the message forward unit 120 that the file migration is in progress. The message forwarding unit 120 uses this flag during file migration in order to perform an operation different from the normal operation.

  The forward blocking flag is a flag for the file copying unit 130 to block the message forwarding by the message forwarding unit 120. When the file duplication unit 130 finishes duplicating the file and checks the consistency of the duplication target, the message forwarding needs to be blocked. For this purpose, this flag is used.

  Note that these flags are an example of a method for performing communication for the message forward unit 120 and the file duplicating unit 130 to perform a cooperative operation. In addition to providing a flag in the file duplicating means 130, there are a method for exchanging requests and responses, a method for providing third-party means for managing flags, a method for relaying requests and responses by third-party means, and the like. is there. Further, communication can be eliminated by collectively mounting these plural units into one unit.

  FIG. 3 is a flowchart showing the operation of the packet processing means of the first embodiment. Referring to FIG. 3, when the packet processing unit 110 receives data from the network 12 or the host unit (step AA1), the packet processing unit 110 starts processing. The high-order means are the message forward means 120 and the file copy means 130.

  First, the packet processing means 110 checks where the received data is from (step AA2). If the received data is a packet from the network 12, the packet processing means 110 acquires a message part from the packet (step AA3). There are cases where a plurality of messages are contained in one packet. In such a case, a plurality of messages are extracted. The packet processing means 110 sends each message to the higher-level means (step AA4) and ends the processing.

  In some cases, one message is fragmented into a plurality of packets. In this case, the packet processing means 110 sends the message to the higher-order means after the data composing the message is prepared.

  If it is determined in step AA2 that the data is from the host unit, the packet repair unit 110 packetizes the message and sends it to the network 12 (step AA5), and the process ends.

  FIG. 4 is a flowchart showing the operation of the message forwarding unit of the first embodiment. Referring to FIG. 4, when the message forward unit 120 receives a message from the packet processing unit 110 (step AB1), it starts processing.

  First, the message forward means 120 checks whether or not the forward cutoff flag is ON (step AB2). If the forward blocking flag is OFF, the message forward means 120 proceeds to the process of step AB4. If the forward cutoff flag is ON, the message forward means 120 once returns to the processing of other means and waits until the forward cutoff flag becomes OFF (Step AB3).

  Steps AB2 to AB3 are performed in order to block communication between the client and the server when the file duplicating unit 130 confirms whether or not the file is consistent between the migration source and the migration destination. Is provided.

  Next, the message forward means 120 checks whether the migration flag is ON (step AB4). If the migration flag is OFF, the message forward means 120 proceeds to the process at step AB7. If the migration flag is ON, the message forward means 120 checks whether the message is an update request or response (step AB5).

  If the message is neither an update request nor a response, the message forward means 120 proceeds to the process of step AB7. If the message is an update request or response, the file forwarding means 120 sends a copy of the message to the file duplicating means 130 (step AB6).

  The processes in steps AB4 to AB6 are processes for enabling the file duplicating unit 130 to confirm whether or not the migration target file has been updated.

  In the process of step AB5, whether or not the message is an update request or response is determined based on the type of command included in the message. The command type may be symbolically indicated in the message or may be indicated in binary form, such as a number. In either case, the determination may be made according to the protocol specifications. Examples of update commands include a file update command, an attribute update command, and a name space update command.

  In addition, depending on the protocol, the type of command is not included in the response. In this case, when a request is received, the message number included in the message is recorded, and when a response is received, the message number is checked to determine whether or not the update system is used.

  Next, the message forward means 120 checks whether or not the message is an exclusive lock request or a response (step AB7). If it is not an exclusive lock request or a response, the message forward means 120 moves to the process of step AB9. If the message is an exclusive lock request or a response, the message forward means 120 sends a copy of the message to the exclusive lock state information management means 140 (step AB8).

  Steps AB7 to AB8 are provided to enable the exclusive lock state information management unit 140 to record the exclusive lock state information.

  In step AB7, whether or not the message is an exclusive lock request or a response can be determined from the type of command and parameters included in the message. The command type and parameter may be symbolically indicated in the message or in binary form, such as a number. In either case, the determination may be made according to the protocol specifications.

  Depending on the protocol, the response does not include the command type and parameters. In this case, the message number included in the message is recorded when the request is received, and the determination is made by checking the message number when receiving the response.

  Finally, the message forwarding means 120 refers to the forwarding table, checks the forwarding destination, sets it as the destination, and sends the message to the packet processing means 110 (step AB9). In this case, the correspondence between the message destination IP address and the forwarding IP address is mapped in the forwarding table. Further, instead of a server identifier, a volume identifier or file identifier may be mapped to a message transfer destination server. In this case, the intermediate apparatus 101 manages to which server the data should be transferred in volume units or file units. It is of course possible to map the correspondence between the server identifier, the volume identifier, and the file identifier and the message transfer server.

  FIG. 5 is a flowchart showing the operation of the file duplicating means of the first embodiment. Referring to FIG. 5, the file copying unit 130 receives a migration start instruction from the system administrator (step AC1) and starts processing. The system administrator specifies the movement source and the movement destination at the time of the instruction.

  The file belonging to the migration source is the migration target file. The file duplicating unit 130 duplicates these to the destination. The instruction is, for example, to move the volume Share1 of the server Server1 to the volume Share2 of the server Server2. In this case, the file duplicating unit 130 moves a file belonging to the volume Share1 to the volume Share2. In this example, the movement is performed in units of volumes. However, it is also possible to specify movement in units of directories, movement in units of files, or movement in units of servers.

  The file duplicating unit 130 that has started the processing sets the migration flag to ON (step AC2). Next, the file duplicating unit 130 duplicates the source file to the destination (step AC3). Details of the process of step AC3 will be described later with reference to the flowchart of FIG.

  Next, the file copying unit 130 switches the access from the client from the movement source to the movement destination (step AC4). Details of the process of step AC4 will be described later with reference to the flowchart of FIG.

  Finally, the file duplicating means 130 returns the migration flag to OFF (step AC5) and ends the process.

  FIG. 6 is a flowchart showing an operation in which the file duplicating unit of the first embodiment duplicates the source file to the destination. Referring to FIG. 6, the file copying unit 130 first creates a synchronization state management tree (step AD1). The synchronization state management tree describes a directory tree to be migrated. Further, the synchronization status management tree describes whether each file constituting the directory tree has been copied or not.

  In order to create the synchronization state management tree, the file replication means 130 sends a request for knowing the directory tree configuration to the server. For example, a request such as READDIR or READDIRPLUS is sent to the server if the protocol is NFS, and FINDFIRST is sent to the server if the protocol is CIFS. Whether each file has already been copied is described as not having already been copied since the copy process has not started at this point.

  Next, the file duplicating unit 130 repeats the processing from step AD3 to step AD7 until all the files listed in the synchronization state management tree have been duplicated and are not checked for update ( Step AD2). The addition and deletion of the update check will be described later with reference to FIG.

  First, the file duplicating unit 130 checks whether or not the migration target has been updated (step AD3). Details of the processing in step AD3 will be described later with reference to FIG.

  Next, the file duplicating means 130 selects one of the files in the synchronization state management tree that has not been duplicated (step AD4). Next, the file duplicating unit 130 checks whether or not the selected file is exclusively locked by inquiring to the exclusive lock state information managing unit 140 (step AD5).

  If the selected file is locked exclusively, the file duplicating means 130 proceeds to the process of step AD7. If the file is not exclusively locked, the file duplicating unit 130 obtains the exclusive lock state information from the exclusive lock state information managing unit 140 (step AD6).

  This exclusive lock information includes information on the type of exclusive lock, the range of the exclusive lock, and the owner of the exclusive lock. The range related to the exclusive lock in the file is indicated by the information on the type and range of the exclusive lock. Information regarding the owner of the exclusive lock is used when a file that is exclusively locked is copied.

  Next, the file duplicating means 130 duplicates the selected file to the movement destination (step AD7). At this time, when the file duplication unit 130 finishes duplicating the file, the file duplication unit 130 puts the file into a duplicated state on the synchronization state management tree.

  If the file to be duplicated is exclusively locked, the file duplicating means 130 uses the exclusive lock status information obtained by the process of step AD6. That is, the file duplicating unit 130 performs duplication by impersonating the owner using information on the owner of the exclusive lock included in the exclusive lock state information.

  The owner of the exclusive lock differs depending on the file access protocol, but is generally a client, a transport such as a TCP connection, a user, a process on the user, or a combination thereof.

  When there are no more unreplicated files in the synchronization state management tree, the file replication means 130 exits the loop of step AD2 and turns on the forward blocking flag (step AD8).

  Finally, the file duplicating unit 130 confirms whether there is any inconsistent migration target (step AD9), and ends the process. Details of the process of step AD9 will be described later with reference to the flowchart of FIG.

  FIG. 7 is a flowchart showing an operation of checking whether the file duplicating unit of the first embodiment has been updated to the migration target. Referring to FIG. 7, the file duplicating unit 130 first determines whether there is a message from the message forwarding unit 120 (step AE1). If there is no message, the file duplicating means 130 ends the process as it is.

  If there is a message, the file duplicating means 130 determines whether or not the file targeted by the message is a migration target (step AE2).

  The file targeted by the message can be known from the file identifier included in the message. The file identifier may be symbolically indicated in the message or may be indicated in a binary format such as a token from the file server 14. If it is symbolically shown as a path name, the file can be easily identified from the file identifier. If the token is shown in binary format, you need to know in some way what file the token corresponds to. Since the token is passed to the client by the response from the server when the opening is successful, as an example, the intermediate device can know the correspondence between the token and the path name by monitoring the opening request and response. For example, the path name included in the open request may be temporarily stored and recorded in association with the token included in the success response.

  In order to confirm whether or not the file targeted by the message is a migration target, it is only necessary to check whether or not the file is managed by the synchronization status management tree.

  If it is determined in step AE2 that the message target is not the migration target, the file copying unit 130 ends the process.

  If it is determined in step AE2 that the message target is a migration target, the file duplicating unit 130 checks whether the message is a request, a success response, or a failure response (step AE3).

  If the message is a request, the file replication unit 130 adds an update check to the file in the synchronization state management tree (step AE4). At this point, it is not known whether the request will succeed or fail, and the file may not be updated. For this reason, it is still impossible to determine whether or not the copy has been completed, and only an update check is given.

  If the message is a successful response, the file duplicating unit 130 returns the target file to which the update check is given to a state where it has not been duplicated (step AE5). In other words, duplication is performed again.

  If the message is a failure response, the file replication unit 130 discards the update check (step AE6).

  FIG. 8 is a flowchart showing an operation in which the file duplicating unit according to the first embodiment confirms whether there is any inconsistent migration target. Referring to FIG. 8, the file duplicating unit 130 first checks whether there is a file that is inconsistent in the migration target (step AF1). Examples of the consistency check method include a method of comparing file update times and a method of comparing checksums of file data.

  If there is no inconsistent file, the file duplicating means 130 ends the process. If there is an inconsistent file, the file duplicating unit 130 turns off the forward blocking flag and returns to the duplication loop of step AD2, that is, the process of step AD2 (step AF2).

  FIG. 9 is a flowchart showing the operation of switching the access from the client from the movement source to the movement destination by the file duplicating means of FIG. Referring to FIG. 9, the file duplicating unit 130 first rewrites the forwarding table so that access to the movement source moves to the movement destination (step AG1). Next, the file duplicating unit 130 turns off the forward blocking flag (step AG2) and ends the process.

  FIG. 10 is a flowchart showing the operation of the exclusive lock state information management means. Referring to FIG. 10, upon receiving data from the message forwarding unit 120 or an inquiry from the file duplicating unit 130 (Step AH1), the exclusive lock state information managing unit 140 starts processing.

  The exclusive lock state information management unit 140 first determines whether the data is received from the message forward unit 120 or an inquiry from the file replication unit 130 (step AH2).

  If the data is received from the message forward means 120, the exclusive lock state information management means 140 checks whether the data is a request message, a success response message, or a failure response message (step AH3).

  If the message is a request message, the exclusive lock state information management unit 140 once holds the information and message number of the exclusive lock request (step AH4), and ends the process.

  The message number is held in order to check which request is responded when there is a response later. The information on the exclusive lock request is retained because there is information included only in the request, and this information is recorded when a success response is received.

  If the message is a success response message, the exclusive lock state information management unit 140 updates the exclusive lock state information by recording the held exclusive lock request information (step AH5), and ends the process. If the message is a failure response message, the exclusive lock state information management unit 140 discards the held exclusive lock request information (step AH6) and ends the process.

  In step AH5 and step AH6, it can be determined from the message number to which request the response corresponds.

  The information on the exclusive lock to be recorded includes information on the type of exclusive lock, the range of the exclusive lock, and the owner of the exclusive lock.

  The type of exclusive lock is information indicating whether it is an exclusive lock for each file or a partial exclusive lock such as a byte range. The exclusive lock range is information indicating in which range of the file the partial exclusive lock is applied.

  The owner of the exclusive lock varies depending on the file access protocol, but is generally a client, a connection, a user, a process, or a combination thereof.

  Information regarding the type and range of the exclusive lock is used to determine whether the file is locked exclusively and to which range the exclusive lock is locked. This is because when the exclusive lock is applied only to a part of the file, it is only necessary to impersonate the owner of the exclusive lock only when the part is copied. Information regarding the owner of the exclusive lock is used when a file that is exclusively locked is copied.

  If it is an inquiry from the file duplicating unit 130 in the determination in step AH2, the exclusive lock state information managing unit 140 sends the exclusive lock state information to the file duplicating unit if the file is locked (step AH7). The process ends.

  According to this embodiment, the message forwarding means 120 transfers and monitors a message between the file server 14 and the client 11 according to the forwarding table, and if there is a request or response for an exclusive lock, the content is exclusive. The lock status information management unit 140 is notified, and if there is an update request or response during file migration, the contents are notified to the file duplication unit 130.

  Based on the notification from the message forward unit 120, the exclusive lock state information management unit 140 manages the exclusive lock state including the presence / absence of the exclusive lock of each file and the owner of the exclusive lock.

  When creating a copy in file migration, the file replication unit 130 acquires the exclusive lock state from the exclusive lock state information management unit 140, and if the exclusive lock is applied, the file replication unit 130 impersonates the owner of the exclusive lock and copies the file. If the notification from the message forwarding means 120 indicates that the copied file has been updated during file migration, the file is copied again and the file copy is completed in a consistent state. Then, the forwarding destination by the message forwarding means 120 for the access from the client is switched by updating the forwarding table.

  Therefore, the intermediate apparatus 101 reads the file using the information on the exclusive lock state recognized from the message, and copies the file in a consistent state using the information on the update of the file recognized from the message. Therefore, file migration can be performed normally even in an online state or when an exclusive lock is applied.

  In the present embodiment, an example in which the intermediate apparatus 101 exists in a physically independent form has been described, but the present invention is not limited thereto. As long as the intermediate device 101 exists logically between the client 11 and the file server 14, it may take any physical form.

  For example, the intermediate device 101 may be configured inside any one of the file servers 14. In that case, the communication between the client 11 and the file server 14 goes through the file server 14 having the intermediate device 101 therein. Further, the intermediate device 101 may be configured inside any one of the clients 11. In this case, communication between the client 11 and the file server 14 is via the client 11 having the intermediate device 101 therein.

In this embodiment, CIFS and NFSv4 are taken as examples of file access protocols, and the user is the owner of the exclusive lock. However, the present invention is not limited to this. There are various subjects that access the file according to the file access protocol, and therefore, the owner of the exclusive lock also varies.
(Second Embodiment)
The client server system according to the second embodiment has the same configuration as that of the first embodiment shown in FIG. However, in this embodiment, an intermediate device 102 is provided instead of the intermediate device 101 in FIG.

  FIG. 11 is a block diagram illustrating a configuration of the intermediate apparatus 102 according to the second embodiment. Referring to FIG. 11, the intermediate apparatus 102 according to the present embodiment includes a packet processing unit 110, a message forward unit 121, a file duplication unit 131, an open state information management unit 150, and an open state reproduction unit 160.

  The packet processing means 110 is the same as that in the first embodiment.

  When the message forwarding unit 121 receives a message from the packet processing unit 110, the message forwarding unit 121 refers to a forwarding table (not shown), checks the forwarding destination, sets it as the destination, and sends the message to the packet processing unit 110.

  Further, in order to manage the open state information in the open state information management unit 150, the message forward unit 121 sends a copy of the message to the open state information management unit 150 if the message is a request or response for changing the open state. send.

  Further, during file migration, in order to enable monitoring of the update of the replicated file in the file replication means 131, the message forward means 121, if the message is an update request or response, copies the message to the file Send to the duplicating means 131.

  Further, after the file migration is completed, the message forward unit 121 checks whether or not it is necessary to reproduce the open state, and if necessary, sends an open state reproduction request to the open state reproduction unit 160 to reproduce the open state. Instruct.

  Further, the message forwarding unit 121 sends a message to be sent using the state in which the open state is reproduced to the open state reproduction unit 160. The message forward means 120 sends the message to the open state reproduction means 160 because the message is forwarded by proxy using the state where the open state is reproduced.

  When receiving a file migration instruction from the system administrator, the file copying unit 131 starts an operation based on the instruction. The file duplicating means 131 that has started the operation duplicates the files between the servers 14. If a copy of the update message is received from the message forwarding means 121 while the file is being copied, it is checked whether the copied file has an update. This is because if the copied file is updated, it is necessary to redo the copying process.

  When the file duplication is completed, the file duplication unit 131 turns on the open state reproduction flag and then rewrites the forwarding table to switch the access from the client.

  When the open state information management unit 150 receives a copy of a request or response message for changing the open state information from the message forward unit 120, the open state information management unit 150 manages the open state information based on the content.

  When receiving an inquiry from the open state reproduction unit 160, the open state information management unit 150 sends the managed open state information to the open state reproduction unit 160.

  When the open state reproduction unit 160 receives the open state reproduction request from the message forward unit 121, the open state reproduction unit 160 reproduces the open state. When the message to be sent in the reproduced open state is received from the message forward unit 121 after reproducing the open state, the token is replaced and sent to the packet processing unit 110 (proxy transfer).

  Next, an operation example of the client server system of this embodiment will be described. Here, it is assumed that the file copying unit 131 starts to operate based on an instruction from the system administrator. In addition, the file duplicating unit 130 allows interruption by processing of other units. If there is an interruption due to another process, the file copying unit 131 sleeps and waits for the process to end.

  Other than the file duplicating means 131, processing is started upon receipt of data input or inquiry, and interruption by other processing is not permitted during the processing.

  In addition, three flags are provided to enable the message forwarding unit 121 and the file copying unit 131 to cooperate.

  The migration flag and the forward cutoff flag are the same flags as in the first embodiment. The open state reproduction flag is a flag for the file duplication unit 131 to notify the message forward unit 121 whether or not it is necessary to reproduce the open state, and is set here for each file server.

  The open state reproduction flag is turned on when the file duplication and the access switching are completed, so that the file server shifts to an operation mode in which the open state is reproduced. When it is necessary to reproduce the open state, the message forward means 121 uses this flag to perform an operation different from the normal time.

  In this embodiment, the timing for turning off the open state reproduction flag is not limited. For example, it may be turned off when there are no clients using the reproduced open state. When all the TCP connections with the client are disconnected, or conversely when all the TCP connections with the server are disconnected, the intermediate apparatus 102 may set the open state reproduction flag to OFF.

  As another example, the system administrator may set the time until the open state reproduction flag is turned off in advance. For example, when one month has elapsed after the open state reproduction flag is turned on, the administrator sets in advance that this flag is turned off and the open state is not reproduced. The intermediate device 102 automatically turns off this flag when the time has elapsed.

  Note that these flags are an example of a method in which the message forwarding unit 121 and the file duplicating unit 131 perform communication in order to perform a cooperative operation. In addition to providing a flag in the file duplicating means 131, there are a method for exchanging requests and responses, a method for providing third-party means for managing flags, a method for relaying requests and responses by third-party means, and the like. is there. Further, communication can be eliminated by collectively mounting these plural units into one unit.

  FIG. 12 is a flowchart showing the operation of the message forwarding means of the second exemplary embodiment. Referring to FIG. 12, when the message forwarding unit 121 receives a message from the packet processing unit 110 or receives an inquiry from the open state reproduction unit 160 (step BA1), the message forwarding unit 121 starts processing.

  First, the message forwarding means 121 checks where the message or inquiry is from (step BA2).

  If the message is from the packet processing means 110, the message forwarding means 121 performs the processing of steps AB2 to AB6 shown in FIG. 4 (step BA3). This is the same operation as in the first embodiment.

  Next, the message forwarding means 121 checks whether or not the message is a request or response for changing the open state (step BA4). If the message is not a request or response for changing the open state, the message forward means 121 proceeds to the process of step BA6.

  If the message is a request or response for changing the open state, the message forward unit 121 sends a copy of the message to the open state information management unit 150 (step BA5). Whether or not the message is a request or response for changing the open state can be determined from the type of command included in the message. The command type may be symbolically indicated in the message or may be indicated in binary form, such as a number. In either case, the determination may be made according to the protocol specifications. Examples of commands that change the open state include open, close, lock, unlock, and delete.

  In addition, depending on the protocol, the type of command is not included in the response. In this case, the message number included in the message is recorded when a request is received, and the type of command is determined by checking the message number when receiving a response.

  Finally, the message forward unit 121 sends a message to the open state reproduction unit 160 or the packet processing unit 110 (step BA6), and the process is terminated. Details of the process of step BA6 will be described later with reference to the flowchart of FIG.

  If it is determined in step BA2 that the query is from the open state reproducing means 160, the message forward means 121 sends a message to the packet processing means 110 (step BA7), and the process is terminated.

  FIG. 13 is a flowchart showing an operation in which the message forwarding unit according to the second embodiment sends a message to the open state reproducing unit or the packet processing unit. Referring to FIG. 13, the message forwarding means 121 first checks whether or not the open state reproduction flag is ON (step BB1).

  If the open state reproduction flag is OFF, the message forward unit 121 refers to the forwarding table to check the forwarding destination, sets it as the destination, sends the message to the packet processing unit 110 (step BB7), and ends the processing. To do.

  If the open state reproduction flag is ON, the message forward means 121 checks whether or not the file targeted by the message needs to reproduce the open state (step BB2).

  The file targeted by the message can be known from the file identifier included in the message. The file identifier may be symbolically indicated in the message such as a path name, or may be indicated in a binary format such as a token from the file server 14. If it is symbolically shown as a path name, the file can be easily identified from the file identifier. If the token is shown in binary format, you need to know in some way what file the token corresponds to. Since the token is passed to the client by a response from the server when the opening is successful, as an example, the intermediate device can know the correspondence between the path name and the token by monitoring the open request and response.

  Also, it is checked whether or not the file needs to reproduce the open state with reference to the synchronization state management tree. Unlike the first embodiment, this synchronization state management tree also describes whether or not each file has been reproduced in the open state. If the file is managed in the synchronization state management tree and the open state has not been reproduced, the file needs to be reproduced.

  The fact that the file is managed in the synchronization status management tree means that the file was a migration target. Therefore, the determination in step BB2 is YES (that is, the file targeted by the message needs to reproduce the open state). Is a migration target, when the file has been copied, but the file that has not been reproduced yet is the target of the message.

  If it is determined in step BB2 that the file targeted by the message does not need to reproduce the open state, the message forward unit 121 proceeds to the process in step BB4.

  If it is determined in step BB2 that the file targeted by the message needs to reproduce the open state, the message forward unit 121 sends an open state reproduction request to the open state reproduction unit 160 (step BB3), and the reproduction process is performed. Wait for it to finish.

  Next, the message forwarding means 121 checks whether or not the message uses the reproduced open state (that is, whether or not the message should be transmitted transparently) (step BB4).

  This step (step BB4) is provided for converting the token passed from the source server to the client into the token acquired by the intermediate device from the destination server for the message using the reproduced open state. Yes.

  The open state used by the message can be identified by a token included in the message and passed from the server when the file is opened. Usually, tokens are implemented as file identifiers in messages. Whether this token is described in the open state reproduction table can determine whether or not the reproduced open state is used. The open state reproduction table is a table in which the token passed from the destination server and the token before reproduction passed from the source server are associated with each other.

  Depending on the file access protocol, not only the token passed from the server when the file was opened, but also the token passed when the user was authenticated and permission to access the volume on which the file exists were received. The open state cannot be identified without using various tokens such as the token passed at the time. In this case, if other tokens are also described in the open state reproduction table, it can be determined whether or not the open state used in the message has been reproduced.

  If it is determined in step BB4 that the open state in which the message is reproduced is not used, the message forwarding unit 121 refers to the forwarding table to check the forwarding destination, sets it as the destination, and sends the message to the packet processing unit 110. (Step BB6).

  If it is determined in step BB4 that the open state in which the message is reproduced is used, the message forward unit 121 sends the message to the open state reproduction unit 160 (step BB5), and ends the process.

  FIG. 14 is a flowchart showing the operation of the file duplicating means of the second embodiment. Referring to FIG. 14, the file copying unit 131 receives a migration start instruction from the system administrator (step BC1), and starts processing. The file duplicating means 131 that has started the processing first turns on the migration flag (step BC2).

  Next, the file duplicating unit 131 duplicates the migration source file to the migration destination (step BC3). Next, the file copying unit 131 switches the client access from the movement source to the movement destination (step BC4). Finally, the file copying unit 131 sets the migration flag to OFF (Step BC5) and ends the process.

  The steps BC1 to BC5 are the same as those in the flowchart of the first embodiment shown in FIG. However, detailed operations of Step BC3 and Step BC4 are different from those of the first embodiment. Details of step BC3 will be described later with reference to FIG. 15, and details of step BC4 will be described later with reference to FIG.

  FIG. 15 is a flowchart showing an operation in which the file duplicating unit of the second embodiment duplicates a source file to a destination. Referring to FIG. 15, the file replication unit 131 first creates a synchronization state management tree (step BD1). The synchronization state management tree describes a directory tree to be migrated. Also, the synchronization status management tree describes whether or not each file constituting the directory tree has been copied. Further, the synchronization state management tree of the second embodiment is different from that of the first embodiment, and further describes whether each file has reproduced the open state.

  Next, the file duplicating unit 131 repeats the processing from step BD3 to step BD5 until all the files listed in the synchronization state management tree have been duplicated and are not checked for update ( Step BD2).

  First, the file copying unit 131 checks whether or not the migration target has been updated (step BD3). The details of the processing of BD3 in the step are the same as those in the first embodiment shown in FIG.

  Next, the file copying unit 131 selects one file that has not been copied from the files in the synchronization state management tree (step BD4). Next, the file duplicating unit 131 duplicates the selected file to the destination (step BD5). At this time, when the file duplication unit 131 finishes duplicating the file, the file duplicating unit 131 puts the file into a duplicated state on the synchronization state management tree. Since the flow shown in FIG. 15 is simplified except for the characteristic part, the migration does not end when the file access protocol is the compulsory lock method and the file has an exclusive lock. However, this may be solved as in steps AD5 to AD7 of the first embodiment.

  When there are no more unreplicated files in the synchronization state management tree, the file replication unit 131 exits the loop of step BD2 and turns on the forward blocking flag (step BD6).

  Finally, the file copying unit 131 confirms whether there is any inconsistent migration target (step BD7) and ends the process. Details of the processing in step BD7 are the same as those in the first embodiment shown in FIG.

  FIG. 16 is a flowchart illustrating an operation in which the file copying unit according to the second embodiment switches the access from the client from the movement source to the movement destination. Referring to FIG. 16, the file duplicating unit 131 first rewrites the forwarding table so that the access to the movement source moves to the movement destination (step BE1). Next, the file duplicating means 131 turns on the open state reproduction flag (step BE2). Finally, the file duplicating unit 131 turns off the forward blocking flag (step BE3) and ends the process.

  FIG. 17 is a flowchart showing the operation of the open state information management unit of the second embodiment. Referring to FIG. 17, when the open state information management unit 150 receives data from the message forward unit 121 or an inquiry from the open state reproduction unit 160 (step BF1), the open state information management unit 150 starts processing.

  The open state information management unit 150 first determines whether data is received from the message forward unit 121 or an inquiry from the open state reproduction unit 160 (step BF2).

  If the data is received from the message forwarding means 121, the open state information management means 150 checks whether the data is a request message, a success response message, or a failure response message (step BF3).

  If it is a request message, the open state information management means 150 once holds the information and message number of the request for changing the open state from the message (step BF4), and ends the processing.

  The message number is held in order to check which request is responded when there is a response later. The information of the request that changes the open state is retained because there is information included only in the request, and when the success response is received, that is, when the request is accepted, the information is recorded. Examples of information included only in the request include a lock type, a lock range, and a file pointer.

  If the message is a success response message, the open state information management unit 150 records the open state information from the held information (step BF5), and ends the process.

  If the message is a failure response message, the open state information management unit 150 discards the stored information (step BF6) and ends the process.

  In step BF5 and step BF6, it can be determined from the message number to which request the response corresponds.

  The open state information to be recorded includes information on a lock applied to the entire file, a partial lock such as a byte range lock, and a file pointer offset state.

  The open state information management unit 150 records the open state information for each token given to the message in order to manage the open state in an identifiable manner. Usually, tokens are implemented as file identifiers in messages.

  Note that, depending on the file access protocol, not only the token passed from the server when the file was opened, but also the token passed when the user was authenticated, passed when permission to access the volume was received. The open state cannot be identified without using various tokens such as a token. In this case, the open state information may be described for each token combination.

  If it is determined in step BF2 that the query is from the open state reproduction unit 160, the open state information management unit 150 sends the open state information to the open state reproduction unit 160 (step BF7), and the process is terminated.

  FIG. 18 is a flowchart showing the operation of the open state reproducing means of the second embodiment. Referring to FIG. 18, the open state reproduction unit 160 receives data from the message forward unit 121 or the packet processing unit 110 (step BG1), and starts processing. First, the open state reproduction means 160 checks where data has been received (step BG2).

  If the data is received from the message forward means 121, the open state reproduction means 160 confirms the contents of the data (step BG3).

  If the content of the data is a message, the open state reproducing unit 160 replaces the token of the message and sends it to the packet processing unit 110 (step BG4) to complete the processing by proxy transfer. At this time, with reference to the open state reproduction table, the token passed from the migration source server to the client is replaced with the token passed from the migration destination server to the intermediate apparatus 102 acting as a proxy for the client.

  If it is determined in step BG3 that the content of the data is an open state reproduction request, the open state reproduction unit 160 reproduces the open state (step BG5) and ends the process. Details of the process of step BG5 will be described later with reference to the flowchart of FIG.

  If it is determined in step BG2 that the data is received from the packet processing means 110, the token of the data content message is replaced and sent to the message forward means 121 in the opposite direction to the processing of BG4 (step BG6). finish.

  FIG. 19 is a flowchart illustrating an operation in which the open state reproducing unit according to the second embodiment reproduces the open state. Referring to FIG. 19, first, the open state reproduction unit 160 inquires of the open state management unit 150 about the open state information of the file targeted by the message, using the file identifier included in the message (step BH1). . When the open state reproduction unit 160 receives a response from the open state management unit 150 that no user has set an open state for the file, the open state reproduction unit 160 ends without performing the subsequent processing. In some cases, the open state of a plurality of users is set in one file.

  When receiving a response indicating that at least one open state information is set, the open state reproducing means 160 reproduces the open state information (step BH2). At that time, the open state reproduction means 160 reproduces each open state one by one. The open state reproduction unit 160 opens the file of the movement destination server when reproducing the open state. When the open state reproduction unit 160 receives permission to open the file, a token is passed from the movement destination server.

  Next, the open state reproduction unit 160 associates the token passed from the migration destination server when the file open permission is received with the token passed from the migration source server to the user before reproducing the open state. And the correspondence information is described in the open state reproduction table (step BH3).

  Note that, depending on the file access protocol, not only the token passed from the server when the file was opened, but also the token passed when the user was authenticated, passed when permission to access the volume was received. The open state cannot be identified without using various tokens such as a token. In this case, other tokens are also described in the open state reproduction table.

  According to the present embodiment, the message forwarding means 121 transfers and monitors a message between the file server 14 and the client 11 according to the forwarding table, and if there is a request or response that changes the open state, the content is displayed. The open state information management unit 150 is notified, and if there is an update request or response during file migration, the contents are notified to the file duplication unit 131. Further, the message forward unit 121 checks whether or not it is necessary to reproduce the open state after the file migration is completed, and if necessary, sends an open state reproduction request to the open state reproduction unit 160. In addition, if there is a message to be sent in a state in which the open state is reproduced, the message forward unit 121 sends it to the open state reproduction unit 160 instead of the packet processing unit 110 for proxy transfer.

  Based on the notification from the message forward unit 121, the open state information management unit 150 manages the open state information by recording the open state of each file in association with the token, and sends an inquiry from the open state reproduction unit 160. When received, it notifies the open state reproduction means 160 of the managed open state information.

  When the file duplicating unit 131 creates a copy of the file in the file migration and knows from the notification from the message forwarding unit 121 that the copied file has been updated during the file migration, the file duplicating unit 131 performs the duplication of the file again and makes it consistent. When the copying of the file is completed in a state where it is removed, the forwarding table by the message forwarding means 121 is switched for the access from the client by updating the forwarding table.

  When the open state reproduction unit 160 receives the open state reproduction request from the message forward unit 121, the open state reproduction unit 160 inquires the open state information management unit 150 to reproduce the open state, records the token association information in the open state reproduction table, and opens the open state. After reproducing the state, the token of the message to be sent in the state in which the open state is reproduced is changed according to the open state reproduction table and transferred as a proxy for the message forward unit 121.

  Therefore, the intermediate device 102 can copy the file in a consistent state, reproduce the open state, and then switch the access of the client. The file can be migrated by keeping the open state in the protocol, and file migration in the online state does not cause file destruction or abnormal termination of the application.

  In this embodiment, an example in which the open state reproduction flag is set for each file server is shown. However, the open state reproduction flag is not necessarily set for each file server. For example, the open state reproduction flag may be set for each migration or for each file. .

  When the open state reproduction flag is set for each file, the flag is turned ON when replication is completed. However, the flag is turned on only for files that need to be reproduced in the open state, in other words, only the files for which the open state has been set on the source server. Further, the flag can be turned OFF when the open state set in the source server by the user is no longer used. For example, it is only necessary to recognize that the open state is not used because the TCP connection from the client used by the user is disconnected. Alternatively, the flag may be turned OFF when a predetermined period has elapsed since the flag was turned ON.

It is a block diagram which shows the structure of the client server system by the 1st Embodiment of this invention. It is a block diagram which shows the structure of the intermediate | middle apparatus 101 of 1st Embodiment. It is a flowchart which shows operation | movement of the packet processing means of 1st Embodiment. It is a flowchart which shows the operation | movement of the message forwarding means of 1st Embodiment. It is a flowchart which shows operation | movement of the file replication means of 1st Embodiment. It is a flowchart which shows the operation | movement which the file replication means of 1st Embodiment replicates the movement origin file to a movement destination. It is a flowchart which shows the operation | movement which the file replication means of 1st Embodiment checks whether it is updated by the migration object. It is a flowchart which shows the operation | movement which the file replication means of 1st Embodiment confirms that there is no inconsistency in a migration object. FIG. 3 is a flowchart showing an operation in which the file duplicating unit in FIG. It is a flowchart which shows operation | movement of an exclusive lock state information management means. It is a block diagram which shows the structure of the intermediate | middle apparatus 102 of 2nd Embodiment. It is a flowchart which shows the operation | movement of the message forwarding means of 2nd Embodiment. It is a flowchart which shows the operation | movement which the message forwarding means of 2nd Embodiment sends a message to an open state reproduction means or a packet processing means. It is a flowchart which shows operation | movement of the file replication means of 2nd Embodiment. It is a flowchart which shows the operation | movement which the file replication means of 2nd Embodiment replicates the file of a movement origin to a movement destination. It is a flowchart which shows the operation | movement which the file replication means of 2nd Embodiment switches the access from a client from a movement origin to a movement destination. It is a flowchart which shows operation | movement of the open state information management means of 2nd Embodiment. It is a flowchart which shows operation | movement of the open state reproduction means of 2nd Embodiment. It is a flowchart which shows the operation | movement in which the open state reproduction means of 2nd Embodiment reproduces an open state.

Explanation of symbols

11 Client 11a User 11b Redirector 12 Network 14 Server 101 Intermediate device 110 Packet processing means 120, 121 Message forward means 130, 131 File replication means 140 Exclusive lock state information management means 150 Open state information management means 160 Open state reproduction means AA1 to AA5 , AB1 to AB9, AC1 to AC5, AD1 to AD9, AE1 to AE6, AF1 to AF2, AG1 to AG2, AH1 to AH7, BA1 to BA7, BB1 to BB6, BC1 to BC5, BD1 to BD7, BE1 to BE3, BF1 ~ BF7, BG1 ~ BG6, BH1 ~ BH3 Step

Claims (12)

An information processing apparatus that is routed through communication between a plurality of servers that store files and a client that accesses the server,
Relay the message transfer between the client and the server, investigate whether the message is a request or response to change the open state, and if the message is a request or response to change the open state Message forwarding means for sending a copy of the message;
Open state information management means for managing each open state information of the file based on a copy of the message sent from the message forward means ;
File replication means for switching access to the file to the replication after creating a replication of the file between the servers;
After the access to the file is switched to the copy, before Symbol in contact open state information management means acquires the open state information, if it is the open file in the source server, the destination server to open An information processing apparatus having open state reproduction means for reproducing the information. Before Symbol open state information management means receives and holds the information contained in the request message for changing the open state from the message forward unit receives the information request by the request message is included in the response message that the accepted The information processing apparatus according to claim 1, wherein the open state information is updated. The open state reproduction means opens the copy on the movement destination server of the file that has been opened on the movement source server, acquires a first token from the movement destination server, and the file is on the client. Reproducing the open state by recording the correspondence between the second token and the first token that were passed from the source server to the user when the user was opened at the source server by The information processing apparatus according to claim 1 or 2. When the open state reproduction means reproduces the open state, when the user is authenticated, when the third token passed from the source server to the user or the volume where the file exists is accessed The information processing apparatus according to claim 3, further recording a correspondence between a fourth token passed from the source server to the user and a token passed from the destination server corresponding to the fourth token. A file management method for managing the file of the server in an information processing apparatus that is routed through communication between a plurality of servers that store files and a client that accesses the server,
Relay the message transfer between the client and the server, investigate whether the message is a request or response to change the open state, and if the message is a request or response to change the open state Generating a copy of the message;
A step of managing an open state information of each of the file based on a copy of the message,
Create a copy of files between previous SL server, the steps of switching the access to the file in said replication,
After the access to the file is switched to the copy, before Symbol open state information, the mobile if the file is opened in the original server, the file management method and a step of reproducing the open state to the destination server. When there is a request message for changing the open state, holds the information included in the request message,
To update the open state information and receiving a response message indicating that the request by the request message has been accepted, the file management method according to claim 5, wherein. Open the copy on the destination server of the file that was opened on the source server to obtain a first token from the destination server;
By recording the correspondence between the second token and the first token passed from the source server to the user when the file is opened at the source server by the user on the client The file management method according to claim 5, wherein the open state is reproduced. When reproducing the open state, when the user is authenticated, the third token passed from the migration source server to the user, or the user from the migration source server when accessing the volume in which the file exists is accessed. The file management method according to claim 7, further recording a correspondence between the fourth token passed to the token and the token passed from the destination server corresponding to the fourth token. A file management program for causing an information processing device to communicate via a plurality of servers storing files and a client accessing the server to manage the files of the server,
Relay the message transfer between the client and the server, investigate whether the message is a request or response to change the open state, and if the message is a request or response to change the open state Generating a copy of the message;
A step of managing an open state information of each of the file based on a copy of the message,
Create a copy of the files between the previous SL server, and the procedure for switching access to the file to the plurality made,
After the access to the file is switched to the copy, before Symbol open state information, if the file is opened in the source server, and a procedure to reproduce the open state to the destination server, causes the computer to execute File management program for. When there is a request message for changing the open state, holds the information included in the request message,
10. The file management program according to claim 9 , wherein the open state information is updated when a response message indicating that the request by the request message has been accepted is received. Open the copy on the destination server of the file that was opened on the source server to obtain a first token from the destination server;
By recording the correspondence between the second token and the first token passed from the source server to the user when the file is opened at the source server by the user on the client The file management program according to claim 9 or 10, which reproduces an open state. When reproducing the open state, when the user is authenticated, the third token passed from the migration source server to the user, or the user from the migration source server when accessing the volume in which the file exists is accessed. The file management program according to claim 11, further recording a correspondence between the fourth token passed to, and the token passed from the destination server corresponding to the fourth token.

Images