Backups

Premium backups capture Airwavy dashboard configuration and selected Discord server structure. Every applied restore requires a completed dry-run review first.

• Use the server owner account or an account with Manage Server, and confirm the server has active premium access.
• Make sure Airwavy can manage every role or channel that a restore may need to change.

1. Open Backups in the dashboard and create a fresh snapshot before a major change.
2. Label or identify the snapshot clearly, then inspect its recorded scope.
3. For a restore, run the dry-run diff first, review every proposed change, and only then confirm application.

• A server can retain up to 25 backup snapshots, each with a name of up to 100 characters.
• Configuration snapshots cover the supported dashboard feature settings.
• Full snapshots can additionally record manageable Discord roles and supported category, text, voice, announcement, stage, and forum channel structure with their permission overwrites.
• Integration-managed roles and other Discord-managed objects are excluded from structural restoration.

1. Choose whether to restore configuration, supported structure, or both, then enter the exact backup identifier as confirmation.
2. Run the required dry run and review the diff delivered to your Discord direct messages.
3. If the proposal is correct, apply it within the 15-minute approval window. If the window expires, run a new dry run.
4. Review the final direct-message report and Discord's Audit Log for skipped or partially applied changes.

• A completed snapshot appears in the server's backup list.
• A dry run reports intended changes without mutating Discord; a confirmed restore applies only the supported reviewed scope and sends its report by Discord direct message.