Reseed Mailbox database
I have had several failed backups using Symantec Endpoint protection of my exchange server, currently the issue stems from the transaction logs being corrupt because the database log files were completely cleared to make sure the exchange server continued
to have space and wouldn't crash. The current solution I would like to try is to do a reseed of the mailbox database on the server that is causing the issue, however I want to know if anything can go wrong from running the command Update-MailboxDatabaseCopy
-Identity DB1\MBX1.
Wrong forum. Please post it in Exchange forum
http://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
Santhosh Sivarajan | Houston, TX | www.sivarajan.com
ITIL,MCITP,MCTS,MCSE (W2K3/W2K/NT4),MCSA(W2K3/W2K/MSG),Network+,CCNA
Windows Server 2012 Book - Migrating from 2008 to Windows Server 2012
Blogs: Blogs
Twitter: Twitter
LinkedIn: LinkedIn
Facebook: Facebook
Microsoft Virtual Academy:
Microsoft Virtual Academy
This posting is provided AS IS with no warranties, and confers no rights.
Similar Messages
-
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
rjm3rdHi,
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 -
CAS restart and Mailbox database dismount unexpectedly somtimes
Hi all,
In my environment I have 2 Exchange server 2013 (CAS + Mailbox Role both) CU2 : EX01 & EX02 in DAG01. Sometimes CAS service is restarted or Mailbox Database copy on Exchange servers is dismounted unexpectedly. For example today:
I have "Mailbox Database 01" copies on EX01 & EX02
Get-MailboxDatabaseCopyStatus "Mailbox Database 01"
Name Status
Mailbox Database 01\EX01 Healthy
Mailbox Database 01\EX02 Mounted
"Mailbox Database 01" copy on EX02 is dismounted, of course the other copy on EX01 is mounted automatically
Log Name: Application
Source: MSExchangeRepl
Date: 4/3/2015 2:32:19 PM
Event ID: 2153
Task Category: Service
Level: Error
Keywords: Classic
User: N/A
Computer: EX02.mydomain.com
Description:
The log copier was unable to communicate with server 'EX01.mydomain.com'. The copy of database 'Mailbox Database 01\EX02' is in a disconnected state. The communication error was: An error occurred while communicating with server 'EX01'. Error: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine. The copier will automatically retry after a short delay.
CAS service on EX01 , The Microsoft Exchange Mailbox Assistants service on EX02 are restarted
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:25:49 PM
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.mydomain.com
Description:
The Microsoft Exchange RPC Client Access service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:25:51 PM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: EX01.mydomain.com
Description:
The Microsoft Exchange RPC Client Access service entered the running state.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:25:54 PM
Event ID: 7032
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EX01.mydomain.com
Description:
The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange RPC Client Access service, but this action failed with the following error:
An instance of the service is already running.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:30:28 PM
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EX02.mydomain.com
Description:
The Microsoft Exchange Mailbox Assistants service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:30:30 PM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: EX02.mydomain.com
Description:
The Microsoft Exchange Mailbox Assistants service entered the running state.
Log Name: System
Source: Service Control Manager
Date: 4/3/2015 3:30:33 PM
Event ID: 7032
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: EX02.mydomain.com
Description:
The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange Mailbox Assistants service, but this action failed with the following error:
An instance of the service is already running.
On EX01 I can see many 1309 , 2009 , 6002 , 4999 in Event Viewer on both servers, and they just used half of RAM
I'm going to upgrade to SP1 this weekend but please help me to figure out really reason of this issue, limit of max connections on Exchange/Window server , or Disk IO or something ?
Thanks for your help.Last night I tried reseed Mailbox Database 01\EX02 , about 8:15 PM
I checked event viewer, last 2153 event happened on 7:49 PM, check around :
Get-MailboxDatabaseCopyStatus -Server ex02 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 07\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 01\EX02
IncomingLogCopyingNetwork : {EX01,ReplicationDagNetwork01,An error occurred while communicating with server
'EX01'. Error: Unable to write data to the transport connection: An established
connection was aborted by the software in your host machine.}
OutgoingConnections :
Name : Mailbox Database 99\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Get-MailboxDatabaseCopyStatus -Server ex01 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 01\EX01
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 99\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Name : Mailbox Database 07\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Then I suspend and update Mailbox Database 01\EX02
Suspend-MailboxDatabaseCopy -Identity "Mailbox Database 01\EX02"
Update-MailboxDatabaseCopy -Identity "Mailbox Database 01\EX02" -Network "DAG01\ReplicationDagNetwork01"
Confirm
Are you sure you want to perform this action?
Seeding database copy "Mailbox Database 01\EX02".
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):
The seeding operation failed. Error: An error occurred while running prerequisite checks. Error: Log files exist in
'D:\Exchange Mailbox Database\Mailbox Database 01'. You must remove them before database seeding or reseeding can be
performed. You can use the Update-MailboxDatabaseCopy cmdlet with the -DeleteExistingFiles or -SafeDeleteExistingFiles
parameter to do this. [Database: Mailbox Database 01, Server: EX02.mydomain.com]
+ CategoryInfo : InvalidOperation: (Mailbox Database 01:String) [Update-MailboxDatabaseCopy], SeedPrepare
Exception
+ FullyQualifiedErrorId : [Server=EX02,RequestId=56f71c07-6209-4aae-94cb-bf3cfc0a38fd,TimeStamp=4/22/2015 1:0
5:56 PM] [FailureCategory=Cmdlet-SeedPrepareException] 5F5B4C53,Microsoft.Exchange.Management.SystemConfigurationT
asks.UpdateDatabaseCopy
+ PSComputerName : ex02.mydomain.com
I want they use DAG01\ReplicationDagNetwork01 (1Gbps) for reseeding database, then I tried to add -SafeDeleteExistingFiles
Update-MailboxDatabaseCopy -Identity "Mailbox Database 01\EX02" -Network "DAG01\ReplicationDagNetwork01" -SafeDeleteExistingFiles
Confirm
Are you sure you want to perform this action?
Seeding database copy "Mailbox Database 01\EX02".
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):
The seeding operation failed. Error: An error occurred while running prerequisite checks. Error: An error occurred
when trying to run the database redundancy validation checks for database 'Mailbox Database 01' due to
'SafeDeleteExistingFiles' being specified. Error: There were database redundancy check failures for database 'Mailbox
Database 01' that may be lowering its redundancy and putting the database at risk of data loss. Redundancy Count: 1.
Expected Redundancy Count: 2. Detailed error(s):
ex02:
Database 'Mailbox Database 01' does not have enough copies configured to meet the validation criteria.
[Database: Mailbox Database 01, Server: EX02.mydomain.com]
+ CategoryInfo : InvalidOperation: (Mailbox Database 01:String) [Update-MailboxDatabaseCopy], SeedPrepare
Exception
+ FullyQualifiedErrorId : [Server=EX02,RequestId=48374aa6-1198-4976-a435-3eb034dc5b58,TimeStamp=4/22/2015 1:0
8:44 PM] [FailureCategory=Cmdlet-SeedPrepareException] 458ED9A2,Microsoft.Exchange.Management.SystemConfigurationT
asks.UpdateDatabaseCopy
+ PSComputerName : ex02.mydomain.com
I think I should stop here, search more about -DeleteExistingFiles before continue. So I Resume-MailboxDatabaseCopy "Mailbox Database 01\EX02"
Everything is fine, I checked again
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus -Server ex02 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 07\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 01\EX02
IncomingLogCopyingNetwork : {EX01,ReplicationDagNetwork01}
OutgoingConnections :
Name : Mailbox Database 99\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
[PS] C:\Windows\system32>Get-MailboxDatabaseCopyStatus -Server ex01 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 01\EX01
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 99\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Name : Mailbox Database 07\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections
What is going on :) ? IncomingLogCopyingNetwork for Mailbox Database 01\EX02 is fine :) til mid night
This morning I view events on EX02 and event 2153 appears again on 7:30 AM , I run command et-MailboxDatabaseCopyStatus again
Get-MailboxDatabaseCopyStatus -Server ex02 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 07\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 01\EX02
IncomingLogCopyingNetwork : {EX01,ReplicationDagNetwork01,An error occurred while communicating with server
'EX01'. Error: Unable to write data to the transport connection: An established
connection was aborted by the software in your host machine.}
OutgoingConnections :
Name : Mailbox Database 99\EX02
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Get-MailboxDatabaseCopyStatus -Server ex01 | fl name,*incoming*,*outgoing*
Name : Mailbox Database 01\EX01
IncomingLogCopyingNetwork :
OutgoingConnections : {}
Name : Mailbox Database 99\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Name : Mailbox Database 07\EX01
IncomingLogCopyingNetwork : {EX02,ReplicationDagNetwork01}
OutgoingConnections :
Any suggest ? -
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 AdvanceHi,
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 -
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
ThomasAs 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. -
Multiple mailbox databases - why?
can I ask from a low tech management standpoint, why you need more than one mailbox database per server? i.e. for what purposes do you need to split the number of mailboxes across more than 1 mailbox database?
Well, one reason may be to apply different database quota and retention policies.
Another may be for any maintenance that may be required ( Reseeding for example in a DAG environment). Smaller dbs mean quicker reseed times.
Things like that....
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied. -
Primary Mailbox Database fails to replicate after failing over to secondary copy in DAG
We had an issue yesterday on a primary mailbox database server when the drive the log files are located on filled up and took the databases off-line on the primary server bringing them up on the secondary.
After the issue was resolved and enough space was freed up, all but one database failed back. The one that would not come back showed Failed in the copy status. It remained mounted on the secondary server. I attempted several times to 'update' the copy and
it would run for aver 40 minutes and look like it was going okay then it would 'fail' and end up in a 'failed and suspended' state. The error would indicated it could not complete because the it could not find the source server.
The Update job was configured to point to the server holding the secondary copy as the source so should not have a problem.
Any idea on how I can get the primary copy working again? I thought about making the second copy the 1st to activate and removing the primary copy from the DAG and recreating it, but past experience doing that did not resolve the issue.
Thank you,
Nick
Nick LaurinoFind out why database file is missing, I doubt on antivirus and start looking at the antivirus sacanning exclusion to ensure it is properly set...
File-Level Antivirus Scanning on Exchange 2010
Then try to reseed the database copy from a good source, it might be possible that antivirus would be scanning file when it is getting reseeded and causing issue...
How to Reseed a Failed Mailbox Database Copy in Exchange Server 2010
Blog |
Get Your Exchange Powershell Tip of the Day from here -
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,
JonAny 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 -
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,
MichaelHi
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) -
[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 -
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. -
Unable to reseed the database .... test-replicationhealt is ok for both node . the problem is that content index is failed on both node .
VERBOSE: [07:18:55.867 GMT] Update-MailboxDatabaseCopy : Active Directory session settings for
'Update-MailboxDatabaseCopy' are: View Entire Forest: 'False', Default Scope: 'XXXXX.com', Configuration Domain
Controller: 'XXXXX.com', Preferred Global Catalog: 'XXXXX.com', Preferred Domain Controllers:
'{ XXXX.com, XXXXX.com }'
VERBOSE: [07:18:55.883 GMT] Update-MailboxDatabaseCopy : Runspace context: Executing user:
VERBOSE: [07:18:55.883 GMT] Update-MailboxDatabaseCopy : Beginning processing &
VERBOSE: [07:18:55.914 GMT] Update-MailboxDatabaseCopy : Instantiating handler with index 0 for cmdlet extension agent
"Admin Audit Log Agent".
VERBOSE: [07:18:55.930 GMT] Update-MailboxDatabaseCopy : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient
Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient
Scope(s): {}, Exclusive Configuration Scope(s): {} }
VERBOSE: [07:18:55.930 GMT] Update-MailboxDatabaseCopy : Searching objects "Mailbox_DB01\Server01" of type
"DatabaseCopy" under the root "$null".
VERBOSE: [07:18:55.977 GMT] Update-MailboxDatabaseCopy : Previous operation run on domain controller
'WDCDSBO2.ds.micron.com'.
VERBOSE: [07:18:55.977 GMT] Update-MailboxDatabaseCopy : Processing object "XXXXXXX".
VERBOSE: [07:18:56.008 GMT] Update-MailboxDatabaseCopy : Admin Audit Log: Entered Handler:Validate.
VERBOSE: [07:18:56.008 GMT] Update-MailboxDatabaseCopy : Admin Audit Log: Entered ClassFactory:InitializeConfig.
VERBOSE: [07:18:56.008 GMT] Update-MailboxDatabaseCopy : Admin Audit Log: Exited ClassFactory:InitializeConfig.
VERBOSE: [07:18:56.023 GMT] Update-MailboxDatabaseCopy : Admin Audit Log: Exited Handler:Validate.
VERBOSE: Updating database copy Server1 on server Server1.
VERBOSE: [07:18:56.023 GMT] Update-MailboxDatabaseCopy : Resolved current organization: .
VERBOSE: [07:18:56.039 GMT] Update-MailboxDatabaseCopy : Update-DatabaseCopy is requesting the Microsoft Exchange
Replication service on server 'Server1' to begin seeding.
VERBOSE: [07:19:14.353 GMT] Update-MailboxDatabaseCopy : Admin Audit Log: Entered Handler:OnComplete.
VERBOSE: [07:19:14.385 GMT] Update-MailboxDatabaseCopy : Admin Audit Log: Exited Handler:OnComplete.
A source-side operation failed. Error An error occurred while performing the seed operation. Error: Communication was t
erminated by server 'Server2': Data could not be read because the communication channel was closed.. [Da
tabase: XXXXXXXXX]
+ CategoryInfo : InvalidOperation: (:) [Update-MailboxDatabaseCopy], SeedInProgressException
+ FullyQualifiedErrorId : DDD603BC,Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateDatabaseCopyThis is the first step of trouble shooting which i did but no success . as i said both copy catalog index is in failed status
What I have done
Create
a full catalog index on mounted copy
Get Index catalog GetSearchIndexForDatabase.ps1 "databaseName"
Stop the index service and delete the catalog index by using ps1
.\ResetSearchIndex.ps1 -force "databaseName"
Start Search Index
crawling not initiated after this
2. Delete the failed copy and re add it again which added successfully but reseed process getting failed with same error .. and event ID 245 Information Store (4492) : The internal database
copy (for seeding or analysis purposes) has been stopped because it was halted by the client or because the connection with the client failed. -
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.
Maybe you are looking for
-
Hi, I am using RFBIBL00 in LSMW to upload AP/AR open items. When I run the job in the foreground, I am getting an error as the second line item is not filled (empty). I think that the structure of my upload file is not correct. Do you have sample upl
-
Why is it not allowed to place images in the english wiki?
Hello, in the german wiki I am allowed to upload images as a normal user. In the english version I am not. Why is it restricted? I think screenshots are a nice way to describe things. Or did I miss something? Thanks, Philip
-
There is a charge on my acct for a $107.00 for a game that i didn't buy, how do i resolve this problem?
-
Push/DataSource question about .cda files
Hi, I'm trying to programm a program and with it it should be possible to rip .cda files to .wav files. Now I found a way how to do this, but I'm not sure, if my idea works well. My idea: In Windows it is possible to play .cda files with JMF. I read,
-
Help - I am unable to receive e-mails on my i-pad since beginning of December. I can send them but not receive?