Take control of your releases with a free, instant demo.

Launch Now
Enov8 VirtualizeMe (vME)Database virtualization and provisioning

Full database copies. In seconds, in megabytes.

vME ingests one image of a database and turns it into as many isolated, fully working clones as your teams need. Each takes seconds to create and around 40 MB of disk, so dev, test and CI/CD never wait for data again.

A virtual appliance on-premises or in your private cloud. Your data stays inside.

Source image · core_banking (example)2.4 TB
Each clone is a full, writable copy.
Full copies
With vME
~40MBdisk per clone
x100faster provisioning
x10smaller data footprint
0data leaves your network

01The problem

Every application needs five to ten copies of its data.

System test, integration, UAT, staging, production support, plus team and project environments. Copying terabytes for each one takes weeks and costs a fortune in storage.

CadenceTest data and environments take weeks or months to deploy.
CostTens of terabytes need high-performance storage and specialists.
QualityCopies in silos drift out of date and out of step.
ServiceabilityTeams wait on DBAs to refresh, roll back or retest.
SecurityEvery extra copy is another place sensitive data can leak.
Storage calculator · try your numbers
Full physical copies
vME: one image plus clones

Illustrative. Assumes ~40 MB per new clone; a clone grows only with the changes written to it.

02How it works

Ingest once. Clone as often as you like.

Four steps take a database from backup file to a copy any team can use, and every step can be automated.

1

Ingest

Load a copy of the source, such as a backup file or SQL dump, into the vME appliance.

DatabasesFilesCloud
2

Snapshot

Take a point-in-time snapshot. Keep as many as you need, and roll back to any of them.

Point in timeRollback
3

Clone

Create a virtual database from a snapshot. It's a full, working copy in a fraction of the space.

Seconds~40 MB
4

Provision

Hand each person or team their own isolated clone. Refresh it on demand, then tear it down.

Web appAPICLI

03Rollback lab

Break it. Reset it. Test again.

Every clone is isolated, so a destructive test only hurts its own copy. Reset to the snapshot in seconds, without filing a ticket or waiting for a DBA.

Try it: run the test, then roll the clone back.

Clone sit-payments · from snapshot Mon 02:00Clean
ACCOUNTSTATUSBALANCE
Clone size: 40 MB

The clone is identical to the snapshot.

04Under the hood

One appliance. A farm of database containers.

vME is an open virtual appliance (OVA) that runs every clone in its own container slot, on top of a ZFS storage pool. Plug it in like a toaster. Run one, or spread several across domains, clouds and teams.

vME · Virtual farm (example)Click a slot: free → launch · running → stop · stopped → remove
1Pool (drives)
4Sources (ingest)
3Snapshots
6Clones
Container cloud
4Running
2Stopped
19Free
Allocated disk capacity
372 GBIn use
23 TBTotal capacity
240 MBUsed by all clones
ContainersEach clone runs in its own container slot: consistent, light and faster to deploy than virtual or physical machines.
ZFS storageAn advanced volume manager gives vME point-in-time snapshots, clones, compression and pooling.
Database agnosticvME works at the file-system block level, so it doesn't care which database or file type it holds.
Scale outAppliances are designed to be federated across your network, divisions and clouds.
Stays insideData remains on-premises or inside your private cloud.
Housekeeping built inStop, start and remove containers to free slots, with no leftover copies.

05DataOps automation

Data operations as code.

A light web app for day-to-day admin, plus a complete API and CLI you can call from any script or pipeline. Replace manual data requests with scheduled, repeatable jobs.

Fresh data every morning

Snapshot and re-clone overnight in the maintenance window, so every team starts the day on current data.

Nightly window→Snapshot→Refresh clones→Teams

A database per pipeline run

Spin up a clean clone for each build, run the tests, then throw it away.

Pull request→vME clone→Tests→Remove
Works with your CI/CD tools:JenkinsGitLab CI/CDAzure DevOpsAWS CodeDeployCircleCITravis CIBitbucket PipelinesBuddyCodeShip

06Benefits

Faster environments. Smaller bills. Happier teams.

What changes when a database copy takes seconds instead of weeks.

Deploy in seconds

Databases are ready in seconds, so environments stop waiting on data.

Megabytes, not terabytes

Clones share one image and store only their changes.

DevOps as code

Script every data operation through the CLI and API.

No data loss

Data stays on-premises or inside your private cloud.

Tidy environments

Provision and decommission copies on demand, with no leftovers.

No disruption

Everyone gets their own copy, so nobody steps on anyone else.

Scales out

Federate appliances across your network for performance.

Simple lifecycle

Automate how clones are created, stored, refreshed and retired.

Private by design

Pair with Test Data Manager to mask data before any clone is made.

08Supported platforms

Any database. Files too.

vME supports the most popular database types and can be configured for others.

OracleMicrosoft SQL ServerIBM Db2PostgreSQLMySQLMariaDBSybaseMongoDBCouchbaseAWS RDSAzure databasesFiles & directories
See all integrations →
SimplicityEasy to learn and on-board, with a straightforward process for technical and non-technical users.
ComplianceFewer physical copies, and every clone can come from a masked image.
SpeedPush-button databases for every person, team and pipeline.
DevOps-ableContinuous data integration and delivery, automatable operations, repeatable standards.

Stop waiting for test databases.

Book a free 30-minute session. We'll look at your environments and show you vME cloning a database like yours.

What you get
1Free 30-minute session. No cost, no commitment.
2Tailored recommendations for your use case.
3An implementation roadmap you can act on.