SOLVED

Recovering archive mailboxes

%3CLINGO-SUB%20id%3D%22lingo-sub-1113022%22%20slang%3D%22en-US%22%3ERecovering%20archive%20mailboxes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1113022%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20all%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20had%20a%20really%20unwanted%20adventure%20over%20the%20past%2010%20days%20and%20need%20your%20expert%20advice%20please%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1%20%E2%80%93%20setup%3C%2FP%3E%3CP%3E2%20X%20DC%3C%2FP%3E%3CP%3E2%20X%20Exchange%202019%20CU3%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%204%20machines%20running%20Windows%202019%20standard%20with%20all%20the%20latest%20updates%3C%2FP%3E%3CP%3E1%20exchange%20server%20holds%20the%20main%20mailboxes%20(ex8)%3C%2FP%3E%3CP%3E1%20exchange%20server%20holds%20the%20archive%20databases%20(ex8-archive)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20working%20perfectly%20well%2C%20until%20I%20decided%20to%20start%20upgrading%20them%20to%20CU4.%20I%20started%20with%20the%20archive%20server%20so%20that%20in%20case%20of%20problem%20the%20downtime%20will%20not%20be%20catastrophic.%20CU4%20install%20failed%20in%20the%20middle%20of%20the%20install%2C%20dumping%20a%20whole%20lot%20of%20code%20and%20error.%20Researched%20for%20days%2C%20tried%20setup%20again%2C%20server%20recovery%2C%20followed%20tons%20of%20instructions%20and%20none%20helped.%20I%20contacted%20Microsoft%20paid%20support%20and%20for%203%20days%2C%20they%20could%20not%20solve%20the%20problem%20either%2C%20so%20they%20just%20told%20me%20to%20install%20a%20new%20machine%20with%20a%20different%20name%20(ex8b-archive)%2C%20which%20OF%20COURSE%20worked%20and%20then%20they%20said%20their%20scope%20is%20complete.%20I%20am%20having%20a%20debate%20on%20that%20with%20them%20that%20they%20could%20not%20figure%20out%20the%20problem%2C%20its%20cause%20or%20solution%2C%20but%20right%20now%20my%20users%20are%20getting%20desperate%20for%20their%20archive%20data.%20Here%20is%20the%20current%20problem%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20the%20archive%20databases%20were%20on%20a%20separate%20virtual%20disk%20so%20they%20were%20unaffected%20by%20all%20these%20issues.%20I%20have%20used%20eseutil%20on%20them%20and%20they%20are%20all%20in%20clean%20shutdown%20state%20and%20good%20health.%20The%20first%20issue%20was%20how%20to%20mount%20these%20to%20the%20new%20server%20ex8B-archive.%20No%20help%20from%20Microsoft%2C%20but%20I%20followed%20an%20article%20which%20told%20me%20to%20create%20a%20new%20database%20with%20the%20same%20names%20elsewhere%2C%20then%20copy%20the%20old%20databases%20back%20as%20restore%20(I%20ticked%20the%20box%20where%20it%20said%20this%20database%20can%20be%20overwritten%20by%20restore).%20So%20far%20so%20good%2C%20all%20archive%20DBs%20mounted.%20Until%20I%20realised%20that%20now%20none%20of%20the%20users%20show%20as%20having%20archive%20mailbox%20(see%20attached%20image)%2C%20although%20it%20showed%20that%20mailboxes%20are%20archive-enabled.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20disabled%20archive%20and%20re-enabled%20it%20for%20a%20couple%20of%20test%20accounts.%20In%20the%20process%20it%20asked%20me%20which%20database%20I%20want%20and%20I%20pointed%20it%20to%20the%20original%20archive%20database%20(there%20is%20one%20example%20in%20the%20image).%20Worked%20great.%20Except%20that%20the%20client%20cannot%20see%20any%20data%20in%20their%20archives.%20If%20I%20run%20a%20mailbox%20statistics%20command%2C%20it%20shows%20the%20size%20of%20the%20archive%20to%20be%200.%20The%20archive%20databases%20are%20still%20full%20(have%20around%2080-100%20Gb%20of%20data%20in%20them)%20and%20the%20retention%20policy%20is%2028%20days%2C%20so%20the%20data%20is%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20do%20not%20know%20how%20to%20recover%20the%20data.%20I%20have%20tried%20very%20cautiously%20to%20use%20New-MailboxRestoreRequest%20command%20once%2C%20but%20not%20sure%20if%20I%20am%20using%20it%20correctly%20or%20not.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENew-MailboxRestoreRequest%20-SourceDatabase%20%22DB14-Archive%22%20-SourceStoreMailbox%20%22user1%E2%80%9D%20-TargetMailbox%20%3CA%20href%3D%22mailto%3Auser1%40example.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Euser1%40example.com%3C%2FA%3E%20-TargetIsArchive%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20run%20this%20it%20says%20Mailbox%20%22user1%22%20doesn't%20exist%20on%20database%20%22DB14-Archive%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20I%20am%20at%20a%20loss%20now%20and%20any%20advice%20would%20be%20greatly%20appreciated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20all%20in%20advance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1113022%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%202019%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1118478%22%20slang%3D%22en-US%22%3ERESOLVED%20-%20Recovering%20archive%20mailboxes%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1118478%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20all%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20in%20case%20anyone%20else%20comes%20across%20this%20issue%2C%20I%20managed%20to%20resolve%20it.%20Please%20see%20below%20links%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.spiceworks.com%2Ftopic%2F2252319-resolved-recovering-archive-data-from-exchange-2019%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fcommunity.spiceworks.com%2Ftopic%2F2252319-resolved-recovering-archive-data-from-exchange-2019%3C%2FA%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.u-btech.com%2Farticles%2Fhow-to-restore-archive-data-en%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.u-btech.com%2Farticles%2Fhow-to-restore-archive-data-en%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F521289%22%20target%3D%22_blank%22%3E%40Calvinator28%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hello all

 

