Service · Backup and recovery

Backup setup

Before touching a single backup job we settle two numbers with you: the amount of recent work you could bear to redo, and the number of hours the company survives offline. Without them, choosing a solution is guesswork, and guesswork rarely holds up on the morning the server refuses to boot.

Send an enquiry See the scope

RPO and RTO

agreed before any setup

3-2-1

three copies, two media, one off-site

Immutable

copies ransomware cannot touch

Restore drills

on a fixed calendar

What the service covers

We configure the checking routine as well as the copying. Copies nobody has ever brought back are wishful thinking rather than protection.

Talk it through with us

Requirements and priorities

Which systems are critical, how many hours of data you can do without, and how fast you must be running again.

A 3-2-1 design

Three copies on two different kinds of storage, one of them always outside your building and your network.

Backup jobs

Servers, databases, virtual machines, Microsoft 365, switch configuration and firewall rules.

Ransomware protection

Separate credentials, MFA on the backup console and immutable copies that cannot be removed early.

Alerting

A failed job notifies a named colleague instead of a mailbox nobody has opened in a year.

Test schedule

Documented drills: sample file recoveries monthly and one critical server rebuilt in full each quarter.

How we deliver it

A typical small or mid-sized environment takes one to two weeks to complete, with the initial complete job and a trial recovery included.

Survey

What gets copied today, what does not, where the copies live, and whether a recovery has ever actually been attempted.

Design

A plan covering data volumes, retention and a window in which every job can finish.

Build

Jobs, storage targets, permissions and alerts, all delivered remotely over secure access.

Timed restore

We restore with a stopwatch running. The figure we record is your true recovery time.

Retention depth beats backup frequency. Attackers frequently lurk inside a network for weeks before triggering encryption. Keep copies for only seven days while the intruder arrived a fortnight earlier, and your entire archive is already compromised. Aim for at least thirty days of dailies and twelve monthly restore points.

Common questions

Databases exported the supported way, virtual machines, switch and firewall configurations, Active Directory or Entra ID data and licence keys. Configurations are the ones people forget: the data survives, but how everything was set up lives only in one engineer's head.

Microsoft keeps the service running, but it does not promise that a deleted folder or an encrypted OneDrive can be recovered once the recycle bin periods have passed. Responsibility for your data is yours, so we take separate backups of Exchange, OneDrive, SharePoint and Teams.

Sample recoveries every month, plus a full, timed rebuild of one critical server every quarter. Actual recovery nearly always takes longer than people assume, and a rehearsal is the cheap way to discover it.

Yes. NIS2 requires in-scope organisations to keep operating and recover from incidents, and GDPR expects you to bring personal data back online promptly. A documented backup with test reports is hard evidence during an audit or an enquiry from the authorities.

Related services

View the whole area

Service Cloud backup Encrypted backup in an EU data centre that nobody can delete

Get your backups set up properly

Describe the systems you depend on and the outage you could live with. Our engineers draft a plan built around those two numbers.

Email
office@apply.dk

Coverage
All of Denmark, delivered remotely

I agree that Apply may handle my details as set out in the privacy policy