Backup & Retention Overview

We take data protection seriously. Below is an overview of how backups work within our platform, including what’s included, how often backups occur, and how long they’re kept.

📂 What’s Included in a Backup?

Every backup—whether created automatically or manually—contains a complete snapshot of your database at the time of the backup. This includes everything needed to fully restore your data.

🕒 When Do Backups Occur?

We support two types of backups at the database level:

⚙️ System-Generated Backups

• Created automatically on a regular schedule

• Retained according to our rolling retention policy to optimize storage

🙋 User-Initiated Backups

Often called “snapshots,” “checkpoints,” or “versions” by users:

• Created manually via Cloud Storage

• Never deleted automatically

• Remain until you choose to remove them

📦 Backup Retention: How Long Are Backups Kept?

We use a rolling retention policy that balances data protection with storage efficiency. Here’s how it works:

Retention Tier	Time Period	What’s Retained
Short-Term	Days 1–4	Always keep the 4 most recent backups
Weekly	Days 5–7	Keep 1 additional backup
Bi-Weekly	Days 8–14	Keep the newest and oldest backups
Monthly	Days 15–30	Keep the newest and oldest backups
Long-Term	Day 31+	Keep the newest and oldest backups

This approach ensures both recent and historical backups are available, while preventing excessive storage use.

☁️ Server-Level Backups (Disaster Recovery)

In addition to per-database backups, we also perform server-level backups:

• Frequency: Daily

• Scope: Entire PostgreSQL server

• Redundancy: Zone-redundant for added resilience

• Retention: Backups are stored for 34 days

These backups are designed for full-server recovery in extreme scenarios, while database-level backups offer more precise restore options.

💡 Backup Best Practices & Tips

To help you get the most from your backup options, we recommend the following:

• Before Major Changes: Create a user-initiated backup (“snapshot”) before making significant updates or running complex models.

• Review & Clean Up: Periodically review your user-initiated backups and delete any that are no longer needed to keep your workspace organized.

• Know How to Restore: Restoring from backups can be initiated directly within the platform. For step-by-step instructions, visit our Model Sharing & Backups for Multi-User Collaboration in Cosmic Frog article .

• Track Critical Backups: Document the timestamps or names of important backups your team may need for future reference.

If you have additional questions about backups or retention policies, please contact our support team at support@optilogic.com