Keep institutional memory
Years of customer conversations, decisions and approvals remain part of the company instead of becoming collateral damage when a server fails.
RayBackup continuously protects messages, changes and business history while Zimbra keeps running. No invasive hooks. No traditional backup window. Your storage, your control.
Business decisions rarely arrive as neat database rows. They arrive as conversations, approvals, attachments, agreements, questions, answers and years of context.
When a mailbox disappears, part of the company disappears with it.
RayBackup is designed to run alongside Zimbra, capture changes continuously and write recovery data to storage you control.
Keeps doing its job.
Captures, organizes and verifies recovery data.
Filesystem, NAS/NFS or S3-compatible storage.
No mailboxd modifications, fragile patches or product-specific storage appliance.
Use storage that makes sense for your environment and your budget.
Protection follows change instead of waiting for tonight’s scheduled job.
Four boringly clear steps. Backup infrastructure does not become more reliable because someone gave every component a mysterious product name.
Changes are tracked continuously, reducing the gap between activity and protected recovery data.
Content and history are stored independently from the live Zimbra server.
Consistency checks help detect gaps instead of quietly turning them into tomorrow’s surprise.
Restore individual content or rebuild logically after a larger failure.
Years of customer conversations, decisions and approvals remain part of the company instead of becoming collateral damage when a server fails.
Know the difference between data that was merely captured and recovery points that are actually restorable and verified.
The backup repository lives in storage chosen by your team. You keep control of cost, location and operational policy.
A failed Zimbra host should be a recovery job, not an archaeological expedition through old disks, scripts and half-remembered procedures.
Continuous protection and scheduled verification are designed to replace repetitive manual checks with useful recovery signals.
RayBackup is being built around source isolation, content-addressable storage, rebuildable local indexes and a repository that remains useful even after the original Zimbra host is gone.
Changes are captured continuously instead of depending only on a scheduled full-backup window.
No invasive mailboxd modifications, no patch dependency and no need to rebuild the backup architecture after every ordinary upgrade.
Write to mounted filesystems or S3-compatible storage. Keep your repository where your operational model says it belongs.
SHA-256 based object storage supports deduplication and integrity verification without multiplying MIME content for moves, tags and flags.
The repository is designed to remain the source of truth. Local catalog data can be rebuilt instead of becoming a hidden single point of failure.
Reconstruct useful mailbox state instead of requiring a physical clone of the original server, database and internal IDs.
The change is durably protected outside the volatile source flow.
The required objects have been processed into a valid recovery state.
Recovery state has been checked for consistency against the source.
RayBackup is built around BYOS. Use a simple mounted filesystem when simplicity matters, or S3-compatible object storage when stronger isolation, scale and storage-enforced immutability matter more.
Local disks or mounted volumes for straightforward deployments.
Keep the repository on infrastructure your team already operates.
Use compatible platforms such as RustFS, MinIO or Ceph-based storage.
Use supported S3-compatible cloud providers and keep storage separate from Zimbra.
When the backend supports Object Lock, WORM or retention policies, RayBackup can use and verify those capabilities. On ordinary filesystems, integrity remains verifiable but physical immutability depends on the storage itself.
A backup should not need the failed server to recover from the failed server.
RayBackup is being designed so a valid repository plus a fresh installation is enough to inspect, rebuild the local catalog and recover supported Zimbra data into a new environment.
RayBackup uses BYOS pricing: your team provides the repository, so the subscription stays focused on the software that protects and restores Zimbra.
All early-access commercial tiers use the same product philosophy.
30-day commercial trial
Annual billing includes the equivalent of two months free. Storage is supplied by the customer.
Join the Early Access WaitlistJoin the RayBackup early-access list. We’ll use these details to prioritize environments, versions and deployment sizes as the product moves toward release.