Skip to main content

Backups

Skysize provides comprehensive backup and restore capabilities to protect your data and ensure business continuity.

Automatic Backups​

Schedule​

Automatic backups are generated daily at 1:00 AM (platform time) for all production environments.

Backup Retention Policy​

Skysize maintains multiple backup copies with the following retention schedule:

  • 7 daily backups: Last 7 days of backups
  • 4 weekly backups: Last 4 weeks of backups
  • 2 monthly backups: Last 2 months of backups

This policy ensures you have access to recent backups while maintaining historical recovery points.

Multi-Region Redundancy​

For maximum data protection, each backup is stored in three separate locations:

Primary Storage (2 copies)​

Two copies are stored in Google Cloud Platform within the same region as your deployment:

  • Fast access for quick restores
  • High availability within the region
  • Redundant storage for reliability

Secondary Storage (1 copy)​

One copy is stored in AWS in a different region:

  • Protection against regional disasters
  • Cross-cloud redundancy
  • Geographic separation for compliance

This multi-region, multi-cloud approach ensures your data is safe even in the event of a regional outage or cloud provider issues.

Manual Backups​

In addition to automatic daily backups, admins can create manual backups at any time.

When to Create Manual Backups​

  • Before major deployments or updates
  • Before data migrations
  • Before testing potentially destructive operations
  • When you want a specific point-in-time snapshot

Creating a Manual Backup​

  1. Navigate to your project in Skysize dashboard
  2. Go to the Backups section
  3. Click "Create Backup"
  4. Wait for the backup to complete
  5. Backup appears in your backup list

Manual backups follow the same redundancy strategy as automatic backups.

Restoring from Backups​

Restore Options​

You can restore backups to any branch in your project:

  • Restore production backup to staging for testing
  • Restore to a new development branch
  • Restore production to itself for recovery

Restore Process​

  1. Select the backup you want to restore
  2. Choose the target branch
  3. Confirm the restore operation
  4. Wait for restore to complete
  5. Verify data in the restored environment
caution

Restoring to an existing branch will replace all data in that branch's database. Make sure you have a backup before restoring.

Download and Import​

Downloading Backups​

You can download backups for:

  • Local storage and archival
  • Compliance and audit requirements
  • Offline analysis
  • Migration to other systems

Importing Backups​

Import backups to:

  • Restore to different environments
  • Migrate data between projects
  • Set up local development environments
  • Disaster recovery scenarios

Backup Contents​

Each backup includes:

  • Database: Complete PostgreSQL database dump
  • Filestore: All uploaded files and attachments

Best Practices​

Regular Testing​

Test your backups regularly:

  • Restore to a development or staging environment
  • Verify data integrity
  • Test recovery procedures
  • Ensure your team knows the restore process

Before Major Changes​

Always create a manual backup before:

  • Major Odoo version upgrades
  • Significant data migrations
  • Large-scale data imports
  • Schema changes

Compliance and Retention​

Consider your compliance requirements:

  • Download backups for long-term archival if needed
  • Understand the retention policy (7 daily, 4 weekly, 2 monthly)
  • Store critical backups offline if required by regulations

Documentation​

Document your backup and restore procedures:

  • Who has access to create/restore backups
  • Recovery time objectives (RTO)
  • Recovery point objectives (RPO)
  • Emergency contact procedures

Backup Security​

Encryption​

All backups are encrypted:

  • At rest in Google Cloud Storage
  • At rest in AWS
  • During transfer between systems

Access Control​

Only authorized users can:

  • Create manual backups
  • Restore backups
  • Download backups
  • View backup contents

Admin role is required for all backup operations.

Disaster Recovery​

Recovery Time Objective (RTO)​

Typical restore times:

  • Small databases (< 1GB): 10-30 minutes
  • Medium databases (1-10GB): 30-60 minutes
  • Large databases (> 10GB): 1-3 hours

Recovery Point Objective (RPO)​

Maximum data loss:

  • With daily backups: Up to 24 hours
  • With manual backups: As recent as your last manual backup

Multi-Region Recovery​

In the event of a complete regional failure:

  1. Backups remain accessible from AWS in alternate region
  2. Create new deployment in different region
  3. Restore from cross-region backup
  4. Update DNS to point to new region
  5. Resume operations

Monitoring Backups​

Backup Status​

Monitor backup health through the Skysize dashboard:

  • View recent backup history
  • Check backup sizes
  • Verify backup completion
  • Review any backup failures