Re-create Mailbox Database

I have a DB on a disk that is almost out of space, so I've moved all user mailboxes to a new DB, as recommended rather than offline defragging.
I have a single DAG made up of 3 members although 2 have all the DB Split between them (Active/passive).
Anyway I want to know now I've moved all users off it the simplest way of removing the existing DB (Which now only has the System arbitration mailbox left on it) and re-creating it ? e.g; can I simply remove the DB via powershell, what happens to arbitration
or do I not care?, then setup as if I was creating a brand new DB with the same name ?
steps and Suggestions please, Many Thanks

Hi,
From your description, I recommend you move (not remove) your EDB files using the following cmdlet.
Move-DatabasePath "Mailbox Database identity" -EdbFilePath "x:\xxx"
What's more, you need to move the arbitration mailboxes to the new mailbox database.
To verify whether the database is mounted and accessible you can use the following two cmdlets.
Get-MailboxDatabase -Status "Mailbox Database identity" | Select Name,Mounted
Test-MAPIConnectivity -Database "Mailbox Database identity"
Hope this can be helpful.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

How to create new storage group and mailbox database on exchange 2007 CCR

Hi, Our Environment:
Exchange 2007 SP3 CCR.
Now I want to create a new storage group with edb file and log files on the new drive.
My plan is as below:
Once we have new drive ready on both active node and passive node,
1): Create new storage group with log files for this new storage group on other new drive from Active Node.
2): Create new mailbox database under this newly created storage group with the DB file on the new drive from active node.
My question is:
1): Do I need to perform above steps from active node only? or Do I need to do it from both active node and passive node?
2): How many storage groups can we create on one Exchange 2007 Enterprise server, we already have 25 SGs in place.
Thanks in advance.

Hi,
Here are my answers you can refer to:
1. We can just create new storage group on the active node. And it’ll be replicated to the passive node.
We can use the following command in EMS to verify the new Storage Group is being replicated to the passive node:
Get-StorageGroupCopyStatus "Second Storage Group" | Select SummaryCopyStatus,CCRTargetNode
http://exchangepedia.com/blog/2007/08/how-to-create-new-storage-group-in-ccr.html
2. For Exchange 2007 enterprise version, we can have up to 50 storage groups:
http://www.computerperformance.co.uk/exchange2007/exchange2007_storage_groups.htm
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.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
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.

MapiExceptionADNotFound When Creating a new Mailbox Database, No such error on the internet

HI
I have a problem that is when I create a new Mailbox Database I face the Error
Failed
Error:
Exchange is unable to mount the database that you specified. Specified database: EMAIL\Second Storage Group\EmailData; Error code: MapiExceptionADNotFound: Unable to mount database. (hr=0x80004005, ec=2417)
Exchange Management Shell command attempted:
mount-database -Identity 'CN=EmailData,CN=Second Storage Group,CN=InformationStore,CN=EMAIL,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=com'
Elapsed Time: 00:00:00
I have this server exchange 2007 SP1 running on Server 2003 SP2 R2 64-Bit
its also additional exchange to the old ex server 2003 SP2
what is this error
I check the evenlog and there is NO related error for this
and I ran EXPBA and it report no problem
I search MSN and Google for this and nothing usefull found
what shell I do
I am a fried that the Main database may fail if this present

Force replication betwenn Domain Controllers.
Article in PT-BR:
http://www.wellingtonagapto.org/2014/07/mapiexceptionadnotfound-unable-to-mount-database-hr-0x80004005-ec-2417-Exchange-Server-2007.html
Wellington Agápto
Consultor de Comunicações Unificadas & Mobilidade
ITIL, CCNA, MCP, MTA, MCITP, MCTS, MCSA, MCSE Communication
Edefense Segurança Digital
Site: http://www.edefense.com.br
Blog: http://www.wellingtonagapto.org

Cannot add mailbox database copy to DR site - .edb file not getting created

I have a DR site setup that I want copies of 4 of my mailbox databases. 3 of the mailbox databases copied over successfully but the last and largest one which is really not that large 69Gbs keeps failing when i Update the database copy. Seems
to not be creating the .edb file. Is there another way to get the .edb file over to the server, possibly manually copying it then doing and update database copy? I have my backups turned off on all the servers that have the mailbox role on it now
thinking that was causing some issues with the database copy? Any suggestions is appreciated, thanks.
Michael Duhon

