Originally posted by: vi_edit
Oh how I miss the fond days of mail stores slamming into the 17 gig barrier and crashing and having to do offline defrags into the wee hours of the morning.
Well...no. I really don't miss that at all.
Crashed mail servers never make for a fun day.
Originally posted by: iamwiz82
Originally posted by: vi_edit
Oh how I miss the fond days of mail stores slamming into the 17 gig barrier and crashing and having to do offline defrags into the wee hours of the morning.
Well...no. I really don't miss that at all.
Crashed mail servers never make for a fun day.
Our Exchange 5.5 database is just a hair over 56GB right now.
![]()
Originally posted by: vi_edit
Originally posted by: iamwiz82
Originally posted by: vi_edit
Oh how I miss the fond days of mail stores slamming into the 17 gig barrier and crashing and having to do offline defrags into the wee hours of the morning.
Well...no. I really don't miss that at all.
Crashed mail servers never make for a fun day.
Our Exchange 5.5 database is just a hair over 56GB right now.
![]()
Enterprise? I can't remember if 5.5 had a limit. I was on the Exchange 2000 "Standard" version.
Originally posted by: iamwiz82
Yessir
The funny thing is that we only have 117 mailboxes. You cannot enforce mailbox limits when your two top offenders are the head hanchos, though.![]()
Originally posted by: ryan256
Originally posted by: iamwiz82
Yessir
The funny thing is that we only have 117 mailboxes. You cannot enforce mailbox limits when your two top offenders are the head hanchos, though.![]()
I feel your pain. I remember doing an exchange 5.5 to 2000 migration once. Of course the M$ conversion tools didn't work right so we resorted to exporting everything as .pst files and then restoring them to the new 2000 box. Senior partner #1's .pst --- 7.4GB Senior partner #2 --- 11.4GB! :Q
Originally posted by: iamwiz82
Originally posted by: ryan256
I feel your pain. I remember doing an exchange 5.5 to 2000 migration once. Of course the M$ conversion tools didn't work right so we resorted to exporting everything as .pst files and then restoring them to the new 2000 box. Senior partner #1's .pst --- 7.4GB Senior partner #2 --- 11.4GB! :Q
Our parent company is discussing a move to 2003 right now. I dread it.![]()
Originally posted by: ryan256
Originally posted by: iamwiz82
Originally posted by: ryan256
I feel your pain. I remember doing an exchange 5.5 to 2000 migration once. Of course the M$ conversion tools didn't work right so we resorted to exporting everything as .pst files and then restoring them to the new 2000 box. Senior partner #1's .pst --- 7.4GB Senior partner #2 --- 11.4GB! :Q
Our parent company is discussing a move to 2003 right now. I dread it.![]()
Don't worry. Exchange 2k3 migrations from 2000 are much easier! Once the box was installed & configured, data migration was a snap.
Originally posted by: MS Dawn
Originally posted by: ryan256
Don't worry. Exchange 2k3 migrations from 2000 are much easier! Once the box was installed & configured, data migration was a snap.
Going from 5.5 to 2003 is going to be FUN. I'm no IT person but I hear screams through the waves to know better. 2003 is very good - good as the hardware it needs! At least you will be able to right click!![]()
Originally posted by: ryan256
Originally posted by: MS Dawn
Originally posted by: ryan256
Don't worry. Exchange 2k3 migrations from 2000 are much easier! Once the box was installed & configured, data migration was a snap.
Going from 5.5 to 2003 is going to be FUN. I'm no IT person but I hear screams through the waves to know better. 2003 is very good - good as the hardware it needs! At least you will be able to right click!![]()
Ohh... 5.5 to 2K3... um yeah .. then be prepared for .pst hell. I haven't heard of anyone be able to pull of a smooth 5.5 migration yet.
