Coming soon. Not 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.
Workloads that do not justify full continuity end up somewhere else: a second vendor, a script, a NAS with an unowned sync job. Two consoles, two invoices, and a restore procedure that lives in one technician’s memory. We have inherited those estates.
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 make it recovery.
Database backups nobody validated
An application dump is useful once its consistency contract is stated and the restore is tested.
Recommended sets, discovered for you
Install the connector and accept the sets it finds, or choose your own. Five steps to a verified recovery point. Advanced selection, consistency, and retention controls wait behind progressive disclosure.
Files, shares, and System State
Metadata and versions travel with the files. Every discovered asset is either protected or a counted exclusion you can explain 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.
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.
| Set type | What it protects | Consistency |
|---|---|---|
| Business files |
| Filesystem-consistent with the platform snapshot method |
| Network dataset |
| Filesystem-consistent, with the access identity recorded |
| Windows System State |
| Consistent through the supported Windows writer |
| Application set |
| The adapter’s stated contract, with native logs where the engine provides them |
File sets sit beside images and tenants in one list, with one filter row and one restore grammar.
Push the agent through your RMM, or turn on File Backup for a machine the console already protects.
Accept the discovered sets. Point them at the appliance or the cloud region. Confirm schedule and retention.
Watch the first recovery point verify itself, then restore a test file so the client sees the round trip.
Data goes missing on the share that moved, the workstation holding the only copy, the database someone stood up on a Tuesday. Close those gaps and the coverage number you give a client is one you would defend in a review.
File Backup is coming soon. Tell us what you run and we will tell you when.
