Hi Mattigan,
The 'move mailbox' function in exchange results in encrypted traffic (see link here
http://groups.google.com/group/microsoft.public.exchange.setup/browse_thread/thread/cd5f60fbae15bc91... between servers so this obviously impacts the Steelhead's ability to dedup this traffic.
The Exchange prepopulation function maintains a client's connection on the Steelhead appliance so that mail may be delivered to the Steelhead even when the client has been shut down or disconnected. Unfortunately, I don't see a way for this pre-pop feature to help you with your mailbox move.
Hopefully your peer users will have a better suggestion for you.
Update: Here is a list of migration tool specialists that one of our PMs was been able to compile. I have not used any specific tool and hence cannot vouch for a specific one. I know Quest has an option to disable encryption and compression
Priasoft:
http://www.priasoft.com/exchangemigration/...ion_manager.aspXOSOFT:
http://www.xosoft.com/products/migrating_e...CFQGuSAodY3XxdgQuest Software:
http://www.quest.com/exchange_migration_wizard/Transend:
http://www.transend.com/?gclid=CNin29ilv4YCFSEgSQodMz4QFwNetIQ:
http://www.netiq.com/products/em/Migration using MSFT tools and techniques
I have seen this as a recommendation over WAN migrations by MSFT folks. The pst s do have some light compression enabled but we still see benefits due to Steelheads.
1) Exmerge out the data to PST
2) Send the data across the WAN. The transport protocol is decoupled and hence you could use FTP or CIFS.
2) Move the (now empty) mailbox across the WAN using Exchange Migration tool.
3) Exmerge back in the data from PST
There is a 2Gbyte per mailbox limit with Exmerge. If there is sufficient Exchange expertise this is a viable alternative.
QUOTE(mattigan @ Jun 4 2008, 04:22 AM) 1062
We are looking to consolidate our Exchange environment back to London, and currently have several Branch Offices throughout Europe with their own Exchange servers which we are planning to shut down once the mailboxes have been moved to London. In the past the 'move mailbox' Exchange task has frequently failed due to slow WAN links when we have attempted to move users' mailboxes between offices often taking several attempts to get the move to complete successfully, although the last move we did between two offices running Steelheads did seem to go through a lot quicker than expected, in spite of a couple of failures/restarts and we suspect that the Steelheads were caching the data that did get through each time so that the subsequent attempts had a head start.
We are now facing the prospect of having to move 100+ users back to London, and are wondering if there is a possibility that we could use the Steelheads prepopulation fuction to preload the mailbox data from a branch office (via backup tape) in London before running the move mailbox task. Has anyone out there attempted this type of thing?
Our current option is to attempt to move one mailbox a night and a few at the weekend which will take a very long time.
Thanks.
