Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

Cutover Steps and Post-Migration Validation

  • how-to
    +
    This section outlines the cutover plan and post-migration validation steps to verify a smooth transition from Couchbase Analytics Service (CBAS) to Couchbase Enterprise Analytics.

    This section outlines the cutover plan and post-migration validation steps to verify a smooth transition from Couchbase Analytics Service (CBAS) to Couchbase Enterprise Analytics. The cutover plan is designed to minimize downtime and make sure that all applications and services continue to function during and after the migration.

    Cutover Plan for Dual-Cluster Environment

    To set up and run 2 or more clusters simultaneously, use 1 of the following approaches:

    • Parallel Cluster Configuration

    • Application Cutover Approach

    The parallel cluster configuration utilizes both CBAS (within an existing Couchbase Server OLTP cluster) and Couchbase Enterprise Analytics (dedicated OLAP cluster) to operate simultaneously during the transition period.

    • Production Environment: Analytics applications continue using CBAS through SDK connections and JDBC drivers for Couchbase Server Analytics Service and Capella Operational Analytics Service.

    • Development/Test Environment: You’re advised to create a replica of your applications using the new Analytics SDK. The new replica application must connect to Couchbase Enterprise Analytics cluster for validation and testing. For more information, see Migration.

    • Data Synchronization: Real-time data replication from operational Couchbase Server to both CBAS and Enterprise Analytics clusters.

    • Preparation and Validation

      • Deploy Couchbase Enterprise Analytics cluster in parallel to existing CBAS infrastructure

      • Configure data synchronization from Couchbase Server to both analytics platforms

      • Update development and test application instances to connect to Enterprise Analytics cluster

      • Validate query compatibility and performance in non-production environments

    • Gradual Application Migration

      • SDK-based Analytics Applications: You’re advised to create a replica of your applications using the new Analytics SDK. All the CBAS analytics features are available in the new enterprise analytics SDK. The new replica application should connect to Couchbase Enterprise Analytics cluster for validation and testing. For more information, see Migration.

      • BI Tools with JDBC: Modify JDBC connection URLs to target Enterprise Analytics JDBC driver and endpoints. You need to use the existing connectors for JDBC with the new endpoints for existing BI tools.

      • Implement feature flags or configuration switches to enable rapid rollback if needed.

      • Monitor both clusters for performance, data consistency, and application behavior.

    • Production Cutover

      • Migrate the new application to production environment.

      • Execute planned maintenance window for production application cutover.

      • Switch production applications from CBAS to Enterprise Analytics using pre-validated connection configurations.

      • Maintain CBAS cluster in standby mode for immediate rollback capability.

      • Implement monitoring and alerting for both clusters during transition period.

    • CBAS Decommissioning

      • Monitor Enterprise Analytics cluster stability and performance for minimum 2 weeks post-cutover.

      • Validate all critical business processes and reporting functions.

      • After successful validation period, begin CBAS cluster decommissioning:

        • Stop CBAS Analytics Service on Couchbase Server nodes.

        • Remove CBAS-specific configurations and indexes.

        • Reclaim resources (CPU, memory, storage) allocated to CBAS.

        • Update monitoring and backup procedures to remove CBAS references.

      • Document final decommissioning steps and resource reclamation for audit purposes.

    Final Checklist

    You must make sure that you have completed all essential tasks and verify them before officially declaring the migration successful and transitioning operations to the new database. This is a critical step that acts as a final sanity check.

    • Application Connectivity Verification: Confirm that all applications can connect to the new database environment.

    • Initial Data Verification: Confirm that a representative sample of data is migrated.

    • Performance sanity checks: Test some critical, high-impact queries to verify that initial performance is within acceptable limits and no regressions in performance.

    • Security Validation Verify that basic security configurations are in place and functioning (For example, RBAC).

    • Sign-off Obtain formal sign-off from designated stakeholders that migration activity is complete.