• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    According to one embodiment, the invention relates to a method of migrating data from a source storage system to a destination storage system comprising the following steps. In a first step, an initial copy (301) is performed. In a second step, one or more incremental copies (302-306) are output and then a final incremental transition copy (311) is output. Executing the one or more incremental copies (302-306) further includes excluding from a respective incremental copy of the one or more incremental copies first parts of data of the data that are likely to change prior to executing a final incremental transition copy (311).
    公开号:BE1022200B1
    申请号:E2014/0777
    申请日:2014-10-14
    公开日:2016-02-29
    发明作者:Ives Aerts；Kim Marivoet
    申请人:Datadobi Cvba；
    IPC主号:
    专利说明:

    DATA MIGRATION TOOL WITH INCREMENTAL INTERMEDIARIES Field of the Invention [01] In general, the invention relates to the field of data migration tools. Such tools are helpful in the automated migration of digital data from a source storage system to a destination storage system.
    More specifically, the invention relates to the migration of huge amounts of data, wherein a single copy of all data on the source storage system to the destination storage system can last on the order of days, weeks or even months.
    Background of the Invention The need for data storage capacity is increasing rapidly every year. Today, a company's storage system can be distributed across different locations and include multiple server racks in one or more data centers, with each rack accommodating multiple storage servers. Some companies place their storage needs with external storage providers, who offer cloud-based storage solutions.
    [04] At a given moment, a user of a storage system can decide to migrate his data from his current storage system to a new one. This decision can be driven by various factors. A first factor can be financial considerations, whereby the provider of the new storage system offers the same or more capacity for a better price. Another factor may be that the capacity of the current storage system cannot be further increased and a migration to a new and larger storage system is inevitable.
    [05] In all of these cases, a data migration must be performed, i.e. all data on the source system must be copied to the destination system and at a given moment users must be switched to the new destination system. During the actual transition, users are typically denied access to both storage systems to ensure data integrity. As a result, users cannot write to data being copied, which could cause data corruption, or users cannot write to a data location that has already passed the migration, which could cause data loss.
    [06] For large storage systems that can handle dozens of Terabytes up to several Petabytes of data, a single copy of all data in the order of days, weeks or even months may be required. Denying a user access to the storage system for such a long time is simply unacceptable and so there is a need for solutions to shorten the transition time.
    WO12149220A discloses the concept of incremental copies to shorten the actual transition time. First, a starting or basic copy is made of all data that must be migrated from the source to the destination system. One or more incremental copies are then made prior to the actual transition. An incremental copy only considers the difference between the source and destination system. This therefore supplies all changes to users who are still using the source storage system. During the initial and incremental copies, users are still allowed to access their data on the source storage system. The actual transition is then carried out at a scheduled time. During the transition, users are denied all access to storage systems and a final or incremental transition copy is made. When the transition is complete, the users are switched to the new destination storage system and the users can regain access to their data.
    [08] Although the above concept greatly reduces the actual transition time, it is still a goal to further shorten the transition time.
    Summary of the Invention This object is achieved by a computer-implemented method for migrating data from a source storage system to a destination storage system, comprising the step of performing an initial copy, then performing one or more incremental copies, and the then perform a final incremental transition copy. This performing one or more incremental copies includes excluding first data portions of data from a respective incremental copy of the one or more incremental copies, which are likely to change prior to performing this final incremental copy.
    [10] After the initial copy or basic copy of all data being migrated, one or more incremental copies are made. In an incremental copy, the differences in data between the source storage system and the destination storage system are supplied to the destination storage system. An incremental copy may include copying a data portion from the source to the destination, deleting a data portion in the destination, or updating a data portion in the destination. The data comprises a plurality of data parts, defined as data units, which are copied from the source system to the destination system. In typical data storage systems, such a data portion is a file that is hierarchically structured in a file system, and the data is thus copied in a file-by-file manner. At the end, the actual transition is performed and a final incremental copy, which is referred to as the final incremental transition copy, is made. After a successful transition, users can start using the destination storage system. During the transition, users were denied access to both storage systems to ensure data integrity.
    [H] When a certain incremental copy is made or prepared, it is checked whether it is likely that a data part will still change before transition, and if this is the case, this part is excluded from the incremental copy. If it is likely that a data part will change in the future prior to the transition, it will end up in a future incremental copy or in the transition copy anyway and therefore it does not have to be already included in the current incremental copy. When data is excluded from an incremental copy, the copy is also referred to as an incremental partial copy.
    [12] By excluding data parts from the incremental copies that will in any event be included in the final transition copy, the incremental copies are smaller in size and can therefore be executed in a shorter period of time. When an incremental copy is smaller, fewer changes will be made by the users until the next incremental copy and also until the final transition copy. In this way the final transition copy is smaller and therefore the execution takes less time. It is therefore an advantage that the transition time during which users could not have access to the storage system is shortened.
    [13] It is a further advantage that less data is copied from the source system to the destination system, saving bandwidth.
    [14] Performing an initial copy may further include excluding second data portions from the initial copy, which are likely to change prior to performing the final incremental transition copy.
    [15] The same principle of excluding data sharing is therefore applied to the full initial copy, thereby reducing the size and duration of this first copy.
    [16] The final incremental transition copy is advantageously performed when a transfer size of the one or more incremental copies has reached an equilibrium state.
    [17] The incremental copies will typically decrease in transfer size and transfer time, until they reach a certain equilibrium state in transfer size, i.e. up to a time when the transfer size and / or time of subsequent incremental copies are substantially the same. At the time of the first initial copy, there is no data in the destination storage system. The transfer size of this first initial copy can therefore be very large, which requires days to months for large storage systems to execute. The transfer size of an incremental copy depends on the length of time since the previous copy. Since the transfer time of the initial copy is so large, the first incremental copy will still be considerably large. Each subsequent incremental copy will then decrease in size until a certain equilibrium state in transfer size and time is reached.
    [18] By carrying out the transition after this equilibrium state has been reached, the transition time is further reduced.
    [19] According to an embodiment, excluding first and / or second data portions includes retrieving metadata associated with data portions of the data on the source storage system, the metadata indicating an likelihood that a respective data portion will change prior to the final incremental transition copy. The exclusion further comprises selecting the first and / or second data parts based on this metadata.
    [20] Metadata is available information about the data parts that provide an indication of whether it is likely that the data part will change before the transition.
    [21] A first type of metadata can be obtained from the source storage system itself. An example of this first type is the type of a respective data part or a file type, if the data part corresponds to a file. A predetermined list of file types can then be used to decide whether it is likely that a data part will change. For example, .pst files, which are typically used to store an e-mail data file, can be excluded from the incremental copies.
    [22] A second example of the first type of metadata is a change overview of a data part or file. Files, which are often changed or still changed after a certain predetermined time, can then be excluded from the incremental copies.
    [23] A third example is a folder path of the data part. It can then be decided in advance that files in a particular folder location should be excluded from the incremental copies.
    [24] A fourth example is the read and write privileges of a data part. Read-only data parts can always be included in the incremental copies.
    [25] Another example is file ownership, where files belonging to certain users are excluded from or included in the incremental copies, because certain users, being actual persons or system processes, may be more active than others.
    [26] According to a further embodiment, the method further comprises performing an incremental intermediate copy, which excludes no data parts, and using a duration of this incremental intermediate copy as an estimate for a duration of the final incremental transition copy.
    [27] The transition itself is a crucial moment in the migration procedure. For large organizations this can be planned months in advance. Transitions are typically planned on weekends to minimize the impact on the productivity of the organization. To ensure and plan the completion of the transition, it is important to know how long the final incremental transition copy will last. Since the incremental partial copies are taken prior to excluding some of the data parts, they are not a good indication of the transition period. Therefore, an incremental intermediate copy is performed without excluding data parts, the duration of which provides a good estimate of the duration of the transition copy.
    [28] Advantageously, the execution of an incremental intermediate copy is performed on the same day of the week on which the execution of the final incremental transition copy is scheduled.
    [291 More advantageously, the execution of an incremental intermediate copy is performed at the same hour of the day that the execution of the final incremental transition copy is scheduled.
    [30] The duration of an incremental copy can depend on the time that it is executed. As a result, planning for it on the same day and / or the same hour as the final transition results in a better estimate.
    [31] This execution of an incremental intermediate copy can then be performed when a transfer size of the one or more incremental copies has reached an equilibrium state.
    [32] When the final transition copy is executed after an equilibrium state of the incremental copies has been reached, a good estimate by the intermediate copy is ensured by also performing the incremental intermediate copy when an equilibrium state in transfer amount of the incremental copies that were previously has been achieved.
    [33] According to a particular embodiment, performing an initial copy and / or performing one or more incremental copies and / or performing a final incremental transition copy and / or performing an incremental intermediate copy: scanning all or one part of the data to be migrated on the source storage system and / or scanning all or part of the already copied data on the destination storage system and creating a list of commands for executing the execution. Then executing the list of commands.
    [34] First, a list of all commands for executing the copies is created and then the commands are executed. Since the list of commands is known prior to actual execution, the progress of the current copy is known when it is executed, since the progress of the copy can be deduced from the current position in the list of commands.
    According to a second aspect, the invention relates to a computer program product, which includes executable instructions on a computer for performing the method of the first aspect when the program runs on a computer.
    According to a third aspect, the invention relates to a computer-readable storage medium, which comprises the computer program product according to the second aspect.
    According to a fourth aspect, the invention relates to a data processing system programmed to perform the method according to the first aspect.
    BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 shows an example of the transfer time and transfer size of data copies from a source storage system to a destination storage system according to an embodiment; and [39] FIG. 2 shows an example of a source and destination storage system; and [40] FIG. 3 shows an example of the transfer time and transfer size of data copies from a source storage system to a destination storage system according to an embodiment; and [41] FIG. 4 shows steps of a method for performing a data migration from a source to a destination storage system according to an embodiment; and [42] FIG. 5 shows steps of a method for performing a data migration from a source to a destination storage system according to an embodiment; and [43] FIG. 6 shows steps of a method for outputting a copy of data from a source to a destination storage system according to an embodiment; and [44] FIG. 7 shows steps of a method for generating a list of commands for executing a copy of data from a source to a destination storage system according to an embodiment; and [45] FIG. 8 shows an exemplary embodiment of a device for performing a data migration.
    DETAILED DESCRIPTION OF EMBODIMENTS [46] The present disclosure relates to data migration between data storage systems and more particularly to data migration from a source storage system to a destination storage system. FIG. 2 shows an exemplary embodiment of such source 200 and destination 220 storage systems. The source storage system comprises a plurality of storage servers 203, each housing one or more digital storage means 202. Similarly, the destination system comprises a plurality of storage servers 223, each housing one or more digital storage means 222. The storage servers 203 and 223 may be housed in the same or a different data center within or outside a company's data network. The storage systems 200 and 220 can provide data storage and access to users and services. Such access can be established via the network 230. Different protocols can be used to gain access to data, such as, for example, CIFS, SMB, FTP or NFS. Company-level storage systems can offer huge data storage capacity and are often used and maintained by external storage providers such as NetApp, EMC or Hitachi.
    [47] The data to be migrated from the system 200 to the system 220 typically comprises a series of data portions, which in the most common case will be files organized according to a file system. These files can be data files belonging to users or groups, system files used by an operating system, or application files used by and for applications.
    In the embodiments below, different steps for performing a data migration from a source system 200 to a destination system 220 are provided. When data is referenced, this is not necessarily a reference to all data on the storage system. The data can first be split into different blocks of data and a data migration can then be performed for each block of data, as disclosed by the embodiments below. Such a block can for instance comprise all data that belong to a specific department of an organization or to a specific subfolder or confirmation point of a file system.
    FIG. 4 shows steps for performing a data migration according to an embodiment of the invention. The steps are further represented by FIG. 3 showing the transfer size and transfer time of copies 301-311 from the source storage system 200 to the destination storage system 220.
    [50] At a given moment a data migration is started. Data storage is still provided by the source data storage system prior to and during migration. During migration, the destination storage system is filled with copies of the data. At the end of the migration, during the transition or transition, users are denied access to both source and destination storage systems and the last bits of data are copied to the destination storage system. All users are then granted access to their data on the destination storage, while the source storage system can be taken out of operation. Due to the transition, where access was denied, data integrity is guaranteed.
    [51] In a first step 431, an initial copy of the data is performed. In FIG. 3, this initial copy is represented by the block 301, the width thereof representing the time required to perform the initial copy, and the height thereof representing the data size of the transfer. For typical large data migrations, such an initial copy can take several days, weeks, or even months. In addition to the size of the data, the transfer time will also be limited by the available bandwidth for transferring the data between the source 200 and the destination 220.
    [52] According to an embodiment, the initial copy 301 comprises all data to be migrated. Thus, in the first step 431, all data portions that constitute the data are copied from the source storage system 200 to the destination storage system 220.
    [53] According to an alternative embodiment, data portions that are likely to change prior to transition are excluded from the initial copy 301. Since it is still likely that the data parts will change, a new copy will have to be made before or during the transition. By excluding such data parts from the initial copy, it will therefore take less time to perform the initial copy and network bandwidth will be saved.
    [54] After performing the initial copy in step 431, one or more incremental copies 302 to 306 are made until the start of the actual transition. During an incremental copy, only differences between the source and destination system 200 and 220 are supplied to or copied to the destination system 220. In FIG. 3, the first incremental copy is represented by block 302. If a data part on the source already has a copy at the destination, which was copied thereto during the initial copy 301, the data part is not copied during the incremental copy. Therefore, the incremental copy 302 will be smaller than the initial copy 301, since it is unlikely that all files on the source storage system will have changed. In addition, data portions that are likely to change prior to the transition are excluded from the incremental copy 302. Since it is still likely that the data parts will change, a new copy will have to be made before or during the transition. By excluding such data parts from the incremental copy, the incremental copy will take less time to execute and network bandwidth is saved. An incremental copy excluding certain data parts is also referred to in the present description as an incremental partial copy.
    The step 432 of performing the incremental copies can be repeated several times until the transition. During a subsequent incremental copy, data parts that were previously excluded can now be copied or excluded again. Depending on the criteria used, a data part that was previously classified as "likely to change" could be re-evaluated as "not likely to change" during a subsequent iteration. Step 432 is preferably repeated at least until the transfer size of the incremental copies has reached an equilibrium state. In FIG. 3, the incremental copies 304, 305 and 306 have reached an equilibrium state with respect to their transfer size. This effect is caused by the transfer size of an incremental copy being dependent on the transfer time of the previous copy. Incremental copy 304 is thus dependent on the transfer time of the copy 303, 303 is dependent on 302 and 302 is in turn dependent on the transfer time of the initial copy. Since the transfer time of the initial copy was large, it takes a few iterations before the incremental copies 302-306 have reached an equilibrium state.
    [56] Next, in step 437, the actual transition copy is performed during the actual transition 322, preferably after an equilibrium state has been reached according to condition 433. During this transition 322, all access to the data is denied and a final incremental transition copy 311 is made. The final incremental transition copy is similar to the previous incremental partial copies except that no files are excluded. After the transition 322, users are again given access to the data, but now on the destination storage system 220.
    [57] Excluding files from the incremental copies reduces the transfer size and therefore also the transfer time of the incremental copies. Since the size of the final incremental transition copy depends on the previous incremental copy, the transfer time of the final copy will also be reduced.
    [58] Planning is crucial in data migration. A transition is typically made during a weekend when fewer users are affected by denial of access to data compared to workdays. To verify that the transition can be completed in a desired time window, a good estimate of the duration of the transition copy is important.
    FIG. 5 together with FIG. 1 uses an additional incremental intermediate copy 107 to estimate the duration 122 of the transition copy 111 according to an embodiment. The first step 531 is the same as step 431, in which a full or partial initial copy 101 is made. Next, in step 532, a first series of incremental partial copies 102 through 106 is made. When these copies have reached an equilibrium state 120 according to condition 533, in which their transfer amount is substantially the same as the transfer amount of the previous incremental partial copy, a test of the transition copy is performed in step 534. During this step, an incremental copy is made without data parts to simulate the final incremental transition copy. In other words, the transfer size and transfer time of this intermediate copy 107 are used to estimate the duration of the final transition copy 111. 538. This estimate can then be used to see if the transition can be performed as planned. If the estimated transition period is too long, more time can be allocated for the transition or a smaller data block can be defined for the migration.
    Preferably, the incremental intermediate copy 107 is performed on the same day and even more preferably at the same hour as the planned transition copy 111. This ensures that time-dependent factors, such as the available bandwidth for the data transfer, approach the transition as closely as possible. Advantageously, both during the intermediate copy 107 and the transition copy 111, only the data migration of a single data block is performed to ensure a short transfer time and a good estimate.
    [61] After the intermediate copy in step 534, one or more incremental partial copies 108-110 are again performed in step 535 until an equilibrium state 121 in the transfer amount of the incremental copies is reached, again according to the condition 536. Next, in step 537, the transition copy becomes 111 performed the same as step 437.
    FIG. 6 shows steps to perform a copy of data during a data migration from the source storage system 200 to the destination storage system 220 according to an embodiment. These steps can be performed to perform the initial or partial initial copy according to steps 431 and 531, to perform the incremental copy according to steps 432, 532 or 535, to perform the incremental intermediate copy for the test according to step 534 or to perform the final incremental transition copy in steps 437 and 537.
    [63] In step 641, the metadata is retrieved from the source storage system and scanned, and in step 642, the metadata is retrieved from the destination storage system and scanned. Next, in step 643, a list of commands is generated by comparing the scanned metadata. Such commands may include: - an instruction to copy a data portion from the source storage system to the destination storage system. - an instruction to delete a data part from the destination storage system. - an instruction to update the metadata of a certain data part on the destination storage system, such as, for example, user rights, property and author information.
    [64] Next, in the final step 644, the list of commands is executed to thereby output the actual copy of the data.
    [65] It is not always necessary to fully perform steps 641 and 642, i.e., it is not necessary to fully scan both source and destination storage systems. For example, a list of changes since the previous iteration can be obtained from the source system. In addition, the state of the destination storage system can be derived from one of its previous states or index and the result of the previous commands to calculate the new system state. If this information is available, the list of commands can be derived in step 643.
    FIG. 7 shows steps performed to generate 643 from the list of commands according to an embodiment for the case where data portions are to be excluded to perform an incremental partial copy. The steps shown are performed on the source storage system 200 for each data part. In the first step 751, it is checked whether there is a difference between the data part at the source and the destination based on the associated metadata scanned in steps 641 and 642. This check can include: - the data part is present at the source storage system, but not on the destination storage system. - the data part is present on the destination storage system, but not on the source storage system. - the data part is present on the destination storage system, but the metadata thereof, such as the file change overview, indicates that the data part on the source storage system has been changed. - the data part is present on the source and destination storage system and the content thereof is unchanged, but some of its metadata has changed. For example, a data file may be unchanged, but user rights may be different.
    [67] If a difference is detected, the method proceeds to the next step 752, otherwise neither the data part nor the metadata thereof is changed and no commands for the respective data part need to be generated. In this next step 752, it is checked whether the respective data part is likely to change before the transition. If it is likely that it will change and although there is a difference for this data part between the source and destination storage system, no further command is generated and this data part is removed from the copy.
    [68] There are various options for detecting this probability from the scanned metadata and these can be further combined. Some examples according to an embodiment are: the type of the data part, such as the file type, is checked on the basis of a predetermined list of types that are excluded from the copies. This list then includes file types, which typically contain data, that are likely to change a lot. Such file types can be, for example, mailbox file types, data file types, system files from an operating system, and cache files for storing temporary data. - the owner or group, to which a file belongs, is checked against a predetermined list of users and groups. - the change overview of a file is checked. If the file has been changed recently, for example after a certain date, the file is excluded from the copy. - it is checked whether the location of a file is in a collection of predetermined locations. Such a location can, for example, be a folder. In this way, locations in the directory system that are known to include files that change a lot can be excluded by default.
    [69] If it is determined in step 752 that it is likely that the respective data part will change, the method proceeds to step 753, in which a command is generated depending on the detected difference in step 751. Such a command may be, for example, : - copy the respective data part from the source to the destination storage system. - remove the respective data part from the destination storage system. - update the metadata of the data part at the destination with the metadata of the data part at the source.
    The steps of FIG. 7 are performed for all scanned data parts, both on the source and the destination storage system, resulting in the list of commands from step 643 in FIG. 6.
    FIG. 8 shows a suitable computer system 800 for performing the steps according to the method of the above embodiments. Computer system 800 can generally be designed as a suitable general-purpose computer and a bus 810, and processor 802, a local memory 804, one or more optional input interfaces 814, one or more output interfaces 816, a communication interface 812, a storage element interface 806 and one or more storage elements 808. Bus 810 can include one or more conductors that enable communication between the components of the computer system 800. Processor 802 can include any type of conventional processor or microprocessor that interprets and executes program instructions. Local memory 804 may include a Random Access Memory (RAM) or other type of dynamic storage device that stores information and instructions for execution by processor 802, and / or a Read-Only Memory (ROM) or other type of static storage device. device that stores static information and instructions for use by processor 802. Input interface 814 may include one or more conventional mechanisms that allow an operator to enter information into computer device 800, such as a keyboard 820, a mouse 830, a pen, voice recognition and / or biometric mechanisms, etc. Output interface 816 may include one or more conventional mechanisms that provide information to the operator, such as a display 840, a printer 850, a speaker, etc. Communication interface 812 may include a transceiver-like mechanism, such as, for example, one or more Ethernet interfaces that enable computer system 800 to communicate with other devices and / or systems, e.g., mechanisms for communicating with source and destination storage systems 200 and 220 of FIG. 2. The communication interface 812 of computer system 800 can be connected to such another computer system by means of a Local Area Network (LAN) or a Wide Area Network (WAN), such as, for example, the internet. Storage element interface 806 may include a storage interface, such as, for example, a Serial Advanced Technology
    Attachment (SATA) interface or a Small Computer System Interface (SCSI), for connecting bus 810 to one or more storage elements 808, such as one or more local disks, for example SATA disk drives, and reading and writing data to and / or control 808 of these storage elements. Although the storage elements 808 have been described above as a local disk, in general any other suitable computer-readable medium, such as a removable magnetic disk, optical storage media, such as a CD or DVD, ROM disk; solid-state drives, flash memory cards, can be used. The system 800 described above can also work as a Virtual Machine above the physical hardware.
    The steps shown by the above embodiments may be implemented as program instructions stored in local memory 804 of the computer system 800 for execution by the processor 802 thereof. Alternatively, the instruction may be stored on the storage element 808 or accessible from another computer system via the communication interface 812.
    The system 800 can be connected to the network 230 of FIG. 2 are connected via its communication interface 812. In this way, the system 800 has access to both the source storage system 200 and the destination storage system 220 for performing the steps according to the different embodiments. The steps according to the above embodiments can also be performed as instructions on one of the servers 203, 223, these servers having the same architecture as the system 800 of FIG. Have 8.
    Although the present invention has been explained with reference to specific embodiments, it will be apparent to those skilled in the art that the invention is not limited to the details of the foregoing exemplary embodiments, and that the present invention may be embodied with various changes and modifications. without departing from the scope thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes that are within the meaning and scope. of equivalence of the claims, are therefore intended to be included therein. In other words, it is intended to cover any and all modifications, variations, or equivalents that fall within the framework of the underlying basic principles and whose essential features are claimed in this patent application. It will further be clear to the reader of this patent application that the words "comprising" or "includes" do not exclude other elements or steps, that the word "one" does not exclude a plurality, and that a single element, such as a computer system, a processor or other integrated unit, can perform the functions of various means mentioned in the claims. Reference characters in the claims are not to be construed as limiting the respective claims concerned. The terms "first", "second", "third", "a", "b", "c" and the like, when used in the description or in the claims, have been introduced to distinguish between similar elements or steps and do not necessarily describe a sequential or chronological order. Similarly, the terms "above", "below", "over", "below" and the like have been introduced for description purposes and do not necessarily indicate relative positions. It will be understood that the terms thus used are interchangeable under suitable conditions and that embodiments of the invention are capable of operating in accordance with the present invention in other sequences or in orientations other than those described above or shown.
    权利要求:
    Claims (14)
    [1]
    CONCLUSIONS
    A computer-implemented method for migrating data from a source storage system 200 to a destination storage system 220, comprising the steps of: - performing (431, 531) an initial copy (101, 301); and - subsequently performing (432, 532, 535) one or more incremental copies (102-106, 108-110, 302-306); and then - subsequently executing (437, 537) a final incremental transition copy (111,311); characterized in that executing one or more incremental copies (102-110) further excludes (752), from a respective incremental copy of the one or more incremental copies, first data portions of the data that are likely to change prior to the performing a final incremental transition copy (111,311).
    [2]
    The method of claim 1, wherein executing (431, 531) an initial copy (101, 301) further excluding (752) from the initial copy second data portions of the data that are likely to change prior to executing (437, 537) of the final incremental transition copy (111, 311).
    [3]
    The method of claim 1 or 2, wherein the final incremental transition copy (111, 311) is performed when (536) a transfer amount of the one or more incremental copies has reached an equilibrium state (121, 321).
    [4]
    Method according to any of the preceding claims, wherein excluding first and / or second data parts comprises: - retrieving (641) metadata associated with data parts of the data on the source storage system; the metadata indicative of a probability that a respective data portion will change prior to the final incremental transition copy; - selecting the first and / or second data parts based on the metadata.
    [5]
    The method of claim 4, wherein the metadata comprises a file type of a respective data part; and wherein selecting first and / or second data parts comprises selecting data parts of a predetermined file type.
    [6]
    Method according to claim 4 or 5, wherein the metadata comprises a change overview of a respective data part; and wherein selecting first and / or second data parts comprises selecting data parts that were changed after a predetermined time.
    [7]
    Method according to one of the preceding claims, further comprising: - executing (534) an incremental intermediate copy (107), wherein no data parts are excluded; and - using (538) a duration of the incremental intermediate copy as an estimate for a duration of the final incremental transition copy.
    [8]
    The method of claim 7, wherein performing an incremental intermediate copy is performed on the same day of the week on which the execution of the final incremental transition copy is scheduled.
    [9]
    A method according to claim 7 or 8, wherein the execution of an incremental intermediate copy is performed at the same hour of the day as when the execution of the final incremental transition copy is scheduled.
    [10]
    The method of any one of claims 7 to 9 and claim 3, wherein performing an incremental intermediate copy (107) is performed when (533) a transfer amount of the one or more incremental copies (102-106) is in a steady state ( 120).
    [11]
    A method according to any one of the preceding claims, wherein performing an initial copy and / or performing one or more incremental copies and / or performing a final incremental transition copy and / or performing an incremental intermediate copy comprises: scanning (641) all or part of the data to be migrated on the source storage system and / or scanning (642) all or part of the already copied data on the destination storage system; and - subsequently creating (643) a list of commands for executing the execution; and - then executing (644) the list of commands.
    [12]
    A computer program product comprising computer-executable instructions for performing the method of any one of claims 1 to 11 when the program runs on a computer (800).
    [13]
    A computer-readable storage medium (808) comprising the computer program product of claim 12.
    [14]
    A data processing system programmed to perform the method according to any of claims 1 to 11.
    类似技术:
    公开号 | 公开日 | 专利标题
    US9250819B2|2016-02-02|Learning machine to optimize random access in a storage system
    US9286328B2|2016-03-15|Producing an image copy of a database object based on information within database buffer pools
    US8984027B1|2015-03-17|Systems and methods for migrating files to tiered storage systems
    US10073631B2|2018-09-11|Recalling files stored on a tape
    US8825653B1|2014-09-02|Characterizing and modeling virtual synthetic backup workloads
    BE1022200B1|2016-02-29|DATA MIGRATION TOOL WITH INCREMENTAL INTERMEDIATE COPIES
    CN107665219B|2021-01-29|Log management method and device
    US20170357680A1|2017-12-14|System and method for maintaining a multi-level data structure
    JP6156517B2|2017-07-05|Write information storage device, method, and program
    EP3144896A1|2017-03-22|Multi-representation dependency graphs
    KR20120082176A|2012-07-23|Data processing method of database management system and system thereof
    US10997127B2|2021-05-04|Preventing inefficient recalls in a hierarchical storage management | system
    US10620865B2|2020-04-14|Writing files to multiple tapes
    US10445409B2|2019-10-15|System and method of supporting user level file system transactions using batch rename and file clones
    US9952780B2|2018-04-24|Method for retrieving data from a tape drive
    EP3944101A1|2022-01-26|Information processing program, information processing method, and information processing device
    EP3940572A1|2022-01-19|Data generalization device, data generalization method, and program
    US10884998B2|2021-01-05|Method for migrating data records from a source database to a target database
    US10296221B1|2019-05-21|Systems and methods for improving the efficiency of recording data to tape
    US10691349B2|2020-06-23|Mitigating data loss
    US20220012217A1|2022-01-13|Archiving accelerator-only database tables
    US20200110819A1|2020-04-09|Low cost fast recovery index in storage class memory
    US9690886B1|2017-06-27|System and method for a simulation of a block storage system on an object storage system
    US10572452B1|2020-02-25|Context-based read-ahead for B+ tree data structures in a deduplication system
    JP4623644B2|2011-02-02|Full-text search processing system for large-capacity long-term storage data
    同族专利:
    公开号 | 公开日
    EP2996025A1|2016-03-16|
    DK2996025T3|2018-06-18|
    US10114579B2|2018-10-30|
    US20170269869A1|2017-09-21|
    WO2016037777A1|2016-03-17|
    EP2996025B1|2018-04-25|
    CA2959647A1|2016-03-17|
    CA2959647C|2021-02-23|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US7743028B1|2005-07-13|2010-06-22|Symantec Corporation|Incremental backup of partial volumes|
    US6996586B2|2003-06-18|2006-02-07|International Business Machines Corporation|Method, system, and article for incremental virtual copy of a data block|
    US7873601B1|2006-06-29|2011-01-18|Emc Corporation|Backup of incremental metadata in block based backup systems|
    US20120278553A1|2011-04-28|2012-11-01|Mudhiganti Devender R|System and method for migration of data clones|
    US8990162B1|2011-09-30|2015-03-24|Emc Corporation|Metadata generation for incremental backup|US10754073B2|2016-11-29|2020-08-25|3M Innovative Properties Company|Optical stack having reflective polarizer with polymeric layers and specified reflectance and transmittance|
    US10970310B2|2018-08-02|2021-04-06|Netapp Inc.|Synchronous replication based cutover engine|
    EP3889753A1|2020-03-30|2021-10-06|Datadobi bv|Data migration|
    法律状态:
    优先权:
    申请号 | 申请日 | 专利标题
    EP14184344.1A|EP2996025B1|2014-09-11|2014-09-11|Data migration tool with intermediate incremental copies|
    EP14184344|2014-09-11|
    [返回顶部]