Smart Disaster Recovery (DR): SmartDR
On this page
This is a Preview feature.
SmartDR creates and manages a continuous asynchronous replication of data between a primary and a geographically separate secondary region.
You can initiate SmartDR via the SingleStore Portal or API.
SmartDR replicates the exact topology from the primary to the secondary region and maintains all the users, permissions, and workspace configurations across the regions.
The principal benefits of SmartDR are minimal ongoing costs and a low Recovery Point Objective (RPO of up to 10 minutes).
A primary use case for SmartDR is to guarantee business continuity in the face of a region outage.
Depending on your business requirements, it may be essential to have both Multi-AZ High Availability (HA) and SmartDR.
In conjunction with SMartDR, Point-in-Time Recovery (PITR), gives you the ability to go back in time and recover data in both the primary and secondary regions.
An existing workspace group - at the time of creation of the workspace group, under
Advanced Settingsyou must check out the
Enable SmartDR and Database Branchingoption.
You can see the
Replicationtab to perform SmartDR and branching only if you have enabled this option.
A workspace in the workspace group - at the time of creation of the workspace, under the
Deployment Type, currently on the Non-Production option is available.
A database and its tables.
Configuring the Replication
Replicationtab from the top menu and then click on
Select the details for:
Primary region- this displays the region where your database(s) currently reside.
This is displayed by default and cannot be modified.
Secondary region- select from the drop-down list the region to which you want to replicate the database(s).
Choose the database(s)to replicate from the list displayed.
Storage Only(this is the only option currently supported).
Submitbutton, you will see a status bar indicating the progress of the replication processes and the replication status of each selected database.
Once the database(s) replication is set up and synced up, you can fail over your application to the secondary region anytime there is a regional failure.
To start the process, click the
Failover button under the
Confirm in the popup window.
During the failover deployment, the system automatically performs the following tasks in the background:
Provisions the environment in the secondary region, maintaining the primary region's topology.
Provisions and configures all your workspaces.
Attaches the databases to the workspace and provides a connection string.
To access the connection string:
Connect Stringfrom the
Connectoption from the drop-down list.
Preserves user permissions, pipelines, firewall settings and other metadata from your primary region.
After initiating the failover process, you may notice either through the UI or by running the SQL command
SHOW DATABASES, there are two databases: one attached to the workspace (WS) and another with the same name but including a timestamp, in a detached state.
The detached database, referred to as a system-managed database, is a continuation of your primary region's database.
During failover, SingleStore attaches a branch of this system-managed database to your workspace.
You can access the data in the system-managed database at any time by attaching it as a branch and recovering the missing rows.
To initiate failback from the secondary region to the primary region:
Failbackbutton located under the
Check the "I confirm.
. . " checkbox and click
Confirmin the popup window.
This action triggers the failback process. A status bar displays progress.
The system automatically performs the following tasks during failback:
Configures the primary region environment.
Attaches replicated databases to the workspace and provides the connection string.
Updates user permissions and other metadata with changes from the secondary region.
Upon successful completion, the primary region becomes active, and the secondary region is no longer accessible.
Last modified: February 9, 2024