Backup & Disaster Recovery Services
A backup means nothing if the restore does not work. Many companies discover this at the worst possible moment: after a ransomware attack, a disk failure or an accidental deletion, when the archive "that was made automatically" turns out to be corrupted, incomplete or months old.
We implement automatic backup — local and in the cloud — with encryption and off-site replication, so that a copy of the data always exists outside the infrastructure that can be affected. And, more importantly, we test the restore regularly: we do not consider a backup working until we have actually brought the data back from it, on a separate environment, on an agreed schedule.
For truly critical situations we build documented Disaster Recovery plans, with clear objectives: how long each system takes to come back (RTO) and how much data you can afford to lose in the worst case (RPO). We set the numbers together, based on how much an hour of downtime costs your business — then size the solution exactly to them.
What we include
- Automatic & encrypted backup
- Off-site replication
- Regular restore tests
- Documented DR plans
- Defined RTO/RPO
- Configurable retention
Who backup and disaster recovery is for
This service fits any company for which lost data or a day of downtime costs money: businesses running their accounting in 1C, trading companies with order and inventory databases, offices working with documents and contracts, and teams running applications on their own servers or in the cloud — in Moldova, the EU or the US. Typical situations: backups run "automatically" but nobody has checked whether they still work; copies sit on the same server or in the same building as the original data; after a ransomware attack or a disk failure nobody knows how long recovery will take; or auditors and partners ask for a documented business continuity plan.
How we work
We start with a free audit: what data you have, where it is, what is being saved now and — the key question — when the restore was last tested. We then define the protection plan and the SLA, with agreed RTO/RPO, implement the backup and replication without affecting production systems, then operate everything 24/7: we monitor every job, get alerts on any failure and run the restore tests on schedule.
After implementation, every backup job is monitored 24/7, and any failure triggers an alert that we handle — not an email nobody reads. Restore test results are documented and included in your periodic report, alongside the state of the copies, storage used and our recommendations. When new systems appear or data volumes change, we update the protection plan and retention policy so coverage stays complete.
How the price of backup and disaster recovery is formed
The price depends on the volume of data protected, the number of servers, databases and workstations included, where the copies are stored (on-premises, in the cloud or both), the retention period and the agreed RTO/RPO targets. The frequency of restore tests and the SLA level also matter. Storage and 24/7 operation are covered by a monthly plan. After the free audit you receive a fixed offer within 48 hours, sized to what an hour of downtime costs your business.
Why ITBOX
Frequently asked questions
What is the right way to back up company data?
The right way to back up company data is automatic, encrypted copies, at least one copy stored off-site, outside the main infrastructure, and regular restore tests. Without a restore test you cannot know whether a backup works. We only consider a backup valid after we have actually restored data from it on a separate environment.
What are RTO and RPO?
RTO is the maximum time a system may take to come back online after an incident, and RPO is the maximum amount of data you can afford to lose, measured in time. We set both together, based on what an hour of downtime costs your business, and write them into the SLA.
Does backup protect us from ransomware?
Yes, backup protects you from ransomware as long as a copy of the data is kept off-site, separate from the infrastructure the attack can encrypt. Off-site replication and restore tests ensure you can bring data back without paying a ransom. The disaster recovery plan sets the order in which systems come back.
Do you back up 1C databases too?
Yes, our backup covers 1C databases, servers, other databases and company files, both on-premises and in the cloud. For 1C, where accounting and inventory live, the backup frequency and RPO target are set separately, so that an incident costs as little re-entered work as possible.
How often is restoring from backup tested?
Restores are tested regularly, on a schedule agreed in the SLA, on a separate environment that does not affect production systems. The result of every test is documented and included in your report. The frequency depends on how critical the data is: core systems are tested more often.
What happens if a backup job fails?
If a backup job fails, our 24/7 monitoring alerts us immediately and we investigate the cause, without waiting for someone on your side to notice. For critical incidents we respond within 30 minutes. The missed copy is re-run, and the cause — storage, network or configuration — is removed.