Hello,
I faced really interesting issue with standalone Exchange 2013 server. Somebody moved 50 000 items from one public folder to another and whole public folder DB stoped responding for more then 4 hours. The size of these items was 3 GB but the move generated more then 15 GB of transaction log. I have tried to added more resources to Exchange server but with no success. DB is stored in enterprise SAN with SSD tier so there shouldn't be a problem (storage is able to do more then 10 000 IOPs). I have tried to restart MS Information Store and restart whole server but it didn't help.
Does somebody have idea where could be a problem?
Is there any way how to stop this background action? The initial move finished after a few minutes but background operation took more then 4 hours.
Thank you for any suggestion,
Petr
I faced really interesting issue with standalone Exchange 2013 server. Somebody moved 50 000 items from one public folder to another and whole public folder DB stoped responding for more then 4 hours. The size of these items was 3 GB but the move generated more then 15 GB of transaction log. I have tried to added more resources to Exchange server but with no success. DB is stored in enterprise SAN with SSD tier so there shouldn't be a problem (storage is able to do more then 10 000 IOPs). I have tried to restart MS Information Store and restart whole server but it didn't help.
Does somebody have idea where could be a problem?
Is there any way how to stop this background action? The initial move finished after a few minutes but background operation took more then 4 hours.
Thank you for any suggestion,
Petr