Coverage and retention
Identify important data across servers, devices and cloud applications. Agree what is included, how often it is protected and how long copies are retained.
Plan for the restore, not just the backup job.

Match backup coverage to the systems and information you need to recover. Discuss retention, restore testing and the order in which business services need to return.
Identify important data across servers, devices and cloud applications. Agree what is included, how often it is protected and how long copies are retained.
Establish the order in which services need to return and what each one depends on. Discuss tolerable downtime and data loss before choosing a recovery approach.
Define restore tests, reporting and responsibility for failed jobs. Include access to recovery credentials and the process for requesting or authorising a restore.
File recovery and whole-service recovery are different requirements. A backup may recover deleted information without immediately restoring a working application, identity system or phone service. Scope each recovery scenario separately.
Read our full backup & recovery overview →An Edinburgh business handling sensitive business information should start with access ownership and working practices. Managed IT can bring devices, Microsoft 365, secure sharing and recovery into the same plan without assuming every user needs identical permissions.
Your backup & recovery brief should account for how people work, the systems they depend on and any changes you are planning. The points below help connect those requirements to the wider environment.
Identify administrators, shared accounts and external collaborators. Agree who approves access, how accounts are removed and which systems need additional sign-in protection.
Service planning: Identify the systems and data that must be protected.
Plan migrations around working hours and critical business dates. Define a pilot group, acceptance checks and a rollback approach before moving the wider team.
Before making changes: Agree recovery objectives and retention periods.
Critical data, current backups, retention needs and the business impact of downtime.
Request a backup & recovery consultation →A backup is one part of continuity planning. Recovery also depends on applications, identity, connectivity, hardware and agreed procedures. Recovery targets must be assessed and confirmed for the actual environment.
Peravix is a UK provider with a registered office in London. We scope remote work and support around your systems. Any on-site attendance, installation or specific response commitment in Edinburgh is agreed in advance and recorded in your proposal.
Pricing and lead time depend on your requirements, the existing environment, third-party dependencies and the agreed scope. We confirm the proposed arrangement before you commit. Keep existing services active until any migration or transfer is agreed.
Review device protection, identity, updates and exposure across your environment. Prioritise practical improvements and clarify which security responsibilities sit with each provider.
Assess which workloads fit a hosted or cloud environment and which need to stay on premises. Plan migration, connectivity, access and ongoing responsibility together.
Bring users, devices, updates and day-to-day support into an agreed service scope. Choose full outsourcing or support that complements your internal IT team.
Tell us about your Edinburgh business and what you need from backup & recovery. We’ll discuss suitability, scope and the route forward.