Core Features

Backup System

Complete server backup and restoration system for Lumière Bot.

Enterprise-grade backup system with compression, scheduled automation, and granular restoration control.

One backup per server - Each new backup automatically replaces your previous one for the same server.

Quick Start

/backup create                    # Create full backup
/backup list                      # View all backups
/backup load backup_id:ID         # Restore backup

What Gets Backed Up

Roles & Permissions Names, colors, permissions, hierarchy
Channels All channel types, categories, permissions, settings
Threads Active threads with members and settings
Server Settings Verification, AFK, notifications, icon, banner
Emojis & Stickers All custom emojis and stickers
Bans Banned users with reasons
Member Data User roles and nicknames
Pinned Messages Up to 10 pins per channel/thread

Commands

Basic Operations

CommandDescription
/backup create [name]Create backup (select components)
/backup listView all your backups
/backup info backup_idDetailed backup information
/backup load backup_idRestore backup (select components)
/backup delete backup_idDelete specific backup
/backup purge [server_filter]Delete multiple backups

Restoration Management

CommandDescription
/backup statusCheck restoration progress
/backup cancelCancel ongoing restoration

Scheduled Backups

CommandDescription
/backup interval on interval:Daily/Weekly/MonthlyEnable auto-backups
/backup interval offDisable auto-backups
/backup interval showView current schedule

Creating Backups

Manual Backup

  1. Run /backup create
  2. Select components to backup
  3. Confirm creation
  4. Backup ID provided
Optional name: Add backup_name:My Backup to customize the name.

Component Selection

You can backup:

  • All Components - Everything in one backup
  • Individual Components - Choose specific items (roles, channels, etc.)

Backup Limits

  • 1 backup per server per user
  • New backups overwrite old ones for the same server
  • Compressed storage (minimal database load)

Restoring Backups

Prerequisites

Bot must have:
  • Highest role in server hierarchy
  • Administrator permission
These are required for successful restoration.

Restoration Process

  1. Run /backup load backup_id
  2. Select components to restore
  3. Review actions (deletions + creations)
  4. Confirm restoration
  5. Wait for completion (progress tracked)

What Happens During Restoration

Destructive Actions:

  • Existing roles → Deleted
  • Existing channels → Deleted
  • Existing emojis/stickers → Deleted
  • Existing threads → Archived

Then:

  • Selected backup components → Created/Restored
This cannot be undone. Always confirm you're restoring the correct backup.

Scheduled Backups

Setup

# Enable daily backups
/backup interval on interval:Daily

# Check schedule
/backup interval show

# Disable
/backup interval off

Intervals

  • Daily - Every 24 hours
  • Weekly - Every 7 days
  • Monthly - Every 30 days

Behavior

  • Scheduled backups overwrite previous ones (1 backup rule)
  • Backs up all components automatically
  • Runs in background
  • Timestamps tracked in /backup interval show

Permissions

Required User Permissions

ActionPermission
Create BackupAdministrator
View BackupsNone (own backups)
Restore BackupAdministrator
Delete BackupNone (own backups)
Scheduled BackupsAdministrator

Required Bot Permissions

  • Manage Roles
  • Manage Channels
  • Manage Server
  • Manage Emojis
  • Ban Members (to fetch bans)
  • Manage Threads
  • Manage Nicknames
  • Administrator (for restoration)

Best Practices

Before Restoring:
  1. Create a fresh backup of target server
  2. Verify bot has highest role + admin
  3. Disable protection bots temporarily
  4. Test in staging server first (if available)
  5. Inform members about downtime
Backup Strategy:
  • Manual backup before major changes
  • Enable scheduled backups (weekly recommended)
  • Keep backups organized with clear names
  • Regularly verify backup contents with /backup info

Troubleshooting


FAQ


Need help? Join our support server or check the FAQ.