The service lifecycle

Every engagement fits one of five phases — most customers use several.

01

Assess

Health checks, architecture assessments and capacity reviews.

02

Build

Implementation, upgrade and migration projects.

03

Operate

Managed monitoring, administration and reporting.

04

Recover

Emergency assistance and recovery coordination.

05

Automate

API integration, workflows and custom development.

Assess

Advisory and Architecture

For teams planning a new, larger or modernised backup platform: we assess where you are, size where you are going, and design the architecture in between.

Current-state assessment

Configuration, capacity, job history and recovery posture — documented, not assumed.

Target architecture design

An architecture that fits your workloads, growth and recovery objectives.

Capacity and performance planning

Sizing for backup windows, restore throughput and data growth.

Recovery and resilience design

RPO/RTO targets translated into copy strategy, retention and drill design.

Technology evaluation

Platform options compared against your requirements — with the trade-offs written down.

Implementation roadmap

A sequenced plan with prerequisites, risks and dependencies.

How it runs

Workshops with your infrastructure, application and compliance teams, followed by structured analysis and design sessions. Findings are validated against your actual job history and restore records.

What you receive

Architecture documentation, a risk register, capacity models, an implementation roadmap and a management summary.

Build

Implementation and Migration

Turning design into a production environment: installation, upgrade, refresh and migration projects with change control and rollback plans.

Platform installation and configuration

New environments installed, hardened and documented from day one.

Version upgrade

Release planning, compatibility checks, rollback plans and post-upgrade validation.

Hardware or storage refresh

Media server and storage migration without losing retention history.

Backup platform migration

Moving between platforms with parallel runs and validated restores.

Cloud and hybrid deployment

On-premises platforms extended to cloud storage, or cloud workloads protected on-premises.

Acceptance testing and documentation

Test results, configuration baselines and runbooks handed to your team.

How it runs

Discover, design, build, validate, transition. Nothing cuts over until restores from the new environment have been tested, and your team receives documentation and knowledge transfer before handover.

What you receive

An implementation plan, test reports, a configuration baseline, operating runbooks, knowledge transfer and acceptance records.

Assess

Health Check and Optimization

Know the condition of your backup environment before an incident reveals it. A structured review across seven dimensions, summarised for management and detailed for engineers.

Architecture and configuration

Design review against current workloads and recovery objectives.

Backup job success and failure trends

What fails, how often, and what the pattern says.

Storage capacity and deduplication

Growth trends, dedupe ratios and when storage runs out.

Recovery readiness

Evidence of recent, successful restores — or the lack of it.

Security and access control

Role design, credential handling and administrative boundaries.

Software lifecycle and patch posture

Version currency, end-of-support exposure and upgrade sequence.

Operational process and reporting

How the environment is run day to day, and what gets reported.

How it runs

A read-only review of your environment against a standard checklist, followed by a findings workshop. One-off checks, quarterly re-checks and annual optimization programs are available.

What you receive

A management summary, findings ranked by severity, remediation recommendations, a prioritised roadmap and a technical appendix.

Recover

Emergency Recovery Services

For critical incidents: platform failures, failed recoveries, and recovery coordination after ransomware events.

Backup platform failure

Management server, media agents or index failures that stop backups or restores.

Failed critical recovery

A restore that must work now and does not — databases, VMs, file services.

Post-ransomware recovery coordination

Sequenced recovery from backup copies, coordinated with your incident response team.

How it runs

Request, triage, authorize, recover, review. We confirm commercial and technical acceptance conditions before starting work, and every engagement ends with a written review.

What you receive

A scoped engagement with defined acceptance criteria, recovery actions logged, and a post-incident review document.

Automate

Automation and Custom Development

Backup operations improved through APIs and integration: consistency, auditability and faster response, achieved by software rather than headcount.

REST API integration

Backup operations connected to your ticketing, monitoring and CMDB.

Self-service recovery workflows

Delegated, controlled restore paths for application and database teams.

Automated disaster recovery drills

Scheduled, evidence-producing DR exercises instead of manual ones.

Compliance and operational reporting

Reports generated from platform data, not assembled by hand.

Archive and data lifecycle workflows

Retention, legal hold and disposal handled by policy.

Service portal integration

Backup status visible inside the portals your teams already use.

How it runs

Discovery workshop, prototype, integration, test, documentation and support — delivered incrementally so each piece earns its place.

What you receive

Working integrations, documented workflows, audit-ready reporting and fewer manual steps across operations.

Operate

Managed Backup Services

Monitoring, administration, incident management and reporting as a subscription — the most common way customers work with us over the long term.

Not sure where to start?

Tell us your platform, its scale and what is hurting. We will recommend the right entry point — even if it is not the biggest engagement.