Automated backup and recovery for OpenShift, including IBM Maximo Application Suite.
Connect a cluster with an API token. DeployVault deploys an in-cluster agent, discovers your application resources, and backs them up on a schedule. Restore the whole environment or just the parts you need, into the same cluster or a different one.
Already a customer? Releases and patch notes are in the client portal.
From a scheduled backup to a restore in any cluster you point it at.
Set up once. Backups run on their own.
Connect
Give DeployVault an API token for the cluster. No manual install on each node.
Discover
An in-cluster agent finds your application resources and the PVC-backed data behind them.
Schedule
Backups run as scheduled jobs on a cron schedule, to Amazon S3, Azure Blob, or local storage.
Restore
Bring back a full environment or selected resources, into the same cluster or a different one.
Restore exactly what you need, where you need it.
A backup is only useful if the restore fits the situation, whether that's one broken component, a lost cluster, or a test copy of production.
Full environment restore
Rebuild an entire application environment from a backup: its Kubernetes resources and their persistent data together.
Selected resources only
Restore just the components you need, including individual Kubernetes resources and their PVC-backed data, without touching the rest.
PVCs and ODF volumes
PVC-backed data is part of the backup, including volumes on Red Hat OpenShift Data Foundation, such as the attachment storage behind Maximo.
Same cluster or a different one
Recover in place, or into another cluster:
- Disaster recovery after losing a cluster
- Migrations to new infrastructure
- Cluster rebuilds and upgrades
- Test environments built from production backups
Keep Maximo attachments available when Azure Blob isn't.
For IBM Maximo attachments stored in Azure Blob, MazzCache runs an in-cluster cache that keeps recently accessed files local, so a cloud outage doesn't stop people from opening the documents they were just working on.
- Recently used files stay local. Cached attachments are served from inside the cluster.
- Outages don't block work. If Azure Blob becomes temporarily unreachable, cached attachments remain available and new uploads are accepted into a durable queue.
- Sync catches up on its own. When connectivity returns, queued files are synchronized automatically and verified for integrity.
Specifications.
Deployed and adapted in your environment. Ask about anything not listed here.
- Platform
- Red Hat OpenShift 4.20+
- Tested with
- IBM Maximo Application Suite 8.x and 9.x, including Manage
- Setup
- API token · in-cluster agent · auto-discovery
- Backups
- scheduled jobs (cron)
- Restore
- full environment or selected resources · same‑cluster or cross‑cluster
- Persistent data
- PVC-backed data, including ODF-backed volumes
- Storage targets
- Amazon S3 · Azure Blob · local storage
- Access
- SSO via SAML, OIDC, LDAP
- MazzCache add-on
- Azure Blob attachment cache · outage read access · queued writes · integrity-verified sync
- Updates
- versioned releases with patch notes, delivered through the client portal
Looking for backups and deploy history for ordinary servers and apps? That's the hosted DeployVault at deployvault.xyz.
Talk through your clusters.
Tell us your OpenShift version, what runs on it, and where backups should live. The engineer who builds DeployVault replies within one business day.