THIN IMPORT FOR A DATA STORAGE SYSTEM

Abstract

The present disclosure relates to systems and methods for migrating data from one data storage system to another data storage system. A method can include copying data from one data storage system to another data storage system wherein data stored in data address locations of the first data storage system containing a NULL or zero is excluded from being written to the second data storage system.

Description

FIELD OF THE INVENTION

The present invention generally relates to importing data to a disk drive or data storage system, and more particularly to systems and methods for thin import of data to a disk drive or data storage system.

BACKGROUND OF THE INVENTION

Oftentimes, a need or desire may arise to transfer data from one disk drive or data storage system to another disk drive or data storage system. In prior data migration methods, along with address locations having meaningful data, empty address locations are transferred to the latter disk drive or data storage system taking up what can often be valuable storage space.

Thus, there exists a need in the art for systems and methods for thin import of data to a disk drive or data storage system, wherein during data migration, data address locations having a NULL or zero may not be imported to, or otherwise copied to, the receiving data storage system.

BRIEF SUMMARY OF THE INVENTION

The present disclosure, in one embodiment, relates to a method for migrating data from one data storage system to another data storage system. The method may include copying data from one data storage system to another data storage system wherein data stored in data address locations of the first data storage system containing a NULL or zero is excluded from being written to the second data storage system.

The present disclosure, in another embodiment, relates to a software program for migrating data from a first data storage system to a second data storage system. The software program may include code for migrating data stored on a data address location on the first data storage system to a data address location on the second data storage system based on a determination of whether the data stored at the data address location on the first data storage system indicates that data address location is empty.

While multiple embodiments are disclosed, still other embodiments of the present invention will become apparent to those skilled in the art from the following detailed description, which shows and describes illustrative embodiments of the invention. As will be realized, the invention is capable of modifications in various obvious aspects, all without departing from the spirit and scope of the present invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

While the specification concludes with claims particularly pointing out and distinctly claiming the subject matter that is regarded as forming the present invention, it is believed that the invention will be better understood from the following description taken in conjunction with the accompanying Figures, in which:

FIG. 1 is a schematic of an environment for thin import according to one embodiment of the present disclosure.

FIG. 2 is flow diagram of a method for thin import according to one embodiment of the present disclosure.

DETAILED DESCRIPTION

The present disclosure relates to novel and advantageous systems and methods importing data to a disk drive or data storage system, and more particularly to novel and advantageous systems and methods for thin import of data to a disk drive or data storage system. Generally, the present disclosure relates to various embodiments of systems and methods for importing data to a disk drive or data storage system wherein data stored on the exporting disk drive or data storage system may be efficiently imported to a receiving disk drive or data storage system. Rather than merely copying all data locations from the exporting disk drive or data storage system, the present disclosure relates to systems and methods wherein data addresses containing NULL or zeros (0) may not be imported to the receiving disk drive or data storage systems. This may be referred to herein as “thin import;” although the term “thin import” is not meant to be limiting in any manner.

A disk drive or data storage system may hereinafter be referred to as a “data storage system.” A data storage system can include a single disk drive or a plurality of disk drives. A data storage system can include a RAID subsystem, for example but not limited to, having a combination of at least one of RAID types, such as RAID-0, RAID-1, RAID-5, and RAID-10. It will be appreciated that other RAID types can be used in alternative RAID subsystems, such as RAID-3, RAID-4, RAID-6, and RAID-7, etc. A data storage system may be similar to the systems (and employ the methods) disclosed and claimed in U.S. Pat. No. 7,398,418, U.S. Patent 7,404,102, U.S. patent application Ser. No. 10/918,329, U.S. patent application Ser. No. 11/689,847, and U.S. patent application Ser. No. 11/689,899, each of which is hereby incorporated herein by reference in its entirety.

FIG. 1 illustrates one embodiment of an environment for thin import 100. The environment 100 may include an exporting or first data storage system 110 and an importing, receiving, or second data storage system 120. The exporting data storage system 110 may include one or more data stores 130, such as but not limited to disk drives for storing data. In some embodiments, the exporting data storage system 110 may include a RAID subsystem. A server or data manager/controller 140 may manage the data stored on data stores 130. The data manager 140 may manage the data stored on data stores 130 by, for example but not limited to, controlling access to the data, managing reads from and writes to the data stores, reorganizing the data stored on the data stores, etc. The importing data storage system 120 may also include one or more data stores 150, such as but not limited to disk drives for storing data. In some embodiments, the exporting data storage system 120 may include a RAID subsystem. A server or data manager/controller 160 may manage the data stored on data stores 150. The data manager 160 may manage the data stored on data stores 150 by, for example but not limited to, controlling access to the data, managing reads from and writes to the data stores, reorganizing the data stored on the data stores, etc. In further embodiments, the importing data storage system 120 may be similar to the systems (and employ the methods) disclosed and claimed in U.S. Pat. No. 7,398,418, U.S. Pat. No. 7,404,102, U.S. patent application Ser. No. 10/918,329, U.S. patent application Ser. No. 11/689,847, and U.S. patent application Ser. No. 11/689,899, each of which was previously incorporated herein by reference. In other embodiments, the exporting data storage system 110, importing storage system 120, and/or both systems 110, 120 may be similar to the systems (and employ the methods) disclosed and claimed in U.S. Pat. No. 7,398,418, U.S. Pat. No. 7,404,102, U.S. patent application Ser. No. 10/918,329, U.S. patent application Ser. No. 11/689,847, and U.S. patent application Ser. No. 11/689,899.

In one embodiment, the exporting data storage system 110 may be communicatively connected to the importing data storage system 120 directly or over a network, such as a LAN, WAN, such as the Internet, etc. In one embodiment, the exporting data storage system 110 may be communicatively connected to the importing data storage system 120 through a switch 170 or other similar device or network node. The switch 170 may direct and/or control the flow of data from the exporting data storage system 110 to the importing data storage system 120.

