RTO/RPO for 1C-Bitrix: From Interview to Runbook

When business says, "the site shouldn't be down for more than an hour," we understand—that's an RTO question. And we are responsible for formalizing agreements with the business and technically ensuring them. Six months later, it turns out restoration from the last backup takes 4 hours, and the business didn't know. RTO and RPO are not technical characteristics; they are agreements that need to be formalized and technically enforced. As certified 1C-Bitrix specialists with over 10 years of experience, we guarantee your target metrics will be achieved with the right approach.

A typical scenario: for an e-commerce store with a daily turnover of 1 million rubles (approximately $11,000), each hour of downtime costs 40,000 rubles ($450). Reducing RTO from 4 hours to 10 minutes can save up to 150,000 rubles ($1,700) per incident. Such numbers motivate businesses to invest in reliability.

What Are RTO and RPO for Bitrix?

RPO (Recovery Point Objective) is the maximum acceptable data loss. If RPO = 1 hour, then in a disaster you can lose no more than an hour of transactions: orders, registrations, stock changes.

RTO (Recovery Time Objective) is the maximum acceptable downtime. If RTO = 30 minutes, the site must be operational within 30 minutes after an incident.

Typical values for an e-commerce store on Bitrix: RPO = 1 hour, RTO = 2 hours. For high-load projects: RPO = 5 minutes, RTO = 15 minutes. The stricter the requirements, the more expensive the infrastructure.

Aligning RTO and RPO with Business

A common mistake is engineers setting technical parameters without consulting the business. This can lead to unjustified infrastructure costs or, conversely, business losses due to long downtimes. We always start with a client interview: how much do you lose per hour of downtime? What data is critical? Only then do we choose the architecture.

How to Calculate Real RTO?

Recovery time is the sum of all steps, not just "restore the database":

1. Incident detection — 0 to 15 minutes (depends on monitoring)
2. Decision to failover — 5–10 minutes
3. Database recovery/promotion — depends on the RPO solution
4. Application configuration change — 2–5 minutes
5. Cache warming — first requests after recovery are slow, Redis/memcached empty
6. Health check — 5–10 minutes

The "cache warming" step is often ignored in RTO calculations. After recovery, the database receives load from scratch: Bitrix cache is empty, OPcache cold. The first 5–10 minutes of operation are peak database load. Without rate limiting, this can bring down the newly restored server. ITIL recommends including detection time in RTO calculation.

Technical Solutions for Different RPO Levels

RPO = several hours. Hourly pg_dump to external storage is sufficient. Simple, cheap, but recovery is slow for large databases.

RPO = minutes. Streaming replication PostgreSQL with synchronous mode (synchronous_commit = on). Each transaction is confirmed only after being written to the replica. Additional latency: +5–15 ms per transaction. More in PostgreSQL documentation.

RPO = seconds. Patroni with synchronous replication plus continuous WAL archiving via archive_command to S3. With WAL archiving, you can restore the database to any point in time (PITR).

# postgresql.conf for PITR
archive_mode = on
archive_command = 'aws s3 cp %p s3://backup-bucket/wal/%f'

Technical Solutions for Different RTO Levels

RTO = several hours. Restore from pg_dump plus deploy code from git. Linearly depends on database size: 10 GB — approximately 45–90 minutes restoration.

RTO = 30–60 minutes. Standby server with hot replica. On incident — manual failover: promote replica, change DNS or app config. Not automatic, but fast.

RTO = less than 10 minutes. Automatic failover via Patroni + HAProxy. No human intervention. Requires initial setup and regular testing.

Which Recovery Method for Your Project?

Choice depends on budget and data criticality. Compare the main options:

Patroni with PITR delivers RTO 6 times faster than restoring from pg_dump.

Decision Matrix for Bitrix

Documentation and Testing

RTO/RPO without a documented runbook is worthless. The runbook must contain the exact command sequence for each failure scenario: primary database failure, web server failure, loss of /upload/, server compromise.

# Example runbook section: PostgreSQL failover (manual)
# 1. Check that primary is unavailable
pg_isready -h primary.db -p 5432

# 2. Promote replica
ssh replica.db 'pg_ctl promote -D /var/lib/postgresql/data'

# 3. Update Bitrix config
sed -i "s/primary.db/replica.db/" /var/www/bitrix/.settings.php

# 4. Clear cache
php /var/www/bitrix/bitrix/modules/main/cli/cache_clear.php

What's Included in RTO/RPO Setup?

• Audit of current infrastructure and business interview to formalize RPO/RTO
• Selection and configuration of the solution (pg_dump, streaming replication, Patroni)
• Setup of WAL archiving for PITR if needed
• Creation of a detailed runbook with recovery commands
• Testing plan and operational documentation
• Knowledge transfer to the client's team (1–2 sessions)

We assess your project in two days. Contact us for a consultation—we'll choose a turnkey solution. Over 50 projects with critical availability requirements—our experience speaks for itself. We guarantee transparent calculations and an operational scheme. Order an audit of your current recovery plan.

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.