The Disaster recovery (DR) feature in Syncrify allow administrators to replicate the primary Syncrify server (DR-Master) to another machine (DR-Slave). In case the primary goes, you can quickly switch existing DR-Slave to DR-Master and have clients connect to that machine.
When DR features are enabled, you must select one of the following roles for Syncrify server:
Machine designated to run as the primary server. Syncrify clients connect to this machine to run backups.
Machine designated to act as a stand-by server. This machine can be made master within a few seconds in case the actual master goes down.
Syncrify server automatically copies the following from a master to slave
In simple terms, Syncrify server becomes read-only when it is designated as a DR-Slave.
Following restrictions apply when a server is assigned a role of DR-Slave.
Before assigning a DR-Slave rold to a server, ensure the following conditions are met:
The following steps assume the primary server, which will become DR-Master, is already up and running. You must setup a DR-Slave before configuring DR-Master.
If your primary server goes down, switch a DR-Slave to DR-Master using the following steps:
Yes. The relationship between DR-Master and DR-Slave is one-to-many; meaning one DR-Master can connect to multiple DR-Slaves. However, it is not the other way around. You cannot configure one DR-Slave to replicate more than one DR-Master.
A DR-Master will replicate files as soon as a backup is completed or when configuration is modified. Additionally, it also backs up the enter dataset once per day.
No. The rsync protocol sacrifices CPU and local disk I/O in order to save network traffic. This is the reason why we recommend both DR-Master and DR-Slave to be on a fast network. Although Syncrify will only copy modified files between the two machines, it will copy the file in its entirety.
No. DR-Slaves inherit licensing information from DR-Master and therefore, no additional license is required.