File transmission method and device, equipment, medium and program product

Abstract

The invention provides a file transmission method and device, equipment, a storage medium and a program product, which can be applied to the field of distributed technologies. The file transmission method comprises the following steps: receiving a request initiated by a first application server and used for indicating file transmission between a first storage device and a second storage device; determining at least one file transmission service cluster associated with the second application service cluster according to the request, the at least one file transmission service cluster comprising at least one of an original file transmission service cluster and an updated file transmission service cluster, the updated file transmission service cluster is obtained by upgrading and transforming an original file transmission service cluster, and the original file transmission service cluster and the updated file transmission service cluster use the same node identifier; and sending the request to a target file transmission server in at least one file transmission service cluster, so that the target file transmission server sends a to-be-transmitted file contained in the request to a second storage device.

Description

Technical Field

[0001] This disclosure relates to the field of distributed technology, and more specifically to a file transfer method, apparatus, device, medium, and program product. Background Technology

[0002] During the upgrade and transformation of an existing application environment (such as localization), a transition between the original and new application environments is typically required. After ensuring the stability of the new application environment, the original application environment is then taken offline. During this transition phase, file transfers between storage devices usually require modifications to both the file sender and receiver. The more senders involved, the greater the modification workload. Because this involves altering the old sending logic, improper handling can result in only one receiver receiving the file or neither side receiving it. Furthermore, after the transition phase, the original application environment will be completely taken offline, and the file sender must remove the link from the original application environment. Again, the more senders involved, the greater the modification workload. Improper handling can also lead to the new application environment being unable to receive files. Summary of the Invention

[0003] In view of the above problems, this disclosure provides a file transfer method, apparatus, device, medium and program product.

[0004] According to a first aspect of this disclosure, the method includes: receiving a request initiated by a first application server to instruct a file transfer between a first storage device and a second storage device, wherein the first storage device is associated with a first application service cluster to which the first application server belongs, and the second storage device is associated with a second application service cluster; determining, based on the request, at least one file transfer service cluster associated with the second application service cluster, wherein the at least one file transfer service cluster includes at least one of an original file transfer service cluster and an updated file transfer service cluster, wherein the updated file transfer service cluster is obtained by upgrading the original file transfer service cluster, and the original file transfer service cluster and the updated file transfer service cluster use the same node identifier; and sending the request to a target file transfer server in the at least one file transfer service cluster, such that the target file transfer server sends the file to be transferred contained in the request to the second storage device.

[0005] According to embodiments of this disclosure, sending a request to a target file transfer server in at least one file transfer service cluster includes: determining a set of cluster addresses associated with a node identifier, wherein the set includes at least one of the following: addresses of multiple file transfer servers in the original file transfer service cluster, addresses of multiple file transfer servers in the updated target file transfer service cluster; determining a target address from the set of cluster addresses, and sending the request to the file transfer server corresponding to the target address.

[0006] According to embodiments of this disclosure, determining the set of cluster addresses associated with a node identifier includes: determining the set of cluster addresses associated with a node identifier through a file transfer service registry, wherein the file transfer service registry is used to maintain the address set of each cluster providing file transfer services.

[0007] According to a second aspect of this disclosure, the method includes: receiving a request initiated by a first application server for instructing a file transfer between a first storage device and a second storage device, wherein the first storage device is associated with a first application service cluster to which the first application server belongs, the second storage device includes an original second storage device and an updated second storage device, the updated second storage device being an upgrade of the original second storage device, and one of the original second storage device and the updated second storage device is associated with a second application service cluster, wherein the request is sent according to any of the methods described above; in response to the second application service cluster being associated with the original second storage device, sending the file to be transferred contained in the request to the original second storage device; and in response to the second application service cluster being associated with the updated second storage device, sending the file to be transferred contained in the request to the updated second storage device.

[0008] According to embodiments of this disclosure, the method further includes: in response to the second application service cluster meeting preset conditions, mounting the second application service cluster to an updated second storage device so that the second application service cluster is associated with the updated second storage device; sending files in the original first storage device to the updated second storage device; and deleting the addresses of multiple file transfer servers in the original target file transfer service cluster from the cluster address set associated with node identifiers.

[0009] According to embodiments of this disclosure, the method further includes: in response to the second application service cluster not meeting preset conditions, mounting the second application service cluster to the original second storage device, so that the second application service cluster is associated with the original second storage device.

[0010] According to embodiments of this disclosure, the second application service cluster includes an original second application service cluster and an updated second application service cluster. The updated second application service cluster is obtained by upgrading and transforming the original second application service cluster. The preset conditions include: performing a file transfer test on the second application server of the updated second application service cluster using a test file, and the test result is that there are log records of the transfer of the test file on the second application server and the test file exists in the original second storage device; obtaining the execution results of the business tasks executed by each second application server in the updated second application service cluster within a preset time period, and the execution results are all successful.

[0011] A third aspect of this disclosure provides a file transfer apparatus, comprising: a first receiving module, configured to receive a request initiated by a first application server instructing a file transfer between a first storage device and a second storage device, wherein the first storage device is associated with a first application service cluster to which the first application server belongs, and the second storage device is associated with a second application service cluster; a determining module, configured to determine, based on the request, at least one file transfer service cluster associated with the second application service cluster, wherein the at least one file transfer service cluster includes at least one of an original file transfer service cluster and an updated file transfer service cluster, wherein the updated file transfer service cluster is obtained by upgrading the original file transfer service cluster, and the original file transfer service cluster and the updated file transfer service cluster use the same node identifier; and a first sending module, configured to send the request to a target file transfer server in the at least one file transfer service cluster, so that the target file transfer server sends the file to be transferred contained in the request to the second storage device.

