So you don't need a server, it can be fully installed on a workstation and the backup store locally or on a shared resource? Why would the documentation not say that? The cost difference is quite big!īut do you really want to trust something as important as your backups to a Desktop machine? Also, most places don't have proper licensing for a VM of a Desktop OS, making that option pretty much impossible. Nightly backups of changes has been adding about 2GB each time. Our Repository, once everything was brought down from O365, takes up 770 GB. We use 142 Veeam licenses (one for each O365 licensed user) and are currently just backing up Exchange Online mailboxes (we won't need any more licenses to add OneDrive and SharePoint backup in the future). Accessing the files through the Explorer is very easy. Now that everything is backed up, the nightly incremental backups take about a half hour.
We use 142 Veeam licenses (one for each O365 licensed user) and are currently just backing up Exchange Online mailboxes (we won't need any more licenses to add OneDrive and Microsoft SharePoint Server 2016 backup in the future). Veeam Support helped us tweak the proxy.xml file to reduce the number of connections made to O365 which allowed us to complete the initial download. The biggest trouble we had was with Microsoft throttling our initial backup of our Public Folders. We did have to bump the disk space up a few times though.
While that may be a better setup (for efficiency or security?), I found it was not required and have everything on one machine for testing. I too was thinking that we needed two separate machines, one for the Server and one for the Repository. When reading the user guide, I got the feeling that there are several ways to set it up so the details are vague.
In our case, it is a stand alone software that we installed on a Windows 7 VM - both the server and the repository. We are currently testing this for our Office 365 backups.