Home/Eagle HyperProtect

Secure Backups with Immutability in Hardened Vaults. Restores you can prove.

Hyper-V, Proxmox VE, Windows file shares, SQL Server, MariaDB, PostgreSQL and Active Directory, into one deduplicating repository, copied to a vault that nobody can delete from. It works on its own, and it reports what is protected to the Eagle Cyber Defence Center.

Eagle HyperProtect

One repository. Every workload.

One Windows service, one deduplicating chunk store, and every restore point a full. What it protects hangs off it; where the copies go is a vault with no way in.

The server Eagle HyperProtect Backup and restore for virtual machines, shares, databases and the directory, from one Windows service with a web interface
Hyper-V hosts This host and every other one, through a small agent paired with a one-time code Proxmox VE Virtual machines over the API, restored as new or over the original Windows file shares Whole shares, folders or single files, with their permissions Databases SQL Server, MariaDB and PostgreSQL by their own online backups, restored to a point in time Active Directory Every user, group, computer, OU and Group Policy as versions, with what changed since Eagle HyperProtect Vault The immutable copy: locked until its time is up, on an appliance with no login Cyber Defence Center What is protected, its status and every job run, reported to the hub of the suite
It reports to the Eagle Cyber Defence Center. What is protected, its status, where the copies are and every job run, so backup coverage is governed where the rest of security is, and a failed run becomes a ticket.

How it fits the Eagle Security Suite

What it does

Every restore point a full

A backup product earns its keep on the day something is lost. Everything here is built for that day: the copy that cannot be deleted, the restore that is a button, and the record that proves it was done.

  • One deduplicating repository. Full and incremental backups into one chunk store, where every restore point is a synthetic full: no chain to replay, nothing to consolidate, and the same block stored once however many machines hold it.
  • Repositories where you want them. A local disk, or an SMB share opened with an account of its own, its password kept under Windows DPAPI. Space per source and version, and a forecast of when the repository fills.
  • Virtual machines, two hypervisors. Hyper-V on the server itself and on every further host through an agent; Proxmox VE over its API. Incrementals by change tracking, with a crash-consistent fallback when the guest cannot quiesce.
  • Restore as new, or over the original. A virtual machine comes back as a new one, sized within the target host's limits and checked for disk space before a byte moves, or over the original once it is off.
  • Files, with their permissions. Windows file shares backed up agentlessly, restored as whole shares, folders or single files, to the original place or another.
  • Databases to a point in time. SQL Server by its native full, differential and log backups; MariaDB and PostgreSQL by theirs. Restore to "yesterday 14:32", to the same server or another, or under a new name, after a green, amber or red check of rights, recovery model and space.
  • Active Directory, object by object. Every user, group, computer, organisational unit and Group Policy as a version. Pick one and see what changed since: deleted, moved, emptied, edited; each with its own button to put it back, with its SID, password and groups where the Recycle Bin allows.
  • Schedules and retention. Daily at chosen times, every few hours in a window, or monthly; retention by number of points and by age, applied after each backup; active fulls when you want them; limits per host and in parallel; retries.
  • Copies to the Vault. Copy jobs after a backup or daily, all points or the newest, with their own retention, into the immutable Eagle HyperProtect Vault, and a copy back when the primary is gone.
  • Reports that go to the board. The protection report as PDF and PowerPoint, on demand or on a schedule, saved to a folder or a share.
  • A job log in plain words. Every backup, restore, copy and report as one entry a person can read, with a dashboard and a daily summary by mail.
Restore, not just backup

From "it is gone" to "it is back"

01 — FIND

Pick the version

Every source has its versions listed: the machine, the share, the database, the directory object. Yesterday at 14:32 is a choice, not a calculation.

02 — SEE

See what changed

For a directory, what was deleted, moved or edited since that version, coloured. For a machine, whether it fits where it is going, before anything is written.

03 — RESTORE

Put it back

As a new machine or over the original, a folder or one file, a database under another name, a user with the SID and the groups it had. One button each.

04 — PROVE

Show it was done

The run is in the job log, and in the Cyber Defence Center as the evidence an auditor asks for: that the backup exists, and that a restore was tested.

The Vault

A copy that nobody can delete

Ransomware goes for the backups first. The Eagle HyperProtect Vault keeps copies that cannot be deleted or changed before their lock ends: not by Eagle HyperProtect, not by an attacker holding its credentials, not by the Vault's own administrator.

  • Append only. Eagle HyperProtect writes to the Vault over mutual TLS with pinned certificates, paired once with a one-time code. It can add, and it can ask; it cannot delete.
  • A lock that only lengthens. Every chunk and every restore point carries the immutable flag of the file system, and the lock policy can be extended but never shortened. Retention and clean-up are the Vault's own, with a guard against a turned-back clock.
  • No way in. A Debian 13 appliance with no SSH and no login accounts: the console and its web interface, behind an authenticator code, are the only ways in. It boots with UEFI Secure Boot and uses the virtual TPM where there is one.
  • Its own updates, signed. Update files signed with Valiente's key, checked on upload and again before they apply; Debian's own updates checked daily and installed on request.
  • Looked after, never weakened. A paired server can see the Vault's status, add storage, retire what has expired and manage the box; nothing it can do weakens protection.
  • Recovery, on paper. If the server that owns the Vault is lost, a new one connects with a one-time recovery code from a printed sheet.
  • Deployed from Eagle HyperProtect. Onto a Hyper-V host as a generation 2 machine with Secure Boot and a vTPM, paired automatically; or as an image for VMware and Proxmox, or an installer ISO. Put it on a host whose administrators are not the ones of the machines it protects.
In the Eagle Security Suite

Complete alone, governed together

Eagle HyperProtect needs nothing else to do its job. Run with the Cyber Defence Center, what it does becomes part of the organisation's security record.

Cyber Defence Center

The protected virtual machines and shares arrive as configuration items, their status and figures follow, and every job run lands in the hub's log. A failed run becomes a ticket with an owner.

Cyber Defence Center

Backups as evidence

The hub's Backups page shows which items of the CMDB are covered and which are not, and a tested restore as the evidence ISO/IEC 27001, NIS2 and DORA ask for. Nothing is typed in; a sense raises, the hub governs.

A licence that is a file

Licensed per server by the number of protected workloads, as every Eagle product is, with the Valiente License Tool. Without a valid licence only backups pause; restores, retention and verification keep working.

How it is secured

Built like the rest of the suite

A backup server holds a copy of everything. It is treated as the target it is.

  • Windows authentication and roles. The web interface signs in with the accounts the domain already has; an Active Directory group is made administrator at first start.
  • Secrets under DPAPI. The account that opens a repository share and the credentials for Proxmox, the databases and the directory are kept with Windows data protection, never in a file somebody can read.
  • Mutual TLS, pinned. Agents on further hosts and the Vault speak to the server over HTTPS with certificates pinned on both sides, paired once with a one-time code.
  • The directory, signed and sealed. Active Directory is read over LDAP with signing and sealing, by an account with the rights it needs and no more.
  • A service account of your choosing. Local System, a domain account, or a group managed service account; HTTPS with a certificate from the computer's store or a new self-signed one.
  • Installed and updated without surprises. A setup wizard that refuses a port another program uses, keeps every setting on update, and leaves data and repositories in place on uninstall.
What it protects, and where it runs

On your premises, on your terms

Hyper-V Proxmox VE Windows file shares SQL Server MariaDB / MySQL PostgreSQL Active Directory Group Policy Windows Server Debian 13 appliance UEFI Secure Boot

See Eagle HyperProtect running

An hour with the people who built it, on a real system, with your questions. No slideware.

Book a walkthrough