Move First Storage Group Logs
Hi, I'm running SBS2008 with Exchange 2007. It's been one year we are using it and everything is going fine. However, my system disk start to run out of space, so I checked which directories are getting too big and I found the First Storage Group Logs. From the beginning I had moved the database to my other data volume (E:), but I just figured out I didn't moved the log files. I used the asistant to move the Second Storage Group Logs (around 4 Gb), and it worked just fine. Then I tried to move the First Storage Group Logs, but I get an error: "WMI exception occured on server ‘exchangeserver.domain.local’: Quota violation". Seems like there is too much logs to be move that way (20 Gb). I tried to run a backup of the database in the storage group to truncate the logs, but it didn't clean any log (the backup worked fine though). I'm not an Exchange expert and I don't really know how to manage this. I've read on forum that I could manually copy (eg xcopy or Robocopy) the log files to the new location and edit the storage group log path using ADSIEdit.msc. But I don't even know how to use ADSIEdit and lot of people says it's the last chance solution and a bit risky. Does anyone could help me on that problem? I there any other simple option to move the Logs? Thank you.
January 5th, 2012 10:19pm

First, don't move the files manually. There are other methods that should be explored first. I am worried about the backup not properly truncating your logs. Is your database in cluster? Is there a secondary copy being used either (SCR copy)? Check your event viewer (application log on the Exchange server) and backup logs for details on the backup. As a temporary work around you could enable Circular Logging on the database. Once enabled, you need to mount and dismount the database. You will then see the amount of logs reduce to a very low amount. See this article for how to do this: http://technet.microsoft.com/en-us/library/bb331968(EXCHG.80).aspx Once the logs file count is reduced, move the the logs again (as you did the first time when it failed) and you should not run into the issue with the quota being reached. After you move the log files, I would remove the Circular Logging setting also dismounting and mounting the database after the change. Hope that helps. JAUCG
Free Windows Admin Tool Kit Click here and download it now
January 6th, 2012 2:21am

First, don't move the files manually. There are other methods that should be explored first. I am worried about the backup not properly truncating your logs. Is your database in cluster? Is there a secondary copy being used either (SCR copy)? Check your event viewer (application log on the Exchange server) and backup logs for details on the backup. As a temporary work around you could enable Circular Logging on the database. Once enabled, you need to mount and dismount the database. You will then see the amount of logs reduce to a very low amount. See this article for how to do this: http://technet.microsoft.com/en-us/library/bb331968(EXCHG.80).aspx Once the logs file count is reduced, move the the logs again (as you did the first time when it failed) and you should not run into the issue with the quota being reached. After you move the log files, I would remove the Circular Logging setting also dismounting and mounting the database after the change. Hope that helps. JAUCG
January 6th, 2012 10:10am

The database is not in cluster. I never setup a secondary copy so I don't think there is one. I checked the events and backup logs but I don't see anything strange about backups. I'm going to try the to enable Circular Logging and I'll tell you the result. Thanx
Free Windows Admin Tool Kit Click here and download it now
January 7th, 2012 9:37pm

On Fri, 6 Jan 2012 07:10:38 +0000, JAUCG wrote: > > >First, don't move the files manually. There are other methods that should be explored first. > >I am worried about the backup not properly truncating your logs. Is your database in cluster? Is there a secondary copy being used either (SCR copy)? Check your event viewer (application log on the Exchange server) and backup logs for details on the backup. > >As a temporary work around you could enable Circular Logging on the database. Once enabled, you need to mount and dismount the database. You will then see the amount of logs reduce to a very low amount. See this article for how to do this: http://technet.microsoft.com/en-us/library/bb331968(EXCHG.80).aspx > >Once the logs file count is reduced, move the the logs again (as you did the first time when it failed) and you should not run into the issue with the quota being reached. > >After you move the log files, I would remove the Circular Logging setting also dismounting and mounting the database after the change. If you do this you should make a backup of the database after you've disabled circular logging, and make that backup right away -- like immediately. Any backups you have will be pretty useless becasue you'll be missing the log files necessary to recover the database if you ever had to restore it. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
January 7th, 2012 10:38pm

By the way, once Circular Logging is activated, how long should it take to reduce log files? Few hours? Days? Weeks? Thank you
Free Windows Admin Tool Kit Click here and download it now
January 7th, 2012 10:42pm

On Sun, 8 Jan 2012 03:33:34 +0000, teraDev wrote: >By the way, once Circular Logging is activated, how long should it take to reduce log files? Few hours? Days? Weeks? It's a pretty quick process. The log files should be reduced within an hour or so, maybe a lot less (depends on how many log files you have). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
January 8th, 2012 11:55am

Well.... Houston, we have a problem ! I let it the whole night with Circular Logging, and I still have all my logs in the First Storage Group logs folder. Folder size is still increasing. What else can I do? I have 21,414 log files for 20.9 Gb ! I read it would be a big deal if there is no more space available on the system drive. I still have some space available on this drive so it won't happened, but I want to fix that before having problems. Please, help ! Thanks
Free Windows Admin Tool Kit Click here and download it now
January 8th, 2012 2:11pm

Did you dismount the database and then re-mount it? You have to do that so the new settings are read. Then the logs should reduce fairly quickly. Thanks.JAUCG
January 8th, 2012 4:45pm

You're the man !!! Thank you so much ! Everything worked perfectly ! Once dismounted then remounted, it took less than 2 seconds to reduce all the log files. Then I moved the log folder to my other drive, I removed the Circular Logging, then dismount/re-mount, and I'm fine ! Thanks again for you great help!
Free Windows Admin Tool Kit Click here and download it now
January 8th, 2012 5:03pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics