locked
Trying to clean up space in Exchange 2003 RRS feed

  • Question

  • I current have users in my First and Third Storage groups in Exchange 2003

    The first storage group has one mailstore and public folder database while the third one has two mailstores.

    Is it better to conduct offline defragmentation on the mailstores or should I move everybody away from the mail stores and put them into new storage groups?  Would it be safe to then delete the first storage group?

    Tuesday, March 26, 2013 2:57 PM

Answers

  • Hi,

    We can delete first storage group, however you must perform the following steps before do that.

    1. First move all the mailboxes in the first storage group to another storage group,

    2. Then need to move System Attendant Mailbox. For more information about how to do that, refer to the following steps. 

    Moving the Exchange System Attendant Mailbox

     

    The System Attendant mailbox on an Exchange server is used by the system for passing messages such as Server Monitor notifications. This account is created in the First Storage Group\Mailbox Store server name database when Exchange is installed. You cannot delete this database until the System Attendant mailbox has been moved to a different database on the same server.

     

    You may not need to move the System Attendant mailbox to accomplish your purpose. If you simply want to rename storage groups and databases, right-click the names in Exchange System Manager and then click rename. If you want to move the database that contains the System Attendant mailbox to another server or storage group, you must move the mailbox. If you do not move the mailbox, notifications and other messages handled by the System Attendant are not sent, although most other server functions will not be affected.

     

    After you move the System Attendant mailbox, you cannot move it back to the original database unless you physically delete and then re-create the original database.

     

    Before you move the mailbox, make a backup of the current database.

     

    To move the System Attendant mailbox:

     

    1. Change the homeMDB attribute of the Microsoft System Attendant object for the server to reflect the new database. For example, if the homeMDB value is CN=Mailbox Store (SERVER1),CN=First Storage Group,CN=InformationStore,CN=SERVER1,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mycompany,DC=com and you want to move the

    System Attendant mailbox to a database called DB2 in storage group Second, change the homeMDB value to

    CN=DB2,CN=Second,CN=InformationStore,CN=SERVER1,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mycompany,DC=com The System Attendant object for each Exchange server is located in the Configuration container of your Active Directory forest. The path to it is: CN=Microsoft System Attendant,CN=[server name],CN=Servers,CN=[administrative group name],CN=Administrative Groups,CN=[organization name],CN=Microsoft Exchange,CN=Services,CN=Configuration

     

    2. Stop and restart all Exchange services.

     

    3. Run the Mailbox Cleanup Agent against the original database. To access the Cleanup Agent, right-click the Mailboxes object for the database. After you run the Cleanup Agent, the original System Attendant mailbox should have a red X next to it, indicating that it is no longer connected to an Active Directory object.

     

    4. Right-click the disconnected System Attendant mailbox, and then permanently delete the mailbox. Warning After you complete this step, you cannot move the mailbox back to the original database. To move it back, you must delete the physical database files, and allow a fresh database to be re-created.

     

    5. From a client workstation, send a mail message to the System Attendant mailbox, requesting a delivery receipt. Address the message in the following format, including use of the square brackets: [SMTPTongue TiedERVERNAME-SA@domain.com]

     

    6. Monitor the Application Log carefully for errors relating to the System Attendant mailbox.

     

    3.Replicate any public folders in the first storage group to another server

    ------------------------------------------------------------------------------------------------------------------

    If this post is useful, please hit the green arrow on the left.

    Thanks


    Tuesday, March 26, 2013 3:08 PM
  • The "Best Practice" is to move all mailboxes into a new database and then kill off the old one, however be aware that;

    1. While mailboxes are being moved they cannot be accessed.

    2. You will generate a substantial amount of log files during the migration actions so be sure to watch your disk space and ensure backups happen to truncate the logs OR you can turn on circular logging during the migrations and then off when done.  However with circular logging on if something happens you will not have the ability to rollup logs to recover data.

    3. Once the moves are done you will need to adjust your backups as well, i.e. take the old DB out of the backup and put the new one in and of course you should do a full backup of the new store as soon as you are done

    The other option would be to do a defrag and isinteg of the databases in question however;

    1. This takes the entire database offline so that ALL users within the DB cannot access their mailboxes

    2. You need 110% of the database size in free space on a local or remote drive

    3. You should run eseutil /d and upon completion run isinteg until there are no errors reported, i.e. at the end of the process it will tell you how many errors/warnings it addressed.  If any ERRORS were reported/fixed then you need to run it again until it reports that there are zero errors and that zero errors were fixed.  

    NOTE:  if you want something automated to do this check out Lucid8's GOexchange http://www.lucid8.com/


    Troy Werelius
    www.Lucid8.com
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 --> 2007 --> 2010 with Lucid8's DigiScope

    Tuesday, March 26, 2013 4:59 PM

