Mailbox Database

Hello ,
I have Exchange 2007 with 6 Mailbox Databases
I need to run a command to export excel sheet for each database and a list of mailboxes related to this database .
I am trying to prepare Migration batch file for Exchange 2013 .
thnx
MCP MCSA MCSE MCT MCTS CCNA

Hi,
I have some tests in my environment using Exchange 2007, you can use the following cmdlet to export mailboxes grouped by mailbox database.
Get-Mailbox | Sort database, name | Select name, database | Export-Csv C:\MailboxResultTest.csv –NoTypeInformation
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Similar Messages

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

Removing mailbox databases

Hello!
I'm getting this warning when removing a mailbox database in Exchnage 2013 SP1:
I've never had it in Exchange 2013 (NOT SP1)... How can I now remove a "monitoring mailbox object of database ..." from my AD?
Thank you in advance,
Michael

Hi
Here you go
Failed to remove monitoring mailbox object of database “database_name”. Exception: Active directory operation failed on “server_name”. This error is not retrievable. Additional information: Access is
denied. Active directory response: 000000005: SecErr: DSID-031520B2, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0.
In this case, the database was removed an Active Directory [AD] error (with a not very useful description) complaining about insufficient permissions is thrown. If you run:
Get-Mailbox -Monitoring
You will most likely see a warning regarding a corrupted Health Mailbox:
WARNING: The object “domain_name”/Microsoft Exchange System Objects/Monitoring Mailboxes/”Health_Mailbox_GUID” has been corrupted, and it's in an inconsistent state. The following validation errors happened:
WARNING: Database is mandatory or UserMailbox.
Because Exchange 2013 did not have sufficient permissions to the domainname/Microsoft Exchange System Objects/Monitoring Mailboxes Organizational Unit [OU], it could not delete the AD objects related to the database’s health mailboxes. In
this case, the database attribute is null because the database the health mailbox references no longer exists.
To fix this issue, simply delete the health mailboxes referenced by the error(s) from that OU by using Active Directory Users and Computers. After removing these, the warning should be gone.
Deleting health mailboxes is a low risk procedure because they will be automatically re-created by the Microsoft Exchange Health Manager service on the Exchange 2013 server hosting the database when this service is restarted
Source of information - http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/ManagementAdministration/exchange-2013-error-deleting-database.html
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

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

What is the best practice on mailbox database size in exchange 2013

Hi,
does anybody have any links to good sites that gives some pros/cons when it comes to the mailbox database sizes in exchange 2013? I've tried to google it - but hasn't found any good answers. I would like to know if I really need more than 5 mailbox databases
or not on my exchange environment.

Hi
As far as I know, 2TB is recommended maximum database size for Exchange 2013 databases.
If you have any feedback on our support, please click
here
Terence Yu
TechNet Community Support

Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database 1006.

