PRIV.EDB

Bonjour,

J'ai effectué un défrag sur ce fichier il y a deux jours et j'ai
gagné 2Go sur 8. Il faut penser à faire une sauvegarde du fichier
avant ainsi que du fichier priv.stm.
Il faut également savoir qu'on peut le faire que banque d'information
démontée !! Donc pas de messagerie pendant le traitement, possbilité
de faire un script et de le plannifier.

Il faut utiliser eseutil (en ligne de commande) pour défragmenter la
base, ci-joint deux liens du support microsoft :

http://support.microsoft.com/kb/192185/fr
http://support.microsoft.com/kb/182903/fr

A plus,

Jean Marc

On peut effectivement reduire la taille mais le mieux est de savoir avant de
le faire ce que l'on va gagner

cordialement
Laurent Teruin
lteruin@hotmail.com
http://lteruin.over-blog.com/


Determining database free space with Exchange 5.5

Service Pack 1 and later versions of Exchange

This article was previously published under Q195914

SUMMARY

Versions of Microsoft Exchange starting with Microsoft Exchange

Server 5.5 Service Pack 1 offer two informational features for

determining free space in Exchange database (EDB) files. Knowing

this can help you decide whether it is worthwhile to perform offline
defragmentation.

MORE INFORMATION

To discover how much free space is available in your database files, look
for an Event 1221 in the Windows

application event log. There will be separate events logged for each
database after online defragmentation

completes for that database. The event descriptions will be similar to the
following:

The database has 151 megabytes of free space after online defragmentation
has terminated.

For Exchange Server 5.5, an Event 179 from source ESE97 is logged for each
database at the beginning of

online defragmentation. An Event 180 signals completion of online
defragmentation. An Event 183 indicates

that online defragmentation did not complete, but has been suspended and
will finish later. Online

defragmentation may be suspended if the online maintenance period that is
defined for the database expires

before online defragmentation completes. In this case, online
defragmentation will resume where it left off

during the next online maintenance window.

In Microsoft Exchange 2000 Server and in Microsoft Exchange Server 2003,
event ID 700 signals the

beginning of a full pass, and event ID 701 signals the completion of a full
pass.

You may view or adjust the Information Store Maintenance schedule in the
Exchange Server Administrator

program for individual databases.

The free space that is reported by Event 1221 is a conservative estimate. If
you perform offline

defragmentation, you will recover at least the amount of space that is
reported as free. All space in an

Exchange database is owned either by the database root or by particular
tables in the database. Event 1221

estimates free space by calculating the number of empty pages owned by the
messages table, the

attachments table, and the database root. Free pages that are owned by other
tables in the database are not

taken into account.

To obtain a closer estimate, you may stop the database and generate a
detailed report on free space by typing

the following at a command prompt: ESEUTIL.EXE /MS [database.edb] >
FREESPACE.TXT

Even on a large database, this procedure will require only a few minutes of
downtime.

Note The /MS switch is available only in Exchange Server 5.5 Service Pack 1
or later versions of Exchange.

The following is an abridged example of typical output that would be saved
to Freespace.txt:

Article ID : 195914

Last Review : November 3, 2004

Revision : 4.1

Page Determining database free space with Exchange 5.5 Service Pack 1 and
later versions... e 1 sur 4

http://support.microsoft.com/default.aspx?scid=kb;en-us;195914 18/11/2004

The first section of the space report is the SLV SPACE DUMP. This reports on
free space in the streaming

database file (.stm). There are 4710 free pages in the .stm file, and each
page is 4096 bytes in length.

Therefore, there are 19,292,160 bytes of empty space in the file (4710 x
4096). If you were to defragment

this file, you would recover approximately 19 megabytes (MB) of disk space.

Note There is no streaming database for Exchange Server 5.5, and thus no SLV
SPACE DUMP section in the

space report.

The second section of the space report is the SPACE DUMP. This reports on
free space in the database file

(.edb). Each table in the database is listed together with the number of
pages that it owns and the number of

pages owned that are available (empty).

Microsoft(R) Exchange Server Database Utilities

