Setting Up Automatic Failover for 1C-Bitrix

The primary database server went down at 3 AM. The on-call engineer is unavailable. Without automatic failover, the site stays down until morning. With properly configured failover, traffic switches to the replica in 30–60 seconds, and users notice nothing. We configure failover turnkey, covering all layers — from the database to Bitrix configuration. In 2–3 days, your cluster achieves production-grade fault tolerance. We work with companies handling from 10,000 visitors per day — more than 50 projects over the past 5 years. Estimate the savings: downtime for a high-traffic site can be costly. Failover pays for itself in a single incident.

Components of Automatic Failover

Automatic failover for Bitrix consists of three independent layers that must work in concert:

If the DB failover is not accompanied by an application config update, Bitrix will output connection errors.

Why Patroni Is the Standard for PostgreSQL Failover

Patroni is the de facto standard for automatic PostgreSQL failover. Architecture: a Patroni agent on each node, etcd/Consul as DCS (distributed configuration store), HAProxy or pgBouncer in front of the cluster.

Patroni monitors node health and, if the primary becomes unavailable, conducts an election for a new leader via DCS. The replica with the smallest lag (lowest LSN lag) becomes the new primary. The entire process takes 10–30 seconds.

Critical for Bitrix: the application connects to the DB not directly to the server IP but through HAProxy or via a virtual IP (VIP) managed by Patroni:

# /bitrix/.settings.php — подключение через HAProxy
dsn => 'pgsql:host=haproxy.internal;port=5432;dbname=bitrix',

HAProxy checks the Patroni REST API (http://patroni-node:8008/master) and routes traffic only to the current primary.

Comparison of Patroni and Orchestrator:

MySQL Failover via Orchestrator

For MySQL-based Bitrix installations, the analogue of Patroni is Orchestrator. It tracks the replication topology, detects the master failure, and automatically promotes the most up-to-date replica. After promotion, Orchestrator calls a hook script that updates DNS or notifies HAProxy.

What to Do with Bitrix Cache After Failover?

After failover, the new primary is a former read-replica. Before the failover, Bitrix might have been configured for read/write splitting:

// /bitrix/.settings.php
'connections' => [
    'default' => [
        'host' => 'primary.db',
        'port' => '5432',
        // ... write-соединение
    ],
    'replica' => [
        'host' => 'replica.db',
        'port' => '5432',
        'readonly' => true,
        // ... read-соединение
    ],
],

After the failover, the replica became the primary — the replica string should no longer be used for read-only connections (it now accepts writes as well). HAProxy with Patroni API health checks handles this automatically: both ports (write 5432, read 5433) are checked separately.

For memcached/Redis, there are no cache issues. For file cache, we invalidate via BXClearCache(true) or through the admin panel. Our setup includes a post-failover hook that does this automatically.

Another issue is uncommitted transactions at the time of the primary crash. WAL replication guarantees the application of all written transactions on the replica, but transactions that were in the primary's memory at the moment of the crash are lost. This is normal behavior for synchronous/asynchronous replication with losses measured in seconds.

Monitoring State

# Patroni — current leader
curl http://patroni-node1:8008/cluster | jq '.members[] | {name, role, lag}'

# Replication lag (PostgreSQL)
SELECT
    client_addr,
    pg_wal_lsn_diff(sent_lsn, replay_lsn) AS lag_bytes
FROM pg_stat_replication;

Alert: if lag_bytes > 50MB, replication is falling behind, increasing the risk of data loss during failover.

Steps for Configuring Failover for Bitrix

1. Audit the current replication scheme and infrastructure.
2. Install and configure Patroni (PostgreSQL) or Orchestrator (MySQL) with DCS (etcd/Consul).
3. Configure HAProxy with health checks via the Patroni REST API.
4. Change Bitrix connection via HAProxy (not directly to the DB IP).
5. Write a post-failover hook script for cache invalidation and notification.
6. Set up replication lag monitoring with an alert when the threshold is exceeded.
7. Test failover on a load testbed with failure simulation.
8. Document and train the on-call team.

#!/bin/bash
# post_failover.sh
# Clear Bitrix file cache
bx-site /path/to/site bx:clear_cache --full
# Notify via Telegram or Slack
curl -X POST -H 'Content-Type: application/json' -d '{"text":"Failover completed"}' https://hooks.slack.com/...

Timelines and Cost

A typical project on a two-server cluster takes 2–3 working days. Complexity increases with sharding, custom replication settings, or specific Bitrix configurations. The cost is calculated individually after an audit. Get a consultation — we will evaluate your infrastructure for free. Contact us for an audit of your project.

Patroni: https://github.com/zalando/patroni Orchestrator: https://github.com/openark/orchestrator

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.