<div>
<div class="content wysiwyg-content">
Hello everyone,<br />
<br />
We have one virtualized (XenServer flavor) Microsoft Exchange 2010 server on a NetApp SAN. In the database folder (which is a mount point to a LUN on our NetApp shelf), the catalogdata folder is growing steadily and not decreasing in size. If I'm not mistaken, this is by design.<br />
<br />
That said, it's starting to concern me, and I've read other answers on this site that suggest that specifically in Exchange 2007 (I've not seen an answer for 2010) you can &quot;reset&quot; the catalogdata (or search index) folder and all of its contents.<br />
<br />
I have a few questions regarding that:<br />
1. What are all of my options, apart from doing a &quot;reset&quot; (if that is an option in 2010) on the catalogdata folder?<br />
<br />
2. What are the commands to perform a reset, and on a 114 GB database about how long would it take? So far the CatalogData is 6 GB and growing. Also, I assume this would be best to run after hours.<br />
<br />
3. If I do a reset, what happens? Does it immediately come back at 6 GB of size, or will it build back up to that?<br />
<br />
4. Should I schedule a &quot;reset&quot; if this is normal Exchange behavior so it constantly resets the search data, or will it at some point stop growing?<br />
<br />
Thanks!
</div>
</div>


Hello everyone,

We have one virtualized (XenServer flavor) Microsoft Exchange 2010 server on a NetApp SAN. In the database folder (which is a mount point to a LUN on our NetApp shelf), the catalogdata folder is growing steadily and not decreasing in size. If I'm not mistaken, this is by design.

That said, it's starting to concern me, and I've read other answers on this site that suggest that specifically in Exchange 2007 (I've not seen an answer for 2010) you can "reset" the catalogdata (or search index) folder and all of its contents.

I have a few questions regarding that:
1. What are all of my options, apart from doing a "reset" (if that is an option in 2010) on the catalogdata folder?

2. What are the commands to perform a reset, and on a 114 GB database about how long would it take? So far the CatalogData is 6 GB and growing. Also, I assume this would be best to run after hours.

3. If I do a reset, what happens? Does it immediately come back at 6 GB of size, or will it build back up to that?

4. Should I schedule a "reset" if this is normal Exchange behavior so it constantly resets the search data, or will it at some point stop growing?

Thanks!

Exchange 2010 CatalogData

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.

Exchange

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.

Email Servers

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.