Jerry Seinfield
asked on
Unable to see reclaimed disk space on a database that was recently updated
Hello Experts,
I have a customer who recently performed bulk mailbox move from a source database to a target DB. The total amount of mailboxes and the expected size to be recovered was 30 GB, and unfortunately the source database still shows the same space
I ran the following PowerShell to check available free disk space on the DBs, and I do not see a difference
Get-MailboxDatabase -Status | Sort-Object AvailableNewMailboxSpace -Descending | Format-Table Name, DatabaseSize, AvailableNewMailboxSpace
The mailboxes were migrated this Monday, and as of today, I am unable to reclaim disk space on the source database
Any ideas?
Our infrastructure
Site 1
3 MBX in DAG 1 [Exchange 2013 SP1] servers
2 CAS Servers behind a HLB F5
Site 2
same as above
The company has 2 Edge servers [Exchange 2010] and 2 DLP servers for each location.
Your feedback is highly appreciated
I have a customer who recently performed bulk mailbox move from a source database to a target DB. The total amount of mailboxes and the expected size to be recovered was 30 GB, and unfortunately the source database still shows the same space
I ran the following PowerShell to check available free disk space on the DBs, and I do not see a difference
Get-MailboxDatabase -Status | Sort-Object AvailableNewMailboxSpace -Descending | Format-Table Name, DatabaseSize, AvailableNewMailboxSpace
The mailboxes were migrated this Monday, and as of today, I am unable to reclaim disk space on the source database
Any ideas?
Our infrastructure
Site 1
3 MBX in DAG 1 [Exchange 2013 SP1] servers
2 CAS Servers behind a HLB F5
Site 2
same as above
The company has 2 Edge servers [Exchange 2010] and 2 DLP servers for each location.
Your feedback is highly appreciated
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Amit,
Is there a Exchange 2013 SP1 CU update that fix the issue of reclaiming whitespace on a Exchange 2013 database that is part of a DAG?
Is there a Exchange 2013 SP1 CU update that fix the issue of reclaiming whitespace on a Exchange 2013 database that is part of a DAG?
I dont think so .
No hotfix required to reclaim disk space. Recreating new DB is the best way.
ASKER
Is there another option to reclaim disk space on a Exchange 2013 database?