[0012] A fourth aspect of this disclosure provides a file transfer apparatus, comprising: a second receiving module, configured to receive a request initiated by a first application server for instructing a file transfer between a first storage device and a second storage device, wherein the first storage device is associated with a first application service cluster to which the first application server belongs, the second storage device includes an original second storage device and an updated second storage device, the updated second storage device being an upgrade of the original second storage device, and one of the original second storage device and the updated second storage device is associated with a second application service cluster, wherein the request is sent according to any of the methods described above; a second sending module, configured to send the file to be transferred contained in the request to the original second storage device in response to the second application service cluster being associated with the original second storage device; and a third sending module, configured to send the file to be transferred contained in the request to the updated second storage device in response to the second application service cluster being associated with the updated second storage device.

[0013] A fifth aspect of this disclosure provides an electronic device comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0014] A sixth aspect of this disclosure also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed by a processor, implement the steps of the above-described method.

[0015] The seventh aspect of this disclosure also provides a computer program product, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method. Attached Figure Description

[0016] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0017] Figure 1 The diagram illustrates a schematic principle of a file transfer method according to one embodiment.

[0018] Figure 2 The illustrations depict application scenarios of file transfer methods, apparatuses, devices, media, and program products according to embodiments of the present disclosure.

[0019] Figure 3 A flowchart illustrating a file transfer method according to an embodiment of the present disclosure is shown schematically.

[0020] Figure 4 A flowchart illustrating a file transfer method according to another embodiment of the present disclosure is shown schematically;

[0021] Figure 5 A schematic diagram illustrating a file transfer method according to an embodiment of the present disclosure is shown.

[0022] Figure 6 A schematic diagram illustrating a file transfer method according to another embodiment of the present disclosure is shown.

[0023] Figure 7 A schematic block diagram of a file transfer apparatus according to an embodiment of the present disclosure is shown.

[0024] Figure 8 A schematic block diagram of a file transfer apparatus according to another embodiment of the present disclosure is shown; and

[0025] Figure 9 A block diagram schematically illustrates an electronic device suitable for implementing a file transfer method according to an embodiment of the present disclosure. Detailed Implementation

