preshomes
asked on
Exchange Admins - What send and receive limits do you use today? Mailbox Size Limits?
Business size is about 200 users and our current Exchange 2007 limits are...
Send/Receive Limits- 10MB
Mailbox Size Limits- SG1 - 200MB, SG2 - 500MB, & SG3 - 1GB.
What Exchange limits do you currently use/allow?
Send/Receive Limits- 10MB
Mailbox Size Limits- SG1 - 200MB, SG2 - 500MB, & SG3 - 1GB.
What Exchange limits do you currently use/allow?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Although we don't have all users archiving, and have some excess mailbox sizes (1.5 - 2Gb, always on my hitlist!), our stores total around 60Gb at the moment.
Lee
Lee
If you are not going to have archiving and dont want users to have PST files it's ok for the most part as long as your DB's stay consistant and well maintained. Ensure Defrags are done on the databases monthly and clean up users that have left and purge orphaned mailboxes as well.
You see Lee's network is 200 users with a 60gb database. My network is 4 servers, ~1,500 users per server and 60gb db's on each. I have backups, snapshot's, and SMR enabled. With everything included takes up my 12TB SAN. It all depends on how you as the Administrator want to handle your network. You might be able to run a restore, but I can tell you from experience that a 2GB database will restore a hell of a lot faster than a 60Gb one. Plus with smaller databse sizes exchange works a hell of a lot smoother.
I would also highly recommened the use of PST's. That reduces the amount of responsability you as the administrator has over someone's mail. I personally dont want to be dealing with the General who lost or deleted a email accidently when its in his PST file and his responsability. Also it pushes part of the workload out of my Operations center and onto the helpdesk. It is a lot of stupid user calls that I dont have to field.
R/S
SSgt Chieffalo
Network Engineer USMC
You see Lee's network is 200 users with a 60gb database. My network is 4 servers, ~1,500 users per server and 60gb db's on each. I have backups, snapshot's, and SMR enabled. With everything included takes up my 12TB SAN. It all depends on how you as the Administrator want to handle your network. You might be able to run a restore, but I can tell you from experience that a 2GB database will restore a hell of a lot faster than a 60Gb one. Plus with smaller databse sizes exchange works a hell of a lot smoother.
I would also highly recommened the use of PST's. That reduces the amount of responsability you as the administrator has over someone's mail. I personally dont want to be dealing with the General who lost or deleted a email accidently when its in his PST file and his responsability. Also it pushes part of the workload out of my Operations center and onto the helpdesk. It is a lot of stupid user calls that I dont have to field.
R/S
SSgt Chieffalo
Network Engineer USMC
ASKER
Romandain - I am well versed in Administration of Exchange as I am Exchange MCITP certified and have been working with Exchange since 5.5...I was more interested in what current limits "real world" admins were using today.
"You might be able to run a restore, but I can tell you from experience that a 2GB database will restore a hell of a lot faster than a 60Gb one. Plus with smaller database sizes exchange works a hell of a lot smoother."
This is common sense.
"Ensure Defrags are done on the databases monthly and clean up users that have left and purge orphaned mailboxes as well."
I stay away from monthly defrags using ISINTEG and ESEUTIL tools these days. The Exchange 2007 and Exchange 2010 online defrag is all you need. To further ensure healthy databases, creating another db then moving mailboxes to this db ensures good db health, no whitespace, and can be completed without the user noticing.
"I would also highly recommended the use of PST's. That reduces the amount of responsibility you as the administrator has over someone's mail. I personally dont want to be dealing with the General who lost or deleted a email accidently when its in his PST file and his responsibility.'
I disagree based on my experience- I have worked in a 10,000 user organization and I would agree that your statement may be true on a larger scale because a user is not going to track you down to recover their .pst stored /archived mostly because they don’t know who you are and usually takes to long to get though the red tape and take the avenues needed to get help recovering .pst stored emails but when working in a midsize organization the responsibility is the same if not greater with the use of PST's because you can be tracked down and Leadership expects that you address each an every user's need no matter what method is used to store data.
"You might be able to run a restore, but I can tell you from experience that a 2GB database will restore a hell of a lot faster than a 60Gb one. Plus with smaller database sizes exchange works a hell of a lot smoother."
This is common sense.
"Ensure Defrags are done on the databases monthly and clean up users that have left and purge orphaned mailboxes as well."
I stay away from monthly defrags using ISINTEG and ESEUTIL tools these days. The Exchange 2007 and Exchange 2010 online defrag is all you need. To further ensure healthy databases, creating another db then moving mailboxes to this db ensures good db health, no whitespace, and can be completed without the user noticing.
"I would also highly recommended the use of PST's. That reduces the amount of responsibility you as the administrator has over someone's mail. I personally dont want to be dealing with the General who lost or deleted a email accidently when its in his PST file and his responsibility.'
I disagree based on my experience- I have worked in a 10,000 user organization and I would agree that your statement may be true on a larger scale because a user is not going to track you down to recover their .pst stored /archived mostly because they don’t know who you are and usually takes to long to get though the red tape and take the avenues needed to get help recovering .pst stored emails but when working in a midsize organization the responsibility is the same if not greater with the use of PST's because you can be tracked down and Leadership expects that you address each an every user's need no matter what method is used to store data.
ASKER
Thanks!
ASKER
Our 1GB SG is only 6GB in Total size today - only folks in Leadership gets such a size.
Our 500MB SG is 12GB in Size
Our 200MB SG is 6GB in Size.
Server Crashes - Not really worred about "losing" a database..I am running CCR and we have a onsite/offsite backup that takes place every hour.
Lee - I am not really a fan of .pst file and generally turn off auto-archive. What is/are your db sizes at these settings?
Anyone else?