Backup

Backups protect your ERP database, attachments, and configuration so you can recover from mistakes, hardware failure, or corruption.

What is backed up

A full backup includes:

• PostgreSQL database dump
• Filestore (attachments and documents)
• Environment configuration
• Addon and version manifest
• Integrity manifest for verification

You can also run a database-only backup when you only need the SQL dump.

Encryption

Local backups are encrypted when a passphrase is configured (SOVIEZ_BACKUP_PASSPHRASE or, preferably, SOVIEZ_BACKUP_PASSPHRASE_FILE). Disabling encryption is an advanced local-only option and weakens your recovery posture.

Local vs off-host

Term	Meaning
Local backup	Stored on the Soviez host; available for restore, but not a substitute for off-site disaster recovery by itself
Off-host destination	S3-compatible storage or SFTP — can serve as disaster recovery when configured and tested

Off-host backup is optional but recommended for organizations that need recovery if the server itself is lost.

Commands

soviez.sh --backup <production-id> [--type full|database-only] [--destination PROFILE]
soviez.sh --backup-list [--production ID]
soviez.sh --backup-show|verify|pin|unpin|delete <backup-id>
soviez.sh --backup-export <backup-id> --output PATH
soviez.sh --backup-import PATH [--confirm]
soviez.sh --backup-destination-list|show|test
soviez.sh --backup-schedule-add <production-id> [--destination PROFILE]
soviez.sh --backup-schedule-list
soviez.sh --security-backup-check

Verify before you need it

Run --backup-verify and --security-backup-check regularly. Corrupt or incomplete backups are reported and blocked from unsafe restore paths.

Pin important backups with --backup-pin so retention cleanup does not remove them.

Related

• RESTORE.md
• BACKUP_DESTINATIONS.md
• BACKUP_RETENTION.md
• DISASTER_RECOVERY.md