Establish what was deleted and what changed afterwards
Restore only the missing file from a known-good point after preserving changes made since that backup.
First identify the exact missing path and any changes made after the backup you might use. Note the exact domain, path, filename and deletion time. Ask the application owner whether the file was generated, uploaded by a user or part of a software release. A generated file may be safer to rebuild from its source; a customer upload may require a specific backup version. If many files or database records are affected, stop and plan a broader recovery instead of copying one item blindly.
Before restoring, preserve the current directory state through an authorised copy or backup. This matters because a full account restore can overwrite files, database rows or mail created since the older backup. Confirm which account and domain actually serve the path; do not guess from a folder named public_html if the site uses a customised document root.
Find the exact file in a separate backup copy
DirectAdmin documents user-level site backups and selectable backup components, but it does not promise a universal one-click restore for a single file. If your entitled account lets you download an authorised archive, extract it in a private local location outside the served website and inspect its paths. Choose the newest known-good copy from before deletion. Confirm its size, expected content, application version and any related assets. Treat an archive from another domain or an unknown source as untrusted.
If you cannot access a suitable archive or do not know whether the file belongs to the current release, ask support or the application maintainer to identify it. Do not restore an entire old database merely to recover one static file.
Replace only the missing path
Use the file manager or approved transfer route for the same entitled domain. Compare the live directory with the extracted backup before uploading. If a file with that name has reappeared, inspect its current version and ask the owner whether it contains newer work. Upload only the chosen missing file, preserving the required path and filename case. Where the file contains secrets or executable code, involve the application owner or operator to set the correct permissions; do not make it world-writable to resolve an access error.
Do not copy a whole directory over newer files, and do not put a private archive in the web root for convenience. Keep a record of the backup identifier and restored path so a later deployment does not unexpectedly replace it.
Test the affected function and recover if versions conflict
Open the affected page or function through the intended HTTPS hostname. Check one linked asset and the application log if the owner has authorised access. A restored file from an older release may call functions or database fields that no longer exist. If it causes errors, put back the pre-restoration current state for that path and ask the maintainer to rebuild a compatible version. Leave unrelated newer files and data untouched.
For example, replacing one deleted image should not roll back newer uploads or the database. Compare the target file and neighbouring timestamps, and stop if the archive restores a larger scope than intended.
Frequently asked questions
Why not use the panel’s full restore? A full restore may roll the entire account back to the backup date. It is a separate recovery decision when only one file is missing.
What if the backup has several copies? Match the domain, path, application release and last known-good time, rather than choosing solely by filename.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.