Objective-driven design
We set RTO and RPO objectives for critical systems and build backup frequency and retention periods around them.
Data Protection and Continuity
Recovery-focused, tested backup against ransomware and human error.
Enterprise backup means taking regular, protected copies of data so it can be restored after corruption, deletion or a ransomware attack. Good backup is not just copying: it means setting recovery objectives (RTO and RPO) and testing recovery regularly. Nanda Teknoloji designs and operates this whole system.
We set RTO and RPO objectives for critical systems and build backup frequency and retention periods around them.
We design a ransomware-resilient structure that makes it harder to delete or modify backup copies.
We keep multiple copies on different media and in different locations, eliminating the single point of failure.
We verify that backups can truly be restored through regular, documented tests.
Monitors failed jobs, raises alerts and reports to management.
Backup and the DR center are handled in the same design; recovery scenarios are written end to end.
Nanda
Backup platform
For the right decision, we put the topics below in writing on every project. The list also works as a checklist when you evaluate vendors.
| Topic | Question to settle |
|---|---|
| RTO / RPO | For each system, how much data loss and downtime is acceptable at most? |
| Retention period | What are the legal and operational retention requirements? |
| Immutability | How are backups protected against deletion and encryption? |
| Recovery testing | How often and how is restoration tested, and who approves it? |
| Scope | Which of the physical, virtual, database, email and file data are backed up? |
01
Recover from a clean backup even if production systems are affected.
02
Restore quickly at the file, database or virtual machine level.
03
Manage retention periods and restore records in a documented way.
Together we clarify the current environment, goals and risks.
We put the architecture, service level and migration plan in writing.
We migrate step by step, tested and with minimal downtime.
We take responsibility for monitoring, maintenance and incident management.
We measure, report and keep improving the environment.
Backup makes a copy of the data. Disaster recovery also covers bringing the system back up elsewhere using that data. The two complement each other.
It is the rule of keeping at least 3 copies of the data, on 2 different media, with 1 of them in a different location. The modern approach adds an immutable copy to this.
They are protected through immutability, network segmentation and separate access privileges, which make it harder to delete and modify backup copies.
RTO states how quickly a system must be back after an outage; RPO states the maximum amount of data loss that is acceptable.
With regular restore tests. The scope, frequency and results of the tests are documented and reported.
Scope is clarified during discovery according to your environment. Physical and virtual servers, databases and file data are the typical scope.
Tell us what you need; our team will work out the right architecture and migration path with you.