In your current setup
ABV goes between storage you already have. Nothing has to be migrated.
Bardin Gate ABV
How ABV works
One copy cycle
Read
The appliance connects to the production side and reads the approved backup objects. The recovery side is disconnected.
Disconnect
It disconnects from the production side completely. For a moment it is connected to neither.
Write
It connects to the recovery side and writes the data to the storage you chose.
Verify
It checks the copy's integrity, records the result and disconnects again.
No route between the two sides survives the cycle. When the appliance is idle, the recovery repository is connected to nothing outside it.
Storage on each side
| Side | What it can be |
|---|---|
| Production | Your backup repository, a NAS, a file share over SMB or NFS, or S3-compatible object storage |
| Recovery | Dedicated storage, an existing NAS, local or removable disks, or S3-compatible object storage |
The two sides need not use the same technology. ABV keeps only the working space a transfer needs and is never the permanent home of your backups.
Ways to deploy it
With dedicated storage
ABV is delivered with recovery storage sized for your retention and speed.
On-premises to object storage
ABV copies from local repositories to S3-compatible object storage on the recovery side.
Talk to our specialists
Tell us about your environment and what you need. One of our specialists will answer you.