Back up Oracle to anywhere your data needs to live.
Revera streams RMAN directly to your storage through its own media library, separates who can back up, restore and change retention, and proves every database is recoverable.
One library between RMAN and every destination
Oracle Database
RMAN runs your backup scripts the way it does today.
Revera SBT library
The media management interface RMAN already uses, implemented by Revera. Direct stream, with no staging copy.
Oracle backup and recovery you can prove.
Native streaming, any storage
Revera's own SBT media library lets RMAN write straight to Azure, Amazon S3, S3-compatible storage or disk. No azcopy, no BlobFuse and no staging disks, on backup or on restore.
No one wipes production by accident
Backup, restore and retention are separate roles. Every restore needs a signed, single-use authorization bound to one database and one host.
Immutable when it matters
Revera never deletes a piece that storage has locked, and keeps the RMAN catalog consistent. Proven on Azure immutable containers and S3 Object Lock.
Recovery you can prove
Health is read from the real recovery chain, with archive-log gap detection and scheduled recovery tests that report the RTO achieved and the RPO demonstrated.
The DBA stays in control
Generate an RMAN script from a form, edit and approve it, and Revera runs exactly that, versioned. RMAN and your Recovery Catalog stay authoritative.
Zero-trust by design
Outbound-only agents over mutual TLS, structured commands only, secrets only in your vault, and an insert-only audit trail that names every actor.
Validated end to end
The full RMAN lifecycle
Backup, crosscheck, restore, recover and open, exercised end to end.
Real storage, not mocks
Live test suites run against real cloud storage.
Oracle's own test utility
The SBT test utility that Oracle supplies passes.
Built as if someone were already inside.
Your backups are your last line of defense. Revera was designed around one question: if a console login, a server or a database host were compromised, could it still hurt your data or your recovery? Each control below is built and tested, and exercised on real Oracle servers.
Nobody restores over production alone
A restore needs a signed authorization from one person and execution by a different person. The authorization is single-use, expires in hours and is tied to one database and one host. The script that runs is the one that was approved.
The server cannot make your Oracle hosts run anything it likes
Every backup command and restore is signed over exactly what will run. Each agent pins the server's verification keys at enrollment and checks the signature before it touches Oracle.
No inbound doors on your database servers
Agents connect out over mutually authenticated TLS, and the server never connects in. Each agent has its own certificate, revoked instantly when needed: a revoked host is cut off within about half a minute.
Secrets in a vault, not in files
Passwords and keys are not in configuration files, databases or logs. Revera includes an encrypted secrets service whose root key is never written to disk and which starts locked after a reboot. It also works with Azure Key Vault, AWS Secrets Manager and HashiCorp Vault.
Least privilege, down to the operating system
On Linux the agent is not root, and may run only one root-owned, validating wrapper as the Oracle user. On Windows, RMAN runs under a dedicated low-privilege account. Passwords never appear on a command line.
Immutable means immutable
Backups stream directly from RMAN to your storage, with no staging copy and no intermediary tool. Revera respects object-lock and immutability policies, proven against a real immutable Azure container and a real S3 COMPLIANCE-mode bucket.
Every action has a name on it
Every change is recorded with the real person's identity, in an audit trail that is insert-only and enforced by the database. Deactivate or demote someone and it takes effect at once.
Licensing that respects your uptime
Licences are verified offline. Revera never phones home, no data about your estate leaves your site, and a licence never stops a backup.
Tested the hard way
Revera has been reviewed and tested by Nadira's own engineering. The review covered the management server, the agents, the storage library written in C, the secrets service, the installers and the web interface, and every Critical, High and Medium finding was fixed. Restore authorization, certificate revocation, session revocation, enrollment protection and the Oracle-host privilege boundary were then exercised against real Linux and Windows Oracle servers, with real backups to disk, Amazon S3 and Azure Blob. A release is refused if it contains a known reachable vulnerability.
38 years of Oracle, in one library.
Revera's core media library decides whether RMAN talks to your storage natively. It was engineered by an Oracle specialist who has lived in Oracle databases for 4 decades, delivering business continuity and HA/DR for large global enterprises.
Check Revera against your environment.
Supported versions and platforms depend on the release. Email us what you run and we will send the compatibility and supportability matrix as a one-page flyer.
Talk to us about your Oracle estate.
Email us your Oracle versions and where backups need to land. We reply to arrange a walkthrough.