Skip to content
Zero Degree Documentation

Server Backups & Snapshots

Imagine the worst-case scenario: a rogue administrator deletes every channel and role in your server. Without a backup, months or years of work could vanish in seconds. Zero Degree Backups is your insurance policy—a powerful tool that records your server’s entire DNA so you can rebuild instantly.

💾 How Backups Work

Section titled “💾 How Backups Work”

A backup is a “snapshot” of your server at a specific point in time. It doesn’t save messages (due to Discord privacy and technical limits), but it saves everything else:

  • Category & Channel Structure: All names, positions, and topics.
  • Permissions: Every single role-overwrite for every channel.
  • Roles: Names, colors, and permissions (excluding the bot’s own role).
  • Server Settings: Region, verification level, and more.

🕹️ Managing Your Snapshots

Section titled “🕹️ Managing Your Snapshots”
  • /backup create: Captures your server’s current state. We recommend doing this after any major reorganization.
  • /backup list: Displays all saved snapshots for your server.
  • /backup info <id>: Dive deep into what a specific backup contains before you decide to restore it.

🚨 Restoring Your Server

Section titled “🚨 Restoring Your Server”

The /backup restore <id> command is the most powerful tool in ZeD’s arsenal. It is designed for total recovery.

[!CAUTION] Restoration is a Destructive Action! When you start a restoration:

  1. ZeD will wipe all existing channels and roles to create a blank canvas.
  2. It will then recreate the entire structure from your snapshot.
  3. This process cannot be stopped or reversed once confirmed.

Safety First

Section titled “Safety First”

Because restoration is so impactful, we’ve built in multiple safety layers:

  • Admin Only: Only users with the Administrator permission can trigger a restore.
  • Double Confirmation: You must click a “Confirm Restoration” button after running the command.
  • Role Hierarchy: ZeD can only restore roles that are below its own role in the hierarchy.

💡 Best Practices

Section titled “💡 Best Practices”
  • Periodic Backups: Create a new backup once a month or after any major staff change.
  • The “Staging” Trick: If you’re unsure about a backup, invite ZeD to a blank test server and run the restore there first to see exactly how it looks.
  • Keep it Clean: Use /backup list to find old snapshots and delete them if they are no longer relevant.

Next: The Logging Engine - Watching everything