I have had a really unwanted adventure over the past 10 days and need your expert advice please:

 

1 – setup

2 X DC

2 X Exchange 2019 CU3

 

All 4 machines running Windows 2019 standard with all the latest updates

1 exchange server holds the main mailboxes (ex8)

1 exchange server holds the archive databases (ex8-archive)

 

All working perfectly well, until I decided to start upgrading them to CU4. I started with the archive server so that in case of problem the downtime will not be catastrophic. CU4 install failed in the middle of the install, dumping a whole lot of code and error. Researched for days, tried setup again, server recovery, followed tons of instructions and none helped. I contacted Microsoft paid support and for 3 days, they could not solve the problem either, so they just told me to install a new machine with a different name (ex8b-archive), which OF COURSE worked and then they said their scope is complete. I am having a debate on that with them that they could not figure out the problem, its cause or solution, but right now my users are getting desperate for their archive data. Here is the current problem:

 

All the archive databases were on a separate virtual disk so they were unaffected by all these issues. I have used eseutil on them and they are all in clean shutdown state and good health. The first issue was how to mount these to the new server ex8B-archive. No help from Microsoft, but I followed an article which told me to create a new database with the same names elsewhere, then copy the old databases back as restore (I ticked the box where it said this database can be overwritten by restore). So far so good, all archive DBs mounted. Until I realised that now none of the users show as having archive mailbox (see attached image), although it showed that mailboxes are archive-enabled.

 

I disabled archive and re-enabled it for a couple of test accounts. In the process it asked me which database I want and I pointed it to the original archive database (there is one example in the image). Worked great. Except that the client cannot see any data in their archives. If I run a mailbox statistics command, it shows the size of the archive to be 0. The archive databases are still full (have around 80-100 Gb of data in them) and the retention policy is 28 days, so the data is there.

 

I just do not know how to recover the data. I have tried very cautiously to use New-MailboxRestoreRequest command once, but not sure if I am using it correctly or not.

 

New-MailboxRestoreRequest -SourceDatabase "DB14-Archive" -SourceStoreMailbox "user1” -TargetMailbox user1@example.com -TargetIsArchive

 

When I run this it says Mailbox "user1" doesn't exist on database "DB14-Archive".

 

So I am at a loss now and any advice would be greatly appreciated.

 

Thank you all in advance.

1 Reply
Highlighted
Best Response confirmed by Calvinator28 (New Contributor)
Solution

Hello all

 

Just in case anyone else comes across this issue, I managed to resolve it. Please see below links:

 

https://community.spiceworks.com/topic/2252319-resolved-recovering-archive-data-from-exchange-2019

https://www.u-btech.com/articles/how-to-restore-archive-data-en

 

@Calvinator28