Stopping Mailbox moves
I am running Exchange 2007 SP2. I need to move some mailboxes so we are running a Move-Mailbox Powershell command. It's only a few so we are not planning on enabling circular logging. I want to make sure I nothing goes wrong, so had some questions on best practice 1. Are transaction logs generated on the source or target SG 2. If I want to cancel the mailbox moves, how can I do this? 3. Will the above mess up the mailbox in any way? 4. Am I correct in thinking that a move-mailbox command basically copies the existing mailbox to the target store and then deletes it from the original? 5. If the above is correct, is there a way to recover the original mailbox from the original store if there is a problem 6. Can mailbox moves cause corruption to the mailbox? Thanks in advance.
January 29th, 2011 6:42am

I have never known move mailbox to cause a problem with the content of the mailbox. In the event of a problem, the process simply stops and the existing content remains in place. It is only removed from the original location once the move is confirmed. You don't have to use PowerShell to move mailboxes, you can do so through the GUI. Then if you wanted to cancel them you just click on cancel. Transaction logs will be generated on both servers if I recall correctly. Certainly on the target, because they are being written to the database. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources
Free Windows Admin Tool Kit Click here and download it now
January 29th, 2011 10:00am

Thank you, Simon. We are using Powershell in this case since there are a couple of different groups of mailbox moves we need to do and it's easier to script them this way. What I'm not entirely sure of is how we can cancel the move process once the move-mailbox commands have been kicked off. Do you know? I mean, can we just CTRL-C in the Exchange Management Shell or we do need to run a seperate set of commands etc? Thanks again.
January 29th, 2011 11:17am

On Sat, 29 Jan 2011 16:12:03 +0000, Sheen1990 wrote: >We are using Powershell in this case since there are a couple of different groups of mailbox moves we need to do and it's easier to script them this way. What I'm not entirely sure of is how we can cancel the move process once the move-mailbox commands have been kicked off. Do you know? I mean, can we just CTRL-C in the Exchange Management Shell or we do need to run a seperate set of commands etc? Just kill the PS session. A cleaner way would be to add something that checks for an external event to the section of code that loops over the set of mailboxes. Maybe just check for the presence of a file named STOPIT.TXT in a directory. As long as the file's not there, move the next mailbox. If the file's there, remove the file and exit the script. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
January 29th, 2011 12:57pm

> Just kill the PS session Do you mean CTRL-C or closing the Powershell window?
January 29th, 2011 2:23pm

On Sat, 29 Jan 2011 19:18:15 +0000, Sheen1990 wrote: >> Just kill the PS session > >Do you mean CTRL-C or closing the Powershell window? Either one. I prefer to manage the shutdown of long running scripts by limiting how long they can run (a minor bit of programming) and by providing an external "trigger" to make them stop gracefully (also a minor bit of programming). The result is an orderly shutdown of the script that ensures that any log files are closed cleanly and any saved data has a chance to be written to permanent storage. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
January 29th, 2011 4:05pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics