LIVE FILE SYSTEM MIGRATION

• US 20130054530A1
• Filed: 08/29/2011
• Published: 02/28/2013
• Est. Priority Date: 08/29/2011
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Brown, Richard S., Baker, William Eugene, Shivam, Piyush
• Granted Patent: US 8,484,161 B2
• Time in Patent Office: Days
• US Class Current: 707/639
• CPC Class Codes: G06F 16/119 Details of migration of file systems migration mechanisms in storage systems G06F3/0647

Abstract

In general, the invention relates to a method for migrating a source file system residing on a source server to a destination server. The method includes sending a first snapshot of the source file system from the source server to the destination server and creating, using the first snapshot, a migrated file system on the destination server. The method further includes sequentially sending, to the destination server, a set of snapshot deltas including modifications to the source file system, updating the migrated file system using the set of snapshot deltas, determining that a freeze threshold is exceeded, freezing the source file system, sending a final snapshot delta from the source server to the destination server, updating the migrated file system using the final snapshot delta, creating a file system husk referencing the migrated file system, and thawing the source file system and the migrated file system.

Claims

1. A method for migrating a source file system residing on a source server to a destination server, comprising:

sending a first snapshot of the source file system from the source server to the destination server;

creating, using the first snapshot, a migrated file system on the destination server;

sequentially sending, from the source server to the destination server, a plurality of snapshot deltas comprising modifications to the source file system;

updating the migrated file system using the plurality of snapshot deltas;

determining that a freeze threshold is exceeded based on a snapshot delta of the plurality of snapshot deltas;

in response to determining that the freeze threshold is exceeded;

freezing the source file system, wherein the source file system is active prior to freezing;

sending, after freezing the source file system, a final snapshot delta from the source server to the destination server;

updating the migrated file system using the final snapshot delta;

creating, in the source file system, a file system husk referencing the migrated file system; and

thawing the source file system and the migrated file system after updating the migrated file system.

2. The method of claim 1, wherein sequentially sending the plurality of snapshot deltas comprises:

identifying, after sending the first snapshot, a second snapshot of the source file system;

performing a comparison of the first snapshot with the second snapshot;

identifying, based on the comparison, a first snapshot delta of the plurality of snapshot deltas comprising a first plurality of differences between the first snapshot and the second snapshot; and

sending the first snapshot delta from the source server to the destination server, wherein updating the migrated file system using the plurality of snapshot deltas comprises updating, after sending the first snapshot delta, the migrated file system with the first snapshot delta.

3. The method of claim 1, wherein determining that the freeze threshold is exceeded comprises:

determining a transmission time period for sending the snapshot delta to the destination server; and

determining that a freeze threshold duration exceeds the transmission time period.

4. The method of claim 1, wherein determining that the freeze threshold is exceeded comprises:

identifying a size of the snapshot delta; and

determining that a freeze size threshold exceeds the size.

5. The method of claim 1, further comprising:

identifying a protocol state structure on the source server;

extracting a plurality of protocol state data from the protocol state structure;

encoding the plurality of protocol state data into an encoded protocol state structure;

sending the encoded protocol state structure to the destination server with the final snapshot delta;

extracting, by the destination server, the plurality of protocol state data by decoding the encoded protocol state structure; and

importing the plurality of protocol state data into a migrated protocol state structure on the destination server.

6. The method of claim 5, wherein the plurality of protocol state data comprises a plurality of client protocol data mapping a plurality of client computing devices to a plurality of files in the source file system, and wherein the plurality of client protocol data is obtained using an over-the-wire protocol

7. The method of claim 1, further comprising:

receiving, from a client application, a first request to modify the source file system, wherein the source file system is active while receiving the first request;

modifying the source file system in response to the first request;

receiving, after freezing the source file system and before thawing the source file system, a second request from the client application to modify the source file system; and

denying the second request.

8. The method of claim 1, further comprising:

receiving, by the file system husk, a request for data from a client computing device; and

sending a reference to the migrated file system to the client computing device, wherein the client computing device directs a plurality of future requests to the migrated file system in response to receiving the reference.

9. The method of claim 1, further comprising:

receiving, prior to sending the first snapshot, an instruction to migrate the source file system from the source server to the destination server.

10. The method of claim 1, further comprising:

identifying a plurality of file handles corresponding to files in the source file system; and

