Untested backups
We restore the service in an agreed environment. We check the selected functions and record how long the test took.
We plan how to restore critical services and data. We test backups and check that services work. You get the test results and a plan for improvements.
We start with the services your business needs to operate. We review the data, access and dependencies needed to restore them.
We restore the service in an agreed environment. We check the selected functions and record how long the test took.
We select backups for Microsoft 365 or Google Workspace. We agree the accounts, shared resources and the recovery method for the chosen data.
We plan how to restore services elsewhere. We account for servers, networking, licences, access and the order of recovery.
We update the plan when services, providers or responsibilities change. Agreed tests check the environment your business uses today.
The scope depends on what needs to work after an outage. You can book a one-off test, commission a recovery setup or arrange ongoing support.
We prepare server or database backups. Recovery tests check the application and the restored data.
Tailored quote
Project, test or ongoing supportScope and cost agreed upfront
We agree backup and recovery for email, files and shared resources in Microsoft 365 or Google Workspace.
Tailored quote
Setup and selected ongoing supportLicences and data included in costing
We plan recovery in another environment. The plan covers resources, dependencies and access.
Tailored quote
Project and agreed readinessRecovery resources included in costing
The quote separates preparation, resources, licences, backup storage, tests and ongoing support. We confirm the full scope and cost before work begins.
If your CyberOnIT support agreement already covers backups or recovery, we account for that scope. We do not charge twice for the same protection, storage or work.
The report shows what we recovered and which functions worked. You receive a record of the test, its limitations and the next steps.
What needs to come back first?
We identify important services, their data, accounts and connections. We agree the recovery order and who will confirm that work can resume.
How current is the data?
We record when the selected backup was taken and which data was recovered. We compare the result with the agreed objective and identify anything that could not be restored.
Can the service be used?
We check agreed sign-in, read and write operations or another important task. Someone you nominate confirms they can complete the agreed task.
What needs attention?
We provide results, instructions and prioritised improvements. We distinguish completed tests from assumptions and define the scope of the next check.
We agree what to restore, where to run it and how much downtime your business can accept. Recovery objectives are confirmed for the selected environment.
| Scope | Servers and databases | Email and files | Recovery environment |
|---|---|---|---|
| Protected scope | System, application and data | Accounts and shared resources | Services and their dependencies |
| Recovery destination | Agreed server or test environment | Selected service or export | Another host or location |
| Result check | Startup and use of data | Recovery of agreed resources | Services and access brought online |
| Backup and test frequency | Matched to system needs | Matched to platform and scope | Matched to the agreed plan |
| Cost and responsibility | Agreed before work begins | Agreed before work begins | Agreed before work begins |
We agree services, data, dependencies, owners and approvers. We identify who is responsible for backups, storage, keys, access and confirming the result. Where another administrator or software vendor is involved, we record the division of responsibilities.
Before a test, we agree permitted actions, the recovery destination and the effect on business operations. Production configuration changes, pausing writes or switching users require the appropriate approval.
We match backup frequency, retention and capacity to the data and how it changes. We agree separation from production, encryption, access to keys and data deletion rules.
Protection against modifying or deleting backups is confirmed for the selected solution. We check separately whether deletion can be prevented. Running the restored service is a separate test from verifying backup files.
The plan covers data and the components required to run a service: its operating system, configuration, application, database and access. Backup methods are matched to the database engine and consistency requirements.
Point-in-time recovery requires suitable configuration and continuous log coverage. A machine backup alone does not establish that capability. We perform an agreed test before confirming it for the selected scope.
We identify the accounts, mailboxes, files, sites and shared resources to protect. We review existing features, licences, data location and delegated access.
We select a vendor-native solution or an external service. Application coverage, backup history and recovery options depend on the chosen product. A test confirms recovery of the selected data, not unlimited coverage of every cloud service.
We plan destination resources, networking, access, licences and the recovery sequence. We distinguish resources provisioned for a test from a recovery environment maintained on an ongoing basis.
The plan covers failover, failback and preservation of new data. We show readiness, replication and test costs separately. A backup stored on a backup server is not a running recovery environment.
We agree how far back the latest recoverable data can be (RPO) and the target time to restore the service (RTO). We measure the outcome for specified data, resources and conditions.
The report records the backup point, test sequence and duration, actions taken and application checks. An unmet target is recorded as a limitation with an improvement plan. One test result is not a guarantee for every outage.
We agree check frequency, tests, documentation updates and reporting channels within ongoing support. Starting incident work and completing recovery are separate parameters.
If hosting, database or another CyberOnIT agreement already covers the work, that scope applies. Additional readiness or work is agreed separately. We agree staff support hours separately, including when backup checks run automatically around the clock.
We show preparation, licences, destination resources, storage, tests and ongoing support separately. We include overlapping environments, transfer and software vendor involvement where required.
We hand over the agreed documentation, test results and recovery instructions. Export, retained copies, data retention and access removal are agreed before the engagement starts.
We identify services and dependencies. We review backups and agreements. We agree the goal, scope and quote.
We prepare backups or use the ones you have. We restore the agreed data and check that the service works.
We explain results and limitations. We provide guidance and improvements. We agree further tests or support.
No. We can assess and test existing backups and work with your administrator. We first agree access, responsibilities and the capabilities of the current solution.
Yes. You can commission an agreed recovery test and report without an ongoing subscription.
Before the test, we confirm the data, destination environment, permitted actions and cost.
We need somewhere to run the service, its configuration, access and working connections to other systems. We test an agreed task in the restored service.
That depends on the recovery point, protection method, data volume and recovery destination. We agree objectives before work and compare them with test results. A specific commitment requires an agreed scope and conditions.
We do not charge twice for activities or resources already covered by the same agreement.
Additional scope, such as another location, longer backup history or an extended recovery test, is quoted separately.
We check whether we can take on the work and what backups are available. We agree the first stage and budget before work begins.
Existing CyberOnIT customers should use the reporting channel and terms in their support agreement.
Tell us which systems you depend on and whether you have backups. We will agree what to protect, how to recover it and how to check the result.
Discuss your recovery plan