Definition
What is disaster recovery for Sitecore Experience Commerce?
Disaster recovery for Sitecore Experience Commerce is the set of systems and decisions that keep a Sitecore XC store taking orders when its primary environment fails.
A traditional plan restores the store from a backup onto rebuilt infrastructure. That takes hours or days and loses everything since the last snapshot. A live replica approach keeps a second, current copy of the store running and isolated, so failover is a switch rather than a rebuild.
The two approaches answer different questions. A backup answers "can we get the data back?". A live replica answers "can customers keep buying while we deal with this?". For a Sitecore XC store the business depends on, the second question is the one that costs money every minute it stays unanswered.
Why now
Why Sitecore XC stores need disaster recovery now
Sitecore Experience Commerce is stable software with a large ecosystem, and that ecosystem is where the risk lives. The store depends on hosting, dependencies and integrations that each change on their own schedule, and any of them can take it down.
The facts that matter for a Sitecore XC store today:
- Sitecore did not release Experience Commerce for Sitecore Experience Platform 10.4. XC 10.3 is the last version.
- XC 10.3 remains under Sitecore's product lifecycle for corrective support, which covers fixes and some third-party compatibility, but no new functionality.
- Sitecore's commerce direction is OrderCloud, a separate headless SaaS product with a different data model.
Failure modes
Where Sitecore XC stores actually fail
Disaster recovery planning tends to imagine fires and floods. Real Sitecore XC outages are more mundane and more frequent. The failure modes that a plan for Sitecore Experience Commerce has to cover:
- A vulnerability in Sitecore, the commerce engine, Windows Server or SQL Server that corrective support does not reach in time.
- A failed content delivery, commerce engine or SQL node in a topology few people still know how to rebuild.
- Ransomware moving through Active Directory into the Sitecore estate and its backups.
- An upgrade of Sitecore XP that leaves XC behind.
- The backup itself: stored on the same host or account, encrypted alongside production, or restored with the intrusion still inside it.
The replica
Why a live replica beats restoring Sitecore XC from backup
Four things change when the store has a live, isolated copy instead of a snapshot on a shelf.
Zero recovery time, because nothing is recovered
The replica is already running. When the primary fails, customers are switched to the copy in seconds. There is no rebuild, no restore window and no scramble to find the person who knows how the store was configured.
Zero data loss, because the copy is current
The replica follows the primary continuously rather than nightly. Orders placed on the replica during an outage are captured and reconciled back when the primary returns.
Ransomware cannot follow
The replica is isolated from the primary's hosting account, network and credentials. An attacker who owns production has no path into the copy, and you never restore from a snapshot that might carry the infection with it.
The vendor's outage is not your outage
When a hosting provider, a cloud region or a dependency fails, the replica sits outside that blast radius. Customers keep buying while someone else fixes their problem.
How it works
How the Jestr replica works for a Sitecore XC store
Jestr does not re-implement Sitecore Experience Commerce. It runs a copy of your actual store, kept current and kept apart.
Jestr builds a live copy of the store
Jestr replicates the Sitecore XC store as it actually runs: the application, its data and its configuration, at the exact version and with the exact dependencies the primary uses. Nothing is re-implemented, so what customers see on the replica is the store they know.
The copy stays current and stays isolated
The replica follows the primary continuously, at a known-good state, so an update that breaks production does not break the copy. It runs on Jestr's side of the outage with no shared credentials, network or identity, so a compromise of the primary stops at the primary.
When the primary fails, you switch
One action moves customers to the replica. They browse the same catalog, sign in to the same accounts and check out. Orders are captured on the replica. The switch works even when your own network is the thing that is down.
When the primary is back, you reconcile and switch back
Orders and account changes made on the replica are reconciled into the restored primary. You choose when to switch back. Nothing was lost and no backup was restored.
What the replica captures for Sitecore Experience Commerce
- Catalog, inventory, pricing and promotion data alongside the Sitecore content and media that render the storefront.
- Customer accounts, carts and the order path, with orders captured during an outage and reconciled afterwards.
- The exact XP and XC runtime, kept current and isolated from the primary.
- Separation from the primary's domain, credentials and network.
Side by side
Backup and restore vs a live Sitecore XC replica
The same outage, handled two ways.
| Dimension | Traditional backup and restore | Live Jestr replica |
|---|---|---|
| Time until customers are served again | Hours to days: provision, restore, reconfigure, test | Seconds: the replica is already running |
| Data lost | Everything since the last snapshot, often a full day | Nothing: the replica is current, and changes made during the outage are reconciled back |
| Ransomware | Backups often sit in the blast radius, and a restore can bring the infection back | The replica is isolated; you switch to it instead of restoring into the compromise |
| Vendor or hosting outage | You wait for the provider | The replica sits outside the provider's failure domain |
| Rehearsal | Rarely tested, because a full restore is disruptive and slow | Switching to the replica is routine and can be rehearsed any time |
| Who does the work at 3am | Your team, from a runbook that may be out of date | The switch is one action; the copy was built and kept current in advance |
FAQ
Frequently asked questions
Does Jestr replace our Sitecore XC backups?
No. Keep backups for archives, audits and long-term retention. Jestr replaces the part of the plan that backups are bad at: keeping the store selling while the primary is down, without a restore window and without data loss.
Can customers actually check out on the replica during an outage?
Yes. The replica runs the real Sitecore XC store, including the cart and checkout path. Orders placed during the outage are captured and reconciled to the primary when it returns. Payment and fulfillment integrations are configured as part of onboarding.
How is ransomware kept out of the replica?
The replica shares nothing with the primary that an attacker could use: no credentials, no network path, no hosting account. Replication is one-way and validated, so an encrypted or tampered primary does not propagate. You switch to a clean copy instead of restoring into the compromise.
How fast is failover?
Seconds. The replica is already running and current, so failover is the act of pointing customers at it. There is no provisioning, restoring or reconfiguring in the critical path.
Does this work with managed Sitecore XC hosting?
Yes. The replica sits outside the hosting provider, whoever it is. That is the point: when the host has a bad day, the store does not.
