Protect the files without protecting the whole machine
Coming soonNot every workload deserves an image. A file server, a shared drive, a database on a box you would rebuild anyway: back up what matters, on the agent you already deployed, in the console you already use.
Selective backup is where tool sprawl starts
The workloads that do not justify full continuity end up somewhere else: a second vendor, a script, a NAS with a sync job nobody owns. Now you have two consoles, two invoices, two restore procedures, and one of them is only documented in a technician’s memory.
A second product for small jobs
Another agent, another portal, another renewal, for the workloads the main tool priced out of reach.
Sync mistaken for backup
A mirrored folder copies the ransomware too. Versions and immutability are what make it recovery.
Database backups nobody validated
An application dump is only useful if the consistency contract behind it is stated and the restore was tested.
One agent, one console, the right amount of protection
Recommended sets, discovered for you
Install the connector and accept the sets it finds, or choose your own. Five steps from install to a verified recovery point, with the advanced selection, consistency, bandwidth, and retention controls waiting behind progressive disclosure for the day you need them.
Files, shares, and System State
Endpoint and server files with their metadata and versions, network datasets, and Windows System State, selected per set. What is protected and what is deliberately excluded are both visible, counted, and explainable to the client.
Database and application sets
SQL Server, Exchange, and open-source databases through signed adapters, each carrying its own consistency, native-log, and validation contract. Application awareness is stated per set, never implied by the presence of a file.
The same agent as everything else
One signed, headless service: silent RMM deployment, no local interface for a user to disable, no inbound management port to attack. The machine you protect for continuity and the machine you protect for files run the same software.
Appliance or direct to cloud
Back up to the local appliance for fast recovery, or straight to your chosen EnterProtect region for sites that do not run one. Small offices and remote workstations do not need hardware to be protected properly.
Verified, versioned, and searchable
Every set ends in a verified recovery point. Browse versions, restore a file, a folder, or the whole set, and close with the same evidence the rest of the platform produces.
Three steps to coverage with no gaps
Assign
Push the agent through your RMM, or turn on File Backup for a machine the console already protects.
Select
Accept the discovered sets. Point them at the appliance or the cloud region. Confirm schedule and retention.
Verify
Watch the first recovery point verify itself, then restore a test file so the client sees the round trip.
The gap is never in the system you thought about
Nobody loses data on the protected domain controller. They lose it on the share that moved, the workstation that held the only copy, the database somebody stood up on a Tuesday. Coverage you can prove is coverage without those stories.
What we commit to
- Every discovered asset is protected or is a deliberate, counted exclusion. No silent gaps.
- Application consistency is stated per set, never assumed from a file extension.
- One agent and one console for files, systems, and everything that follows.