yuzuy software · Failover / Failback
Failover for Qumulo in one checked run, and back.
yuzuy switches all replication relationships of a cluster pair to the other side together, with checks at every step. Failback brings them home the same way. Qumulo replicates the data; yuzuy orchestrates everything around it.
How it works
The same steps, in the same order, every time.
Failover tends to happen when things are hectic. yuzuy knows every step and runs them for you, instead of a checklist of CLI commands and API calls.
- Running replication jobs finish where possible, and yuzuy saves the replication state.
- Source directories on the primary become read-only, and their shares are renamed.
- The selected floating IPs move to the secondary; networks are created there if needed.
- Replicated directories on the secondary become writable. Clients carry on.
Checks run throughout, and the web interface shows the status of every step.
| Start | One click in the web interface, or one API call, for example from your monitoring |
| Scope | All replication relationships of a relation switch together |
| Duration | Typically about 5 seconds; running transfers get a configurable timeout (default 1 minute) |
| Network | IP failover moves floating IPs to the secondary (mostly NFS); DFS failover removes them on the primary (SMB via DFS) |
| Failback | Keep data (default), replicate changed data back, or discard changes |
| Clusters | Any number of clusters and relations; cross-replicating pairs supported |
| Record | Progress and history per relation |
| Cost | Included in the yuzuy subscription |
See it in action
A planned and an unplanned failover, step by step.
No half measures
No test mode, on purpose.
yuzuy has no dry run and no partial failover. A test that skips steps proves little and gives a false sense of safety. A planned failover is the real test, and yuzuy makes it a routine one.
Prepare once
What to set up outside yuzuy.
- Separate FQDNs for NFS, SMB without DFS and SMB via DFS
- A plan for distributing floating IPs (older Qumulo Core versions limit them per node and VLAN)
- A DFS cache duration that suits your failover
- Target directories named after their source cluster
- Admin rights on both clusters
“The collaboration between Qumulo and yuzuy has not only met but exceeded the hospital’s expectations.”
Alex Weber
Storage Systems Engineer, Platform Services
Universitätsspital Basel
Universitätsspital Basel has run failover and failback for its Qumulo clusters with yuzuy since 2023.
Background
Read more on the topic.
How to fail over Qumulo Continuous Replication for SMB and NFS clients
The steps of a planned and an unplanned failover, the failback, and where failovers go wrong.
Qumulo failover with DFS namespaces
Why DFS fails over on its own but rarely fails back, and how to bring SMB clients home reliably.
Keeping shares, exports and quotas in sync between replicated clusters
Replication copies data, not configuration: by hand, by script, or automatically.
FAQ
Questions admins ask.
Are there any limitations to the number of floating IP addresses that Qumulo or yuzuy have?
Qumulo limits the number of floating IP addresses per storage node per VLAN to 10. This applies especially in failover scenarios where a cluster with many nodes fails over to one with fewer nodes, as typically all floating IPs from the primary cluster must be transferred to the secondary.
In failover relationships with significant differences in the number of nodes between clusters, there’s a risk of exceeding the 10 floating IP limit on the secondary cluster, leading to errors. yuzuy checks for this during configuration and alerts you. Proper planning of floating IP distribution from the start is recommended to avoid DNS changes later. yuzuy also assists with a planning tool for IP address distribution.
Link to this answerHow long does a failback take?
During a failback, you can choose to replicate new data back to the primary cluster or discard it. Typically, new data is replicated back, with the duration depending on the amount of data and performance. Clients remain connected to the secondary cluster without interruption. Once the primary cluster is up to date and in continuous replication state, the final step of the failback takes only a few seconds.
Link to this answerWhat happens to replication data in flight when initiating a failover?
For planned failovers and failbacks, yuzuy waits for replication to complete before proceeding. The timeout for this can be configured, and if necessary, yuzuy can cancel the ongoing replication and force a failover. In the event of a cluster outage, some data in flight may not have been replicated yet.
Link to this answerNo answer matches your search. Ask us directly, we reply within one business day.
