Link to home
Create AccountLog in
Avatar of ITGeneral
ITGeneral

asked on

Exchange 2003 low drive space - database won't/can't shrink

We have a 2003 Exchange server (v6.5.7638.1) that's 95% complete migrating to a 2010 Exchange server. We cannot move mailboxes to the 2010 server however until our phone system gets upgraded (probably another week or 2 away) due to compatibility issues with existing version of Unity and Exchange 2010.

Last night during backups the drive space situation went critical and shut down our mailstore. The drive has about 8GB of free drive space on it. Of course I've deleted about 10GB worth of unused mail accounts but as we all know you don't get that drive space back unless you do an offline defrag. My problem is that it would likely take a couple of days to run the offline defrag which of course we can't afford to do. To my knowledge the offline defrag has NEVER been done before - so we're talking at least 6 years. The .edb is 148+GB while the .stm is 50GB. I tried eseutil last night with the /t /p switches but cancelled it after half an hour because it was still at 0%. Also I checked the App log for event id 1221 and it only shows like 70MB of free space available. But if I go back to previous days that number is changing all the time - sometimes higher - sometimes lower. So I'm not even sure if we had the time if an Offline Defrag would do anything for us.

We have tons of drive space but all on the network which 2003 will not let you use UNC paths or Network drives. So I'm looking for options as to how I can either move the data store to a network drive or get it to actually shrink. Anyone have any ideas?!
Avatar of Manpreet SIngh Khatra
Manpreet SIngh Khatra
Flag of India image

about 200GB of database will take approx 40-50 hours just for the repair (eseutil /p)

So I'm looking for options as to how I can either move the data store to a network drive or get it to actually shrink. Anyone have any ideas? - You have hit the ahrd part buddy any database that has White space can be used for move mailbox and then delete the Physical files of the Database that has no active Mailboxes after Good Online Backup is taken of that Database :)

- Rancy
ASKER CERTIFIED SOLUTION
Avatar of Akhater
Akhater
Flag of Lebanon image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
What partition is the data on?

Which partition has the logs?
Avatar of ITGeneral
ITGeneral

ASKER

Akhater: Sorry that was run with /d /t NOT /p /t. I went under First Storage -> Mailbox and changed the "Deletion Settings" from 5 days to 0 days for the "Keep Deleted mailboxes for (days):" field. Hit apply and it hasn't helped with the free space at all. Has it actually deleted those mailboxes I got rid of yesterday at this point? Is it most likely just deleted them from the mailstore and will not free-up drive space until I run an off-line defrag (which I think at this point is probably out of the question considering the time I figure it would take to run).

npsingh123: My data store, logs and stream files are all on F:\ - I could move the tran logs to C:\ I suppose which would free up almost 3GB. Will it want to take the store offline for that or can I just browse to the new path and let it go while its in production?


Thanks for the suggestions so far guys. Another thought - what about using VMWare P2V and virtualizing it so that I can then mount a new virtualized drive and just make it bigger than the current one?
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
and if you want to move the logs you need to dismount/mount the database
Ok great, at this point I'll definately take that. I'll move the trans logs tonight as well.
If the issue is with Space and you have too many logs consuming the space ... you can simply Enable "Circular Logging" and restart Information Store service (This will only leave 5-6 logs and will keep on appending each in FIFO method).

- Rancy
Randy - that's interesting - any negative effects should Exchange crash altogether? I can move the logs quite easily to the C:\ drive where I have about 55GB of free drive space - currently trans logs only take up about 3GB.
circular logging is never a good idea on a production server, you can however enable it to clear the logs and then disable it again.

Honestly i would advise you to just move it to another location
Ya I think I'm still going to go with my original plan of moving the log files.

Any suggestions on a more permanent solution? ie. using VMWare P2V to virtualize the 2003 box so that I can our massive storage array's resources to just grow the drive to where I've got a safe cushion again.
exchange 2003 is not supported on a VM and anyway since you are soon moving to 2k10 i don't think you have a lot to worry about
that's interesting - any negative effects should Exchange crash altogether? - Nopes no side affects of this  :)

Akhater: I didnt say its a good idea so dont want to comment why you thought so.

- Rancy
@Rancy: I didn't say you said so, the OP asked if circular logging as a negative effect if exchange comes to crash all together and the answer is obviously that with circular logging enabled your chances of recovering a DB are much less.

I don't think you would have ever advised the OP to enable circular logging if it was a "normal" case (i.e. not a server 95% out of production) so i am just stressing on this point nothing more
Setting the retention period to 0 days allowed the mail store to remove the old mailboxes immediately instead of waiting the 5 days that was there previously.

After checking event ID 1221 it now shows that I have 10GB of free space within the mail store so that should be sufficient to get us through the next couple of weeks while we wait to transition fully to Exchange 2010.

Thanks for all suggestions everyone!