Obmondo logo
  • Why Obmondo
  • Scope of Service
  • Compliance
  • Pricing
  • Features
LoginSignup
Close
  • Why Obmondo
  • Scope of Service
  • Compliance
  • Pricing
  • Features
  • GitHub
LoginSignup
    • digital sovereignty at the core
    • how we work
    • services
    • onboarding
    • security & access
    • monitoring & alerts
    • backup strategy
    • restore & disaster recovery
    • pricing & contract
    • SKI 02.22
      • digital sovereignty at the core
      • how we work
      • services
      • onboarding
      • security & access
      • monitoring & alerts
      • backup strategy
      • restore & disaster recovery
      • pricing & contract
      • SKI 02.22
      Obmondo

      Open-source platform for security, compliance, and operations — run on any cloud with no vendor lock-in.

      Products

      • Services
      • Features
      • Pricing
      • Compliance
      • Scope of Service

      Company

      • About
      • Solutions Brief
      • Careers
      • Blog
      • Why Obmondo

      Contact

      • info@obmondo.com
      • sales@obmondo.com
      • Talk to us
      • Contact Us

      © 2026 Obmondo. All rights reserved.

      Terms & ConditionsUnsubscribe
      1. scope of service
      2. 7
      3. backup strategy

      Backup Strategy

      Our backup approach depends on whether we are working with a clean, newly provisioned server or an existing environment.

      New Installations

      When you provide a blank server (typically a minimal install of Ubuntu or Debian LTS), we deliver a fully open-source backup setup and can configure all required backup strategies as part of the deployment.

      Existing Systems

      For existing servers, we cannot assume anything about what has been configured, and we do not modify your setup without alignment. In these cases, we work with you to evaluate your current backup approach and agree on a path forward that meets your reliability and recovery requirements.

      Backup Methods

      We support multiple backup strategies depending on the system and your needs:

      • Point-in-Time Recovery (PITR) for PostgreSQL using WAL archiving to S3 and for other systems, that support PITR

      • Snapshots for Kubernetes storage for rapid local recovery

        • Snapshots WILL be pushed to s3 for host redundant backup - and backup server - SHOULD be replicated to offsite location

      Anything we don’t already support, we can extend - our tooling is open source and continuously improved.

      Frequency & Retention

      Backup frequency is typically based on what already works for you. We review your current policies, recommend improvements if needed, and help define a schedule that fits your RPO/RTO requirements.

      Storage & Encryption

      We normally push backups to S3-compatible storage. Encryption options include:

      • Client-side encryption (recommended), or
      • Storing backups unencrypted on S3 while encrypting the data disk on the backup server using LUKS

      Backups can be encrypted at rest, depending on the configuration you select, and are always encrypted in transit via HTTPS.

      On this page

      • New Installations
      • Existing Systems
      • Backup Methods
      • Frequency & Retention
      • Storage & Encryption