Governance · Policy

Backup Policy

Governing entity
Servana Managed Services Ltd
Framework
StackTrack Governance
Effective date
12 August 2026
Version
2026-08-12
Document owner
Managing Director
Next review
12 August 2027

This document describes standard governance controls. Customer-specific contractual commitments are defined in the applicable service agreement.

1. Purpose

Servana Managed Services Ltd maintains backups to protect the confidentiality, integrity and availability of information and Managed Services operated under the StackTrack brand.

This policy defines the minimum controls applied to backup creation, retention, encryption, geographic resilience, recovery and testing.

Service-specific requirements may supplement this policy through an applicable Statement of Work, Service Level Agreement or service plan.

2. Scope

This policy applies to electronic information, configuration, software and service data identified as requiring backup as part of a Servana-managed service or internal information system.

Backup requirements are determined according to:

  • the nature and criticality of the service;
  • the applicable service tier;
  • customer requirements;
  • recovery requirements;
  • data residency requirements;
  • technical architecture; and
  • applicable legal, contractual and security obligations.

3. Backup frequency

Managed Services are backed up at least once every 24 hours unless a different backup schedule is specified for the applicable service.

Additional or more frequent backups may be agreed where required by a customer or by the technical or operational characteristics of a service.

Additional backup requirements may be subject to:

  • technical feasibility;
  • storage and infrastructure requirements;
  • additional Charges; and
  • an updated Statement of Work or other written agreement.

4. Backup retention

Standard backup retention is determined by the applicable Managed Service tier.

Service tierBackup frequencyStandard retention
StandardAt least daily7 days
EnhancedAt least daily14 days
PremiumAt least daily28 days

A different retention period may be agreed where required by the customer, service architecture, regulation or contractual requirements.

The applicable service plan or Statement of Work determines the service tier and any customer-specific variation.

5. Recovery objectives

Servana defines Recovery Point Objectives and Recovery Time Objectives for restoration from Managed Service backups.

Recovery Point Objective

The Recovery Point Objective (RPO) represents the target maximum age of recoverable data when restoration from backup is required.

For Managed Services using the standard daily backup schedule, the target RPO is:

24 hours

A lower RPO may be agreed where more frequent backup or replication is required.

Recovery Time Objective

The Recovery Time Objective (RTO) represents the target period within which an affected Managed Service will be restored where recovery from backup is determined to be the appropriate recovery action.

Standard recovery objectives are:

Service tierTarget RPOTarget RTO
Standard24 hours8 hours
Enhanced24 hours6 hours
Premium24 hours2 hours

The RTO includes the operational time reasonably required to:

  • identify and assess the incident;
  • establish that restoration from backup is appropriate;
  • allocate the required support capacity;
  • obtain information, access or approvals reasonably required for recovery;
  • select an appropriate recovery point; and
  • initiate and complete the restoration process.

Once a valid backup has been selected and restoration has been initiated, the underlying technical restoration process is typically capable of completing substantially faster and, for many Managed Services, within approximately 30 minutes.

Actual technical restoration duration may depend on factors including:

  • service architecture;
  • data volume;
  • infrastructure availability;
  • cloud-provider availability;
  • third-party dependencies; and
  • the nature and extent of the incident.

6. Customer-caused recovery events

Where restoration is required following a customer action, deletion, configuration change or other customer-controlled event, the applicable RTO begins once:

  • the incident has been reported to or detected by Servana;
  • the information and access reasonably required to perform recovery are available; and
  • Servana has determined that restoration from backup is the appropriate recovery action.

Delays caused by unavailable customer access, information, approvals or other customer dependencies are not included when measuring the applicable recovery objective.

7. Backup and service availability

The RPO and RTO values in this policy relate specifically to recovery from backup.

They do not replace or redefine separate commitments relating to:

  • service availability;
  • incident response;
  • high availability;
  • automatic failover;
  • disaster recovery;
  • support response times; or
  • other Service Levels.

Where an applicable Statement of Work or Service Level Agreement defines different recovery commitments, those service-specific commitments apply.

8. Encryption

All Managed Service backups must be protected using encryption appropriate to the sensitivity of the information being protected.

