Tonight I stumbled across a limitation in Exchange 2010 when moving a vast amount of Transaction Logs to volume on an Exchange 2010 SP2 server. This server had over 100,000 logs which needed to be moved to an alternative location, when utilising the Move-DatabasePath command with the -LogFolderPath switch, the command would hang approximately 10 minutes then fail with the following error.
Failed to connect to target server "ExchangeServer". Error: WMI exception occurred on server 'ExchangeServer.domain.local': Quota violation
+ CategoryInfo : InvalidOperation: (Mailbox Database 0529333988:DatabaseIdParameter) [Move-DatabasePath],
InvalidOperationException
+ FullyQualifiedErrorId : 7897D20B,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveDatabasePath
After doing some research I discovered that this only occurs when attempting to move a ridiculously large quantity of log files.
To resolve this problem you must purge the transaction logs first before performing the operation. This can be done in 3 ways::
Failed to connect to target server "ExchangeServer". Error: WMI exception occurred on server 'ExchangeServer.domain.local': Quota violation
+ CategoryInfo : InvalidOperation: (Mailbox Database 0529333988:DatabaseIdParameter) [Move-DatabasePath],
InvalidOperationException
+ FullyQualifiedErrorId : 7897D20B,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveDatabasePath
After doing some research I discovered that this only occurs when attempting to move a ridiculously large quantity of log files.
To resolve this problem you must purge the transaction logs first before performing the operation. This can be done in 3 ways::
- Perform a Full Backup of the Server which in effect will purge the logs. This can be performed by using Windows Server Backup or another product.
- Enable Circular Logging, dismount/remount the database, then Re-enable Circular Logging.
- Manually delete the log files using windows explorer (SHIFT + DELETE). Do not perform this procedure without checking first that all log files have been played into the database, doing so could result in loss of data. Please see the following post for manually flushing transaction logs http://clintboessen.blogspot.com.au/2010/09/flush-transaction-logs-in-exchange.html
Microsoft always has this stupid hidden errors. In our case we've moved 180 mailboxes from exchange 2003 to exchange 2010, after we found thousands of transaction logs. We couldn't move the mailbox from drive c: to a secondary drive d:
ReplyDeleteWe just started a Full VSS Backup. We'll try again later.
of course if the backup "DO WHAT IT'S SUPPOSED TO DO WITH THE LOG FILES"
BB
We take the frustration out of parking management for Apartments, Home Owners Associations, Condominiums, Townhouses Co-ops, and other parking areas.Webparkingsoftware.com has reinvented how parking management should be done.
ReplyDeleteGuest parking
Thank You, Clint! This really save my Day!
ReplyDeleteI've a SBS 2011 and, when I setup it, I've used the SBS console to move the Exchange Data to another partition. Yesterday, I've notice that the SBS Console change the path of the MailBox Database, but not the Transaction Logs Path, so I had the C: partition completelly full.
Luckily, the Mailbox DB was consistent, so I could move the log without problems! After that the Mailbox move procedure works correctly on 17 seconds!
violation management
ReplyDeleteWe take the frustration out of parking management for Apartments, Home Owners Associations, Condominiums, Townhouses Co-ops, and other parking areas. www.Webparkingsoftware.com has reinvented how parking management should be done and more information then contact us :
CBT SOLUTIONS, INC.
23785 El Toro Road Suite 122
Lake Forest, CA 92630
call : 1-855-228-0411
That was great! Thank you!
ReplyDelete