Summary:
This article explains how BrynQ backs up data and how Salure restores service during incidents to meet agreed RPO and RTO values.
BrynQ backup and continuity overview
Salure has clear policies for backups, restore tests, and incident management so that BrynQ stays available and data can be restored when needed. These policies support ISO 27001 controls for backup, incident management, and business continuity.
Backup scope and frequency
Backups are made for important components, including databases and user files, and stored in a central backup location.
Database backups are created every 15 minutes and kept for a long period, with extra monthly copies.
Application backups for BrynQ are taken several times per day.
The RPO for these daily backups is effectively immediate, and the RTO is one working day.
Some containerized applications are not backed up separately because they can be quickly redeployed; their data is covered in other ways.
Backup storage, monitoring, and testing
Code is managed and backed up via a central Git repository; user files are stored in a managed backup location.
Healthchecks.io monitors backup jobs; if a job fails, an alert is sent and a ticket is created in Jira.
Restores are tested several times per year. Each test is documented in Jira, including restore time and functional checks.
Recovery and disaster scenarios
For a single client, a specific database backup can be downloaded and restored using MySQL commands.
For larger incidents, such as loss of a database container, Docker containers are redeployed with the necessary backup files.
Business continuity planning includes redundancy and availability of information processing facilities.
Continuity roles and communication
A Business Continuity Management plan defines when the recovery plan is activated, for example when the application is unreachable, server response times are high for a long time, or many users report problems.
Roles include the Manager Data & Analytics (communication), Lead Developer (technical decisions), developers (execution), and support staff (customer contact and status page).
Communication uses targeted emails and general updates on the status page, without technical details or strict time promises. After the incident, Salure evaluates and documents what happened and takes measures to prevent a repeat.
Procedure:
For your own continuity strategy, note BrynQ’s RPO and RTO values and check if they fit your business needs.
Identify which of your processes depend on BrynQ and how long you can work without the platform during an incident.
Use “Backup scope and frequency” to explain to your risk team how often BrynQ data is backed up and how long backups are kept.
Use “Backup storage, monitoring, and testing” to show that backups are monitored and regularly tested.
Add the points from “Continuity roles and communication” to your internal incident playbooks so teams know what to expect from Salure during an outage.
Document any extra local backups or export processes you use to complement BrynQ backups.
Additional Information:
ISO 27001 controls for backup, information security continuity, and redundancy support this approach.