- BFSIBanking, Financial Services & Insurance
- HealthcareComing soon
- ManufacturingComing soon
- Retail & E-CommerceComing soon
Arcserve Replication and High Availability
Your database server fails at 2 a.m. Users shouldn’t wait for someone to restore it — Arcserve Replication and High Availability streams every byte-level change from your Windows and Linux servers to a replica you run, and a heartbeat check switches users over when the master fails — physical, VMware, Hyper-V, EC2 or Azure.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
The Arcserve platform family
This page covers Arcserve Replication and High Availability — the continuous replication and failover product, with Assured Recovery as a licensed module. The rest:
Quick facts
30-second orientation- Product
- Continuous, byte-level replication with heartbeat failover for Windows and Linux servers
- Maker
- Arcserve, LLC, Eden Prairie, Minnesota; privately held, CEO Chris Babel since May 2024
- Status
- Version 18.0 since 2019; Service Pack 3d (September 2025) added Windows Server 2025
- Price
- Not published and not on Arcserve’s e-store; quoted per server through partners
- Licence
- Key built from OS, Replication or HA, applications and hosts; Assured Recovery is a module
- Platforms
- Physical, VMware, Hyper-V, Amazon EC2 and Azure; Exchange, SQL, IIS, SharePoint, Oracle
- Recovery
- Arcserve claims RPOs and RTOs of seconds; the replica checks the master every 30 s by default
- Rewind
- Data Rewind points and manual bookmarks roll a replica back to before corruption
- India
- Arcserve hosts no copy; the replica is a server you place, with offices in Hyderabad and Bengaluru
- In India via
- TechBag — scenario design, quote in INR with GST, first switchover test
Understand replication and high availability before you buy it
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
What is replication with high availability?
A replica server receives every change as it happens, and a heartbeat moves users to it when the main server fails.
Nightly backups and a manual restore vs Arcserve RHA — the honest table
What consolidation actually replaces, dimension by dimension.
| Dimension | Nightly backups and a manual restore | Arcserve Replication and High Availability |
|---|---|---|
| Data lost in a failure | Everything since last night’s backup | What was in flight; Arcserve claims seconds |
| Who starts the failover | An engineer, once they are reached | A heartbeat check, after a set timeout |
| How users reconnect | New addresses sent round by email | DNS, IP or computer-name redirection |
| Undoing corruption | Restore and re-enter a day’s work | Rewind the replica to a point or bookmark |
| Proving the DR plan | A weekend outage once a year | An Assured Recovery test while replication spools |
| What it is NOT | — | Backup, a hosted DR site, or a published price |
The cheapest test is one server: replicate it to a spare VM, run a planned switchover and switchback, and time both against your RTO.
The five pieces of the platform
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
Engine
An Engine service runs on every server in a scenario, picks up byte-level file-system changes on the master and writes them to the replica, over port 25000 by default.
Control
The Control Service holds scenario definitions and can itself be protected by a standby copy; the Manager and Overview Page are where you create, run and monitor scenarios.
Scenarios
Each scenario pairs a master with one or more replicas for files, an application such as SQL Server or Exchange, or a full system, as a replication or a high-availability job.
Heartbeat
The replica pings the master, its services and databases every 30 seconds by default; after a 5-minute timeout it switches over and redirects users by DNS, IP or computer name.
An Engine on every server and a heartbeat on the replica — byte-level changes streamed, users switched over on failure.
Nine capabilities. Replicate, fail over, rewind.
Arcserve RHA keeps a live replica of each critical server and moves users to it when the master stops answering.
Changes sent as they happen
After a first synchronisation, each byte-level change on the master is replicated asynchronously to the replica, without a schedule.
App-aware scenarios
Ready scenario types cover Exchange, SQL Server, IIS, SharePoint, Oracle and Hyper-V, plus custom applications you define.
No VPN between the sites
Data moves between local and remote servers with AES-128, AES-256 or custom encryption, so a VPN tunnel is not required.
Detects a dead master
Ping, service and database checks run every 30 seconds by default; when all fail for 5 minutes the master is declared down.
Users follow the switch
DNS redirection, Move IP or Switch Computer Name points clients at the replica, so they reconnect without new addresses.
Reverse, then return
A backward scenario replicates from the replica to the old master, then a switchback hands the active role home again.
Back to before the damage
Rewind points and your own bookmarks let you roll the replica back to a moment before corruption or ransomware struck.
Test the replica live
A test brings the replica up while master changes queue in a spool, then rewinds it and applies the queue when you finish.
Measure before you commit
Assessment Mode reports bandwidth use and compression for a scenario without replicating anything, to size the WAN first.
Watch Arcserve RHA in action
The RHA 18.0 launch webinar, a two-minute product overview and a short look at continuous data protection. All from Arcserve’s official channel, recorded in 2019; 18.0 is still the current line.
Arcserve RHA 18.0 Launch Webinar
The launch of 18.0, still the current line; later service packs changed platforms, not the design.
Arcserve Replication & High Availability
A two-minute overview of continuous replication and automatic failover in RHA.
What “always on” looks like: Continuous data protection with Arcserve RHA
A one-minute look at RHA’s continuous data protection and point-in-time rollback.
Want a live, India-context walkthrough for your environment?
Book a guided demo →A restore takes as long as it takes. RHA keeps a replica ready and switches to it.
Here’s what genuinely sets it apart — and exactly where it stops.
Failover that does not wait for a person
In a high-availability scenario the replica checks the master’s ping, services and databases every 30 seconds by default. If every check fails for the timeout, 5 minutes by default, RHA can switch over on its own and move users by DNS, IP or computer name. Arcserve claims RPOs and RTOs of seconds; prove yours in a test.
One tool across servers, hypervisors and clouds
RHA protects Windows and Linux systems whether they are physical, on VMware or Hyper-V, or in Amazon EC2 or Azure, with scenario types for Exchange, SQL Server, IIS, SharePoint and Oracle. Arcserve built it for dissimilar hardware, so an old physical database server can fail over to a VM elsewhere.
Rewind past corruption, test without a pause
Continuous replication copies damage as faithfully as data, so RHA records rewind points and your bookmarks; you can roll the replica back to just before the bad write. Assured Recovery, a separately licensed module, brings the replica up for a test while master changes wait in a spool, then rewinds it.
Where it stops
There is no public price, and the e-store does not sell it. The 18.0 line dates from 2019, kept current by service packs, and the newest English video is from that year. Groups switch over together, but there are no multi-step runbooks across sites. It is not backup, Arcserve hosts no DR site, and a rewind cannot be replayed forward.
The numbers behind the platform
What your Arcserve RHA rollout looks like
Pick the servers that cannot stop
List the application servers where minutes of outage hurt, note their OS and apps, and decide Replication or HA for each.
Measure the link first
Run Assessment Mode on the busiest scenario to see bandwidth and compression before you buy the WAN or the licences.
Build the replica and scenario
Provision the replica in your Indian site or cloud account, install Engines, and choose DNS, IP or name redirection.
Switch over and switch back
Run a planned switchover, let the backward scenario sync, switch back, and time each step against your RTO target.
Turn on rewind and drills
Set Data Rewind retention, add bookmarks before risky changes, and schedule Assured Recovery tests if you license it.
The review scoreboard
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
Quick poll — what’s driving your evaluation?
Talk to an advisor“Our core SQL Server failed at 2 a.m. and RHA switched to the replica before the on-call engineer had logged in.”
“We protect an old physical Oracle box with a VM replica in another city. Dissimilar hardware was the reason we chose it.”
“A bad script wiped a file share. We rewound the replica to a bookmark set that morning and copied it back by noon.”
“Run Assessment Mode first. It showed our branch link could not keep up with the ERP database during month-end.”
“DNS redirection worked well; Switch Computer Name needed a reboot on one older server, so test each method you use.”
“It does the job, but the console feels dated and the quote took weeks. We wanted a price list for budgeting.”
Where everyone sits — the grids
Analyst firms bury this view behind paywalls, and G2 retired its Grid. So here’s TechBag’s synthesis of the disaster recovery market — tap any vendor to see why it sits where it does.
TechBag Disaster Recovery Grid
Execution strength vs product vision — the classic market map, minus the paywall.
Quoted per server through partners; no public price.
Workload Breadth × Failover Automation
The grid nobody publishes — how many kinds of server, hypervisor and cloud a product protects vs how much of the failover runs without a person.
Physical, three hypervisor or cloud targets, six app types; heartbeat switchover.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Arcserve RHA vs the continuous replication field
Against HPE Zerto Software, NAKIVO Real-Time Replication, Veeam CDP, Azure Site Recovery and AWS Elastic Disaster Recovery — on workloads, RPO, failover, failback, price, ransomware defence, support and India.
| Dimension | Arcserve Replication and High Availability | HPE Zerto Software | NAKIVO Real-Time Replication | Veeam CDP | Azure Site Recovery | AWS Elastic Disaster Recovery |
|---|---|---|---|---|---|---|
| What it is | Server HA + replication | Journal-based DR suite | VMware CDP add-on | CDP inside the platform | Azure’s managed DR | AWS’s managed DR |
| Deployment | Engine on each server | Per-site appliances | Filter + journal VA | Your own servers | Vault, on-prem appliance | Agent + staging subnet |
| Workloads covered | Physical, VMs, clouds | vSphere and clouds | vSphere 7.0–9.1 only | vSphere as the target | VMs, Hyper-V, physical | Any server into AWS |
| Replication and RPO | Byte-level, seconds | Seconds, 30-day journal | 1 second to 1 hour | Seconds, 7-day points | Points every 5 minutes | Seconds, by AWS’s claim |
| Orchestration and tests | Heartbeat + groups | Recovery Plans, sandbox | Site Recovery action | Runbooks are Premium | Plans, isolated drills | Plans since Aug 2026 |
| Failback | Backward scenario | Reverse Protect | No RTR failback step | Documented failback | Yes; physical as a VM | Failback Client ISO |
| Pricing model | Per server, by scenario | Per protected VM | Per VM or per socket | Per workload (VUL) | Per instance, monthly | Per server-hour |
| Published entry price | Not published | No list price | $2.95/VM/month | ~$350–450 a year | $25/instance/month | $0.028/server/hour |
| Included vs add-on | AR is a module | Vault recovery in ARE | Own licence; not Pro | In every edition | Target costs extra | Fee is not the bill |
| Ransomware defence | Rewind, no detection | Encryption detection | Rewind by the second | Immutable repos, scans | Replicates what lands | Launch an older point |
| India DR site | Your replica server | Wherever you target | Your vSphere host | Your vSphere cluster | Four Indian regions | Mumbai and Hyderabad |
| Support | Portal, chat, phone | HPE Tech Care | 24/7 on subscription | 24/7, 1-hour Sev 1 | Paid plan from $29 | Paid AWS plan |
| Lock-in and exit | Dissimilar hardware | Native VMs at the target | VMware at both ends | vSphere for CDP | Azure is the target | AWS is the target |
| Best fit | App servers, any host | Ordered VMware DR | A few critical VMs | Veeam-licensed estates | Azure as the DR site | AWS as the DR site |
Which approach fits you?
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Choose Arcserve RHA if…
- ✓Windows or Linux application servers need to fail over on their own when a heartbeat fails, not when someone wakes up
- ✓Your estate mixes physical servers, VMware, Hyper-V, EC2 and Azure, and you want one replication tool across all of them
- ✓You want a replica you can rewind past corruption and test with Assured Recovery while replication keeps spooling
Compare alternatives if…
- ✓You need ordered, multi-step recovery plans across many VMware groups — Zerto and Veeam Recovery Orchestrator do this
- ✓You want a price you can read before a sales call — NAKIVO RTR, Azure Site Recovery and AWS DRS publish theirs
- ✓You would rather rent the DR site than run one — Azure Site Recovery and AWS DRS both have Indian regions
Do not expect…
- ✓A published price, or an RHA listing on Arcserve’s e-store
- ✓An Arcserve-hosted DR site, or backup-length retention from the rewind log
- ✓A Gartner Leader placement — Arcserve was a Niche Player in 2025 and 2026
Arcserve Replication and High Availability is one of 27 disaster recovery products TechBag carries. The Disaster Recovery guide narrows them to a shortlist and shows the reasoning. →
What does a server outage cost you?
Drag the sliders (servers you protect; IT staff-hour cost). Estimates model the staff time spent restoring servers, re-entering lost data and moving users by hand after a failure, at an assumed 1.5 hours per server a year, with 70% of it saved by continuous replication and heartbeat failover. Both figures are assumptions. Illustrative.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Three ways to consume it
Quote only. Arcserve publishes no price for Replication and High Availability, and its e-store, which sells UDP and SaaS Backup to the USA, Australia and New Zealand, does not list it. The licence key is built from the operating system, the product (Replication or High Availability), the applications protected, the number of hosts and add-on modules such as Assured Recovery. In India it is bought through Arcserve partners; Arcserve shows no rupee price. TechBag lists your servers and scenarios first, then quotes in INR with GST.
Arcserve Replication
Best for a live copy you recover from by hand
- Continuous byte-level replication
- Data Rewind points and bookmarks
- Quoted per server and application
+ Platform add-ons
Best for a broader rollout
- Scoped to your estate
- Add-on modules as needed
- Phased, right-sized deployment
Arcserve High Availability
Best for servers that must fail over on their own
- Heartbeat checks, automatic switchover
- DNS, Move IP or computer-name redirection
- Assured Recovery testing is a module
Buy it for less — TechBag pricing beats list
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Get an India-ready quote
Tell us your requirements and current tools — we’ll model it against what you spend today.
The 8 questions to ask every vendor
Take this into your next vendor call — including ours.
Which servers need automatic failover rather than a restore? HA scenarios cost more; replicate the rest.
Is every server Windows or Linux on physical, VMware, Hyper-V, EC2 or Azure, at a version 18.0 SP3d supports?
Does each app have a scenario type — Exchange, SQL Server, IIS, SharePoint, Oracle — or need a custom one?
Where will the replica run: your Indian data centre, a colo, or your own EC2 or Azure account in India?
Has Assessment Mode shown the WAN can carry your peak change rate? A slow link lengthens real data loss.
Which method moves users — DNS, Move IP or Switch Computer Name — and do both servers share a trusted domain?
Will you buy Assured Recovery for live replica tests, or plan switchover drills with a maintenance window?
Does the quote list OS, product, applications, host count and modules? Ask for INR with GST and the maintenance term.
Questions buyers ask
Ready to evaluate Arcserve RHA?
List the servers that cannot wait for a restore first, or let a TechBag advisor size the WAN with Assessment Mode, place the replica in India and get the quote itemised in INR.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.