Knowledge base

A 3-2-1 backup plan for a small company

A 3-2-1 backup plan for a small company — selection, terms and a business quote in Kazakhstan.

What the numbers mean

Three copies, two independent storage types and one copy away from the primary site. The design reduces dependence on one disk, server or building. It is an organizational principle, not a promise that any three folders provide protection.

Start with important systems

Email, accounting, files and application servers can have different requirements. Define RPO, the acceptable data loss, and RTO, the acceptable recovery time, for each. “Copy everything daily” does not answer whether waiting two days for recovery is acceptable.

Separate access

If one account can delete all copies, storage independence is limited. Configure separate rights, retention and deletion protection where supported. A backup on a connected network drive can be affected alongside the primary data.

Testing matters more than a green status

Restore a representative file, mailbox and complete system in a test environment. Measure time, check dependencies and record the result. A successful job log proves transfer; a test record proves the recovered data can be used after an incident.

Offsite copies and operations

For an offsite copy, check the storage location, media capacity and access rights. Assign an owner who reads alerts. The contract should specify monitoring, retention, recovery testing and responsibilities rather than merely mentioning backup.

Run a recovery exercise

Choose an incident matching the business risk: a deleted folder, lost server or unavailable site. Do not alter production merely to test; recover separately and ask the data owner to verify the result. Record elapsed time, missing access and manual actions.

Update instructions afterward: where the copy is, who can decrypt it and the order for starting dependent services. An encrypted copy is useless if its key is lost with the primary system. Instructions and emergency contacts must remain available when the main server fails. Repeat testing after significant changes; scope and frequency follow system criticality rather than an advertising promise.

Before deciding

This guide helps prepare questions; it does not replace the supplier’s current specification. Plan contents and program rules can change. Confirm the exact edition and entitlement at the order date, and verify implementation against agreed criteria.

Veeam · Licensing · Implementation and support

Rights holder terms

IT TECHNOLOGY · ALMATY

Find a solution

Tell us your task — we’ll send a quote within one business day. Send an email ↗