Version 6.5

Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating FILE DUMP mode...

Database: priv1.edb

****************************** SLV SPACE DUMP ******************************

Chunk Free Res Del Com |------------ Used ------------|

===========================================================================
512 110 0 0 402 *************************

1024 505 0 0 7

1536 0 509 1 2 ********************************

2048 512 0 0 0

2560 511 0 0 1

3072 512 0 0 0

3584 512 0 0 0

4096 512 0 0 0

4608 512 0 0 0

5120 512 0 0 0

5632 512 0 0 0

===========================================================================
TOTALS:

Free: 4710

Reserved: 509

Deleted: 1

Committed: 412

Unknown: 0

-------------

5632

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

******************************** SPACE DUMP
***********************************

Name Type ObjidFDP PgnoFDP PriExt Owned Available

==============================================================================
priv1.edb Db 1 1 256-m 24064 19726

<SLV Avail Map> SLV 6 33 32-m 32 29

<SLV Owner Map> SLV 7 65 32-m 64 10

1-103C1 Tbl 793 2073 8-s 8 3

MsgFolderIndex7 Idx 795 2074 1-s 1 0

MsgFolderIndexPtagDel Idx 798 2077 1-s 1 0

MsgFolderIndexURLComp Idx 797 2076 1-s 1 0

RuleMsgFolderIndex Idx 796 2075 1-s 1 0

. . . .

1-23 Tbl 61 236 2-m 226 15

<Long Values> LV 1439 619 1-m 137 9

. . . .

Msg Tbl 19 112 2-m 866 53

<Long Values> LV 106 359 1-m 16 0

-------------------------------------------------------------------------------

20687

Operation completed successfully in 6.89 seconds.

Page Determining database free space with Exchange 5.5 Service Pack 1 and
later versions... e 2 sur 4

http://support.microsoft.com/default.aspx?scid=kb;en-us;195914 18/11/2004

The number at the lower right of the output (20687) is the total of all free
pages in the database. If you

multiply this number by 4096, you will see that defragmenting this database
will recover 84,733,952 bytes of

space.

Background information

The Exchange database files Dir.edb, Priv.edb, and Pub.edb grow as needed to
handle new data. As old data is

deleted, the "holes" in the file are re-used for new data before growing the
file size again, but the files never

shrink in gross size until an offline defragmentation is performed.

In regular operation, the size of the .edb files will stabilize after a few
weeks or months. Significant changes in

usage or configuration may change the equilibrium size of the files.
Examples of significant changes in usage

or configuration include adding or deleting large numbers of mailboxes or
adding an Internet gateway. In such

cases, offline defragmentation may be helpful to not only reduce file size,
but to improve performance and to

increase data allocation efficiency, especially with versions of Exchange
that are earlier than Exchange Server

5.5 Service Pack 1.

Exchange Server 5.5 Service Pack 1 added significant new capabilities to
online defragmentation. While online

defragmentation cannot shrink the gross size of the database files, it is
now as efficient as offline

defragmentation in rearranging file layout for maximum performance.

Offline defragmentation is not a periodically-required Exchange maintenance
practice and should be performed

only when the events in the application event log tell you that there would
be benefit from it, or when you

have performed operations that warrant it. The most commonly performed
operation that warrants an offline

defragmentation is moving a large group of mailboxes off your server.

As a very broad rule, you will probably not obtain long term file size
shrinkage unless the amount of free space

in your database is ten times the average daily traffic on your server.
(Determine daily traffic by adding up the

sizes of all the EDBnnnnn.log transaction log files generated on a typical
day with circular logging turned off.)

Offline defragmentation is performed with the Eseutil.exe utility's /D
switch, and requires stopping Exchange

services. Plan for a minimum of 30 minutes of downtime per gigabyte (GB) of
data to be defragmented.

Offline defragmentation works by creating a new database and copying pages
in use from the old database to

a temporary database. Offline defragmentation also discards and rebuilds all
indexes.

After all pages in use have been copied to the temporary database, the old
database is deleted and the new

database file is renamed. We recommend that before defragmentation begins,
you have free disk space equal

