Quick answer
Restore the smallest set that can produce a consistent working application. A single missing file may need selective recovery; changed code and data may need a matched set. Confirm what the available backup method replaces, preserve newer changes and test before a live overwrite.
Identify what is missing before choosing a restore
Identify the missing files or data, the last good time and changes since then. Inspect the candidate backup’s actual contents. A deleted image, damaged database and lost account require different recovery scopes.
This guide is a decision aid for an authorised account holder and application owner. It does not establish that a particular Novasean plan includes backups, a file browser or self-service recovery. Check the accepted service schedule and your actual panel permissions before treating any route as available. For a VPS image or Virtualizor backup, use the related VPS restore guide because replacing a whole virtual machine has different effects from a hosting-account restore.
Choose the smallest recovery scope that can meet the goal
One known file or folder
Recover the item into an isolated location, then replace only the verified target if the backup method and permissions allow it. Confirm its path, version and ownership, and check whether the application also changed its database or generated files. A single old file may be incompatible with newer code or data. Follow the single-file recovery procedure for the detailed steps and safeguards.
Site files and application data
Recover a matched file-and-database set from the same safe point, preferably on an isolated test target first. A file-only or database-only rollback can leave the application inconsistent; identify transactions or uploads made after the backup.
Several hosting-account components
Consider a selected-component or full-account restore under the operator’s approved plan. Confirm which domains, databases, mailboxes, settings and files are in the archive and which newer changes could be replaced.
A whole VPS
Use the authorised VM or application recovery process. A hosting-account archive and a VM image have different contents, owners and restore targets.
The narrowest scope is only safer when it can actually produce a consistent working application. Do not choose a file-only restore just to avoid downtime if the database or configuration also needs recovery.
Preserve changes made after the backup
Before any overwrite, record the selected backup timestamp and time zone, current site version, recent uploads, orders or other transactions, mailbox changes and important configuration. Where feasible and authorised, preserve a separate copy of the current state. Ask the application owner which later changes must be replayed or reconciled. Do not assume that “restore” removes every unwanted newer file or that it leaves unrelated data untouched; behaviour depends on the backup and restore method.
Agree the target, affected components, downtime, operator, validation owner and rollback plan before starting. A test restore should go to an isolated authorised destination and must not send production mail, webhooks or payments. Use the related isolated-restore guide for the rehearsal steps.
Check what your backup method can actually restore
DirectAdmin documents User-level Create/Restore Backups with selectable website, database, email and other components. That is component selection, not a promise that every installation can browse and restore one file through the panel. A separate backup product, application backup or operator-assisted extraction may offer finer recovery; verify its licence, scope and permission before relying on it. If only a full archive exists, ask the operator whether a controlled isolated restore or safe extraction can supply the required item without replacing the live account.
Check that the source backup includes both database settings and data when a database restore is needed, and that mail account settings and message data are not being confused. A DirectAdmin user-account backup does not necessarily contain server-wide configuration, external DNS, third-party mail, domain registration or SaaS data. A full-account action is not a substitute for separate recovery of those services.
Example: recover an image without rolling back orders
If one image was deleted while new orders continued, first look for a verified copy of that image and check its path and compatibility. A full-account rollback may replace newer orders or mailbox data unnecessarily. If the application’s database reference also changed, recover or reconcile that related state rather than assuming the file alone solves the loss.
If the panel only offers account components, do not assume it can browse individual files. Ask for an authorised isolated restore or controlled extraction route; confirm exactly what would be overwritten before choosing the action.
Restore through the authorised route and verify the result
- Confirm the exact source point, destination and selected components with the person who can approve data loss.
- Use only the recovery action available to your account, or ask Novasean support to perform the operator step under the agreed service. Stop at the confirmation screen if the scope or overwrite effect is unclear.
- Record completion or error status. After the restore, compare the target file or dataset with the expected version and test a representative page, login or read-only application task. Check mail only if mail was within scope.
- Confirm that newer legitimate changes have been preserved or reconciled, and that scheduled jobs, integrations, HTTPS and external DNS still point to the intended service. Retain the preserved current-state copy until the application owner accepts recovery.
A completed panel task is not proof of successful application recovery. If the restored copy fails validation, stop further overwrites and preserve the error and both states for diagnosis.
Ask for a scoped recovery plan when self-service is unclear
Give support the service and account identifier, the missing item or failing function, first failure time and time zone, candidate backup point, changes since that point, current availability, preferred isolated target and the application owner who will validate the result. Ask which restore scopes your service actually supports, what each would replace, whether an isolated extraction or test is possible, and who performs each step. Do not send passwords, private keys, raw customer data or a full backup archive through an ordinary ticket unless a secure transfer method has been agreed.
Should I restore the whole account to recover one image? First check whether the image can be recovered and verified separately. A full restore can affect newer data and unrelated components. Can I select only a database in DirectAdmin? DirectAdmin documents selectable database components, but your installed service and archive must support the needed action; confirm its effect before execution. Will a full account restore recover external DNS or a registrar account? No general promise can be made; identify those external owners and their separate recovery routes.
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.