EDB Postgres Data Migration

 

Service Overview

EDB Postgres Data Migration is designed to ensure the success of a critical step in moving a legacy database to EDB Postgres, the migration of data. This package accelerates the process by helping to configure appropriate tooling for minimal downtime migrations, executing, validating, and documenting the process to ensure ongoing migration success. The offering is available in three tiers based on the total data volume for one (1) database in a single non-production environment. 

 

Small

Medium

Large

Database Size

Less than 1TB

Less than 5TB

5TB or Greater

 

Scope of Service

An EDB consultant will guide your team through the foundational migration execution, focusing on the following key activities:

  • Planning: Review and agree on a downtime window to plan and execute migration activity with appropriate tooling.
  • Migration Tooling Setup: Install and configure the migration tooling (e.g. EDB Migration Toolkit or Replication Server) to orchestrate the connection and data transfer between the source and target databases.
  • Data Migration: Execute the physical data migration from the source system to the target EDB Postgres database(s) validated with EDB supported tooling. 
  • Runbook Creation: Document a detailed migration runbook that captures the exact steps, configurations, and validations used, ensuring the process is repeatable for future environments in the agreed downtime window. 

 

Deliverables

At the conclusion of the engagement, EDB will provide the following:

  • Fully configured data migration tooling using mutually agreed EDB supported tools.
  • Migrated target database(s) per sizing tier.
  • Comprehensive Migration Runbook, including any post-migration scripting.

 

Roles and Responsibilities

EDB Project Manager:  Responsible for initial planning, task alignment, and project closeout.

EDB Senior Consultant: Technical Lead, responsible for execution of schema conversion, MTK deployment, configuration, validation and documentation.

Customer Team: Responsible for providing the main point of contact for requirements and prerequisites gathering. . Resources and Roles (or similar Technical Stakeholders) where input may be needed for the engagement include:

  • Database Administrator
  • System Architect
  • Application Owner(s)
  • Infrastructure Manager 
  • Network Administrator
  • Security Officer 

 

Assumptions

  • A project kickoff will be conducted to review the service scope and confirm the schedule.
  • This service is delivered remotely unless otherwise agreed.
  • EDB will provide a secure fileshare for customer to share prerequisites for analysis.
  • Customer will provide the names, title, email, phone number, and area of responsibility of those participating. One person will be designated as the main contact, and will be able to provide access to the people most knowledgeable about the topics to be discussed or examined. 
  • Customer will make appropriate personnel available to assist EDB in the performance of the services as needed and requested by EDB in a timely manner so as not to disrupt the project schedule. 
  • Customer will not provide Personal Data (as defined in applicable law). Customer agrees that it will work with EnterpriseDB to ensure that all such data is not provided.  
  • Customer will ensure timely access to all systems through screen sharing and experts including third parties as required. 
  • Customer will assign the appropriate resources with the appropriate privileges for the task being planned for any screen sharing sessions as needed throughout the engagement.
  • Customer will provide timely feedback on all deliverables. Deliverables without commentary within 5 business days will be deemed as delivered.
  • Schema and Object counts are unchanged and consistent with the migration assessment performed and documented by EDB.
  • EDB will leverage mutually agreed tooling for data migration and validation including but not limited to:
    • EDB Migration Toolkit
    • EDB Replication Server
    • EDB LiveCompare
  • Current Databases available for migration include: 
    • Oracle
    • MySQL
    • MariaDB
    • DB2
    • Sybase
    • SQL Server
  • EDB and Customer will mutually agree on a downtime window for migration execution. 


Prerequisites

  • Customer will provide resource availability for workshop planning and a point of contact for coordination. 
  • Customer will provide additional infrastructure as required to support installation of EDB tooling.
  • Customer is responsible for gathering all data for analysis including:
    • DDL extracts 
    • Migration Questionnaires
    • SQL extracts or example application code
  • Customer is responsible for providing all necessary internal design and project related documentation and requirements where EDB is required to analyze, operate, or modify customer implemented systems.
  • Customer will coordinate availability of Application teams to support any migration related queries
  • Customer acknowledges that during the engagement there may be work required by Customer’s team related to configuration changes, performance, testing activities, and other efforts related to the Migration effort.  
  • Customer understands that moving from Customer’s current drivers to the latest Postgres drivers may require configuration changes and testing by the Customer during the engagement. 
  • Customer is responsible for upstream and downstream applications, APIs, data validation and testing requirements.
  • Customer understands that stored procedure updates may require configuration changes and testing by the Customer during the engagement. 
  • Customer will make no database and/or schema changes during the engagement period