On our clusters we run groups of (3) 100GB DBs that share a 50GB log file. Ours rarely go above 20-30 GB a day before being cleared out by backups.
The only time we have to worry is when (a) backups fail or (b) we are moving mailboxes around. Regards, Don Guyer Catholic Health East - Information Technology Enterprise Directory & Messaging Services 3805 West Chester Pike, Suite 100, Newtown Square, Pa 19073 email: [email protected]<mailto:[email protected]> Office: 610.550.3595 | Cell: 610.955.6528 | Fax: 610.271.9440 For immediate assistance, please open a Service Desk ticket or call the helpdesk @ 610-492-3839. [cid:[email protected]] From: [email protected] [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Monday, June 24, 2013 4:56 PM To: [email protected] Subject: [Exchange] Transaction logs - how many, how fast Exch 2010 I have 3 databases, Database 1 with 1020 mailboxes, Database2 with 1002 mailboxes, and Database 3 with 980 mailboxes. On Database 1, I'm getting 2-3 new transaction logs pretty much every second. This is filling up the drive rather quickly, taking about 30ishGB since last night. The drive had filled up last Friday, I expanded it by 200GB, and it was full again by Sunday night. I have been having some issues with backups, so that will help once the backup is successful, taking away well over 100GB, but it just doesn't seem right that I'm getting that many new transaction logs so quickly. I've run ExMon against the first server, but there aren't any mailboxes sticking out with really high CPU%, or LogBytes. The top box changes every refresh. Any other ideas of where to look, or is that rate of logs "normal" for databases this size? Thanks, Joe Heaton Enterprise Server Support CA Department of Fish and Wildlife 1807 13th Street, Suite 201 Sacramento, CA 95811 Desk: (916) 323-1284 Confidentiality Notice: This e-mail, including any attachments is the property of Catholic Health East and is intended for the sole use of the intended recipient(s). It may contain information that is privileged and confidential. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please delete this message, and reply to the sender regarding the error in a separate email.
<<inline: image001.jpg>>