to the size of the database being defragmented. However, you actually must
only have free disk space

equivalent to the expected defragmented size of the database.

If you run out of space or if offline defragmentation fails for some other
reason, no harm is done to your

original database. But you should find and manually delete the partial new
database to free up disk space. The

partial new database is typically named Tempdfrg.edb.

Offline defragmentation can be performed in place or out of place on another
server if you are short on disk

space. Copy the defragmented .edb file back in place after defragmentation
completes. This will, of course, be

a much longer process than defragmenting the database "in place."

Make sure that you perform a full online backup after defragmentation.
Defragmentation makes dramatic

changes to the database without recording those changes in the transaction
logs. Therefore, transaction logs

cannot be replayed across the point where an offline defragmentation has
occurred. If it were to become

necessary to restore a pre-defragmentation backup, you would not be able to
recover data past the point of

defragmentation. After defragmentation, you should consider all previous
backups of the database to be

invalid.

APPLIES TO

. Microsoft Exchange Server 2003 Standard Edition

. Microsoft Exchange Server 2003 Enterprise Edition

. Microsoft Exchange 2000 Server Standard Edition

. Microsoft Exchange Server 5.5 Standard Edition

Keywords: kbhowto kbinfo KB195914

Page Determining database free space with Exchange 5.5 Service Pack 1 and
later versions... e 3 sur 4

http://support.microsoft.com/default.aspx?scid=kb;en-us;195914 18/11/2004

©2004 Microsoft Corporation. All rights reserved.

Page Determining database free space with Exchange 5.5 Service Pack 1 and
later versions... e 4 sur 4

http://support.microsoft.com/default.aspx?scid=kb;en-us;195914 18/11/2004

Base de connaissances Microsoft - 328804

How to defragment Exchange databases

Liste des produits concernés par cet article.

This article was previously published under Q328804

INTRODUCTION

Disk defragmentation is the process of rearranging the data that is stored
on a computer's hard disks to make the files

more contiguous and to increase data access and retrieval speed. When you
defragment your hard disks, you can

increase disk performance and help the servers in your organization run more
smoothly and efficiently, including the

servers that are running Exchange.

MORE INFORMATION

The fragmentation of Exchange data occurs on a different level than regular
disk fragmentation. The fragmentation of

Exchange data occurs within the Exchange database itself. If you run regular
disk defragmentation on an Exchange

computer, you should do it during off-hours and preferably with Exchange
databases stopped. The process of disk

defragmentation is a very I/O intensive process. Therefore, the Exchange
database engine could have difficulty accessing

the hard drives in a timely manner.

By default, Exchange databases run a defragmentation process daily. This
process arranges the mailbox store data and

the public folder store data more efficiently to consolidate unused storage
space. You can also defragment Exchange

databases manually offline.

Online defragmentation

Exchange database online defragmentation occurs automatically as part of the
database maintenance process. Online

defragmentation detects and removes database objects that are no longer
being used. This makes additional database

space available. The online defragmentation process provides more database
space without changing the file size of the

database. By default, Exchange is configured to run online defragmentation
daily between 01:00 and 05:00.

Note To increase the efficiency of maintenance and backup processes, you may
want to schedule your maintenance

processes and backup operations to run at different times.

There are two ways to schedule database defragmentation:

?? To schedule database defragmentation for an individual database, use the
Maintenance interval option on the

Database tab of a mailbox store or public folder store object to configure
the maintenance interval.

?? To schedule database defragmentation for a collection of mailbox stores
and public folder stores, use the

Maintenance interval option on the Database (Policy) tab of a mailbox store
or a public folder store policy to

configure the maintenance interval.

Offline defragmentation

Although online defragmentation provides some additional database space, you
must defragment your Exchange

database offline to reduce the physical size of your Exchange database. You
can use the Eseutil utility (Eseutil.exe) to

perform offline defragmentation while your mailbox stores and public folder
stores are offline.

For example, you might perform offline defragmentation if you recently moved
many users from a server that is running

Exchange. In that case, offline defragmentation reduces the size of your
Exchange databases by rearranging the data on

