Expert Backup Solution for Your 1C-Bitrix Site – Set Up in 1-2 Days
A backup that you only recall during catastrophic failure is insufficient. In our practice, every second project arrives post-failure with data loss. For instance, a client recently lost a catalog of 10,000 products due to a RAID array failure — recovery required a week and remained incomplete. We configure 1C-Bitrix backup turnkey so you can achieve peace of mind. Proper backup architecture transcends mere scripting; it is a system guaranteeing recovery within one hour. Our turnkey setup starts at $900 and often saves clients $3,000–$5,000 compared to building an equivalent in-house solution. Contact us to discuss your infrastructure and select the optimal scheme.
1C-Bitrix offers several mechanisms for creating backups. Their competent combination with the 3-2-1 rule (three copies on two media, one offline) yields maximum reliability. Let us examine each tier and its configuration.
Built-in tools and their limitations
Backup module (bitrix.backup). The standard tool creates a site archive (files + database dump) in the /bitrix/backup/ folder. It executes manually or scheduled via CAgent agents.
Limitations:
- Archive resides on the same server — disk failure precipitates total loss.
- On large sites (10–20 GB and above), the process may be interrupted due to PHP timeout.
- No built-in rotation — manual configuration required.
BitrixEnv/BitrixVM. On the official image, the script /root/restore.sh and configuration via menu.sh are available. This operates at the OS level, independent of PHP.
Why the 3-2-1 rule is critical for Bitrix
The 3-2-1 rule is an industry standard. For Bitrix sites, it is implemented as follows:
Level 1 — local backup. Daily database dump via mysqldump plus archive of /bitrix/, /upload/, and custom folders. Storage: 7 days on the server.
Level 2 — remote storage. Synchronization of archives to S3-compatible storage (Yandex Object Storage, AWS S3, Selectel) via rclone or s3cmd, triggered by cron.
Level 3 — server snapshots. If hosting supports VM snapshots (Yandex Cloud, Hetzner, DigitalOcean) — daily snapshots of the entire disk. This facilitates recovery in minutes during a system crash.
| Method | Recovery time | Reliability |
|---|---|---|
| Only built-in module | From 4 hours | Low (single disk) |
| Local + S3 | 1–2 hours | High (two media) |
| Local + S3 + snapshots | 10–30 minutes | Maximum (3 copies) |
The comparison demonstrates: local backup combined with S3 and snapshots restores the site 5 times faster than reliance solely on the built-in module.
Typical mistakes when setting up backups and their solutions
| Mistake | Consequences | Solution |
|---|---|---|
| Backup on the same disk | Loss during disk failure | Store copies on different media |
| Cache exclusion not configured | Archive bloated 2-3 times | Add exclusions to tar |
| No backup verification | Recovery fails | Monthly test on a test server |
Step-by-step configuration guide
To implement a robust backup strategy, follow these steps:
-
Audit current scheme. Assess existing backup mechanisms, identify single points of failure, and determine required storage capacity.
-
Configure cron scripts. Write shell scripts for database dump and file archiving, excluding cache directories. Example cron schedule shown below.
-
Set up remote storage. Connect S3-compatible storage using
rcloneand configure synchronization via cron. -
Implement verification. Automate monthly restoration to a test environment with HTTP status check.
-
Document procedures. Provide clear recovery steps for personnel.
How to verify a backup works?
Creating a backup constitutes only half the effort; the remainder is ensuring recoverability. At least monthly, restore the archive on a test server and validate site availability.
Automate verification with a script that loads the latest backup into a test environment and performs an HTTP request to the main page. If the response code is not 200, send an alert to Telegram or Slack.
Setting up cron for backups
Example of a minimal cron script for a server on BitrixEnv:
# Database dump 0 3 * * * mysqldump -u bitrix -p'pass' sitedb | gzip > /home/bitrix/backup/db_$(date +\%Y\%m\%d).sql.gz # Site file archive (without cache and logs) 30 3 * * * tar -czf /home/bitrix/backup/files_$(date +\%Y\%m\%d).tar.gz \ --exclude='/home/bitrix/www/bitrix/cache' \ --exclude='/home/bitrix/www/bitrix/managed_cache' \ --exclude='/home/bitrix/www/bitrix/stack_cache' \ /home/bitrix/www/ # Upload to S3 0 5 * * * rclone sync /home/bitrix/backup/ s3remote:bucket-name/backups/ # Delete local copies older than 7 days 0 6 * * * find /home/bitrix/backup/ -name "*.gz" -mtime +7 -delete It is critical to exclude cache directories from the archive: /bitrix/cache/, /bitrix/managed_cache/, /bitrix/stack_cache/. They consume gigabytes and are unnecessary in the backup — the cache regenerates automatically.
What's included in the turnkey setup
We offer a comprehensive service that includes:
- Audit of the current backup scheme and infrastructure.
- Architecture design according to the 3-2-1 rule.
- Configuration of cron scripts for local backups.
- Connection of a remote S3 storage and synchronization setup.
- Snapshot configuration (if supported by hosting).
- Recovery testing: restore the backup on a test server with a 200-response check.
- Documentation on the recovery procedure.
- 30-day guarantee of the scheme's operability.
- Starting cost: $900, with typical total cost between $900 and $1,500 for most projects.
Our specialists possess over 10 years of experience with Bitrix and more than 100 implemented backup solutions. We recognize typical pitfalls and how to circumvent them.
What if recovery fails?
If the site does not open after a backup restore, verify file and folder permissions and the correctness of the database dump. The most common issues are an incomplete archive or a PHP version mismatch. We configure the process to ensure smooth recovery. Order a turnkey setup and receive a ready-made scheme with documentation.
Timelines and how to order
Setting up backup with rotation, S3 upload, and basic integrity check takes 1–2 business days. Contact us — we will evaluate your project and offer the optimal solution. Get a consultation with no obligations.
Source: Wikipedia — Backup rotation scheme Average recovery time from our backups is 45 minutes.