Defining RPO & RTO Objectives
RPO and RTO objectives are defined according to workload criticality, and the backup and recovery architecture is planned around those objectives.
Why Doz Teknoloji Data Backup?
We go beyond installing backup software to design end-to-end disaster recovery plans with recovery objectives and restore scenarios tailored to your workloads.
Direct Engineer Support
During a critical data-loss incident, you can contact the responsible specialist directly.
Immutable Storage
We validate supported retention locks and administrative boundaries through deletion and recovery tests.
Recovery Testing and Application Acceptance
We validate data, applications and access through automated or controlled restore tests according to service scope.
GDPR & Legal Compliance (Encryption)
We apply technical controls such as backup-data encryption, access permissions and key management according to the project scope; legal compliance must also be evaluated against the organization's processes and obligations.
Flexible Hybrid Backup
We spread risk across local NAS/SAN systems and cloud backup storage through an integrated hybrid architecture.
Backup, Storage and Recovery Services
Start with your existing backup/storage products; assess physical, virtual, cloud and SaaS data through RPO/RTO, retention, independent copies and actual restore acceptance.
Physical, Virtual and Application Backup
We deploy and operate image, file and application-consistent backups with your existing backup software. Selection follows source-system support and recovery requirements.
- VM, database, mail and file coverage
- Isolated recovery and application acceptance
TrueNAS and NAS Backup Targets
We evaluate TrueNAS/OpenZFS, OpenMediaVault, XigmaNAS, Unraid and other NAS/SAN solutions as repositories or independent copies. Check protocols, capacity and backup-product support together.
- SMB/NFS/iSCSI and restore-read performance
- Datasets, quotas, access and health monitoring
Snapshots, Replication and Remote Copies
We design local snapshots, separate pools and remote systems as distinct risk layers. Verify source/destination retention, privileges and location independence.
- Incremental transfers and bandwidth planning
- RPO: latest usable destination data point
Immutable or Offline Protection
Where supported, strengthen protection through retention locks, separate administration or offline copies. A snapshot or ordinary NAS share alone is not immutable.
- Verify protection through deletion tests
- Separate identity and access boundaries
Microsoft 365 and Google Workspace Backup
Define independent mail/team-file backup coverage through product/API support. Assess retention, Vault and Purview separately from operational restore requirements.
- Mailboxes, Drive/OneDrive and team files
- Ownership, permissions and item-level restore tests
Bare-Metal and Disaster Recovery
Plan OS, application and dependency recovery on different hardware or locations. Validate replica startup, failover/failback and user acceptance against scope.
- Boot, drivers, networking and identity dependencies
- Measured RTO and controlled failback
Encryption and Recovery Access
Configure supported in-transit and at-rest encryption. Protected recovery-key access stays with authorized administrators; protect configuration alongside data.
- Key access and configuration backups
- Least privilege and access records
Restore Testing, Monitoring and Reporting
Plan tests covering versions, ACLs, application startup and user acceptance beyond copy completion. Frequency and response scope are defined in the service agreement.
- Failed-job, capacity and remote-target alerts
- RPO/RTO and recoverability records
RAID and snapshots are not independent backups. Define whether the NAS holds production data, a repository or a remote copy, and assess shared administration, chassis and location risks.
Related Next Steps
Continue with the relevant technical guide, product/licensing page or project scenario.
Evaluating backup architecture together with server infrastructure, VMware and Hyper-V virtualization, firewall and cybersecurity and the ransomware prevention guide helps create a more resilient recovery architecture.
Related Technical Guides
Review the related Knowledge Center guides before a purchase or project decision.
Data Backup: Buying and Project Decision Guide
A Data Backup project is more than product selection. Capacity, licensing, security, operations and growth should be evaluated together.
When Should You Reassess?
Revisit backup design when copies exist in only one location, restores are not tested, RPO/RTO targets are undefined, or ransomware recovery is not clearly documented.
Selection Criteria
- Business RPO and RTO targets
- Protected data size and daily change rate
- Immutable and offsite copy requirements
- Restore-test frequency
- Retention, licensing and capacity planning
Doz Teknoloji Project Approach
We classify protected workloads, measure data volumes and change rates, then design the copy strategy around recovery objectives, immutability, offsite protection and scheduled restore testing.
Frequently Asked Questions
Data Backup: is taking backups enough?
No. Backups should be verified through restore testing and ideally include an immutable or offsite copy.
Data Backup: how are RPO and RTO defined?
They are set per workload according to acceptable data loss and acceptable outage duration.
Data Backup: does Microsoft 365 need separate backup?
Independent backup is commonly evaluated when the organization needs stronger retention and recovery control.
Plan Your Data Backup Project
Share your current environment and requirements so we can define the appropriate product, licensing and implementation approach.