Prepare a precise recovery request so support can identify the right data and avoid replacing newer work unnecessarily. State what is missing, the desired recovery point and where the recovered copy should be placed.
IN THIS ARTICLE
01 Prepare the request
- Identify the product, service ID and affected account or website. Describe the exact item, folder, database or file path using the product's terminology.
- Record when the item was last known to be correct and when the problem was discovered, including the timezone. Mention any deletion, update or migration near that time.
- Preserve the current state where practical. Avoid repeated edits or cleanup that could overwrite evidence or remove recoverable versions.
- Check the product's Trash, version history or documented user recovery option. Record what was attempted and its result.
- Specify whether a separate recovered copy is preferred or whether replacement of current data is required. Identify any newer orders, messages or edits that must be preserved.
- Provide the business authorisation and scope needed for support to act. Ask which recovery points are available and what the restore will affect.
- After recovery, verify representative content and the affected workflow. Reconcile missing changes and correct the cause before resuming normal operation.
02 Example: request one file without replacing newer orders
A useful recovery request for an online store could say:
Service: the affected hosting service ID and domain
Missing item: /public_html/uploads/catalogue.pdf
Last known correct: 16:00 UTC on the stated date
Discovered missing: 09:00 UTC the following day
Requested result: recover an available earlier copy to a separate location
Preserve: current order database and all newer customer activity
Already checked: application Trash, current file location and recent changes
Replace the example path and times with your evidence. Ask which recovery points exist and whether the requested file can be restored selectively. After support provides a recovered copy, open it and confirm the expected catalogue before deciding whether to replace the live file. A whole-site restore is a separate decision with a wider effect.
Common questions
Can support recover anything ever deleted?
No. Recovery depends on available copies, retention and the product's capabilities. Report the issue promptly and request a specific available recovery point.
Should I restore the whole website for one missing file?
Ask whether a selective recovery is available. A whole-site restore can replace newer database or customer activity.
What evidence helps confirm success?
Use known messages, file versions, record counts or representative transactions. A successful job status is useful, but the recovered business data must also be checked.
Related articles
- Restoring website files or a database with CodeGuard
- Recovering a deleted or overwritten Google Drive file
- Recovering a deleted message in OX App Suite
- Choosing between mailbox retention, archiving and backup
- Using server snapshots alongside independent backups
- Questions to ask about data location before choosing a service