none
Whitespace cleanup RRS feed

  • Question

  • We currently have 2 exchange servers that are in a DAG.  One exchange server has a 2TB drive for the databases and the other has 2.6TB drive for the databases.  The server with the smaller drive has about 100 GB of free space right now but when we check the AvailableNewMailboxSpace it is showing that we can reclaim about 80 GB of space.  We would like to reclaim this space by creating a new DBs and moving mailboxes to the new databases then remove the old ones.  The problem is we don't have enough space on the one server for this to happen.  The question I have is can we create a new "non-replicated" database on the server with the larger drive and move the mailboxes to that database, then after confirming everything is working remove the old DB and replicate the new database to the server with the smaller drive?
    Wednesday, September 12, 2018 10:04 PM

All replies

  • You can do that, however first;

    1. How much space are your LOGS associated with the DB taking up and how many of them exists?

    2. How large are the physical EDB files?


    Search, Recover, Export Mailboxes, Contacts, Calendars, Tasks from ALL versions of Exchange Offline EDB's, On-Premises Exchange Databases & Office 365. Export, Migrate/Recover into On-Premises Exchange Server, Office 365 with Lucid8's DigiScope

    Wednesday, September 12, 2018 10:12 PM
  • 1. The Logs for the DB with the largest whitespace takes up 1.2 GB.

    There are 1230 log files for that database.

    2. The edb file for that database is 263 GB.

    Wednesday, September 12, 2018 10:26 PM
    1. OK that's a reasonable # of logs & size
    2. What else is on that drive taking up the other 1.7 TB?

    Search, Recover, Export Mailboxes, Contacts, Calendars, Tasks from ALL versions of Exchange Offline EDB's, On-Premises Exchange Databases & Office 365. Export, Migrate/Recover into On-Premises Exchange Server, Office 365 with Lucid8's DigiScope

    Wednesday, September 12, 2018 10:31 PM
  • Hi,

    AvailableNewMailboxSpace tells how much space is available in the root tree of the database. It is not representative of the white space within the database. You will need to dismount the database and use ESEUTIL /MS to check the available whitespace in a database.

    To reclaim the whitespace in database, you can do the following:
    1. Create a new database and associated database copies.
    2. Move all mailboxes to the new database.
    3. Delete the original database and its associated database copies.

    Refer to the blog about to view details about database maintenance.
    Database Maintenance in Exchange

    Please feel free to post your questions, and I am glad to provide further assistance.

    Regards,

    Dawn Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, September 13, 2018 9:57 AM
    Moderator
  • The other DBs are taking up the rest of the space.  We are thinking that if we can cleanup the DB with the largest available space it would free enough space up until we start migrated to O365 which will start in a couple of months.

    Also the logs are on a separate drive from the databases.

    Thursday, September 13, 2018 2:53 PM
  • Dawn,

    Do we have to create the database copies of the new database before we move the mailboxes?  If I am thinking about this correctly, if we create the database copies first when we move the mailboxes it would replicate the changes to the other server, which would then cause the drive to fill up.

    Thursday, September 13, 2018 2:59 PM
  • You are correct and so yes you could create a non-replicated DB, move the mailboxes, take the OLD DB offline to ensure everything works well and then either dial-tone the replicated DB's and move mailboxes back OR delete the original pair and create a replication to dag member of new DB. 

    NOTE: If you dial tone the original and move mailboxes back into the new empty DB anything you have interfacing with those DB's like backup would remain intact, otherwise you would need to modify to remove old DB's and add in new


    Search, Recover, Export Mailboxes, Contacts, Calendars, Tasks from ALL versions of Exchange Offline EDB's, On-Premises Exchange Databases & Office 365. Export, Migrate/Recover into On-Premises Exchange Server, Office 365 with Lucid8's DigiScope

    Thursday, September 13, 2018 3:19 PM
  • Better you go for offline defragmentation over the weekend to claim whitespace. The only challenge is you need to dismount your DB to carry this out.

    Please mark as an answer if this answers your question .

    PREM RANA

    MCSE Exchange 2013, MCSA 2012 Server MCTS Exchange 2007,

    2010, MCITP Exchange 2007, 2010 MCSE 2003 Server,

    MCSA Exchange 2003 ITIL V3 Foundation

    https://ranaprem.wordpress.com/

    This posting is provided AS IS with no warranties and confers no rights.

    Saturday, September 15, 2018 11:52 AM
  • Actually the defrag will require 110% of the EDB size to complete so approximately 300 GB is needed.  Also he would need to break the DB pairing within the DAG and then see from the defragmented DB to the paired side later

    Search, Recover, Export Mailboxes, Contacts, Calendars, Tasks from ALL versions of Exchange Offline EDB's, On-Premises Exchange Databases & Office 365. Export, Migrate/Recover into On-Premises Exchange Server, Office 365 with Lucid8's DigiScope

    Saturday, September 15, 2018 1:21 PM
  • Hi,

    How is everything going? If there is any update or anything unclear, please don't hesitate to post it here. If you have solved the problem, you can mark the helpful reply as answer.

    Thanks for your understanding.

    Regards,

    Dawn Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, September 20, 2018 10:31 AM
    Moderator