Backups, recovery and business continuity for businesses
A backup is only half the story. What really matters is the ability to restore: knowing the data is there, that it was not hit together with the network, and how long it will take to get back to work. We build an isolated backup system, test it with a real restore, and prepare the business for the day it needs it.
Elad personally oversees every project and makes sure it runs at the highest standard, from the first mapping to the restore test.
Backup is a technology. Recovery is a capability.
Almost every business has a backup. But on the day of a failure, an accidental deletion or a ransomware attack, the question is not whether the backup ran last night, but whether you can restore from it: whether all the important data was included, whether the systems work after the restore, and how long it actually takes. Backup is also a central part of the business's information security. Attackers know the backup is how an organization gets back to work without paying a ransom, so ransomware attacks try to hit the backups first. A backup that sits on the same network and uses the same accounts as the other systems can be hit together with them.
We start from the business, not the servers: which systems and processes are most critical, how long you can work without them, and how much data you can afford to lose. On that basis we design a backup system following the 3-2-1 rule, with an isolated copy protected against deletion and change, Microsoft 365 backup, and documented restore tests. At the end you have a clear recovery plan: what to restore first, who is responsible for what, and how to get back to work in an orderly way.
When should you deal with backups?
If one of these sounds familiar, it is time to review your backup system.
There is a backup, but nobody has tried to restore
The backup system shows green every night, but nobody knows whether restoring really works or how long it takes.
Concern about ransomware
The backup sits on the same network and accounts as the other systems, and one attack can hit both.
Microsoft 365 is not backed up
Email, OneDrive and SharePoint rely only on what Microsoft keeps by default, for a limited time.
The backup depends on one person
Only one IT person knows how the backup works and how to restore, and that knowledge is not documented.
No plan for an emergency
Nobody has defined what to restore first, how much downtime the business can absorb, or who makes the decisions.
An insurer, customer or standard requires it
Cyber insurance, a supplier questionnaire or ISO 27001 asks about isolated backups and restore tests.
A backup that is planned, protected and tested with a real restore
We start by mapping what matters to the business, and build a plan that fits it.
Mapping what must be backed up
Servers, endpoints, Microsoft 365, cloud systems and databases, according to their importance to the business.
Deliverable: map of systems and dependenciesDefining recovery targets
How long each system can be down, and how much data you can afford to lose. A business decision made with you in advance.
Deliverable: recovery targets for every systemDesign by the 3-2-1 rule
Three copies of the data, on two types of storage, with one copy off site.
Deliverable: backup architectureAn isolated copy protected from change
A copy separated from the network and the regular business accounts, and protected against deletion or change for a defined period (immutable).
Deliverable: active isolated copyMicrosoft 365 backup
Backup of email, OneDrive, SharePoint and Teams, so you can restore files that were deleted or encrypted too.
Deliverable: 365 backup configuredProtecting the backup system itself
Separate permissions, multi-factor authentication, encryption and alerts, so the backup system does not become a weak point.
Deliverable: hardened backup systemDocumented restore tests
A real restore of files and systems, and measuring how long it actually takes.
Deliverable: restore test reportRecovery plan
What to restore first, who is responsible for what, how to communicate during an incident, and how to get back to orderly work.
Deliverable: approved recovery planOngoing support and periodic testing
Regular restore tests, monitoring backup alerts and updating the plan as the business changes.
Deliverable: periodic reportHow it works
Four stages that end with a real restore, not just a backup that runs.
1. Introduction and mapping
We learn which systems and processes matter most to the business, and review the existing backup system.
2. Design
Recovery targets, backup architecture and solution selection, approved with you before we start.
3. Deployment and hardening
We set up the backup, isolate the protected copy and harden the backup system.
4. First restore and handover
We run a real restore test, document the results and hand over the recovery plan.
What stays with you at the end
Everything belongs to you, so your IT provider can carry on from the same point.
- A map of systems and dependencies, with the priority of each system.
- Agreed recovery targets for every critical system.
- A diagram of the backup system, including the isolated copy.
- A restore test report, with the times actually measured.
- An emergency recovery plan, with roles and responsibilities.
- A short restore procedure for common cases, such as a deleted file or a compromised mailbox.
Backups that are really tested, with personal oversight
Elad Elimelech, founder of Marom Cyber, brings 20 years of technology experience, most of them in management roles. In recent years he led technology strategy in information security and management at companies serving hundreds of organizations in high tech, finance and healthcare. He defined information security standards at the highest level and was the go-to authority for the most complex technology challenges across those organizations. When standard solutions were not enough, he led the solution.
Personal oversight until the project succeeds
Elad oversees every stage of the project and is responsible for the result. You have one senior point of contact for every question.
Backup as part of information security
We design the backup from an information security perspective: what an attacker would try to do, and how the protected copy stays out of reach.
A view of the whole organization
The backup is designed together with Microsoft 365, the network, endpoint protection and compliance requirements, so everything works as one system.
Tested, not assumed
Every backup system we set up is tested with a real restore, so you know the actual state and not just what the system reports.
Frequently asked questions about backups and business continuity
If anything is unclear, you can always ask us directly.
Completing the picture
Articles and services that connect to backups and business continuity.
You have a backup. Can you restore it?
An article on the difference between a backup that runs and a real ability to get back to work.
Read the article →Ransomware: why backup is not enough
What ransomware attacks look like today, and what else you need beyond backups.
Read the article →Microsoft 365 hardening
Business email and files are a main target for attackers. This is how to protect them.
Learn more →When did you last restore from your backup?
A short call with Elad, and you will know where your backup stands and what to check first. Free and with no obligation.
Book a call →