[0026] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0027] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0028] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0029] When using expressions such as "at least one of A, B and C", they should generally be interpreted in accordance with the meaning that is commonly understood by those skilled in the art (e.g., "a system having at least one of A, B and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B and C, etc.).

[0030] Figure 1 The diagram illustrates a schematic principle of a file transfer method according to one embodiment.

[0031] like Figure 1 As shown, the first storage device 110 can be a Network Attached Storage (NAS) disk, a device or system that stores data via network sharing. Its working principle is to connect the storage device to one or more computers via a network, allowing these computers to access the data in the NAS disk as if it were local storage. Typically, an application service cluster shares file storage and access via the NAS disk. For example, if a single node in the application service cluster 120, such as application server 121, writes or modifies a file on the first storage device 110, other application servers in the application service cluster 120 (such as application server 122 and application server 123) can read the contents of that file.

[0032] File transfer across NAS drives is generally achieved through Network File Transfer (NFT) service technology. This means that all nodes in the application service cluster deploy file transfer servers (NFT servers), and multiple NFT servers form an NFT service cluster. Each NFT service cluster has an NFT service node number. The NFT service node number is used for NFT service cluster addressing. For example, if the nodes in the application service cluster deploy file transfer servers 131, 132, and 133 respectively, these three NFT servers form a file transfer service cluster 130.

[0033] When files need to be transferred between NAS drives, any single node in the application service cluster acts as the sender and invokes the local NFT server. The local NFT server accesses the NFT service registry based on the node number of the NFT service cluster to obtain the address of the target file transfer server. The local NFT server then sends a file transfer request to the target NFT server. The target file transfer server receives the file and writes it to the NAS drive, thus enabling file transfer between application service clusters.

[0034] When an application service cluster is upgraded or modified (such as for localization), a transition upgrade is generally required with both the old and new clusters running side-by-side. The new application service cluster will use entirely new NAS disks and NFT node numbers. The existing upstream NFT sender needs to be modified to send NFTs to both the old and new NFT nodes to ensure that both the old and new application service clusters can read the same file content during the side-by-side operation phase.

[0035] like Figure 1 As shown, when the application service clusters are upgraded or modified, application service cluster 150 and file transfer service cluster 140 remain the old application environment, using the old secondary storage device 180. Application service cluster 170 and file transfer service cluster 160 remain the new application environment, using the new secondary storage device 190. File transfer service cluster 130 is the sender of files transferred across NAS drives, and application service cluster 120 initiates file transfer requests to file transfer service cluster 130. File transfer service clusters 140 and 160 are the receivers of files transferred across NAS drives. File transfer service cluster 140 uses the old node number, while file transfer service cluster 160 uses the new node number. Both file transfer service clusters 140 and 160 register their node numbers and corresponding IP and port information with the NFT registry center. One node number corresponds to the IP and port information of multiple NFT servers within the NFT cluster.

[0036] For example, the old node number is node number A, which corresponds to the IP and port information of NFT server 141, NFT server 142 and NFT server 143, and the new node number is node number B, which corresponds to the IP and port information of NFT server 161, NFT server 162 and NFT server 163.

[0037] based on Figure 1 For example, you can follow these steps to transfer files across NAS drives.

[0038] Step 1: The NFT server receives an NFT file transfer request initiated by the application server, requesting to send files to both the old NFT service cluster 140 with node number A and the new NFT service cluster 160 with node number B.

[0039] Step 2: The NFT server queries the NFT registry center to obtain the set of NFT service cluster addresses with node number A, and selects an NFT server address from the address set.

[0040] Step 3: The NFT server queries the NFT registry center to obtain the set of NFT service cluster addresses with node number B, and selects an NFT server address from the address set.

[0041] Step 4: The NFT server sends file transfer requests to the NFT server with node number A and the NFT server with node number B respectively, based on the selected server address.

[0042] Step 5: After receiving the file, the NFT server with node number A and the NFT server with node number B write it to the NAS disk of their respective environments. The file content read from the old application service cluster 150 and the new business application service cluster 170 is consistent.

[0043] During the transition phase of bilateral operation, for file transfer requests, the sender needs to send requests to both the old and new NFT clusters. Therefore, the sender needs to be modified to send requests to both clusters. The more senders there are, the greater the modification workload. Furthermore, because it involves altering the old sending logic, improper handling could result in only one receiving party receiving the file, or even both sides failing to receive the file, leading to low fault tolerance. Further, after the bilateral operation transition phase ends, the old system environment will be completely offline, and the file sender needs to delete the link for sending files to the old nodes. The more senders involved, the greater the modification workload. It also involves altering the old sending logic; improper handling could result in the new system being unable to receive files, resulting in low fault tolerance.

[0044] To address the aforementioned issues, this disclosure proposes a file transfer method applicable to local NFT servers. This method configures the original file transfer service cluster and the updated file transfer service cluster to use the same node identifier, so that the sender of the file transfer request, i.e., the local NFT server, does not need to undergo bilateral modifications and can use the original file sending link, thereby avoiding the risks associated with modifications.

[0045] In the technical solution disclosed herein, the user information (including but not limited to user personal information, user image information, user device information, such as location information) and data (including but not limited to data used for analysis, stored data, and displayed data) involved are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, storage, use, processing, transmission, provision, disclosure, and application of related data all comply with relevant laws, regulations, and standards, do not violate public order and good morals, and provide corresponding operation entry points for users to choose to authorize or refuse.

[0046] In scenarios involving automated decision-making using personal information, the methods, devices, and systems provided in this disclosure all offer users corresponding entry points for choosing to agree to or reject the automated decision-making results. If the user chooses to reject, the process proceeds to the expert decision-making stage. Here, "automated decision-making" refers to the activity of automatically analyzing and evaluating an individual's behavioral habits, interests, or economic, health, and credit status through computer programs, and then making a decision. Here, "expert decision-making" refers to the activity of making decisions by personnel who specialize in a particular field, possess specialized experience, knowledge, and skills, and have reached a certain level of professional expertise.

[0047] Figure 2 The illustrations depict application scenarios of file transfer methods, apparatuses, devices, media, and program products according to embodiments of the present disclosure.

[0048] The file transfer method provided in this application embodiment can be applied to, for example, Figure 2 The application scenarios shown are among 200. For example... Figure 2 As shown, the data source 202 accesses the Internet through the first network node set 210, and the data destination 204 accesses the Internet through the third network node set 230. The first network node set 210 and the third network node set 230 are connected via the second network node set 220. Data packets sent by the data source 202 are forwarded through the first network node set 210, the second network node set 220, and the third network node set 230 before finally reaching the data destination 204. The first network node set 210, the second network node set 220, and the third network node set 230 can specifically be switches or routers, and there can be at least two of each. Figure 1The first network node set 210 shown includes a first network node 210a and a second network node 210b; the second network node set 220 includes a third network node 220a, a fourth network node 220b, a fifth network node 220c, and a sixth network node 220d; and the third network node set 230 includes a seventh network node 230a and an eighth network node 230b. The method provided in this application embodiment can be executed at the data source end 202, the network node set (e.g., the first network node set 210, the second network node set 220, or the third network node set 230), or the data destination end 204.

[0049] In one embodiment, the target network node for the next hop determined by the data source 202 is... Figure 2 The second network node 210b can also execute the method provided in the embodiments of this application after receiving the data packet to be forwarded.

[0050] For example, the data source and data destination can be a terminal or a server. Terminals can include, but are not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc. A server can be a server providing various services, such as a backend management server supporting websites browsed by users using the terminal (this is just an example). The backend management server can analyze and process received user requests and other data, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device. A server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services such as cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and basic cloud computing services such as big data. The server can be the backend server of the aforementioned target application, used to provide backend services to the client of the target application.

[0051] The following will be based on Figure 2 The described scene, through Figures 3-6 The file transfer method according to the embodiments of this disclosure will be described in detail.

[0052] Figure 3 A flowchart illustrating a file transfer method according to an embodiment of the present disclosure is shown schematically.

[0053] like Figure 3As shown, the file transfer method of this embodiment includes operations S310 to S330, and can be applied to a local file transfer server.

[0054] In operation S310, a request is received from the first application server to instruct a file transfer between the first storage device and the second storage device.

[0055] In this embodiment of the disclosure, the first storage device is associated with the first application service cluster to which the first application server belongs, and the second storage device is associated with the second application service cluster.

[0056] The first application server can refer to each service node that constitutes the first application service cluster, which can handle different services. The first storage device and the second storage device can refer to NAS disks. Each node in the first application service cluster also deploys an NFT server, i.e., a local file transfer server. In scenarios where file transfer across NAS disks is required, the first application server can initiate a file transfer request and send the request to the local file transfer server.

[0057] The association of a first storage device with a first application service cluster to which a first application server belongs can mean that the first application service cluster interfaces with the first storage device, enabling each first application server in the first application service cluster to retrieve or store files from the first storage device. Similarly, the association of a second storage device with a second application service cluster can mean that the second application service cluster interfaces with the second storage device, enabling each application server in the second application service cluster to retrieve or store files from the second storage device.

[0058] In operation S320, at least one file transfer service cluster associated with the second application service cluster is determined based on the request.

[0059] In this embodiment of the disclosure, at least one file transfer service cluster includes at least one of an original file transfer service cluster and an updated file transfer service cluster. The updated file transfer service cluster is obtained by upgrading and transforming the original file transfer service cluster. The original file transfer service cluster and the updated file transfer service cluster use the same node identifier.

[0060] Specifically, the request may include the node identifier of the file transfer service cluster, which is used to identify the file transfer service cluster, and the file transfer service cluster represented by the node identifier is the recipient of the request.

[0061] In scenarios where the original file transfer service cluster needs to be upgraded or modified, such as through localization, an updated file transfer service cluster needs to be deployed. Both the updated and original file transfer service clusters need to be running. When deploying the updated file transfer service cluster, a node identifier for representing the updated file transfer service cluster needs to be configured. This node identifier can be configured to be the same as that of the original file transfer service cluster. For example, if the original file transfer service cluster uses node number A as its node identifier, then when deploying the updated file transfer service cluster, it can also be configured to use node number A as its node identifier.

[0062] In operation S330, a request is sent to a target file transfer server in at least one file transfer service cluster, so that the target file transfer server sends the file to be transferred contained in the request to a second storage device.

[0063] In this embodiment of the disclosure, after determining the file transfer service cluster, a request can be sent to the target file transfer server in the file transfer service cluster. The request may include the file to be transferred. After receiving the request, the target file transfer server can transfer the file to be transferred to its associated second storage device according to the request.

[0064] Through the embodiments of this disclosure, the original file transfer service cluster and the updated file transfer service cluster are configured to use the same node identifier, so that the sender of the file transfer request, i.e. the local file transfer server, does not need to be modified on both sides and can use the original file sending link, thereby avoiding the risks brought about by modification.

[0065] According to embodiments of this disclosure, sending a request to a target file transfer server in at least one file transfer service cluster includes: determining a set of cluster addresses associated with a node identifier, wherein the set includes at least one of the following: addresses of multiple file transfer servers in the original file transfer service cluster, addresses of multiple file transfer servers in the updated target file transfer service cluster; determining a target address from the set of cluster addresses, and sending the request to the file transfer server corresponding to the target address.

[0066] In this embodiment of the disclosure, the cluster address set can be indexed by node identifiers, thereby associating the cluster address set with node identifiers. The file transfer server address can refer to address information composed of an IP address and a port. The IP address can be the internal network IP address of the application server node, and the port can be used to identify the service provided by the application server. Therefore, the combination of IP address and port can be used to uniquely identify the file server address.

[0067] A preset load balancing algorithm can be used to determine the target address from the cluster addresses. For example, the current number of active connections to all available addresses can be detected, and the address with the fewest connections can be selected as the target address. Furthermore, it can be pre-set that file transfer requests from the same sender are sent to the same target address to ensure session consistency in file transfers. Additionally, either round-robin or random selection of the target address can be chosen.

[0068] Through the embodiments of this disclosure, the cluster address set includes the addresses of multiple file transfer servers in the file transfer service cluster and the addresses of multiple file transfer servers in the updated target file transfer service cluster. This allows the requesting party to send the request to the file transfer server in the updated target file transfer service cluster using the existing node identifier. As a result, the requesting party does not need to modify the sending link, thereby reducing the amount of modification work during the upgrade process.

[0069] According to embodiments of this disclosure, determining the set of cluster addresses associated with a node identifier includes: determining the set of cluster addresses associated with a node identifier through a file transfer service registry, wherein the file transfer service registry is used to maintain the address set of each cluster providing file transfer services.

[0070] In this embodiment of the disclosure, the set of cluster addresses associated with node identifiers can be determined through the file transfer service registry. It is understood that when deploying updated file transfer service clusters and updated application update clusters, an automatic registration process can be performed, that is, the IP address of each application server and the service ports of different services supported by each application server are written to the registry. The file transfer service registry can receive and store the address information of service nodes in each file transfer service cluster, including IP address, port, and may also include running status, etc.

[0071] Furthermore, when it is necessary to determine the set of cluster addresses associated with a node identifier, a query request can be directly sent to the file transfer service registry without relying on local static configuration. The registry retrieves the cluster currently mapped to the node identifier in the request and extracts the active server addresses within that cluster from a real-time maintained list. Finally, these addresses are packaged into a cluster address set and returned to the requester, thus achieving dynamic acquisition of address data.

[0072] Through the embodiments of this disclosure, a file transfer service registry is used to maintain and determine the cluster address set. The registry manages the address set in a unified manner, and the updated cluster actively writes the address information to the registry. This ensures the real-time and accuracy of the obtained cluster address set, and can also automatically adapt to changes such as node expansion, contraction, migration, or failure offline that occur within the cluster.

[0073] Figure 4 A flowchart illustrating a file transfer method according to another embodiment of this disclosure is shown schematically. Figure 4 As shown, the file transfer method of this embodiment includes operations S410 to S430, and can be applied to the recipient of a file transfer request, such as a target file transfer server.

[0074] In operation S410, a request is received from the first application server to instruct a file transfer between the first storage device and the second storage device.

[0075] In this embodiment of the disclosure, the first storage device is associated with the first application service cluster to which the first application server belongs, and the second storage device includes the original second storage device and the updated second storage device. The updated second storage device is obtained by upgrading and modifying the original second storage device. One of the original second storage device and the updated second storage device is associated with the second application service cluster. The request is sent according to any of the above methods.

[0076] In this embodiment, the first application server is the sender of the file transfer request. The first application service cluster mentioned in the first application server is associated with the first storage device; therefore, the file carried in the file transfer request is obtained from the first storage device. The target file transfer server is the receiver of the file transfer request. The target file transfer server is associated with the second application service cluster, and the second application service cluster is associated with the second storage device; therefore, the received file can be transferred to the second storage device. During the upgrade and transformation of the application service cluster, in order to adapt to the updated application service cluster, it is usually necessary to configure an updated storage device. Therefore, the second storage device includes the original second storage device and the updated second storage device.

[0077] In operation S420, in response to the association of the second application service cluster with the original second storage device, the file to be transferred, contained in the request, is sent to the original second storage device.

[0078] In this embodiment of the disclosure, if the second application service cluster is in a bilateral transition phase, both the original second application cluster and the updated second application cluster are associated with the original second storage device, thereby ensuring that the file to be transferred is sent to the original second storage device. In other words, when the second application service cluster is in a bilateral transition phase, the file to be transferred received by the target file transfer server is stored on the original second storage device.

[0079] In operation S430, in response to the second application service cluster associating with the updated second storage device, the file to be transferred, contained in the request, is sent to the updated second storage device.

[0080] In this embodiment of the disclosure, if the second application service cluster is in the final stage of a bilateral transition, the second application cluster is associated with the updated second storage device, thereby ensuring that the file to be transferred is sent to the updated second storage device. Furthermore, since the bilateral transition has ended, it indicates that the updated second application service cluster can operate stably. In other words, when the second application service cluster is in the final stage of a bilateral transition, the file to be transferred received by the target file transfer server is stored on the updated second storage device.

[0081] Through the embodiments of this disclosure, during the bilateral operation transition phase, the file to be transferred is stored in the original second storage device, and during the bilateral operation end phase, the file to be transferred is stored in the updated second storage device. This avoids the data inconsistency problem that may occur if the file to be transferred is stored in both the original second storage device and the updated second storage device at the same time.

[0082] According to embodiments of this disclosure, the method further includes: in response to the second application service cluster meeting preset conditions, mounting the second application service cluster to an updated second storage device so that the second application service cluster is associated with the updated second storage device; sending files in the original first storage device to the updated second storage device; and deleting the addresses of multiple file transfer servers in the original target file transfer service cluster from the cluster address set associated with node identifiers.

[0083] In this embodiment of the disclosure, the preset condition can be a condition that characterizes the stable operation of the second application service cluster, that is, a condition that characterizes the bilateral operation can end. Mounting the second application service cluster to the updated second storage device can mean mapping the file directory of the updated second storage device to the local operating system of the second application service cluster through a standardized network storage protocol, so that when the second application service cluster executes business applications, it can obtain files or store files from the updated second storage device, thereby realizing the association between the second application service cluster and the updated second storage device.

[0084] Furthermore, assuming the second application service cluster is running stably, it is necessary to send the files from the original first storage device to the updated second storage device. Specifically, a third-party tool can be used to achieve a one-time file synchronization. Additionally, it is necessary to take the original target file transfer service cluster and the original application service cluster offline, and remove the addresses of multiple file transfer servers in the original target file transfer service cluster from the cluster address set associated with the node identifier.

[0085] Through the embodiments of this disclosure, after ensuring that the second application service cluster is upgraded, the second application service cluster is then mounted to the updated second storage device. This ensures the reliability of the new environment, the operation of synchronizing historical files guarantees the continuity and integrity of business data, and the deletion of no longer needed cluster addresses from the address set can release resources and prevent subsequent file transfer requests from being incorrectly routed to addresses used during the transition period or to obsolete paths.

[0086] According to embodiments of this disclosure, the method further includes: in response to the second application service cluster not meeting preset conditions, mounting the second application service cluster to the original second storage device, so that the second application service cluster is associated with the original second storage device.

[0087] In this embodiment, the fact that the second application service cluster does not meet the preset conditions indicates that the second application service cluster is not yet running stably or that the upgrade and transformation are not yet completed. Therefore, the second application service cluster needs to be mounted to the original second storage device. That is, the file directory of the original second storage device is mapped to the local operating system of the second application service cluster through a standardized network storage protocol, so that when the second application service cluster executes business applications, it can obtain files or store files from the original second storage device, thereby realizing the association between the second application service cluster and the original second storage device.

[0088] Through the embodiments of this disclosure, when the second application service cluster is not yet running stably or its upgrades are incomplete, storing received files on the original second storage device can avoid large-scale data loss or business interruption due to compatibility or environmental instability issues, thereby maximizing the continuity and stability of business operations.

[0089] According to embodiments of this disclosure, the second application service cluster includes an original second application service cluster and an updated second application service cluster. The updated second application service cluster is obtained by upgrading and transforming the original second application service cluster. The preset conditions include: performing a file transfer test on the second application server of the updated second application service cluster using a test file, and the test result is that there are log records of the transfer of the test file on the second application server and the test file exists in the original second storage device; obtaining the execution results of the business tasks executed by each second application server in the updated second application service cluster within a preset time period, and the execution results are all successful.

[0090] In this embodiment, the preset conditions include passing functional verification and business stability verification of the updated second application service cluster. Functional verification of the updated second application service cluster involves testing the cluster using test files. Specifically, this test task can refer to file transfer tests such as data read / write, business process flow, and large file transfer, to ensure that the updated second application service cluster can transfer files normally and has effective interaction with the updated second storage device. Business stability verification refers to the ability of each second application server in the updated second application service cluster to execute business normally within a predetermined time period, without functional errors, performance timeouts, or data inconsistency issues. The predetermined time period is, for example, 7 days.

[0091] Through the embodiments of this disclosure, file transfer testing on the updated second application service cluster can ensure the real connectivity of the data link, and business stability verification can ensure that the updated second application service cluster can run stably.

[0092] Figure 5 A schematic diagram illustrating a file transfer method according to an embodiment of the present disclosure is shown.

[0093] like Figure 5 As shown, during the transition phase of bilateral operation, file transfer across NAS disks can be performed by following these steps.

[0094] Step 1: The application server in application service cluster 520 calls the NFT server in NFT service cluster 530 to initiate an NFT file transfer request, requesting to send a file to the NFT cluster with node number A.

[0095] Step 2: The NFT server in NFT service cluster 530 queries the NFT registry center to obtain the NFT service cluster address set with node number A, and selects the address information of the target NFT server from the address set.

[0096] Among them, NFT cluster 540 can refer to the original NFT cluster, and NFT cluster 560 can refer to the updated NFT cluster. The node number of both NFT cluster 540 and NFT cluster 560 is A. Therefore, the selected NFT server may belong to NFT cluster 540 or NFT cluster 560.

[0097] Step 3: The NFT service cluster 530 sends a file transfer request, including the file to be transferred, to the target NFT server selected in Step 2 above.

[0098] Step 4: After receiving the file transfer request, the target NFT server writes the file to be transferred carried in the file transfer request to the second storage device 580.

[0099] The second storage device 580 is the original storage device, while the second storage device 590 is an upgraded version of the second storage device 580. During the transition and upgrade phase, the second storage device 590 is idle and not used.

[0100] Figure 6 A schematic diagram illustrating a file transfer method according to another embodiment of the present disclosure is shown.

[0101] like Figure 6 As shown, at the end of the bilateral operation phase, the original storage device synchronizes all existing files to the updated storage device and then goes offline. Simultaneously, the original application service cluster and the original NFT service cluster also go offline, and the updated application service cluster is mounted to the new storage device. During the end of the bilateral operation phase, file transfer across NAS disks can be performed by following these steps.

[0102] Step 1: The application server in the application service cluster 620 calls the NFT server in the NFT service cluster 630 to initiate an NFT file transfer request, requesting to send a file to the NFT cluster with node number A.

[0103] Step 2: The NFT server in NFT service cluster 630 queries the NFT registry center to obtain the NFT service cluster address set with node number A, and selects the address information of the target NFT server from the address set.

[0104] Among them, NFT cluster 660 can refer to the updated NFT cluster. All nodes in NFT cluster 660 are numbered A. Therefore, the selected NFT server belongs to NFT cluster 660.

[0105] Step 3: The NFT service cluster 630 sends a file transfer request, including the file to be transferred, to the target NFT server selected in Step 2 above.

[0106] Step 4: After receiving the file transfer request, the target NFT server writes the file to be transferred carried in the file transfer request to the second storage device 690.

[0107] Based on the above file transfer method, this disclosure also provides a file transfer device, which will be described below in conjunction with... Figure 7 The device is described in detail.

[0108] Figure 7 A schematic block diagram of a file transfer apparatus according to an embodiment of the present disclosure is shown.

[0109] like Figure 7 As shown, the file transfer device 700 of this embodiment includes a first receiving module 710, a determining module 720, and a first sending module 730.

[0110] The first receiving module 710 is used to receive a request initiated by the first application server, instructing a file transfer between the first storage device and the second storage device, wherein the first storage device is associated with the first application service cluster to which the first application server belongs, and the second storage device is associated with the second application service cluster. In one embodiment, the first receiving module 710 may be used to perform the operation S310 described above, which will not be repeated here.

[0111] The determining module 720 is used to determine, based on a request, at least one file transfer service cluster associated with the second application service cluster. The at least one file transfer service cluster includes at least one of an original file transfer service cluster and an updated file transfer service cluster. The updated file transfer service cluster is obtained by upgrading the original file transfer service cluster. The original file transfer service cluster and the updated file transfer service cluster use the same node identifier. In one embodiment, the determining module 720 can be used to perform the operation S320 described above, which will not be repeated here.

[0112] The first sending module 730 is used to send a request to a target file transfer server in at least one file transfer service cluster, so that the target file transfer server sends the file to be transferred contained in the request to a second storage device. In one embodiment, the first sending module 730 may be used to perform the operation S330 described above, which will not be repeated here.

[0113] According to an embodiment of this disclosure, the first sending module 730 includes a set determination module and a first processing module. The set determination module is used to determine a set of cluster addresses associated with a node identifier, wherein the set includes at least one of the following: addresses of multiple file transfer servers in the original file transfer service cluster, and addresses of multiple file transfer servers in the updated target file transfer service cluster. The first processing module is used to determine a target address from the set of cluster addresses and send a request to the file transfer server corresponding to the target address.

[0114] According to embodiments of this disclosure, the set determination module includes a set determination submodule, which is used to determine the set of cluster addresses associated with node identifiers through a file transfer service registry, wherein the file transfer service registry is used to maintain the address sets of each cluster providing file transfer services.

[0115] According to embodiments of this disclosure, any plurality of modules among the first receiving module 710, determining module 720, and first transmitting module 730 may be combined into one module, or any one of these modules may be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules may be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the first receiving module 710, determining module 720, and first transmitting module 730 may be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or any other reasonable means of integrating or packaging circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, at least one of the first receiving module 710, determining module 720, and first transmitting module 730 may be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0116] Based on the above file transfer method, this disclosure also provides a file transfer apparatus. The following will be combined with... Figure 8 The device is described in detail.

