Dedicated Archive mailbox databases generate excessive whitespace

Our company has several mailbox databases that are dedicated to arhive mailboxes.  I just joined the company a month ago and found one database that was about 500 GB with about 300 GB of whitespace!  So, I created a new DB and moved all the archive
mailboxes, and removed the original DB.  at the time there was minimal whitespace.  Today, the DB is in much the same condition.  what makes this so odd is that there are less that 30 mailboxes on database!  Further, it seems
as though these DBs are also generating way too many transaction logs and causing management to become concerned about drive space and DBs dismounting.   Bottom line:  how can I determine what is causing the excess whitespace to be generated? 

Hi,
I recommend you refer to the following article :
Exchange 2010 whitespace reclamation
In addition, as Ed mentioned, you can monitor the available new mailbox space with the following command:
get-mailboxdatabase  -status | ft Name, AvailableNewMailboxSpace
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Similar Messages

  • Specifying separate UNC path for Exchange Archive Mailbox Database

    Hi All,
    In Exchange Server 2013 SP1, is it possible to specify UNC path to a separate hardware appliance ?
    In this case I'd like to create the Archive mailbox database on the CIFS share hosted by EMC Data Domain to perform the hardware based data deduplication & compression.
    Does this path must also be accessible on the DAG passive node in DR data center ?
    /* Server Support Specialist */

    Hi ,
    most Scenarios are not supported while there is still some Scenario where you can use shares.
    "If access to a disk resource requires that a share be mapped, or   if the disk resource appears
    as a remote server by means of a Universal Naming   Convention (UNC) path
    (for example,   \\servername\sharename)   on the network, the disk storage system is not supported
    as a location for   Exchange Server databases. "
    This is also true for the Arcive DB.
    Please note that UNC directly with Exchange 2013 is possible with limited support only, and no
    version of Exchange allows you to store databases on an UNC path (except the one when you map
    SMB 3.0 shares to a VM) : 
    http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx#Best
    (Please also note the recommendation not to use deduplication by the storage.)
    Don't try to do that, because even if you configure that you will run into a non-supported situation.
    I strongly suggest you to avoid that.
    In addition, there is a webcast from Scott Schnoll about virtualization and file Shares that makes it a Little more clear. 
    https://channel9.msdn.com/Events/TechDays/Techdays-2014-the-Netherlands/Exchange-Server-2013-Virtualization-Best-Practices
    While the session is about virtualization, on 13:00 they start a discussion about storage.
    There is the reasons discussed why not to use UNC for your databases. (Don't worry, they start discussion with NFS)
    The presentation shown on 21:43 is what you need to think about when planning to use UNC resources.
    Storing an Exchnage DB on UNC is not supported.
    Regards,
    Martin
    Hi martin,
    So how are we going to Deduplicate the data ? Any suggestion perhaps ?
    My understanding is that Exchange Server 2010 onwards doesn't have data deduplication.
    How about mapping the UNC path as mapped network drive ? 
    /* Server Support Specialist */

  • Mailbox Database Size/White Space Reduction in a DAG

    I have several large databases in which I'm moving mailboxes off of in an attempt to prevent my LUNs from running out of disk space. As well, I have several mailboxes of users who have left the company. My questions are as follows:
    1. When I run remove-mailbox -id "some mailbox" -permanent $true, the mailbox is deleted from Exchange relatively instantly. Will Exchange recoup the white space that is left behind after the mailbox has been deleted so that the
    database shrinks in size? Or will it just start writing over the white space rather than growing the size of the database?
    2. Perataining to mailboxes that have been moved, if "Keep Deleted Mailboxes for" is set to 4 days on the database that holds mailboxes that I'm moving off, will the database hold onto the mailbox (even though it has successfully been moved to
    another database) for the duration of the "Keep Deleted Mailboxes for" setting? Or will the mailbox be hard deleted after the move completes successfully?
    3. As part of Online Maintenance, will Exchange defrag a databse and decrease the white space, thereby shrinking the database size or will I have to take it offline to do that?
    4. What are the procedures to perform an Offline Defrag of an Exchange Databse? How risky is this?

    Hello,
    To answer your questions:
    1.   When and online database defrag completes a pass on the database it will reclaim this as whitespace in the database. It will not however reclaim space on the disk by shrinking the .edb file. An offline defrag is required for that.
    2.   Moved mailbox will not be hard deleted until the 4 day retention period has past, unless you manually purge them using Remove-StoreMailbox.
    3.   Related to the answer for number 1. Exchange will fill whitespace as mailboxes grow, but it will not reclaim disk space.
    4.   In a DAG you will you need to dismount the mailbox database and run eseutil /d against the active database copy. This is a relatively low risk procedure, but requires databases to be offline thus interrupting mailbox access. It can also
    take quite along time depending on the database size. The rate of defrag estimated by MS is 9 GB/hr. Here is a reference:
    http://support.microsoft.com/kb/192185/en-us
    For these types of situations my preference (If disk space allows) is to move all mailboxes to a fresh database then delete the database with excessive white space

  • Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'

    I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
    two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
    Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
    Data migrated:                        
    Migration rate:                        
    Error:                        
    MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎ Diagnostic
    context:    ......    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam:
    0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server
    FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 45169   StoreEc: 0x824        
    Lid: 50544   ClientVersion: 15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 44273      Lid: 49064   dwParam: 0x1    Lid: 37288  
    StoreEc: 0x6AB         Lid: 49064   dwParam: 0x2    Lid: 59431   EMSMDB.EcDoConnectEx called [length=203]    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]   
    Lid: 62184      Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3460    Lid: 12696   dwParam: 0x0 Msg: EEInfo:
    Generation Time: 0414-04-07T16:32:03.2100000Z    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753    Lid: 9624   
    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856   
    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode  string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode  string: <Server FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo:
    prm[2]: Long val: 2767313664    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 59505   StoreEc: 0x824         Lid: 50544   ClientVersion:
    15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 36081      Lid: 51152      Lid: 52465   StoreEc: 0x80040115   
    Lid: 60065      Lid: 33777   StoreEc: 0x80040115    Lid: 59805      Lid: 52487   StoreEc: 0x80040115    Lid: 19778      Lid: 27970  
    StoreEc: 0x80040115    Lid: 17730      Lid: 25922   StoreEc: 0x80040115
    All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
    The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
    The Source Server is Running Exchange 2007.
    I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
    I would appreciate any help you can give me!
    Thanks,
    Jon

    Any update if you have resolved the issue.
    Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required

  • Error: The specified mailbox database [Mailbox Database Name] does not exist, when you try to export mailbox in Exchange 2007

    [Symptom]
    ======================
    In Exchange 2007, when you want to export mailbox to a .pst file, you should run the
    Export-Mailbox cmdlet from a 32-bit computer that has the following installed:
    The 32-bit version of the Exchange management tools
    Microsoft Office Outlook 2003 SP2 or later versions
    If not, you may encounter the following error message:
    You check that you have these required installed, but you get the error below when you run Export-Mailbox in EMS.
    “The specified mailbox database [Mailbox Database Name] does not exist.”
    [Cause Analysis]
    =======================================
    This is because that the account you use to run Export-Mailbox cmdlet don’t have the Exchange Server Administrator role assigned.
    You can check if this account has been delegated the Exchange Server Administrator role through the following path.
    EMC -> Organization Configuration-> Check permissions in the result pane.
    To delegate this Exchange Server Administrator role, right click on the
    Organization Configuration node and choose Add Exchange Administrator,
    you will see the Add Exchange Administrator window.
    [More Information]
    ==============================
    Export-Mailbox
    http://technet.microsoft.com/en-gb/library/aa998579(v=exchg.80).aspx
    How to Export and Import mailboxes to PST files in Exchange 2007 SP1
    http://blogs.technet.com/b/exchange/archive/2007/04/13/3401913.aspx
    Exchange 2007 cannot export pst files via its powershell
    http://social.technet.microsoft.com/Forums/forefront/en-US/b3bc0dce-35f3-4a69-9a33-4f2a855b9f94/exchange-2007-cannot-export-pst-files-via-its-powershell?forum=exchangesvrgenerallegacy
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hi,
    Based on my test, if you make the user the owner of the database (rather than a user with the db_owner role), when you create a query, it creates it under the dbo schema rather than DOMAIN\username.
    Steps to do so (in Management Studio):
    Right click database, select Properties 
    Click File 
    Change Owner in the textbox 
    OK to confirm 
    Downside - other users under db_owner role will still have their username appended. So schemas have to be created for these users.
    Jaynet Zhang
    TechNet Community Support

  • Set the default size for all archive mailboxes including the ones it will be created in the future

    Hi there.
    We are in the phase where we Will enable Online Archive for all the users.
    We see that the default Archiving Quota is set up for 50 GB. We have found this powershell command on MsTechnet forum
    Get-Mailbox -resultsize unlimited | where {$_.ArchiveDatabase -ne $null} | set-mailbox -ArchiveQuota 7GB -ArchiveWarningQuota 6GB
    which I guess it will set up the ArchiveQuota to 7GB to all the users, true?
    The question is if this command will work only for those users who currently have archiving enabled or it Will also work for those users which we are planing to enable archiving in the future?
    The idea is that everyone would not have 50GB by default and this should be a default value also for those who currently do not have archiving enabled.
    with best regards,
    bostjanc

    Hi there.
    I don't quite get it.
    I have created "for example" a database called: STH ARCHIVE.
    Then if I take look on properties of this database this is how it's shown:
    And now here comes the "tricky part" which is a little bit odd to me.
    I have enabled archive on my mailbox and selected this STH ARCHIVE DB to hold this archive mailbox.
    Then I have manually ran ManagedFolderAssistant for my account: Start-ManagedFolderAssistant -Identity "my-email-address"
    And after I have greped the size of my mailbox:
    Get-Mailbox | Get-MailboxStatistics -Archive | Sort totalitemsize -desc | ft displayname,totalitemsize, itemcount >C:\report-archive-database-mailboxes.txt
    And get the result:
    Personal Archive - MYUSERNAME
    TotalItemSize: 4.071 GB (4,371,586,689 bytes)  
    ItemCount: 55227
    So now I don't understand how I was able to go thru that sizes which are in the upper print screen of archive DB properties?
    bostjanc

  • Best practice on mailbox database size & we need how many server for deployment exchange server 2013

    Dear all,
    We have  an server that runs Microsoft exchange server 2007 with the following specification:
    4 servers: Hub&CAS1 & Hub&CAS2 & Mailbox1 & Mailbox2 
    Operating System : Microsoft Windows Server 2003 R2 Enterprise x64
    6 mailbox databases
    1500 Mailboxes
    We need to upgrade our exchange server from 2007 to 2013 to fulfill the following requirment:
    I want to upgrade the exchange server 2007 to exchange server 2013 and implement the following details:
    1500 mailboxes
    10GB or 15GB mailbox quota for each user
    How many
    servers and databases  are
    required for this migration<ins cite="mailto:Mohammad%20Ashouri" datetime="2014-05-18T22:41"></ins>?
    Number of the servers:
    Number of the databases:
    Size of each database:
    Many thanks.

    You will also need to check server role requirement in exchange 2013. Please go through this link to calculate the server role requirement : http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
    2TB is recommended maximum database size for Exchange 2013 databases.
    Here is the complete checklist to upgrade from exchange 2007 to 2013 : http://technet.microsoft.com/en-us/library/ff805032%28v=exchg.150%29.aspx
    Meanwhile, to reduce the risks and time consumed during the completion of migration process, you can have a look at this proficient application(http://www.exchangemigrationtool.com/) that would also be
    a good approach for 1500 users. It will help you to ensure the data security during the migration between exchange 2007 and 2013.

  • Mailbox database Size

    Hi,
       I have DAG enabled Exchange Server 2010 installed with three mailbox databases having sizes 282GB,162GB and 129GB respectively. I have started with a total of 250GB in 2010 and now it has reached a size more than 650GB.
       It has become very difficult to take the backup of such huge database files now and restoring it in case of a DR.
       Presently I have not enabled online archiving in any of these mailboxes mainly because most of the PCs are installed with outlook 2007 which doesn't show online archive.Of course OWA is another candidate to see those mails.
       Please suggest a best practice to reduce the size of these mailbox databases without losing any of the mails.
    Thanks
    Thomas

    As mentioned above, Exchange database files do not shrink.  
    If you do a defrag, then since you have copies of this DB in the DAG then you have to reseed.  take a look at this
    http://blogs.technet.com/b/rmilne/archive/2013/08/23/offline-defrag-and-dag-databases_2c00_-oh-my_2100_.aspx
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Removing Pubilc folder and default mailbox database

    I have two mailbox sever in our environment, a virtual EX2010 and physical EX server 2010. We had migrated from EX2003 to Virtual
    EX2010 including Public folders. All the clients are using Outlook 2010 so we don’t need the public folders. All the mailbox have been moved to physical EX2010.
    I have used
    ADSIEdit tool and removed the public folders completely but the other
    mailbox database is still referring ( path ) to default public folder ( DB properties – client setting)
    I am not using Virtual Exchange and when I try to delete the default mailbox database I get below eroor msg.
    The mailbox database Mailbox Database 145247587848' cannot be deleted.
    Mailbox Database 145247587848
    Failed
    Error:
    This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, or arbitration mailboxes. To get a list of all mailboxes in this database, run the command
    Get-Mailbox -Database <Database ID>. To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of archive mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Archive. To get
    a list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Arbitration. To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID>.
    To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID> -Archive. Arbitration mailboxes should be moved to another server; to do this, run the command New-MoveRequest <parameters>. If this
    is the last server in the organization, run the command Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox. Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan
    <MailboxPlan ID> -Database <Database ID>.
    Can anyone guide me how to resolve these issues so I can uninstall exchange roll.
    Thanks

    Hi,
    Just as what Amit suggested, if you want to remove the default public folder database for a mailbox database, you can clear the value of the msExchHomePublicMDB attribute.
    Here is a related article for your reference.
    http://exchangeserverpro.com/remove-default-public-folder-database-exchange-mailbox-database/
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange server 2013 supported mailbox databases and public folder databases

    I want to know about Exchange server 2013 SP1 Standard and Enterprise version support how many Mailbox databases and Public folder Databases? Total Mailbox and Public folder databases supported information.
    I Know as below but not clear:
    1) Exchange server 2013 SP1 Sandard edition support 5 Databases, It's include Public folder databases, total=5 or 5 mailbox databases+5 public folder databases=10 databases
    2) Exchange server 2013 SP1 Enterprise edition support 100 Databases, It's include Public folder databases, total=100 or 100 mailbox databases+100 public folder databases=200 databases
    kindly let me know. Thanks.
    Babu

    Hi Babu,
    Please check this link too.
    http://blogs.technet.com/b/exchange/archive/2013/06/04/per-server-database-limits-explained.aspxhttp://blogs.technet.com/b/exchange/archive/2013/06/04/per-server-database-limits-explained.aspx
    Thanks & Regards S.Nithyanandham

  • Error While Removing Mailbox Databases

    I'm trying to remove two extra Mailbox databases that we recently migrated users off of during consolidation. However, when I try and remove the DB's I get the following error message:
    Microsoft Exchange Error
    The mailbox database 'chsexmbm' cannot be deleted.
    chsexmbm
    Failed
    Error:
    This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, or arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database <Database ID>. To get a list of all mailbox plans
    in this database, run the command Get-MailboxPlan. To get a list of archive mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Archive. To get a list of all arbitration mailboxes in this database, run the command Get-Mailbox
    -Database <Database ID> -Arbitration. To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the
    command Disable-Mailbox <Mailbox ID> -Archive. Arbitration mailboxes should be moved to another server; to do this, run the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command Disable-Mailbox <Mailbox
    ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox. Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID> -Database <Database ID>.
    OK
    Now I have run the "Get-Mailbox -Database <DB> -Arbitration" and get three entries:
    Name                                    Alias                                  
    ServerName
    FederatedEmail.4c1f4d8b-8179-4148-93bf- FederatedEmail.4c1f4d8b-8179-4148-93bf- smschsexmb1
    00a95fa1e042                            00a95fa1e042
    SystemMailbox{1f05a927-f1d5-4153-bd93-d SystemMailbox{1f05a927-f1d5-4153-bd93-d smschsexmb1
    fca46ac6957}                            fca46ac6957}
    SystemMailbox{e0dc1c29-89c3-4034-b678-e SystemMailbox{e0dc1c29-89c3-4034-b678-e smschsexmb1
    6c29d823ed9}                            6c29d823ed9}
    However, when I try and move or remove these mailboxes, I get an error from EMS stating that they cannot be found.
    Any idea what I need to do here to resolve this so I can remove these DB's?
    Thanks!!

    Hi
    Suggestion 1:  verify mailboxes:
    1. In Exchange management shell, run these cmdlets:
    Set-ADServerSettings -ViewEntireForest  $True
    get-mailbox -database "DBname" –arbitration
    2. Please verify if arbitration mailbox shows. If yes, please move these mailboxes with this cmdlet:
    Get-Mailbox -Database "DBname" -Arbitration|New-MoveRequest -TargetDatabase "DB2Name"
    Note: please replace DB2Name with the target database name.
    3. Wait for the complete of AD replication, after that, please try to remove database again.
    Suggestion 2: If the database still cannot be removed and you have followed the instruction in error message, but nothing returned. It seems the database is empty. So I suggest we use ADSI Edit to remove the database object directly since it no
    longer contains any mailboxes.
    TechNet Subscriber Support
    in forum
    If you have any feedback on our support, please contact
    [email protected]
    Terence Yu
    TechNet Community Support

  • Duplicate Messages In Archive Mailbox

    We are running Exchange 2010 sp1 rollup 8.
    Hub Transport, CAS, Mailbox, UM running on same server.
    We have recently started testing archiving.
    We created a test archive database and enabled archiving for a group of test users, pointing the archive mailboxes to the archive database.
    The mailboxes have a retention policy with three tags in it which are as follows.
    1. Tag Type: "All other folders in the mailbox"
        Age Limit: 180
        Action: "Move To Archive"
    2. Tag Type: "Sent Items"
        Age Limit: 180
        Action: "Move To Archive"
    3. Tag Type: "Inbox"
        Age Limit: 180
        Action: "Move To Limit"
    The policy appears to be working, but we are seeing duplicates of all messages in the archive mailboxes.
    Thank You in advance for any ideas relating to this issue.

    I suggest you open a support case for analysis. http://support.microsoft.com/contactus/
    Mike Crowley | MVP
    My Blog --
    Planet Technologies

  • Problems with archive mailbox in Outlook, with exchange 2010+2013 co-existence

    Hi!
    We have an Exchange 2010 environment plus one Exchange 2013 MBX server meant for archive mailbox purpose. (We are going to upgrade to 2013 but with over 20.000 mailboxes it will take som time. Therefore we need to co-exist with primary mbx on 2010 and archive
    mbx on 2013 for some time.)
    My primary mailbox is on a 2010 MBX server, and I have today given myself an archive mbx on 2013 MBX server.
    When I use OWA, both my primary mailbox and my archive shows up and everything works 100% fine!
    But when I try Outlook 2010 or Outlook 2013, only my primary mailbox works. The archive mailbox shows up, but generates an error when accessing it:
    "The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance"
    Anyone who knows about this issue? Would we nice to know why it works in OWA but not in Outlook.
    Thanks!
    Trond Jenssen

    Hi,
    Please try to recreate a profile to access archieve mailbox.
    If it doesn't make sense, also try Uncheck “Download shared folders” and check it again.
    If you have any feedback on our support, please click
    here
    Wendy Liu
    TechNet Community Support

  • Exchange 2010 - Create a new Mailbox Database

    Hello all and thanks in advance for your time and expertise.
    Here's my scenario:
    In my ORG we have one exchange server.  The hard drive space on this server was quite low so we added two more drives which are independent and in their own Raid Configuration from the drives that were already installed.  In other words, the current
    mailbox database is housed on drives with a total storage capacity of 837GB. 
    We recently added two more drives, each 2TB, and configured them in a RAID1. 
    I'm going to create a new Mailbox Database on the 2TB drives and move over some mailboxes to balance out the storage. 
    Question one:  When we move some of the mailboxes over to the new database - will this free up space on the existing database or do we have to reclaim it such as with an offline degrag.
    Question two:  When I create the new mailbox database and I'm prompted to Enter the new file locations for the database (database path and log folder path) - do I just change the paths to the new drive letter path such as G:
    We're eventually going to Office365 (hopefully sooner rather than later) but I just want to make sure I handle this process correctly. Your input here is greatly appreciated.

    Hello,
    Your databse size is 650 GB.  As per my experience , it would not take more than 14 hours for total mailbox movement.
    You will be creating new database of 2 TB , you have already allocated 2 Tb drive to exchange server.
    If you are dividing drive into 2 or four part and creating that much databse, it will be helpful for maintence activity in future.
    It is recommended that you move mailbox during off bussiness hours, it will fasten the movment,as there will be no load on exchange server . You can do it on daily basis Or you can do it on weekend .
    You need to take care of logs generated during movment, are you going to  use seperate log drive for databse, or combine with database drive. If you are moving all mailbox to one database, It will genrate same size of logs file as of total mailboxes
    size (650 GB). You neeed to handle it properly. Enable circular logging on database, after movment ,you can disable it.
    Moreover, if you will create move request of all mailboxes, exchange will process nly 50 request, rest will be in queue state.
    Regarding public folders, I understand there is no seperate disk for public folders, if you planning to delete old dtabse and free up disk space, you will have to move this public folders database to new disk also.
    Would recommend that you take advice  from other expert in this forum, before implementation.

  • Seed mailbox database copy through replication network (DAG members on different subnets in different sites)

    Good afternoon
    I currently operate a two node DAG in our primary site supporting one mailbox database. I plan to introduce a third DAG node in our datacenter which is in a different Active Directory site. Both current DAG members replicate over a dedicated replication
    network to keep the traffic separate from the MAPI traffic. The third DAG member will also have a dedicated replication network adapter (of course, on a different subnet). Ideally I would like to seed the database at a time of my choosing, rather than at the
    moment I add the mailbox database copy (I know how to achieve this), but I would like to specify which network the data replicates over.
    According to the following (see below link) under the 'Seeding and Networks' section as my two DAG members will be on different subnets in different sites Exchange will make the decision to use the MAPI network adapters of the target and source server.
    'If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.'
    http://technet.microsoft.com/en-us/library/dd335158%28v=exchg.150%29.aspx
    Am I able to force Exchange to use the replication network adapters of both source and target server when I initiate the seeding process? I have a 200+ GB mailbox database that will need to replicate over a 100Mbps internet connection to our secondary
    site and I would like to keep that traffic to the replication network I have configured.
    Any insight would be helpful.

    Hi,
    If you want to specify the networks for seeding, you can use the
    Network parameter when running the
    Update-MailboxDatabaseCopy cmdlet and specify the DAG networks that you want to use.
     If you don't use the Network parameter, then the system uses the following default behavior for selecting a network to use for the seeding operation:
    If the source server and target server are on the same subnet and a replication network has been configured that includes the subnet, the replication network will be used.
    If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.
    If the source server and target server are in different datacenters, the client (MAPI) network will be used for seeding.
    So please use the Update-MailboxDatabaseCopy cmdlet with
    NetWork parameter to specify which DAG network should be used for seeding.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