the server's Exchange databases and discarding any unused database pages.

Note Eseutil is an Exchange utility that you can use to defragment, repair,
and examine the integrity of Exchange

databases. You can find Eseutil on the Exchange CD. For information about
how to use Eseutil, see Eseutil.rtf in the

SupportUtils folder of your Exchange CD.

By default, Eseutil /d defragments a database by creating a new database,
copying the old database records to the

new one, and discarding any unused database pages. This results in a newly
organized compact database file.

You may want to use the following option when you use Eseutil to defragment
your Exchange databases:

?? You can run Eseutil with the /d /p option at the command line to
configure Eseutil to create the new

defragmented database in a separate location, such as a location on a
different hard disk. If you turn off instating,

328804 - How to defragment Exchange databases Page 1 sur 2

http://support.microsoft.com/default.aspx?scid=kb;en-us;328804&Product=e...
10/09/2004

the offline defragmentation process preserves the original database
uncompacted, and the temporary file that is

created is the defragmented version of the database. For example, you could
turn off instating by using the /d /p

option. Unlike the standard offline defragmentation process (Eseutil /d), if
you run Eseutil with the /d /p option,

the original database is not overwritten with the new defragmented database
when the offline defragmentation

process is complete.

The /d /p option can also significantly reduce the time it takes to
defragment large databases because you do not copy

the defragmented database from the temporary location and overwrite the
original fragmented file. However, if you want

to mount the defragmented database after you use this option, you must
manually move the defragmented .edb

and .stm files into the database path and rename them to the correct
database file names. For example, if Tempdfg.edb

and Tempdfg.stm are the defragmented files that you created by running the
/d /p option, you must rename them to

Priv1.edb and Priv1.stm respectively if Priv1.edb and Priv1.stm are the
databases that you originally ran Eseutil against.

The following example command would defragment a database that is named
Mailbox Store.edb and its accompanying

streaming file, turn off instating, and create the defragmented databases on
the D drive. (Note that there is no space

after /t.)

eseutil /d /p "c:program filesexchsrvrmdbdatamailbox store.edb"
/t"d:tempdfg.edb"

Note If you do not use the /t option, the Tempdfgxxxx.edb file and the
Tempdfgxxxx.stm file are created in the location

that you run Eseutil from. (In the previous file names, #### is a random
number.)

Because offline defragmentation rearranges the data in your Exchange
databases, use the Backup utility immediately

after defragmentation to create standard backups of the databases that
secure the new data arrangement. Earlier

incremental or differential backups are no longer useful because they refer
to database pages that were rearranged by

the defragmentation process. For more information about backup types, visit
the following Microsoft Web site to

download the Exchange Resource Kit:

http://www.microsoft.com/exchange/techinfo/reskit/2000.asp

REFERENCES

For additional information about how to defragment your Exchange database
with Eseutil, click the following article

number to view the article in the Microsoft Knowledge Base:

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

For additional information about how to use Eseutil /d to defragment a
database and the streaming file associated with

the database, click the following article number to view the article in the
Microsoft Knowledge Base:

254132 Eseutil /d defragments the database and the streaming file

The information in this article applies to:

?? Microsoft Exchange Server 2003 Enterprise Edition

?? Microsoft Exchange Server 2003 Standard Edition

?? Microsoft Exchange 2000 Server

Last Reviewed: 8/19/2004 (4.0)

Keywords: kbinfo KB328804

© 2004 Microsoft Corporation. Tous droits réservés. Conditions d'utilisation
Confidentialité Accessibilité

Contactez-nous

328804 - How to defragment Exchange databases Page 2 sur 2

http://support.microsoft.com/default.aspx?scid=kb;en-us;328804&Product=e...
10/09/2004

"Henri Dubayle" <hdubayle@libertysurf.fr> a écrit dans le message de news:
44226fb6$0$167$a3f2974a@nnrp1.numericable.fr...

Bonjour.
Comment réduire la taille du fichier de la banque d'informations privée
(PRIV.EDB)? Peut-on compresser ce fichier? Merci d'avance pour votre aide.
Cordialement.