Services

Resources

Company

Our Work

Blog

#Data-Migration

Back to Tags

Blogs

May 14, 2025 | 8 min read

Optimizing MongoDB backup strategy: Lessons from achieving a 1-Hour RPO

Mihir Bhagwat

SRE @One2N

Sanket Rajgiri

SRE @One2N

This post walks through how we implemented a disaster recovery solution for a MongoDB cluster running on Google Kubernetes Engine (GKE) using the MongoDB Community Operator

May 14, 2025 | 8 min read

Optimizing MongoDB backup strategy: Lessons from achieving a 1-Hour RPO

Mihir Bhagwat

SRE @One2N

Sanket Rajgiri

SRE @One2N

This post walks through how we implemented a disaster recovery solution for a MongoDB cluster running on Google Kubernetes Engine (GKE) using the MongoDB Community Operator

May 14, 2025 | 8 min read

Optimizing MongoDB backup strategy: Lessons from achieving a 1-Hour RPO

Mihir Bhagwat

SRE @One2N

Sanket Rajgiri

SRE @One2N

This post walks through how we implemented a disaster recovery solution for a MongoDB cluster running on Google Kubernetes Engine (GKE) using the MongoDB Community Operator

May 14, 2025 | 8 min read

Optimizing MongoDB backup strategy: Lessons from achieving a 1-Hour RPO

Mihir Bhagwat

SRE @One2N

Sanket Rajgiri

SRE @One2N

This post walks through how we implemented a disaster recovery solution for a MongoDB cluster running on Google Kubernetes Engine (GKE) using the MongoDB Community Operator

May 14, 2025 | 8 min read

Optimizing MongoDB backup strategy: Lessons from achieving a 1-Hour RPO

Mihir Bhagwat

SRE @One2N

Sanket Rajgiri

SRE @One2N

This post walks through how we implemented a disaster recovery solution for a MongoDB cluster running on Google Kubernetes Engine (GKE) using the MongoDB Community Operator

Case Studies

Zero downtime MySQL schema migrations for 400M row table

Problem Statement. DB schema migrations on large tables (400+ million rows or 150+ GB in size for a single table) caused replication lag and impacted latencies. Adding indexes on large tables also resulted in replication lag and degraded query performance. Developers had to wait months to roll out their features which needed schema changes.

400 M

Biggest table migrated

7

migrations per month

0

Downtime due to schema migrations

Learn More

Zero downtime MySQL schema migrations for 400M row table

Problem Statement. DB schema migrations on large tables (400+ million rows or 150+ GB in size for a single table) caused replication lag and impacted latencies. Adding indexes on large tables also resulted in replication lag and degraded query performance. Developers had to wait months to roll out their features which needed schema changes.

400 M

Biggest table migrated

7

migrations per month

0

Downtime due to schema migrations

Learn More

Zero downtime MySQL schema migrations for 400M row table

Problem Statement. DB schema migrations on large tables (400+ million rows or 150+ GB in size for a single table) caused replication lag and impacted latencies. Adding indexes on large tables also resulted in replication lag and degraded query performance. Developers had to wait months to roll out their features which needed schema changes.

400 M

Biggest table migrated

7

migrations per month

0

Downtime due to schema migrations

Learn More

Zero downtime MySQL schema migrations for 400M row table

Problem Statement. DB schema migrations on large tables (400+ million rows or 150+ GB in size for a single table) caused replication lag and impacted latencies. Adding indexes on large tables also resulted in replication lag and degraded query performance. Developers had to wait months to roll out their features which needed schema changes.

400 M

Biggest table migrated

7

migrations per month

0

Downtime due to schema migrations

Learn More

Zero downtime MySQL schema migrations for 400M row table

Problem Statement. DB schema migrations on large tables (400+ million rows or 150+ GB in size for a single table) caused replication lag and impacted latencies. Adding indexes on large tables also resulted in replication lag and degraded query performance. Developers had to wait months to roll out their features which needed schema changes.

400 M

Biggest table migrated

7

migrations per month

0

Downtime due to schema migrations

Learn More

Migrating 1.3TB of Primary Data from Self-Hosted MySQL to GCP CloudSQL

Problem Statement. Build an automated backup and recovery process for the SIEM data Provide administrative controls for customizing the backup and restore options Implement tenant-wise customizations for data retention, data locality, and other parameters

Learn More

Migrating 1.3TB of Primary Data from Self-Hosted MySQL to GCP CloudSQL

Problem Statement. Build an automated backup and recovery process for the SIEM data Provide administrative controls for customizing the backup and restore options Implement tenant-wise customizations for data retention, data locality, and other parameters

Learn More

Migrating 1.3TB of Primary Data from Self-Hosted MySQL to GCP CloudSQL

Problem Statement. Build an automated backup and recovery process for the SIEM data Provide administrative controls for customizing the backup and restore options Implement tenant-wise customizations for data retention, data locality, and other parameters

Learn More

Migrating 1.3TB of Primary Data from Self-Hosted MySQL to GCP CloudSQL

Problem Statement. Build an automated backup and recovery process for the SIEM data Provide administrative controls for customizing the backup and restore options Implement tenant-wise customizations for data retention, data locality, and other parameters

Learn More

‹ Data-Engineering

Go ›