Backup and recovery strategy
A document setting out, for each system, the acceptable downtime, the acceptable data loss, who does what and in which order. That is what people turn to during an outage instead of inventing solutions on the spot.
Three services answer three questions: what to back up with, where to keep it and what to do on the day everything fails.
We define what has to be saved: accounting databases, file shares, device configurations, email. We set the frequency, the retention and the alerts so a failed job does not slip past unnoticed.
The copy leaves the building and settles on a separate site with its own credentials. Neither a fire, nor stolen equipment, nor malware inside the perimeter can reach it.
A document setting out, for each system, the acceptable downtime, the acceptable data loss, who does what and in which order. That is what people turn to during an outage instead of inventing solutions on the spot.
Before choosing a tool you need two numbers for each system: how many hours it may be down and how much data loss you can live with.
Downtime up to four hours, data loss within an hour. A single nightly backup is not enough; frequent transaction log snapshots are needed.
Downtime up to a day, data loss within a day. A single overnight backup outside working hours is enough.
Downtime up to four hours, data loss within an hour. The database backup is supplemented by a separate mail archive.
Downtime no more than an hour, data loss within an hour. Meeting that target is impossible without a prepared standby site.
Downtime up to a day, data loss within a day. Achievable only if the documents are not kept on the workstation itself.
Something saved on the same hardware does not count as a backup. A failed drive, malware or an accidental deletion will destroy it along with the original. The working minimum is two copies on different media and one outside the building.
The setup itself takes a few days, but the value appears at the fourth stage, which is the one most often skipped.
We establish where the valuable data actually lives. We regularly find accounting databases on employees' personal machines and files that exist only as email attachments.
Together we fix the maximum downtime and acceptable loss for each system. Those two numbers are what set the cost of the solution.
The frequency, the retention, encryption and a secondary site. We configure alerts for both outcomes: success and failure.
Every month we restore the backup on a separate rig and time it. There is simply no other proof that it works.
The point is not whether you have backups but when you last restored from one. In our experience a fair share of supposedly configured schemes do not work: the job has been failing for months, the wrong folder is being saved, the file is locked with a forgotten password. Such a check takes a day and costs little.
Only if it cannot be reached from the same network with the same credentials. Modern malware deliberately hunts for backups. That is why you need a copy on a separate site, with its own permissions and immutability enabled.
The typical scheme: daily copies for two weeks, weekly for about two months, monthly for a year. That depth helps not only when hardware fails but also with a mistake discovered weeks later. For the finance department the periods are usually set longer.
It depends on the size of the data and the bandwidth. A fifty-gigabyte database restores from a local drive in an hour and a half, and noticeably longer from a remote site. We get the exact figure during a test restore and write it into the procedure so you know it in advance.
Изучим действующую схему, попробуем восстановиться из имеющегося архива и без обиняков сообщим, выручит он вас при отказе или окажется бесполезным.
Request received
It is already with a manager. You will get an answer within the working day, and urgent requests go to the duty engineer immediately.
There is no such city in the list. Check the spelling.