10-11-2026, 05:39 PM
What this guide does
Create a backup plan for aaPanel Mail Server, run it immediately, and check that an archive was actually produced. This protects mailbox messages before maintenance or migration.
Tested on the AdminsForum lab
aaPanel 8.0.6 on Ubuntu, with Mail Server installed. We saved a weekly plan, ran the task once, and verified the completed archive. We did not restore over existing mailboxes. Screenshots below show the actual lab result.
Before you begin
1. Open the mail backup page
Click Mail Server → Other Settings → Backup. This is the Mail Server backup page, not the website backup page. Look for Backup Plan, Open Backup, the schedule fields and Mail import.
2. Choose the schedule and retention
Turn on Open Backup. For the lab demonstration we selected:
AdminsForum lab screenshot — saved plan and the generated archive
![[Image: mail-backup-result-20261011.png?v=copyright1]](https://adminsforum.com/images/tutorials/mail-backup-result-20261011.png?v=copyright1)
3. Run a backup now
Open Cron from the left menu. Find [Do not delete] Mail server data backup task. Check its destination, retention and execution cycle. Click Execute in that row, then confirm. This starts a real backup immediately; you do not need to wait until the next scheduled time.
Wait for completion. The word Running in the task list indicates the task is enabled; it is not proof that a backup completed successfully.
4. Read the backup log
Open the task's Log. Look for the source directory, available disk space, compression result, destination filename, and a completion message. Our lab log reported:
These sizes are examples from a small lab mailbox. Your sizes will differ. A log reporting an error, an empty output file, or only a start time is not a successful backup.
AdminsForum lab screenshot — successful execution log
![[Image: mail-backup-log-20261011.png?v=copyright1]](https://adminsforum.com/images/tutorials/mail-backup-log-20261011.png?v=copyright1)
5. Check and keep an off-server copy
Return to Mail Server → Other Settings → Backup. In our tested version the generated archive appeared under Mail import, with Restore and Delete actions. Check its timestamp and filename against the task log.
Use aaPanel Files to open the exact directory shown in your log. Download the archive to secure storage outside the VPS. Backups contain private email, so do not put them in a public website directory or attach them to a forum post. Check that the downloaded file has a sensible size and can be opened/listed as an archive.
What is covered?
The backup task in this demonstration archived /www/vmail. This is not evidence of a full-server backup. Separately record or back up your mailbox/domain configuration, mail service settings, DNS records, certificates and other required recovery material. Do not assume a mail-data archive alone can recreate every part of a new server.
6. Understand the recovery controls
The page provides Upload from local and Select in server for importing a backup, and a Restore action for the listed archive. Before using them, keep a current backup and test on a separate disposable server. Confirm that the target has compatible Mail Server software and the correct mailbox/domain setup. Importing old mail into live accounts can affect existing data; this guide does not claim a completed restore test.
7. Stop a demonstration schedule
If you only created the schedule for practice, return to the Mail Server backup page, turn off Open Backup and save. Check the corresponding Cron task is paused. Keep the successful archive. On our lab we disabled the temporary plan after testing.
Common problems
Verification checklist
Reference: aaPanel Mail Server documentation. Labels may differ between versions. For help, post your aaPanel version and the relevant error lines in Support & Troubleshooting; remove mailbox contents and credentials first.
Create a backup plan for aaPanel Mail Server, run it immediately, and check that an archive was actually produced. This protects mailbox messages before maintenance or migration.
Tested on the AdminsForum lab
aaPanel 8.0.6 on Ubuntu, with Mail Server installed. We saved a weekly plan, ran the task once, and verified the completed archive. We did not restore over existing mailboxes. Screenshots below show the actual lab result.
Before you begin
- Sign in to aaPanel as an administrator and confirm that Mail Server is installed.
- Check free disk space. Allow room for the existing mail data, a temporary archive, and retained backups.
- Decide how much mail you can afford to lose. A weekly backup can leave up to a week of new messages unprotected; busy mailboxes usually need more frequent backups.
- Keep a second copy on another server or storage account. A backup on the same disk cannot protect you from losing that VPS or disk.
1. Open the mail backup page
Click Mail Server → Other Settings → Backup. This is the Mail Server backup page, not the website backup page. Look for Backup Plan, Open Backup, the schedule fields and Mail import.
2. Choose the schedule and retention
Turn on Open Backup. For the lab demonstration we selected:
- Period: Weekly.
- Day: Monday.
- Time: 01:30, using the server's schedule/time settings.
- Backup to: Disk of server.
- Keep last: 3 copies.
AdminsForum lab screenshot — saved plan and the generated archive
3. Run a backup now
Open Cron from the left menu. Find [Do not delete] Mail server data backup task. Check its destination, retention and execution cycle. Click Execute in that row, then confirm. This starts a real backup immediately; you do not need to wait until the next scheduled time.
Wait for completion. The word Running in the task list indicates the task is enabled; it is not proof that a backup completed successfully.
4. Read the backup log
Open the task's Log. Look for the source directory, available disk space, compression result, destination filename, and a completion message. Our lab log reported:
Code:
Backup directory: /www/vmail
Directory size: 213.22 KB
Compressed archive: 13.05 KB
Saved under: /www/backup/path/vmail/
Backup is completeAdminsForum lab screenshot — successful execution log
5. Check and keep an off-server copy
Return to Mail Server → Other Settings → Backup. In our tested version the generated archive appeared under Mail import, with Restore and Delete actions. Check its timestamp and filename against the task log.
Use aaPanel Files to open the exact directory shown in your log. Download the archive to secure storage outside the VPS. Backups contain private email, so do not put them in a public website directory or attach them to a forum post. Check that the downloaded file has a sensible size and can be opened/listed as an archive.
What is covered?
The backup task in this demonstration archived /www/vmail. This is not evidence of a full-server backup. Separately record or back up your mailbox/domain configuration, mail service settings, DNS records, certificates and other required recovery material. Do not assume a mail-data archive alone can recreate every part of a new server.
6. Understand the recovery controls
The page provides Upload from local and Select in server for importing a backup, and a Restore action for the listed archive. Before using them, keep a current backup and test on a separate disposable server. Confirm that the target has compatible Mail Server software and the correct mailbox/domain setup. Importing old mail into live accounts can affect existing data; this guide does not claim a completed restore test.
7. Stop a demonstration schedule
If you only created the schedule for practice, return to the Mail Server backup page, turn off Open Backup and save. Check the corresponding Cron task is paused. Keep the successful archive. On our lab we disabled the temporary plan after testing.
Common problems
- No archive appears: run the correct mail backup task and inspect its log; saving a plan does not immediately create a backup.
- Disk full or inode error: free space safely or move verified old backups off-server before trying again.
- Backup exists but messages are missing after recovery: check the backup date, mailbox mapping and recovery log. Do not overwrite your only copy while experimenting.
- Different time in the UI and log: check server and browser timezone settings; compare the actual file timestamp as well.
Verification checklist
- Backup settings persisted after saving.
- The correct task executed and its log ended successfully.
- A timestamped, non-empty archive exists.
- An off-server copy is secured.
- A separate recovery rehearsal is planned before relying on the backup.
Reference: aaPanel Mail Server documentation. Labels may differ between versions. For help, post your aaPanel version and the relevant error lines in Support & Troubleshooting; remove mailbox contents and credentials first.