Availability & recovery
If a zone fails
Section titled “If a zone fails”The store database is zone-redundant. A standby instance runs in a different Azure availability zone and takes over if the primary’s zone becomes unavailable.
Read from Azure on 9 August 2026:
| Reading | Value |
|---|---|
| High availability mode | Zone-redundant |
| State | Healthy |
| Standby availability zone | 1 |
| Tier / size | GeneralPurpose · Standard_D2ds_v5 |
“Healthy” is the part worth pausing on. A high-availability setting that is configured but not healthy protects nothing, and the difference is invisible unless somebody reads the state rather than the setting.
If data needs to be recovered
Section titled “If data needs to be recovered”The database supports point-in-time restore — recovering the database to a chosen moment rather than only to the last nightly copy.
We have tested it, and here is the outcome
Section titled “We have tested it, and here is the outcome”A point-in-time restore was run end to end as a drill, not assumed from the feature being available.
| Drill | Result |
|---|---|
| Point-in-time restore, performed end to end | PASS |
We publish the outcome, because “we take backups regularly” and “we have restored from a backup” are different statements, and only the second one is evidence. A backup nobody has restored is a belief.
The backup you can run yourself
Section titled “The backup you can run yourself”Recovering from your own mistake — a bad import, a bulk edit that went wrong — should not depend on our response time. CIQRA provides merchant-initiated backup and restore, so it does not require a support ticket.
This page deliberately does not walk you through the screen. Not because the capability is in doubt, but because a click-path is only worth publishing when it has been checked against the admin as it is today, and that check has not been done for this article. When it is, the steps go in the relevant product guide — and this page will link to it.
What this page does not say
Section titled “What this page does not say”- It does not publish RTO or RPO targets. Those numbers have not been measured, and a recovery-time promise that nobody has timed is worse than no promise: it is one a merchant might plan around.
- It does not claim continuous availability. Zone redundancy protects against the loss of one availability zone. It is not a guarantee of uninterrupted service, and no configuration is.