Data protection plan
We list the systems and data that are critical to the business. Then we agree on backup frequency, retention period, storage location and acceptable data loss.
A successfully completed backup is not the same as a verified recovery. Together we define what we protect and how we bring the business back to work.
We list the systems and data that are critical to the business. Then we agree on backup frequency, retention period, storage location and acceptable data loss.
We set up and maintain backups with solutions such as Veeam and Synology, according to compatibility and available licences. We consider separating copies and access rights from production systems.
We agree on restore tests for files, virtual machines and individual services. We document the steps, dependencies and observed limitations so the plan does not remain just on paper.
We plan the MailStore archive separately from backup. We define sources, search, access and retention rules together with your responsible people. The technical solution does not replace a legal assessment of retention obligations.
We get to know the system, users, risks and the desired outcome.
We define scope, schedule, responsibilities and post-work checks.
We document what was done and agree on ongoing maintenance.
For each system we agree an RPO as the target acceptable data loss expressed in time, and an RTO as the target recovery time. We define the order in which identity, network, database and application are restored. These targets become test criteria, not an automatic guarantee that comes with buying software.
The scope may include backup jobs, backup copy procedures, retention, free-space monitoring and separation of administrative accounts. We assess local and remote storage as well as offline or immutable copies depending on platform support. For Synology we check capacity, access rights, disk health and the device's role in the overall protection plan.
The test covers selected files, a virtual machine or an application unit, depending on the agreed scope. We record restore time, data consistency, user login and service functionality. For MailStore we additionally check archiving sources, search permissions and the message export procedure; the retention policy is confirmed by the client's responsible person.
We use experience with VMware, Veeam and network storage to link backup operations with business dependencies. Particular emphasis is placed on backup administration and recovery verification having clearly assigned responsible people.
No. A backup is for restoring data after loss or failure, while an archive is for organised retention and searching of email. Both approaches are often needed.
We first define the business objective, then check whether the existing infrastructure supports it. Agreed targets must be aligned with a feasible, tested procedure.
Tell us what works, what gets stuck and what you want to improve.