HI all,
I ran into a problem with one of the servers in my DAG. Due to a backup failure, the log partition filled up and the Exchange database went offline on this particular server. The DAG continued to function on the other server. So this particular
DB01 had only some test accounts in it so I removed the database copy. Unfortunately the removal must not have completed correctly.
After recovering the needed space in the partition, I tried to recopy the database and it failed. So I deleted the entire database from the active server and it successfully removed it from the active server. Now on both the servers the database
is not showing, however I'm receiving the error below which indicates to me that the service still thinks the database exists. I am also getting event 4113 Database redundancy health check failed for the database copy as it shows there is only one copy
of the database (failed redundancy) but there should be zero copies.
This database no longer exists in AD as I have verified this with ADSI so it must have something on the exchange server that is still telling the service the database exists.
Can you point me to the location to clean this up?
Log Name:      Application
Source:        MSExchange Mailbox Replication
Date:          02/25/2011 2:00:07 PM
Event ID:      1006
Task Category: Service
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      email1.domain.com
Description:
The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: DB01
Error: MapiExceptionUnknownUser: Unable to open message store. (hr=0x80004005, ec=1003)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=243]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=200][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x3EB
    Lid: 26937
    Lid: 21921   StoreEc: 0x3EB
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 22086
    Lid: 27206
    Lid: 17990
    Lid: 16966   StoreEc: 0x8004010F
    Lid: 31433   StoreEc: 0x8004010F
    Lid: 8620    StoreEc: 0x3EB
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849
    Lid: 21817   ROP Failure: 0x3EB
    Lid: 26297
    Lid: 16585   StoreEc: 0x3EB
    Lid: 32441
    Lid: 1706    StoreEc: 0x3EB
    Lid: 24761
    Lid: 20665   StoreEc: 0x3EB
    Lid: 25785
    Lid: 29881   StoreEc: 0x3EB
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchange Mailbox Replication" />
    <EventID Qualifiers="32772">1006</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-02-25T22:00:07.000000000Z" />
    <EventRecordID>181576</EventRecordID>
    <Channel>Application</Channel>
    <Computer>email1.domain.com</Computer>
    <Security />
</System>
<EventData>
    <Data>DB01</Data>
    <Data>MapiExceptionUnknownUser: Unable to open message store. (hr=0x80004005, ec=1003)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=243]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=200][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x3EB
    Lid: 26937
    Lid: 21921   StoreEc: 0x3EB
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 22086
    Lid: 27206
    Lid: 17990
    Lid: 16966   StoreEc: 0x8004010F
    Lid: 31433   StoreEc: 0x8004010F
    Lid: 8620    StoreEc: 0x3EB
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849
    Lid: 21817   ROP Failure: 0x3EB
    Lid: 26297
    Lid: 16585   StoreEc: 0x3EB
    Lid: 32441
    Lid: 1706    StoreEc: 0x3EB
    Lid: 24761
    Lid: 20665   StoreEc: 0x3EB
    Lid: 25785
    Lid: 29881   StoreEc: 0x3EB     </Data>
</EventData>
</Event>

Hi
This error occurs because the MailboxReplicationService (MRS) currently caches Mailbox Database information past the lifetime of some databases.
Restarting the service will clear the cache.
Maybe it is the simplest way to solve it.
If it doesn’t work, you can try cmd to check it.
Get-MailboxDatabase : Can you find the database which you delete?
Remove-MailboxDatabase -Identity "MyDatabase": You can try to delete database if you can see the database.

Best practice for default location of mailbox database(s) / logs

Hello,
I don't recall seeing any options during the Exchange 2013 install, to specify an alternate location for either the mailbox database or log files. I've reviewed the commands for moving the mailbox databases, but before reviewing the options for setting a
location for the log files, I thought it best to see whether it's still advised to separate log/mailbox databases away from the OS, with our Exchange server being a virtualised instance?
Also, I'm assuming that Exchange still requires the usual backup of transaction logs, for them to be cleared?
Many thanks.

Hi JH,
here is a link to storage options and requirements for the Mailbox server :
http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
By default when installing New Exchange server With mailbox role,it will create default database and log path.
Recomended is to have Database and Log files on seperate disks.You will have to attache those disk first,then you can create New database using ECP.
Please look at my Gallery With full guide on how to setup New Exchange server.
http://gallery.technet.microsoft.com/Install-Exchange-server-b5cce9e4
Also for future use you might need to clean up log files to free up Space on Your Exchange server:
http://gallery.technet.microsoft.com/Task-Scheduler-to-cleanup-25047622
Hope this helps
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

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.

Healthy copy of mailbox Database in DAG acting as a seeding source for another Healthy copy Database in DAG

Overview of the architecture
We have Site (Primary & DR)
2 Database copies in primary site and 1 Database on the DR site (Primary site 2 copies one mounted and second healthy & on the DR site one healthy copy of Database)
Recently Due to Network Problem the DR copy got in to the easyncronous state and was removed from the DAG.
As company does not want the downtime we have followed the below steps to Restore Database at DR site.
1)Stopped the backup to Not trucate the log file
2)Took Full backup and in the restore mode we shipped the full backup to the DR site.
3)As the above process needs 2 days, manually copied the some Logs to the DR site (IN some drive as much possible to reduce seed time)
4)Added the mailbox database of the DR site back in the DAG as its seeds from the start, we manually suspend the process post the Database folder hierrachy gets created
5)Added the EDB and logs files in the recently created folders
6)Resumed the Database seed, so only the remaining logs were copied and seeded from primary site to DR site, In some hours DR site databse became healhty with no copy queue and replay queue.
7)trucated the logs which synced using DAG
Now Dag has copies as initial setup but the since we followed the above process the primary site healthy copy is acting as the seed-source and logs not truncating for the database
When restarts the Replication services on the Primary site server with healthy the state becomes healthy but again after some time it becomes seed- source.
Wanted to know when DR site copy is in healthy state why its acting as a seed-source continueously
Need Experts advice in manage Database copies in healthy state...
Thanks in Advance

