Data migration framework

A method, comprising:

• selecting, from a plurality of cohorts of entities, a cohort of entities for migration from a source storage repository to a target storage repository;
• obtaining a mapping between a source storage schema of the source storage repository to a target storage schema of the target storage repository;
• migrating data for a plurality of entities in the cohort, wherein migrating the data of an entity of the plurality of entities comprises:
• copying, without locking the data in the source storage repository, the data from the source storage repository to the target storage repository,
• locking, after copying, the data in the source storage repository and the target storage repository,
• verifying, while the data in the source storage repository and the target storage repository is locked, that the data in the source storage repository is the same as the data in the target storage repository,
• changing, while the data in the source storage repository and the target storage repository is locked, an entity pointer for the entity to the target storage repository based on the verifying, and
• unlocking the data in the source storage repository and the target storage repository,
• wherein, based on the entity pointer, the data in the target storage repository is accessed after migrating;
• receiving, by a first storage unit, an input output request for an account;
• determining, responsive to the input output request and by the first storage unit, that a current time is within a preset time range for performing migration;
• transmitting, from the first storage unit to a second storage unit, an account lock request to determine whether the account is locked;
• receiving a response to the account lock request;
• and
• processing the input output request when the account is not locked based on the response.

A method comprising:

• selecting, from a plurality of cohorts of entities, a cohort of entities for migration from a source storage repository to a target storage repository;
• obtaining a mapping between a source storage schema of the source storage repository to a target storage schema of the target storage repository;
• and
• migrating data for a plurality of entities in the cohort, wherein migrating the data of an entity of the plurality of entities comprises:
• copying, without locking the data in the source storage repository, the data from the source storage repository to the target storage repository,
• locking, after copying and prior to verifying the data, the data in the source storage repository and the target storage repository,
• waiting, after locking the data, a leading buffer time to verify the data,
• verifying, while the data in the source storage repository and the target storage repository is locked, that the data in the source storage repository is the same as the data in the target storage repository,
• changing, while the data in the source storage repository and the target storage repository is locked, an entity pointer for the entity to the target storage repository based on the verifying, and
• unlocking the data in the source storage repository and the target storage repository,
• wherein, based on the entity pointer, the data in the target storage repository is accessed after migrating.

A system comprising:

• a migration repository;
• a computer processor;
• and
• a migration service for executing on the computer processor, the migration service comprising:
• a scheduler for:
• selecting, from a plurality of cohorts of entities, a cohort of entities for migration from a source storage repository to a target storage repository, and
• scheduling a job to migrate the cohort, and
• a job manager for executing the job, wherein executing the job comprises:
• obtaining a mapping between a source storage schema of the source storage repository to a target storage schema of the target storage repository;
• and
• migrating data for a plurality of entities in the cohort, wherein migrating the data of an entity of the plurality of entities comprises:
• copying, without locking the data in the source storage repository, the data from the source storage repository to the target storage repository,
• locking, after copying and prior to verifying the data, the source storage repository and the target storage repository,
• waiting, after locking the data, a leading buffer time to verify the data,
• verifying, while the data in the source storage repository and the target storage repository is locked, that the data in the source storage repository is the same as the data in the target storage repository,
• changing, while the data in the source storage repository and the target storage repository is locked, an entity pointer for the entity to the target storage repository based on the verifying, and
• unlocking the data in the source storage repository and the target storage repository,
• wherein, based on the entity pointer, the data in the target storage repository is accessed after migrating.

A method comprising:

• partitioning a plurality of entities into a plurality of cohorts;
• and
• migrating each cohort of the plurality of cohorts individually, wherein migrating a cohort comprises migrating data for the plurality of entities in the cohort, wherein migrating the data of an entity of the plurality of entities comprises:
• copying, without locking the data in a source storage repository, the data from the source storage repository to a target storage repository,
• locking, after copying and prior to verifying the data, the source storage repository and the target storage repository,
• waiting, after locking the data, a leading buffer time to verify the data,
• verifying, while the data in the source storage repository and the target storage repository is locked, that the data in the source storage repository is the same as the data in the target storage repository,
• changing, while the data in the source storage repository and the target storage repository is locked, an entity pointer for the entity to the target storage repository based on the verifying, and
• unlocking the data in the source storage repository and the target storage repository,
• wherein, based on the entity pointer, the data in the target storage repository is accessed after migrating.