Video Screencast Help

Backing up Exchange 2013 and removing log files

Created: 30 Dec 2013 • Updated: 23 Jun 2014 | 4 comments
This issue has been solved. See solution.

Exchange 2013 running on server with OS Windows Server 2012 Datacenter. Backup Exec 2012 running on server OS Windows 2008.

Currently there is no special license for Exchange installed on the BE server. My understanding is this means that the Exchange server is getting backed up as if it were a sort of file server and that no mailboxes can be restored. Correct?

If the above is correct, then if the Exchange license is installed, will this then delete the log files from the Exchange server as part of the backup? If not, how do we keep the Exchange server drive from filling up with log files?

Or will this all have to wait until the next version of Backup Exec which will be fully Exchange 2013 compatible?

Jonathan

Operating Systems:

Comments 4 CommentsJump to latest comment

lmosla's picture

Yes, the AWS without the Exchange license will only back up flat files on the Exchange server and not communicate with Exchange that the logs need to be flushed.

pkh's picture

When you have the license for Agent for Applications and Databases and is backing up Exchange through the Exchange agent, BE will truncate the logs automatically whenever you backup the mailboxes. You don't have to wait for the next release of BE

SOLUTION
JLeslie's picture

Thank you very much for that information! That is exactly what I was trying to be certain of.

 

 

Jonathan

Colin Weaver's picture

BTW if you do not have the application and databases license, it is likely that you are NOT backing up Exchange data at all as Active File Exclusion may be blocking the EDB etc files that form part of Exchange. Have you checked to see if these files are selectable for restore and / or have you analyzed the byte count against the volume to make sure something close to the expected data is being backed up .

 

This is potentially a way more important reason to have the correct agent licenses enabled than just the log truncation .

 

Note to truncate the logs you actually need the correct agent license and you also need to backup the information store and not just the volume that contains the information store.