[0117] Figure 8 A schematic block diagram of a file transfer apparatus according to an embodiment of the present disclosure is shown.

[0118] like Figure 8 As shown, the file transfer device 800 of this embodiment includes a second receiving module 810, a second sending module 820 and a third sending module 830.

[0119] The second receiving module 810 receives a request initiated by the first application server, instructing a file transfer between the first storage device and the second storage device. The first storage device is associated with the first application service cluster to which the first application server belongs. The second storage device includes an original second storage device and an updated second storage device, the updated second storage device being an upgrade of the original second storage device. One of the original second storage device and the updated second storage device is associated with the second application service cluster. The request is sent according to any of the methods described above. In one embodiment, the second receiving module 810 can be used to perform the operation S410 described above, which will not be repeated here.

[0120] The second sending module 820 is configured to send the file to be transferred, contained in the request, to the original second storage device in response to the association between the second application service cluster and the original second storage device. In one embodiment, the second sending module 820 may be used to perform the operation S420 described above, which will not be repeated here.

[0121] The third sending module 830 is configured to send the file to be transferred, contained in the request, to the updated second storage device in response to the association between the second application service cluster and the updated second storage device. In one embodiment, the third sending module 830 may be used to perform the operation S430 described above, which will not be repeated here.

[0122] According to embodiments of this disclosure, the file transfer device 800 further includes a first mounting module, a fourth sending module, and a deletion module. The first mounting module is used to mount the second application service cluster to an updated second storage device in response to the second application service cluster meeting preset conditions, so that the second application service cluster is associated with the updated second storage device. The fourth sending module is used to send files in the original first storage device to the updated second storage device. The deletion module is used to delete the addresses of multiple file transfer servers in the original target file transfer service cluster from the cluster address set associated with node identifiers.

