Documentation

Backup & Restore

Surgical Restoration System™

Most bots respond to a nuke by wiping the server and rebuilding it from a template. Ember's Surgical Restoration System repairs only what an attacker actually damaged, leaving message history, untouched channels, and unaffected roles exactly where they were.

Restore Modes

Targeted vs. Full-Diff Restore

A targeted restore repairs only the entities Ember watched get damaged during an incident. A full-diff restore, run manually, compares the entire current server against a backup and shows you every difference before you confirm.

Incident Damage LedgerEXCLUSIVE

During an attack, Ember keeps an entity-level ledger of every deleted channel, created channel, renamed role, and permission change, plus a short pre-threshold buffer so the first couple of destructive actions still make it into the restore.

Restore Quiet Window

Ember doesn't fire a restore on the very first destructive event. It waits for a quiet period first. If the attacker keeps going, the timer extends, the incident stays open, and new damage merges into the same restore instead of the repair starting (and being undone again) mid-attack.

Restore Resilience

Mid-Restore Attack DetectionEXCLUSIVE

If destructive activity starts again while a restore is already running, Ember can stop the current restore state, retain what it's learned about the incident, account for the new damage, and re-arm restoration rather than finishing a repair that's already out of date.

Cross-Wave Incident MergingEXCLUSIVE

An attacker who strikes in multiple waves, including a second wave that arrives while Ember is still restoring the first, doesn't get to reset the clock. Accumulated damage information stays tied to one evolving incident across every interrupted restore cycle.

After a Successful Restore

Ember clears the attack state, purges messages the attacker sent (including through any webhooks they created), and takes a fresh system-generated recovery backup, labeled separately from your regular scheduled backups so you can tell the two apart.

What a Backup Contains

Server name & icon

@everyone permissions

Unmanaged roles & colors

Role permissions

Text & announcement channels

Voice & stage channels

Forum channels

Channel hierarchy & topics

NSFW state & rate limits

Permission overwrites

Custom emoji info

Category structure

Automatic backups run on a 24-hour cycle and are DMed to the server owner. Manual restores through &serverrestore always show a preview of the exact changes first and wait for confirmation before touching anything, with the ability to abort a restore partway through.

Command Reference

CommandSyntaxDescriptionPermissionsExample
&autobackup&autobackup [on|off] or /autobackupToggles the automatic 24-hour backup cycle. Snapshots are DMed to the server owner and stored for the Surgical Restoration System.Administrator&autobackup on
&serverbackup&serverbackup or /serverbackupTakes an immediate, complete JSON snapshot of roles, channels, categories, permission overwrites, and server metadata.Administrator&serverbackup
&serverrestore&serverrestore <attach backup.json> or /serverrestoreLoads a backup, previews the exact structural differences, and restores after confirmation. Supports abort mid-restore.Administrator&serverrestore (with file attached)