A usable recovery point matters when a file is lost, an update fails or a website needs to be rebuilt. Zevonix provides encrypted off-site backups for covered sites; the schedule, retention and restore scope follow your Service Summary.
Identify what is covered, choose the recovery point and verify the restored site. A stored copy alone does not prove that every function works.
- Covered copies
- Recovery point
- Restore checks
Know what the backup contains
List the files, uploads, database and application settings needed to recover the working site. Also record dependencies such as external email, payment services and licences. A website backup does not automatically include those providers' data or account access.
For WordPress: a full recovery normally needs both the database and website files. The official WordPress backup guide explains the distinction.
Questions for your service record
- Which sites and data are covered, and when did the last usable backup complete?
- How often are copies taken, where are they stored, and how long are they retained?
- Can the requested file, site or database be recovered independently?
- Who can authorise a restore, and what validation is included?
Retention is a period during which copies are kept. It does not establish that every retained copy contains the data you need or a guaranteed recovery time. Backups are a recovery tool, not a long-term records archive.
Agree the restore before replacing data
- Describe the problem. Record when it began, the affected pages or functions and the last known working state.
- Select the recovery point. Confirm the available copy and the files or database that would be replaced.
- Account for newer activity. Identify orders, enquiries, uploads or content added since that point. Agree how they will be preserved or reconciled.
- Authorise and validate. Confirm the intended destination, approve the scoped work and test the recovered functions before closing the request.
A restore needs a functional check
Agree a test destination and an authorised check before an incident. Review important pages, media, logins, forms and application-specific functions. A completed copy job or a loading homepage alone does not establish that the whole service is usable.
For stores, avoid replacing a live order database with an older copy without a reconciliation plan. Read the store hosting guidance and staging checklist when planning a test.
What to include in a recovery request
Use the established customer support route. Provide the site, the symptom, the approximate time it started, the affected data and who can approve replacement. Share credentials only through an agreed secure process. Response coverage, additional work and any recovery targets need confirmation under the agreement.
Backup questions
How many days of backups are included?
Your Service Summary identifies the schedule and retention. Confirm the available recovery points for the specific site before relying on a particular date.
Is a restore guaranteed to lose no recent data?
No blanket zero-data-loss promise applies. The selected recovery point and activity since that copy determine what needs preservation or reconciliation.
Does this include a new backup purchase?
Backup care is part of the covered hosting service. Archive requirements, extra recovery work and any additional charges need an agreed scope.
Related planning guides
- Included care and extra technical work
- Migration and recovery planning
- Choosing a backup-retention policy
Review your backup and recovery needs
Tell us the public site URL, platform and the work you need. We will confirm the scope and responsibilities before quoting.
Ask about your site