The other day I encountered an exchange 2K Standard server at a site which I occassionally do work for, where it had hit the 16GB limit on the mailbox store. There is one storage group.
As usual, it was management had the largest mailboxes. To get the store remounted, I applied the E2K patches to allow me to use the temporary limit, then autoarchived some stuff from the management mailboxes (manually on their PCs), online defragged, then offline defragged, and now everything is fine. Well, for now...! :D
Priv1.edb is now about 14gig (with stream file). All log files etc are all in the same folder on a RAID-5 array on a SBS2000 server.
Options I was thinking through to prevent this happening again, which is where I would please like some advice.
1) Force auto-archive (although managers arent keen on this - what a surprise!)
2) As I cannot create a new mailbox store, can I create a new Storage Group and place the management users into the new storage group mailbox store?
If I can, I don't have enough space on the drive to be able to facilitate this. I was going to map a network drive for our newer 2003 "server" and store it on there. This machine was configured by someone else to not actually perform as a Windows server. Instead, it runs a bespoke Oracle database system.
BUT - what happens if (in my absence) someone reboots this server? Will exchange horribly fall over because the database has suddenly disappeared off the face of the earth without being dismounted? Or will it gracefully recover when the machine comes online.
3) Find E2K Enterprise from somewhere?!
4) Use 2003 server to make use of Ex2003 as well, and host the larger mailboxes on there. (Again as in point 2, what happens here?)
5) Move everything to E2003
My preference is Option 2 but I am worried about the server reboot issue.
Thanks for your help.