markmagnus
asked on
Exchange 2013 Tmp files with exchange databases files edb
files ending with the tmp extension are showing up in the database directories of our 2013 exchange server. These TMP files have zero bytes. They have the current days time stamp while the EDB database file has a date that is several days old. No database goes more than two days without being backed up. We are using Veritas to do full backups at the database level and not incremental backups aka Veeam. If I dismount and remount the database manually the tmp files go away and the edb file gets the current date. Not seeing anything in the application event which might point the way. No end user complaints.
Last Comment
Hypercat (Deb)
The tmp files are created while processing the transaction logs. They should be deleted automatically (and possibly be replaced by others) after a short period of time. Are they staying around for long periods of time?
The backups should be triggering a log file consolidation with Exchange creating new blanks as it goes along.
The Exchange mailbox databases are sensitive to fragmentation. It's a good idea to put either the databases or the log files into their own partition to eliminate a no-mount situation due to fragmentation.
The Exchange mailbox databases are sensitive to fragmentation. It's a good idea to put either the databases or the log files into their own partition to eliminate a no-mount situation due to fragmentation.
That's normal. They should get flushed/truncated when your exchange aware backup runs.
ASKER
the log files and the database files are on separate RAID arrays. No database goes more than 2 days before being backed up. Backups are full edb backups every time
ASKER
I have 51 databases on that server. 11 of those databases have the tmp files. Another backup was run against those databases and none of the tmp files cleared. dismounting and mounting the database seems to clear the tmp files. These all go back to 3/8 which is the day after the backups were run. Some event must have triggered this. This weekend if the backup doesn't clear these files I will dismount and mount the affected databases and then see if they begin to reappear. If they are related to the log files I find it odd that don't appear in the log files directories on the log file RAID but appear within the databases location. I will report back after the weekend about the status of the tmp files.
ASKER
Update. We have been doing a lot of cleanup and most of the databases have a meaningful amount of white space. That can explain why the database dates don't change but doesn't seem to explain why the tmp files don't go away when the backups run. Veritas support says I am crazy to blame it on them. My general feelings on this are that just because I am crazy doesn't mean the latest version of their software is not defective.
Mark Magnus
Mark Magnus
ASKER
we kept looking at this and turned off the firewall on the backup server. This seems to have resolved the issue. The tmp files are closed and deleted when the backup is run. Will have to spend some time reading the fine manual to see if the Veritas documentation addresses what ports should be open. Tech support had no clue.
Mark Magnus
Mark Magnus
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Glad to know you sorted out and thanks for sharing the solution. :))
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
