1. Docs
  2. Administration
  3. Self-Hosting
  4. Operations
  5. Backup and Recovery

Backup and Recovery

    Self-hosting is only available with Pulumi Business Critical. If you would like to evaluate the self-hosted Pulumi Cloud, sign up for the 30-day trial or contact us.

    A reliable backup and recovery strategy is essential for self-hosted Pulumi Cloud. This page covers database backups, object storage protection, and recovery procedures.

    Database backups

    Automated backups

    • Enable automated daily backups.
    • Schedule backups during low-traffic periods.
    • Test restore procedures regularly.

    Cross-region backups

    For disaster recovery, copy backups to a secondary region:

    • Enable point-in-time recovery (PITR) on your database.
    • With versioning and cross-region replication on object storage enabled, you have:
      • Protection against accidental deletion (versioning)
      • Regional failure protection (cross-region replication)

    Recovery procedures

    Document and test these recovery scenarios:

    ScenarioRecovery approachRTO target
    Single AZ failureAutomatic failover (DB, compute, LB)< 5 minutes
    Database instance failureAutomatic failover to replica< 1 minute (Aurora), < 5 minutes (RDS)
    Object storage corruptionRestore from versioned object< 15 minutes
    Full region failureRestore DB from cross-region backup, fail over storage1–4 hours
    Accidental state deletionRestore from S3 versioning or DB PITR< 30 minutes

    Resource protection

    • Enable deletion protection on your database cluster and load balancer.
    • Mark critical Pulumi resources as protect: true in your IaC code to prevent accidental destruction.
    • Take a final snapshot before any planned database deletion.