Design backup jobs, retention and restore checks around the data and business workflows you need to recover.
Start with a plan below, or talk to us about a custom setup.
Resources, deliverables and commercial terms confirmed against your requirements.
Commitment and billing term confirmed in quotation
Applicable taxes, software licences, migration, backups and management unless expressly included.
Choose backup & recovery around a measured workload and a clear operating model.
Organisations that need a documented approach to protecting application files and databases.
Teams reviewing how to rebuild an environment and validate the restored application.
Businesses assessing dependencies, recovery priorities and authorised restore decisions.
The quotation records the available options and the exact supplied configuration.
| Requirement | What to review |
|---|---|
| Protected data | Files, databases, configuration and required external dependencies. |
| Frequency | Choose jobs around acceptable data loss and workload behaviour. |
| Retention | Define recovery points, deletion and storage growth. |
| Storage | Confirm location, separation, access and encryption options. |
| Restoration | Specify restore tasks, validation and authorised contacts. |
| Testing | Agree a test environment and evidence of application recovery. |
Separate the core service from work and software that need an additional agreement.
The server configuration or professional service described in the quotation. Confirm access, operating system and the agreed deliverables.
Migration, backup administration, monitoring, management and additional software need a separately agreed scope and price.
Confirm taxes, setup charges, licensing, commitment, renewal and cancellation. Availability, workload location and support commitments belong in the quotation.
Ask which business records matter most and how much recent data the organisation could afford to recreate. Identify application owners who can validate a restoration. These questions help choose backup frequency and retention without treating an arbitrary number of days as a recovery plan. A database and a folder of uploaded files may need a coordinated recovery point. Record the assumptions and revisit them when the application or data volume changes.
A copy that follows every deletion or corruption immediately may not provide a usable earlier state. Review how backup jobs retain recovery points, who can delete them and how the storage is accessed. Include configuration and rebuild instructions where they are needed to restart the service. Storage separation and protection options depend on the agreed setup. They must be confirmed rather than assumed from the word backup on a plan card.
Choose a controlled environment for a restore test and check the application with its owner. Confirm that the restored files, database, credentials and dependencies work together. Record what was restored, which recovery point was used and which checks passed. The result informs a realistic recovery discussion; it is not a promise that every future incident will meet the same timing. Agree how jobs, failures and storage growth are reviewed afterwards.
The management proposal lists the environments and tasks that CloudLelo will administer. It should identify monitoring checks, maintenance approval, patching windows, backup administration and incident escalation. Your team retains responsibility for application changes, business data, access approvals and decisions about acceptable interruption. An agreed scope is essential: server management does not automatically include application development, software vendor support or unlimited incident work.
A task is assigned to CloudLelo only when it appears in the agreed management scope.
| Task | Customer / self-managed | Scoped CloudLelo management |
|---|---|---|
| Configuration | Define and administer the environment | Perform agreed configuration tasks |
| OS / account updates | Plan, test and apply required changes | Apply agreed changes in approved windows |
| Monitoring | Select checks and respond to alerts | Operate the specified checks and escalation |
| Backup administration | Arrange jobs, retention and recovery testing | Administer the agreed backup jobs and restore tests |
| Applications and data | Own code, data and business validation | Application work only where explicitly included |
| Support scope | Provide authorised contacts and useful incident detail | Follow the agreed channels and service boundaries |
Deployment dates, service commitments and acceptance criteria are agreed for your project.
List applications, versions, dependencies, usage and authorised contacts. Identify protected data and the business owner who can validate deployment.
Confirm resources, software, access, transfer, fees and the administration scope. Record commitments and exclusions before approving the quotation.
Agree migration or deployment, backup checks and acceptance tests. Define the rollback decision and retain source access until handover criteria are met.
Document credentials, ownership and escalation contacts. Review resource use, maintenance and recovery arrangements as the workload changes.
Understand the configuration and responsibilities before requesting an order.
No. The quotation must identify the protected data, backup schedule, retention and restore responsibilities.
No. A restore test must validate the data and application dependencies in a controlled environment.
Storage location, separation, access controls and available protection options are confirmed in the service scope.
The quotation identifies resources or subscriptions, selected operating work, taxes, licences and commercial commitments. Consulting and provider consumption charges are reviewed separately.
Describe the application or provider, current setup, users, data size and intended change. Avoid passwords, private keys and confidential business records.
Confirm protected data, frequency, retention, storage location and restore responsibilities separately. Provider retention features do not automatically establish an independent backup arrangement.
The approved scope lists tasks, channels, escalation and maintenance responsibilities. Any support hours or response commitments must be agreed for the service.
Changes depend on availability, software and commercial commitments. Review potential interruption, data, licences and costs before approving a resource or subscription change.
From a new server to an existing application migration, start with your workload and leave with a clearly defined scope.