Forum Discussion

K_G's avatar
K_G
Level 6
14 years ago

move archive

hi,

move archive of;

 

2  different evserver ,2  different directory,2 different  site,same domain,same exchange is not working.

i will write my steps which i follewed;

 

-Disable mbx.

-Move archive.

-Destination to new archive selected.

-Move archive status completed.

-Old server user archive renamed.

-New server user archive seen.In reporting page i can see the all of the migrated items.everything is ok

-Items are still reachable.(if i delete old server renamed archive,items will be unreachable ,i tested.)

-In new server migrated archive is disabled,i will enabled on new server?

-I enabled migrated user in new server with enable wizard.(with selecting  existing index and exsisting vault store )

(after enable this archive,empty permissions pane is filled with related user permissions.)(after move archive completed,permissions not transfered to new archive on new server,enable operation do this.)

-Then i delete completed  move archive task in task status screen.(renamed old server archive automatically deleted.)

-Archived shortcuts unreachable!!!  new items archiving works.(shortcuts couldnt updated.)

(new server have same  exchaneg task and provisioning group of related user.)

 

what is your idea?

thanks...

  • Hi,

    I must have been having a brain block before.  Re-reading the case it stands out why the shortcut update phase is omitted.

    When you are doing the move you are selecting 'New archive' for the destination.  This means that the Move Archive process will create a new archive in the destination - as such it is just an archive that is not linked to any mailbox.  What you need to do is the following:

     

    1. Disable the mailbox in the source site

    2. (Ideally) Make sure the user is no longer covered by a provisioning group in the source site.  This is important as you are targeting the same Exchange server in each site.

    3. Provisioning and Enable the user in the destination site.  After this you will be ready to create a Move Archive job.

    4. In the source site go through the Move Archive wizard - when it comes to selecting the destination archive you want to make sure it's linked to the archive/mailbox that now exists thanks to enabling the mailbox in step 3.

    5. Now when move archive runs you should get a phase where it sits at Updating shortcuts (sorry can't remember the exact words).

    6. When it hits this phase move to the destination site, Right click the archiving task and select Run Now, select a single mailbox for shortcut processing only and do a run.  This should perform the required shortcut updates.

    7. After a while in the source site the move archive job should move to completed.

    Again - I would suggest running this against another test user but hopefully this should get you there.

    Regards

    Karl

16 Replies

  • Is there any chance you can setup a test user and process them? That way you can ensure that the steps you are following were 100% right. It may be useful to write the steps down into a document and check them off as you go through them.

    You could use the references in this blog, https://www-secure.symantec.com/connect/blogs/restoreshortcutbody, and run it against the affected user only - BE CAREFUL and make sure you only select that one user!! This may resolve the shortcut issue (but I'm not totally sure as the MA process doesn't seem to have properly completed)..

     

  • i done this test with test user there are just 5 archived mail in this user MBX.

    i applied your TN and run shortcut processing in report mode for this user,burt shortcuts are still unreachable.

    do you have any idea?

    if this test is succesfull ,then i will carry alot of users from other site.

    thanks...

  • That's the only way I know of. This shouldn't be the way you are doing this, as in doing additional steps outside that of Move Archive, hence my point about a new Test user (as I didn't know this was a test user) and just try the process again.......

    Sorry that I can't help out much more, I've got to the limit of my MA knowledge...

  • Hi,

    I must have been having a brain block before.  Re-reading the case it stands out why the shortcut update phase is omitted.

    When you are doing the move you are selecting 'New archive' for the destination.  This means that the Move Archive process will create a new archive in the destination - as such it is just an archive that is not linked to any mailbox.  What you need to do is the following:

     

    1. Disable the mailbox in the source site

    2. (Ideally) Make sure the user is no longer covered by a provisioning group in the source site.  This is important as you are targeting the same Exchange server in each site.

    3. Provisioning and Enable the user in the destination site.  After this you will be ready to create a Move Archive job.

    4. In the source site go through the Move Archive wizard - when it comes to selecting the destination archive you want to make sure it's linked to the archive/mailbox that now exists thanks to enabling the mailbox in step 3.

    5. Now when move archive runs you should get a phase where it sits at Updating shortcuts (sorry can't remember the exact words).

    6. When it hits this phase move to the destination site, Right click the archiving task and select Run Now, select a single mailbox for shortcut processing only and do a run.  This should perform the required shortcut updates.

    7. After a while in the source site the move archive job should move to completed.

    Again - I would suggest running this against another test user but hopefully this should get you there.

    Regards

    Karl

  • Good spot Karl. That's the key to all of this. As the report was stating, it was never going to do the Shortcut update as it was a New Archive....