2010-04-01 09:03 AM
I hope this is the correct area for posting this.
Our Exchange server lod drive (iSCSI dedicacted) is filling up every month causing us to have to go in and manually delete the log entries from the following location: L:\SME_SnapInfo\EXCH__SECURITY-MAIL\SG__First Storage Group
I've gone into snapdrive and snapmanager on the Exchange server, but unable to locat the settings to correct this.
2010-04-04 10:46 AM
Are you asking about purging Exchange log files? After a successful VSS backup including checksum verification, Exchange will truncate the log files. If the checksum verification is not done, or fails, then the log files will not be truncated.
2010-04-04 03:56 PM
The retention of the backup sets is controlled by the retention parameters in the backup job in Windows Scheduled Tasks. If you are basing your retention on days, the you will see a -RetainDays parameter. If you are basing your retention on the number of backups you want to keep online, then you will see a -RetainBackups parameter.
If SME backup or verification fails, transaction logs are not truncated and retention policies are not enforced.
Manually, deleting logs is a bad thing to do as this can cause VSS errors which can result in SME backup failures. Also, manually deleting snapinfo log data outside of SME delete backup action can cause problems with SME retention working properly.
If you are looking to free up space in your log LUN, I suggest that you do the following:
1. Check to see if SME backups and verification are working properly. This can be done by looking at the backup logs in the Report section of SME. If the backups and verification are working correctly, then you should look at three ways to alliviate your space problems: 1) Increase the size of the Transaction Log LUN using SnapDrive, or 2) Decrease the amount of backup sets that you are keeping online, or 3) Manually delete SME backup sets using the "Delete Backup" action in SME.
To increase the size of the Transaction Log LUN, you will need to increase the size of the flexvol where the LUN is located. The size you will increase the flexvol will be the size of the LUN plus any fractional reserve.
To decrease the amount of backup sets that you are keeping online, modify either the -RetainDays or -RetainBackups in the SME backup job in Windows Scheduled tasks on the Exchange server.
2010-04-06 08:07 AM
I checked the scheduled job as you said and -RetainBackups set for "8"
I did look at the last backup job and saw and error that it couldn't locate eseutil.exe followed by errors everytime that executable was called. I've attached the log file.
Thanks for your help,
2010-04-06 10:25 AM
I would if I knew where the proper location was. I see a copy in exchsrvr\bin, which is where I imagine it should be because that's were exmerge sits along with other utlities.
2010-04-06 08:26 PM
Thanks for providing the log from the backup. The backup job is not configured to do a verification after a backup.
The error that you are seeing is where SME is querying eseutil the checkpoint log for which logs have been committed.
If SME cannot determine which logs have been committed, it cannot archive the logs to snapinfo so that one day they will be purged per SME retention policies.
If you open a command line on the exchange server and run this command:
eseutil /mk L:\Exchsrvr\mdbdata\E00.chk
What is the result?
2010-04-07 08:08 AM
Mark, here is the output.
E:\Exchsrvr\bin>eseutil /mk L:\exchsrvr\mdbdata\E00.chk
Microsoft(R) Exchange Server Database Utilities
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
Checkpoint file: L:\exchsrvr\mdbdata\E00.chk
FullBackup time: 04/07/2010 06:00:18
IncBackup time: 00/00/1900 00:00:00
Signature: Create time:02/25/2005 14:08:22 Rand:2328769 Computer:
( off, 252, 12600, 1741, 12600, 500, 10240, 229376)
Operation completed successfully in 1.62 seconds.
Thanks for your help,
2010-04-07 10:22 AM
This is good. Eseutil.exe is not damaged.
Can you open a command prompt and type the command: path
Please post the output of this command.
Also, I would like you to re-run the SME Configuration wizard and please set the verification server to be the exchange server. SME should detect the path of eseutil.exe. If not, then manually set the path.
After you have done that, please re-run the backup.