Backups & Snapshots

There are two distinct strategies for backing up stateful data in RasnuOS: Logical Dumps (managed by the Agent) and Block Storage Snapshots (managed via the Cloud API).

A resilient infrastructure utilizes both.

Logical Database Dumps

A logical dump extracts the exact SQL required to rebuild your database.

Because the RasnuOS Agent is running natively on your server, you can schedule automated logical backups directly from the dashboard.

1. The Execution: The Agent executes mysqldump or pg_dump locally.
2. The Compression & Encryption: The Agent pipes the output through gzip and optionally encrypts the archive using an asymmetric GPG key.
3. The Offsite Transfer: The Agent natively streams the encrypted archive directly to an S3-compatible object storage bucket (e.g., AWS S3, Cloudflare R2, or Backblaze B2).

The backup file never touches the RasnuOS Control Plane. It moves securely from your server directly to your private AWS S3 bucket.

Restoring from a Logical Dump

If you need to restore data, you simply select the backup point in the UI. The Agent will reverse the process: pulling the archive from S3, decrypting it, and piping it back into the local database daemon natively.

Block Storage Snapshots

Logical dumps are perfect for point-in-time recovery of individual tables, but they are slow to restore.

For catastrophic disaster recovery, RasnuOS integrates with your Cloud Credentials to orchestrate full-disk Block Storage Snapshots.

If you have connected DigitalOcean or AWS, you can configure a daily schedule in RasnuOS. The Control Plane will issue native API commands to your cloud provider to freeze the block storage volume and take a bit-for-bit snapshot of the entire server disk.

If the server is ever completely destroyed, you can use that snapshot to provision an identical clone of the server natively from the RasnuOS dashboard.