This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 67%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHN%3C/text%3E%3C/svg%3E)
Hello dear all,
A few days ago I partitioned the hard disk of my Exchange 2013 mail server in order to move the databases to the new partition.
Only while moving the databases I mistakenly indicated the same path to two databases, suddenly two databases ended up in the same directory.
One of the databases fails to build the catalog directory for indexes. I would like to move this database again to the right directory without causing any damage and I would like to know if there is a procedure for that.
I need your help.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(25.6, 67%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Is there any progress here about this issue, below links provided detailed steps you may need to use, you could take a reference:
Move Exchange database to another drive
Move Exchange DAG database to another drive
Repairing a Failed Content Index in Exchange Server 2016
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Sure just move one of the databases again. It wont affect the other one in that same path.
However, you may need to rebuild the search index again of the one left behind, you can do that by removing those catalog files and restarting the search service if you find there is an issue
But I wouldnt do that unless there is an issue.
Hello,
Thank you so much. I do it and I come back to you to tell you what it is.
Hello,
Thank you so much. I do it and I come back to you to tell you what it is.
Thanks a lot for your help. I managed to move the database and recreate the index.