[0123] According to an embodiment of this disclosure, the file transfer device 800 further includes a second mounting module, which is used to mount the second application service cluster to the original second storage device in response to the second application service cluster not meeting a preset condition, so as to associate the second application service cluster with the original second storage device.

[0124] According to embodiments of this disclosure, the second application service cluster includes an original second application service cluster and an updated second application service cluster. The updated second application service cluster is obtained by upgrading and transforming the original second application service cluster. The preset conditions include: performing a file transfer test on the second application server of the updated second application service cluster using a test file, and the test result is that there are log records of the transfer of the test file on the second application server and the test file exists in the original second storage device; obtaining the execution results of the business tasks executed by each second application server in the updated second application service cluster within a preset time period, and the execution results are all successful.

[0125] According to embodiments of this disclosure, any plurality of modules among the second receiving module 810, the second transmitting module 820, and the third transmitting module 830 may be combined into one module, or any one of these modules may be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the second receiving module 810, the second transmitting module 820, and the third transmitting module 830 may be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented by any other reasonable means of integrating or packaging the circuitry, or implemented in software, hardware, or firmware, or in any suitable combination of any of these three implementation methods. Alternatively, at least one of the second receiving module 810, the second transmitting module 820, and the third transmitting module 830 may be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0126] Figure 9 A block diagram schematically illustrates an electronic device suitable for implementing a file transfer method according to an embodiment of the present disclosure.

