Defragment with the Eseutil utility

Sun, 09 Dec 2007 07:01:27 GMT

How to defragment with the Eseutil utility (Eseutil.exe)

View products that this article applies to.

Article ID	:	192185
Last Review	:	October 25, 2007
Revision	:	7.2

This article was previously published under Q192185

SUMMARY

You can use the Eseutil utility to defragment the information store and directory in Microsoft Exchange Server 5.5 and to defragment the information store in Microsoft Exchange 2000 Server and in Microsoft Exchange Server 2003. Eseutil examines the structure of the database tables and records (which can include reading, scanning, repairing, and defragmenting) the low level of the database (Ese.dll).

Eseutil is located in the Winnt\System32 folder in Exchange Server 5.5 and in the Exchsrvr/Bin folder in Exchange 2000 and in Exchange 2003. The utility can run on one database at a time from the command line.

Back to the top

MORE INFORMATION

The defragmentation option makes used storage contiguous, eliminates unused storage, and compacts the database, which reduces the database's size. Eseutil copies database records to a new database. When defragmentation is complete, the original database is deleted or saved to a user-specified location, and the new version is renamed as the original. If the utility encounters a bad record, the utility stops and displays an error message.

Back to the top

Defragmenting an Exchange Server 5.5 database

Note Defragmenting a database requires free disk space equal to 110 percent of the size of the database that you want to process. To determine the actual space required, follow these steps:

Article ID	:	192185
Last Review	:	October 25, 2007
Revision	:	7.2

To defragment the Exchange Server 5.5 database, follow these steps:

Stop the service of the database you wish to defragment by using the Services tool in Control Panel.

�	For the Exchange Directory database, stop the Microsoft Exchange Directory service.
�	For the Exchange Mailbox or Public Folder databases, stop the Microsoft Exchange Information Store service.

At the command prompt, change to the Winnt\System32 folder, and then type the eseutil /d command, a database switch, and any options that you want to use.

For example, the following command runs the standard defragmentation utility on the directory and saves the copy in the user-defined file:

C:\winnt\system32> eseutil /d /ds /tc:\dbback\tempdfrg.edb /p

Use one of the following database switches to run Eseutil on a specific database.

Option         Description
----------------------------------------
/ds            Directory

/ispriv        Private information store

/ispub         Public information store

Use one or more of the following options to specify the operations that you want to perform on the database.

Option         Description
-----------------------------------------------------------------------
/b       Makes a backup copy of the original uncompacted database
               at the specified location.

/p             Retains and preserves the original uncompacted database
               in its original location and stores the new compacted
               database in the default file Exchsrvr\Bin\Tempdfrg.edb.

/t  Creates and renames the new compacted database in the
               specified path.

/o             Does not display the Microsoft Exchange Server banner.

Back to the top

Defragmenting an Exchange 2000 or Exchange 2003 database

Note Defragmenting a database requires free disk space equal to 110 percent of the size of the database being processed.

1.	In Exchange System Manager, right-click the information store that you want to defragment, and then click Dismount Store.
2.	At the command prompt, change to the Exchsrvr\Bin folder, and then type the eseutil /d command, a database switch, and any options that you want to use.

For example, the following command runs the standard defragmentation utility on a mailbox store database:

C:\program files\exchsrvr\bin> eseutil /d c:\progra~1\exchsrvr\mdbdata\priv1.edb

Use the following database switch to run Eseutil defragmentation on a specific database:

eseutil /d <database_name> [options]

Defragmentation/Compaction

Performs off-line compaction of a database.

Syntax: eseutil /d <database_name> [options]

Parameters: <database_name> is the file name of the database that you want to compact.

You are not required to use any of the following options, but you can use one or more (separated by a space) to specify the operations that you want to perform on the database.

Option         Description
----------------------------------------------------------------
/b   Make a backup copy under the specified name

/t   Set the temporary database name (the default is
               Tempdfrg.edb)

/s       Set the streaming file name (the default is NONE)

/f       Set the temporary streaming file name (the default
               is Tempdfrg.stm)

/p             Preserve the temporary database (in other words,
               do not instate)

/o             Suppress logo

/i             Do not defragment streaming file

Span Ports

Mon, 05 Nov 2007 16:55:01 GMT

Cons Cmds

ena

config t

