Skydivers are different.\nSome go to skydiving school and land face-up into the wind and on both feet.\nOthers do the same thing, but their parachute is leaky. Others jump without a parachute at all. What do they hope for? Probably, they will grow wings behind their back in flight, be picked up by a dragon or a giant eagle.\nFor some reason, when it comes to website backup (which is like a parachute), website owners turn into these third parties: they either have some kind of backup system, or they don't have one at all. Meanwhile, the statistics are relentless: \nfrom 25 to 45% of companies close after a large-scale data loss (cmitsolutions.com).\nHow to avoid losing a site, money and prospects due to your own carelessness or ignorance, we will tell you.\nWe are convinced that there are only two backup rules. They are very simple.\nRule #1. The backup system should be layered.\nRule #2. The more complex the project, the more complex the backup system.\nOften, site owners limit themselves to creating only one backup that is stored on the server, or rely on a hosting backup system. Why not? Let's tell 3 stories from life.
The first story is tragic
One of our clients – a construction company – lost the password to the email address to which the site and hosting were registered. I started a new one, changed the address in the site settings, and forgot about hosting until the site crashed. The problem was noticed only after a month (why so late is another question). They began to understand. It turned out that the old mail received reminders from the hosting with a request to pay for services. There was no reaction, the site was disabled and deleted. Together with backups - as it should be, after 30 days. There were no other copies, the site could not be updated.
The story of the friend is instructive
Once a state order fell on one online store of trade equipment. Work is for six months. They forgot about the site out of happiness, and when the work on the tender ended, of course, they wanted to resume the online store. And then it turned out that the hosting was blocked, the site was removed and there was no backup. The owners of the site did not have it any more. Fortunately, during the installation of the site, our experts set up a backup to the 1C-Bitrix cloud, and in the archives of the support service, a report on the installation of the site was found, which preserved the license key and encryption password of the backup copy. The site was restored, and the client thought about a multi-level backup system.
The third story is sad
If you have a corporate website
We use a two-level copying system: 2-3 backup copies are stored on the server, another 2-3 - in the 1C-Bitrix cloud. How often to backup: daily or once every 2-3 days, depending on how often you update the site.
If you have an online store
A complex backup and daily backup system is required, including to the cloud. It is recommended to: Configure a standard daily backup using 1C-Bitrix and transfer the archive to the cloud. Configure a backup using the hosting site to a separate storage (for example, a remote FTP server). cloud or to your own backup server. If necessary, a specialized company will help you create such a service. \nThe main thing: the data must be physically on your premises!\nDevelop a disaster recovery plan and instructions. It is very important to check the functionality of this manual every month. To do this, it is enough to restore a copy on the test site.
For large projects
By "large" we mean online stores with the number of applications from 50-100 per day and with a turnover of more than 1 million rubles per month. The general rules are the same as for online stores from the previous point. \nHowever, what is additionally necessary in this case:\nVersion control system as an additional source of backup copies of the software code (protection against human factor and programmer errors).\nDistributed database server with instant replication.\nReady backup server - for the developer or the customer's territory. It will help in an emergency situation to divert traffic and prevent the site from crashing. We recommend using a fault-tolerant cluster.
Emergency kit
When a site goes down, the most important data for its recovery becomes unavailable along with it. In case of emergencies, we recommend having logins and passwords for access to hosting and the site, the key to the encrypted copy stored in the cloud, and the key number to 1C-Bitrix at hand. Fill out and print this table, keep it in a safe place (or vice versa) - this will be your emergency kit in case of emergency situations.
