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]
> To: [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
                                          

Reply via email to