RE: Transaction logs
The method I would use - that gets the same results really - is to run eseutil /mh on the database (it needs to be dismounted first). From: bounce-8435332-8066...@lyris.sunbelt-software.com [mailto:bounce-8435332-8066...@lyris.sunbelt-software.com] On Behalf Of Phil Thompson Sent: 20 February 2009 13:30 To: MS-Exchange Admin Issues Subject: RE: Transaction logs Yes I do, it's a long story. I just want to make sure that it is a valid work around before I do something that could cause more problems. Especially on a 'Friday'!! Thank you again. From: Jake Gardner [mailto:jgard...@ttcdas.com] Sent: Friday, February 20, 2009 8:25 AM To: MS-Exchange Admin Issues Subject: RE: Transaction logs Do you have a backup solution like Backup Exec? I use BE to flush my commited logs. I've never had to use the steps you mention, but I know they are the ones to use when you need to manually flush the logs. Thanks, Jake Gardner TTC Network Administrator Ext. 246 From: Phil Thompson [mailto:ph...@wpiinc.com] Sent: Friday, February 20, 2009 8:07 AM To: MS-Exchange Admin Issues Subject: Transaction logs I have 30 some GB of transaction logs that are no longer used. (for what ever reasons).. I read this article that gave instructions on how to tell where the last log that was committed. The instructions are below. I want to run this by you'll before I do this. It is a valid thing to do? * How to manually (and safely) purge Exchange Server transaction logs To do this from a command line, go to the \Program Files\Exchsvr\bin directory on the server and run the following command: eseutil /mk C:\Program Files\Exchsrvr\MDBDATA\E00.chk (The quotes are important, as they delimit the full pathname for the file.) In the results returned you'll see these lines: LastFullBackupCheckpoint: (0x0,0,0) Checkpoint: (0x2,EC2,1C7) The first number in the Checkpoint entry -- 0x2 -- is a hexadecimal number that refers to the last checkpoint log. Therefore, any logs numbered E01.log or earlier could be removed. If the checkpoint was 0x14C8, then logs numbered E0014C7.log or earlier could be removed. Thank you, Phil ***Teletronics Technology Corporation*** This e-mail is confidential and may also be privileged. If you are not the addressee or authorized by the addressee to receive this e-mail, you may not disclose, copy, distribute, or use this e-mail. If you have received this e-mail in error, please notify the sender immediately by reply e-mail or by telephone at 267-352-2020 and destroy this message and any copies. Thank you. *** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Transaction logs
It may be a bit late, but I would just do a NTbackup of the Exchange Store. It will flush any log files and give you a good backup before doing anything else.. From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk] Sent: Monday, February 23, 2009 4:45 AM To: MS-Exchange Admin Issues Subject: RE: Transaction logs The method I would use - that gets the same results really - is to run eseutil /mh on the database (it needs to be dismounted first). From: bounce-8435332-8066...@lyris.sunbelt-software.com [mailto:bounce-8435332-8066...@lyris.sunbelt-software.com] On Behalf Of Phil Thompson Sent: 20 February 2009 13:30 To: MS-Exchange Admin Issues Subject: RE: Transaction logs Yes I do, it's a long story. I just want to make sure that it is a valid work around before I do something that could cause more problems. Especially on a 'Friday'!! Thank you again. From: Jake Gardner [mailto:jgard...@ttcdas.com] Sent: Friday, February 20, 2009 8:25 AM To: MS-Exchange Admin Issues Subject: RE: Transaction logs Do you have a backup solution like Backup Exec? I use BE to flush my commited logs. I've never had to use the steps you mention, but I know they are the ones to use when you need to manually flush the logs. Thanks, Jake Gardner TTC Network Administrator Ext. 246 From: Phil Thompson [mailto:ph...@wpiinc.com] Sent: Friday, February 20, 2009 8:07 AM To: MS-Exchange Admin Issues Subject: Transaction logs I have 30 some GB of transaction logs that are no longer used. (for what ever reasons).. I read this article that gave instructions on how to tell where the last log that was committed. The instructions are below. I want to run this by you'll before I do this. It is a valid thing to do? * How to manually (and safely) purge Exchange Server transaction logs To do this from a command line, go to the \Program Files\Exchsvr\bin directory on the server and run the following command: eseutil /mk C:\Program Files\Exchsrvr\MDBDATA\E00.chk (The quotes are important, as they delimit the full pathname for the file.) In the results returned you'll see these lines: LastFullBackupCheckpoint: (0x0,0,0) Checkpoint: (0x2,EC2,1C7) The first number in the Checkpoint entry -- 0x2 -- is a hexadecimal number that refers to the last checkpoint log. Therefore, any logs numbered E01.log or earlier could be removed. If the checkpoint was 0x14C8, then logs numbered E0014C7.log or earlier could be removed. Thank you, Phil ***Teletronics Technology Corporation*** This e-mail is confidential and may also be privileged. If you are not the addressee or authorized by the addressee to receive this e-mail, you may not disclose, copy, distribute, or use this e-mail. If you have received this e-mail in error, please notify the sender immediately by reply e-mail or by telephone at 267-352-2020 and destroy this message and any copies. Thank you. *** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Transaction logs
Sounds right. If you want to be extra careful, you could change your transaction logging to another directory first. From: Phil Thompson [mailto:ph...@wpiinc.com] Sent: Friday, February 20, 2009 7:07 AM To: MS-Exchange Admin Issues Subject: Transaction logs I have 30 some GB of transaction logs that are no longer used. (for what ever reasons).. I read this article that gave instructions on how to tell where the last log that was committed. The instructions are below. I want to run this by you'll before I do this. It is a valid thing to do? * How to manually (and safely) purge Exchange Server transaction logs To do this from a command line, go to the \Program Files\Exchsvr\bin directory on the server and run the following command: eseutil /mk C:\Program Files\Exchsrvr\MDBDATA\E00.chk (The quotes are important, as they delimit the full pathname for the file.) In the results returned you'll see these lines: LastFullBackupCheckpoint: (0x0,0,0) Checkpoint: (0x2,EC2,1C7) The first number in the Checkpoint entry -- 0x2 -- is a hexadecimal number that refers to the last checkpoint log. Therefore, any logs numbered E01.log or earlier could be removed. If the checkpoint was 0x14C8, then logs numbered E0014C7.log or earlier could be removed. Thank you, Phil ** Note: The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Transaction logs
Do you have a backup solution like Backup Exec? I use BE to flush my commited logs. I've never had to use the steps you mention, but I know they are the ones to use when you need to manually flush the logs. Thanks, Jake Gardner TTC Network Administrator Ext. 246 From: Phil Thompson [mailto:ph...@wpiinc.com] Sent: Friday, February 20, 2009 8:07 AM To: MS-Exchange Admin Issues Subject: Transaction logs I have 30 some GB of transaction logs that are no longer used. (for what ever reasons).. I read this article that gave instructions on how to tell where the last log that was committed. The instructions are below. I want to run this by you'll before I do this. It is a valid thing to do? * How to manually (and safely) purge Exchange Server transaction logs To do this from a command line, go to the \Program Files\Exchsvr\bin directory on the server and run the following command: eseutil /mk C:\Program Files\Exchsrvr\MDBDATA\E00.chk (The quotes are important, as they delimit the full pathname for the file.) In the results returned you'll see these lines: LastFullBackupCheckpoint: (0x0,0,0) Checkpoint: (0x2,EC2,1C7) The first number in the Checkpoint entry -- 0x2 -- is a hexadecimal number that refers to the last checkpoint log. Therefore, any logs numbered E01.log or earlier could be removed. If the checkpoint was 0x14C8, then logs numbered E0014C7.log or earlier could be removed. Thank you, Phil ***Teletronics Technology Corporation*** This e-mail is confidential and may also be privileged. If you are not the addressee or authorized by the addressee to receive this e-mail, you may not disclose, copy, distribute, or use this e-mail. If you have received this e-mail in error, please notify the sender immediately by reply e-mail or by telephone at 267-352-2020 and destroy this message and any copies. Thank you. *** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Transaction logs
Yes I do, it's a long story. I just want to make sure that it is a valid work around before I do something that could cause more problems. Especially on a 'Friday'!! Thank you again. From: Jake Gardner [mailto:jgard...@ttcdas.com] Sent: Friday, February 20, 2009 8:25 AM To: MS-Exchange Admin Issues Subject: RE: Transaction logs Do you have a backup solution like Backup Exec? I use BE to flush my commited logs. I've never had to use the steps you mention, but I know they are the ones to use when you need to manually flush the logs. Thanks, Jake Gardner TTC Network Administrator Ext. 246 From: Phil Thompson [mailto:ph...@wpiinc.com] Sent: Friday, February 20, 2009 8:07 AM To: MS-Exchange Admin Issues Subject: Transaction logs I have 30 some GB of transaction logs that are no longer used. (for what ever reasons).. I read this article that gave instructions on how to tell where the last log that was committed. The instructions are below. I want to run this by you'll before I do this. It is a valid thing to do? * How to manually (and safely) purge Exchange Server transaction logs To do this from a command line, go to the \Program Files\Exchsvr\bin directory on the server and run the following command: eseutil /mk C:\Program Files\Exchsrvr\MDBDATA\E00.chk (The quotes are important, as they delimit the full pathname for the file.) In the results returned you'll see these lines: LastFullBackupCheckpoint: (0x0,0,0) Checkpoint: (0x2,EC2,1C7) The first number in the Checkpoint entry -- 0x2 -- is a hexadecimal number that refers to the last checkpoint log. Therefore, any logs numbered E01.log or earlier could be removed. If the checkpoint was 0x14C8, then logs numbered E0014C7.log or earlier could be removed. Thank you, Phil ***Teletronics Technology Corporation*** This e-mail is confidential and may also be privileged. If you are not the addressee or authorized by the addressee to receive this e-mail, you may not disclose, copy, distribute, or use this e-mail. If you have received this e-mail in error, please notify the sender immediately by reply e-mail or by telephone at 267-352-2020 and destroy this message and any copies. Thank you. *** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja~
RE: Transaction Logs
It all depends on how busy the server is. Are those 2000 users sending five messages each a day or five hundred? I have 9Gb for logs on a server with 200 users. Most space I've seen used up was around 1Gb, which built up over three days when the tape drive was broken so we ran no backup. Scaling that up, you'd have been over 9Gb in a similar situation. If I was building a new server today, with disk prices the way they are, I'd probably spec a mirrored pair of 18Gb drives for logs (or even more... can you ever have too much disk space?). -Original Message- From: Brad Anstett [mailto:[EMAIL PROTECTED]] Sent: 15 December 2001 18:42 To: MS-Exchange Admin Issues Subject: Transaction Logs I'm installing a new server and would like some guidelines on how big the disk for the logs would be. I don't want circular logging. The organization is about 2000 users. Is 9GB big enough? Thanks Brad List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Transaction Logs
Hi Brad. Out of curiosity, is this Exchange5.5 or 2000? That doesn't really make much difference in terms of transaction log requirements, but 2000 average users on an Exchange5.5 machine is quite a few Ultimately, requirements for things like transaction logs, depend on usage. Do your users send lots of attachments, high volumes of email? 9GB might be fine if you are completing full online backups nightly. I don't think that will leave you much room if you are unable to perform a backup for a few days. Just my thoughts. William Lefkovics, MCSE, A+, WLKMMAS -Original Message- From: Brad Anstett To: MS-Exchange Admin Issues Sent: 12/15/01 10:42 AM Subject: Transaction Logs I'm installing a new server and would like some guidelines on how big the disk for the logs would be. I don't want circular logging. The organization is about 2000 users. Is 9GB big enough? Thanks Brad List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
