Backup & Restore Overview
SYNTHET Backup & Restore lets you capture snapshots of your entire bot configuration and settings. Protect against accidental changes, test new configurations safely, and recover quickly if something breaks.
Quick Commands
/backup create — Manual backup capture/backup list — List backup history/backup info <version> — Show backup details/backup diff <v1> <v2> — Compare two versions/backup restore <version> — Start restore operation/backup schedule <on/off> — Toggle auto backups/backup stats — Backup statistics/backup purge — Delete ALL backup data (owner only)Dashboard Guide
Access backup features from the Backup Hub page in the SYNTHET dashboard:
Backup Hub Page
Central control panel for all backup operations:
- • Create new backup with optional description
- • View complete backup history with timestamps
- • Filter by backup type (manual/automatic)
- • Quick actions for each backup
- • Storage usage and quota information
Scheduling Settings
Configure automatic backup frequency:
- • Enable/disable automatic backups
- • Choose schedule (daily, weekly, monthly)
- • Set backup time and timezone
- • Configure retention period
- • View next scheduled backup
Version History
Manage and track all backup versions:
- • Timeline view of all backups
- • Backup size and module count
- • Creator and creation time
- • Mark/unmark as important
- • Download backup files
Diff Viewer
Compare changes between two backup versions:
- • Side-by-side comparison view
- • Highlight added/removed/modified settings
- • Filter by module type
- • Export diff report
Restore Wizard
Step-by-step guide for safe restoration:
- • Select source backup to restore
- • Preview what will be overwritten
- • Choose which modules to restore
- • Confirm before applying
- • Automatic backup created before restore
What Gets Backed Up?
Backups preserve your complete SYNTHET configuration:
Module Settings
Configuration for all enabled modules (Automations, Events, Feeds, Giveaways, etc.)
Automations
All automation workflows, triggers, actions, conditions, and event handlers
Events
Created events, recurring patterns, reminders, RSVP settings, series configurations
Feeds & Subscriptions
Feed sources (YouTube, Twitch, Reddit, RSS), delivery channels, message templates
Giveaways
Giveaway requirements, winner count, channel settings, prize details
Game Intel
Game subscription types (Steam patches, Epic free, driver updates, deals), notification channels
Suggestions System
Suggestion board settings, voting configuration, status workflows, review queue
Custom Commands
All custom slash commands and their response configurations
Moderation Rules
Auto-mod rules, filters, mute/kick/ban configurations, spam detection
Role Rewards
Level role assignments, reward configurations, leveling thresholds
Welcome Messages
Welcome DM templates, onboarding flows, channel greetings
RBAC Policies
Role-based access control, permission overrides, admin settings
Logging Channels
Configured logging channels and event types to log
Dashboard Preferences
Display settings, theme preferences, widget configurations, custom layouts
What Does NOT Get Backed Up?
These items are intentionally excluded for safety and consistency:
Discord Server Structure
Channels, roles, permissions, and server metadata are server-specific and managed by Discord, not backed up.
Historical Data & Analytics
Message logs, analytics data, behavior insights, incident history, and performance metrics are not included.
Member Data
Member profiles, levels, experience points, roles, and personal data change frequently and are not backed up.
API Keys & Secrets
Sensitive credentials, tokens, and API keys are never included in backups for security.
Transient State
Active events, pending giveaways, ongoing automations, and runtime state are not preserved.
Backup Types & Frequency
Choose between manual on-demand backups or automatic scheduled backups:
Manual Backups
Create snapshots instantly, anytime you want:
- • Created immediately on demand
- • Useful before major changes or experiments
- • Kept indefinitely until manually deleted
- • Can be downloaded and stored locally
- • Can be labeled with descriptions
Automatic Backups
Scheduled backups created on a recurring schedule:
- • Daily, weekly, or monthly frequency
- • Or custom cron expression for flexibility
- • Kept for configurable retention period (default 30 days)
- • Happens automatically in the background
- • Recommended: Schedule during off-peak hours
Backup Information & Retention
Each backup stores metadata for tracking and management:
Backup Metadata
- • Timestamp: Exact date and time created
- • Size: Backup file size (typically 2-15 MB)
- • Module Count: Number of modules included
- • Created By: Which admin created it
- • Type: Manual or automatic
- • Description: Optional notes and tags
Retention Policy
- • Manual backups: Kept indefinitely
- • Automatic backups: Kept for configurable period (default 30 days)
- • Storage limit: Maximum 50 total backups
- • Overflow handling: Oldest auto-backups deleted when limit reached
- • Marked important: Auto-backups tagged as important are never auto-deleted
Common Use Cases
Before Major Changes
Create backup before reconfiguring automations, moderation rules, or dashboard settings. Easy rollback if needed.
Disaster Recovery
Quickly restore from backup if something breaks, settings get accidentally deleted, or a bad automation causes issues.
Configuration Testing
Backup before testing new automation workflows or rule changes. Restore clean state if experiments fail.
Server Migration
Back up on old server, restore on new server to transfer complete SYNTHET configuration to another Discord server.
Compliance & Audit
Regular backups provide audit trail of configuration changes and compliance snapshots for record-keeping.
Seasonal Resets
Save configuration at season end, reset settings for new season, restore old config when season returns.
Backup Best Practices
- • Enable automatic daily backups at night for always-on protection
- • Create manual backup before any major configuration changes
- • Download and store important backups locally as offline copies
- • Label backups with descriptive names (e.g., "Before Major Automation Overhaul")
- • Review backup list monthly and delete very old manual backups
- • Test restore process quarterly to ensure backups are working correctly
- • Keep at least 3-5 recent backups available for quick rollback
- • Document major configuration changes with backup timestamps
- • Use diff viewer before restore to understand what will change
- • Mark critical backups as important to prevent auto-deletion