Provider backups are a recovery layer, not a substitute for customer-controlled business continuity.
Applies to: Service policies and customer responsibilities
This operational guidance complements Tudor Internet's formal terms and policies. Where there is a conflict, the current contract, product description and published legal terms take priority.
Before you start
- Confirm the active product or addon and the domain or user it protects.
- Record the current settings before changing them.
- Download anything that must be retained and confirm whether the action is reversible.
What you need to do
- Keep an independent backup of critical data.
- Verify backup status and restoration.
- Understand plan retention and exclusions.
- Take a fresh backup before major changes.
Confirm the result
- Website pages, database-driven functions and any affected email service are tested rather than assuming the operation completed correctly.
- A separate recovery copy and the rollback point are retained until the restored or migrated service is stable.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The restored site opens but behaves incorrectly. | Files and database were restored from different times, cached data is stale or configuration still points to the old location. | Align the restore points, clear application caches and verify URLs, credentials and scheduled tasks before declaring recovery complete. |
| Recent data is missing. | The selected recovery point predates the change or the data was stored outside the backed-up location. | Stop making further changes, identify the required timestamp and ask support what recovery points remain available. |
Important notes
- Destructive or ownership-changing actions may be irreversible and can have billing or data-retention consequences. Confirm the target and authority before proceeding.
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The customer account email address
- The affected invoice, service, domain or ticket number
- The exact message and the time it appeared
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Cancel an addon without losing required data or protection
- Keep a change and rollback record for production services
- Remove secrets and personal data from screenshots and logs
- Prepare safe diagnostics for a support ticket
- Report abuse or security concerns
Last reviewed: 2026-07-18.
