Removing old archives can recover account disk space, but a backup should be deleted only after its retention value is understood. Keep a verified off-server copy when the archive is still part of your recovery plan.
IN THIS ARTICLE
Prepare for the change
Identify the archive by account, date and scope. Confirm no backup or restore job is currently writing or reading it. Check that a newer usable backup exists; a new queued job is not yet a replacement.
01 Delete an obsolete DirectAdmin backup archive
- Open System Info & Files > File Manager and locate the account backup directory, commonly
backups. - Compare the exact filename and modification date with your backup record. Avoid selecting application directories or every archive at once.
- Download any copy that must be retained to independent storage and verify that it is complete before continuing.
- Select the obsolete archive and choose the file-removal action. Read whether the panel will use a trash area or permanently remove it, and confirm only the intended file.
- Refresh the directory and review disk usage after the panel accounting has updated. A trash copy may still consume space until it is safely cleared.
How do I confirm the obsolete backup was removed safely?
Confirm the intended archive is gone and the backups you still need remain readable. Make sure there is enough working space for the next backup job, not merely enough for its final compressed file.
If the change does not work
If space is not recovered, inspect trash retention and account usage rather than deleting more files at random. If an archive is unexpectedly in use or removal is denied, check the running jobs and ask support. Deleting a backup archive does not repair a failed backup schedule; investigate the failure separately.