A Restored Database Won't Mount
Copying live database files can leave you with an inconsistent recovery point.
Use the database engine's own backup method, with scheduled isolated restores and query tests.
Get the database, the shares and the laptop files back without paying to image the whole machine. One machine price covers all its backup sets. Each recovery point is checked through the restore path, so you can see what's been verified.
Make sure the database opens, the versions survive and the systems outside your image-backup plan are covered.
Copying live database files can leave you with an inconsistent recovery point.
Use the database engine's own backup method, with scheduled isolated restores and query tests.
Some workloads need file or application recovery without a full server image.
Back up SQL Server, Exchange or System State separately, with all sets covered by one machine price.
Sync copies whatever changed, the ransomware's work included.
Recover earlier versions from immutable backups that a compromised server can't delete.
Check coverage for NAS shares, Macs, domain controllers and application databases.
Windows, Linux, Apple Silicon Macs, Synology and QNAP, SQL Server, Exchange and System State, each its own set with its own schedule.
Think about the systems added since the last backup review.
A script can copy a database mid-write. Sync can copy the ransomware's changes. Having the files doesn't mean you have a recovery point you can use.
Protect the data on its own terms, with application-consistent backups, locked versions and checks you can inspect.
Back up the SQL instance, the shares or System State at a file-backup price. Give each its own schedule. Pay once for the machine.
Protect only the SQL Server instance, Exchange or a domain controller's System State, and pay a file price instead of imaging the whole server.
Files, shares, SQL Server and System State on one server are separate sets, each with its own schedule, sharing that machine’s one charge.
Application-consistency checks confirm that every writer succeeded. Scheduled restore tests recover the database in isolation and run a query.
File Backup spots the other backup products on a machine at every capture, and never truncates a log chain it doesn’t own.
Search by name, path, owner or date, then restore to a new location by default. Restores resume, and one failed file never restarts a million-file job.
Every point has a signed manifest and a sample read through the restore path. The console distinguishes those checks from a full test restore, so you can see exactly what has been verified.
Install the agent, review the recommended backup sets and choose where to store them.
Push the same signed, silent agent BCDR uses through your RMM, or install the native package on a Synology or QNAP. No tray icon, nothing for anyone to switch off.
It finds the files, System State and applications on the machine and recommends a set for each. Pick the appliance or the cloud, and add credentials where needed.
Every set publishes a verified first point. Restore a test file in front of the client, so they see the round trip.
That's the public list price. Your MSP rate is lower. Enter your quantities in the calculator and see what you'd actually pay.
Every set the server needs, from files and System State to SQL Server, Exchange and other databases, for one charge, with 1 TB pooled.
Back up selected data without a full-machine image.
Files and folders on a Windows, Linux or Apple Silicon desktop or laptop, with 250 GB of storage pooled across your clients.
Back up desktop and laptop files without a full-machine image.
Enter what you protect. See your rate on screen and get the full pricing PDF by email, so you can check the numbers before you quote.
Every row dated and sourced, and the line between File Backup and BCDR.
Have a question about your setup? Contact our team.
No. It brings back files, System State and application data. If the server has to boot again, that's BCDR, and the console tells you when a restore needs it.
Yes. Add a SQL Server set and File Backup uses SQL Server's own backup method, with full backups, transaction logs and point-in-time restore to the original instance or another one. The server is one charge however many databases it holds.
No. It truncates a log only when it owns the chain and its own copy is safe and immutable. If another product owns the chain, it backs up without truncating.
Yes, Apple Silicon Macs, files and folders, billed as a workstation. No Intel build, and no Mac image or bare-metal recovery.
Every point gets a signed manifest, a check that every object is intact, and a sample read back through the real restore path. Databases also get a structure check every backup and, on your schedule, a restore in isolation and a query.
No, on purpose. The immutable copy exists to survive a stolen login, and a bucket your team administers can be emptied by whoever holds your admin credentials. A NAS can hold an extra copy you control.
Per machine per month, month to month: a workstation or a server. One server is one charge whatever it carries, and storage is pooled across your clients: 250 GB a workstation, 1 TB a server.
Yes, if you let them. Delegate named paths to a client’s IT person and they restore within those paths, no ticket needed.
EnterProtect File Backup is file and application backup for MSPs. It protects a server’s shares, its SQL Server or Exchange databases, or a domain controller’s System State on their own, at a file price instead of an image price.
Join the waitlist before File Backup launches and get the Founding Partner Rate.
It closes the day File Backup launches.
Loading the current public count…
Protect the files and applications your client needs to get back, at one price per machine. Check the verification results before the next restore request arrives.