Hi,
Based on your description, sometimes the content index state of passive database copy in primary site is healthy, but sometimes the state is crawling.
You can use the following command to reseed the catalog only to check result.
Update-MailboxDatabaseCopy -Identity Database -SourceServer EX -CatalogOnly
Best regards,
Belinda Ma
TechNet Community Support

Mailbox database size before & after backup

Hi there
i recently made a similar thread and someone told me that i should do it here so here is my issue :
i've been assigned to do a specific report related to exchange and its backup
so what we want is a report that would give us the global size of all our mailbox databases before and after the backup ( even the size of the logs before and after)
(example : we have a mailbox database X: , we need to go inside the data folder, and retrieve the size of the .edb
then do the same thing with the logs, go inside the logs folder, and retrieve the logs size )
i was wondering if anyone ever managed to pull a script that does similar things, given the fact that i ve never worked with powershell and my knowledge is kinda limited in that area
Thanks

Hi Amassuo,
for finished scripts that do things, check out the
gallery. If you want to learn powershell (I might be biased, but I highly recommend it), check out the
learning center.
Regarding your specific issue, you can check the free space on a specific disk by running this powershell command:
Get-WmiObject win32_logicaldisk -Filter "DeviceID = 'C:'" | Select -ExpandProperty FreeSpace
Comparing before/after will get you the space differential (adapt drive letter in filter as needed).
Cheers and good luck with your script,
Fred
There's no place like 127.0.0.1

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

How do you assign a user or group FULL access to all Exchange 2013 DAG mailbox databases?

How do you assign a group or user FULL mailbox access rights to ALL mailboxes in the Organization or DAG mailbox databases?
Commands I've tried with no avail:
get-mailboxdatabase -server “exch01″ | add-adpermission -user “domain admins” -AccessRights GenericAll
get-mailboxdatabase -identity "DAG database" | add-adpermission -user "user" -accessrights FullAccess
Please let me know if you can help! Thanks.

Get-Mailbox | Add-MailboxPermission -Identity UserMailbox -User "Domain\Group" -AccessRights FullAccess - worked for me! Thanks again!

Reseed one Exchange 2013 server databases housing 15 mailbox databases (mailboxes) - NO DAG

I have one exchange server with fourteen server databases. One these server databases is housing 15 mailbox databases (user mailboxes databases) of these fifteen mailbox DB's all have the same search problem in both the inbox and
sent items. They all have the problem in outlook 2010 on their desktop and in Outlook Web APP - Everything I read refers to suggests a reseed of the database, since its effecting all 15 mailboxes in one server database I'm thinking I have to reseed
the one server database a DAG copy - again everything I read refers to a copy /DAG - I don't have a DAG.
I need to reseed this Exchange server database:
This one shows me how I can reseed mailbox database
https://technet.microsoft.com/en-us/library/ee633475(v=exchg.150).aspx
WHILE
http://exchangeserverpro.com/how-to-reseed-a-failed-database-copy-in-exchange-server-2013/
Shows me how to reseed a Copy of Exchange server database using EAC
I have never done either before - so I'm hoping someone can point me in the right direction
Thanks
rjm3rd

Hi,
If you don't have DAG, you need to follow the steps below to rebuild content index.
1. Stop the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services.
2. Delete, move, or rename the folder that contains the Exchange content index catalog.
3. Restart the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services.
Best regards,
Belinda Ma
TechNet Community Support

Enable-Mailbox: provisioning without -Database attribute (balance across mailbox databases)

We have a 16 Exchange 2013 Mailbox Databases. Of those 16, 12 have been 'Excluded from Provisioning'.
We are trying to come up with a script or at least command to enable-mailbox for existing AD user accounts.
The question is, we want the enable-mailbox command to balance or randomly create mailboxes across databases and not just on one specific database.
Can this be done?

Hi,
From your description, I would like to clarify the following thing:
Automatic distribution is used when you don't specify the Database parameter on the Enable-Mailbox cmdlet. This process randomly distributes mailboxes across all of the suitable mailbox databases in your organization.
If you also want the mailboxes to be distributed to the other 12 databases, you can run the cmdlet below to set the IsExcludedFromProvisioning to $false for them.
Set-MailboxDatabase <database name> -IsExcludedFromProvisioning $false
Hope my clarification can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

Mailbox Database

Similar Messages

Maybe you are looking for