Forum Discussion

karen_timmons's avatar
14 years ago
Solved

Lotus to Exchange using Quest Notes Migrator for Exchange program

I've read the documentation on this, seems pretty straightforward - does anybody have any lessons learned or information they would like to share about this proceess?

Any input would be appreciated

  • Tom's recommendation is right the quickest for migrating. Just use Quest to migrate the EV for Domino shortcuts over to the Exchange mailbox.

     

    Another recommendation I would make is to see if the customer is on an older version of EV for Domino check to see if Storage Expiry is turned on. In previous version of EV for Domino some customer have run into the the issue where storage expiry would delete items from storage, but then it would leave orphaned shortcuts in the mailbox. This would create issues for the EVdominoExchangemigration tool if a -policy switch was used.

     

    Shortcut expiry and orphaned shortcut deletion is available in EV 9.0 SP2. So before migrating make sure they are on EV 9.0 SP2 and set the orphaned shortcut deletion policy and this will remove all orphaned shortcuts. Plus you won't have to migrate them either.

    The other workaround which is less desierable for some customers is if you can't upgrade is to run the evdominoexchangemigration tool against the exchange mailboxes with the -po none. This should skip any storage checks when the tool runs and prevent evdominoexchangemigration issues.

    jim

  • Hi Karen,

    It's also worth considering that if you have archived Lotus Notes archives with Enterprise Vault, there is a solution to do a direct Notes -> Exchange archive-to-archive solution, using TransVault. This means you don't need to do a complete restore and cause users problems with shortcuts and Mail Server growth - you can do it all within the confines of Enterprise Vault and migrate direct from an EV Notes archive to an EV Exchange one.

    Thanks,

    Dan

  • I dont think you need to do a complete restore from EV to Domino.

    If you just migrate the Domino EV shortcuts using Quest NME there is a tool covered in the EV Utilities Manual called EVDominoExchangeMigration Tool.  No need to restore everything to Domino then bring it over.  Just leave it as is.

     

    Tom

  • Tom's recommendation is right the quickest for migrating. Just use Quest to migrate the EV for Domino shortcuts over to the Exchange mailbox.

     

    Another recommendation I would make is to see if the customer is on an older version of EV for Domino check to see if Storage Expiry is turned on. In previous version of EV for Domino some customer have run into the the issue where storage expiry would delete items from storage, but then it would leave orphaned shortcuts in the mailbox. This would create issues for the EVdominoExchangemigration tool if a -policy switch was used.

     

    Shortcut expiry and orphaned shortcut deletion is available in EV 9.0 SP2. So before migrating make sure they are on EV 9.0 SP2 and set the orphaned shortcut deletion policy and this will remove all orphaned shortcuts. Plus you won't have to migrate them either.

    The other workaround which is less desierable for some customers is if you can't upgrade is to run the evdominoexchangemigration tool against the exchange mailboxes with the -po none. This should skip any storage checks when the tool runs and prevent evdominoexchangemigration issues.

    jim

  • Tom, isnt the EVDominoExchangeMigration tool a manual process? karen had another post asking if there's a way to automate that and Symantec said no.

    TransVault can offer a fully automated shortcut migration engine to, at least, handle that part for you.

  • It appears that Karen is already committed to Quest for the Domino to Exchange migration.

    The evdominoexchangemigrationtool is just a utility used to fix up the shortcuts that are migrated to the Exchange mailbox and convert the necessary mapi properties. It is a command line tool. I think at this point she just needs to find a way to script the tool for bulk processing.