Correction: Also, the text-based log files are limited to a churn of 250 MB per log directory per day (by default). Even if you have absolutely everything turned on, you are still only referring to 6-7 GB per day. Compared to the size of your database log files and databases, that should be tiny.
From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Monday, March 10, 2014 6:55 PM To: [email protected] Subject: RE: [Exchange] disable exch2013 default logging The requirements are "more" because UM is on every server, whereas in most places before, it simply didn't exist. Of course, other new features do impact performance, but I believe that is the single largest impact. Now, back to the OP: you know that image backups of Exchange servers are not supported, correct? Also, the log files are limited to a churn of 250 MB per log directory per day (by default). Even if you have absolutely everything turned on, you are still only referring to 6-7 GB per day. Compared to the size of your log files and databases, that should be tiny. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Steven Peck Sent: Friday, March 7, 2014 5:56 PM To: [email protected]<mailto:[email protected]> Subject: RE: [Exchange] disable exch2013 default logging I don't think those are 'preemptive for MS PSS'. Pretty sure these are all part of the 'Managed Availability' that is built in now. As far as I can see, they pretty much took all the stuff that was in previous SCOM management packs and built it into Exchange. http://blogs.technet.com/b/exchange/archive/2012/09/21/lessons-from-the-datacenter-managed-availability.aspx http://www.expta.com/2012/12/exchange-2013-health-check-monitors-and.html http://technet.microsoft.com/en-us/library/jj150551(v=exchg.150).aspx Which I think is why the requirements are so much more beefy even on test environment servers. I could be wrong, as I am a bit rusty on the Exchange side since they tossed me back on the team so working to catch back up Someone will correct me if I am wrong on this. Steven Peck > From: [email protected]<mailto:[email protected]> > To: [email protected]<mailto:[email protected]> > Subject: [Exchange] disable exch2013 default logging > Date: Fri, 7 Mar 2014 16:27:31 +0000 > > Is there a way to disable the baked-in Exchange 2013 diagnostic logging? > > I see google-fu around relocation of it, but couldn't find an off switch. My > concern relates to image-based backups of these systems and having to seed an > extra semi-useless 1GB+ per day for things like this from a default install: > > C:\Program Files\Microsoft\Exchange > Server\V15\Logging\Diagnostics\DailyPerformanceLogs > C:\Program Files\Microsoft\Exchange > Server\V15\Logging\Monitoring\Monitoring\ActiveMonitoringTraceLogs > > Those directories appear to self-clean, so it's not a permanently growing > file structure ... but it still results in a massive daily delta for image > backups that'd just as soon avoid seeding to disk and cloud if I can. > > I know why it's there (preemptive diags for PSS in the event I need to invoke > them) but curious if there's a way to just turn it off. > > Anyone know anything on this? I presume that turning off Health Manager > service maybe helps, not sure if there's a downside to that, or if that's > comprehensive enough to stop that data being written (maybe there's baked-in > tasks as well, etc etc) > > Any insight/pointers appreciated. I don't mind having that data around except > for the negative impact on those image-based backups. > > Rick
