<div>
Whether you have created new DB and then replicated from old DB?<br />
<br />
The old DB might have whitespaces, that include in the DB size.<br />
<br />
to check whether the replication completed or not, i would suggest follow the below steps.<br />
<br />
You need to export all the public folders (source&amp; destination) with size an number of items into excel sheet and verify whether source and destination folders have same size and also number of public folder items.
</div>


Whether you have created new DB and then replicated from old DB?

The old DB might have whitespaces, that include in the DB size.

to check whether the replication completed or not, i would suggest follow the below steps.

You need to export all the public folders (source& destination) with size an number of items into excel sheet and verify whether source and destination folders have same size and also number of public folder items.

<div>
<div class="content wysiwyg-content">
I have replicated the ENTIRE PF to another server but the file size is different than the original PF .edb. &nbsp;The original file is larger in size. &nbsp;Is there a rational explanation for this or I did something wrong?
</div>
</div>


I have replicated the ENTIRE PF to another server but the file size is different than the original PF .edb.  The original file is larger in size.  Is there a rational explanation for this or I did something wrong?

PF replication, file size is difference

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.