Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
box with a lot of corruptions

Answered box with a lot of corruptions

  • Monday, May 14, 2012 12:06 AM
     
     
    Sign In to Vote
    0

    i'm migrating mbx from 2003 to 2010. i have a mailbox that failes out with 60 corruptions.

    is it better to set corruption to  70 or just export that mailbox into pst

     

All Replies

  • Monday, May 14, 2012 11:47 AM
     
      Has Code
    Sign In to Vote
    1

    You can try 70, but again you may hit that limit too, you may wanty to accept data loss & set the baditemlimit to something hiher or unlimited

    e.g 

    New-MoveRequest -Identity 'Kweku' -PrimaryOnly -TargetDatabase "DB01" -BadItemLimit 100 -AcceptLargeDataLoss

    Sukh

     
  • Monday, May 14, 2012 4:12 PM
     
     
    Sign In to Vote
    0

    Hi,
    If you have a another database in Exchange 2003, try and move the mailbox there first and then to Exchange 2010.


    I had to do the same a couple of weeks ago and it solved my problem.
    Before I went with that road, I checked the movehistory log and saw that all corrupted items had to do with meeting requests and mostly Acceptance and Declined messages that he sent and received.
    I suspect that the problem was caused by his iPhone, but I can't be sure.

     

    Martina Miskovic

     
  • Monday, May 14, 2012 4:20 PM
     
     
    Sign In to Vote
    0

    Martina,

    I've done that. I was able to move her mailbox on Ex2003 without any issues but it fails out when i'm trying to move to Ex2010.

    My concern is that her mailbox is only 300 mb or so and she has 60 corrupted items.

     
  • Monday, May 14, 2012 4:33 PM
     
     
    Sign In to Vote
    0
    Hi,
    What kind of items is it and are they in the same folder?

    Martina Miskovic

     
  • Monday, May 14, 2012 6:31 PM
     
     
    Sign In to Vote
    0
    I'm not sure. I don't think it's a folder structure. I think folders are being moved within first 10%. It errors out at around 25. I'm thinking it might be deleted items
     
  • Monday, May 14, 2012 6:35 PM
     
     
    Sign In to Vote
    0

    Check the moverequest log, it will tell you. The first 10% only creates the mailbox hiearchy.
    Example: Get-MoveRequest USER | Get-MoveRequestStatistics -IncludeReport

    Martina Miskovic

     
  • Monday, May 14, 2012 6:57 PM
     
     
    Sign In to Vote
    0

    i'm getting this

     
  • Monday, May 14, 2012 7:04 PM
     
     
    Sign In to Vote
    0
    Try again (but this time with format-list):
    Get-MoveRequest USER | Get-MoveRequestStatistics -IncludeReport | fl

    Martina Miskovic

     
  • Monday, May 14, 2012 8:25 PM
     
     
    Sign In to Vote
    0

    that worked. Thanks.

    I see some corruptions with calendar /appt items.

     
  • Monday, May 14, 2012 8:29 PM
     
     
    Sign In to Vote
    0
    You should also see the folder they are stored in...Do you?

    Are most of them also (as in my case) most accepts and declines?

    Martina Miskovic

     
  • Monday, May 14, 2012 8:31 PM
     
     
    Sign In to Vote
    0
    What do you plan on doing with them, it's good you have found them but if they are corrupt and you export/import will those be usable,? Probably not, manually going through them may take to filter, unless you really need them, so it may be just worth increasing the bad limit and just moving it.

    Sukh

     
  • Monday, May 14, 2012 9:45 PM
     
     
    Sign In to Vote
    0

    i tried to do that however i'm getting an error



    • Edited by Halo-NEXT Monday, May 14, 2012 10:51 PM
    • Edited by Halo-NEXT Monday, May 14, 2012 11:10 PM
    •  
     
  • Monday, May 14, 2012 9:50 PM
     
     Answered
    Sign In to Vote
    1
    Hi,
    Did you use the parameter -PrimaryOnly as suggested by Sukh?
    That will not work.

    Martina Miskovic

    • Marked As Answer by Halo-NEXT Tuesday, May 15, 2012 5:06 PM
    •  
     
  • Monday, May 14, 2012 10:52 PM
     
     
    Sign In to Vote
    0
    i did
     
  • Tuesday, May 15, 2012 6:04 AM
    Moderator
     
     Answered
    Sign In to Vote
    1

    Use this to check whether the mailbox is ready to move:

    New-MoveRequest -Identity 'tony@alpineskihouse.com' -TargetDatabase DB01 -WhatIf

    Then try to move the mailbox (without -PrimaryOnly):

    New-MoveRequest -Identity 'tony@alpineskihouse.com' -TargetDatabase DB01

    Here is a related document for you:

    Create a Local Move Request
    http://technet.microsoft.com/en-us/library/bb124495.aspx

    Thanks,

    Evan

    Evan Liu

    TechNet Community Support


     
  • Tuesday, May 15, 2012 5:06 PM
     
     
    Sign In to Vote
    0

    MArtina,

    Thanks. Having luck this time.

     
  • Wednesday, May 16, 2012 10:49 AM
     
     
    Sign In to Vote
    0
    So the increase of the bad limit was the way to go.

    Sukh

     
  • Wednesday, May 16, 2012 11:29 AM
     
     
    Sign In to Vote
    0

    Sukh,

    I left out -PrimaryOnly. I set it to 70 and it failed out again. After setting 500 it finally went through.

     
  • Wednesday, May 16, 2012 11:43 AM
     
     
    Sign In to Vote
    0

    Sukh,

    I left out -PrimaryOnly. I set it to 70 and it failed out again. After setting 500 it finally went through.


    I was emphasizing that the bad item limit had to be used here.

    Sukh

     
  • Wednesday, May 16, 2012 1:50 PM
     
     
    Sign In to Vote
    0

    i did.

    I saw her having 60 corruptions so i figure i set it to 70.