Client and a server and methods thereof for data management relating to shared data storage
First Claim
1. A method in a client for seamlessly migrating a shared data storage from a first node to a second node, where the shared data storage is accessible to clients accessing the shared data storage during and after the migration, wherein the client comprises a first replica of the shared data storage associated with the first node to be used for operations on the shared data storage, the method comprising:
- configuring, by a migration manager in the client, a second replica of the shared data storage associated with the second node;
configuring, by the migration manager in the client, the first and the second replicas to be used for operations simultaneously during the migration from the first node and the second node;
configuring, by the migration manager in the client, a virtual replica encapsulating the first and second replicas internally to provide a single interface towards applications operating on the shared data storage;
receiving information, at the migration manager in the client, that the shared data storage associated with the first node is synchronized with the shared data storage associated with the second node, wherein the synchronization comprises applying operations performed on the first and second replicas to the shared data storage associated with the first node and the shared data storage associated with the second node; and
based on the received information, configuring, by the migration manager in the client, the first and the second replicas to only use the second replica for operations on the shared data storage.
1 Assignment
0 Petitions
Accused Products
Abstract
A distributed shared data storage such as the distributed shared memory exemplified with the DSM Master can seamlessly migrate (i.e. move) in the runtime between different nodes without affecting the user perceived performance according to embodiments of the present invention. This is achieved by using more than one replica simultaneously operating towards different master databases during the migration. That is, all distributed shared memory replicas can automatically and seamlessly be migrated to another master database, thus making the communication more flexible and efficient.
-
Citations
26 Claims
-
1. A method in a client for seamlessly migrating a shared data storage from a first node to a second node, where the shared data storage is accessible to clients accessing the shared data storage during and after the migration, wherein the client comprises a first replica of the shared data storage associated with the first node to be used for operations on the shared data storage, the method comprising:
-
configuring, by a migration manager in the client, a second replica of the shared data storage associated with the second node; configuring, by the migration manager in the client, the first and the second replicas to be used for operations simultaneously during the migration from the first node and the second node; configuring, by the migration manager in the client, a virtual replica encapsulating the first and second replicas internally to provide a single interface towards applications operating on the shared data storage; receiving information, at the migration manager in the client, that the shared data storage associated with the first node is synchronized with the shared data storage associated with the second node, wherein the synchronization comprises applying operations performed on the first and second replicas to the shared data storage associated with the first node and the shared data storage associated with the second node; and based on the received information, configuring, by the migration manager in the client, the first and the second replicas to only use the second replica for operations on the shared data storage. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A method in a second node for seamlessly migrating a shared data storage from a first node to the second node, where the shared data storage is accessible to clients during and after the migration, the method comprises:
-
configuring, by a migration manager in the second node, a first proxy replica of the shared data storage associated with the first node; configuring, by the migration manager in the second node, a second proxy replica of the shared data storage associated with the second node; wherein a virtual replica is configured in a client that encapsulates the first and second proxy replicas internally to provide a single interface towards applications that operates on the shared data storage; configuring, by the migration manager in the second node, a synchronization of the first and the second proxy replicas; wherein the synchronization is performed by copying data from one of the first and second proxy replicas to other of the first and second proxy replicas upon receiving an update by the one of the first and second proxy replicas regarding an operation performed by the client or the other of the first and second proxy replicas; and updating a lookup table replica maintained, by the migration manager in the second node, with information that the shared data storage associated with the second node can be used in addition to the shared data storage associated with the first node, wherein the lookup table replica is associated with a lookup table master which in turn is associated with lookup table replicas of other nodes and clients. - View Dependent Claims (9, 10, 11, 12, 13)
-
-
14. A client of an end user device which includes a processor and a memory for seamlessly migrating a shared data storage from a first node to a second node, where the shared data storage is accessible to clients accessing the shared data storage during and after the migration, wherein the client comprises:
-
a first replica of the shared data storage associated with the first node to be used for operations on the shared data storage; and a migration manager that; configures a second replica of the shared data storage associated with the second node; configures the first and the second replicas to be used for operations simultaneously during the migration from the first node and the second node; configures a virtual replica encapsulating the first and second replicas internally to provide a single interface towards applications operating on the shared data storage; and based on receiving information that the shared data storage associated with the first node is synchronized with the shared data storage associated with the second node, wherein the synchronization comprises applying operations performed on the first and second replicas to the shared data storage associated with the first node and the shared data storage associated with the second node, configures the first and the second replicas to only use the second replica for operations on the shared data storage. - View Dependent Claims (15, 16, 17, 18, 19, 20)
-
-
21. A second node for seamlessly migrating a shared data storage from a first node to the second node wherein the first node and the second node each include a processor and a memory, where the shared data storage is accessible to clients during and after the migration, wherein the second node comprises a migration manager that configures:
-
a first proxy replica of the shared data storage associated with the first node, a second proxy replica of the shared data storage associated with the second node, wherein a virtual replica is configured in a client that encapsulates the first and second proxy replicas internally to provide a single interface towards applications that operates on the shared data storage, a synchronization of the first and the second proxy replicas, wherein the synchronization is performed by copying data from one of the first and second proxy replicas to other of the first and second proxy replicas upon receiving an update by the one of the first and second proxy replicas regarding an operation performed by the client or the other of the first and second proxy replicas, and updates a lookup table replica maintained by the migration manager with information that the shared data storage associated with the second node can be used in addition to the shared data storage associated with the first node, wherein the lookup table replica is configured to be associated with a lookup table master which in turn is configured to be associated with lookup table replicas of other nodes and clients. - View Dependent Claims (22, 23, 24, 25, 26)
-
Specification