[0127] like Figure 9 As shown, an electronic device 900 according to an embodiment of the present disclosure includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage portion 908 into a random access memory (RAM) 903. The processor 901 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 901 may also include onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0128] RAM 903 stores various programs and data required for the operation of electronic device 900. Processor 901, ROM 902, and RAM 903 are interconnected via bus 904. Processor 901 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 902 and / or RAM 903. It should be noted that the programs may also be stored in one or more memories other than ROM 902 and RAM 903. Processor 901 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0129] According to embodiments of this disclosure, the electronic device 900 may further include an input / output (I / O) interface 905, which is also connected to a bus 904. The electronic device 900 may also include one or more of the following components connected to the input / output (I / O) interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the input / output (I / O) interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 910 as needed so that computer programs read from it can be installed into the storage section 908 as needed.

[0130] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0131] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 902 and / or RAM 903 and / or one or more memories other than ROM 902 and RAM 903 described above.

[0132] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code enables the computer system to implement the file transfer method provided in the embodiments of this disclosure.

[0133] When the computer program is executed by the processor 901, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0134] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 909, and / or installed from a removable medium 911. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0135] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 909, and / or installed from the removable medium 911. When the computer program is executed by the processor 901, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0136] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on a user's computing device, partially on a user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0137] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0138] Those skilled in the art will understand that the features described in the various embodiments of this disclosure can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments of this disclosure can be combined and / or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0139] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A file transfer method, characterized in that, The method includes: Receive a request from a first application server to instruct a file transfer between a first storage device and a second storage device, wherein the first storage device is associated with a first application service cluster to which the first application server belongs, and the second storage device is associated with a second application service cluster; The request determines at least one file transfer service cluster associated with the second application service cluster, wherein the at least one file transfer service cluster includes at least one of the original file transfer service cluster and the updated file transfer service cluster, wherein the updated file transfer service cluster is obtained by upgrading the original file transfer service cluster, and the original file transfer service cluster and the updated file transfer service cluster use the same node identifier. The request is sent to the target file transfer server in the at least one file transfer service cluster, so that the target file transfer server sends the file to be transferred contained in the request to the second storage device.

