A backup only counts if you can restore it.
Backup and disaster recovery for companies in Lebanon and the region: local copies for fast restores, offsite and cloud copies for disasters, immutable copies that ransomware cannot touch, and restore tests with written results.
- 3-2-1-1-0 backups
- Immutable copies
- Offsite & cloud copies
- Restore testing
- RTO & RPO
- Ransomware recovery
Built for the failures Lebanese companies actually face
Most companies have backups. Far fewer have proven they can restore a whole server, a database or a mailbox within the time the business can tolerate. Ransomware now targets backup files first, so a copy on the same network as the servers is no longer enough.
Operating in Lebanon adds its own risks: power cuts and generator switch-overs that corrupt disks and databases, internet links too slow to restore terabytes from the cloud in a hurry, and offices that may need to work from another location at short notice. We design backup and recovery around those realities: fast local restores, an offsite or cloud copy for disasters, an immutable copy for ransomware, and a written recovery plan that names who does what.
- Every critical system and its data listed, with an agreed recovery time (RTO) and data-loss limit (RPO)
- Fast local restores from on-site backup storage
- An offsite or cloud copy for site-wide disasters
- Immutable or offline copies that ransomware cannot encrypt or delete
- Microsoft 365 mail, OneDrive, SharePoint and Teams backed up separately
- Scheduled restore tests with written results
- A disaster recovery runbook your team can follow under pressure
Backup and recovery services
Backup design & implementation
Veeam or Acronis for physical servers, VMware and Hyper-V virtual machines, databases and file servers, sized to your RTO and RPO.
Immutable & offline copies
Hardened backup repositories, object-lock storage or rotated offline media, so attackers with admin rights still cannot destroy your last good copy.
Offsite & cloud copies
Copies to a second site or to Azure, with bandwidth planned around Lebanese internet links and seeding by disk when the first copy is large.
Microsoft 365 backup
Independent backup of Exchange Online, OneDrive, SharePoint and Teams. Microsoft keeps the service running; restoring your deleted or encrypted data is your responsibility.
Disaster recovery site & failover
A standby server, a replica at a second location or recovery in Azure, with a documented and rehearsed failover and failback.
Restore testing & monitoring
Daily job monitoring, alerts on failed or skipped backups, and scheduled test restores of whole machines, with a short report after each test.
Vendor-neutral, certified expertise
We recommend what fits your environment and budget, not what fills a quota.
- Veeam Backup & Replication
- Acronis Cyber Protect
- Microsoft Azure Backup
- Azure Site Recovery
- VMware vSphere replication
- Microsoft Hyper-V Replica
- QNAP NAS
- Object-lock storage
- APC UPS
Frequently asked questions
What is the 3-2-1-1-0 backup rule?
Three copies of your data, on two different types of storage, one copy offsite, one copy offline or immutable, and zero errors when a restore is tested. It is the practical standard for surviving both hardware failure and ransomware.
Is a cloud backup enough on its own?
Usually not in Lebanon. Restoring several terabytes over a typical business internet link can take days. We keep a local copy for fast restores and use the cloud or a second site as the disaster copy.
Can ransomware encrypt our backups?
Yes, if the backups sit on a normal network share or a server the attacker can log into. Immutable repositories and offline copies are designed so that even an administrator account cannot delete or change them before a set date.
Do we need to back up Microsoft 365?
Yes. Microsoft protects the service, not your data against deletion, ransomware or a departing employee. Retention policies help, but an independent backup gives you point-in-time restores of mailboxes, sites and files.
How often should we test a restore?
Test a file restore at least monthly and a full server or database restore at least twice a year, and after any major change. We record how long each restore took, so you know whether your recovery target is realistic.
What are RTO and RPO?
RTO (recovery time objective) is how long a system can be down. RPO (recovery point objective) is how much data, measured in time, you can afford to lose. Both drive the design and the cost, so we agree them with management first.
When did you last restore a whole server?
A backup and recovery review checks what is protected, how long a restore really takes and where a single failure would stop the business.