Avid tech and PC enthusiast. System Administrator by day, Dad by night.

  • 13 Posts
  • 39 Comments
Joined 1 year ago
cake
Cake day: July 2nd, 2023

help-circle






  • 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.






  • 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*

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

    Set-Mailbox -Identity @mydomain.com -RemoveDelayHoldApplied

    Set-Mailbox -Identity @mydomain.com -RemoveDelayReleaseHoldApplied

    1. 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.

    2. 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

    1. Force a sync of users using Azure AD Connect

    2. 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@lemmy.worldtoLinux@lemmy.mlSnapless Ubuntu
    link
    fedilink
    English
    arrow-up
    7
    ·
    11 months ago

    This.

    I just went from Arch to Debian 12 Bookworm. Running the stable branch, but so far most of the packages are rather recent. Kernel is 6.1 instead of 6.4, but I could switch to the Testing or Unstable branch to get the “bleeding edge” packages/kernels if I need to. But honestly so far it’s been a real pleasure to use. Everything is just working and is stable.