2. The method according to claim 1, characterized in that, Sending the request to the target file transfer server in the at least one file transfer service cluster includes: Determine a set of cluster addresses associated with the node identifier, wherein the set includes at least one of the following: addresses of multiple file transfer servers in the original file transfer service cluster, and addresses of multiple file transfer servers in the updated target file transfer service cluster; The target address is determined from the cluster address set, and the request is sent to the file transfer server corresponding to the target address.

3. The method according to claim 2, characterized in that, The determination of the cluster address set associated with the node identifier includes: The file transfer service registry determines the set of cluster addresses associated with the node identifier, wherein the file transfer service registry is used to maintain the address set of each cluster that provides file transfer services.

4. A file transfer method, characterized in that, The method includes: The system receives a request from a first application server to instruct a file transfer between a first storage device and a second storage device, wherein the first storage device is associated with a first application service cluster to which the first application server belongs, the second storage device includes an original second storage device and an updated second storage device, the updated second storage device being an upgrade of the original second storage device, and one of the original second storage device and the updated second storage device is associated with a second application service cluster, wherein the request is sent using the method according to any one of claims 1 to 3; In response to the association between the second application service cluster and the original second storage device, the file to be transferred contained in the request is sent to the original second storage device; In response to the second application service cluster being associated with the updated second storage device, the file to be transferred contained in the request is sent to the updated second storage device.

