Backups that survive the ransomware that wants to encrypt them.

No. M365 has retention policies (typically 30-180 days for Exchange and SharePoint deletions) but those are not backups: they expire, they are not immutable, and they cannot recover from a malicious admin or a corrupted item. Microsoft's own shared-responsibility documentation says you are responsible for backup. We deliver M365 backup as a standard inclusion on Professional and Enterprise tiers.

3 copies of your data (production + 2 backups), 2 different media types, 1 off-site copy. Industry-standard because each layer protects against a different failure mode: deletion, hardware failure, site loss. Most clients run it as 3-2-1-1: the extra "1" being immutability for ransomware protection.

Default retention varies by tier (30 days Standard, 90 days Professional, custom Enterprise). Regulated industries usually need longer (7-25 years). We tier the retention: hot storage for the first 30-90 days, cold storage for long-term. Storage cost scales with volume and retention; we model it transparently.

Backups are written to storage that the storage system itself prevents from being modified or deleted for the retention period. Even an administrator with full rights cannot delete an immutable backup before it expires. This is how a ransomware attacker who gains domain admin still cannot encrypt your last good backup.

Default: Microsoft Azure (UAE region) or AWS (Bahrain region) for clients requiring data sovereignty within the GCC. Alternative: our managed off-site storage in a separate Dubai datacenter. Custom destinations available for clients with specific compliance requirements.

Yes. We assess current state, identify gaps (typically: missing immutability, untested restores, no off-site copy, M365 not backed up), and deliver a remediation plan. Most takeovers complete in 2-4 weeks with minimal disruption to your existing schedule.

Failure escalates to the on-call engineer immediately, not to a daily report. They investigate, re-run, or fix the root cause. Persistent failures (3+ consecutive on the same system) trigger an engineering review with you. Backup health is reviewed in your monthly summary; misses are documented, not buried.

Backup is the data layer of DR. A complete DR programme adds: written RPO/RTO targets, recovery runbooks, replication architecture, annual live failover, and incident response procedures. Backup alone gets you the data; DR gets the business back online inside the agreed window. Most regulated clients buy both.