Method and system for data migration

• US 8,032,523 B2
• Filed: 05/08/2008
• Issued: 10/04/2011
• Est. Priority Date: 05/08/2008
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Stahl, Elisabeth R., Salve, Vivek, Hamilton, Rick A. II, Sand, Anne R., Li, Jenny S.
• Primary Examiner(s): Ali; Mohammad
• Assistant Examiner(s): Hocker; John P
• Application Number:
  US12/117,330
• Publication Number:
  US 20090282273A1
• Time in Patent Office: 1,244 Days
• Field of Search: 707/720, 707/809
• US Class Current: 707/720
• CPC Class Codes: G06F 1/3203 Power management, i.e. event-based initiation of a power-saving mode

Abstract

A method and system for migrating source data from one or more databases to a destination database, wherein the destination database is selected based on power consumption of the destination database. A data migration server determines which destination database should be selected by selecting a number of candidates and comparing the power consumed, the available space and the maximum monthly power consumption limit. A user intervention policy is created to evaluate which data should be moved to a destination database. A “payback period” is calculated to determine the amount of time that will elapse before savings are realized.

Claims

1. A method for determining whether a data migration server should migrate source data from a source database to a destination database, wherein the source and destination databases carry out one or more transactions, comprising:

determining the average power consumption per transaction of the source database;

surveying with the data migration server a plurality of candidates for a destination database by monitoring the power consumption level of each of the plurality of candidates,

wherein the step of monitoring the power consumption level comprises checking each of the plurality of candidates for i) available space;

ii) power consumed up to the point of checking; and

iii) maximum monthly power consumption limit;

comparing the average power consumption per transaction of the source database against the average power consumption per transaction of each candidate;

selecting a candidate from the plurality of destination database candidates that uses less power consumption per transaction than the source database;

moving the source data to the selected destination database; and

surveying with the data migration server, after moving the source data to the selected destination database, the plurality of candidates for changes in the average power consumption per transaction of each candidate; and

relocating the source data from the selected destination database to a second destination database if the second destination database uses less power consumption per transaction than the selected destination database.

2. The method of claim 1 wherein the monitoring step is performed periodically.

3. The method of claim 1 further comprising relocating the source data from the selected destination database to the second destination database if the power consumption increases past a preset threshold.

4. The method of claim 1 wherein the method of migrating source data from a source database to a destination database is carried out by the data migration server.

5. The method of claim 1 further comprising:

creating a user intervention policy comprising factors related to the source data to determine which source data should be migrated whereby the factors comprise one or more of;

i) a list of one or more databases, ii) archive status of the one or more databases, iii) criticality of the one or more databases, iv) applications of the one or more databases, and v) scheduling of the one or more databases.

6. The method of claim 5 whereby weighted value is assigned to each of the factors to assist in determining which source data should be migrated.

7. The method of claim 6 wherein the source data is categorized into categories comprising one or more of:

i) less critical, ii) more critical;

iii) older, iv) recent, v) used infrequently, and vi) used every day; and

whereby the less critical, older data that is used infrequently is moved to a database that has less power efficiency than the source database.

8. The method of claim 1 further comprising computing a payback period to determine the length of time as defined by x, measured by a predefined time period, required before the savings are realized comprising:

estimating the ownership cost per predefined time period of the source database defined as T₀;

estimating the energy consumption cost per predefined time period of the source database defined as E₀;

estimating the cost of migrating the source data to the destination database defined as M_i;

estimating the ownership cost per predefined time period of the destination database T_i;

estimating the energy consumption cost per predefined time period of the source database E_i;

whereby (T₀+E₀)x=M_i+(T_i+E_i)x.

9. The method of claim 8 wherein the predefined time period is measured in minutes, hours, days, months, or years.

10. A system for determining whether source data should be migrated from one or more source databases to a destination database comprising:

one or more source databases;

a plurality of destination databases;

one or more staging databases;

a data migration server;

whereby the data migration server determines whether the one or more source databases should be moved to one or more of the plurality of destination databases based on power consumption parameters, selects one of the destination databases for the migration of the source data thereto by i) monitoring the power consumption level of the plurality of destination databases by checking each of the plurality of candidates for available space, power consumed up to the point of checking, and maximum monthly power consumption limit;

ii) comparing the power consumption level of each of the plurality of destination databases; and

iii) selecting the destination database that uses the least amount of power per transaction,

moves the source data to the selected destination database,

continues to survey the plurality of candidates for changes in the average power consumption per transaction of each candidate; and

relocates the source data from the selected destination database to a second destination database if the second destination database uses less power consumption per transaction than the selected destination database.

11. The system of claim 10 wherein the data migration server creates a user intervention policy comprising factors related to the source data to determine which source data should be migrated whereby the factors comprise i) a list of one or more source databases, ii) archive status of the one or more source databases, iii) criticality of the one or more source databases, iv) applications of the one or more source databases, and v) scheduling of the one or more source databases.

12. The system of claim 11 whereby a weighted value is assigned to each of the factors to assist in determining which source data should be migrated.

13. The system of claim 12 wherein the data migration server computes a payback period to determine the length of time as defined by x, measured by a predefined time period, required to pass before savings are realized from the migration of data to the destination database, by using formula (T₀+E₀)x=M_i+(T_i+E_i)x, whereby

T₀=estimated total cost per predefined time period of ownership of the source database;

E₀=estimated cost per predefined time period of the energy consumption of the source database;

M_i=estimated cost of migrating the source data to the destination database;

T_i=estimated cost per predefined time period of ownership of the destination database; and

E_i=estimated cost per predefined time period of the energy consumption of the destination database.

14. The system of claim 13 wherein the predefined time period is measured in minutes, hours, days, months, or years.

15. A computer program product encoded in a non-transitory computer readable storage medium for instructing a migration data server to determine whether source data from a source database should be moved to a destination database, wherein the source and destination databases carry out one or more transactions, comprising:

instructing the migration data server to determine the average power consumption per transaction of the source database;

instructing the migration data server to survey a plurality of candidates for a destination database by evaluating the average power consumption per transaction of each candidate, wherein the migration data server evaluates the average power consumption per transaction of each candidate comprises checking each of the plurality of candidates for i) available space;

ii) power consumed; and

iii) maximum monthly power consumption limit;

instructing the migration data server to compare the average power consumption per transaction of the source database against the average power consumption per transaction of each candidate;

instructing the migration data server to determine if the average power per transaction of the source database is greater than the average power consumption per transaction of any of the plurality of candidates;

instructing the migration data server to select the destination database that uses less power consumption per transaction than the source database;

instructing the migration data server to move the source data to the selected destination database;

instructing the migration data server to survey, after moving the source data to the selected destination database, the plurality of candidates for changes in the average power consumption per transaction of each candidate; and

instructing the migration data server to relocate the source data from the selected destination database to a second destination database if the second destination database uses less power consumption per transaction than the selected destination database.

16. The computer program product of claim 15 further instructing the data migration server to compute a payback period to determine the length of time as defined by x, measured in a predefined time period, required to pass before savings are realized from the migration of data to the destination database, by using formula (T₀+E₀)x=M_i+(T_i+E_i)x, whereby

T₀=estimated total cost per predefined time period of ownership of the source database;

E₀=estimated cost per predefined time period of the energy consumption of the source database;

M_i=estimated cost of migrating the source data to the destination database;

T_i=estimated cost per predefined time period of ownership of the destination database; and

E_i=estimated cost per predefined time period of the energy consumption of the destination database.

17. The system of claim 16 wherein the predefined time period is measured in minutes, hours, days, months, or years.