Ok, hopefully this will be the last Exchange question for a while.

What is the best practice for moving a 300GB Exchange DB that I KNOW has corrupted items.

Unmount and then Move-DatabasePath, or should I use an alternative method? (And can you add a BadItemLimit to a Move-DatabasePath?)

I just want this to go flawlessly and have options in case one option fails.

Thank You,

SV

Hi

You could create another server, move the mailboxes to the new DB?

• Proposed as answer by Anil K Singh 7 hours 2 minutes ago

This DB is going to be unmounted and kept for compliance purposes.

The server is not a problem and has working DBs.  It's just this one overlarge DB I inherited when put in charge of this that I need to move to make space.

Hi

You could create another server, move the mailboxes to the new DB?

• Proposed as answer by Anil K Singh Saturday, June 14, 2014 3:50 AM

1. Then you can just do a DB and Log Path Move http://technet.microsoft.com/en-us/library/bb124742%28v=exchg.150%29.aspx and unless there are DISK/VOLUME issues it will work just as before.
2. If you want to be able to access the offline copy of the EDB without having to keep it on the live server check out Lucid8's DigiScope

The best method is only here to create new DB and move all your mailbox from old DB. This will not only help for corrupted items but it will reduce the target DB size will remove white spaces.

Move-DatabasePath will dismount the database for you, move the edb file but its simple file copy operation, it doesn't look for items it has inside, and mount the database back if move operation is successful.

Being that said, it doesn't have any baditemlimit option as it is simple file copy operation (However it doesn't work if you have multiple database copies)

Hi,

As what Amit mentioned above, there is no BadItemLimit parameter with the Move-DatabasePath cmdlet. And it will take some time to move these files, the database will be dismounted during this time. Therefore, please schedule a non-business time to do this.

If you dont want to affect the mail flow, you can try another way. Create a new database on other driver and move the mailboxes to the new database.

Best regards,
Belinda