<div>
As far the catalog files are concern they are not *super* important data.<br />
The same Catalog files can be created after the next Full text indexing - crawling.<br />
<br />
Just would take a while to rebuild the same depends on the DB size/mail volume<br />
Only during that time of rebuild the end-users wouldn't get the full-text search response.
</div>


As far the catalog files are concern they are not *super* important data.
The same Catalog files can be created after the next Full text indexing - crawling.

Just would take a while to rebuild the same depends on the DB size/mail volume
Only during that time of rebuild the end-users wouldn't get the full-text search response.

<div>
<div class="content wysiwyg-content">
Hi,<br />
I am running out of space on my Exchange 2007 DB drive and want to move it to another drive.<br />
I've read up on the process and it seems pretty straight forward to move storage path, DB and Public folders. Exchange is on VMWare and I want to reclaim the original DB drive back for use withother VMs. Am I ok to delete the old DB drive once the move is done or are there any other files that need to be moved. eg. Catalog Data?
</div>
</div>


Hi,
I am running out of space on my Exchange 2007 DB drive and want to move it to another drive.
I've read up on the process and it seems pretty straight forward to move storage path, DB and Public folders. Exchange is on VMWare and I want to reclaim the original DB drive back for use withother VMs. Am I ok to delete the old DB drive once the move is done or are there any other files that need to be moved. eg. Catalog Data?

Exchange 2007 DB move

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.