Servers, data storage systems and backup are the foundation on which all of an organisation’s information systems run. NVP «Plasmotekhnika» designs, supplies, implements and supports server solutions, data storage systems and disaster recovery (DRP) complexes — both as standalone projects and as part of the full cycle of building a secure IT infrastructure.
A distinctive feature of our approach: the infrastructure is designed in line with baseline cybersecurity requirements. For systems that process restricted information, an architectural basis is laid for the subsequent implementation of TPI measures and ICS security authorization under Resolution No. 712 of the Cabinet of Ministers of Ukraine, without the need for later rework.
Server platforms and virtualisation
A properly selected server platform is a balance of performance, fault tolerance and budget. We begin with a survey of the existing systems and a calculation of loads, not with a price list.
- design and supply of server platforms for actual and projected loads;
- virtualisation: consolidation of physical servers, fault-tolerant clusters, migration of existing systems to a virtual environment without lengthy downtime;
- modernisation of the existing server fleet with a phased transition;
- integration with the client’s networks, directory services and monitoring systems.
Data storage systems
Different data impose different requirements: a transactional database needs speed, an archive needs capacity and reliability, video surveillance needs a stable write stream. That is why the configuration of a data storage system is determined by the data profile, not by a universal template.
- analysis of the data profile and loads, and capacity planning with a horizon of several years;
- building fault-tolerant data storage systems with no single point of failure;
- data replication between sites for critical systems;
- separate secure repositories for backups.
If data must be transferred between networks of different security levels — for example, from a closed segment to a backup repository — we use our own product PLASMA DD: a one-way gateway that physically rules out any reverse flow of data.
Backup
A backup that has never once been restored is merely an assumption that it exists. We build backup as a managed process: with a policy, automation, monitoring and regular test restores.
- a backup policy based on the «3-2-1» principle: several copies, different types of media, at least one copy off the main site;
- protection of copies against ransomware attacks: immutable copies and copies disconnected from the network;
- automation of backup jobs and execution monitoring with failure alerts;
- a schedule of test restores and verification of the actual recovery time.
Disaster recovery (DRP)
Backup answers the question «will the data survive». A disaster recovery plan (DRP) answers the question «how quickly will the organisation be working again» after a fire, the flooding of a server room, a cyberattack or a prolonged power outage.
The two key DRP metrics in plain terms:
| Metric | The question it answers | What it determines in practice |
|---|---|---|
| RPO — recovery point | How much of the most recent data is it acceptable to lose? If copies are made once a day, up to a day’s work may be lost after an incident. | The frequency of backup or replication |
| RTO — recovery time | How long can the systems remain down while recovery is under way? | The recovery technology: from restoring from copies to a standby site that takes over the load |
The closer RPO and RTO are to zero, the more expensive the solution. That is why these metrics are set not by the IT department but by the business — for each system individually. Our job is to help formulate realistic targets and select the technologies that will deliver them without excessive cost.
- analysis of system criticality and agreement of the target RPO/RTO;
- design of a solution of the appropriate level — from copies at a remote site to replication into a backup data centre;
- development of the recovery plan: the sequence of actions, roles and persons responsible;
- periodic testing of the plan and adjustments based on the results.
Does DRP necessarily require building a backup data centre?
No. The level of the solution depends on the target metrics: for some systems, backups at a remote site are sufficient, while critical ones require replication to standby capacity. A mixed approach, in which different systems receive different levels of protection, is usually the most cost-effective.
Who this is critical for
Data loss or many hours of downtime are painful for any organisation, but in certain industries they bring the core business to a halt.
Financial sector
A stoppage of transactional systems means direct losses from the very first minute and reputational consequences that last far longer. Regulatory pressure is added on top: the requirements for data integrity and retention leave no room for improvisation.
Manufacturing
A failure of ERP or of manufacturing or warehouse management systems means a stoppage of production lines and shipments. The loss of process data and formulations can cost more than the equipment itself.
Retail
Checkout tills, the loyalty programme, the online shop and logistics operate in real time. Every hour of downtime means lost sales that do not come back.
Discuss your task
Tell us which systems you run and what would happen if they stopped for a day. We will conduct a survey, propose an architecture to suit your target RPO/RTO and support the implementation — submit a request or call: +38 (044) 204-83-62.