what is safe to delete in logging folder exchange

• Updated on Baronial 4, 2021
• Exchange, Powershell

Starting from Substitution 2013 and higher, logs are taking up more than space on the Windows Server. This is when cleanup logs Exchange 2013/2016/2019 script plays an important role. Clear Exchange logs with PowerShell and go gratis infinite on the Exchange Server. These logs are Not database logs! You tin can safely delete these logs. In fact, I recommend yous to delete them.

Logs are cracking when you need more than data and want to take a wait into it when y'all are having problems. Commutation Servers are filling upwards easily with all these logs. The best way is to clear the logs considering you demand to free up some size on the disk. The script in this article is my edit to the original script from Edward van Biljon. Y'all can download the official script from Microsoft Technet.

Table of contents

• Gear up the cleanup logs Exchange script
• Run the cleanup logs Exchange script
  • Before running the cleanup logs script
  • After running the cleanup logs script
• Conclusion

Prepare the cleanup logs Exchange script

Re-create the following lawmaking and paste information technology in Notepad. Salvage the file type as CleanupLogs.ps1. You tin can as well download the CleanupLogs.ps1 script (directly link). If information technology does not give yous a prompt to save the file, right-click on CleanupLogs.ps1 and click save link as. You should be able to save the script.

                  # Set execution policy if non set $ExecutionPolicy = Go-ExecutionPolicy if ($ExecutionPolicy -ne "RemoteSigned") {     Set-ExecutionPolicy RemoteSigned -Strength }  # Cleanup logs older than the gear up of days in numbers $days = ii  # Path of the logs that you like to cleanup $IISLogPath = "C:\inetpub\logs\LogFiles\" $ExchangeLoggingPath = "C:\Program Files\Microsoft\Exchange Server\V15\Logging\" $ETLLoggingPath = "C:\Program Files\Microsoft\Commutation Server\V15\Bin\Search\Ceres\Diagnostics\ETLTraces\" $ETLLoggingPath2 = "C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Diagnostics\Logs\"  # Make clean the logs Office CleanLogfiles($TargetFolder) {     Write-Host -Debug -ForegroundColor Yellowish -BackgroundColor Cyan $TargetFolder      if (Test-Path $TargetFolder) {         $Now = Get-Engagement         $LastWrite = $Now.AddDays(-$days)         $Files = Go-ChildItem $TargetFolder -Recurse | Where-Object { $_.Proper name -similar "*.log" -or $_.Proper noun -similar "*.blg" -or $_.Name -like "*.etl" } | Where-Object { $_.lastWriteTime -le "$lastwrite" } | Select-Object FullName         foreach ($File in $Files) {             $FullFileName = $File.FullName               Write-Host "Deleting file $FullFileName" -ForegroundColor "yellow";              Remove-Item $FullFileName -ErrorAction SilentlyContinue | out-null         }     }     Else {         Write-Host "The folder $TargetFolder doesn't be! Cheque the folder path!" -ForegroundColor "red"     } } CleanLogfiles($IISLogPath) CleanLogfiles($ExchangeLoggingPath) CleanLogfiles($ETLLoggingPath) CleanLogfiles($ETLLoggingPath2)                

Brand sure that you lot change line 8. At the moment information technology is showing $days=2. That means information technology will cleanup logs from the Exchange Servers that are older than 2 days.

If you accept changed the path of the Exchange configuration, change the path in the line xi,12,13, and 14.

Save the file on the Substitution Server in the post-obit path C:\scripts\. Give information technology the name CleanupLogs.ps1

Requite your account permission access to the beneath four folders. If the script does not have permission, it volition non cleanup logs in that folder. I recommend making a service business relationship in Active Directory. Give the service user account read/write permission on the below 4 folders. Create a scheduled task to clear Exchange logs that volition run every day with the service user account.

                  C:\inetpub\logs\LogFiles\ C:\Plan Files\Microsoft\Exchange Server\V15\Logging\ C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Diagnostics\ETLTraces\ C:\Programme Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Diagnostics\Logs\                

Run the cleanup logs Exchange script

Before running the cleanup logs script

Before you run the script, have a await at how much gratis space you have on the bulldoze. See the before cleanup screen.

Run the script as Ambassador. Right-click the fileCleanupLogs.ps1 and click on Run with PowerShell. A PowerShell window will evidence up and the script is cleaning up the logs. Await till the PowerShell window disappears from the screen. It ways that the script finished.

Later on running the cleanup logs script

Have a await again at how much free space you have on the drive. See the after cleanup screen.

The script did cleanup 14GB of the Substitution logs. Did the cleanup logs Commutation script help y'all out?

Note: Practise y'all like to automate the script? Read more on how to Cleanup Exchange logs automatically with scheduled task.

Conclusion

In this commodity, you learned how to articulate Exchange logs with PowerShell. Information technology's a groovy script to cleanup logs on Exchange 2013/2016/2019 and go complimentary space. Don't forget to create a scheduled task to cleanup logs on the Substitution Server to automate the procedure.

If you enjoyed this article, yous may also like Motion mailbox to some other database with PowerShell. Don't forget to follow the states.

ALI TAJRAN is a passionate IT Architect, Information technology Consultant, and Microsoft Certified Trainer. He started Data Engineering at a very young historic period, and his goal is to teach and inspire others. Read more »

casadygaver1985.blogspot.com

Source: https://www.alitajran.com/cleanup-logs-exchange-2013-2016-2019/

Share this post