F2Cloud Backup
Immutable Backup as a Service
Protecting selected backup copies against modification or deletion during a defined retention period.
Live flow
- Protection flow
- Restore
Write backup → retention lock → reject deletion → verified restore
Conceptual animation; real throughput and volume depend on your agreed scope.
01What this service means
A restore point an attacker cannot simply delete.
An attacker with production access may target backups too. One copy managed with the same credentials is not enough.
Outputs of the agreed scope
A protection design defining immutability periods, access separation and restore validation.
Important boundary
Immutability does not stop an attack or guarantee clean data. The recovery point must be validated separately.
02F2Cloud Backup / Service flow
Selected copies. Protection for a defined period.
Write backup → retention lock → reject deletion → verified restore
Outcome: A copy is created.
-
At this stage
The daily backup is written encrypted to F2Cloud storage.
-
At this stage
It is marked immutable for the policy period.
-
At this stage
Even if production is encrypted, protected copies are unaffected.
-
At this stage
A suitable restore point is selected, verified in isolation and restored.
The lock applies only during configured retention. Immutability does not prevent an attack; candidate points require assessment; absolute cleanliness is not guaranteed.
In ransomware incidents attackers often go after backups first: they reach the backup server and delete or encrypt copies. Immutable backup counters this by storing copies in a write-once, cannot-modify state for a defined period.
In F2Cloud, immutable copies are kept on storage that is logically separated from your production environment and administrator accounts. Changing or deleting a copy before its retention ends is blocked.
Protection depends on implementation and threat model. Immutable backup does not stop an attack; it ensures a trustworthy restore point exists afterwards.
Technical scope and limits
- Immutability is limited to the configured retention period.
- If an intrusion predates the backup, selecting a clean point requires analysis.
- Immutable backup doesn't replace endpoint security or network segmentation.
Frequently asked questions
What is immutable backup?
A backup copy that cannot be modified or deleted during the defined retention period, so it survives even if ransomware or unauthorised access targets your backups.
Does immutable backup stop ransomware?
No. It doesn't prevent the attack; it ensures a reliable recovery point exists afterwards. Prevention needs layers such as EDR and segmentation.
Who decides the retention period?
Retention policies are defined together with you, based on business and regulatory needs.
Related services
-
F2Cloud Backup
Backup as a Service (BaaS)
F2 engineers design, operate and regularly restore-test the backups of your servers and virtual machines.
-
F2Cloud Recovery
Cyber Recovery as a Service (CRaaS)
After ransomware the goal isn't paying a ransom — it's returning from a protected restore point, verified in an isolated environment.
-
F2Cloud Security
Workload Security as a Service (SECaaS)
We protect your server and container workloads in F2Cloud with visibility, segmentation and incident response workflows.
Before you decide
-
Backup vs disaster recovery: what is the difference?
Backup protects data. Disaster recovery prepares the environment, dependencies and operations needed to resume the business using that data.
-
What are RPO and RTO? Defining disaster recovery targets
How much data loss is acceptable, and how long can the business stop? Answers to these different questions shape recovery architecture.
-
Backup and recovery for VMware, Hyper-V, KVM and Sangfor workloads
A platform list is a scope question, not a marketing label. Each hypervisor is backed up differently, and cross-platform recovery requires per-workload validation.
03What confidence is built on
Less adjectives. More accountability.
F2Cloud brings F2 Bilişim's networking, cybersecurity and virtualization engineering into a managed service model. A sound decision needs clear boundaries as well as commitments.
- 01
Written scope. Clear ownership.
Which workloads are protected? Who monitors and responds? The proposal defines architecture, included services and responsibility boundaries.
Explore the details - 02
A target matters when it is measured.
RPO and RTO are set around your workloads. Recovery exercises assess applications, networking and access together. A target is not a guarantee.
Explore the details - 03
Know where data lives and who can reach it.
A Turkey-hosting assessment must cover primary data, backups, logs and support access. KVKK considerations include data flows and roles, not location alone.
Explore the details
F2Cloud
Talk to our engineers
Tell us what you run. We'll define the architecture, scope and monthly service model together.
Request a Recovery Assessment