Backups & Recovery

Structural snapshots

Backups capture recoverable Discord structure including @everyone permissions, ordinary roles, supported categories/channels, channel settings and permission overwrites. Automatic structural backup passes run every 24 hours. The dashboard records snapshot age and contents.

Selective restore

Restore workflows use a preview/prepared plan, explicit confirmation, current-state validation and a pre-restore structural backup. This allows staff to restore selected structure instead of blindly overwriting an entire guild.

Full Server Recovery

For a replacement server, Bureaucramancer can rebuild the supported structural snapshot into a separate target server. The source server stays read-only, target-only roles/channels are preserved, managed bot/integration roles are remapped only when a safe matching managed role already exists, and an automatic verification pass records a persistent recovery report.

Member role assignments, server-level configuration, AutoMod rules, onboarding/Server Guide, server emoji/sticker libraries, webhook secrets and exact thread-object reconstruction are not currently claimed as automatically recovered. Member-specific permission overwrites can only be restored for users who have already joined the replacement server.

Message recovery

Archived message records can be reconstructed only when Bureaucramancer captured them before they became unavailable. Cross-server content replay is opt-in and recovered content is posted as labelled Bureaucramancer reconstruction output rather than impersonating the original Discord author.

Attachment Protection

When Attachment Protection succeeds, Bureaucramancer stores the actual file bytes in private object storage and tracks a verified object independently from the original Discord URL. Older, failed, oversized or reference-only attachments may still depend on the original Discord URL and are shown as exceptions in the dashboard.

The protected copy is designed to survive loss of the original Discord CDN object. Independent object-storage disaster recovery is a separate infrastructure control and is not implied merely because Attachment Protection succeeded.

What backups do not guarantee

Bureaucramancer cannot recover data it never received, inaccessible historical messages, files that were never successfully protected, people or integrations that have not joined the replacement server, or platform objects Discord no longer permits the bot to recreate. Server owners should test recovery on non-critical content before treating a workflow as operationally relied upon.

Database continuity

Bureaucramancer's production PostgreSQL data is separate from guild-level Discord snapshots. Infrastructure backup and point-in-time-recovery configuration must be verified and restore-tested independently before they are treated as a recovery guarantee. Guild snapshots protect Discord structure; database recovery protects Bureaucramancer's own stored records.