Product
An agent on every machine, a console for the IT team, a quiet tray icon for the user. All of it on your own equipment — nothing rented by the month.
Windows service
Installed on every workstation or server to protect. It evaluates the schedule, scans watched folders, packages, encrypts and uploads. It starts with the machine and restarts itself after a failure.
Administration
The IT team’s screen: companies, machines, watched paths, frequencies, run history and restore. This is where “is that machine protected?” gets answered.
User side
The only part the user sees: current backup status, and a way to pause it for a few hours without calling support.
Under the hood
Implementation details are what separate a reliable backup from a folder someone copied by hand.
Four frequency types — once, daily, weekly, monthly — evaluated continuously. Only one frequency fires per cycle: two schedules landing at the same time never collide.
The agent doesn’t trust a local state that could lie after a reinstall: it compares against the last snapshot recorded server-side. File names are normalized so accents never cause false positives.
Changed files are split into compressed packages with a capped source size. A large folder goes out as several successive batches rather than one fragile transfer.
Every batch is sent with the record of everything confirmed so far. If a batch fails, the server cannot believe an un-uploaded file is backed up — the state stays accurate even after a cut.
Encryption is applied as the package is written. If encryption is requested and no key is available, the agent sends nothing: never a plaintext upload “just to unblock things”.
Every run leaves a trace: files processed, volumes, duration, errors. That history serves diagnostics as much as proof, during an audit or an insurance claim.
Deployment
Installation is scripted: agent copy, configuration, service creation, tray icon. Re-running the same script with new binaries updates the machine while keeping its configuration.
01
The MIRRO service, its database and the vault are placed on a server in your network. That is where every backup will live.
02
From the console: the company to protect, its agent account, the watched folders and their frequencies.
03
One installation script in an administrator console: the agent is copied, configured, registered as a service and started.
04
The first full run goes out and the console confirms the volumes received. Later runs are incremental, with an email report.
MIRRO succeeds the original Java agent and keeps its data model: your companies, paths and history stay in place. Migration happens machine by machine with no loss of history — a new password is simply set for each agent account.
A 30-minute demo on your own fleet: scheduling, restore, logs. No strings attached.