PDA

View Full Version : Problem moving mailboxes Exchange 2003


GeordieSteve
03-04-07, 17:59
Anyone had problems moving mailboxes between priv files on Exchange 2003? I'm just using Exchange System Manager but MAPI sh*ts it's self every time and I need to reboot the box

Lucifer
03-04-07, 18:08
Yes thats an easy one. What OS is the box on? And what SP level is exhcange on?

GeordieSteve
03-04-07, 18:54
I think the issue is largely down to the 0Mb space on the C drive lol I checked for drive space on C: (RAID 0+1, 30gb disks) and it was down to 1.7Mb free space. Quick clean up and we're back in business. Strange really as the new priv files are sitting on the D drive (RAID 5, oodles of free space). Exchange is installed on the C tho so I'm wondering if it caches the mailboxes to C while transferring them. hmmmmm bugger

Lucifer
03-04-07, 18:55
Temp Swap Area.

GeordieSteve
03-04-07, 18:57
Thought as much. Move of the swap area possible or will it be a reinstall of Exchange on the D partition? After all that's happened mate I'm surprised to see you replying. I doff my cap and appreciate it

Lucifer
03-04-07, 19:00
YOu can move the swap area. Exchange writed to the Profile Temp if I remember correctly but uses alot of teh SYtem swap. Control panel, system, advanced IIRC.

GeordieSteve
03-04-07, 19:02
Are we talking virtual memory swap file or does Exchange have it's own swap file?

grahamc
03-04-07, 19:19
doesnt exchange store a load of LOG files every day? We normally delete the days set with the evening backup.

GeordieSteve
03-04-07, 19:20
Shouldn't be enough to fill 30gb tho. Only a handful of small mailboxes on there and the server hasn't been live for long at all

grahamc
03-04-07, 19:26
you will be surprised... we filled ours in 17 days (70gb drive).

besides, you have OS, and other stuff on the drive as well.

Schtuv
04-04-07, 09:48
When you move a mailbox using ESM the mail is transferred using the MTA. By default the MTA db and working files are in the Exchange install directory (C:\Program Files\Exchsrvr), hence you need some space.
If this isn't working due to disk space then try using EXMERGE from the Exchange install CD (or bin directory). Remember that the EDB you're moving from won't shrink without an offline defrag, the EDB you're moving to will grow, you'll create transaction log files during the move, and if you EXMERGE you'll lose single instance storage (mailbox will increase in size).

Also: when moving mailboxes using ESM it's been known for the process to stick at 'Saving Changes To Directory'. This inducates mailbox corruption.

EDIT: It is possible to move the MTA by navigating down in ESM to the queues on your server, selecting X.400, properties, and updating the location. This will only move the database, though, and may still use C: for working files.

EDIT 2: Guess what I've been doing at work recently ;)

GeordieSteve
04-04-07, 10:20
EDIT: It is possible to move the MTA by navigating down in ESM to the queues on your server, selecting X.400, properties, and updating the location. This will only move the database, though, and may still use C: for working files.
BRILLIANT! That's exactly what I wanted. You just saved my ass ;)

Schtuv
04-04-07, 11:02
MKIVSUPRA.net ... for all your IEC 10021-2 message handling standard requirements :)

GeordieSteve
04-04-07, 11:09
No such luck! Will I need a reboot to take effect? Just tried to move a mailbox from C to D and it filled C up again even though I'd moved the MTA database

Schtuv
04-04-07, 11:23
You'll need to restart the message transfer agent service for it to take effect. Are your transaction log files on C:\? (General tab on the properties of your storage group)

GeordieSteve
04-04-07, 11:28
They were until about 15 mintues ago. Martin was right the logs have HAMMERED disk space. Any way I can restrict the size of the log files?

Schtuv
04-04-07, 11:33
Each completed full backup will wipe out all the transaction log files. The logs are a record of each and every email which arrives at the system since the last backup. In short it's in case your database corrupts - the log files can be replayed back into a restored database if you have to restore, ensuring a lossless restore.
You can (although it's not recommended) enable circular logging (mailbox store properties page, tickbox), which means you only get two (10Mb) log files for each storage group. It's an emergency measure, though.

GeordieSteve
04-04-07, 11:38
I think I love you pmsl Mail has started cueing up on the old server now and won't send... not really my day is it?

grahamc
04-04-07, 11:42
You'll need to restart the message transfer agent service for it to take effect. Are your transaction log files on C:\? (General tab on the properties of your storage group)

Thats what I said, but forgot the name.

Schtuv
04-04-07, 11:49
Thats what I said, but forgot the name.
D'oh! So you did - I should read more carefully. I just wish there was giant red alert light somewhere for when they don't disappear ...

GeordieSteve
04-04-07, 11:51
Sorry Graham I love you too xxx

Schtuv
04-04-07, 11:56
Mail has started cueing up on the old server now and won't send... not really my day is it?
When Exchange works, it's great. When it doesn't - Run For The Hills!

GeordieSteve
04-04-07, 12:13
When Exchange works, it's great. When it doesn't - Run For The Hills!
Exchange is one thing... DNS is a horrible HORRIBLE creation!

grahamc
04-04-07, 12:20
Sorry Graham I love you too xxx
:D now I am happy...

grahamc
04-04-07, 12:20
When Exchange works, it's great. When it doesn't - Run For The Hills!

Sorry off topic...

Has anyone done the upgrade from Exchange 2003 to 2007 yet?? We are starting to research now...

GeordieSteve
04-04-07, 12:23
Bit too early doors for me 2007 I'm affraid.