Definition
What is disaster recovery for Drupal 7?
Disaster recovery for Drupal 7 is the set of systems and decisions that keep a Drupal 7 site serving visitors when its primary environment fails.
A traditional plan restores the site 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 site 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 visitors keep working while we deal with this?". For a Drupal 7 site the business depends on, the second question is the one that costs money every minute it stays unanswered.
Why now
Why Drupal 7 disaster recovery changed on January 5, 2025
Drupal 7 ran a remarkable share of government, university and non-profit websites, and a large number of them are still live. Since January 5, 2025 those sites have been running without a security team behind them. Disaster recovery for Drupal 7 is now about surviving the incident that the patch would have prevented.
The facts that matter for a Drupal 7 site today:
- Drupal 7 reached end of life on January 5, 2025, after several extensions of the original date.
- The Drupal security team no longer publishes advisories or fixes for Drupal 7 core or contributed modules. Paid extended support exists from a small number of vendors.
- Drupal 8 reached end of life in November 2021, so 8 is not a stopping point either. Drupal 10 and 11 are the supported line.
- Drupal 7 to 10 is a migration, not an upgrade: the theme layer, the module ecosystem and much of the site-building approach changed completely.
Failure modes
Where Drupal 7 sites actually fail
Disaster recovery planning tends to imagine fires and floods. Real Drupal 7 outages are more mundane and more frequent. The failure modes that a plan for Drupal 7 has to cover:
- A newly discovered vulnerability in Drupal 7 core or a popular contributed module with no fix coming.
- A hosting provider retiring the PHP version Drupal 7 depends on.
- A compromised site used to host malware or spam, with the reputational cost that carries for public bodies and universities.
- Ransomware encrypting the site and its backups together.
- 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 Drupal 7 from backup
Four things change when the site 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, visitors 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 site was configured.
Zero data loss, because the copy is current
The replica follows the primary continuously rather than nightly. Changes made 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.
Unpatched is survivable when it is not a single point of failure
Drupal 7 will not receive another vendor fix. The replica does not change that, but it changes the cost of the next vulnerability: the exposed primary can be taken down to contain an incident while the isolated replica keeps visitors working.
How it works
How the Jestr replica works for a Drupal 7 site
Jestr does not re-implement Drupal 7. It runs a copy of your actual site, kept current and kept apart.
Jestr builds a live copy of the site
Jestr replicates the Drupal 7 site 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 visitors see on the replica is the site 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 visitors to the replica. They open the same pages, sign in and keep working. Changes 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
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 Drupal 7
- Nodes, taxonomies, files, views and the theme, so visitors and editors see the same site on the replica.
- Forms, logins and the roles around them, so the site keeps functioning.
- The Drupal 7 runtime and module set kept current and isolated from the internet-facing primary.
- Separation from the primary's hosting credentials and network.
Side by side
Backup and restore vs a live Drupal 7 replica
The same outage, handled two ways.
| Dimension | Traditional backup and restore | Live Jestr replica |
|---|---|---|
| Time until visitors 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 |
| Unpatched platform | Every new vulnerability is permanent and the only copy is exposed | The exposed primary can be contained while the isolated replica serves visitors |
| 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 Drupal 7 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 site available while the primary is down, without a restore window and without data loss.
Can visitors sign in and work on the replica, or is it a static copy?
It is the real Drupal 7 site, not a snapshot of its pages. Logins, forms and integrations work. Changes made during the outage are captured and reconciled when the primary returns.
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 visitors at it. There is no provisioning, restoring or reconfiguring in the critical path.
Is it safe to keep running Drupal 7 at all now that end of life has passed?
Safer than it looks, if the exposure is managed. The replica does not patch the software, but it means the exposed primary is no longer the only copy. When a vulnerability is disclosed, the primary can be restricted or taken down to contain it while the isolated replica keeps visitors working. Unpatched is survivable when it is not also a single point of failure.