10-10-2026, 07:11 PM
Quick answer
In aaPanel Free Edition, open Website → PHP Project, find your domain, and click its Backup / Restore entry. Check the configured backup type, click Backup, and wait for completion. Keep an off-server copy and test recovery on a disposable site.
Website files and database are separate
Our lab's backup configuration was Only Site File → Local Server. This backs up site files, not the application's database. Pair it with a database backup. Do not assume every backup labelled Website contains both.
1. Open the website backup dialog
Go to Website → PHP Project. Find the correct domain and check its description. Click the Backup / Restore entry; for a new site this can read 0 Backup. Dismiss the optional first-use help wizard if it blocks the controls.
2. Check the backup configuration
Read the Current configuration line before starting. In this tested guide it was Only Site File stored on Local Server. Other configurations may behave differently. Record what is included and where it is stored. Ensure enough free disk space for the backup and restoration.
3. Create the backup
Click Backup and wait for the task to complete. Confirm the archive appears with its file size, time, backup type and storage destination. Our small lab site produced a ZIP archive; actual sizes vary.
![[Image: attachment.php?aid=23]](https://adminsforum.com/attachment.php?aid=23)
AdminsForum tutorial lab: aaPanel reports the website backup completed successfully.
4. Keep a copy outside the server
Use the archive's Download action and confirm the transfer completed. Keep the file securely off the VPS. Website archives may contain configuration secrets and private uploads; never post a production archive publicly. A local backup will not protect against losing the entire server.
5. Test restoration on a disposable site
For a real application, restore into an isolated test setup before trusting the backup. In our dedicated lab we created a harmless text file containing a known value, made the backup, changed that file, and restored the archive.
Restore can replace current files and interrupt service. In our test the website briefly returned HTTP 403 while its directory was being restored, then returned HTTP 200 after completion. Plan a maintenance window for a live site and do not treat the temporary state as a completed restore.
6. Check the result
Verify a known file or upload, the homepage, application login and important functions. Restore the corresponding database when needed, using a consistent recovery point. Website files alone do not restore a database-backed application fully.
What we tested
On 10 October 2026, aaPanel Free Edition 8.0.6 created an Only Site File backup for our dedicated lab domain. We copied the archive to a separate computer, changed a disposable test file and restored through the panel. Both a filesystem check and an HTTPS request confirmed the original text returned. The homepage returned HTTP 200 after recovery.
Common questions
Is this a VPS snapshot?
No. This backup does not capture the whole operating system or all server settings.
Does this set up scheduled backups?
No. The dialog has a separate Schedule & Remote Storage section. A reliable schedule also needs retention, off-server storage, monitoring and restore testing.
Should I leave backup archives in the website root?
No. Keep backups outside publicly served folders and protect them appropriately.
What if the application still fails after files are recovered?
Check the database recovery point, PHP version and extensions, environment settings, file permissions and logs. File recovery alone may not undo application/database changes.
Related guides
Back up and restore a database in aaPanel Free Edition
Change PHP 8.3 to 8.5 in aaPanel Free Edition
In aaPanel Free Edition, open Website → PHP Project, find your domain, and click its Backup / Restore entry. Check the configured backup type, click Backup, and wait for completion. Keep an off-server copy and test recovery on a disposable site.
Website files and database are separate
Our lab's backup configuration was Only Site File → Local Server. This backs up site files, not the application's database. Pair it with a database backup. Do not assume every backup labelled Website contains both.
1. Open the website backup dialog
Go to Website → PHP Project. Find the correct domain and check its description. Click the Backup / Restore entry; for a new site this can read 0 Backup. Dismiss the optional first-use help wizard if it blocks the controls.
2. Check the backup configuration
Read the Current configuration line before starting. In this tested guide it was Only Site File stored on Local Server. Other configurations may behave differently. Record what is included and where it is stored. Ensure enough free disk space for the backup and restoration.
3. Create the backup
Click Backup and wait for the task to complete. Confirm the archive appears with its file size, time, backup type and storage destination. Our small lab site produced a ZIP archive; actual sizes vary.
AdminsForum tutorial lab: aaPanel reports the website backup completed successfully.
4. Keep a copy outside the server
Use the archive's Download action and confirm the transfer completed. Keep the file securely off the VPS. Website archives may contain configuration secrets and private uploads; never post a production archive publicly. A local backup will not protect against losing the entire server.
5. Test restoration on a disposable site
For a real application, restore into an isolated test setup before trusting the backup. In our dedicated lab we created a harmless text file containing a known value, made the backup, changed that file, and restored the archive.
- Open the correct site's Backup / Restore dialog.
- Identify the intended archive and its date.
- Click Restore.
- Read the confirmation carefully. Our panel displayed Will be restoring the site files and database, continue?, even though the archive type was Only Site File. Check the actual backup type rather than inferring its contents from this generic warning.
- Confirm only after protecting current data and planning downtime.
- Wait for the recovery task to finish and inspect its log.
- Verify the recovered files, ownership/permissions, HTTPS site and application behavior.
Restore can replace current files and interrupt service. In our test the website briefly returned HTTP 403 while its directory was being restored, then returned HTTP 200 after completion. Plan a maintenance window for a live site and do not treat the temporary state as a completed restore.
6. Check the result
Verify a known file or upload, the homepage, application login and important functions. Restore the corresponding database when needed, using a consistent recovery point. Website files alone do not restore a database-backed application fully.
What we tested
On 10 October 2026, aaPanel Free Edition 8.0.6 created an Only Site File backup for our dedicated lab domain. We copied the archive to a separate computer, changed a disposable test file and restored through the panel. Both a filesystem check and an HTTPS request confirmed the original text returned. The homepage returned HTTP 200 after recovery.
Common questions
Is this a VPS snapshot?
No. This backup does not capture the whole operating system or all server settings.
Does this set up scheduled backups?
No. The dialog has a separate Schedule & Remote Storage section. A reliable schedule also needs retention, off-server storage, monitoring and restore testing.
Should I leave backup archives in the website root?
No. Keep backups outside publicly served folders and protect them appropriately.
What if the application still fails after files are recovered?
Check the database recovery point, PHP version and extensions, environment settings, file permissions and logs. File recovery alone may not undo application/database changes.
Related guides
Back up and restore a database in aaPanel Free Edition
Change PHP 8.3 to 8.5 in aaPanel Free Edition