Cloud Backup for Business

What happens on the day your data disappears

Most businesses discover their backup was never working at the exact moment they need it most: a server goes down, a disk burns out, an employee deletes a whole folder, or ransomware encrypts the entire network in minutes. The difference between a one-hour incident and a week of paralysis is not luck - it is planning.

Cloud backup moves a copy of your data outside the office, somewhere fire, theft and ransomware cannot reach. We build the system, monitor it daily, and verify that recovery genuinely works - not merely that the backup "ran".

What we back up

Physical and virtual servers

Full image-level backup, so an entire server can be rebuilt - operating system, configuration and data - rather than recovering individual files alone.

Endpoints and laptops

Employee machines are the weak point: they leave the office, they get stolen, they get infected. Backup runs automatically in the background, with nothing for the employee to remember.

Microsoft 365 and Google Workspace

A common misconception: Microsoft and Google back up their infrastructure, not your data. A deleted mailbox, an overwritten SharePoint site, an employee who left the company - all of these are your responsibility. We back up mail, files, calendars and contacts to a separate, independent copy.

Databases and core systems

SQL, ERP/CRM platforms and internal applications get application-aware backup, which guarantees the data is consistent and restorable rather than captured mid-write.

The 3-2-1 rule - the backup that actually survives

This is the standard every serious backup system is built on, and it is simple:

• 3 copies of the data - the original plus two more.
• 2 different media - local storage and cloud, for instance, so a single failure cannot wipe everything.
• 1 copy off-site - physically away from the office.

We add a layer that has become essential: an immutable copy. Even someone who has gained administrator rights on your network cannot delete or encrypt it - which is precisely what stops ransomware from destroying the backup along with everything else.

How fast you get back to work

Two numbers determine how much an incident hurts, and it is worth knowing them before one happens:

• RPO - how much data you can afford to lose. If backup runs once a day, you risk losing a full day of work.
• RTO - how long it takes to get back online. Restoring a single file takes minutes; rebuilding a whole server can take hours.

During the scoping session we set both numbers with you for each system, then match backup frequency and recovery method to meet them. A critical system gets frequent backup and fast recovery; an old archive needs neither the same service level nor the same cost.

Encryption, access control and compliance

Data is encrypted on your side before it ever leaves the network, stays encrypted in transit and at rest, and the keys are not stored alongside the backup itself. Restore access is permission-limited and logged, so it is always clear who restored what and when.

For regulated businesses - finance, healthcare, or anyone holding personal data under Israel's Privacy Protection Law - we align storage location and retention policy with the requirements, including keeping data in Israel where that is necessary.

What it costs

Pricing comes down to three things: how much data there is, how far back you keep it, and how fast you need it restored. There is no sense paying for instant recovery of a 2015 archive, and no sense economising on the one server the whole company works from.

We start with a short mapping of your systems, mark what is critical and what is not, and build pricing around that - no hardware commitment, and no paying for capacity you will not use.

Backup is one layer of a wider system: it works alongside your cloud solutions and information security.