packetloss

packetloss OP , 8 months ago

Looking to perform daily backups of all users OneDrive files, SharePoint data, Teams (teams, channels, files, tabs), Exchange Online mailboxes.

This would be for long-term retention. 5+ years. Thinking of using object storage like Wasabi as a destination.

packetloss OP , 8 months ago

What I’m trying to achieve is backup and archival of data for long term retention and recovery.

There are certain legal obligations that as an organization we need to fulfill. Being able to recover emails and data from up to 5 years ago. If a user leaves or deletes an email or a file that we suddenly need to reference years down the road, that is not possible with the retention tools MS gives us.

So I’m looking for a solution that allows me to backup this data daily and store it for 5 to 7 years for future reference and recovery if needed.

packetloss OP , 8 months ago

It’s actually a completely separate product from Veeam Backup & Replication. Not a connector or add-on to VBR. Would be nice if it was.

packetloss OP , 9 months ago

No, we don’t have any licenses other than Business Basic or Business Standard.

packetloss OP , 9 months ago (edited 9 months ago)

Edit: September 25, 2023 - Added more details to the solution for my issue.

Just wanted to update this so if anyone else is having the same issue hopefully it helps them.

During initial tenant setup I created a couple of retention policies. I thought these would only affect Teams data, but it turns out it also applied to Exchange Online mailboxes. When I tried to remove the Exchange Online license from the user it would give an Exchange error message in admin console and the mailbox would not get removed.

The issue turned out to be caused by holds that were applied to the user mailbox. Specifically these two:

DelayHoldApplied

ReleaseDelayHoldApplied

Both were set to $true.

1. I removed the retention policies, they probably weren’t configured correct in the first place.
2. Used the following Powershell command to identify the holds applied to mailboxes:

Get-Mailbox | FL Identity,*HoldApplied*

3. Used the “Set-Mailbox” command to remove those holds:

Set-Mailbox -Identity @mydomain.com -RemoveDelayHoldApplied

Set-Mailbox -Identity @mydomain.com -RemoveDelayReleaseHoldApplied

4. Delete the user’s mailbox by removing the Exchange Online license from the user and waited for the mailbox to disappear from the Exchange Online admin center.
5. Run the following command to wipe out the pre-existing mailbox data. Without doing this, even after the on-prem user is synced Exchange Online will not care that the user has an on-prem mailbox, and will restore the previously deleted cloud mailbox from step 4.

Set-User @mydomain.com -PermanentlyClearPreviousMailboxInfo

6. Force a sync of users using Azure AD Connect
7. Re-enable the Exchange Online license for the user. After this is done in the users Mail settings you should see a message “This user’s on-premises mailbox hasn’t been migrated to ‎Exchange Online‎. The ‎Exchange Online‎ mailbox will be available after migration is completed”

Thanks to everyone who replied and offered help.

packetloss OP , 11 months ago

We are going through a replacement of our BSS/BMM system, going from 2 systems to 9, so far… Maybe more in the future. All to handle the same number of customers.

packetloss OP , 11 months ago

Of course… how could I not with that look he’s giving. Haha

packetloss OP , 11 months ago

Haha! He gets a TON of cuddles, don’t you worry. But he’ll act like he’s deprived to get more.

packetloss OP , 11 months ago

I don’t blame you, haha

packetloss , 11 months ago

I agree with this. Would be totally up for seeing this sort of content on here, just as long as it didn’t flood the feed.