Backup System
The backup system allows you to create complete backups of your server and restore them when needed.
What is a Backup?
A backup is a complete copy of your server that includes:
- 💬 All messages (with original avatars and names)
- 📁 All channels and categories
- 👤 All roles
- 😀 All emojis
- 📋 Server settings
Suppose your server has 100 channels, 50 roles, and 10,000 messages. If something goes wrong (for example, someone deletes everything), you can restore everything from the backup.
Create a Backup
Using Commands
/backup create
The bot will start creating the backup. This may take several minutes depending on your server size.
The bot sends you a private message
You will see the progress in real-time in your private messages with the bot.
The bot collects all information
Collects messages, channels, roles, emojis, etc. This may take time.
You receive a unique ID
When finished, you will receive a unique ID (for example: abc123-def456-ghi789). Save this ID, you will need it to restore.
List Backups
/backup list
Shows all available backups with their IDs, dates, and sizes.
View Backup Information
/backup info backup_id:abc123-def456-ghi789
Shows detailed information about a specific backup.
Restore a Backup
Important: Restoring deletes existing content
- Deletes ALL existing channels (except the log channel)
- Deletes ALL existing roles (except @everyone and bot roles)
- Creates new channels and roles based on the backup
- Restores all messages using webhooks (to maintain original names and avatars)
Use this only if you are sure you want to replace everything.
Steps to Restore
Get the backup ID
Use /backup list to see your backups and copy the ID of the one you want to restore.
Execute the restore command
/backup restore backup_id:abc123-def456-ghi789
Note: You must execute this command in the server WHERE you want to restore (it can be different from the original server).
Confirm the restoration
The bot will ask for confirmation because this will delete existing content.
Monitor progress
The bot will send you updates in private messages showing the restoration progress.
Member notifications
When finished, the bot will send a private message to all members of the ORIGINAL server with an invitation to the new server where the backup was restored.
Partial Restoration (Restore Partial)
Partial restoration allows you to restore only missing elements from a backup without deleting existing content on your server. It is ideal when you only need to recover some roles, categories, or channels that were accidentally deleted.
- Full Restoration (/backup restore): Deletes EVERYTHING and restores EVERYTHING from the backup
- Partial Restoration (/backup restore-partial): Only restores what is missing, keeps what already exists
What does partial restoration restore?
Partial restoration analyzes your current server and compares it with the backup to identify and restore only:
- 👤 Missing roles - Roles that existed in the backup but not in the current server
- 📁 Missing categories - Categories that existed in the backup but not in the current server
- 💬 Missing channels - Channels that existed in the backup but not in the current server
When to use Partial Restoration
Use partial restoration when:
- ✅ Someone accidentally deleted some channels or roles
- ✅ You want to recover specific elements without losing current content
- ✅ Your server has new content you don't want to lose
- ✅ You only need to restore the structure (roles, categories, channels) but not messages
Steps for Partial Restoration
Get the backup ID
Use /backup list to see your backups and copy the ID of the one you want to use for partial restoration.
Execute the partial restore command
/backup restore-partial backup_id:abc123-def456-ghi789
Note: You must execute this command in the server where you want to restore the missing elements.
The bot analyzes the server
The bot will compare your current server with the backup and show you a summary of what is missing:
- Number of missing roles
- Number of missing categories
- Number of missing channels
Automatic restoration
If there are missing elements, the bot will start restoring them automatically. You will see the progress in real-time.
Result
When finished, you will receive a summary of what was restored. If there were no missing elements, the bot will inform you that everything already exists on the server.
Suppose your server had 50 channels and someone accidentally deleted 5 of them. With partial restoration, the bot:
- Will detect that those 5 channels are missing
- Will restore them with their original structure
- Will keep the other 45 channels intact
Note: Messages from those channels will not be automatically restored. To restore messages, use full restoration.
Automatic Scheduled Backups
You can configure the bot to automatically create backups at regular intervals. This ensures you always have a recent backup without having to remember to do it manually.
Enable Scheduled Backups
/backup schedule-enable
This activates the scheduled backup system for your server.
Configure Interval
You can configure how often backups are created:
/backup schedule-interval intervalo:daily/backup schedule-interval intervalo:weekly/backup schedule-interval intervalo:monthly
Available options:
- hourly - Every hour
- daily - Daily (once per day)
- weekly - Weekly (once per week)
- monthly - Monthly (once per month)
Configure Execution Time
For daily, weekly, or monthly backups, you can configure the exact time they will execute:
/backup schedule-time hora:02:00/backup schedule-time hora:14:30
docs.sections.backup.scheduledTimeFormat
Configure Day (for Weekly or Monthly)
For weekly backups: Configure the day of the week (0 = Sunday, 1 = Monday, ..., 6 = Saturday)
docs.sections.backup.scheduledDayCommand
For monthly backups: Configure the day of the month (1-31)
docs.sections.backup.scheduledDayCommand
Configure Number of Messages per Channel
/backup schedule-messages mensajes:100
This configures how many messages per channel will be saved in each automatic backup (1-1000).
View Configuration Status
/backup schedule-status
Shows the current status of scheduled backup configuration, including the interval, scheduled time, and when the next backup will be.
Disable Scheduled Backups
/backup schedule-disable
This disables the scheduled backup system. Manual backups will continue to work normally.
Configuration from Web Panel
docs.sections.backup.scheduledWebDesc
- Go to web panel → Your server → Settings
- Find the "Backups" section
- Enable "Scheduled Backups"
- Configure the interval and time
- Changes are saved automatically
🔄 Automatic Restoration
The automatic restoration system allows the bot to automatically restore channels and roles deleted during raids, comparing them with the most recent available backup. This system is designed to protect your server against bot attacks that massively delete channels and roles.
- Name-based search: Restoration searches for channels and roles by name instead of ID
- Tracking system: Records all deletions and restores when the limit is reached
- Complete restoration: Restores ALL elements deleted by the user, not just the last one
- Integrated protections: Does not restore elements deleted by the bot or whitelisted users
How It Works?
The system works as follows:
Deletion Tracking
When a user deletes a channel or role, the bot records it in the tracking system. It does NOT restore yet.
Enable Automatic Restoration
Use the following command to enable or disable automatic restoration:
/backup auto-restore estado:enable
Restoration When Limit is Reached
When the user reaches the limit configured in anti-raid protections, the bot executes the action (ban/kick/etc.) and restores ALL channels/roles deleted by that user.
Configuration from Web Panel
You can also configure automatic restoration from the web panel:
- Go to web panel → Your server → Settings
- Navigate to the "Backup" tab
- Find the "🔄 Automatic Restoration" section
- Check/uncheck the "Enable Automatic Restoration" option
System Behavior
The automatic restoration system has intelligent behavior:
Suppose the channel deletion limit is set to 2:
- User deletes channel "general" → Recorded, counter: 1/2, NOT restored
- User deletes channel "announcements" → Recorded, counter: 2/2, NOT restored
- User deletes channel "rules" → Counter: 3/2, ACTION EXECUTED and ALL 3 CHANNELS RESTORED
- The bot searches for each channel in the most recent backup and restores it with all its properties
- Requires a backup: Without a backup, there is nothing to restore
- Name-based search: If a channel/role changed name after the backup, it may not be found
- Only restores when limit is reached: Does not restore immediately, only when anti-raid action is executed
Requirements
For automatic restoration to work, you need:
- ✅ At least one backup created previously (manual or automatic)
- ✅ Anti-raid protections enabled (anti_channel_delete or anti_role_delete)
- ✅ Automatic restoration enabled in settings
Delete Backups
You can delete backups from the web panel:
- Go to web panel → Your server → Backup
- Find the backup you want to delete
- Click "Delete"
Use Cases
- ✅ Server migration - Move everything to a new server
- ✅ Recovery after an attack - Restore after someone destroyed the server
- ✅ Periodic backup - Create regular backups for security
- ✅ Cloning - Create an exact copy of the server
Frequently Asked Questions
How long does it take to create a backup?
Depends on server size. A small server (100 channels, 1000 messages) may take 2-5 minutes. A large server may take 10-30 minutes or more.
Do restored messages look the same as the originals?
Yes, messages are restored using webhooks, which means they maintain the original user's name and avatar. You won't see "Bot sent this", you'll see "User123 sent this" as if it were the original user.
Can I restore a backup to a different server?
Yes, you can restore a backup to any server where the bot has administrator permissions.
What happens to server members?
Members are not automatically restored (Discord does not allow this). However, the bot will send invitations to all members of the original server to join the new server.