Database Cluster Recovery Add-on for PaaS
The Database Cluster Recovery add-on runs a comprehensive diagnostic of a MySQL, MariaDB or Percona cluster on MassiveGRID PaaS, identifies broken replication, split-brain or lost quorum, and can repair the cluster automatically. It turns the most stressful database incident into a dashboard action.
Both buttons open the MassiveGRID PaaS dashboard with Database Cluster Recovery pre-selected. The trial needs no credit card.
Database Cluster Recovery Package Facts
| Attribute | Value |
|---|---|
| Package | Database Cluster Recovery |
| Type | Add-on (attaches to an existing environment) |
| Category | Add-ons & Utilities |
| Software vendor / project | Jelastic / Virtuozzo (package) |
| Licence | Open-source add-on |
| Runtime / stack | Add-on for MySQL, MariaDB and Percona clusters deployed from the marketplace |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Free add-on; the host environment is billed per use from $2.46/month |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is Database Cluster Recovery?
Replicated databases fail in specific, well-known ways: a replica stops applying changes after a conflicting write, a Galera cluster loses quorum after a network partition, a node restarts with a stale data set and refuses to rejoin. Fixing these by hand requires knowing which node has the most advanced state and issuing the right sequence of commands, under time pressure, without making things worse.
This add-on encodes that knowledge. It inspects every node's replication status, GTID position, cluster state and error logs, produces a readable report, and offers a recovery action tailored to the topology: restart replication from the correct position, bootstrap the most advanced Galera node and rejoin the others, or resynchronise a stale node. It works with the clusters deployed by the MySQL/MariaDB/Percona Cluster and multi-region packages.
What Database Cluster Recovery Changes in Your Environment
Add-ons run against an environment you already have. Nothing is rebuilt, and the change can be removed from the same dashboard.
- Cluster diagnostic: Checks replication threads, GTID positions, Galera cluster size and state, and node connectivity, and reports findings.
- Automatic recovery: One-click repair that chooses the safe recovery path for the detected problem and topology.
- Scheduled checks (optional): Run the diagnostic periodically and alert if the cluster is degraded.
- Logs and reports: Detailed output of each diagnostic and recovery run, available in the dashboard.
Why Teams Choose Database Cluster Recovery
Understands every marketplace topology
Primary-secondary, primary-primary, Galera, Percona XtraDB and MySQL InnoDB Cluster.
Safe by design
Picks the node with the most advanced data set as the source of truth before repairing.
Minutes, not hours
Recovery that would take an experienced DBA an hour runs in a few minutes.
Proactive monitoring
Scheduled diagnostics catch silent replication breaks before users notice stale data.
How to Add Database Cluster Recovery on MassiveGRID PaaS
Attaching the add-on takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the Database Cluster Recovery add-on pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Pick the target environment
Choose the environment, and where relevant the node layer, that Database Cluster Recovery should attach to, then confirm. The add-on configures itself on the running nodes without a redeploy.
Who Runs Database Cluster Recovery on PaaS
Teams without a full-time DBA
Developers operating replicated databases who need a safety net.
High-availability deployments
Galera and multi-region clusters where quorum loss must be resolved quickly.
After maintenance or incidents
Verifying cluster health after upgrades, restarts or network events.
Why Run Database Cluster Recovery on MassiveGRID PaaS
Built for uptime. Database Cluster Recovery runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.
Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet Database Cluster Recovery environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.
Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.
No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.
Related on massivegrid.com: Support Plans.
Database Cluster Recovery Questions
More from the Marketplace
Packages that are often deployed alongside Database Cluster Recovery, or that solve the same problem a different way. Browse all 84 packages.
Deploy Database Cluster Recovery Today
Start the free 14-day trial and have Database Cluster Recovery running in minutes. No credit card required.