The More Involved One: OneDrive for Businessįirst, get yourself the SharePoint Online Management Shell as you'll need it very soon. The dynamic distribution list automatically includes new Exchange Online mailboxes, and I get no warnings.
Now head into the VBO console and set your job to target our new group, and edit the listing to only backup Mail (and Archive if needed.) Set-DynamicDistributionGroup -Name 'O365 Mail Users' -HiddenFromAddressListsEnabled I also hid mine from from the Global Address List, as this was for Veeam. Then, create your distribution list choosing a name of your liking: New-DynamicDistributionGroup -Name 'O365 Mail Users' -IncludedRecipients 'MailboxUsers' $ExSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri "" -Credential $Cred -Authentication "Basic" –AllowRedirection Start by connecting to Exchange Online via PowerShell: $Cred = Get-Credential If I set one of these up in the Exchange Online Admin Center, it's only going to pull in mailboxes that exist in the cloud. Once I stepped back to think about this one for a moment, it was plainly obvious: Dynamic Distribution List. It's only Exchange Online and OneDrive for Business I had to worry about. I was already happy with the SharePoint side of things, as I only had to backup a handful of sites and their sub-sites. If these warnings are accepted as normal, then other unexpected warnings are going to slip through the cracks. If there's a warning (or a pattern of warnings) it should be a sign that something isn't quite right and needs some investigation. When everything is working right, I was to see green check marks. It basically means that the user is licensed for OneDrive but hasn't opened it yet. Yes, strictly speaking these warnings are expected. It's fine though, right? Those warnings are expected! I also started getting jobs finishing with warnings instead of success. This worked, in so far as I was getting the data backed up that needed to be backed up. "Normalization of Deviance"Īt one point I was attempting to backup the OneDrive of every user that was licensed for it. I tried a number of different options for solving these issues, and ended up causing a new issue. Users can start using OneDrive before their mailbox is online.
It's a manual process and humans make mistakes.This user job backed up Exchange and OneDrive and I was adding people to the jobs manually as migration occurred.
One for SharePoint sites (not personal ones) and one for user based items. Given the speed difference between Exchange and SharePoint backups (at least before v3), I'd originally opted to split out into two different jobs. Honestly, the easiest way to get the job done is just to setup a job and select to backup the "entire organization." If you're interested in checking out the beta yourself, head over to the Veeam Community Forum. Screenshots in this post were taken using the VBO v3 Beta. While you're in limbo, how do you decide which users to backup and how do you set things up so that you don't miss people as they are migrated or start to use OneDrive for Business? With that in mind, you've got yourself a product to backup your Office 365 data such as Veeam Backup for Microsoft Office 365 (VBO) - yes, there are other products out there, but Veeam is what I know so it's what I use in my "hypothetical" scenarios. but you're also not telling people not to use it.Īnd, of course, even though you're moving to the cloud you understand that your data is still your problem. You're not yet advising users to throw data into OneDrive for Business. Some of your user's still have mailboxes on-site and others are with Exchange Online. Let's say you're midway through a migration to Office 365.