Every version is kept
The Drive keeps the version history of every file, for the period set by the administrator. A file overwritten by mistake can be recovered from an earlier version.
A folder synchronised across the company's workstations, like OneDrive or Dropbox, but built on BeBackup backup: every version is kept, every deletion can be undone.
A shared folder synchronises everything, including mistakes: a file overwritten or deleted is overwritten or deleted on every workstation.
BeBackup Drive is used just like the tools your teams already know: a folder in Explorer, opened with the usual software, whose contents appear on every workstation. The difference lies underneath. The Drive is built on BeBackup backup: every file is versioned, deduplicated and encrypted like a backup. A mistake synchronised everywhere can therefore be recovered from the history.
A product that complements backup, then: backup protects workstations and servers, while Drive gives teams a shared working space that keeps the same memory.
The Drive keeps the version history of every file, for the period set by the administrator. A file overwritten by mistake can be recovered from an earlier version.
A deleted file disappears from the workstations, but its versions remain on the server. It can be restored from the web interface, like any other backup.
Two people edit the same file at the same time, or offline? Both versions are kept: one under the original name, the other as a conflict copy named after its author.
The content is encrypted on the workstation before it leaves, and deduplicated like a BeBackup backup: the same file present in several places is stored only once.
The Drive space resides on your host's BeBackup server, with the same storage and server-to-server replication rules as your backups.
A full resynchronisation takes place every day: it catches up on anything that may have been missed and removes conflict copies identical to the original. A scheduled maintenance task runs on the server.
The administrator creates the Drive share in the BeBackup web interface and, if required, organises it into folders: "Accounts", "Projects", etc.
Each user installs it with the BeBackup agent: the share appears as a folder in Explorer, for example D:\SOCIETE_CLOUD. Each workstation chooses which folders it mounts.
A file added, modified or deleted reaches the other workstations within seconds if they are switched on, otherwise at their next connection.
The Drive share is managed in the BeBackup web interface, alongside the backups:
These settings are inherited, from the hosting provider to the reseller, the customer, the user and the share: a provider sets them once for all their customers and only configures the exceptions separately.
Day to day, it works just the same: one folder synchronised across workstations, with files on demand. The difference lies underneath: BeBackup Drive is built on BeBackup backup. Every version is kept, a deleted file remains restorable, content is encrypted on the workstation and deduplicated, and the storage is hosted on your hosting provider's BeBackup server.
The Drive keeps both versions. One retains the original name, the other becomes a conflict copy named after its author, for example Report-Isabelle.xlsx. Nothing is lost and nothing is guessed: it is the people who merge. Conflict copies identical to the original are removed during the daily resynchronisation, to a quarantine folder.
Deleting removes the file from the workstations, but its versions remain on the server. It can be recovered from the share's "Restore" tab in the BeBackup web interface. It remains available for the history and retention period set by the administrator.
Yes: content is encrypted by the BeBackup agent, on the workstation, before it leaves. The Drive space is hosted on your host's BeBackup server, wherever that server is located, with the same storage and replication rules as your backups.
Yes, on the files present on the workstation: the Drive is a local folder. Your changes are sent at the next connection, and other people's changes arrive at that point. If someone has modified the same file in the meantime, you get a conflict copy, not a loss. In files on-demand mode, pin the files you will need before you leave.
Right-click the file, then "Share with BeBackup Drive": you get a download link to send them, with an optional expiry date and password. The shared file is made available on the hosting provider's server for the lifetime of the link. Transfer works in that direction only: an external person cannot upload a file.
Not necessarily. With files on demand, the workstation only keeps the names, and the content is downloaded when the file is opened. You can pin a file or folder to keep it on the workstation, or free it up to reclaim space. Windows 10 version 1709 or later is required.
Not within a single share: a Drive share is a space shared by a company, and all of its users have access to all of its folders. Choosing which folders are mounted on a workstation is a convenience, not a security barrier. To separate teams, create distinct shares.
No, not with everyone's changes appearing live. Such co-authoring is an online Microsoft service, on a file opened from a web address; no file synchronisation can provide it on a local file, Dropbox no more than BeBackup Drive. If two people modify the same file at the same time, the second one gets a conflict copy.
Yes. On a Remote Desktop server (RDS), each Windows user manages their own Drive, without seeing anyone else's.
BeBackup Drive is offered by BeBackup IT providers and hosting providers. Request a demonstration, or speak to your provider about it.
Would you like to know more about our BeBackup backup solution?