Real time data migration system and method employing sparse files

• US 5,564,037 A
• Filed: 03/29/1995
• Issued: 10/08/1996
• Est. Priority Date: 03/29/1995
• Status: Expired due to Term

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Cheyenne Software International Sales Corporation
• Inventors: Lam, Wai T.
• Primary Examiner(s): Kulik, Paul V.
• Application Number:
  US08/413,056
• Time in Patent Office: 559 Days
• Field of Search: 395/488, 395/600
• US Class Current: 711/161
• CPC Class Codes: G06F 12/08 in hierarchically structured memory systems, e.g. virtual memory systems
• CPC Class Codes: G06F 16/185 Hierarchical storage management [HSM] systems, e.g. file migration or policies thereof details of archiving G06F16/11
• CPC Class Codes: G06F 3/0608 Saving storage space on storage systems
• CPC Class Codes: G06F 3/0647 Migration mechanisms
• CPC Class Codes: G06F 3/0685 Hybrid storage combining heterogeneous device types, e.g. hierarchical storage, hybrid arrays
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

A system and method for real time data migration in a networked computer system uses a known operating system feature, a sparse file, to represent a migrated file. The sparse file consumes a minimum amount of physical space on the file server but is defined as having the same size and attributes as the original final. When a user accesses a migrated file, the file appears to be resident on the file server and is automatically and transparently returned to the file server from an optimized storage location in a hierarchical storage management system.

Claims

1. A method for migrating a data file in a networked computer system from a primary storage device to a secondary storage device, the data file having a first actual size, comprising the steps of:

transmitting the contents of the data file to the secondary storage device;

truncating the data file; and

generating a sparse file in the primary storage device having an apparent size equal to the first actual size and a second actual size less than the first actual size.

2. The method according to claim 1, further comprising the step of migrating the data from the secondary storage device to a tertiary storage device as a function of a predetermined storage hierarchy scheme.

3. The method according to claim 1, wherein the networked computer system includes a Novell®

NetWare®

version 3.x operating system.

4. The method according to claim 1, further comprising the step of:

storing a migration key in the sparse file.

5. The method according to claim 1, wherein the step of generating the sparse file further includes the steps of:

performing an open operation on the data file;

performing a first write operation on the data file;

performing a seek operation on the data file;

performing a second write operation on the data file; and

performing a close operation on the data file.

6. The method according to claim 5, wherein the seek operation seeks to the first actual size.

7. The method according to claim 5, wherein the first write operation writes a migration key into the data file.

8. The method according to claim 1, wherein the step of generating the sparse file further includes the steps of:

performing an open operation on the data file;

performing a first write operation on the data file;

performing a change size operation on the data file; and

performing a close operation on the data file.

9. The method according to claim 8, wherein the change size operation changes size to the first actual size.

10. A system for migrating a data file in a networked computer system from a primary storage device, the data file having a first actual size, comprising:

a migration engine coupled to the primary storage device; and

a secondary storage device coupled to the migration engine;

wherein the migration engine reads the data file, transmits the contents of the data file to the secondary storage device, and generates a sparse file in the primary storage device having an apparent size equal to the first actual size and having a second actual size less than the first actual size.

11. The system according to claim 10, further comprising a tertiary storage device coupled to the secondary storage device for receiving a further migration of the data file as a function of a predetermined storage hierarchy scheme.

12. The system according to claim 10, wherein the migration engine stores a migration key in the sparse file.

13. The system according to claim 10, wherein the networked computer system includes a Novell®

NetWare®

version 3.x operating system.