Documentation menu
Getting started
New in v2.0
Feature deep dives
Reference
Backup & Clone
Encrypted Backups, Clone & Migration
AES-256-GCM encrypted configuration backups, historical message cloning with progress checkpoints, and zero-downtime data migration.
Verified against the checkout built for v2.2.4 · updated 20 Oct 2026
Overview
Managing production forwarding configurations requires robust disaster recovery, configuration portability, and the ability to backfill historical archives from source channels into new destinations.
AES-256-GCM Encrypted Backups
AutoTelegramForward exports user configurations as encrypted bundles using industry-standard authenticated encryption:
- Encryption Standard: AES-256-GCM with unique 96-bit initialization vectors.
- Key Derivation: PBKDF2-HMAC-SHA256 with 600,000 iterations and cryptographic salting.
- Scope: Exports all forward rules, filter lists, cleaner presets, and template variables without leaking raw session string secrets.
Historical Message Cloning
While standard forwarding processes incoming real-time updates, the Clone Engine backfills past channel history:
start_message_id to end_message_id• Checkpoint persistence: Resumes from last forwarded ID if worker is restarted
• Adaptive rate-limiting: Built-in 2-second sleep between requests to avoid Telegram flood limits
• Applies all Cleaner and Shortcode rules to cloned posts
Restoring Configuration
To restore an exported backup on a fresh installation:
- Upload the
.atfbakencrypted backup file to the Telegram bot or Web Dashboard. - Provide the decryption passphrase specified during creation.
- The system verifies the cryptographic GCM auth tag, decodes the rules, and imports them under your authenticated user ID.