reconstructing the plurality of file handles in the migrated file system.

11. The method of claim 1, wherein freezing the source file system comprises allowing a plurality of in-flight operations to complete and declining a plurality of new operations.

12. The method of claim 1, wherein thawing the migrated file system comprises activating the migrated file system.

13. A non-transitory computer-readable medium storing a plurality of instructions for migrating a source file system residing on a source server to a destination server, the plurality of instructions comprising functionality to:

send a first snapshot of the source file system from the source server to the destination server;

create, using the first snapshot, a migrated file system on the destination server;

sequentially send, from the source server to the destination server, a plurality of snapshot deltas comprising modifications to the source file system;

update the migrated file system using the plurality of snapshot deltas;

determine that a freeze threshold is exceeded based on a snapshot delta of the plurality of snapshot deltas;

in response to determining that the freeze threshold is exceeded;

freeze the source file system, wherein the source file system is active prior to freezing;

send, after freezing the source file system, a final snapshot delta from the source server to the destination server;

update the migrated file system using the final snapshot delta;

create, in the source file system, a file system husk referencing the migrated file system; and

thaw the source file system and the migrated file system after updating the migrated file system.

14. The non-transitory computer-readable medium of claim 13, wherein sequentially sending the plurality of snapshot deltas comprises:

identifying, after sending the first snapshot, a second snapshot of the source file system;

performing a comparison of the first snapshot with the second snapshot;

identifying, based on the comparison, a first snapshot delta of the plurality of snapshot deltas comprising a first plurality of differences between the first snapshot and the second snapshot; and

sending the first snapshot delta from the source server to the destination server, wherein updating the migrated file system using the plurality of snapshot deltas comprises updating, after sending the first snapshot delta, the migrated file system with the first snapshot delta.

15. The non-transitory computer-readable medium of claim 13, wherein the plurality of instructions further comprise functionality to:

identify a plurality of file handles corresponding to files in the source file system; and

reconstruct the plurality of file handles in the migrated file system.

16. A system for migrating file systems, comprising:

a source server comprising a source file system;

a destination server; and

a migration manager configured to;

send a first snapshot of the source file system from the source server to the destination server;

create, using the first snapshot, a migrated file system on the destination server;

sequentially send, from the source server to the destination server, a plurality of snapshot deltas comprising modifications to the source file system;

update the migrated file system using the plurality of snapshot deltas;

determine that a freeze threshold is exceeded based on a snapshot delta of the plurality of snapshot deltas;

in response to determining that the freeze threshold is exceeded;

freeze the source file system, wherein the source file system is active prior to freezing;

send, after freezing the source file system, a final snapshot delta from the source server to the destination server;

update the migrated file system using the final snapshot delta;

create, in the source file system, a file system husk referencing the migrated file system; and

thaw the source file system and the migrated file system after updating the migrated file system.

17. The system of claim 16, further comprising:

a common service communicatively connected to the source server and the destination server and configured to;

assign, prior to creating the migrated file system, a unique file system identifier (FSID) to the source file system, wherein the unique FSID is stored as a persistent attribute within the source file system, and wherein a plurality of file handles from the source file system are maintained in the migrated file system.

18. The system of claim 16, wherein sequentially sending the plurality of snapshot deltas comprises:

identifying, after sending the first snapshot, a second snapshot of the source file system;

performing a comparison of the first snapshot with the second snapshot;

identifying, based on the comparison, a first snapshot delta of the plurality of snapshot deltas comprising a first plurality of differences between the first snapshot and the second snapshot; and

sending the first snapshot delta from the source server to the destination server, wherein updating the migrated file system using the plurality of snapshot deltas comprises updating, after sending the first snapshot delta, the migrated file system with the first snapshot delta.

19. The system of claim 16, wherein the migration manager is further configured to:

identify a plurality of file handles corresponding to files in the source file system; and

reconstruct the plurality of file handles in the migrated file system.

20. The system of claim 16, wherein the migration manager is further configured to:

identify a protocol state structure on the source server;

extract a plurality of protocol state data from the protocol state structure;

encode the plurality of protocol state data into an encoded protocol state structure;

send the encoded protocol state structure to the destination server with the final snapshot delta;

extract, by the destination server, the plurality of protocol state data by decoding the encoded protocol state structure; and

import the plurality of protocol state data into a migrated protocol state structure on the destination server.