monitor session (#) source interface (FastEthernet0/47) Both

monitor session (#) destination interface (FastEthernet0/48) ingress unt

monitor session 1 source interface Fa0/48
monitor session 1 destination interface Fa0/47 encapsulation replicate ingress untagged vlan 1

http://www.cisco.com/en/US/docs/switches/lan/catalyst2960/software/release/12.2_25_see/configuration/guide/swspan.html#wp1207676

Example Code:��

LCS-CAT2960(config)#mon ses 1 sourc int fa0/48 both
LCS-CAT2960(config)#mon ses 1 des int fa0/47 ing unt vlan 1

********************************************************************************************************

monitor session 1 source interface Fa0/48
monitor session 1 destination interface Fa0/47 encapsulation replicate ingress untagged vlan 1
end

LCS-CAT2960B#show monitor
Session 1
---------
Type�� : Local Session
Source Ports�� :
�� Both�� : Fa0/48
Destination Ports : Fa0/47
�� Encapsulation : Replicate
�� Ingress : Enabled, default VLAN = 1
�� Ingress encap : Untagged

Manualy remove Exchange server transaction logs

Mon, 05 Nov 2007 16:40:11 GMT

How to manualy remove Exchange server transaction logs.

Database states

If an Exchange Server database has not been shut down correctly, the database remains "attached" to its transaction log stream. This means that not all the data from the transaction log file has been secured to the database files. During the next startup of the database, Exchange Server detects this condition. Exchange Server then applies the missing data to the database files. If the log files that contain this data are not available, the database cannot be started.

When an Exchange Server database is shut down correctly, that database "detaches" from its transaction log stream. In this situation, the database does not require the previous transaction log files when that database next starts. However, these log files could be useful if a backup or an earlier version of the database were to be restored. The log files will be used to roll the database forward from the time of backup. Therefore, transaction log files should not be permanently deleted until you are sure that you will not want to replay them into an older version of the database.

Before you manually remove any transaction log files, you should determine the state of any database that used the particular transaction log files. In this situation, determine the "attach" or "detach" state of each database that used the particular transaction log files. You can determine whether a database is attached or detached by examining the database file header by using the Eseutil utility's /MH command switch. For example, run the following command at a command prompt where database_name is the name of the database that you want to examine:

eseutil /MH database_name

For example, to examine the Mailbox Store (Server1) database, type

eseutil /MH �Mailbox Store (Server1).edb�

Note To examine the header of a database by using the Eseutil command, the database must be stopped.

After you run this command, examine the State value in the header information that appears. The State value provides the following information about whether the database has been correctly detached:

�
If the database has been correctly detached, the state value is either Clean Shutdown or Consistent, depending on the version of Exchange Server that is running.
�
If the database has not been correctly detached, the state value is Dirty Shutdown or Inconsistent. This means that some of the existing transaction log files contain outstanding transactions that are required by the database. If you remove the transaction log files in this situation, the database cannot be started again unless you restore the database from a backup or unless you repair the database by using the Eseutil command and the Isinteg command.

For more information about how to repair an Exchange Server database, click the following article number to view the article in the Microsoft Knowledge Base:
812357 (http://support.microsoft.com/kb/812357/) How to maintain your Exchange database after you repair by using the Eseutil /p tool in Exchange Server 5.5, in Exchange 2000 Server, and in Exchange Server 2003

Two reserve transaction log files that act as placeholders and that reserve hard disk space are also available in case the hard disk on which the transaction log files are stored becomes full. These reserve transaction log files are named Res1.log and Res2.log. If the hard disk where the transaction log files are located becomes full, Exchange Server will use these two reserve transaction log files to continue logging long enough to stop the database cleanly. When Exchange Server cannot create an additional transaction log file because the log disk is full, Res2.log is renamed and is used as the next log. If it is required, Res1.log will also be used.

Sometimes the capacity of both of the reserve transaction log files might be exceeded. This causes all the databases in the storage group to be stopped in a Dirty Shutdown or Inconsistent state.

Warning If you run out of disk space on the transaction log drive, the databases may not be able to shut down cleanly. If one or more of the databases are in a Dirty Shutdown or Inconsistent state and if you delete all the transaction log files in order to free disk space, no databases in the affected storage groups will be mountable again without being repaired or restored. You must not delete log files that are still required by one or more of the databases.

Back to the top

Storage groups

Exchange Server databases are organized into storage groups. A storage group is a set of databases that share a single transaction log file stream. In Exchange Server 5.5, there is a single Information Store storage group that contains up to two database files. These two database files are named Priv.edb and Pub.edb respectively. Additionally, Exchange Server 5.5 contains a single Directory Service storage group that contains a single database file that is named Dir.edb.

In Exchange 2000 Server and in Exchange Server 2003, there is no Directory Service storage group. In Exchange 2000 Server and in Exchange Server 2003, there can be up to four Information Store storage groups per server. Each of these storage groups can contain up to five databases. The names of these databases are configurable by the administrator.

If the transaction log drive becomes full, all databases in the storage group will be stopped immediately. When you start any database in a storage group, the state of all databases in the storage group is checked. Any required transaction log file replay is performed together for all databases before the first database can start. Transaction log file replay operations and events generally apply to all databases in a storage group, not to an individual database.

Important You should verify that each database file is in a Clean Shutdown or Consistent state. One or more databases in a particular storage group may be correctly detached even though another database in that same storage group is not correctly detached. Do not assume that all databases in a storage group are in a Clean Shutdown state based on the state of the first database that you examine.

Note For Exchange Server 5.5, you must examine each database that is contained in a single .edb file by using the Eseutil command. For Exchange 2000 Server and for Exchange Server 2003, each database is divided into two files. The two files are an .stm file and an .edb file. Examine the state of both the .stm file and the .edb file by using the Eseutil command.

GPA Pix 501 [ DHCP outside]

Fri, 27 Apr 2007 19:01:46 GMT

show config
: Saved
: Written by enable_15 at 14:54:37.115 UTC Fri Apr 27 2007
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password fDLBfk8ruleFLQQb encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname GPA
domain-name GPA.Local
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rsh 3389
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list 100 permit tcp any any eq 3389
access-list 100 permit icmp any any echo-reply
access-list 100 permit icmp any any
access-list GPA_splitTunnelAcl permit ip 192.168.1.0 255.255.255.0 any
access-list inside_outbound_nat0_acl permit ip 192.168.1.0 255.255.255.0 10.0.100.0 255.255.255.128
access-list outside_cryptomap_dyn_20 permit ip any 10.0.100.0 255.255.255.128
pager lines 24
icmp permit any outside
icmp permit any inside
mtu outside 1500
mtu inside 1500
ip address outside dhcp setroute retry 4
ip address inside 192.168.1.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool VPNPool 10.0.100.1-10.0.100.100
pdm location 192.168.1.10 255.255.255.255 inside
pdm location 0.0.0.0 255.255.255.255 outside
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp interface 3389 192.168.1.10 3389 netmask 255.255.255.255 0 0
access-group 100 in interface outside
timeout xlate 3:00:00
timeout conn 2:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:10:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
http server enable
http 0.0.0.0 0.0.0.0 outside
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
sysopt connection permit-pptp
sysopt noproxyarp outside
sysopt noproxyarp inside
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto dynamic-map outside_dyn_map 20 match address outside_cryptomap_dyn_20
crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map client authentication LOCAL
crypto map outside_map interface outside
isakmp enable outside
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
vpngroup GPA address-pool VPNPool
vpngroup GPA dns-server 192.168.1.10
vpngroup GPA wins-server 192.168.1.10
vpngroup GPA split-tunnel GPA_splitTunnelAcl
vpngroup GPA idle-time 1800
vpngroup GPA password ********
telnet 0.0.0.0 0.0.0.0 inside
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 outside
ssh timeout 5
console timeout 0
username Lantek password 8h83TKLnDr67RWq5 encrypted privilege 15
terminal width 80
Cryptochecksum:0d0e3eea5a37daed72eb97811316e61d

�GPA#�

Claysville PIX 501

Tue, 10 Apr 2007 15:30:22 GMT

PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password fDLBfk8ruleFLQQb encrypted
passwd fDLBfk8ruleFLQQb encrypted
hostname Claysville
domain-name ciscopix.com
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list inside_outbound_nat0_acl permit ip any 192.168.1.128 255.255.255.128

access-list 100 permit tcp any any eq 3389
access-list 100 permit icmp any any
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 65.209.105.106 255.255.255.248
ip address inside 192.168.1.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool VPN_Inside 192.168.1.150-192.168.1.200
pdm location 192.168.1.128 255.255.255.128 outside
pdm location 192.168.1.2 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp 65.209.105.106 3389 192.168.1.10 3389 netmask 255.255.255.255 0 0
access-group 100 in interface outside
route outside 0.0.0.0 0.0.0.0 65.209.105.105 1
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
http server enable
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-pptp
telnet 192.168.1.0 255.255.255.0 inside
telnet timeout 5
ssh timeout 5
console timeout 0
vpdn group PPTP-VPDN-GROUP accept dialin pptp
vpdn group PPTP-VPDN-GROUP ppp authentication pap
vpdn group PPTP-VPDN-GROUP ppp authentication chap
vpdn group PPTP-VPDN-GROUP ppp authentication mschap
vpdn group PPTP-VPDN-GROUP ppp encryption mppe auto
vpdn group PPTP-VPDN-GROUP client configuration address local VPN_Inside
vpdn group PPTP-VPDN-GROUP pptp echo 60
vpdn group PPTP-VPDN-GROUP client authentication local
vpdn username lantek password *********
vpdn enable outside
vpnclient server 192.168.1.1
vpnclient mode client-mode
vpnclient vpngroup Claysville password ********
terminal width 80
Cryptochecksum:48526126b1a4b17708e96ea1a8483b77
: end

phpMyFAQ - The five questions posted most recently:

Defragment with the Eseutil utility

How to defragment with the Eseutil utility (Eseutil.exe)