Deprecated: Function set_magic_quotes_runtime() is deprecated in /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php on line 1505 Call Stack: 0.0001 326800 1. {main}() /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:0 0.0003 327652 2. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:25 0.0006 328940 3. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php:20 0.0018 403244 4. vB_Registry->vB_Registry() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php:43 0.0019 403900 5. vB_Input_Cleaner->vB_Input_Cleaner() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php:2337
Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /archive/global.php on line 26

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3113

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265
manually delete transaction log files. [Archive] - MCSE
PDA

View Full Version : manually delete transaction log files.

mary
03-29-04, 05:38 PM
something
The log disk on the Exchange server is full.
I need to manually delete transaction log files. (there is 30-40Gb transaction log files)

How can I safely remove the transaction log files?

If I shutdown and restart the IS, all transactions are writen to the database
and I should be able to safely remove the transaction log files. Or can I ???

If I run eseutil /mk edb.chk, I can se which transactions log files that have been writen to the database and
I should be able to safely remove transaction log files created before the last log file writen to db. Or can I ???


Yes I know that a full online backup purges log files but I need to manually remove them.
Mark Fugatt [MVP]
03-29-04, 05:38 PM
something
Never delete them manually, why is your backup not purging them?

--
Mark Fugatt
Exchange MVP
http://www.exchangetrainer.com
http://www.msexchange.org
"mary" <anonymous@discussions.microsoft.com> wrote in message
news:2668CAE7-CEB6-4CA0-9A6B-524706B62D0E@microsoft.com...
> The log disk on the Exchange server is full.
> I need to manually delete transaction log files. (there is 30-40Gb
transaction log files)
>
> How can I safely remove the transaction log files?
>
> If I shutdown and restart the IS, all transactions are writen to the
database
> and I should be able to safely remove the transaction log files. Or can I
???
>
> If I run eseutil /mk edb.chk, I can se which transactions log files that
have been writen to the database and
> I should be able to safely remove transaction log files created before the
last log file writen to db. Or can I ???
>
>
> Yes I know that a full online backup purges log files but I need to
manually remove them.
Jaclynn Hiranaka [MSFT]
03-29-04, 05:38 PM
something
If you shut down the IS or simply dismount the store all of the transaction
logs should be committed to the database. You should be able to do an
eseutil /mh to dump the header of the database to determine if it is in
clean shutdown.

I would agree with Mark in that you should be doing regular online full
backups that should be purging your transaction log files.

I would never say delete the log files but if you are trying to make up for
space and your databases are in a consistent state move them to an
alternalte drive with more space.

--
Hope that helps.

-------------------------
Jaclynn Hiranaka
Enterprise Messaging Support

This posting is provided "AS IS" with no warranties, and confers no rights.
© 2003 Microsoft Corporation. All rights reserved.


"mary" <anonymous@discussions.microsoft.com> wrote in message
news:2668CAE7-CEB6-4CA0-9A6B-524706B62D0E@microsoft.com...
> The log disk on the Exchange server is full.
> I need to manually delete transaction log files. (there is 30-40Gb
transaction log files)
>
> How can I safely remove the transaction log files?
>
> If I shutdown and restart the IS, all transactions are writen to the
database
> and I should be able to safely remove the transaction log files. Or can I
???
>
> If I run eseutil /mk edb.chk, I can se which transactions log files that
have been writen to the database and
> I should be able to safely remove transaction log files created before the
last log file writen to db. Or can I ???
>
>
> Yes I know that a full online backup purges log files but I need to
manually remove them.
vBulletin v3.6.2, Copyright ©2000-2010, Jelsoft Enterprises Ltd.