The environment 100 shown in FIG. 1 is illustrative only, and it is recognized that an environment for thin import 100 according to the present disclosure may include any number of exporting data storage systems and/or importing data storage systems. Each of the data storage systems may be communicatively connected directly or over a network, such as a LAN, WAN, such as the Internet, etc., as described above.

Generally, data may be imported from the exporting data storage system 110 to the importing data storage system 120 so that the importing data storage system 120 can be used as a new or additional data storage system for managing the respective data. In some embodiments, the importing data storage system 120 may become the new and sole system, an additional system, a primary data system, a back-up or secondary system, etc. In one embodiment, the environment 100 illustrated in FIG. 1 may be used to migrate data from the exporting data storage system 110 to the importing data storage system 120.

Oftentimes, empty data address locations of the data stores 130 of the exporting data storage system 110 may be indicated by storing a NULL or zero (0) in each of those data address locations. According to one embodiment of the present disclosure, during data migration from the exporting data storage system 110 to the importing data storage system 120, data address locations having a NULL or zero (0) may not be imported to, or otherwise copied to, the data stores 150 of the importing data storage system 120.

As stated above, systems and methods for thin import may be used to migrate data from one data storage system to another. FIG. 2 illustrates one embodiment of a method for thin import 200 according to the present disclosure. In step 210, the migration of data from one data storage system to another may be initiated by communicatively connecting an exporting data storage system to an importing data storage system. As stated above, the exporting data storage system may be communicatively connected to the importing data storage system directly or over a network, such as a LAN, WAN, such as the Internet, etc. In step 220, data stored on the data stores of the exporting data storage system may begin to be transferred, or otherwise copied, to the data stores on the importing data storage system. In step 230, if it is determined that a data address location of the data stores of the exporting data storage system contains a NULL or zero (0), then in step 240, that address location may not be written to, or otherwise copied to, the data stores of the importing data storage system. The data in the address locations containing a NULL or zero (0) can be discarded, ignored, or the like. If, on the other hand, it is determined that a data address location of the data stores of the exporting data storage system does not contain a NULL or zero (0), then in step 250, the data may be written, or otherwise copied, to the data stores on the importing data storage system. In some embodiments, the software and/or hardware that can be used for determining whether a data address location of the data stores of the exporting data storage system contains a NULL or zero (0) in systems and methods for thin import according to the present disclosure may be located at the importing data storage system or operably connected to the importing data storage system. In a further embodiment, the importing data storage system may be similar to the systems (and employ the methods) disclosed and claimed in U.S. Pat. No. 7,398,418, U.S. Pat. No. 7,404,102, U.S. patent application Ser. No. 10/918,329, U.S. patent application Ser. No. 11/689,847, and U.S. patent application Ser. No. 11/689,899, and the data transferred, or otherwise copied, from the exporting data storage system may be stored in the data stores of the importing storage system according to the methods disclosed in the above-identified patents and patent applications, including the use of, among other things, data allocation, data progression, instant data fusion, and data instant replay.

Although the present invention has been described with reference to preferred embodiments, persons skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the invention.

Claims

1. A method for migrating data from a first data storage system to a second data storage system, comprising: copying data from the first data storage system to the second data storage system;wherein data stored in data address locations of the first data storage system containing a NULL or zero are excluded from being written to the second data storage system.

2. The method of claim 1, wherein either or both the first and second data storage systems comprise a RAID subsystem.

3. The method of claim 1, further comprising communicatively connecting the first and the second data storage systems over a network.

4. The method of claim 3, wherein the network comprises a LAN, WAN, Internet, or combination thereof.

5. The method of claim 3, wherein the communicative connection over the network further comprises a switch or a network node configured to direct or control data flow from the first data storage system to the second data storage system.

6. The method of claim 1, wherein the first data storage system is a primary data storage system and the second data storage system is a back-up or secondary data storage system.

7. The method of claim 1, wherein determining if a data address contains a NULL or zero is performed by software encoded on or operably connected to the second data storage system.

8. A system for migrating data, comprising: a first data storage system comprising a plurality of data address locations;a second data storage system comprising a plurality of data address locations; anda data manager operatively connected to both the first and second data storage systems configured to copy data from the first data storage system to the second data storage system, wherein data stored in data address locations of the first data storage system containing a NULL or zero are excluded from being written to the second data storage system.

9. The method of claim 8, wherein either or both the first and second data storage systems comprise a RAID subsystem.

10. The system of claim 8, wherein the first and the second data storage systems are communicatively connected over a network.

11. The system of claim 10, wherein the network comprises a LAN, WAN, Internet, or combination thereof.

12. The system of claim 10, further comprising a switch or a network node configured to direct or control data flow from the first data storage system to the second data storage system.

13. The system of claim 8, wherein the first data storage system is a primary data storage system and the second data storage system is a back-up or secondary data storage system.

14. The system of claim 8, wherein determining if a data address contains a NULL or zero is performed by software encoded on or operably connected to the data manager.

15. A computer software program stored on a computer-readable medium for copying data from a first data storage system to a second data storage system, the program comprising computer-implementable code for configured to: from a plurality of data address locations at the first data storage system, determine if any of the data address locations contain a NULL or zero;transmit from the first data storage system to the second data storage system data from the data address locations at the first data storage system which do not contain a NULL or zero and not transmit data from the data address locations at the first data storage system which contain a NULL or zero; andat the second data storage system, write the transmitted data to data address locations.

16. The computer software program of claim 15, wherein at least one of the first and second data storage systems comprises a RAID subsystem.