WO2012095053A2 - 数据迁移方法和设备 - Google Patents
数据迁移方法和设备 Download PDFInfo
- Publication number
- WO2012095053A2 WO2012095053A2 PCT/CN2012/071820 CN2012071820W WO2012095053A2 WO 2012095053 A2 WO2012095053 A2 WO 2012095053A2 CN 2012071820 W CN2012071820 W CN 2012071820W WO 2012095053 A2 WO2012095053 A2 WO 2012095053A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data migration
- source node
- node
- destination
- source
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/214—Database migration support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements
Definitions
- the embodiments of the present invention relate to the field of information technologies, and in particular, to a data migration method and device. Background technique
- Embodiments of the present invention provide a data migration method and device. Realize the rational use of network resources, improve data migration efficiency, and avoid network congestion.
- an embodiment of the present invention provides a data migration method, including:
- An embodiment of the present invention provides another data migration method, including:
- an embodiment of the present invention further provides a migration platform, including:
- a processing module configured to adjust a quality of service according to a quality of service from a source node to a destination node in the network Describe the data migration tasks to be scheduled in each source node;
- a scheduling module configured to send a scheduling command to the target source node corresponding to the to-be-scheduled data migration task, where the scheduling command is used to schedule the data migration task.
- the embodiment of the invention further provides a node, including:
- a receiving module configured to receive a scheduling command that is sent by the migration platform, where the scheduling command is used to schedule a data migration task to be scheduled, and the data migration task to be scheduled is used by the migration platform according to a source node to a destination node in the network. Quality of service QOS is determined;
- an execution module configured to schedule the data migration task according to the scheduling command.
- the data migration method and device provided by the embodiment of the present invention, by setting a migration platform in the network, the migration platform schedules the data migration task of the source node according to the quality of service QOS of the source node to the destination node in the network, thereby realizing the rational use of the network resource. Improve data migration efficiency and avoid network congestion.
- FIG. 1 is a flowchart of an embodiment of a data migration method provided by the present invention.
- FIG. 2 is a flowchart of still another embodiment of a data migration method provided by the present invention.
- Figure 3a is a schematic diagram of an implementation of a data migration method according to an embodiment of the present invention
- Figure 3b is a flow chart of an embodiment of the migration method of the implementation scenario shown in Figure 3a
- Figure 3c is a flowchart of the implementation shown in Figure 3a.
- Figure 4a is a schematic diagram of an implementation of a data migration method according to another embodiment of the present invention
- Figure 4b is a schematic diagram of an embodiment of the data migration method shown in Figure 4a
- FIG. 5 is a schematic diagram of an implementation scenario of another embodiment of a data migration method according to the present invention
- 6 is a schematic structural diagram of an embodiment of a migration platform provided by the present invention;
- FIG. 7 is a schematic structural diagram of still another embodiment of a migration platform provided by the present invention.
- FIG. 8 is a schematic structural diagram of an embodiment of a node provided by the present invention.
- FIG. 9 is a schematic structural diagram of an embodiment of a node provided by the present invention. detailed description
- FIG. 1 is a flowchart of an embodiment of a data migration method according to the present invention. As shown in FIG. 1, the method includes:
- the execution body of the above steps is a migration platform, which may be any node in the network, for example: a physical machine in the network, or a virtual machine. It can also be a device that is set up independently in the network, or it can be integrated with the nodes in the network. For example: It can be integrated with the device that can be used as the destination node, such as the data center.
- the embodiments of the present invention can be applied to various implementation scenarios such as data migration from a physical machine to a virtual machine in a network, data ranging from a virtual machine to a data source. Therefore, the source node involved in the embodiment of the present invention may be a physical machine in the network or a virtual machine; the destination node may be a virtual machine, a data center, or a data device.
- the source node involved in the embodiment of the present invention refers to a node that registers data migration information on the migration platform, that is, an originating end of a data migration task.
- each source section in the network The point may pre-register the data migration information on the migration platform, and the data migration information may include: migration directory information of the source node, address information of the destination node, and migration directory information of the destination node.
- the migration platform can generate a data migration task according to the data migration information registered by the source node and the address information of the source node, and the migration platform can add the generated data migration task to the scheduling queue of the migration platform.
- the scheduling queue may be set in a processor or a memory module local to the migration platform, where the scheduling queue is used to store a data migration task generated by the migration platform according to the data migration information registered by the source node.
- the migration platform can continuously add the newly generated data migration task to the scheduling queue. After the data migration task in the scheduling queue is executed, the migration platform can delete the executed data migration task in the scheduling queue.
- a node in the network can share its own address information and directory information in the network. Therefore, the source node can obtain the address information of the destination node and the migration directory information of the destination node from the shared network information; In the technology, the nodes in the network can also transfer their own address information and directory information in sequence between other nodes. Therefore, the source node can obtain the address information of the destination node and the migration directory information of the destination node from other nodes in the network.
- the source node in the network can periodically send an Internet Control Message Protocol to the destination node.
- ICMP Internet Control Message Protocol
- the source node detects the packet, and the source node can obtain the quality of service QOS from the source node to the destination node according to the ICMP response packet returned by the destination node, and report the quality of service QOS from the source node to the destination node to the migration. platform.
- the service quality QOS is simply referred to as QOS in this embodiment and the following embodiments.
- the migration platform can also monitor the Internet control protocol sent by the source node to the destination node, and obtain the QOS of the source node to the destination node according to the ICMP response.
- the above is only a feasible implementation manner of the migration platform provided by the present invention to obtain the QOS of the source node to the destination node in the network, but the limitation is not limited thereto.
- the migration platform can also obtain the source in the network through various existing methods.
- the QOS of the node to the destination node can also obtain the source in the network through various existing methods.
- the migration platform can determine the source section according to the quality of service QOS of the source node to the destination node in the network.
- the data migration task to be scheduled in the point That is, the migration platform can determine one or some data migration tasks that need to be scheduled from among multiple data migration tasks that have been generated in the scheduling queue.
- the target source node involved in the embodiment of the present invention is a source node corresponding to the data migration task to be scheduled determined by the migration platform, that is, the originating end of the data migration task to be scheduled.
- the data migration task of the migration platform may be: starting a data migration task that has not performed data migration, and causing the target source node corresponding to the data migration task to perform data migration to the destination node; or: causing the target source node
- the data migration task in which data migration is in progress is suspended (that is, temporarily stopped, data migration can be resumed after a period of time) or stopped (that is, completely stopped, data migration can be restarted, or data migration can be started); Can be: Reduce or increase the data migration rate of the data migration task where the target source node is undergoing data migration.
- the migration platform after the migration platform obtains the QOS of the source node to the destination node, the QOS of all the source nodes in the source network segment can be further calculated to obtain the QOS of the source network segment. Similarly, the migration platform can be Count all the destination nodes in the destination network segment to the QOS of the source node to obtain the QOS of the destination network segment.
- the source network segment of the embodiment of the present invention may be the same subnet IP address segment with one or more source nodes.
- the destination network segment may be the same subnet with one or more destination nodes. IP address segment.
- the QOS of the source network segment or the QOS of the destination network segment may include:
- the migration platform may collect statistics from all source nodes of the same subnet IP address segment to the QOS of the destination node.
- the average value of the QOS of the source network segment is calculated by the QOS value of the total number of ⁇ % from the source node to the destination node in the source network segment.
- the migration platform can aggregate all the destination nodes of the same subnet IP address segment to the QOS of the source node for statistical analysis, and obtain the QOS from the destination node to the source node from the small to the large direction in the destination network segment.
- the QOS value of the total number ⁇ % is used to calculate an average value, which is the QOS of the destination network segment.
- ⁇ % is the sampling ratio of the QOS of the network segment. In order to calculate more reasonable and true, the ratio may be greater than or equal to 70% and less than or equal to 100%. For example: The value may be 80%.
- the migration platform can be based on each source network segment.
- the QOS and/or the QOS of each destination network segment determine the data migration tasks to be scheduled in each source node.
- the migration platform can increase the data migration to be migrated in the source network segment.
- the task that is, the migration platform can initiate more data migration tasks on the source network segment (by sending a scheduling command to the corresponding source node in the source network segment to enable the source node to initiate data migration), and the source in the source network segment.
- the node can perform more data migration operations to improve data migration efficiency in the source network segment.
- the QOS of the source network segment is greater than or equal to the first threshold, the source network segment is congested.
- the migration platform can reduce the number of the source network segment to be migrated.
- the data migration task that is, for the data migration task in which the data migration is being performed, the migration platform can stop or suspend some data migration tasks in the source network segment (by issuing a scheduling command to the corresponding source node in the source network segment to enable the source The node pauses or stops data migration).
- the migration platform can determine whether the destination network segment is congested according to the QOS value of the destination network segment. If the QOS of the destination network segment is smaller than the second threshold, the destination network segment is not congested. Increase the data migration task to be migrated in the destination network segment. That is, the migration platform can start more data migration tasks on the destination network segment.
- the source node is started by sending a scheduling command to the source node corresponding to the data migration task to be scheduled. If the QOS of the destination network segment is greater than or equal to the second threshold, the destination network segment is congested.
- the migration platform can reduce the data migration task to be migrated in the destination network segment. That is, for data migration tasks that are undergoing data migration.
- the migration platform can stop or suspend some data migration tasks in the source network segment (by sending a scheduling command to the source node corresponding to the data migration task to be scheduled, the source node is suspended or stopped).
- the migration platform may not schedule the data migration task, or schedule the data migration task according to the network segment where the network segment or the destination network segment corresponding to the data migration task is congested.
- the first threshold and the second threshold may be set according to experience values or specific conditions in the network. It should be noted that the first threshold of the embodiment of the present invention is used to refer to the QOS threshold of a source network segment, and the corresponding first threshold may be the same or different for different source network segments. Similarly, the second threshold of the embodiment of the present invention is used to refer to the QOS threshold of a destination network segment, and the corresponding second threshold may be the same or different for different destination network segments.
- the migration platform may further increase the data migration task to be migrated or reduce the data migration task to be migrated in the source network segment according to the QOS of the backbone network in the source network segment.
- the backbone network in the source network segment may be the main path in the source network segment. For example, it may be a necessary path for the source node in the source network segment to perform data migration.
- the migration platform does not need to collect the QOS of all the source nodes in the source network segment to the destination node, but can collect the QOS of all the source nodes in the backbone network of the source network segment to the destination node to obtain the QOS of the backbone network.
- the QOS of the backbone network determines to increase the data migration task to be migrated or reduce the data migration task to be migrated in the source network segment.
- the migration platform does not need to collect the QOS of all the destination nodes in the destination network segment to the source node, but can collect the QOS of all the destination nodes in the source network backbone network to the source node to obtain the QOS of the backbone network, according to the QOS of the backbone network. Determine whether to add data migration tasks to be migrated or reduce data migration tasks to be migrated in the destination network segment.
- the migration platform may further adjust the data migration task to be scheduled according to the interface traffic information reported by the network device on the migration path of each source node to the destination node.
- the network device may be a network device on a critical path (for example, a backbone path) in each network segment, for example, a router, a switch, and the like.
- the device has an interface traffic monitoring function, and can report the traffic information of the interface to the migration platform. After the migration platform receives the interface traffic information reported by the network device, if the interface traffic of the network device is greater than or equal to the third set threshold, if the network device is located in a source network segment, the migration platform can reduce the network device to which the network device belongs.
- the data migration task to be migrated in the source network segment, or the data migration rate of the data migration task in the source network segment to which the network device belongs is reduced.
- the migration platform can reduce the data migration task to be migrated in the destination network segment to which the network device belongs, or reduce the data migration task of the data migration task in the destination network segment to which the network device belongs. Rate of movement.
- the QOS of a network segment is large, that is, when the network segment is congested, the interface traffic of the network device in the network segment is usually larger; the QOS value of a certain network segment. If the network segment is not congested, the interface traffic of the network device in the network segment may be large, or may be small, or may be in a normal state. This is because the interface traffic of the network device is related to the processing power of the network in addition to the QOS of the network.
- the migration platform may reduce the data migration task to be migrated in the source network segment to which the network device belongs according to the interface traffic information reported by the network device, for example: You can pause or stop the data migration task of the network device that has a large amount of traffic on the interface.
- the migration platform can also reduce the data migration rate of the data migration task that is undergoing data migration in the source network segment to which the network device belongs.
- the migration platform can reduce the data migration tasks to be migrated in the destination network segment to which the network device belongs according to the interface traffic information reported by the network device. For example, you can pause or stop the network device that has a large interface traffic. Data migration task; or, the migration platform can also reduce the data migration rate of data migration tasks that are undergoing data migration in the destination network segment to which the network device belongs.
- the third threshold can be set according to the experience value or the specific situation in the network. It should be noted that the third threshold of the embodiment of the present invention is used to refer to the interface traffic threshold of a certain network device, and the corresponding third threshold may be the same or different for different network devices.
- the migration platform may further determine whether each source node or destination node is congested according to the QOS of each source node to the destination node. Specifically: If the QOS of the source node to the destination node is greater than or equal to the fourth set threshold, the source node and/or the destination node are congested, and the migration platform can reduce the data migration rate of the data migration task being performed by the source node.
- the QOS of the source node to the destination node involved in the embodiment of the present invention mainly refers to the QOS of the point-to-point.
- the QOS of the path between the source node and the destination node is omitted.
- the migration platform may determine the data migration task to be scheduled according to the QOS of each source network segment or the destination network segment, and further according to each source node to the destination node.
- QOS to determine whether each source node or destination node is congested. If the QOS of the source node to the destination node is greater than or equal to the fourth set threshold, it indicates that the source node and/or the destination node are congested, and the QOS condition of the source node and/or the destination node cannot meet the requirements of the existing data migration task. .
- the migration platform can still reduce the data migration rate of the data migration task being performed by the source node. It can be understood that, as another feasible implementation manner, the migration platform may also directly determine whether the source node and/or the destination node are congested according to the QOS of the source node to the destination node, and then generate the source node and/or the destination node. When congestion occurs, reduce the data migration rate of the data migration task that the source node is performing.
- the fourth threshold may be set according to an empirical value or a specific situation in the network. It should be noted that the fourth threshold involved in the embodiment of the present invention is used to refer to a QOS of a source node to its corresponding destination node, and for a different source node, a QOS of the corresponding destination node is fourth.
- the thresholds can be the same or different.
- the source node in the network has the capability of monitoring the traffic information of the interface, and the source node may report the interface traffic information of the source node to the migration platform, and the migration platform may further determine, according to the interface traffic information of the source node, The data migration rate of the data migration task that the source node is undergoing data migration is reduced to ensure the normal data migration task of the source node and/or the destination node.
- the migration platform may first be combined according to one or any of the following settings: data migration time period, Target network segment and target destination network segment, determine the initial data migration task to be migrated in the source node, and migrate to the initial data.
- the target source node corresponding to the migration task sends a scheduling command to start the initial data migration task of the target source node.
- the migration platform may also determine different initial data migration tasks according to different implementation scenarios.
- the data migration task is data backup from the source node to the destination node
- the migration platform may further perform at least one of a data backup interval, a maximum backup data volume, and a maximum backup bandwidth.
- a data backup interval can be set so that the data center can schedule the data. After the source node performs a mail backup, it can back up the mail at a set time.
- the time period of the data migration may be set to reduce the data migration task or reduce the data migration rate of the data migration task that is performed during the time period from the source node to the destination node; the QOS of the source node to the destination node is small.
- the time period increases data migration tasks and so on.
- the target source network segment is set for the migration platform, and includes the source network segment of the target source node corresponding to the data migration task to be scheduled.
- the target destination network segment is set by the migration platform, and includes the destination node corresponding to the data migration task to be scheduled. Destination network segment.
- the target source network segment of the data migration can be determined according to the number of source nodes in each source segment of the network. Similarly, the target destination segment of the data migration task can also be based on the number of destination nodes in each destination segment of the network. determine.
- the migration platform may determine the target source network segment and/or the target destination network segment according to the traffic volume of each source network segment or destination network segment in the network in each time period.
- the target source node can report the QOS of the source node to the destination node to the migration platform during the data migration process, so that the migration platform can adjust the data migration task to be scheduled according to the QOS of the source node to the destination node, and
- the target source node corresponding to the data migration task sends a scheduling command, which is used to schedule the data migration task.
- the scheduling command can be used to indicate that the target source node starts, stops, or suspends the data migration task, and can also be used to indicate that the target source node adjusts the data migration rate of the data migration task.
- the migration platform adjusts the data migration task, and the scheduling command can be sent to the target source node corresponding to the data migration task to be scheduled, so that the target source node can start, stop, or suspend the data migration task according to the scheduling command, or adjust the data migration rate.
- FIG. 2 is a flowchart of still another embodiment of a data migration method according to the present invention. As shown in FIG. 2, the method includes:
- S201 Receive a scheduling command sent by the migration platform, where the scheduling command is used to schedule the data migration task to be scheduled, and the data migration task to be scheduled is adjusted by the migration platform according to the quality of service QOS of the source node to the destination node in the network;
- the execution body of the above steps is the source node.
- the source node can be a physical machine in the network or a virtual machine.
- the source node can register the data migration information to the migration platform in advance.
- the source node may download the client agent (Client Agent) from the migration platform, and register with the migration agent on the migration platform: according to the migration information, where the data migration information may include: the migration directory information of the source node.
- the address information of the destination node and the migration directory information of the destination node may be obtained by network sharing or sequentially transmitting between nodes.
- the migration platform can generate a data migration task to join the scheduling queue according to the data migration information registered by the source node.
- the source node may periodically send an ICMP probe packet to the destination node, and obtain the QOS of the source node to the destination node according to the ICMP response returned by the destination node.
- the source node may periodically send an ICMP probe packet to the destination node, and send two probe packets each time.
- the first probe packet involves routing and forwarding of the network device.
- the delay is relatively large. Therefore, the source node can determine the delay between the source node and the destination node by responding to the second probe packet by the destination node, and can be based on the delay in a period of time. Packet loss to calculate the average delay, delay jitter, and packet loss, and then determine the source node to the destination node.
- the source node sends an ICMP probe packet to the corresponding destination node every tl time.
- the source node can record the response delay of the second probe packet in each ICMP probe packet sent in each period: It is: dl ... dn, if the packet is lost, the delay is recorded as 0.
- the number of second probe packets sent in the period of the T (recommended T is an integer multiple of tl, and T>10tl) is: T/tl, and the number of responses received by the second probe packet is: m .
- the average delay is: (dl+d2+...dn) /m
- the delay jitter is: Average delay and minimum delay difference (dl+d2+...dn)/m - dmin
- the QOS between the source node and the destination node (the number of received packets * (average delay + X * delay jitter) + the number of lost packets * Y * average delay) / (average delay * number of packets sent) - 1
- X is the QOS impact factor of jitter and Y is the QOS impact factor of packet loss (X, Y may have different values in different network environments).
- the values of X and Y can be 2 and 10 respectively according to the best practice recommendations.
- the maximum QOS index is 2 when the network has no jitter and no packet loss, and the maximum QOS of the network is 9 when the data platform is in the scheduling process. For example, when Q0SO.5 is selected, the current scheduling task is maintained; if Q0S>1, the data task scheduling is reduced.
- the above is only one feasible implementation manner for the source node to obtain the QOS of the source node to the destination node, but does not constitute a limitation on the present invention.
- the source node may also obtain the source node to the destination node by using various existing methods. QOS, not here - enumeration.
- the source node can report the QOS of the source node to the destination node to the migration platform.
- the migration platform can determine the data migration task to be scheduled according to the QOS of the source node reported by the source node in the network to the destination node.
- the specific process of the data migration task to be scheduled by the migration platform can be referred to the previous embodiment, and is not mentioned here.
- the scheduling command sent by the migration platform to the source node may be specifically configured to: start a data migration task that has not performed data migration, and enable the source node to perform data migration to the destination node; or: indicate data migration in which data migration is in progress
- the task is suspended (that is, temporarily stopped, you can continue the data migration after a period of time) or stopped (that is, completely stopped, you can restart the data migration, or you can not start the data migration); you can also: Reduce or increase the The data migration rate of the data migration task for data migration.
- the source node After receiving the scheduling command, the source node performs the corresponding operation indicated by the scheduling command.
- the data migration method provided by the embodiment of the present invention by setting a migration platform in the network, the migration platform schedules the data migration task of the source node according to the quality of service QOS of the source node to the destination node in the network, and after the source node receives the scheduling command, Perform the corresponding operations indicated by the scheduling command to implement reasonable utilization of network resources, improve data migration efficiency, and avoid network congestion.
- the above embodiment describes the data migration method provided by the present invention from the migration platform side and the target source node side respectively.
- FIG. 3 is a schematic diagram of an implementation scenario of another embodiment of a data migration method according to the present invention.
- the implementation scenario provided by the embodiment is that the physical machine (PC) performs data migration to the desktop cloud virtual machine.
- the data migration is usually an operating system to operating system migration, that is, the migrated object is the operating system of the source node.
- Various files under the directory are possible.
- the source node is a distributed physical machine
- the destination node is a centralized desktop cloud virtual machine.
- a PC with the same network segment IP address has the same access and aggregation layer network devices.
- the devices with the same network segment IP address have the same access and aggregation layer network devices. Because the source node compares its access layer and aggregation layer network bandwidth is uncertain and the general exit bandwidth is small, congestion is likely to occur.
- the access network of the destination network has a large bandwidth. There are some necessary aggregation and core network devices in the migration path. There may be bandwidth bottlenecks in the migration path.
- the data migration method provided in this embodiment specifically includes:
- the source node logs in to the migration platform, downloads the migration client agent, installs, and registers the data migration information on the migration platform by using the client agent.
- the data migration information includes: the migration directory information of the source node, the address information of the destination node, and the purpose. Migration directory information for the node.
- the address information of the destination node and the migration directory information of the destination node may be obtained by network sharing or sequentially transmitting between nodes.
- the address information may be an IP address, or a Uniform Resource Locator (URL) or the like.
- the migration platform generates a data migration task according to the data migration information and the address information of the source node.
- the data migration tasks include: migration directory information and address information of the source node, and migration directory information and address information of the destination node.
- the migration platform combines one or any combination of the following information: a data migration time segment, a target source network segment, and a target destination network segment, and determines an initial data migration task to be migrated in each source node.
- the migration platform may reduce the data migration task or reduce the data migration rate of the data migration task in the time period from the source node to the destination node QOS; and may also have a smaller QOS from the source node to the destination node.
- the target source network segment of the data migration may be: reducing the data migration task or reducing the data migration rate of the ongoing data migration task on the source network segment with a larger QOS from the source node to the destination node; comparing the QOS of the source node to the destination node
- the small source network segment increases the data migration task to be migrated, etc.; the destination destination network segment of the data migration is similar to the target source network segment of the data migration, and is not mentioned here.
- the migration platform may not increase or decrease the data migration task to be migrated in the target source network segment and the target destination network segment; or The migration platform can also be based on a larger network segment of QOS, reducing the data migration tasks to be migrated.
- the target source network segment of the data migration can be determined according to the number of source nodes in each source segment of the network.
- the target destination segment of the data migration task can also be based on the number of destination nodes in each destination segment of the network. determine.
- the target source network segment and/or the target destination network segment S304 and the target corresponding to the initial data migration task of the migration platform may be determined according to the QOS situation of each source network segment or the destination network segment in the network in each time segment.
- the source node sends a scheduling command, which is used to start the initial data migration task.
- the client agent of the target source node corresponding to the initial data migration task starts to migrate to the destination node.
- the target source node After the data source is started, the target source node periodically sends an Internet Control Message Protocol (ICMP) packet to the destination node, and obtains the source node according to the average delay, delay jitter, and number of lost packets of the ICMP response packet returned by the destination node. QOS to the destination node.
- ICMP Internet Control Message Protocol
- the source node reports the QOS of the source node to the destination node to the migration platform.
- the target source node can move the target source node to the destination node's QOS on the migration platform in real time, and periodically to the migration platform "3 ⁇ 4 target source node to the destination node's QOS.
- the network device on the migration path from the source node to the destination node reports the interface traffic information to the migration platform.
- the network device on the migration path from the source node to the destination node may be a device such as a switch or a router.
- the network device may be a network device on a critical path from the source node to the destination node.
- the migration platform may first determine the initial data migration task to be migrated in the source node according to information such as the data migration time period, the target source network segment, and the target destination network segment.
- the target source node corresponding to the initial data migration task may report the source node to the destination node to the migration platform during the execution of the scheduling command.
- the QOS, the network device can also send the interface traffic information to the migration platform in the process of executing the scheduling command by the target source node corresponding to the data migration task.
- the migration platform adjusts the data migration task to be scheduled in each source node according to the QOS of the source node to the destination node.
- the migration platform obtains the QOS of the source node to the destination node
- the QOS of all the source nodes in the source network segment can be further calculated to obtain the QOS of the source network segment.
- the migration platform can be The QOS of all destination nodes in the destination network segment to the source node is counted, and the QOS of the destination network segment is obtained.
- the migration platform can collect the QOS of all the source nodes of the same subnet IP address segment to the destination node for statistical analysis, and obtain the QOS from the source node to the destination node from the small to the large direction in the source network segment.
- the QOS value of the total number ⁇ % is used to calculate an average value, which is the QOS of the source network segment.
- the migration platform can aggregate all the destination nodes of the same subnet IP address segment to the QOS of the source node for statistical analysis, and obtain the QOS from the destination node to the source node from small to large in the destination network segment.
- the QOS value of the total number ⁇ % is used to calculate an average value, which is the QOS of the destination network segment.
- Z% is the sampling ratio of the QOS of the network segment. To calculate the more reasonable and realistic, the ratio can be greater than or equal to 70% and less than or equal to 100%.
- the platform can reduce the data migration task to be migrated in the source network segment. That is, for the data migration task that is undergoing data migration, the migration platform can stop or suspend some data migration tasks in the source network segment. If the destination network segment is less than the second threshold and the destination network segment is not congested, the migration platform can increase the data migration task to be migrated in the destination network segment. That is, the migration platform can start more on the destination network segment.
- the data migration task is to enable the source node to initiate data migration by sending a scheduling command to the source node corresponding to the data migration task to be scheduled. If the QOS of the destination network segment is greater than or equal to the second threshold, the destination network segment is congested and migrated.
- the platform can reduce the data migration task to be migrated in the destination network segment. That is, for the data migration task that is undergoing data migration, the migration platform can stop or suspend some data migration tasks in the source network segment.
- the first threshold of the embodiment of the present invention is used to refer to a QOS threshold of a source network segment, and the corresponding first threshold may be the same or different for different source network segments.
- the second threshold of the embodiment of the present invention is used to refer to the QOS threshold of a destination network segment, and the corresponding second threshold may be the same or different for different destination network segments.
- the first threshold and the second threshold can be set based on empirical values or specific conditions in the network.
- the migration platform may further determine the data migration task to be scheduled according to the interface traffic information reported by the network device on the migration path of the source node to the destination node.
- the network device can be a network device on a critical path in each network segment, for example, a router, a switch, and the like.
- the device has an interface traffic monitoring function, and can report the traffic information of the interface to the migration platform.
- the migration platform may use the interface traffic information reported by the network device. The data migration task to be migrated in the source network segment to which the network device belongs is reduced.
- the data migration task of the network device with a large interface traffic can be suspended or stopped.
- the migration platform can also reduce the source network segment to which the network device belongs.
- the data migration task to be migrated in the destination network segment to which the network device belongs is reduced.
- the data migration task of the network device with a large interface traffic can be suspended or stopped.
- the migration platform can also reduce the data migration rate of data migration tasks that are undergoing data migration within the destination network segment to which the network device belongs.
- the QOS value of a network segment is large, that is, when the network segment is congested, the interface traffic of the network device in the network segment is usually large; QOS of a certain network segment If the network segment is not congested, the interface traffic of the network device in the network segment may be large, or may be small, or may be in a normal state. This is because the interface traffic of the network device is related to the processing power of the network in addition to the QOS of the network.
- the migration platform can reduce the data migration tasks to be migrated in the network segment to which the network device belongs according to the interface traffic information reported by the network device, for example, the network device with large interface traffic can be suspended or stopped.
- the data migration task; or, the migration platform can also reduce the data migration rate of the data migration task in the network segment to which the network device belongs.
- the third threshold can be set according to the experience value or the specific situation in the network. It should be noted that the third threshold of the embodiment of the present invention is used to refer to the interface traffic threshold of a certain network device, and the corresponding third threshold may be the same or different for different network devices.
- the migration platform may further determine whether each source node and/or the destination node is congested according to the QOS of each source node to the destination node. Specifically: if the QOS of the source node to the destination node is greater than or equal to the fourth set threshold, the source node and/or the destination node are congested, and the migration platform can reduce data migration of the data migration task of the source node undergoing data migration. rate.
- the QOS of the source node to the destination node involved in the embodiment of the present invention mainly refers to the QOS of the point-to-point, and ignores the QOS of the path between the source node and the destination node.
- the migration platform may adjust the QOS to be scheduled according to the QOS of the source network segment or the destination network segment, and further according to the QOS of each source node to the destination node, that is, the point-to-point QOS. , ignoring the QOS of the path between the source node and the destination node, Whether the source node or the destination node is congested. If the QOS of the source node to the destination node is greater than or equal to the fourth set threshold, it indicates that the source node and/or the destination node are congested, and the QOS condition of the source node or the destination node cannot meet the requirements of the existing data migration task.
- the data migration task to be migrated is added to the source network segment; or the destination network segment to which the destination node belongs is not congested, and the data migration task to be migrated is added to the destination network segment.
- the migration platform can still reduce the data migration rate of the data migration task of the source node that is undergoing data migration.
- the migration platform can also directly judge the QOS of the path between the source node and the destination node according to the QOS of each source node to the destination node, that is, the QOS of the point-to-point node. Whether the source node and/or the destination node are congested, and when the source node and/or the destination node are congested, the data migration rate of the data migration task of the source node undergoing data migration is reduced.
- the fourth threshold is used to refer to the QOS of a source node to its corresponding destination node, and for different source nodes, the QOS of the corresponding destination node.
- the fourth threshold may be the same or different.
- the fourth threshold can be set based on empirical values or specific conditions in the network.
- each source node in the network has the capability of monitoring the traffic information of the interface. Therefore, each source node may report the interface traffic information to the migration platform, and the migration platform may further determine that the source node is being determined according to the interface traffic information of the source node. The data migration rate of the data migration task for data migration is reduced to ensure the normal data migration task of the source node and/or the destination node.
- the migration platform delivers a scheduling command to the target source node corresponding to the data migration task to be scheduled, and the scheduling command is used to schedule the data migration task.
- the target source node executes the scheduling command for the data migration task.
- the scheduling task delivered by the migration platform to the target source node may be used to start a data migration task that has not been subjected to data migration, so that the source node corresponding to the data migration task performs execution.
- Data migration of the destination node also used to pause the data migration task that is undergoing data migration (ie, temporarily stop, can continue data migration after a period of time) or stop (ie, stop completely, then restart data migration) , you can also not start data migration); can also be used to reduce or increase the data migration rate of data migration tasks that are undergoing data migration.
- FIG. 4 is a schematic diagram of an implementation of a data migration method according to another embodiment of the present invention.
- the implementation scenario provided by the embodiment is that the desktop cloud virtual machine backs up data to the data backup, that is, the source node may be The desktop cloud virtual machine in the cloud computing data center, the destination node can be centralized data.
- each access switch under the same aggregation switch, there are multiple access switches, and each access switch is connected to a server of an IP address of a certain network segment.
- a server that may access the IP address of the same network segment under different switches.
- Under the same aggregation of the source nodes there are multiple servers with different network segment IP addresses under the same access switch.
- the servers with the IP addresses of the same network segment exist under multiple access switches.
- the source node does not have a corresponding relationship with the access switch.
- the same source network segment is generally under the same aggregation switch; the source network has sufficient access bandwidth, and the network core above the aggregation layer and the aggregation to the backup end are prone to insufficient bandwidth and network congestion.
- the method specifically includes:
- the source node logs in to the migration platform, downloads the migration client agent, installs, and registers data migration information on the migration platform by using the client agent.
- the data migration information includes: migration directory information of the source node, address information of the destination node, and purpose. Migration directory information for the node. 5402.
- the migration platform generates a data migration task according to the data migration information and the address information of the source node.
- the migration platform combines one or any combination of the following information: a data migration time segment, a target source network segment, and a target destination network segment, and determines at least one initial data migration task of each source node.
- the migration platform may further determine an initial data migration task according to information such as a backup time interval, a maximum backup task number, and a maximum backup bandwidth of the source network segment or the target network segment.
- a source node needs to back up the mail directory to the data center. Since the source node changes the mail directory when receiving new mail, you can set the data backup interval so that the data center can schedule the source node to perform mail backup. After that, the mail backup can be performed at intervals.
- the migration platform sends a scheduling command to the target source node corresponding to the initial data migration task, where the scheduling command is used to indicate that the initial data migration task is started.
- the client agent of the target source node corresponding to the initial data migration task starts to migrate to the destination node.
- the target source node After the data source is started, the target source node periodically sends an Internet Control Message Protocol (ICMP) packet to the destination node, and obtains the source node according to the average delay, the delay jitter, and the number of lost packets of the ICMP response packet returned by the destination node. QOS to the destination node.
- ICMP Internet Control Message Protocol
- the source node reports the QOS of the source node to the destination node to the migration platform.
- the network device on the migration path from the source node to the destination node reports the interface traffic information to the migration platform.
- the migration platform determines, according to the QOS of the source node to the destination node, a data migration task to be scheduled by each source node.
- S401-S409 is similar to that of S301-S309. For details, refer to the related description in S301-S309. As shown in FIG. 4b, the method further includes:
- the migration platform compares the changed data blocks in the file on the target source node and the corresponding destination node.
- the data migration of the source node can be more backup to the destination node. Files, or you can back up part of the data of a file. According to this, if the migration platform and the destination node are integrated (for example, the migration platform can be a module in the destination node), as shown in FIG.
- the migration platform may carry the indication information in the scheduling command sent to the target source node by comparing the changed data block in the change file of the source node and the corresponding destination node, so as to indicate that the target source node only backs up the changed data block without backing up the entire file. , thereby reducing the amount of data backup and improving backup efficiency.
- the migration platform sends a scheduling command to the target source node corresponding to the data migration task to be scheduled, where the scheduling command is used to schedule the data migration task.
- S410 is an optional step. If the migration platform executes S410, the scheduling command sent by the migration platform to the target source node in S411 may carry indication information, where the indication information is used to indicate that the target source node backs up the changed data block in the file to Destination node.
- the target source node After receiving the scheduling command of the migration platform, the target source node performs a scheduling command on the data migration task.
- the target source node may, after receiving the indication information in the scheduling command, back up the changed data block in the file of the target source node according to the indication information.
- each data of the source node is As a new data migration task, the migration platform determines whether to migrate the task to the scheduled data according to the QOS of the source node to the destination node.
- the data migration method in this embodiment, in the implementation scenario of the data segmentation, by setting a migration platform in the network, each desktop cloud virtual machine in the network registers data migration information on the migration platform, and the migration platform generates a data migration task, and According to the service quality QOS of the source node to the destination node in the network, optionally, according to the interface traffic information of the source node, optionally, the data migration task of each source node may be performed according to the interface traffic information of the network device. Scheduling, so as to achieve reasonable use of network resources, improve data migration efficiency, and avoid network congestion.
- the migration platform can also compare the changed data blocks in the target source node and the corresponding destination node, and carry the indication information in the scheduling command sent to the target source node to indicate that the target source node backs up each file.
- the changed data block to the destination node, thereby reducing the amount of data backup and improving the backup efficiency.
- FIG. 6 is a schematic structural diagram of an embodiment of a migration platform provided by the present invention. As shown in Figure 6, the migration platform includes: a processing module 11 and a scheduling module 12;
- the processing module 11 is configured to adjust a data migration task to be scheduled in the source node according to the quality of service QOS of the source node to the destination node in the network;
- the scheduling module 12 is configured to send a scheduling command to the target source node corresponding to the data migration task to be scheduled, and the scheduling command is used to schedule the data migration task.
- the migration platform provided in this embodiment, by setting a migration platform in the network, the migration platform is based on The quality of service from the source node to the destination node in the network QOS schedules the data migration tasks of each source node to achieve reasonable utilization of network resources, improve data migration efficiency, and avoid network congestion.
- FIG. 7 is a schematic structural diagram of still another embodiment of a migration platform according to the present invention.
- the migration platform may further include: a receiving module 13 and a monitoring module 14 At least one of them; where:
- the receiving module 13 is configured to receive a QOS of the source node to the destination node reported by the source node;
- the monitoring module 14 is configured to monitor the Internet control message protocol that the source node periodically sends to the destination node.
- the ICMP probe packet obtains the QOS of the source node to the destination node according to the ICMP response packet returned by the destination node.
- the processing module 11 may be specifically configured to: collect QOS of all source nodes to destination nodes in each source network segment, and obtain QOS of each source network segment; if the QOS of the source network segment is smaller than the first configuration If the threshold is set, the data migration task to be migrated in the source network segment is increased. If the QOS of the source network segment is greater than or equal to the first threshold, the data migration task to be migrated in the source network segment is reduced.
- the processing module 11 may be specifically configured to: collect all the destination nodes in the destination network segment to the QOS of the source node, obtain the QOS of the destination network segment, and connect the QOS and the destination node of the source node to the destination node to The QOS of the source node is equal. If the QOS of the destination network segment is smaller than the second threshold, the data migration task to be migrated in the destination network segment is increased. If the QOS of the destination network segment is greater than or equal to the second threshold, the destination network is reduced. The data migration task to be migrated in the segment.
- the receiving module 13 is further configured to: receive interface traffic information reported by the network device on the migration path from the source node to the destination node;
- the processing module 11 is further configured to: if the interface traffic of the network device is greater than or equal to the third set threshold, if the network device is located in the source network segment, reduce the data migration task to be migrated in the source network segment to which the network device belongs Or, the data migration rate of the data migration task in the source network segment to which the network device belongs is reduced; if the network device is located on the destination network segment, the data migration task to be migrated in the destination network segment to which the network device belongs is reduced. Or, the data migration rate of the data migration task that is undergoing data migration in the destination network segment to which the network device belongs is reduced.
- the processing module 11 is further configured to: if the QOS of the source node to the destination node is greater than or equal to a fourth set threshold, reduce data of the data migration task of the source node that is undergoing data migration Migration rate.
- the QOS of the source node to the destination node involved in the embodiment of the present invention mainly refers to a point-to-point QOS, and ignores the QOS of the path between the source node and the destination node.
- the receiving module 13 is further configured to: receive the interface traffic information reported by the source node, so that the processing module 11 can determine, according to the interface traffic information of the source node, a data migration rate of the data migration task of the source node that is undergoing data migration.
- the processing module 11 is further configured to: determine, according to one or any combination of the following information: a data migration time period, a target source network segment, and a target destination network segment, and determine an initial to be migrated in the source node.
- Data migration task ;
- the scheduling module 12 may be further configured to: send a scheduling command to the target source node corresponding to the initial data migration task, where the scheduling command is used to start the initial data migration task.
- the processing module 11 may further determine an initial data migration task according to one or any combination of the following information: a data backup time interval, a maximum backup data amount, and Maximum backup bandwidth.
- processing module 11 is further configured to: compare the data blocks that are changed in the file on the target source node and the corresponding destination node;
- the scheduling command sent by the scheduling module 12 to the target source node may further carry indication information, where the indication information is used to indicate that the target source node backs up the changed data block in each file to the destination node.
- the migration platform can further include:
- the registration module 15 is configured to obtain data migration information registered by the source node, where the data migration information includes: migration directory information of the source node, address information of the destination node, and migration directory information of the destination node; correspondingly, the processing module 11 may also be used. : Generate data migration tasks based on the data migration information obtained by the registration module and the address information of the source node.
- the migration platform provided in this embodiment, by setting a migration platform in the network, each source node in the network
- the data migration information is registered on the migration platform, and the migration platform generates a data migration task, and according to the service quality QOS of each source node to the destination node in the network, optionally, according to interface traffic information of each source node, optionally,
- the data migration task of each source node can be scheduled according to the interface traffic information of the network device, thereby realizing the rational use of network resources, improving data migration efficiency, and avoiding network congestion.
- the migration platform can also compare the data blocks that are changed in the files of the target source node and the corresponding destination node, and carry the indication information in the scheduling command sent to the target source node to Instruct the target source node to back up the changed data blocks in each file to the destination node, thereby reducing the amount of data backup and improving the backup efficiency.
- the migration platform provided by the embodiment of the present invention may be set independently, or may be integrated with the destination node, for example, a data center.
- the method for the data migration method is the same as the data migration method provided by the embodiment of the present invention.
- FIG. 8 is a schematic structural diagram of an embodiment of a node provided by the present invention. As shown in FIG. 8, the node includes: a receiving module 21 and an executing module 22;
- the receiving module 21 is configured to receive a scheduling command that is sent by the migration platform, where the scheduling command is used to schedule the data migration task to be scheduled, and the data migration task to be scheduled is determined by the migration platform according to the quality of service QOS of the source node to the destination node in the network. ;
- the executing module 22 is configured to schedule a data migration task according to the scheduling command.
- the migration platform schedules data migration tasks of each source node according to the quality of service QOS of each source node to the destination node in the network, and after the source node receives the scheduling command, performs execution.
- the corresponding operations indicated by the scheduling command thereby realizing the rational use of network resources, improving data migration efficiency, and avoiding network congestion.
- FIG. 9 is a schematic structural diagram of an embodiment of a node according to the present invention. As shown in FIG. 9, the node may further include: a sending module 23, a processing module 24, and a reporting module 25, where:
- the sending module 23 is configured to periodically send an Internet Control Message Protocol (ICMP) to the destination node.
- ICMP Internet Control Message Protocol
- the processing module 24 is configured to obtain, according to the ICMP response packet returned by the destination node, the QOS of the source node to the destination node;
- the reporting module 25 is configured to report the QOS of the source node to the destination node to the migration platform.
- the receiving module if the data migration task is data backup from the source node to the destination node, the receiving module
- the received scheduling command may further include indication information, where the indication information is used to indicate that the source node backs up the changed data block in the file to the destination node.
- the node can further include:
- the registration module 26 is configured to register data migration information with the migration platform, where the data migration information includes: migration directory information of the source node, address information of the destination node, and migration directory information of the destination node, so that the data platform migrates information and the source node according to the data.
- the address information generates a data migration task.
- the migration platform in the network schedules the data migration task of each source node according to the quality of service QOS of the source node to the destination node in the network, thereby realizing the rational use of network resources, improving data migration efficiency, and avoiding network congestion.
- the node may reduce the data component according to the data block to the target node in the backup file. Improve backup efficiency.
- the node provided by the embodiment of the present invention is a target source node corresponding to the data migration task to be scheduled, and may be a physical machine or a virtual machine in the network, and the node corresponds to the data migration method provided by the embodiment of the present invention, and is a data migration.
- the specific process of the method for performing the data migration refer to the method embodiment, and details are not described herein again.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2012/071820 WO2012095053A2 (zh) | 2012-03-01 | 2012-03-01 | 数据迁移方法和设备 |
CN201280000571.4A CN103053146B (zh) | 2012-03-01 | 2012-03-01 | 数据迁移方法和设备 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2012/071820 WO2012095053A2 (zh) | 2012-03-01 | 2012-03-01 | 数据迁移方法和设备 |
Publications (3)
Publication Number | Publication Date |
---|---|
WO2012095053A2 true WO2012095053A2 (zh) | 2012-07-19 |
WO2012095053A3 WO2012095053A3 (zh) | 2013-01-31 |
WO2012095053A9 WO2012095053A9 (zh) | 2013-03-14 |
Family
ID=46507500
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2012/071820 WO2012095053A2 (zh) | 2012-03-01 | 2012-03-01 | 数据迁移方法和设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN103053146B (zh) |
WO (1) | WO2012095053A2 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109189756A (zh) * | 2018-06-29 | 2019-01-11 | 平安科技(深圳)有限公司 | 电子装置、数据迁移的方法及存储介质 |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104426795B (zh) * | 2013-09-09 | 2017-09-12 | 中国电信股份有限公司 | 用于负载均衡的方法、节点调度服务器和系统 |
CN104580306B (zh) * | 2013-10-21 | 2018-02-16 | 北京计算机技术及应用研究所 | 一种多终端备份服务系统及其任务调度方法 |
US9558005B2 (en) * | 2014-05-19 | 2017-01-31 | Intel Corporation | Reliable and deterministic live migration of virtual machines |
CN105897604B (zh) * | 2016-04-06 | 2019-04-09 | 中国人民解放军国防科学技术大学 | 一种提高数据中心网络更新成功率的方法 |
CN109391663B (zh) * | 2017-08-10 | 2021-11-16 | 阿里巴巴集团控股有限公司 | 一种访问请求的处理方法与设备 |
CN109002263B (zh) * | 2018-07-20 | 2021-03-19 | 腾讯科技(深圳)有限公司 | 存储容量的调整方法及装置 |
CN109857528B (zh) * | 2019-01-10 | 2021-08-27 | 北京三快在线科技有限公司 | 数据迁移的速度调整方法、装置、存储介质和移动终端 |
CN111104206B (zh) * | 2019-12-25 | 2023-09-01 | 曙光信息产业(北京)有限公司 | 虚拟机存储迁移方法、装置和计算机设备 |
CN113259473B (zh) * | 2021-06-08 | 2021-11-05 | 广东睿江云计算股份有限公司 | 一种自适应云数据迁移的方法 |
CN113590613A (zh) * | 2021-07-13 | 2021-11-02 | 上海一谈网络科技有限公司 | 数据表分区方法、装置、计算机设备和存储介质 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101101563A (zh) * | 2007-07-23 | 2008-01-09 | 清华大学 | 基于海量数据分级存储系统的迁移管理方法 |
CN102147709A (zh) * | 2010-02-05 | 2011-08-10 | Lsi公司 | 基于服务质量的存储分层与迁移技术的系统和方法 |
CN102170396A (zh) * | 2011-05-06 | 2011-08-31 | 浙江大学 | 一种基于区分服务的云存储系统QoS控制方法 |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080008183A1 (en) * | 2004-12-28 | 2008-01-10 | Keiichi Takagaki | Communication Device, Storage Medium, Integrated Circuit, and Communication System |
-
2012
- 2012-03-01 WO PCT/CN2012/071820 patent/WO2012095053A2/zh active Application Filing
- 2012-03-01 CN CN201280000571.4A patent/CN103053146B/zh active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101101563A (zh) * | 2007-07-23 | 2008-01-09 | 清华大学 | 基于海量数据分级存储系统的迁移管理方法 |
CN102147709A (zh) * | 2010-02-05 | 2011-08-10 | Lsi公司 | 基于服务质量的存储分层与迁移技术的系统和方法 |
CN102170396A (zh) * | 2011-05-06 | 2011-08-31 | 浙江大学 | 一种基于区分服务的云存储系统QoS控制方法 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN109189756A (zh) * | 2018-06-29 | 2019-01-11 | 平安科技(深圳)有限公司 | 电子装置、数据迁移的方法及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
WO2012095053A3 (zh) | 2013-01-31 |
CN103053146B (zh) | 2014-06-25 |
CN103053146A (zh) | 2013-04-17 |
WO2012095053A9 (zh) | 2013-03-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2012095053A2 (zh) | 数据迁移方法和设备 | |
US11799793B2 (en) | Adaptive private network with dynamic conduit process | |
US11405309B2 (en) | Systems and methods for selecting communication paths for applications sensitive to bursty packet drops | |
US8745204B2 (en) | Minimizing latency in live virtual server migration | |
JP5519859B2 (ja) | 管理通信の改善 | |
EP2690552B1 (en) | Method and device for migrating virtual machine parameters and virtual machine server | |
WO2016015582A1 (zh) | 传输报文的方法、装置和系统 | |
WO2011100900A2 (zh) | 资源动态调整方法和调度设备 | |
US11144423B2 (en) | Dynamic management of monitoring tasks in a cloud environment | |
WO2013163865A1 (zh) | 虚拟机热迁移和部署的方法、服务器及集群系统 | |
US20210258117A1 (en) | Agile Transport for Background Traffic in Cellular Networks | |
Zhang et al. | Tuning the aggressive TCP behavior for highly concurrent HTTP connections in intra-datacenter | |
Hwang et al. | Deadline and incast aware TCP for cloud data center networks | |
JP2022532731A (ja) | スライスベースネットワークにおける輻輳回避 | |
WO2015149491A1 (zh) | 一种网络资源的处理装置、方法和系统 | |
EP2700195A1 (en) | Technique for controlling and handling probe tunnel set up | |
WO2017185992A1 (zh) | 一种请求消息传输方法及装置 | |
JP2013048320A (ja) | 送信レート制御のためのプログラム、制御方法及び情報処理装置 | |
JP2011203810A (ja) | サーバ、計算機システム及び仮想計算機管理方法 | |
Xing et al. | A highly scalable bandwidth estimation of commercial hotspot access points | |
Guo et al. | IEEE SA Industry Connections-IEEE 802 Nendica Report: Intelligent Lossless Data Center Networks | |
JP5575953B1 (ja) | 情報システム間サービス提供装置、情報システム間サービス提供方法および情報システム間サービス提供プログラム | |
US20150372895A1 (en) | Proactive Change of Communication Models | |
US10103950B2 (en) | Hub filtering | |
JP6744260B2 (ja) | 仮想サーバ構成変更方法および仮想サーバ構成変更システム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201280000571.4 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12734514 Country of ref document: EP Kind code of ref document: A2 |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12734514 Country of ref document: EP Kind code of ref document: A2 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 12734514 Country of ref document: EP Kind code of ref document: A2 |