Every New Point Booted Before You Need It
Each new recovery point is integrity-checked, mounted read-only, then booted on a private network with no route to production. A point that never booted shows as a gap, not a green check.
EnterProtect BCDR is disaster recovery for MSPs. It boots every new recovery point in isolation to prove it works, brings a failed server back locally in minutes, and runs the whole site in our recovery cloud.
Backup answers whether a copy exists. Disaster recovery answers how long until your client is working again, and the honest answer depends on something nobody checked: whether last night's recovery point actually boots. A completed job proves data moved and nothing else, so the usual way to find out is during the restore, with the client on the phone. EnterProtect finds out first, every time a new recovery point lands.
Every vendor images and restores. These are the parts that change how long your client waits.
Each new recovery point is integrity-checked, mounted read-only, then booted on a private network with no route to production. A point that never booted shows as a gap, not a green check.
Change, entropy and canary signals flag points that look wrong and hold the points before them. Boot a candidate in isolation, scan the copy, then bring systems back in dependency order.
When the building is gone, servers boot in EnterProtect's own recovery cloud, one at a time or as a saved plan with boot order, private networks, VPN and public access set up the way you left them.
Test one server, one application or the whole site, in isolation. Every run records what booted, how long it took and what failed. Restore tests run monthly by default, never less than quarterly.
The appliance is our software on any x86-64 machine that meets the published minimums, with no appliance licence and nothing recurring per box.
Short answers for the conversation about how much a client can lose, and how long they can wait.
The most data a client can afford to lose, measured in time, and how it differs from RTO.
Read the AnswerWhole-machine backup that boots, locally or in the cloud, so a failed server runs while you fix it.
Read the AnswerYes, with EnterProtect: any x86-64 machine with hardware virtualization and two separate drives.
Read the AnswerWith evidence, not a screenshot: coverage, lock receipts and restore-test results.
Read the AnswerBackup keeps a copy. Disaster recovery gets the client working again from it, in an order and a time you can state. EnterProtect BCDR does both: it captures, proves every new point boots, and runs servers locally or in our recovery cloud.
RPO is the most data a client can afford to lose, measured in time, so it sets how often you capture. RTO is how long the client can be down, so it sets how fast a system has to come back.
Monthly, with quarterly as the floor. EnterProtect runs restore tests monthly by default and never less than quarterly, and boots every new recovery point in isolation on top of that.
No. EnterProtect never sells hardware and charges no appliance licence. BCDR runs on any x86-64 machine that meets the published minimums, including hardware you or your client already own.
Every new point booted before anyone needs it, on hardware you own. Here's what EnterProtect puts in writing.