Maybe you are looking for

  • SUN ONE Directory Server installation Problem on Win XP

    Can some one look at the installation error on WIndows XP ERROR: Ldap authentication failed for url ldap://santoshlaptop.cook.com:51303/o=NetscapeRoot user id admin (151:Unknown error.) Fatal Slapd Did not add Directory Server information to Configur

  • Error While validating OAGIS Document

    Hi All, My requirement is that i need to send a OAGIS 9.0 file from the Host Trading partner to the Remote trading partner. So, i have defined the OAGIS document in the Custom Document protocol over Generic Busines Protocol.I does not get any error w

  • Need help with my iTunes on iPhone 5 and Macbook Pro

    Need help with my iPhone 5 and my Macbook Pro.  I was purchased some music on itunes at my mac. Some reason I deleted those music from both on Mac and iPhone 5.  Today, I went to my iPhone iTunes store inside of iCloud to redownload my puchased. But

  • Creative Cloud Desktop App wont install on my Win 7

    Hello, i have been trying to install the CC Desktop on my computer all day today but it doesnt seem to work. I cleared the cache and tried to run the application in safe mode too but it just doesnt work. Does anyone have a work around to this? Thanks

  • Cat0-3750 upgrade. Error: system number 1 does not support the same feature

    I am trying to upgrade or rather downgrade from ipadvservices (inadvertently upgraded to) to ipservices on a stack of Cat-3750s, but I get the following error message: Ios Image File Size: 0x00877A00 Total Image File Size: 0x00B04200 Minimum Dram req