asked on

After deleted Ex2013 DB folders are left behind, cannot delete them

Hi Everyone

Environment : Server 2012 / Ex2013 fully updated

I've noticed that after deleting an additional Exchange DB that was used for testing purposes, remnants of the Exchange DB remain behind, which are:

indexmeta
journal
ms

{see attached}

How can i delete these?
If i try it says that they are in use, even though the DB has been successfully deleted.

Regards
1.PNG

Arjun Vyavahare

Hi,

Try performing below command in exchange powershell:

Remove-MailboxDatabase -Identity "MyDatabase"

otherwise Microsoft has release CU1 for exchange 2013:
http://www.microsoft.com/en-in/download/details.aspx?id=38176

Before applying CU1 on exchange 2013 server, suggest you to take full backup and then apply CU1.

I hope this will help you.

Regards,
Arjun

aNaLyz3R

ASKER

After running :
Remove-MailboxDatabase -Identity "DBName" it comes up saying the the DB cannot be found.
The DB has already been deleted, it's just these folders that remain.
I'll follow the process of loading CU1 and see if that helps....

Krishna Patil

Rather than CU1, go for SP1. Microsfot just released SP1 of Exchange 2013

aNaLyz3R

ASKER

Awesome will complete the install over the weekend.
Are there any considerations when installing sp1?

ASKER CERTIFIED SOLUTION

Krishna Patil

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Arjun Vyavahare

Sorry Friend,

I was not aware about the SP1 release for Exchange 2013, but yes instead of implementing CU1, you can implement SP1 for Exchange 2013.

Regards,
Arjun

aNaLyz3R

ASKER

Thanks guys, will will report back on Monday morning to confirm if everything is alright.

Simon Butler (Sembee)

Have you restarted the Exchange Information Store? That is probably holding on to the files.
Changes to the databases now require an information store restart to take full effect.

Furthermore, be aware that there is a bug in Exchange 2013 over third party transport agents, such as those use by products like GFI Mail Essentials and Exclaimer. If you are using products like that you may want to move to CU3 instead, until the bug is resolved.

Simon.

aNaLyz3R

ASKER

Hi guys

After loading SP1, the problem has gone away!