Quantcast
Channel: All Data Protector Practitioners Forum posts
Viewing all articles
Browse latest Browse all 10494

Re: Error Granular DP 8,12.

$
0
0

This appears to be more of a problem with Exchange than with DP

 

I checked lab cases for this error, and found none.  Then, I googled' the error, and got one hit

 

https://www.google.com/search?hl=en&source=hp&q=must+be+logging+in+with+guids&gbv=2&oq=must+be+logging+in+with+GUIDs&gs_l=heirloom-hp.1.1.0i22i10i30j0i22i30.2465.9922.0.20593.9.7.0.2.2.0.187.1124.0j7.7.0....0...1ac.1.34.heirloom-hp..0.9.1155.QIADb6ALDlw

 

new-mailboxrestorerequest -sourcedatabase rdb -sourcestoremailbox a -targetmailbox a -skipmerging storageproviderforsource

 

what  happened was the above command restored the mailbox. it did not skipped the merging, so i was not able to see the restore folder in OWA.

I refreshed the page many times but there was no Restore folder because it was merged with the original mailbox

 

http://msitpros.com/?p=1801

 

To create a restore request, you must provide the DisplayName, LegacyDN, or MailboxGUID for the soft-deleted or disabled mailbox. To get a list of mailboxes you can restore run Get-mailboxStatistics –Database Testrestore

 

 Error detail: must be logging in with GUIDs. not legDN. I tried with the DisplayName, LegacyDN and MailboxGUID without success.

 

But I found another parameter I could use: -SkipMerging StorageProviderForSource.

and it worked

 

=============

 

By no means should I be considered a Exchange expert, and you shoud run this past teh Exchange administrator before trying it.  Also, I don't know how this would figure into Exchange GRE restore, since the documentation does not show any where where a login is required

 

 


Viewing all articles
Browse latest Browse all 10494

Trending Articles