Yes manually copy the edb file and paste them in the DR server . Then try to update with for the incremental of database copy. Verify the database is clean shutdown that you are moving to the DR site.
What error message it throws when you performing update the database copy
Exchange Queries

Automate creating a mailbox database

Hi everyone,
I have a new deployment at a customer and I want to create many databases in an automated way. I have all the settings in an excel sheet delivered by the customer after reviewing design options.
So how can I do such automated creation for the databases? I have to specify some quota settings that are different in each database
Mohammad, IT NOC Team

Assuming you have a csv located at C:\DB.csv, you can open a Microsoft Exchange PowerShell Console and run:
(assuming that your databases will be located at F:\DBs\ and logs at F:\Logs
$csv= import-csv -path c:\db.csv
Foreach ($row in $csv)
New-MailboxDatabase -name $row.name -server $row.server -edbfilepath "F:\DBs\($row.name).edb" -logFolderPath "F:\LOGs"
Set-MailboxDatabase $row.name -MailboxRetention 30.00:00:00 -ProhibitSendReceiveQuota 1.5gb -ProhibitSendQuota 1gb -RecoverableItemsQuota 3gb -RecoverableItemsWarningQuota 512MB -DeletedItemRetention 30.00:00:00 -MaintenanceSchedule {Sun.4:00 AM-Sun.8:00
AM, Mon.4:00 AM-Mon.8:00 AM, Tue.4:00 AM-Tue.8:00 AM, Wed.4:00 AM-Wed.8:00 AM, Thu.4:00 AM-Thu.8:00 AM, Fri.4:00 AM-Fri.8:00 AM, Sat.4:00 AM-Sat.8:00 AM} -QuotaNotificationSchedule {Sun.12:00 AM-Sun.12:15 AM, Mon.12:00 AM-Mon.12:15 AM, Tue.12:00 AM-Tue.12:15
AM,Wed.12:00 AM-Wed.12:15 AM,Thu.12:00 AM-Thu.12:15 AM,Fri.12:00 AM-Fri.12:15 AM,Sat.12:00 AM-Sat.12:15 AM} -RetainDeletedItemsUntilBackup $True -IssueWarningQuota 900MB
You can customize the above script to match your database settings
ammarhasayen

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)

Unable to create mail database