Backups must be encrypted:

  • at rest; and
  • in transit where transferred between systems, services or locations.

Cryptographic controls must be implemented in accordance with Servana's Cryptographic Controls Policy.

Access to backup systems and backup data must be restricted according to least-privilege principles and limited to authorised personnel and services.

9. Geographic resilience

Managed Service backups must be replicated across geographically separate cloud regions where supported by the service architecture.

The purpose of geographic replication is to reduce the likelihood that a single regional infrastructure failure affects both the live service and all recoverable backup copies.

Backup locations must remain within the data residency and processing boundaries applicable to the relevant service and customer agreement.

Typical deployment patterns may include:

  • European Union: replication between separate EU regions, such as Ireland and Frankfurt;
  • United Kingdom and Europe: replication between UK and European regions where permitted by applicable data protection, transfer and customer requirements; and
  • United States: replication between two separate cloud regions located within the United States.

The specific cloud regions used may change as infrastructure, provider capabilities, resilience requirements and customer requirements evolve.

10. Backup integrity and protection

Backup systems must be designed and operated to reduce the risk of:

  • accidental deletion;
  • unauthorised access;
  • corruption;
  • loss of integrity;
  • compromise of the production environment affecting backup availability; and
  • failure of a single infrastructure location.

Where appropriate to the service, additional controls may include:

  • separate backup accounts or storage locations;
  • restricted deletion permissions;
  • retention controls;
  • versioning;
  • immutability controls; and
  • independent recovery credentials.

11. Monitoring

Backup operations must be monitored to identify failed, incomplete or abnormal backup activity.

Material backup failures must be:

  • investigated;
  • remediated within a reasonable period;
  • escalated where they create a material recovery risk; and
  • handled in accordance with applicable operational and incident-management procedures.

12. Restore testing

Backups must be tested periodically to provide reasonable assurance that they can be successfully restored.

Testing may include:

  • automated backup verification;
  • integrity checks;
  • test restores;
  • service recovery exercises; and
  • recovery testing performed as part of business continuity or disaster recovery exercises.

The frequency and scope of testing should reflect the criticality and architecture of the relevant service.

Any material failure identified through testing must be investigated and remediated.

13. Software and configuration

Software, infrastructure configuration and other components required to restore or reproduce a Managed Service must be protected through appropriate mechanisms.

Depending on the system, this may include:

  • source control;
  • infrastructure-as-code repositories;
  • configuration management;
  • artefact repositories;
  • software package repositories;
  • image registries; and
  • conventional backup systems.

The objective is to ensure that the software and configuration required to operate a service can be recovered or reproduced with minimal unnecessary disruption.

14. Third-party services

Third-party providers used to store, replicate or process backups must be assessed and managed in accordance with Servana's supplier-management requirements.

Backup services provided by third parties must provide security and resilience appropriate to the information and services being protected.

The use of third-party cloud infrastructure does not remove Servana's responsibility for implementing the backup controls defined in this policy for Managed Services under its control.

15. Customer-specific requirements

Customers may request backup arrangements that exceed the standard service tier, including:

  • increased backup frequency;
  • longer retention;
  • additional geographic copies;
  • customer-specific recovery points;
  • lower RPO targets;
  • different RTO targets; or
  • additional recovery testing.

Customer-specific requirements must be agreed in writing and may be subject to additional Charges.

16. Responsibilities

Servana is responsible for:

  • defining appropriate backup controls for Managed Services;
  • operating and monitoring backup systems under its control;
  • protecting backup confidentiality and integrity;
  • performing appropriate restore testing; and
  • maintaining recovery capability consistent with applicable service commitments.

Customers remain responsible for any backup, retention or recovery requirements that are expressly identified as customer responsibilities in the applicable Statement of Work.

17. Review

This policy is reviewed at least annually and following significant changes to:

  • Managed Service architecture;
  • backup technology;
  • recovery requirements;
  • applicable legal or regulatory requirements; or
  • Servana's information security management system.

Material changes will be published as a new version of this policy.

18. Approval

Document owner: Managing Director Approved by: Managing Director Effective date: 12 August 2026 Next review: 12 August 2027

Related governance