Solved

Message tracking logs - mailbox server being decomm - Exchange 2013

Posted on 2016-10-18
2
61 Views
Last Modified: 2016-11-01
Currently got 4 mailbox servers - call them A, B, C, and D.

All mailbox databases have been moved off A. All transport rules have been disabled on A,.
However, if you run message tracking query, obviously, there are log files on A pertaining to previous emails processed by A.

We now need to decommision server A. Problem is if we do this then surely we're losing all the message tracking logs off A? Admitedly, we're not getting any new messages processed by A but if we need to search tracking logs we're losing info if we turn off A.

Is there any way around this? Copying logs to one of the remainign servers etc?
0
Comment
Question by:paulfoel
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 6

Accepted Solution

by:
Niten Kumar earned 500 total points
ID: 41848034
The "Search Message Tracking Logs" section from the documentation states:

You can't copy the message tracking log files from another Exchange server and then search them by using the Get-MessageTrackingLog cmdlet. Also, if you manually save an existing message tracking log file, the change in the file's date-time stamp breaks the query logic that Exchange uses to search the message tracking logs.

But as the logs are plain text files in a simplistic structure you would be able to rename the log files to integrate them with the existing ones on a different server. The file name is something along MSTRKyyymmdd-n.log where n is an increment with a maximum of 9999. If you have not used a copy method which would pertain the last write access time stamp, you probably would want to set the copied files' last write timestamps e.g. using the LastWriteTime property of the FileInfo object accordingly.

Events obviously would not be in a chronological order - this might impact searchability by time (not sure if it really is going to be the case). I simply would try it out with a couple of manually renamed log files and script a renaming function for the rest, if it works out.

You also could pull the data using Get-MessageTrackingLog and dump it to a file using Export-Clixml so you could reload it later and filter on the results using Powershell functions, if needed. This however would require you to use a different function to load the object and deprive you of Get-MessageTrackingLog-specific filters.
0
 
LVL 1

Author Comment

by:paulfoel
ID: 41848036
Thanks. I'd thought of these things. Perhaps exporting the logs is the easiest option allowing for the drwabacks with this method. After all, in three months or so we wont need to worry any more.
0

Featured Post

Comparison of Amazon Drive, Google Drive, OneDrive

What is Best for Backup: Amazon Drive, Google Drive or MS OneDrive? In this free whitepaper we look at their performance, pricing, and platform availability to help you decide which cloud drive is right for your situation. Download and read the results of our testing for free!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In-place Upgrading Dirsync to Azure AD Connect
This article outlines some of the reasons why an email message gets flagged as spam on a recipient's end.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
This video discusses moving either the default database or any database to a new volume.

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question