04 66 72 51 22

All your clients on a single screen

BeBackup was not adapted to multi-client use after the fact: the server has been multi-tenant from the start, because it was written by an IT service provider for its own estate.

The real problem starts at twenty clients

At five clients, you read the reports. At fifty, you no longer do.

This is the point where a solution designed for a single company shows its limits: as many consoles as clients, credentials scattered about, reports arriving by the dozen in a mailbox, and supervision that rests on the memory of whoever did the install. The day a backup has been failing for three weeks, nobody has noticed.

BeBackup's web interface is served by the server itself, with no third-party web server to install and maintain. It is built around one principle: a service provider sees everything, acts everywhere, and delivers reports to its clients under its own name.

A dashboard that surfaces anomalies

Computed server side and filtered by scope, it distinguishes seventeen states — among them:

  • Erreur
  • Avertissement
  • Backup not started
  • Medium locked
  • Backup in progress
  • Restore in progress
  • Replication in progress
  • Integrity check in progress
  • Office 365 backup

To which are added the backup-not-started alerts, computed from the schedule specific to each medium: this is not a global threshold, it is that medium's own rule that determines whether it should have run. Where several servers are linked, the alert queries the other servers before firing — a workstation that backed up elsewhere does not raise a false alarm.

Disk space alerts and administration events go out by email to the recipients you name.

What the console puts in your hands

A hierarchy that fits your organisation

  • Resellers, companies, users, devices
  • Settings inherited in cascade: template, then provider, then company, then medium
  • Locking field by field, to freeze what must not be changed further down
  • Views: free groupings of companies and users, to filter the screen
  • Quotas on volume and on number of media at every level

Rights at the granularity of the technician

  • Around fifty named rights per reseller user
  • Create a user, change a medium, launch an integrity check
  • Restore, edit an agent's configuration, manage the white label
  • A first-line technician can restart a backup without being able to touch retention
  • Passwords are never sent back to the browser

In your colours

  • White label per provider: name, URL, logo
  • HTML reports by template and by provider
  • Backup report and alert report, with recipients set per medium
  • Manual sending, with a history you can browse by date and by medium
  • Consolidated reports in CSV format
  • Interface, emails and reports in five languages, each user's own choice

Acting without logging on to the workstations

  • Around sixty commands on the agents, from the web
  • Start or stop a backup, follow progress live
  • Test the connection, list the VSS components and the ESXi VMs
  • Restore files, disks and virtual machines
  • Export the file list or the deduplication report
  • Restart the agent or the machine, purge the logs, uninstall
  • Agent configuration editable directly from the interface

Hosting remains your decision

This is what sets the model apart. The BeBackup server is installed wherever you decide: on your own premises, at your client's, or on a dedicated server. You are not required to go through storage imposed by the vendor.

The consequences are direct for a service company:

  • You control your own cost base on the storage side, instead of reselling a line whose price is dictated to you.
  • You answer the question of where the data is plainly: your clients know which server, in which premises, their backups live on.
  • You keep a way out: whether the stores are hosted by us or by you, the architecture is the same and you can bring them back onto your own server. This is not storage you would not hold the keys to.
  • You fit the architecture to the client: an eight-workstation practice and a hundred-and-fifty-seat industrial SME do not call for the same arrangement, but it is the same solution to master.

The server-to-server replication handles the off-site copy with no extra tool and without going back through the clients' workstations: it is the server that replicates, following rules inheritable per medium.

What running it does not ask of you

A multi-client solution is only worth having if it does not demand a full-time post to maintain it.

  • The server updates itself without interrupting backups in progress
  • A separate watchdog monitors it and restarts it if it stops responding
  • Windows agents update themselves, distributed by the server
  • A periodic health check watches disk, logs and memory
  • Each operation runs in an isolated process: a medium in trouble does not affect the others
  • Long operations can be scripted from the command line on the server

Take back control of your backup offering

Thirty minutes with the engineer who develops the solution, on your own estate and your real constraints.

Request a demo

The other pages in this section Features

  • What's new in v7 Microsoft 365, BeBackup Drive, agents for macOS, Linux, Synology, Android and iPhone…
  • Microsoft 365 Mailboxes, contacts, calendars, OneDrive and SharePoint backed up through Microsoft Graph…
  • System and virtualisation SmartImage, disk image, VSS for SQL Server and Hyper-V, VMware VMs backed up agentlessly with…
  • Restore and recovery A file, a folder, a partition, a whole disk, a physical machine to an ESXi VM, booting under…
  • You are here For service providers
  • Security and encryption AES-256 encryption on the workstation, key held by the client, TLS 1.3, two-factor…

Contact the BeBackup team

Would you like to know more about our BeBackup backup solution?