--- title: "Business Backups Made Simple: The 3-2-1 Rule" description: "If a server fails, ransomware locks your files or a laptop goes missing, will your data survive? The simple 3-2-1 backup rule and a short checklist." canonical: https://techlab-ssh.com/en/blog/backup-3-2-1-rule language: en --- # Business Backups Made Simple: The 3-2-1 Rule > If a server fails, ransomware locks your files or a laptop goes missing, will your data survive? The simple 3-2-1 backup rule and a short checklist. Page: https://techlab-ssh.com/en/blog/backup-3-2-1-rule 2026-10-17 Does your company have backups? Most people answer straight away: "Yes, of course." The next question usually gets silence: when did you last try to restore something from them? A backup is only worth something if it works on the day you need it. In this article we explain, in plain language and without jargon, what that takes. ## Why data gets lost It always feels unexpected, but the causes are familiar: - **A disk fails.** Every disk dies eventually. The only question is when. - **Ransomware encrypts your files.** It locks files on the computer and across the network, then demands payment. - **Someone makes a mistake.** A folder gets deleted, an old file is saved over a new one, or a wrong operation is run in the 1C database. - **Theft, fire or a flood.** If the server and all copies sit in the same room, one incident can wipe out everything at once. One point deserves special attention: ransomware encrypts everything it can reach on the network. If your backup sits on a network drive in that same network, it gets hit too. ## What is the 3-2-1 rule? The most widely used backup rule in IT is refreshingly simple: - **3 copies.** Your working data plus two backups. - **2 different devices.** The copies aren't on the same disk but on separate devices, for example the server and a separate network storage box (NAS). - **1 copy off-site.** At least one copy lives in another building or in the cloud, so it survives whatever happens at the office. For a small office it can look like this: the 1C database and files are on the server, they're copied to a network storage box in the office every night, and from there an encrypted copy goes to the cloud. One more condition, because of ransomware: one of the copies must not be deletable or changeable from an ordinary user account. That means a disk that gets disconnected from the network, or cloud storage that keeps older versions. ## How often should you back up? Ask yourself a simple question: how much work are you willing to redo? If re-entering a day of 1C transactions is manageable, a daily backup is enough. If it isn't, back up several times a day. Keeping only the latest copy isn't enough either. Mistakes are often noticed a week or two later, not right away. So keep several versions, for example the last 7 days, the last 4 weeks and the last few months. ## The most important step: test the restore The most dangerous backup problem is finding out too late that it wasn't working. The software reports "success" every night, and on the day you need it you discover it has been copying an empty file for months, or the most important folder was never on the list. So once a quarter, run a small test: restore one file, one folder and a copy of the 1C database to a separate place and open them. Note how long the restore took, too. When work has stopped, every hour counts. ## A short checklist - It's written down which data matters: 1C databases, file folders, email, the website. - Backups run automatically and don't depend on someone remembering. - At least one copy is kept off-site. - Ransomware can't delete or change one of the copies. - If a backup fails, someone finds out straight away. - You know the date of the last restore test. If your answer to any of these is "I don't know", start there. ## The bottom line Backups don't have to be expensive or complicated. What matters is the rule: three copies, two devices, one off-site. And a restore that gets tested regularly. TechLab sets up and monitors backups as part of your [IT infrastructure](https://techlab-ssh.com/en/it-infrastructure), and with our [1C hosting](https://techlab-ssh.com/en/hosting) daily backups are kept separately from the server. If you'd like to know where you stand, [book a free consultation](https://techlab-ssh.com/en/contact?topic=cloud). ## Contact - Phone: +994 50 668 33 34 - WhatsApp: +994 50 272 33 02 (https://wa.me/994502723302) - Email: info@techlab-ssh.com - Working hours: Monday – Friday, 09:00 – 18:00 - Address: Nizami küçəsi,7 Səbail, Bakı, Baku, Bakı - Request form: https://techlab-ssh.com/en/contact#form