Konrad Kowalski (rootsher)Principal Platform & Reliability Architect000101010010111000000111101010100010001111010100

Databases

posts (4)

  1. Recovery from the Ground Up: Rollback, PITR, and Returning After Failure4/5

    PITR for One Tenant: Restoring One Database

    A simple PITR example in a multi-tenant system: one tenant has one database, so we restore only that database instead of rolling back the whole production…

  2. Recovery from the Ground Up: Rollback, PITR, and Returning After Failure3/5

    Whole-Server PITR: Restore Is Only the Beginning

    Whole-server PITR does not end when the database is restored. We still need to freeze writes, validate state, switch traffic, and consciously abandon or move…

  3. Recovery from the Ground Up: Rollback, PITR, and Returning After Failure2/5

    Rolling Back a Release: Code Is the Easy Part

    Release rollback often looks like returning to the previous application image. In practice, the hard parts are data, migrations, and side effects that already…

  4. series · 5 parts

    Recovery from the Ground Up: Rollback, PITR, and Returning After Failure

    Recovery does not start with a large disaster recovery plan. It starts with a simple question: what exactly do we need to return to, and how much can we lose?