5. The method according to claim 4, characterized in that, The method further includes: In response to the second application service cluster meeting a preset condition, the second application service cluster is mounted to the updated second storage device so that the second application service cluster is associated with the updated second storage device; Send the files in the original first storage device to the updated second storage device; Remove the addresses of multiple file transfer servers in the original target file transfer service cluster from the cluster address set associated with the node identifier.

6. The method according to claim 5, characterized in that, The method further includes: In response to the second application service cluster not meeting the preset conditions, the second application service cluster is mounted to the original second storage device so that the second application service cluster is associated with the original second storage device.

7. The method according to claim 5 or 6, characterized in that, The second application service cluster includes the original second application service cluster and the updated second application service cluster. The updated second application service cluster is obtained by upgrading and transforming the original second application service cluster. The preset conditions include: A file transfer test was performed on the second application server of the updated second application service cluster using a test file. The test results showed that there were log records of the transfer of the test file on the second application server and that the test file existed in the original second storage device. Obtain the execution results of the business tasks executed by each second application server in the updated second application service cluster within a preset time period, and all execution results are successful.

8. A file transfer device, characterized in that, The device includes: The first receiving module is configured to receive a request initiated by the first application server to instruct a file transfer between the first storage device and the second storage device, wherein the first storage device is associated with the first application service cluster to which the first application server belongs, and the second storage device is associated with the second application service cluster. The determination module is configured to determine at least one file transfer service cluster associated with the second application service cluster according to the request, wherein the at least one file transfer service cluster includes at least one of the original file transfer service cluster and the updated file transfer service cluster, wherein the updated file transfer service cluster is obtained by upgrading the original file transfer service cluster, and the original file transfer service cluster and the updated file transfer service cluster use the same node identifier. The first sending module is used to send the request to the target file transfer server in the at least one file transfer service cluster, so that the target file transfer server sends the file to be transferred contained in the request to the second storage device.

9. A file transfer device, characterized in that, The device includes: The second receiving module is configured to receive a request initiated by the first application server to instruct a file transfer between the first storage device and the second storage device, wherein the first storage device is associated with the first application service cluster to which the first application server belongs, the second storage device includes an original second storage device and an updated second storage device, the updated second storage device being obtained by upgrading the original second storage device, and one of the original second storage device and the updated second storage device is associated with the second application service cluster, wherein the request is sent by the method according to any one of claims 1 to 3; The second sending module is configured to send the file to be transmitted contained in the request to the original second storage device in response to the association between the second application service cluster and the original second storage device; The third sending module is configured to send the file to be transferred contained in the request to the updated second storage device in response to the association between the second application service cluster and the updated second storage device.

10. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

11. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

12. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

Images