question

SteveBottoms-6910 avatar image
0 Votes"
SteveBottoms-6910 asked KyleXu-MSFT commented

EO E3: on-prem mailboxes & archives migrated; HostedPending as ArchiveState in EAC

Good morning! Environment is on-prem Ex2016 CU20 DAG with some in-place archives on some mailboxes. No litigation holds on any accounts being discussed; migrations completed last year, archives are readily accessible with Outlook and OWA. Clients have valid licenses assigned (E3).

All user mailboxes that we've migrated successfully to EO with active, valid in-place archives all have the ArchiveState (according to EAC) as "HostedPending".
* Both migrated users in EAC (on-prem) had an Archive Status of "HostedPending", with the state of the AD property "msExchArchiveStatus" as "<not set>". I've since changed the "msExchArchiveStatus" on one account to "1", and the Archive Status in EAC has changed to "HostedPending" on that one modified account.

  • In Powershell (Exchange Online module loaded) both users have "ArchiveStatus" as "None", and "Archive State" as "Local". (I'm assuming that "Local" is referring to when they archives were actually hosted on-prem originally).

  • In Powershell (Exchange Online module loaded) when I attempt "enable-remotemailbox <user> -Archive" I get an error indicating the recipient already has an archive.

  • In EO Admin center, the "Manage Mailbox Archive" option is disabled, and enabling it return the error "Recipient <userID> already has an archive".

Again, all archives are accessible via Outlook and OWA, but our backup agent (Veeam VBO) cannot see the archives to back them up. I've since migrated another account WITHOUT an in-place archive, then enabled the in-place archive on that account and it's working as expected (including backups).

Suggestions? Thanks.
SteveInReno

office-exchange-server-administration
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

KyleXu-MSFT avatar image
0 Votes"
KyleXu-MSFT answered KyleXu-MSFT commented

@SteveBottoms-6910

Enable archive before("m1" mailbox below) or after("M2" mailbox below) migration are different:

  1. If you enable archive before migration, the Exchange on-premises will show this mailbox is enabled archive function.

  2. If you enable archive after migration(Enable from Exchange online), the Exchange on-premises will know this mailbox is enabled archive function.

From ECP:
107422-qa-kyle-10-42-45.png
From EAC:
107423-qa-kyle-10-44-15.png

This is the expected behavior for migrated mailboxes. I don't know the working mechanism of your backup tool, due to our policy, I cannot test it for you.

But, I think you may need to make sure archive function are all enabled in the same way for all mailbox. Modify attributes from ADUC may make mailbox looks similar, but they are still different in nature. I would suggest you export archive data to PST, then disable archive and enable it in the supported way for your backup tool, then import data to the archive mailbox again.


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@SteveBottoms-6910
I am writing here to confirm with you any update about this thread now?
If the above suggestion helps, please be free to mark it as an answer for helping more people.

0 Votes 0 ·
SteveBottoms-6910 avatar image
0 Votes"
SteveBottoms-6910 answered KyleXu-MSFT commented

KyleXu, thanks for responding! The archives were migrated at the same time as the main mailbox; they were not migrated at different times, so no, there was no enabling of the remote mailbox other than that performed at the time of the mailbox migration. Attempts to enable the remote mailbox now doesn't work, because the mailbox/archive already exists.

I am trying to identify a mechanism that properly migrates in-place archives from on-prem to hosted, because we have a number of users where creating a PST then re-importing isn't feasible; their archives are well over 50G in size.

Given that disabling an archive in M365 does NOT delete it for 30 days, waiting ANOTHER 30 days to see if the process works is rather onerous. If the migration process can't handle on-prem in-place archives, perhaps Microsoft should state that clearly in the documentation.

Thanks. Since there doesn't appear to be a solution I guess we'll just delete it, recreate it, and import the HUGE PSTs.
Steve

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

It seems that your backup tool only could works for archive mailbox which enabled after migration. Office 365 provide the network upload tool which could help you import your organization's PST files to Microsoft 365(It could import data to archive mailbox directly).

0 Votes 0 ·