All replies

  • Hi,

    We can delete first storage group, however you must perform the following steps before do that.

    1. First move all the mailboxes in the first storage group to another storage group,

    2. Then need to move System Attendant Mailbox. For more information about how to do that, refer to the following steps. 

    Moving the Exchange System Attendant Mailbox

     

    The System Attendant mailbox on an Exchange server is used by the system for passing messages such as Server Monitor notifications. This account is created in the First Storage Group\Mailbox Store server name database when Exchange is installed. You cannot delete this database until the System Attendant mailbox has been moved to a different database on the same server.

     

    You may not need to move the System Attendant mailbox to accomplish your purpose. If you simply want to rename storage groups and databases, right-click the names in Exchange System Manager and then click rename. If you want to move the database that contains the System Attendant mailbox to another server or storage group, you must move the mailbox. If you do not move the mailbox, notifications and other messages handled by the System Attendant are not sent, although most other server functions will not be affected.

     

    After you move the System Attendant mailbox, you cannot move it back to the original database unless you physically delete and then re-create the original database.

     

    Before you move the mailbox, make a backup of the current database.

     

    To move the System Attendant mailbox:

     

    1. Change the homeMDB attribute of the Microsoft System Attendant object for the server to reflect the new database. For example, if the homeMDB value is CN=Mailbox Store (SERVER1),CN=First Storage Group,CN=InformationStore,CN=SERVER1,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mycompany,DC=com and you want to move the

    System Attendant mailbox to a database called DB2 in storage group Second, change the homeMDB value to

    CN=DB2,CN=Second,CN=InformationStore,CN=SERVER1,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mycompany,DC=com The System Attendant object for each Exchange server is located in the Configuration container of your Active Directory forest. The path to it is: CN=Microsoft System Attendant,CN=[server name],CN=Servers,CN=[administrative group name],CN=Administrative Groups,CN=[organization name],CN=Microsoft Exchange,CN=Services,CN=Configuration

     

    2. Stop and restart all Exchange services.

     

    3. Run the Mailbox Cleanup Agent against the original database. To access the Cleanup Agent, right-click the Mailboxes object for the database. After you run the Cleanup Agent, the original System Attendant mailbox should have a red X next to it, indicating that it is no longer connected to an Active Directory object.

     

    4. Right-click the disconnected System Attendant mailbox, and then permanently delete the mailbox. Warning After you complete this step, you cannot move the mailbox back to the original database. To move it back, you must delete the physical database files, and allow a fresh database to be re-created.

     

    5. From a client workstation, send a mail message to the System Attendant mailbox, requesting a delivery receipt. Address the message in the following format, including use of the square brackets: [SMTPTongue TiedERVERNAME-SA@domain.com]

     

    6. Monitor the Application Log carefully for errors relating to the System Attendant mailbox.

     

    3.Replicate any public folders in the first storage group to another server

    ------------------------------------------------------------------------------------------------------------------

    If this post is useful, please hit the green arrow on the left.

    Thanks


    Tuesday, March 26, 2013 3:08 PM
  • The "Best Practice" is to move all mailboxes into a new database and then kill off the old one, however be aware that;

    1. While mailboxes are being moved they cannot be accessed.

    2. You will generate a substantial amount of log files during the migration actions so be sure to watch your disk space and ensure backups happen to truncate the logs OR you can turn on circular logging during the migrations and then off when done.  However with circular logging on if something happens you will not have the ability to rollup logs to recover data.

    3. Once the moves are done you will need to adjust your backups as well, i.e. take the old DB out of the backup and put the new one in and of course you should do a full backup of the new store as soon as you are done

    The other option would be to do a defrag and isinteg of the databases in question however;

    1. This takes the entire database offline so that ALL users within the DB cannot access their mailboxes

    2. You need 110% of the database size in free space on a local or remote drive

    3. You should run eseutil /d and upon completion run isinteg until there are no errors reported, i.e. at the end of the process it will tell you how many errors/warnings it addressed.  If any ERRORS were reported/fixed then you need to run it again until it reports that there are zero errors and that zero errors were fixed.  

    NOTE:  if you want something automated to do this check out Lucid8's GOexchange http://www.lucid8.com/


    Troy Werelius
    www.Lucid8.com
    Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 --> 2007 --> 2010 with Lucid8's DigiScope

    Tuesday, March 26, 2013 4:59 PM
  • Hi Bart

    Any update on this thread?

    Cheers


    Zi Feng
    TechNet Community Support

    Wednesday, March 27, 2013 6:05 AM
    Moderator