Backup Failures

Backups are managed by a separate Odoo instance — the Backup Server. The Master registers subscriptions and queries backup state over HTTP using an API key. Failures can occur at registration, at scheduled execution time, during cloud upload, or during restore.

See Tutorial: Set Up Backup Storage for initial configuration.

Backup State Indicator

The Backup State field on the subscription form (displayed as a colored badge) reflects the health of automated backups.

Architecture Reminder

The backup system runs on a separate Odoo instance. The Master registers subscriptions and queries their state via HTTP API. If the Backup Server is unreachable, backups cannot run and the Master cannot report accurate state.

Master Odoo  ──── HTTP API + API key ────▶  Backup Server Odoo
                                              (sadeem_saas_backup_manager)
                                                      │
                                                      ▼
                                              Cloud Storage (S3 / compatible)

Common Failures

1. Backup Server Unreachable

Symptom: Backup state is stuck at not_configured for a subscription that has been Running for some time, or state shows danger with 0 backups.

1. Navigate to SAAS Management → Infrastructure → Backup Servers → <server>.
2. Click Test Connection — a green result confirms the Master can reach the Backup Server API.
3. If the connection fails, verify the URL and API Key on the backup server record.
4. If the Backup Server Odoo process is down, SSH to the server and restart it, then retest.
5. After restoring connectivity, re-register the subscription: open the subscription form and click Action → Register Backup.

2. S3 / Cloud Credentials Invalid or Expired

Symptom: Backups are created on the Backup Server but cloud upload fails. The backup count in the Master stays at 0 even though the Backup Server shows activity.

1. Log into the Backup Server Odoo (not the Master).
2. Navigate to the storage account records (sadeem.saas.backup.storage.account) and check for credential errors in the record chatter or server logs.
3. Update the credentials in the affected storage account record on the Backup Server.
4. Back on the Master, navigate to the backup server record and click Action → Sync Cloud Accounts to pull the updated account list.

3. Disk Full on Backup Server

Symptom: Backups stop running. Backup Server logs show disk space errors.

1. SSH to the Backup Server host.
2. Check available space:

   df -h
   

3. Free disk space or expand the volume.
4. Consider reducing backup retention counts in the scheduled action configuration on the Backup Server.

4. Queue Job Worker Not Running

Symptom: The backup registration POST was sent (visible in Backup Server access logs) but the backup job never executed. backup_uuid is assigned but 0 backups exist.

1. Log into the Backup Server Odoo.
2. Navigate to Technical → Queue Jobs → Jobs and filter by Failed or Pending status — look for backup-related jobs.
3. Restart the queue_job worker process on the Backup Server. Check your process manager:

   # Supervisor
   supervisorctl restart odoo-queue-job
   
   # Systemd
   systemctl restart odoo-queue-job
   

4. Re-trigger the job from the Queue Jobs list if it is in Failed state.

5. Cloud Accounts Out of Sync

Symptom: Backup subscriptions reference cloud accounts that no longer exist on the Backup Server, or newly added cloud accounts do not appear when configuring a subscription.

1. Navigate to SAAS Management → Infrastructure → Backup Servers → <server>.
2. Click Action → Sync Cloud Accounts.
3. This calls GET /sadeem/backup/cloud-accounts on the Backup Server and refreshes the local account list on the Master.
4. Verify the expected accounts now appear in the Cloud Accounts tab of the backup server record.

Retrying a Backup Manually

1. Open the subscription form.
2. Click the Backup smart button to open the backup list.
3. Review the most recent entry for status details and any error messages.
4. To trigger an immediate backup: log into the Backup Server Odoo and run the backup scheduled action manually from Technical → Automation → Scheduled Actions.

Restore Operations

If Restore Local fails, verify:

• The saas_slave_enabled checkbox is ticked on the subscription form.
• The customer instance is in Running state.
• The file or URL provided in the wizard is valid and accessible from the customer instance.

Related Pages

• Tutorial: Set Up Backup Storage
• Concepts: SaaS Slave
• Concepts: Architecture Overview