okay, I had 4 hard drives fail at once on my Storage Server,
Lost the VHD for my Exchange VM
Created a new VM, recovered Exchange 2010 SP3 using setup /m:recoverserver
Didn't appear to have any errors until it was time to mount the database, database wouldn't mount.
Tried to create a new database, getting Error 5000.
When I looked under Exchange\V14\mailbox, I can't actually find a copy of my mail database, so, I am not able to mount because I can't actually create a good mail database.
When I try to create a mail database, I get these errors
From EMC
AcmeMail2
Failed
Error:
Couldn't set the System Attendant for database "AcmeMail2".
The requested search root 'Acmenet.local/Configuration/Services/Microsoft Exchange/Acme/Administrative Groups/Exchange Administrative Group (FYDIBOHF23SPDLT)/Servers/Acme/Microsoft System Attendant' is not within the scope of this operation. Cannot perform
searches outside the scope 'Acmenet.local/MyBusiness'.
Warning:
An error occurred while trying to prepopulate newly created mailbox "/o=Acme/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=SystemMailbox{22655608-c412-4e60-baa3-4d716ab38f20}" in database "AcmeMail2" on server "Acme".
"/o=Acme/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=SystemMailbox{22655608-c412-4e60-baa3-4d716ab38f20}" may not immediately be available for certain cmdlets and operations until it has replicated. If you need to run the
cmdlet again, and you want more information about the error, please add the -Verbose parameter. Error: 0x8004010F.
Exchange Management Shell command attempted:
new-mailboxdatabase -Server 'Acme' -Name 'AcmeMail2' -EdbFilePath 'C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2\AcmeMail2.edb' -LogFolderPath 'C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2'
From the Application Log
Event ID 5000
Failed to save admin audit log for this cmdlet invocation.
Organization:
Log content:
Subject: Acmenet.local/Users/Administrator : New-MailboxDatabase
Body:
Cmdlet Name: New-MailboxDatabase
Object Modified: AcmeMail2
Parameter: Server = Acme
Parameter: Name = AcmeMail2
Parameter: EdbFilePath = C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2\AcmeMail2.edb
Parameter: LogFolderPath = C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2
Property Modified: OrganizationId =
Property Modified: Id = AcmeMail2
Property Modified: DataMoveReplicationConstraint = None
Property Modified: RawName = AcmeMail2
Property Modified: RpcClientAccessServerExchangeLegacyDN = /o=Acme/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Acme
Property Modified: Server = Acme
Property Modified: LogFilePrefix = E01
Property Modified: LogFolderPath = C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2
Property Modified: SystemFolderPath = C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2
Property Modified: AdminDisplayName = AcmeMail2
Property Modified: ExchangeLegacyDN = /o=Acme/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Acme/cn=Microsoft Private MDB
Property Modified: EdbFilePath = C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\AcmeMail2\AcmeMail2.edb
Property Modified: DisplayName = AcmeMail2
Property Modified: MasterServerOrAvailabilityGroup = Acme
Property Original: OrganizationId =
Property Original: Id =
Property Original: DataMoveReplicationConstraint = SecondCopy
Property Original: RawName =
Property Original: RpcClientAccessServerExchangeLegacyDN =
Property Original: Server =
Property Original: LogFilePrefix =
Property Original: LogFolderPath =
Property Original: SystemFolderPath =
Property Original: AdminDisplayName =
Property Original: ExchangeLegacyDN =
Property Original: EdbFilePath =
Property Original: DisplayName =
Property Original: MasterServerOrAvailabilityGroup =
Caller: Acmenet.local/Users/Administrator
Succeeded: False
Error: System.InvalidOperationException: Couldn\'t set the System Attendant for database \"AcmeMail2\". ---> Microsoft.Exchange.Data.Directory.ADOperationException: The requested search root \'Acmenet.local/Configuration/Services/Microsoft Exchange/Acme/Administrative
Groups/Exchange Administrative Group (FYDIBOHF23SPDLT)/Servers/Acme/Microsoft System Attendant\' is not within the scope of this operation. Cannot perform searches outside the scope \'Acmenet.local/MyBusiness\'.\r\n at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String
preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, String optionalBaseDN, ADObjectId& rootId, ADScope scope)\r\n at Microsoft.Exchange.Data.Directory.ADSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request,
ADObjectId originalId, Boolean emptyObjectSessionOnException)\r\n at Microsoft.Exchange.Data.Directory.ADSession.Save(ADObject instanceToSave, IEnumerable`1 properties)\r\n at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession.Microsoft.Exchange.Data.IConfigDataProvider.Save(IConfigurable
instance)\r\n at Microsoft.Exchange.Management.SystemConfigurationTasks.NewMailboxDatabase.SetSystemAttendantObject(MailboxDatabase database)\r\n --- End of inner exception stack trace ---
Run Date: 2014-04-04T19:48:39
OriginatingServer: Acme (14.03.0123.002)
Error:
Exception thrown during AdminLogProvisioningHandler.Validate: Microsoft.Exchange.Data.Storage.ObjectNotFoundException: The discovery mailbox, a hidden default mailbox that is required to search mailboxes, can't be found. It may have been inadvertently deleted.
This mailbox must be re-created before you can search mailboxes.
at Microsoft.Exchange.Data.Storage.Infoworker.MailboxSearch.MailboxDataProvider.GetDiscoveryMailbox(ADRecipientSession session)
at Microsoft.Exchange.Management.SystemConfigurationTasks.AdminAuditLogHelper.CheckArbitrationMailboxStatus(OrganizationId organizationId, ADUser& user, ExchangePrincipal& principal, String& errorMessage)
And Event ID 3154
Active Manager failed to mount database AcmeMail on server Acme.Acmenet.local. Error: An Active Manager operation failed. Error The database was never mounted..
On the Domain Controller, I have run setup /prepareAD several times
Any suggestions?
Don Miller Network Administrator Teton Machine Company

In the case,
the VM is hosted on the Host machine's local drive, the VHD is too.
I created this database about an hour ago (there still isn't a database or log file that has been created), but when I try to mount it manually, I am getting this error
Microsoft Exchange Error
Failed to mount database 'acme'.
acme
Failed
Error:
Couldn't mount the database that you specified. Specified database: acme; Error code: An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred
during a database operation. Error: An error occurred while preparing to mount database 'acme'. Error: An I/O error occurred while attempting to enumerate log files. Error 0x3 (The system cannot find the path specified) from Windows API 'FindFirstFile'. [Database:
acme, Server: acme.acmenet.local].
An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: An error occurred while preparing to mount database
'acme'. Error: An I/O error occurred while attempting to enumerate log files. Error 0x3 (The system cannot find the path specified) from Windows API 'FindFirstFile'. [Database: acme, Server: acme.acmenet.local]
An Active Manager operation failed with a transient error. Please retry the operation. Error: An error occurred while preparing to mount database 'acme'. Error: An I/O error occurred while attempting to enumerate log files. Error 0x3 (The system cannot find
the path specified) from Windows API 'FindFirstFile'. [Server: acme.acmenet.local]
An error occurred while preparing to mount database 'acme'. Error: An I/O error occurred while attempting to enumerate log files. Error 0x3 (The system cannot find the path specified) from Windows API 'FindFirstFile'.
An I/O error occurred while attempting to enumerate log files. Error 0x3 (The system cannot find the path specified) from Windows API 'FindFirstFile'
Don Miller Network Administrator Teton Machine Company

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

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

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

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

Powershell command to migrate Exchange 2007 mailbox databases with a legacy name, & import them into a new 2007 instance, with a new name.

Hi All. I am currently at the later stage of provisioning a new CCR Exchange 2007 migration (to
virtualise old Exchange 2007 hardware) for 5,000 users & have a quick question.
I have created around 15 newly named storage groups, & have named 1 new DB per group, with the same name (let's say New-DB-1), residing within them. The problem I have, is the old legacy DB's have different names (let's say Old-DB-1) & I need
to import them into the new storage groups, to match the new names. So far I can import/export between old & new OK if both old & new DB names\folders etc. names marry up perfectly, but are unable to if there not the same. Does anyone have any thoughts
on how best to tackle this, as this is one of the final hurdles stopping the migration? Many Thanks, John

Hi All
Many Thanks for the feedback.
The terminology 'migrate' was used based around the fact I will be decommissioning the old 2007 physical environment. This is after moving all DB's over to the new newly created Virtual environment that will host all roles.
The solution I ended up using yesterday, was the following:
1) Dismounted the relevant named DB (NEWDB) in the new environment.
2) I then ticked the 'This database can be overwritten by a restore option' box.
3) Copied over the old named DB (OLDDB) to the same location, & overwrote using the new name (NEWDB).
4) Re-mounted the (NEWDB).
5) Ran the following 2 PowerShell commands:
Get-mailbox –database OLDDB | move-mailbox –targetdatabase NEWDB -configurationonly:$true
Get-MailboxDatabase NEWDB | ResetSearchIndex.ps1 -force
6) Checked to make sure the clients were working ok, in the now the new (NEWDB) environment.
Rich: Many thanks for your PS script, which I will test with future DB moves & provide feedback
J
John.

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

Mailbox Databases - 1500 users Exchange 2010 DAG

I have the following setup for a 5 server DAG setup and would like to know the recommended setup for high availability for all user databases. I would like the databases copied to several DAG members servers, but am unsure as to how i should stagger the
database replication. Please see the drive sizes below and send me feedback/recommendations.
Each of my DAG member servers (mailbox servers) has the following storage space available:
C:\60GB(O/S), D:\1TB(Mailboxes), E:\1TB(Mailboxes) F:$logs)
How many databases should i create to maximize efficiency and give best user performance/experience?
To how many DAG member servers should i copy the database in order to achieve a reasonable amount of High Availability?
Again, I have 1500 users and 2TB per server to accommodate mailbox databases.
Users average 500MB mailbox quotas.
Can i create the DAG replicas on the second drive (E:$ or should i just use both terabyte volumes exclusively for users mailboxes?

Hi,
5 members in a DAG and one database created for every member, I suggest you create three copys for a database like the following figure. Any two servers corruption couldn't interrupt any client connection.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Sean Xiao
TechNet Community Support

Re-create Mailbox Database

Similar Messages

Maybe you are looking for